View Single Post
Old 08-02-2020, 01:37 AM   #17
nightscope
Human being with feelings
 
nightscope's Avatar
 
Join Date: Sep 2007
Posts: 1,145
Default

Quote:
Originally Posted by oldmanstan View Post
Why isn't parameter control part of the control surface protocol?
Because the protocol that comes with the hardware is not designed for the DAW. Reaper, in this case. Each DAW has to implement a system to interface with the controller. Not the other way round. Some controllers use MCU[Mackie Control Universal] protocol. This will interface, by default, with Cubase and Logic mainly, giving FX parameter control and lots of other goodies. Best is in Logic as the MCU was developed originally for Logic by Emagic. Other DAW's, Live, Reaper, Samplitude, etc, have to use their own system designed by their dev's based around either Cubase or Logic MCU protocol templates that are baked, hardwired, into the controllers.

Your controller does use MCU protocol which will work with some DAW's, sort of, as far as I know. Reaper's native MCU is a bit of a threadbear wasteland, no FX, no sends, not much really. However, Klinke's .dll does do FX very well and is totally customisable and loads of other nice stuff. Also Geoff's CSI is another option, tho I know nothing about that.

The main problem with controllers like yours is that there is no LCD/Head Up Display so you have no way of seeing what's doing what and why. That is, which fader, pot is controlling whatever parameter in the DAW and when. Unless you use a virtual LCD/HUD in software. Which is a pain and leads to insanity.

ns

Last edited by nightscope; 08-02-2020 at 01:47 AM.
nightscope is offline   Reply With Quote