Studio One and control surfaces

[Julien Ober]

Hi,

I recently created a new setup to replace a very old PC.

Everything works very well except for the control surface (Icon Qcon Pro G2) which is recognized by SO 7 but which does not send it any message, whether it is a new session or an old one.

The control surface firmware is up to date and there is no specific driver since it is basic MIDI hardware (which is also well recognized by win10 64 pro). I used a MIDI monitoring tool to see if the surface is sending messages and everything is ok. I disabled Boot Secure because Windows Support told me that it could block messages.

In short, everything seems OK and yet, nothing. The surface is recognized by SO but the software does not send it any message. Does anyone have an idea?

Thanks

 

[ShortRound_RB]

Did you ever figure this out? I seem to be having the same problem, and haven't figured out how to solve it.

 

[Bastiaan]

I am actually dealing with this exact problem for a Behringer FCB1010 floor board. Other MIDI devices work fine. Will report back if I find anything.

 

[Gerran]

Not only does your computer have to recognize the device, you'll also need to add it as an external device (control surface) in studio one. Make sure the device is set up to both receive and send data.

 

[ShortRound_RB]

Not only does your computer have to recognize the device, you'll also need to add it as an external device (control surface) in studio one. Make sure the device is set up to both receive and send data.

So that's exactly what's weird. It's all set up in the external devices, and studio one recognizes it being plugged in. I've found (in my case at least) Midi data is even often sent out the devices, and they see it (my keyboard's metronome or stop/play buttons light up to match the setting in S1), but for some reason S1 doesn't receive any midi messages sent out from the control surfaces (the play button doesn't respond when I press it, for example).

 

[OutrageProductions]

In the <input from> section of the <external devices> dialog, have you limited which MIDI channels are active? IIRC, the Icon series could be set internally to transmit on ch2 for example and the DAW was set to receive on ch1. System would recognize device but transmission was hindered. No joy.

 

[Sebby_McG]

Kinda feel like I'm now spamming the forum but hopefully this helps someone...

I had a similar issue on a Windows PC due to using and updating to the latest UA console firmware. If you're also using windows + UA Console than maybe this is the reason (I'll copy/paste from my thread)...

There seems to be an issue with the last UA Console update for Windows. There's an option in Console to use a MIDI controller. The latest UA update has a bug where it latches onto all available MIDI controller even when you don't select a MIDI device in Console's options. Because of this, no other software (ie Studio One) can use these MIDI devices. The problem appears to be due to UA, and not S1. I would think that an uninstall of UA and reinstall of the older version would solve the issue, but instead I went to Task Manager and disable/end the task that UA is using to connect to MIDI devices. I think its called UA Mixer Helper, UA Mixer Engine, or something like that (I'll update with the exact name when I'm back at my computer). I have to do this on every PC start up before opening S1.

Hope this helps someone!

 

[ShortRound_RB]

Kinda feel like I'm now spamming the forum but hopefully this helps someone...

I had a similar issue on a Windows PC due to using and updating to the latest UA console firmware. If you're also using windows + UA Console than maybe this is the reason (I'll copy/paste from my thread)...

There seems to be an issue with the last UA Console update for Windows. There's an option in Console to use a MIDI controller. The latest UA update has a bug where it latches onto all available MIDI controller even when you don't select a MIDI device in Console's options. Because of this, no other software (ie Studio One) can use these MIDI devices. The problem appears to be due to UA, and not S1. I would think that an uninstall of UA and reinstall of the older version would solve the issue, but instead I went to Task Manager and disable/end the task that UA is using to connect to MIDI devices. I think its called UA Mixer Helper, UA Mixer Engine, or something like that (I'll update with the exact name when I'm back at my computer). I have to do this on every PC start up before opening S1.

Hope this helps someone!

Oh my gosh, this was it exactly! Thanks so much!

Also, right when I started investigating what you said, UAD Console gave me an update, and the notes said something about MIDI devices, so I think the latest update fixes it, at least all my problems appear to have gone away for now. Maybe it'll fix it for you too?