Strange problem with one of my synths when connected to my Midihub. The UNO Synth Pro X acts normally / as expected after a fresh start, but it stops responding to incoming MIDI Notes after I’ve started and stopped my sequencer(s) just once. All other information seems to be received and/or processed normally, so I can restart the sequence and change tempo. So start / stop and clock seem to work, but I cannot play notes on my KeyStep Pro or trigger it from my Digitakt (it normally fires when selecting a track).
The BSP is clock master and the USPX is set to MIDI channel 1, so it responds to sequencer / track 1 on the BSP. As said, with everything freshly rebooted, I can play notes on the keyboard and the UNO responds as expected. Same goes for track 4 on the BSP, it is set to channel 14 on which the DT is listening for its ‘selected track’. It routes the played notes nicely to the USPX when I have a MIDI track selected that’s sends on MIDI channel 1. This all stops working after I hit play and stop on the KSP…
What MIDI data could possibly overload or be missed on the USPX side that could result is this kind of behavior? It doesn’t matter if I use MIDI over USB or DIN. Hopefully some of you can clarify things up for me or point me in the right direction, before I have to send the USPX in for inspection. Thanks!
Hey, please upload the preset you currently use on your Midihub. (please ensure the MIDI ports are named so we know which ports are in use for what device)
I’d suggest you try and find the minimal amount of MIDI messages sent from Midihub to USPX to make it stop responding to notes (use the MIDI Monitor pane to see the exact output). Then post it up here, we can take a look and determine if the sequence seems valid.
First the stuff about CC56 etc I mentioned before refers to KS37 so that’s irrelevant!
the Unknown stuff you’re getting in the Monitor may just be to do with the fact that it’s set up to deal with 3 bytes of data at a time and Sysex doesn’t follow that pattern. @Giedrius will advise on this when he’s around, no doubt! (beyond my skill-set…)
Plugging in KeyStep Pro , I see the Sysex too (and no way in the “Control Center” to turn it off it seems)†
Okay, so it’s only the USPX that doesn’t respond well to the SysEx data (generated by the KSP)?
Ps. graphics are made in Snagit. It’s an image editor from TechSmith, mainly focused on e-learning and online help content. They also develop Camtasia, a tool for more instructional and interactive video content.
Yes, but I think I will test this also with a direct connection.
I can see that the software shows the information as ‘from KSP’, but I don’t know what kind of internal processing already took place. Or is is that ‘raw’?
AFAIK, the Monitor at any input shows all the data incoming.
Don’t forget your Monitor Settings, tho’: you can toggle various data types on&off so, if you changed them previously, some lines may be hidden from view.
Still curious why the Sysex is mucking up the Uno; I’d expect it to have Arturia id bytes so should be ignored.
Yes I know from the tutorials how to filter the Monitor, but this wasn’t the only reason why the output was cleaner.
After adding the suggested SysEx Filter to the Pipe the ‘crippled’ and blank Note events were gone, too. When removing the SysEx filter they show up again.
This I don’t understand. It seems to me as if the incoming signal is contaminated already and the that USPX is more prone to it then my other gear.
then go off for a while to think and test!
Thanks for the help and useful tip thus far!
