WDI
I really wish cakewalk would fix all issues in a release before moving forward on a new paid for release. It's been my main concern with cakewalk for a long time.

For instance, it was well known that there was issues with the old track lanes that were not resolved release after release after release.

The implementation of mute automation as a separate control and not writable from a control surface is another one. Mute automation should work like any other automatable control in console view. Seems most cohesive and logical.

Then there is the issue of breaking control surface support with every new release. This should have been taken care of before moving to a new release. Cakewalk completely has ignored these issues release after release and I think they are paying for it now. Not the customers.

I realize the company has to make money on a new release. But losing customers is also a way of losing money.

YES! YES! YES!
100%
+1
Absolutely
Without a doubt!!!
 
Mike 

jm24
Even the Microsoft managers understood/understand the need for a user defined button bar, given the stupidity of the ribbon/command bar.  The buttons I PUT ON THE  1-click button bar are my most used bits of office 07, 10, 13. What I need where I want it.  The command ribbon is nearly always hidden. But the w8 windows explorer, folder manager, is way stupid compared to the w7 explorer. Extra clicks for what are the most used functions, i.e., quick display of images and file contents. Another example of idjits designing an application they do not use. (XL is another) Sonar WAS known for its configurability. It WAS a MAJOR feature and selling point.  Who were the sick bastards that decided to get rid of colors, user menus and 1-click button bars?????????????? And who were the way dumb sycophants that allowed them to do so????? Off with their heads!!!!

I'm glad to hear from another who sees things somewhat as I do...

I frequently wonder who is making these decisions and try to imagine what work they do with it and how... Obviously way different than myself or the majority of musician engineers I know...

Sonar's personalization abilities thru 8.5.3 were one of Soar's most endearing qualities... Now lost to the whims of who/why...

I'm still hoping they will return these ideas once they get over the new GUI and touch needs...


Keni

That's something I've always wondered as well. Who is the best person or group to come up with color schemes to replace custom schemes? And who decides what can be altered vs. not? Microsoft, Apple, Ubuntu, and then all of the DAW makers tend to make decisions based on a very limited scope. I don't want to say Skylight is ugly, but yes, there are some things I'd like to customize for easier viewing. The thing is, I wasn't consulted on this. Are Beta testers asked for this? I wasn't picked to become a tester, so I honestly don't know.
 
Anyway, it's like Acura, for example. They made some incredible-looking cars in 2004-2008. I love the shape and form of my Acura TL. In 2009 Honda did something that I strongly believe negatively affected their ability to sell the TL. They made it larger and tons uglier. I absolutely hated that car. So, what if I were in the room when it was being decided to choose that design? I truly wonder how they'd have felt if I said, "It's ugly and isn't going to sell like the Accord". Would they care? Or is it simply a call on what designer pulls so much weight? It's silly to place so much trust in designers for many companies. Great ideas come out of that, but some of the best ideas aren't conjured by professionals. In fact, those go unnoticed because the idea was brought up by someone with no clout in that industry. Life as we know it. 
 

Who? Marketing!

SteveStrummerUK
 
Here's a question for those of you hovering between jumping ship or sticking with Cakewalk.
 
If all your Pro-Channel modules had also been made available as standard VST plug-ins (like the CA-2A now is) so you could use them in any host program, would that make your decision to defect easier?
 

If I felt than that the Pro-Channel modules were indispensable, then perhaps. But alas, they were not. I've gone ahead and ordered Cubase 7. The grass may not be greener, but a different shade of brown can also inspire.
 
KEv

This is my  last Monday to check website for X2b update. But unfortunately...  today I'm going to order Cubase 7 too.  I need a stable Daw to live, i'm sorry...

Cubase 7 is amazing. Absolutely amazing. The plugins alone are worth it.
Cakewalk have a lot of catching up to do!!

burkek

SteveStrummerUK
 
Here's a question for those of you hovering between jumping ship or sticking with Cakewalk.
 
If all your Pro-Channel modules had also been made available as standard VST plug-ins (like the CA-2A now is) so you could use them in any host program, would that make your decision to defect easier?
 

If I felt than that the Pro-Channel modules were indispensable, then perhaps. But alas, they were not. I've gone ahead and ordered Cubase 7. The grass may not be greener, but a different shade of brown can also inspire.
 
KEv

Most of the ProChannel stuff is to lock you into the Cakewalk eco system. You cant use it outside of Sonar in the majority of cases. That's part of the reason I wont touch ProChannels with a bargepole.

brconflict
That's something I've always wondered as well. Who is the best person or group to come up with color schemes to replace custom schemes? And who decides what can be altered vs. not? Microsoft, Apple, Ubuntu, and then all of the DAW makers tend to make decisions based on a very limited scope. I don't want to say Skylight is ugly, but yes, there are some things I'd like to customize for easier viewing. The thing is, I wasn't consulted on this. Are Beta testers asked for this? I wasn't picked to become a tester, so I honestly don't know.
 
Anyway, it's like Acura, for example. They made some incredible-looking cars in 2004-2008. I love the shape and form of my Acura TL. In 2009 Honda did something that I strongly believe negatively affected their ability to sell the TL. They made it larger and tons uglier. I absolutely hated that car. So, what if I were in the room when it was being decided to choose that design? I truly wonder how they'd have felt if I said, "It's ugly and isn't going to sell like the Accord". Would they care? Or is it simply a call on what designer pulls so much weight? It's silly to place so much trust in designers for many companies. Great ideas come out of that, but some of the best ideas aren't conjured by professionals. In fact, those go unnoticed because the idea was brought up by someone with no clout in that industry. Life as we know it. 
 

The design brief for the X series feels like its been aimed at the hobbyist market more than the pro one. The huge icons, the low number of tracks visible, being touch friendly, the large toolbar, low level of UI customisation. Feels like Roland is doing to Sonar what Apple did with Logic i.e. bought for the tech and the clever people. Before we know it X2 will have been out for 1 year and we've had 1 update. It is an absolute disgrace. Cubase 7 on exactly the same rig is absolutely bomb proof - 5 updates in a shorter period of time. I've gone through the bug raising and wasted a lot of time in the process only to be told that the product works as expected, isn't a bug or check my hardware. Futile and a waste of time. It was actually the final straw as I couldn't see any light at the end of the tunnel.
 
At least with Honda - the wheels don't fall off! They still get the basics right even if the design if a bit f. ugly.

brconflict
Anyway, it's like Acura, for example. They made some incredible-looking cars in 2004-2008.

I liked the RSX.  Affordable, attractive and great little car with an awesome interior. They dumped production after 2005, I believe. Dumb.
 
Well, my Sonar X2aP seems to be getting better. I had one WSOD crash the other day while turning on console emulators down the line while audio was playing. Sorry, but my bad habits don't allow me to not audition constantly while making changes. I increased my buffer size in an attempt to cure the crash. More testing to follow. If not getting better, then I will be buying a Firewire card and going forward with that.
 
I will retract my statement about jumping ship with Sonar. I am vested, and I want to see it get better. I know the system, and I know how to use it...mostly. ProChannel modules are a convenient plus and something definitely unique to Sonar. I like the convenience, I suppose. On the other hand, there are some great non-ProChannel plugins out there. So is it really necessary to have the ProChannel strip in the first place?  At the end of the day, what difference does it make whether the plugin is a ProChannel or in the FX Bin? Overall, I like using ProChannels, which is why I upgraded to Producer in the first place. As long as Cakewalk programs QUALITY in the ProChannel modules, then I will usually try to use them over other, similar plugins (compressors, saturation, and EQ definitely).
 
However, I don't agree with paying MORE for any updates. Come on now...