Re: Settings query
Posted: Sat Nov 10, 2012 9:00 am
From your post it sounded like you might want to understand why Miditzer stopped when you held a button down on the Teensy unit. Stopping the keystrokes using Midi-Ox solves the problem when more notes are played while holding down a button but I think that the same thing will happen if you change a lot of stops at the same time and the Midi buffering gets full between the Miditzer->Midi-Ox->Teensy USB path. If you were using the Teensy “Callback” method to process the CC received commands, then a simple fix might be to call the usbMIDI.read() function while you are looping and waiting for the button to be released. This way then the keyboard noteOn/Off messages would be purged and the CC commands would be processed as needed and you wouldn't need Midi-Ox.bdalton wrote:Because of the way I've programmed the Teensy switch scanning loop, if I hold a stop switch pressed the loop stops running untill I release the switch, (this is to stop the Miditzer/teensy loop oscillating between stop On and stop Off),and the Midi input from Miditzer does'nt get serviced.
If play some notes in this situation fluidsynth does not respond untill I release the stop switch, then all the notes I played are quickely produced (on and off) by fluidsynth.