Fault with Sonar X2 and MCU protocol for control surfaces - problems with SSL Matrix
Hi,
I've been using Sonar for many years (since Sonar 7) with a Mackie Control Universal (+XT and C4) - i've had very few problems with this using the Chris Boucher template included in Sonar. I've upgraded through Sonar 8, 9 and X1 / 2 - and MCU control has been fine with Mackie control units.
I'm just trying out an SSL matrix, that also runs MCU as a communication protocol - and works seamlessly with other MCU enabled DAWs like Nuendo, cubase and Logic etc.
But Sonar X2 will not pick up the midi connection to the Matrix using the MCU template / protocol.
the Ethernet ipMIDI appear as MIDI devices in Sonar preferences - and are enabled as the only MIDI devices.
I see midi signals in the Sonar MIDI icon in the task bar (red flashing lights over the 'keyboard' icon) and I have no other midi equipment connected.
I can send midi signals (via ip MIDI) from the Matrix to other pieces of MCU protocol enabled software, RME total mix works fine - i have bi-directional control of the Matrix faders and track info on the scribble strips.
But Sonar X2 will not connect - i've deleted and setup from scratch, changed IPmidi channels.
From this set of info
- I have ipMIDI signals output from Matrix in MCU format
- These ipMIDI signals can control other MCU enabled software - bi directional communication occurs
- Sonar can see ipMIDI devices and is receiving MIDI signals
So my diagnosis is Sonars MCU template is not functioning as intended for many MCU based controllers, ther than Mackie ones - which is weird.
Others seem to be having the same problem with MCU communication between control surfaces and Sonar
http://forum.cakewalk.com/tm.aspx?m=2378785 Please can Cakewalk urgently fix this - or has anyone else found a solution?
I presume the same problem afflicts SSL Nucleus
thanks