


I'm down to use something like this Midi Ox if necessary but these channel numbers and such are a bit mystifying. Its got the piano roll for notes and velocity but I don't see where I could examine program change, control change and note-off events. Issue still occurs with all effects off and decay/release all the way down.Īlso, Does anyone know if Ableton has a "midi log". Different patches are all the same issue, Panic button will not be helpful in a live situation (One held note could be ear splitting when clashing with another.), Not using Midi-Thru at all. I really want to lay down loops in ableton that I can tweak on the external synths. When I used all the same gear (Ableton 8 plus M-Audio Fastrak Pro) to sequence my M1 it was fine. I actually have two Novation synths and both glitch up (held notes and missing notes) when sequenced from Ableton. Is there any possibility your synth is a Novation? Note that if you have a really long MIDI thru chain you will probably get dodgy stuff like stuck/hanging notes from time to time. Continuously sending all notes off using a knob can result in some bizaare (read: AWESOME) behaviour if you twiddle that sucker quickly when stuff is playing. You can even do funky **** like assign a knob or button to send all note off messages thereby creating a panic button. Or you could script it so MIDI OX injects cc#123 message itself when cc#123 is sent by your DAW. If it doesn't send this message or its not firing properly you can setup a datamap so that if cc#123 is sent then fire cc#123 again. This sort of thing gets sent when you press stop on the transport in your DAW. For instance, you look for cc#123 (all notes off) messages in the event log. If the problem is 'unfixable' by conventional means then you can use data maps/scripts in MIDI OX to fire under certain circumstances where you get a stuck note. Other times its more complicated but you can diagnose a loop or a logjam with MIDI OX and looking at the event logs. Sometimes its as simple as turning off local control if you use a synth keyboard as your controller. Need more details about your setup and how its connected. Some synths deal with it better than others). As mentioned above it could be a MIDI feedback loop or a log jam (sending a buttload of MIDI messages to a synth at once which makes it cry. Lots of reasons that this could be happening.
