Posted: 08 Jul 2014, 07:54
Hope this is the last thing I need to ask for help for awhile..
Summary is, I have rows of 16 patches being individually activated when receiving MIDI CC. THe MIDI CC is generated internally in Usine by 256 incoming program change messages being divided into 16 "banks" When one one row is activated, the previous row MUST be deactivated. All is fine and dandy with my hack job to make it work.. 93% of the time. The other 7%, I end up not deactivating the patches and end up with more than one row active at a time.
It seems like no matter how I set up the MIDI control for activating the patch, it always acts like a toggle, as in if I send CC #74 at any value from 0-127 and at any MIDI learn setting the patch is toggled on and off so I have built an overly elaborate method that receives "Patch ID" via bus when the patch is active, stores this value as the CC# to quickly send to the currently active patch to turn it off one bloc before the next selected patch is activated. While it may be creative, it's ghetto and unreliable. There must be a better way?
Usually I am missing something that is right in front of me.. :rolleyes:
(btw, the patch in the image is used to activate / deactivate 2 rows in parallel as I could not get another rack of patches to respond to the same CC on the same channel
Summary is, I have rows of 16 patches being individually activated when receiving MIDI CC. THe MIDI CC is generated internally in Usine by 256 incoming program change messages being divided into 16 "banks" When one one row is activated, the previous row MUST be deactivated. All is fine and dandy with my hack job to make it work.. 93% of the time. The other 7%, I end up not deactivating the patches and end up with more than one row active at a time.
It seems like no matter how I set up the MIDI control for activating the patch, it always acts like a toggle, as in if I send CC #74 at any value from 0-127 and at any MIDI learn setting the patch is toggled on and off so I have built an overly elaborate method that receives "Patch ID" via bus when the patch is active, stores this value as the CC# to quickly send to the currently active patch to turn it off one bloc before the next selected patch is activated. While it may be creative, it's ghetto and unreliable. There must be a better way?
Usually I am missing something that is right in front of me.. :rolleyes:
(btw, the patch in the image is used to activate / deactivate 2 rows in parallel as I could not get another rack of patches to respond to the same CC on the same channel