Thanks, yeah that makes sense and actually I confused the situation - I am in midi mode layer B with my mapped changes - I am hoping you ar right and this is just a Studio One setting because it seems I am almost there.
Another Q please - the CC assignments make sense to me so I think I can map them if I can get past the DAW setup , but other buttons/rotarys in the editor are all labelled as ‘notes’ how would I assign say a button to a transport control or another function…or is this impossible in midi mode? If I press play button in Layer B atm it opens a channel strips im assuming i could assign that to play etc? - just dont get the note values and how they relate to a daw function
Rotaries you can either make them CCs, absolute (from 1-127, like a fader), or INC/DEC (that means relative, twist right increases what you want, twist left decreases).
For the buttons, use notes. They come in handy if you want to control an on/off switch, like grids or anything that turns on and off, or shoot commands. Quantize, record, undo, etc.
But most of the game depends on what studio one wants to see when it comes to notes or CCs or anything else.
Edit: for the encoders, there’s a page for their Push function, which is sort of a button if you think about it, this one needs to be set as a note, yes. But on the next tab, you can configure the twisty motion of the encoders. So there’s two messages for each encoder. The push part, on one page, and the twist part on another.
A final tip: the global channel that you see? This is the MIDI channel that the Compact uses internally for its own purposes. Light up leds, move the faders, display the led segments around the encoders etc. I found that it’s a good idea to NOT send stuff to this channel FROM the DAW. So, keep this in mind if you notice any spooky stuff, like faders moving on their own when they’re not supposed to, or buttons lighting up seemingly at random.
perfect, thanks for all your help. I think I’m almost there, just need to figure out what Studio One wants. If I can get the expression/mod faders and the buttons mapped like a stream deck with the transport controls working as expected I will be happy …hopefully just a setting. thanks again, big help
thought id follow up - Big thanks to you for your patience. I have managed to get it all done and thought I’d post the solution for anyone else in the future who stumbles across this. So, for anyone else who uses Studio One:
I’m on mac, but editing the midi mode layer via pc and connecting to mac worked fine, all settings saved. For the cc1/cc11 etc faders was simple, just change the numbers as needed in the editor. Studio One only accepts CC commands, so the ‘notes’ for buttons and rotary all had to be changed to CC. In studio One all I had to do was create a ‘new control surface’ instrument, open the control settings, click ‘midi learn’ and push the button i wanted to assign, then assign a command/macro. I’m assuming if I create a Mackie control surface I can reboot the XTC into Mackie and use for mixing duties, but this is actually a secondary concern for me.
One thing to note, dont ‘midi learn’ the faders in studio one. Just assign then cc1/cc1 etc in the editor.
So I have managed to assign all the bottom buttons to commonly used keyboard shortcuts/macros and just wondering what to assign all the rotary for? How do you use them mostly as panning for me is mostly inside a Kontakt instance