Hi
Just watching the video Sonar X2 complete it is very good.
 
On the section of control surfaces I got confused.
I am using a Quad  Capture and my keyboard is an M-Audio.
 
They are working but not 100% sure if I have the correct control surface assigned for the hardware,
 
I have used Cakewalk Generic Surface for the Quad Capture and Act Midi Controller for the M-Audio keyboard.
 
They work but   is there a better control surface for both bits of hardware? Or should I leave well alone?
 
I am a little confused also in the area of input output for my keyboard. I am not using it to control anything so I guess I don't need and out Port?
 
If anyone out there is using the same setup as me please can you let me know your settings?
 
Thanks
jorel

Neither one of those is a control surface. A CS is a hardware device that controls faders and transport as well as many other things. Mackie Control is a control surface. VS 700 is a control surface. 

I'm not sure John but the M-Audio might have faders knobs etc in a similar way to the PCR and A-Pro range. NOt sure about the Quad capture though.

If they do have a control surface element unless they have their own surface protocol or work with one (such as the MackieControl) then generic and ACT are probably the best bet.

The surface I used to demonstrate those in the video was my ZED-R16 which has a MIDI control section but no specialised surface. The knobs, faders, and buttons are connected via ACT and I use the generic surface for the transport element.

Just noticed the out port part.....

The out port is only usually needed if the controller has motorised faders or lights to indicate knob position etc. If it doesn't it won't need (or possibly not even have) an out port.

Thanks for buying the video BTW.

FastBikerBoy


I'm not sure John but the M-Audio might have faders knobs etc in a similar way to the PCR and A-Pro range. NOt sure about the Quad capture though.

If they do have a control surface element unless they have their own surface protocol or work with one (such as the MackieControl) then generic and ACT are probably the best bet.

The surface I used to demonstrate those in the video was my ZED-R16 which has a MIDI control section but no specialised surface. The knobs, faders, and buttons are connected via ACT and I use the generic surface for the transport element.

I have an M-Audio 88 Pro and it is no control surface even though it has somewhere around 50 buttons knobs and sliders. It even has a transport section that I have never gotten to work. it works well enough under ACT for controlling a synth but not Sonar.  

If it has knobs and sliders it should be possible to map the controls for use in Sonar.

It is a two stage process though - MIDI learn the controls to the cells in the ACT/generic controller and then ACT learn the parameters to those cells. I demo how to do both in the video in the control surface section.

I don't have one though so there may be some reason it won't work, but theoretically it should. Of course usabilityis a long way short of an MCU but it is better than nothing.

FastBikerBoy


If it has knobs and sliders it should be possible to map the controls for use in Sonar.

It is a two stage process though - MIDI learn the controls to the cells in the ACT/generic controller and then ACT learn the parameters to those cells. I demo how to do both in the video in the control surface section.

I don't have one though so there may be some reason it won't work, but theoretically it should. Of course usabilityis a long way short of an MCU but it is better than nothing.

Karl I know all about it.

Thanks for the info I have gone for the ACT and all works well...
BTW the video is excellent..
Regards
John

jorel


Thanks for the info I have gone for the ACT and all works well...
BTW the video is excellent..
Regards
John

Thanks John - I'm glad you're finding it useful. Thanks again for the support.

jorel

Thanks for the info I have gone for the ACT and all works well...

This is about the M-Audio keyboard and NOT about Quad-Capture, right?
Or did you actually manage to assign Sonar parameters to the four knobs (Output, Mix, and two Sens knobs) on the QC's front panel? (which would be cool but troublesome )