+- Conductive Labs Support Forum (https://conductivelabs.com/forum)
+-- Forum: The NDLR (https://conductivelabs.com/forum/forumdisplay.php?fid=1)
+--- Forum: MIDI Connectivity (https://conductivelabs.com/forum/forumdisplay.php?fid=5)
+--- Thread: Start/Stop Midi Out conflict (/showthread.php?tid=2410)
Start/Stop Midi Out conflict - alexliberati - 02-13-2025
hello, first post here.
I currently have the NDLR sending MINI ch 1-2-3-4 for motifs, pads and drone, efficiently to 4 separate machines. It is all routed out of MIDI OUT A port and into the MRCC which is then rerouting.
No problem there, everything is working well, I can individually start and stop parts or I can start them all together and stop them all together.
No problem.
But.
When I want to use the NDLR to send a clock and start&stop to my drum machine, through MIDI OUT A hell breaks lose.
The error is that while the drum machine starts and stops and clocks correctly, all parts start at the same time even if I'm only playing a motif or a pad or any one of them. Furthermore, there seems to be Midi leakedge between the parts as it seems the machines are overlapping notes from other parts they should not be playing.
This is the procedure which gives me the error:
I go to settings page 1/3
Select Midi Out: MIDI A strt/stop
Press play on any of the four bottom buttons.
I have checked all my midi routing for loops and such, but there is no such problem.
Please help! XD
Thanks in advance!
RE: Start/Stop Midi Out conflict - alexliberati - 02-13-2025
I think start/stop seems like a relatively small midi msg, and I wasn’t sending any aftertouch or complex cc info.
So in my mind I should still have plenty of space on the same midi out.
I wonder if the problem lies in the MRCC routing… as in it not being able to process all that midi info on one midi in.