adrian4u

for now I'm not sure if "junk-CCs" are sent because of mechanical (soldering) issues or program issues. from one hand - it worked well after reloading program - even after few on-offs, but after day or two without power - I run keyboard and junk-CCs appeared again. From the other hand - I moved keyboard from one place to another. So - it can be something with chip, with connestions and with program.... Got to check it somehow... but it looks that I need few more days, because I have hard time in my office.

yup, I have multimeter, but I'm affraid that I'l have to get electronics out of the box. It's hard to visually controll all the connections, especially these analog ones. It's not "elegant" construction, so some pins are soldered with "shortcuts"

especially if I'm rookie, right :) as I mentioned above - first of all I will check connections, because I've seen somewhere on uCApps that accidental communicates can be sent if some free inputs arent grounded or something like this. It will take a while, cause I have to unscrew CORE and DIN and DOUT modules and take them out the enclosure. I can only guess, that there is something wrong concerning analog inputs, but I can be wrong. Maybe you have an idea what's up? Next thing is to find where in code (and in which file) I can define mIDI channel for outgoing MIDI messages from controllers.

Keyboard itself and Sustain work great - and keyboard and Sustain are on DIN and DOUT. But I still have troubles with MOD, AT, PB - and these controllers are cinnected to analog inputs (J5) I've fouynd some code lines concerning PB, MOD and AT - in MAIN.ASM file. those controls are connected to analog inputs. It seems for newbie that everything gonna be OK, but I can't find description, where to change MIDI channel of "Fatar pitchbend", and... I don't really know what's wrong with these controls - they still sending accidental values. I fixed itself after reloading program, but after 2 days of not being Maybe problem isn't in the code but in the CORE itself, or problem is somewhere in connections? I wanted to try latest MIOS to compare if theese errors will still appear but I'm affraid thar original program wil not work on higher version of mIOS. And I don't have MIOS 1.5 to load it back in case that program won't work on MIOS 1.9. Any sugestions?

Jim, I understand why I had to change only one number, I'll show you: In this example - what was very important to me - was changing value from 64 (HEX: 40) to 127 (HEX: 7F) but SUSTAIN is #CC: 40, so changing every "40" value into 7F did not gave me expected results, because somehow I changed #CC: 40 into #CC: 7F. What I finally did was line: I more-less understand why only this line - because it defines value that will be sent if SUSTAIN go to state 2 (pressed). I can (for now, because I have no Assembler skills for now) only assume, that lines: just determine #CC of controller. What I was looking for in meantime (and I'vefound it a week ago but I can't remember where) were lines with controllers definition. Next issue is that PitchBend (Roland Pitchbend - it's described like this somewhere in the code) in farest left sends accidental SysEX values like STOP, START etc (MIDIOX shows those values), and in farest right - it sends "G19 NOTE OFF".... totally weird. Moreover I want to change two things: 1. PitchBend WHEEL works on CH 3 instead of CH 1. 2. I want to change PitchBend WHEEL into #CC: 2 (Breath Controller) Later I have to check what's up with code or CORE, because I DID ERROR-FREE loading several times, I made few ON-OFFs, and keyboard was running great, but yesterday I had issues like in first post: - PB and MOD was sending acccidental values (mostly 0)..... Jim - is there another way (newer core?) to try to make this project simpler?

sO FAR SO GOOD: 1. i HAVE lcd 2. i made ONE change in code - so now SUSTAIN sends values 0 and 127. good :) 3. after reloading program - accidental PB MOD AT values sending - dissapeared. :) now - another issues. 1. check AfterTouch. There are two strips - one for white, one for black keys. AT on black keys don't work. 2. After extremly pushing MOD lever, it sends SysEX too! and "g19 NOTE OFF"... WTF?

TODAY, in Polnad we have New Year Eve.. so I go t work (party DJ). For now I'm getting familiar with code, moreover yesterday evening I had smal "session" with constructor of this keyboard, so I hope from 1-st of January I start first modification in code and debugging to check what's wrong with AT, Mod and PB - is it software or hardware problem, because constructor swears, that he had no problem like this :) We will see.

startup message on LCD: MEOS Z1.5 ?

true :) Thanks, Jim :)

well, before I go to journey I have to start with first step ;) so I will try both: to use what I have from previous owner, especially that he promised to help me if I'll stuck. and to use up to date version of MIOS Studio. We will see what will happen :) It looks that uCApps comunity is very special, because even on "my" forum, where I'm one of moderators, you won't find so helpful people sometimes. Maybe, when I'll learn more, I'll try to make little add-ons and modify/update some lines in code, but it's song of future. I concern is it worth to add more controllers (LCD, program/bank change buttons or dialer, free assignable pots and buttons), or leave it as it is - a great hammer action masterkeyboard only.

Jim, Keyboard project is operational, with some bugs I described above: main issues are PB, MOD and AT controllers. I would like to change Velocity response too (for now it starts from value +/- 20 instead of 1), but in this point it's not as important, because it works good as it is. Thank you very much for help in finding Sustain lines, Now I have to make changes in code, compile it and load to CORE. Which one MIDI Studio should I to use? this one in attachement (few post above) or this one from uCApps download?

Thanks, I've was thinking it's just a simple setup with Sustain, somewhere in code (setting min and max value). About a project - in a fact this is projest from CuBase I think (I don't know if this guy is present on this forum, but I can suppose that this is the person. He told me he had problems with this project, tears blood and sweat. Project is almost done, most irritating things are PitchBend, Modulation, AfterTouch. While PB and MOD wheels are doubled, so they go crazy if one PB is set to "0" and second is higher/lower; AT just acts like sending impulses of "0" and "actual" value. I will try to record it at home.

Believe me, I started to read uCApps a week ago - just maybe I'm not patient enough. Thank you for help, give me few more days - I wait for some stuff coming after Christmas - LCD, cables, etc.... And I'll let myself gto write here, ok? ;)

anyone would help me? I buy Polish vodka :)

for now I know that inside is CORE on PIC, DIN and DOUT only, I have code for this keyboard, compiler and loader, but still it's black magic for me :-/ I can send you code, compiler etc if you would like to see it.kompiler.rarsm_16x16_fatar_88wood_V2009.rar