Qstick333 wrote: ↑Wed Jul 02, 2025 10:54 pm
I have arthritis that is getting worse and need to move to a control surface to avoid some of the mouse usage. I've been on Reaper for years and love it, but I am absolutely willing to move on. I'm pretty lousy with understanding all of the software (CSI, etc...) solutions that I read about.
What DAW and control surface will work best together, hopefully fully featured, and out of the box with minimal customization? Ideally, I'd like multiple faders and the ability to use the faders, pan, solo/mute, automate and transport. Beyond that, anything would be a bonus. That would at least help me get automation written and get initial levels and panning taken care of almost exclusively without a mouse.
Plugin control seems great, but I doubt I have the ability or time to get it going. My hands only allow so much in a day, and it won't be spent fumbling for hours

Thank you!
I use Cubase, because I am familiar with it, and have invested in it considerably over the years and I have used almost every controller known under the sun and none of them fulfill my needs, that said some have proved more useful than others. Nothing can be all things to all people.
I have found learning as many keyboard shortcuts as I can, and in Cubase, you can create macros, I am sure you can in other DAWS as well.
I use a foot controller for transport controls and have a few of the switches on the foot control assigned to macros, so for example I have one macro that stops recording, deletes the last take, goes back to the left locator, and starts recording again.
I also bought a Novation Launch Control which is designed to work with Ableton. However Cubase has a 'learn' function whereby the user can 'customize' the controller. It has a matrix of 8x8 pads which work as 'switches' +16 extra pads, 48 of the pads are assigned to track selection, so I can select any of 48 tracks at random, which I think is really useful. The other pads are configured to select from a set of commands I allocated to them. I would be happier using proper touch controls, the pads are a bit 'spongy'
I have recently bought a Nektar cs12 which is a single fader controller with quite a useful range of buttons and rotary controllers. The cs12 has one particular feature, in that it doesn't use the more common MCU protocol. The MCU assigns faders in groups of 8 and to move from say track 8 to track 9, you have to bank across, using the bank controls.
However, the cs12 'follows' track selection - remember I wrote the Novation allows me to select any of 48 tracks at random? well that comes in useful with a single fader controller, I jump from say track 3 to track 30, and the fader operates on the selected track. The cs12 also works as a quasi channel strip for the selected track. The cs12 also has similar functionality for the Logic DAW.
If you use an 8 fader controller, you might well still us the MCU protocol, yes you can leap from any of the track 1 to 8, and the fader follows that choice, but go beyond 8, and you have to bank along in jumps of 8. If you choose this option, your mixer in Cubase(or whatever) will have to be configged accordingly eg if I have 24 tracks and have 8 MIDI, 8 audio and 8VSTi then they will have to appear in the mixer - just saying, this had me going round in circles to figure out why, when I banked from 1-8 to 9-16, the faders didn't worked - reason, they weren't added to the mixer config DOH
What helped me was it dawned on me, created my own templates and treat my DAW exactly as I would a hard disk recorder - eg track 1 is always MIDI piano, track 2 is always MIDI bass, and so on, and I always leave some tracks empty, to accommodate other instrument I might not use all the time, and/or for my drum tracks, I use a VSTi drumkit, Groove Agent, and have one of 8 tracks always set to 1- kick, 2 - snare etc etc
That way, when I press whatever button, I know exactly what it does.
The mouse cannot be unplugged and given to the cat, but my dependence on it is much reduced. It will take time to set up and acclimatize, but it becomes a habit after a while, just takes some planning.
I also have a Faderport 16, which has 16 flying faders, but I find I am using the cs12 in favour of it these days, or because of the 16 faders (then bank across as described) I might use it for mixdown, have the 16 faders at my fingers is more useful at mixdown than when tracking so I am going to hold onto it.
I see Wonks mentions Studio One, the Faderport is optimized for Studio ONe, there is a Cubase Template but it isn't as comprehensive as the Faderport + Studio One combination. the cs12 (single fader bear in mind) is optimized for Logic and/or Cubase, it might have similar for Reaper but it pays to check of course