MCC Error Message

[bcab17]

Just got a Keylab MK2. I turned it on. Opened my DAW (Reaper). Put an instance of Analog Lab on a track, and started trying things out. Then I opened MCC on my pc, and an error message popped up...something like "Device cannot be found. Confirm that the device is not in use by another application." I've tried this a few times, and either keep getting the same error or MCC won't open at all ("the program is not responding").

Does this mean that MCC and Reaper cannot be open at the same time...or is there a specific order in which I must:
Turn on the MK2. Open MCC. Open Reaper?

[LBH]

Does this mean that MCC and Reaper cannot be open at the same time

I don't have an Arturia controller to test. But if it works, when you close MCC  - at least before opening Reaper, then you have your answer i would say.

[bcab17]

Does this mean that MCC and Reaper cannot be open at the same time

I don't have an Arturia controller to test. But if it works, when you close MCC  - at least before opening Reaper, then you have your answer i would say.

Thank you for the reply.

[Koshdukai]

Windows MIDI drivers aren't multi-client, meaning, they can't "serve" multiple applications at the same time for the same MIDI port.

So, this is a natural thing to happen. If Reaper takes control of the USB MIDI Ports used by the KeyLab, then no other app can access it, like the MCC.
Likewise, if you start MCC before Reaper while the KeyLab is connected, Reaper won't be able to access it until you close the MCC.

On a sidenote, usually you'll use the MCC just to set things up on the KeyLab and then "forget" about it, only needing it again to do firmware updates to the KeyLab.

Some brands provide their own custom USB MIDI drivers that can support multi-clients (i.e. multiple applications using the same MIDI port). Arturia does this but only for specific products (like the PolyBrute, MicroFreak)

[bcab17]

Windows MIDI drivers aren't multi-client, meaning, they can't "serve" multiple applications at the same time for the same MIDI port.

So, this is a natural thing to happen. If Reaper takes control of the USB MIDI Ports used by the KeyLab, then no other app can access it, like the MCC.
Likewise, if you start MCC before Reaper while the KeyLab is connected, Reaper won't be able to access it until you close the MCC.

On a sidenote, usually you'll use the MCC just to set things up on the KeyLab and then "forget" about it, only needing it again to do firmware updates to the KeyLab.

Some brands provide their own custom USB MIDI drivers that can support multi-clients (i.e. multiple applications using the same MIDI port). Arturia does this but only for specific products (like the PolyBrute, MicroFreak)

That’s a perfect explanation. Than you so much.