Regarding the thought that a control will never "fully" replace the DAW screen controls.
Yeah, that's probably true.
However, for the transport functions (stop, play, record), it's really nice to do it while at my drums, wearing my guitar, or with one hand on the piano, and NOT have to reach for the mouse and look at the screen before recording.
 
For faders, again, the control fader is easier to manipulate than the screen with a mouse.
 
However, when you start talking plugins, softsynths, etc.
Now you just want to do it with the mouse, imo.
Setting up the control surface is just too involved at that point.
And with so many different apps and layouts for third party stuff, it's too hard to recall what each knob/fader will do anyhow.  Until you start moving it, and screw up your current parameters.

chuckebaby
... I haven't always been keen on Behringers stuff but they are improving / using better parts/better engineering...

I also was concerned about Behringer's reputation for lack of quality/reliability, but after reading positive reviews about them, I purchased the X-Touch and after using it for a couple months, I'm very pleased with my purchase.
 
Wish they would come out with an 8 fader add-on. For now you have to series connect 2 or more X-Touch's, if you want more fader control w/o having to switch banks. Makes for a wide desk.
 
Walt
 

hector945
However, when you start talking plugins, softsynths, etc.
Now you just want to do it with the mouse, imo.
Setting up the control surface is just too involved at that point.
And with so many different apps and layouts for third party stuff, it's too hard to recall what each knob/fader will do anyhow.  Until you start moving it, and screw up your current parameters.

 
That's the problem with hardware controllers...way too many things they can't control!

chuckebaby
 
touch has its draw backs, for example, to be super accurate, you need gestures/ click +enter.

 
There is no need to be "super accurate" - normal interaction is perfectly fine. I'm using mine with Studio One's native support and it's great in every sense. I don't even understand the part about "gesture / click + enter" - I don't have to do any of that. My hands replaces the mouse cursor, to put it in the simplest terms.
 
Maybe different DAWs behave differently or offer different levels of native support for touchscreen monitors?
 

chuckebaby
with a hardware fader in your hand you can dial in much faster.

 
That's true of faders, but there is a whole lot more than moving faders. Working with plugins, vst intruments, editing, etc., etc., is something a hardware controller is very poor at.
 

chuckebaby
im not even going in to transport controls either.

 
Transport controls are perfectly fine with a touchscreen. Have you experienced any problems?
 
 

hector945
Thanks guys.
Yeah, most of those options are not "inexpensive" for a new home studio.
For now, I'm going to give up on the 16 fader option, and go with the typical 8.
I ordered this:
http://www.korg.com/us/products/controllers/nanokontrol_studio/
 
It's wireless too.  So, I can start my DAW record button from my drumset.
Rather that walk there from my PC and have to use a bunch of count-in measures before recording.
And, when I "screw up" my drum tracks, I can restart w/o having to leave my drum stool :)

I quite like the look of this as an inexpensive option, I wonder how well it works with Sonar? My new NI S61 keyboard has given me unprecidented control over my virtual instruments and Kontakt libraries but beyong transport controls its not so good as a control surface.

BCF 2000s  are NOT real touch sensitive faders and do not correctly write automation data... unless something has changed.  I had one and the automation curves for fader moves continuously snapped back to 0.0 when not moving so if you raise or lowered the fader and then stopped movement the written automation would snap back to zero whether you let go or kept your finger on it.  VERY annoying and at the time I had one, there was no workable solution.  Mackie control works well but you can't use them for all the Sonar functionality, only transport, shuttle, pan and MSR.   Bottomline is that there is NO control surface that SONAR supports where you get your moneys worth unless you get real real cheap on ebay.  It is a real downside for Sonar..  One of the 2....  That and no apple support.

stxx
BCF 2000s  are NOT real touch sensitive faders and do not correctly write automation data... unless something has changed.  I had one and the automation curves for fader moves continuously snapped back to 0.0 when not moving so if you raise or lowered the fader and then stopped movement the written automation would snap back to zero whether you let go or kept your finger on it.  VERY annoying and at the time I had one, there was no workable solution.

Latch mode for automation writing?
 

 Mackie control works well but you can't use them for all the Sonar functionality, only transport, shuttle, pan and MSR.

And everything else, except soft synth parameters and some ProChannel modules (EQ/Comp works)
 

Bottomline is that there is NO control surface that SONAR supports where you get your moneys worth unless you get real real cheap on ebay.

Any surface can work with Sonar, from gamepads up to digital mixers...
 

It is a real downside for Sonar..  One of the 2....  That and no apple support.

I do not see that as a downside

I have a couple of devices that provide faders/knobs/buttons in addition the primary purpose they were purchased for.  I really like having the physical faders, BUT I don't use them because they aren't motorized.  Having to recapture/reset the level(s) at every bank switch is a major PITA to me.
 
 

If Sonar supported apple, it would likely be morhiughly recognized and supported by companies that do make control surfaces such at Slate Raven.    SONAR has a VERY small user base next to the others  bigger ones (and deserves much larger base) and one of the reasons is lack of support by Apple IOS.  This has been written numerous times. Control surface:  Nothing worked for me with BCF2000 and I searched and searched.   Does anyone have a BCF200 that properly writes automation?   Not questioning or doubting, just asking.   Prochannel doesn't work and that is a HUGE deficite of function.  Plugins don;t work well either.   It is common knowledge SONAR does not support Mackie in the "normal" standard way

BobF
I have a couple of devices that provide faders/knobs/buttons in addition the primary purpose they were purchased for.  I really like having the physical faders, BUT I don't use them because they aren't motorized.  Having to recapture/reset the level(s) at every bank switch is a major PITA to me.

That is why I have introduced "instant" with non linear response curves and "endless imitation" modes. If I want change something, initial coarse response it not a problem (it converges with time). I just do not want it "jumps" and I do not want "catch" the position. For the "final touch" MIDI resolution is in most cases not sufficient (think of EQ parameters), so I switch to the "fine" mode.
 
And so using curved instant combined with endless fine (by shift key) method, I can use my MPK mini with the feeling it has endless encoders with good (for the case) resolution. Sure, there are times when that does not work perfect, for example when the knob is all the way left while the parameter is all the way right. But in practice that does not happened too often.
 

stxx
If Sonar supported apple, it would likely be morhiughly recognized and supported by companies that do make control surfaces such at Slate Raven.    SONAR has a VERY small user base

Sure, support from Slate Raven will instantly explode the number of Sonar users
Roland has tried that... and after counting (I guess by fingers, may be on abacus) the number of attracted customers, near instantly has stopped the production and has sold Cakewalk a bit later... 
 
Nektar has thought the problem is the price. So they have made a cheap keyboard with Sonar support. Counted customers, no Sonar support in upper models...
 

 ...and one of the reasons is lack of support by Apple IOS.  This has been written numerous times. Control surface:  Nothing worked for me with BCF2000 and I searched and searched.   Does anyone have a BCF200 that properly writes automation?   Not questioning or doubting, just asking.

As with StudioMix, supposed automation mode for not touch sensitive controls is "Latch". For touch sensitive it is "Touch" (a kind of logical).
 

  Prochannel doesn't work and that is a HUGE deficite of function.  Plugins don;t work well either.   It is common knowledge SONAR does not support Mackie in the "normal" standard way

There are several methods to control ProChannel and plug-ins. There is no "normal" way for Mackie, that is a myth... Do you know that from computer perspective there is NO difference between let say MIDI Keyboard and MCU? They both just send "Keys" (all buttons on MCU), "Pitch bend" (faders of MCU) and "Control changes" (Mod wheel on keyboard, encoders on MCU). So, what is "standard" then? Should Sonar play a melody when you press transport keys?
 
You are right in part that Cakewalk was not updating Mackie support for quite long time. But I guess the reason is still the same, that is not worse the effort.
 
You can ask why I think I can judge in that area. That is easy to explain. I have created Sonar controlling platform, which can work with ANY device (gamepads, keyboards, MCU, even HUI and StudioMix which communicate rather weird way). Bidirectionally, with close to any possible in Sonar operations support, unique features (for example, search for other DAW controller solution with feedback as a speach instead of light), completely FREE to use, with FREE remote configuration when required. For those who do not like closed source project, I have declared myself ready to support CW Mackie plug-in (and I have "fixed" it to support ProChannel EQ/Compressors, to show I am able to do that). You can guess what I need to count the number of really interested Sonar users - fingers on one hand...