Steve Moddelmog Posted Saturday at 07:58 PM Share Posted Saturday at 07:58 PM I've been using a Nektar LX49+ keyboard with Sonar/Cakewalk/Sonar for many years. I use it almost exclusively as a keyboard, not as a control surface. Just recently, I am seeing sysx data when I view the Event List in every MIDI file. Files older than the past few months don't have any sysx data. What's going on?? I discovered it when I encountered a situation where Arturia's Synthx V plugin was silent for many presets. If I export the recorded MIDI track and then re-import it, Synthx V plays fine. Not sure what the sysx data has to do with it, but even deleting the sysx events didn't make those presets work - only exporting and then importing. Is there something that got accidentally turned on in Preferences that I should turn off to avoid this? Link to comment Share on other sites More sharing options...
Amberwolf Posted Sunday at 12:21 AM Share Posted Sunday at 12:21 AM There's a place (in MIDI options?) to choose to record Sysex data or not. But if the sysex data is causing a problem, it should cause that same problem every time it is sent from the source device, not just when it's played back in a track. If you don't see that happening, I'd guess the sysex isn't causing the problem, but some other data that is not exported in a MIDI clip (i don't know what is and isn't). Link to comment Share on other sites More sharing options...
Wookiee Posted Sunday at 10:45 PM Share Posted Sunday at 10:45 PM @Steve Moddelmog check the volume is not being zeroed. Check to see if zero controllers is set in Preferences, some Arturia synths suffer is this is enabled, Stage 73 is one. Link to comment Share on other sites More sharing options...
msmcleod Posted Monday at 08:31 AM Share Posted Monday at 08:31 AM FWIW, soft synths aren't sent Sysex data, so them being there shouldn't make a difference. You could take @Amberwolf's advice and uncheck "System Exclusive" from MIDI -> Playback and Recording within preferences. Beware however, if you're using a control surface, this may need to be left checked.... actually if you're using a control surface, it could be that sending the sysex out... double check your input ports. From what I can tell, the Nektar LX49+ only uses standard CC messages for it's buttons/knobs/faders, so it shouldn't be sending sysex out (unless you've initiated a MIDI dump), so it's likely coming from somewhere else. The other thing to check is your templates - as a sysex bank gotten itself into one? Link to comment Share on other sites More sharing options...
Wookiee Posted Monday at 08:58 AM Share Posted Monday at 08:58 AM @msmcleod I have noticed when recording MIDI with my Arturia Keylab 88 Mk1 that with certain Arturia instruments, if I look at the events list there is SYSEX data dumped at the end. During recording I have not used any of the sliders or knobs for automation. I haven't initiated a SYSEX dump it has just appeared. I normally delete it and it doesn't reappear even if I record more MIDI. The only thing I can think of is that I pressed the transport stop on the controller rather than use the computer keyboard. Link to comment Share on other sites More sharing options...
msmcleod Posted Monday at 10:54 AM Share Posted Monday at 10:54 AM 1 hour ago, Wookiee said: @msmcleod I have noticed when recording MIDI with my Arturia Keylab 88 Mk1 that with certain Arturia instruments, if I look at the events list there is SYSEX data dumped at the end. During recording I have not used any of the sliders or knobs for automation. I haven't initiated a SYSEX dump it has just appeared. I normally delete it and it doesn't reappear even if I record more MIDI. The only thing I can think of is that I pressed the transport stop on the controller rather than use the computer keyboard. Interesting.... is there more than one MIDI input port on the KeyLab? You might find that the transport messages are sent out on a different port, in which case you should probably be not using that port as an input for recording. FWIW - If you've set up a non-ACT control surface that handles messages on those ports, then they're usually "swallowed" before sent to the track for recording. Link to comment Share on other sites More sharing options...
Wookiee Posted Monday at 12:01 PM Share Posted Monday at 12:01 PM 1 hour ago, msmcleod said: Interesting.... is there more than one MIDI input port on the KeyLab? You might find that the transport messages are sent out on a different port, in which case you should probably be not using that port as an input for recording. FWIW - If you've set up a non-ACT control surface that handles messages on those ports, then they're usually "swallowed" before sent to the track for recording. The Controller does have two ports, one over USB and the other 5 Pin DIN. On my main computer I only use the USB port. The 5 pin DIN output goes to another computer altogether, via a PreSonus Audiobox USB, the MIDI DIN input on the keylab is not connected consequently it is unused. Link to comment Share on other sites More sharing options...
Steve Moddelmog Posted Monday at 12:45 PM Author Share Posted Monday at 12:45 PM Thanks for the replies. I'm going to assume that the sysx data had nothing to do with the behavior of the plugin with the MIDI track and that it was just an anomaly. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now