Multiple controllers – midi ouput, feedback, Windows 11
Hi. What’s the trick to getting this to work? I’ve only gotten it to work once and not sure what I did differently that one time.
My setup: Multiple controllers (from Yaeltex) connected via DIN to MidiHubs. I use Bome to route those outputs into a single Virtual Port (call it BMT2) and then reroute back from BMT2 to the MidiHubs.
I had this working, without CSS. Midi mapping inside Ableton, I had feedback on every button on each controller.
In order to test CSS for what I need, I midi mapped one button with CSS. I deleted the midi mapping that was inside Ableton for this button, selected the CSS script under Control Surface, selected BMT2 for its Input and Output and it worked, encouraging me to complete midi mappings for 122 buttons across two controllers yesterday.
Went to test last night, no feedback. Not only no feedback, no control with anything that the CSS was supposed to control. So changed Control Surface and its respective Input and Output back to None and now no midi output at all. Multiple reboots, Bome log window now shows midi input working fine but no midi output at all. It is like CSS broke it.
So now I’m trying to get everything working back to where it was before, pre-CSS, which as I’m writing this, I just did, after deleting Virtual Ports and various other things. So that’s good.
I know Windows and midi are finnicky, can’t share midi ports across softwares and devices etc, that’s why Bome exists.
But what’s the trick to getting CSS to work? I saw the initial setup video and it makes it looks simple, just select the controller in Input and Output and it is supposed to work, but this is not working that way for me, even if I back everything down to just one controller and only using CSS mappings.
There must be something I’m not understanding because through this forum, not finding a lot people with the same problem. Insight?
Hi herbert,
Do you have any errors being generated from the script in the Control Surface Studio log?
Sign up
User registration is currently not allowed.
No but the problem isn’t the script itself. I actually got it working for a bit, on one controller, but the next controller, no. Same script basically, it’s the same messages just with different cc’s and track numbers and for the life of me could not get midi output/feedback on that controller. Nor understand why. Even if I make a unique midi ports for each controller, I could only ever get that one controller working. So I stopped working on it, have a gig coming up, need to practice and after that is done, will work on it again. Strange thing to me is that I haven’t had midi output/feedback problems for several years but the moment I selected an input and output for the CSS script, I couldn’t get feedback, whether the CSS script was selected as a controller or not. I ended up having to delete every virtual midi port and make all new ones with new names and even that didn’t work initially and then a couple restarts and poof, midi ouput/feedback worked again (with no CSS installed). So I don’t know. Was hoping someone might have some insight because I spent days trying to get feedback and I’d really like to get it working and move on.