That said, I once wrote a patch in Pure Data that multiplied the knobs of a controller by creating an infinite number of banks. Does the regular MC mode work for more than 8 tracks? The issue is that with the regular MIDI mode you get one CC or Note per button/knob, and REAPER associates just one of those for each action, which are track dependent. No, this current solution works only for up to eight tracks. does it work for more than 8 tracks, like the MCU protocol? Can it bank previous/next and/or track previous/next? Just curious, thx again!
My code will only work with my custom layers and also if the X-Touch Mini device ID is set to 2 for both input and output. Top row of buttons: recording arm togglesīottom row: transport buttons, first one moves back to the beginning of project, second adds a marker to current position, the others are the same as the labels on the controller It keeps checking the faders and GUI buttons (mute, solo, etc.) every now and then, and then syncs back with the X-Touch Mini. This one is initialised using the global startup action from SWS.
I wrote scripts to reset pan and volume, and another one which syncs any movement in the GUI using the mouse back to the X-Touch Mini.
I also added my custom layers which need to be sent to the X-Touch Mini via its editor (I wanted some buttons to be true toggles, others to be regular momentary buttons). If anyone is ever interested, my code can be found here: I had come across that video but I decided to take a different route and write my own ReaScripts. Thank you so much for your reply, themixtape. I don't need each encoder to be volumes as that constantly changes depending on the project, but having them as useful Reaper functions works better for my workflow. buttons are transport, and additional ones like arm selected track, etc. One encoder is a jog wheel (left/right by measure), another is track scroll previous/next, and others are zoom horizontally, vertically, etc. I use my X-Touch Mini as a control surface using general midi / custom actions in Reaper. I never used it for anything other than Transport control, and the motorized faders. You can also consider a used Mackie Control Universal with the Klinke script, which I used for years. Lots of options, but nothing is insanely cheap. the motorized faders are great, and the position of everything is remembered, upon opening a project, depending on the bank (1-8, 9-16, 17-24, etc) you're on.
again, that's synth parameter stuff.įor volume control and transport (only), I think the Behringer X-Touch series (X-Touch, X-Touch Compact, and X-Touch One) work wonderfully. while not everyone is a fan of Automap, it does exactly what it needs to do, and you can save custom mappings, so they load as default, and everything remembers the positions depending on the active plugin. It's mostly for synth plugin parameters, though, from my research.Īnother option you can consider is instead, using a Novation Nocturn, which gives you midi feedback using Automap. It's a bit of an effort to set up, but it works. If you are looking for feedback from your controller, I suggest The Reaper Blog's YouTube channel, and his video about midi feedback. So I was wondering if this is also possible in REAPER: is there a way of sending all CC values from the project to the controller at the press of a key or when REAPER launches? I tested this with Pure Data: moving knob 1 will send values from CC1 ch11, but also sending any value between 0 and 127 from Pure Data to CC1 ch11 will override the state of the X-Touch Mini. The X-Touch Mini can both send and receive MIDI data. A solution is to enable soft takeover, of course, but I am looking for a different solution: If this is set to volume, this will then make the volume slider of track 1 jump to 0. If I move this knob now, it will override whatever I have got it set to control in my project. E.g., the first knob is CC1 channel 11 and starts at 0.
The issue I have is that when I launch REAPER after just connecting the X-Touch Mini, all CC values in the MIDI controller will be set to 0. In MIDI mode, I am able to assign actions to both layers and this works very well for me. I find the MCU mode rather limiting, even when using Klinke's MCU implementation. I recently bought a Behringer X-Touch Mini and I am trying to control REAPER with it using its MIDI mode (not the Mackie Control Universal mode).