![]() |
|
#1
|
|||
|
|||
|
I am trying to use the pedal to switch back and forth between 2 maps. On my keyboard, I have mapped the pedal to CC80 - General_5. On the Synths menu, the pedal makes the view number jump around - incrementing by more than one on a press, usually decrementing by 1 on a release.
In live play, it does not seem to do anything at all. |
|
#2
|
||||
|
||||
|
Hi Cliff,
I currently check the incoming controller data by: if(data > 64) increment synths map (and update screen if synths screen) else decrement synths map (and update screen if synths screen) The MIDI 1.0 spec says: "If a receiver is expecting switch information it should recognize 0 - 63 (00H - 3FH) as off and 64 - 127 (40H - 7FH) as on." If your controller generates 0 and 64, then my above if statement would always decrement, which it doesn't. I'll change it to: if(data >= 64)... which is correct, per the midi spec. If I recall correctly at the time I tested this by remapping the sustain pedal, and controller 80 wasn't technically tested, so that could be an issue. -- still doesn't explain your symptoms. I suspect the synths maps are getting updated, but during real-time play, somehow they're getting reset back to previous values?? The actual code looks so simple, and I can't currently imagine any type of midi feedback loop, like Local On/Off being on. That can't happen here, since I don't send any midi controller events out, I just catch the incoming ones and update the actual synths map value then return. I'll keep exploring what could be happening. Thanks, Paul |
|
#3
|
||||
|
||||
|
At 3 in the morning it occured to me that, unlike the KG map pedal updates that simply require the map variable to change, during synths updates I need to send the updated patch, volume, pan, etc. out to the synths right when it occurs. When viewing the synths sceen this is automatically done since I redraw the screen.
Still doesn't explain the multiple pedal ups and unreliable pedal downs you're seeing. |
|
#4
|
|||
|
|||
|
Is it possible that the foot pedal has a really bouncy key switch? If you want me to drop my pedal by your place or anything else I can do to help troubleshoot, let me know.
|
|
#5
|
||||
|
||||
|
Internally I use a function called UpdateProgramsAndVolumes that goes through and sends out the latest program, volume, and pan changes if they are different than they were to the synths during synths map updates. I discovered I wasn't updating them at all, and added this routine at the correct places.
Now I'm trying to track down a really bizzar thing that generates duplicate control and program changes, but handles note on and offs just fine. So for each pedal up and down I get 2 events, which switches from synths map 0 to 2 to 0 to 2, etc. So if it's in your hardware, it's also in mine. It's happening right down where the system captures the midi messages, themselves. I can always filter out duplicate messages but that's a bandaid and not the cleanest approach. I've eliminated all midi buffering, that's not it. Thanks for offering your support, think it's in my hands for now, To be continued... |
![]() |
| Thread Tools | |
| Display Modes | |
|
|