chris.r

msmcleod
For anything else you can either use ACT, or Alexi's AZ Controller which will work with anything.

I didn't intend to get into particular issues, the need to use additional software like the excellent AZ Controller to unlock ProChannel features in hardware controller is just an overall example what I mean. Not very intuitive for newbies and newcomers.

You don't need the AZ Controller to use the ProChannel features, just Alexi's enhanced version of the standard MackieControl. I've actually further enhanced this myself to get the "Select" button working to my satisfaction on the Korg NanoKontrol studio (Korg actually admit it doesn't work properly - it kinda does, but not as I wanted it to).
 
I'd have hoped the bakers would have taken both Alexi's and my changes and merged them into the main Cakewalk code. This after all, was the point of releasing the ACT framework under the MIT license - i.e. any changes are shared with Cakewalk.
 
@Noel - is this likely to happen at some point?  If nothing else, it would save us from having to replace the MackieControl.dll every time we upgrade, and all of the changes have optional checkboxes so it doesn't change the default behaviour.

I would agree that having plug and play with controllers is a nice to have.

Realistically the majority do not own these things, so I'm not convinced that is a top priority.

If anything just add a preset configuration for a single device at different price point tiers. That way you can say there is some current out of box controller configuration. It is then up to the consumer to buy one of those specific ones or not.

If an audio interface is compatible with your computer Cakewalk is going to be able to use it.

Thanks will review it!