3 MCUs or 1 MCU and 2XTs?
Posted: Tue Apr 16, 2013 6:02 amAre y'all using 3 MCUs, or 1 MCU and 2 XTs in your DAW setup to integrate with D8Bridge?
I realize I'm pretty far down the road to be asking this basic question, but in Sonar X2a I've always had it configured as 1 MCU and 2 XTs like the Presonus StudioOne example in the D8Bridge version 1.1 Quick and Dirty Instructions.
I was flipping through the Quick and Dirty Instructions again tonight and I noticed that in the Nuendo example, 3 MCUs are being used, not 1 MCU and 2 XTs. So there's a discrepancy in device type between the Nuendo example (3 MCUs) and the StudioOne example (1 MCU and 2 XTs).
One of the reasons I ask this is that when I examine the startup MIDI messages between Sonar and D8Bridge, Sonar is trying to initialize with D8Bridge on the 3 MIDI interfaces saying it has 1 MCU (using MIDI SysEx Device ID 0x14 = MCU) and 2 XTs (using MIDI SysEx Device ID 0x15 = XT), which is how I set it up, but D8Bridge is responding with complete disregard saying it is not acknowledging 1 MCU and 2 XTs but is instead acknowledging 3 MCUs (all MIDI SysEx Device IDs are 0x14 = MCU).
From Sonar - Device IDs 0x14, 0x15, 0x15
From D8Bridge - Device IDs 0x14, 0x14, 0x14
Trying to "fix" the XT machine ID responses from D8Bridge to 0x15 (using Bome MIDI Translator) only serves to break a lot of control surface functionality for channels 9 through 24. I guess I'm going to try experimenting with setting up my DAW interface to 3 MCUs rather than 1 MCU and 2 XTs, but I thought I'd check in here first and see what everybody else is using. Thanks!
I realize I'm pretty far down the road to be asking this basic question, but in Sonar X2a I've always had it configured as 1 MCU and 2 XTs like the Presonus StudioOne example in the D8Bridge version 1.1 Quick and Dirty Instructions.
I was flipping through the Quick and Dirty Instructions again tonight and I noticed that in the Nuendo example, 3 MCUs are being used, not 1 MCU and 2 XTs. So there's a discrepancy in device type between the Nuendo example (3 MCUs) and the StudioOne example (1 MCU and 2 XTs).
One of the reasons I ask this is that when I examine the startup MIDI messages between Sonar and D8Bridge, Sonar is trying to initialize with D8Bridge on the 3 MIDI interfaces saying it has 1 MCU (using MIDI SysEx Device ID 0x14 = MCU) and 2 XTs (using MIDI SysEx Device ID 0x15 = XT), which is how I set it up, but D8Bridge is responding with complete disregard saying it is not acknowledging 1 MCU and 2 XTs but is instead acknowledging 3 MCUs (all MIDI SysEx Device IDs are 0x14 = MCU).
From Sonar - Device IDs 0x14, 0x15, 0x15
- Code: Select all
0002B449 5 -- F0 Buffer: 8 Bytes System Exclusive
SYSX: F0 00 00 66 14 1A 00 F7
0002B449 7 -- F0 Buffer: 8 Bytes System Exclusive
SYSX: F0 00 00 66 15 1A 00 F7
0002B449 9 -- F0 Buffer: 8 Bytes System Exclusive
SYSX: F0 00 00 66 15 1A 00 F7
From D8Bridge - Device IDs 0x14, 0x14, 0x14
- Code: Select all
0002B44A 4 -- F0 Buffer: 8 Bytes System Exclusive
SYSX: F0 00 00 66 14 1B 00 F7
0002B44B 6 -- F0 Buffer: 8 Bytes System Exclusive
SYSX: F0 00 00 66 14 1B 00 F7
0002B44B 8 -- F0 Buffer: 8 Bytes System Exclusive
SYSX: F0 00 00 66 14 1B 00 F7
Trying to "fix" the XT machine ID responses from D8Bridge to 0x15 (using Bome MIDI Translator) only serves to break a lot of control surface functionality for channels 9 through 24. I guess I'm going to try experimenting with setting up my DAW interface to 3 MCUs rather than 1 MCU and 2 XTs, but I thought I'd check in here first and see what everybody else is using. Thanks!