Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MIDI Clock issue
#1
I’m encountering an issue with the MIDI clock that I can’t quite figure out. I use The NDLR as the clock master and a mioXL to distribute its USB output to all devices that need to sync. However, in this setup, only about 50% of my devices respond to the clock signal.

Here’s the odd part: if I unplug the USB cable from a non-functioning device (let’s call it Device A) and plug it into a functioning device (Device B), Device B syncs perfectly. This suggests that the cables and mioXL routing are fine.
When I switch to using my DAW as the clock master (with a different mioXL configuration), everything works flawlessly. This leads me to suspect that there’s something unusual about the MIDI clock output from The NDLR that I can’t explain. MIDI clock should be one of the simplest things, right?

I conducted another experiment: one of the machines that doesn’t sync to the NDLR’s clock can still play a motif perfectly. However, when I filter out all MIDI messages except the clock (including note ON and OFF messages), it still doesn’t sync. How is it possible that this machine receives the clock signal from the DAW without any issues, but not from The NDLR?

Unfortunately, I don’t know how to monitor or “spy” on The NDLR’s MIDI output directly, but I suspect it might be sending messages that some devices can’t handle. For example, I noticed a delay pedal changing its configuration even though it wasn’t mapped to any MIDI channel on The NDLR. I resolved that issue by drastically filtering out everything except the clock signal, and the pedal behaved normally after that.
Reply
#2
Can you let me know what fw version you're running and on which hardware version?

This one is tricky to diagnose, since we have so much going on and we don't have access to the MioXL to test it. Not to say there isn't a bug here, just that without a way to reproduce the issue on my end it's almost impossible to find out let alone solve it. It may help to know what devices are in play besides the Mio. Additionally, a good test to try might be something like connect the NDLR to the computer, connect device A to the computer via USB and use a MIDI utility like MIDI OX to pass the NDLR clock to the device and see if it works that way. It would be easier to recreate that for example.
Reply
#3
(01-30-2025, 06:46 PM)Jesse Johannesen Wrote: Can you let me know what fw version you're running and on which hardware version?

This one is tricky to diagnose, since we have so much going on and we don't have access to the MioXL to test it. Not to say there isn't a bug here, just that without a way to reproduce the issue on my end it's almost impossible to find out let alone solve it. It may help to know what devices are in play besides the Mio. Additionally, a good test to try might be something like connect the NDLR to the computer, connect device A to the computer via USB and use a MIDI utility like MIDI OX to pass the NDLR clock to the device and see if it works that way. It would be easier to recreate that for example.
Yes, it's definitely tricky, and I'm increasingly suspecting that the issue lies with the mioXL itself. I've seen similar reports on forums from others experiencing the same problem (without the NDLR involved). At first, I thought there might be something wrong with my machines, but then I noticed that some machines began randomly exhibiting the same behavior. Interestingly, while I was tweaking the mioXL with the Auracle editor, everything suddenly started working perfectly, but after a power cycle, the issues returned. I'm not sure what else I can do at this point, so I've logged a support ticket with iConnectivity.
Reply


Forum Jump:


Users browsing this thread:
2 Guest(s)