+- Conductive Labs Support Forum (https://conductivelabs.com/forum)
+-- Forum: The NDLR (https://conductivelabs.com/forum/forumdisplay.php?fid=1)
+--- Forum: General Support (https://conductivelabs.com/forum/forumdisplay.php?fid=2)
+--- Thread: USB 1 Clock In - Pads are not Triggered (/showthread.php?tid=139)
USB 1 Clock In - Pads are not Triggered - MKS30 - 03-10-2019
Latest Firware
When using 'USB 1/ Clock in' and enabling 'Clock and Start/Stop' in Bitwig, Motifs 1 @ 2 emit ok, but Pad does not emit Midi.
When using 'USB 1/ Clock in', Pad is only emitting when triggered by sweeping: Position, Range or Spread controls i.e the Chord Buttons do not trigger the Pad notes without the sweeping action.
Any ideas on what might be going on?
NDLR Cntrl 1 All
KB Trans 1 All
MIDI Out ALL Ports
Clock In USB1
Pad 2USB1 or '2USB1 | 3USB1 | 4USB1 | 5USB1'
Drone 3USB2
Motif1 4USB3
Motif2 5USB4
** note: The NDLR does not like SPP or MTC being enabled from Bitwig, will not play at all.
RE: USB 1 Clock In - Pads are not Triggered - Darryl - 03-10-2019
The NDLR doesn't use Start when using an external clock. It starts when the clock starts. It should start all parts that are armed. See the manual (version 1.3) page 32 (section titled "External MIDI Clock & Stop/Start/Continue Messages").
NDLR Cntl and KB Trans must be on separate ports.
RE: USB 1 Clock In - Pads are not Triggered - MKS30 - 03-11-2019
(03-10-2019, 10:36 PM)Darryl Wrote: The NDLR doesn't use Start when using an external clock. It starts when the clock starts. It should start all parts that are armed. See the manual (version 1.3) page 32 (section titled "External MIDI Clock & Stop/Start/Continue Messages").
NDLR Cntl and KB Trans must be on separate ports.
1.3 manual: "MIDI 5 Pin port B & USB port 1 - MIDI Stop/Start/Continue messages are ACCEPTED"
Bitwig triggers nothing unless Start/Stop is enabled. Nice to note that hitting Start repeatably, now Start/Stops the NDLR...nice
** Changing KB Trans to another port, solved the reported 'Pads not triggering when using external clock' issue...I would suspect this to be an unintended side effect of having both Cntl and KB Trans on the same ports.
RE: USB 1 Clock In - Pads are not Triggered - Darryl - 03-12-2019
Quote:1.3 manual: "MIDI 5 Pin port B & USB port 1 - MIDI Stop/Start/Continue messages are ACCEPTED"We must have meant, accepted and put into the bit bucket
We'll take a look at that and clarify or adjust the behavior.We should probably prevent choosing the same port for KB Trans and Cntl
RE: USB 1 Clock In - Pads are not Triggered - MKS30 - 03-13-2019
(03-12-2019, 11:34 PM)Darryl Wrote:Quote:1.3 manual: "MIDI 5 Pin port B & USB port 1 - MIDI Stop/Start/Continue messages are ACCEPTED"We must have meant, accepted and put into the bit bucket
We should probably prevent choosing the same port for KB Trans and Cntl
Cheers, it's a genius device..and an real adventure to integrate