Below are the new startup messages. Among the many things I don't yet understand about MT is whether I have to explicitly install a translator inline, interrupting an internal MIDI path between D8Bridge and Sonar or does MT insert itself when specifying a particular internal port to translate? I think I've got a lot more troubleshooting ahead Going out of my mind at this point
|Date Added:||24 May 2013|
|File Size:||59.8 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I used no rules for the d8briege translators. Do I need to do MT routing to accomplish this translation or not? The original messges that got through anyway but shouldn't have are in red.
Here are the control surface port mappings in Sonar X2a. Let me do some digging and see why it's coming up. Anybody have any ideas for how to prohibit c8bridge of the two original messages I'm translating? Yes, this makes sense and it's kinda where my brain was headed.
Does that make sense? Unfortunately, the MT corrected messages seem to have had no substantial positive effect on the integrated operations of Sonar X2a and D8Bridge v1. This forum is read-only.
Translator entries, now in a single MT project - 'xt-not-mcu. I believe that Sonar is ignoring the second message of each pair with the correct machine ID since it is a redundant message type apart from the corrected machine ID. I think I've got a lot v8bridge troubleshooting ahead Granted, you can do this whole process with only MT's Virtual Ports which will be more efficient but you want to make sure that the D8Bridge is not sending to the same port in MT as in Sonar, so nothing gets duplicated across the applications.
Any assistance from the MT community for how to wire this translation up would be a huge help. Don't hesitate to bring questions here. I'll let you know how I make out. Once I figure out the details I'm going to try rewiring as below. I condensed the two projects into one project file with two translations.
This is because subsequent messages from Sonar on the two XT ports, ports 4 and 6, all specify the 0x14 machine ID, the first meassage type of the two pairs passed without f8bridge. Going out of my mind at this point How hard could it be?
Newbie MT wiring advice request - Bome Forum -- READ ONLY
I still don't understand the distinction between the two port types in MT, but this seems to have worked. Take a deep breath, though, I think you're almost there.
Below are the new startup messages. F0 00 00 66 15 1B 00 F7 ; Correct translation to machine ID 0x15 - D8BRidge response to second XT on port 5 If anybody has any brilliant ideas for how to guarantee that the original messages being translated can be prevented from passing on to the interface I'm all ears. Those messages are as follows. Among the many things I don't yet understand about MT is whether I have to explicitly install a translator inline, interrupting an internal MIDI path between D8Bridge and Sonar or does MT d8bridgr itself when specifying a particular internal port to translate?
Another thing I have been wrestling with, unwittingly, is the D8Bridge software appears to be hyper-tweakish about new or removed MIDI ports between invocations; those actions seem to really screw up its internal MIDI port indexing and mapping.
I think your MIDI routing is the issue here. Regardless of that, good luck.
X2 MCU Users and X2 d8b/D8Bridge Users: SELECT Button Behavior?
Thank you very much for the feedback! This is probably an easy question for most of you but I'm a bit lost at the moment. So do those not work? I setup 2 translator project files, 'xt-not-mcu-3' and 'xt-not-mcu-5', both setup to translate input F0 00 00 66 14 1B 00 F7 to F0 00 00 66 15 1B 00 F7 and to swallow the inbound MIDI message. When Sonar first boots it sends a series of 3 SysEx messages queries, I believe to what it thinks is an MCU unit and 2 XT units control surface definitions manually configured inside Sonar by the user.