Hi,
I checked this on mine and I can see the clock going thru the NDLR.
My config:
I have a Arturia Beatstep connected to MidiB in and set the clock to external on the NDLR.
I conncted the NDLR via USB to the Computer and used MIDI-OX to monitor the output of the NDLR.
The midi settings in NDLR are adapted that the 4 different parts send to USB1 - the other 4 parameters on the right are default - esp. MIDI Out has "NO PORTS".
As soon as I press start on the Arturia the Time starts ticking and the Drone (in this example) is getting played.
When I press Stop, the note off is sent and the clock stops ticking.
The result is the following:
However you see no Start or Stop Message. I reconfigured then to make it according to midi thru settings of the manual.
Configuration is now:
Arturia in to Port B, all 4 midi outs to USB2. I also set the MIDI Out to USB2. There is no change in behaviour other that I now receive the Note-On/Off of a key pressed on the Arturia and the Mi
Again i can now see the Control Change of the Arturia (which for whatever reason sets and resets the mod wheel every start and stop) and I can also see notes coming thru I play on the keyboard, however still not Start/Stop Message. It looks like its gets filtered.
This is how it should look like if the messages would come thru:
Please remark that the Start and Stop messages came in to Midi-OX directly via the USB Midi channel of the Keystep and not thru the NDLR. You can identify that by looking at the midi Channel.
What I also do not understand, why it is sending out the clock at channel 4 (also all other events from the NDLR) as I am only using the drone for this example (hence the single note on command) and would have expected channel 3
So - I would consider that a bug.
I checked this on mine and I can see the clock going thru the NDLR.
My config:
I have a Arturia Beatstep connected to MidiB in and set the clock to external on the NDLR.
I conncted the NDLR via USB to the Computer and used MIDI-OX to monitor the output of the NDLR.
The midi settings in NDLR are adapted that the 4 different parts send to USB1 - the other 4 parameters on the right are default - esp. MIDI Out has "NO PORTS".
As soon as I press start on the Arturia the Time starts ticking and the Drone (in this example) is getting played.
When I press Stop, the note off is sent and the clock stops ticking.
The result is the following:
Code:
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00013376 2 -- F8 -- -- -- --- Timing Clock
00013377 2 -- 82 30 00 3 C 3 Note Off
00013377 2 -- 92 30 7F 3 C 3 Note On
000133C6 2 -- F8 -- -- -- --- Timing Clock
00013418 2 -- F8 -- -- -- --- Timing Clock
0001346B 2 -- F8 -- -- -- --- Timing Clock
000134BF 2 -- F8 -- -- -- --- Timing Clock
00013513 2 -- F8 -- -- -- --- Timing Clock
00013567 2 -- F8 -- -- -- --- Timing Clock
000135B9 2 -- F8 -- -- -- --- Timing Clock
0001360D 2 -- F8 -- -- -- --- Timing Clock
0001365F 2 -- F8 -- -- -- --- Timing Clock
000136B4 2 -- F8 -- -- -- --- Timing Clock
00013706 2 -- F8 -- -- -- --- Timing Clock
0001375A 2 -- F8 -- -- -- --- Timing Clock
000137AC 2 -- F8 -- -- -- --- Timing Clock
00013801 2 -- F8 -- -- -- --- Timing Clock
00013854 2 -- F8 -- -- -- --- Timing Clock
000138A7 2 -- F8 -- -- -- --- Timing Clock
000138D9 2 -- 82 30 00 3 C 3 Note Off
However you see no Start or Stop Message. I reconfigured then to make it according to midi thru settings of the manual.
Configuration is now:
Arturia in to Port B, all 4 midi outs to USB2. I also set the MIDI Out to USB2. There is no change in behaviour other that I now receive the Note-On/Off of a key pressed on the Arturia and the Mi
Code:
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00001443 4 -- B0 36 7F 1 --- Control Change
00001445 4 -- F8 -- -- -- --- Timing Clock
00001445 4 -- F8 -- -- -- --- Timing Clock
00001445 4 -- 82 30 00 3 C 3 Note Off
00001445 4 -- 92 30 7F 3 C 3 Note On
00001494 4 -- F8 -- -- -- --- Timing Clock
000014B7 4 -- B0 36 00 1 --- Control Change
000014E8 4 -- F8 -- -- -- --- Timing Clock
0000153B 4 -- F8 -- -- -- --- Timing Clock
0000158E 4 -- F8 -- -- -- --- Timing Clock
000015E2 4 -- F8 -- -- -- --- Timing Clock
00001635 4 -- F8 -- -- -- --- Timing Clock
00001688 4 -- F8 -- -- -- --- Timing Clock
000016AA 4 -- B0 33 7F 1 --- Control Change
000016AB 4 -- 82 30 00 3 C 3 Note Off
000016FE 4 -- B0 33 00 1 --- Control Change
000027F2 4 -- 90 3C 61 1 C 4 Note On
00002878 4 -- 80 3C 00 1 C 4 Note Off
000034F0 4 -- 90 37 58 1 G 3 Note On
00003554 4 -- 80 37 00 1 G 3 Note Off
Again i can now see the Control Change of the Arturia (which for whatever reason sets and resets the mod wheel every start and stop) and I can also see notes coming thru I play on the keyboard, however still not Start/Stop Message. It looks like its gets filtered.
This is how it should look like if the messages would come thru:
Code:
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00010464 1 -- FA -- -- -- --- Start
00010468 4 -- B0 36 7F 1 --- Control Change
0001046A 4 -- F8 -- -- -- --- Timing Clock
0001046A 4 -- 82 30 00 3 C 3 Note Off
0001046A 4 -- 92 30 7F 3 C 3 Note On
000104B9 4 -- F8 -- -- -- --- Timing Clock
000104F5 4 -- B0 36 00 1 --- Control Change
0001050D 4 -- F8 -- -- -- --- Timing Clock
00010550 1 -- FC -- -- -- --- Stop
00010555 4 -- B0 33 7F 1 --- Control Change
00010556 4 -- 82 30 00 3 C 3 Note Off
000105AD 4 -- B0 33 00 1 --- Control Change
Please remark that the Start and Stop messages came in to Midi-OX directly via the USB Midi channel of the Keystep and not thru the NDLR. You can identify that by looking at the midi Channel.
What I also do not understand, why it is sending out the clock at channel 4 (also all other events from the NDLR) as I am only using the drone for this example (hence the single note on command) and would have expected channel 3
So - I would consider that a bug.