best control surface

pharohoknaughty · Post by **pharohoknaughty** » Mon Apr 03, 2006 7:56 am

Hello

I hope I got the right forum here. I am planning to use Scope as a monitor mixer and front end to my DAW.

My Question:

Can Scope support the CM Labs Motormix? It has motorized faders, and I use one right now to control Sonar. I like the build quality and size of these very professional grade controllers.

If they work with Scope, how in general do they control the mixer?

If I can't use the Motormix, I am planning to use a Peavey PC1600.

Any thoughts would be appreciated.

Post by **garyb** » Mon Apr 03, 2006 9:10 am

afaik, both work fine, but you will need to use midi, and you will need to make templates. also, since midi only supports 128 controllers numbers, you'll have to choose what to automate.

others can give you more details.

sidx · Post by **sidx** » Mon Apr 03, 2006 3:49 pm

hey
i am planing to use mackie control universe with scope.Hope all will be ok.

pharohoknaughty · Post by **pharohoknaughty** » Wed Apr 05, 2006 8:30 am

Bump. Anyone else know about this?

at0m · Post by **at0m** » Wed Apr 05, 2006 12:19 pm

Hi,

I'm not sure about the MotorMix, but I can tell you about Scope's Mixers' remote control

The Scope mixers respond to one channel or omni, even the big STM4896 can only use about 120 CC#. One knob can listen to one CC#. This config has a couple issues:

Some control surfaces send multiple channels and same CC# for similar controls, ie. faders sending all CC# 7 on MIDI channel as fader number. To fix this, a software routing through MIDI-OX or so is needed.
There's not enough CC# for all controls of the bigger mixers. Theoretically(*), by switching through multiple MIDI control presets of the device, different mixer panels can be controlled by the same CC# groups received on the same MIDI channel. To make 'vertical' MIDI remote on the mixer, so to say, so one patch of the control surface would link to all/most controls of a single channel.
(*)I say 'theoretically', since I've tried to link device MIDI presets to mixer channel numbers, but without success: Cycling MIDI presets on the fly seemed to put quite some stress on Scope, and sometimes controls would not be re-assigned properly.

Another option, as I'm using now, is to have a couple of control surface (Pc1600x for me, check my presets here ) presets together using up all of the max. 120 assignable CC# for mixer controls: level, pans, aux sends, mute, solo and some more. I've stored that in a default project, newly added stuff is assigned on the fly using different Pc1600x presets.
Note that the built-in channel fx' (EQ, compressor) controls cannot be assigned to MIDI, manually inserted fx can.

Whatever you choose to remote control on the mixers, current assignments that you move from the PC (mouse, keyboard) are always transmitted to the device's MIDI output. That MIDI can be used as feedback to the remote control surface, ie. to move the motorised to the correct position as on the Scope device.

Hope this helps...

at0m.

husker · Post by **husker** » Wed Apr 05, 2006 1:53 pm

On 2006-04-03 16:49, sidx wrote:
hey
i am planing to use mackie control universe with scope.Hope all will be ok.

Without scope supporting the MCU 'protocol' I think you might have trouble using the MCU effectively. I does send standard midi, but not in a 'normal' way. It uses pitch bend a lot to get 14bit resolution, and note messages. No CC at all, so not much match up with scope. The MCU display will also not work at all.

pharohoknaughty · Post by **pharohoknaughty** » Wed Apr 05, 2006 2:50 pm

Thanks for the response.

Looks like I should stay away from motorized faders, and use the Peavey PC1600.

16 faders is probably enough for me.

The way the manual reads, I can assign a fader to just about anything.

valis · Post by **valis** » Wed Apr 05, 2006 3:18 pm

There are a lot of CW users who use the Peavey PC1600 (and the x ver) with Scope.

buyakasha · Post by **buyakasha** » Wed Apr 05, 2006 3:58 pm

I have the MCU with 2 extenders and have been using them for some time and they work great. I use the Generic remote in SX on a 1 to 1 mapping. Save your project(s) and it's total recall. perfect.

The only problem I have when controlling the STM2448 from the MCU is the 'mute' button. It has a reverse polarity. So Off is On and visa versa.

The bigger problem is that Creamware haven't done and won't do F..k All about adding more midi channels to their mixers. It is(to my knowledge) one of (if not) the best mixer(s) you'll find in a computer. It's achilles heel will always be it's midi limitations. (Even the Generic Remote has 16 midi channels)

Anyway, as to say which is the best controller, there are many out there that can do just as good a job as the other. It would really depend on how much you wanna spend.

And the dispay does work with the MCU

<font size=-1>[ This Message was edited by: buyakasha on 2006-04-05 17:02 ]</font>

sidx · Post by **sidx** » Thu Apr 06, 2006 11:56 am

Tell me please can you make as example like this:
ONE page(as i imagine) on MCU - controlling SX (or any sequencer) and then
with immidietly switching to SECOND page - you controlling now STM2448 ?

Chisel · Post by **Chisel** » Wed Apr 12, 2006 10:04 pm

I don't get how you can use a controller without motorized faders in Scope. I mean, when you load a project, how do you get the physical faders to match exactly with the onscreen ones? I mapped three presets of my UC-33e to the faders on the STM2448, but I don't use it because of this shortcoming.

Peace /
Chisel

HUROLURA · Post by **HUROLURA** » Fri Apr 14, 2006 3:07 pm

What about a couple of Berhinger BCF-2000 ???

Post by **garyb** » Fri Apr 14, 2006 3:31 pm

On 2006-04-12 23:04, Chisel wrote:
I don't get how you can use a controller without motorized faders in Scope. I mean, when you load a project, how do you get the physical faders to match exactly with the onscreen ones? I mapped three presets of my UC-33e to the faders on the STM2448, but I don't use it because of this shortcoming.

Peace /
Chisel

afaik, you'll need to move the faders and then the controller will follow them thereafter. if the controller sends a reset or moves to a position when the preset is called up, then the on screen fader will follow the motor fader.