🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left... mailtimers.com
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Your shopping cart is empty.

Midi monitor doesn't work when ableton is open

Submitted by godboat on Sat, 11/06/2021 - 20:43
godboat
Control Surface Studio User

System: Razer Blade Stealth 10th gen intel i7 Windows 11, Ableton 11, most recent CSS

So I'm having several issues with CSS and I'm wondering if there related and anyone has experienced this before?

If I open ableton, then CSS, my launchpad mini MK3 does not show up in "connected midi inputs" I need to close ableton and css, then reopen css to get the launchpad to appear in the midi monitor.

If I open css first, then ableton, the launchpad will not show up in the midi devices section in ableton and I get no midi signal into ableton, though it remains connected to css.

This problem feels like exclusive mode on audio devices, though I didn't know that was a thing with midi devices.

The problem with this is that, when attempting to create a new script in css, it makes it really hard to do anything and I get no output in the css log from ableton when following one of the remotify tutorials that haves you check the logs to confirm a script is working.

So yeah, anyone know why none of my midi devices cannot connect to both applications simultaneously and why I get not feedback in the logs whenever I set it up?

Thank you.

Topic Category: 

2 Responses

Comments

fatphil
Control Surface Studio User
#1

I've got the same problem. I've got in to the habit of opening and closing each application in turn for each change I make. It's not a very smooth workflow.

Apparently on Windows some external devices can't talk to 2 apps at the same time. One app gets an exclusive handle I believe.

I'm wondering if something like MidiOx or LoopBe1 (or LoopBe30) would be a way of working around this problem. Has anyone on Windows figured out how to do this?

trololololol
Control Surface Studio User
#2

It doesnt work properly with boom etc. Its on the driver side....