Adding new MIDI interface disables my Control Surface

[jeff s]

I've recently decided to get back into recording MIDI tracks and incorporating some drum machines and vintage synths. Over the years, I have mostly used SONAR (and CW ProAudio) as a tape machine as I tend to record full bands ensemble in the live room - that's more my thing as I came from the pre-digital/MIDI world.  My last significant MIDI experiences were back when everything was trying to sound like Miami Vice and very machine-like.... but I digress.

I am currently still running Platinum on a Win10x64 PC (but I continue to install the latest version of CW by BL, but I'm just more comfortable in Platinum) .  This is a commercial studio so change is slow or avoided when things just work as is.  I use RME HDSP 9652 as my interface and am utilizing the 2 MIDI ports to control my 2 (original) Mackie Control surfaces along with a Frontier Tranzport (USB).  It's been bullet proof :) 

So now I try to add an external MIDI interface (MOTU USB Fastlane or an Arturia USB interface via DrumBrute) and when I attempt to use them, they work but disable my control surfaces.  I really need to use the control surfaces...  any thoughts or suggestions on where to start trouble shooting?  I'm sure they can both co-exist but darned if I know ;)

Thanks!

jeff

 

[Gswitz]

In the preferences, you can choose which midi device is mapped to your controller.

It is default behavior that when you unplug the midi device mapped to your controller, if you have another midi device [rme] it maps that.

It is very confusing behavior but easily fixed of you recognize it.

If that does not fix it for you, try removing the controllers temporarily. Then add them back.

I have a frontier alpha track for which the azslow driver does wonders.

http://www.azslow.com/index.php?PHPSESSID=0869hkhnigi7pbn5kbp8occol0&action=downloads

I'm not sure if this might help you too.

Edited March 21, 2020 by Gswitz

[jeff s]

Thank you for the reply.  I will give that a try.  I recall having an issue when I upgraded my DAW hardware and did a rebuild for Win10x64.  I had a heck of a time getting my second controller (Tranzport - USB) to work properly with my Mackie Controllers (via RME midi ports) - I think I understand what you are saying: 

• Delete RME midi ports
• add new midi interface (MOTU Fastlane)
• reinstall RME ports for controllers

I'm not familiar with the azlow driver but I have seen that mentioned in other threads when I have been researching my issue.  I will look into that also.  I'm sure there is a way to have them all working, I just need to get the right method of installation sequence (?).  I am surprised that it's that finicky ....  Thank you again!  

[Gswitz]

I was really going for 2 things. One is midi devices and one is midi controllers. In the controllers image attached, you can see where the device is specified. Make sure the right device is specified for the right controller. When this gets flipped so the devices are controlling the wrong thing, it won't work.

Below, you can see that my Alpha Track (AZ Controller -1) has been assigned to my RME UCX Midi Port. This is wrong. I will NEVER run my Alpha Track (USB) through my RME. To fix this, I can either plug in my Frontier Alpha Track and map it to this controller or I can delete the controller.

If I do nothing, I cannot use the Midi from UCX Midi Port 1 for anything, including soft synths.

Edited March 22, 2020 by Gswitz