FreeFlyBertl


It may (or may not, we'll never know) have been a strategic decision at Cakewalk to put their focus on the toy side (e.g. touch, iPad remote, etc) to target mass market / home user / annual upgraders and keep upgrade fees flowing. If so, they'll eventually run off pro users, which are after stability, usability and workflow. You just cannot satisfy users at opposite end of the spectrum.

Playing devils advocate here. I would think the interest in making a touch screen daw, software control surface and what not would be a way for Cakewalk to save money.  If they can invest money into creating some kind of a touch screen software control surface that can replace a hardware control surface, they would save a TON of money.  Having said that, I'm sure the power users will revolt at the idea of loosing their hardware.

*EDIT*
Something like this.... 

http://www.humatic.de/htools/touchdaw/

Obviously, predicting the future is a fool's errand, but I'll have a tentative bet on touch screen not being a big deal for Sonar for quite some time yet. The Windows tablets are not flying off the shelves, for one thing.

Hey John... I think in time they will. Touch is really taking hold, rather it be android or apple devices. If the Windows code base market does not want to become extent, they will eventually need to cave in and start making their apps touch enabled.   Do I like it?  I'm not sure yet. I like the hybrid idea myself. Touch enabled, but still use keyboard and mouse.

We'll see. I may well be proven wrong. I think touch makes sense for some use cases and not others. I think in music production, that use case will turn out to be for some types of writing and performance activity. For full on mixing, I'm very skeptical. I mean, that Slate touch console is kind of "wow", but once you get past that first impression, it seems like a solution looking for a problem to me.

All bug issues that CW acknowledged in X2a are being looked at for completion. I don't believe CW acknowledge a bug then forgets about it. Sonar X programs usually have a,b,c,d, upgrades. X2 is only at a, therefore there may be 3 additional b,c,d, updates to follow. If CW can't reproduce the bug don't expect them to fix it. If CW acknowledged the bug, it may be fixed in an upcoming update. Standard procedure. I believe every bug issue in the VS700 they can identify will be fixed before the final X2 maintenance release is issued.

kday


All bug issues that CW acknowledged in X2a are being looked at for completion. I don't believe CW acknowledge a bug then forgets about it. Sonar X programs usually have a,b,c,d, upgrades. X2 is only at a, therefore there may be 3 additional b,c,d, updates to follow. If CW can't reproduce the bug don't expect them to fix it. If CW acknowledged the bug, it may be fixed in an upcoming update. Standard procedure. I believe every bug issue in the VS700 they can identify will be fixed before the final X2 maintenance release is issued.

based on ... pure speculation? insider knowledge? or female intuition?

Do your homework, check the track record and draw your own conclusions, and then wait for the final outcome? We're only at first base, X2a. Wait until the X2 update game is over before calling the game.

homework has been done over and over, it's cakewalk not doing theirs. X1 a,b,c and d did not bring the VS700 to proper use aside from the pushing of faders and other basic stuff. And maybe the way they've dealt with the VS system since is why this VS forum is so full of what we see around here. You can't blame ppl for being upset after the amount of money they've put it out for this and you can expect ppl to just be quiet and go away about it either.

Actually, in fairness, I think v700 support *finally* got good in X1d. Which is why it's such a tooth grinder that it sucked again in X2. Basically, both X series releases have launched with awful v700 support, and fixing it has been late running in both cases. These are facts.

CW has timetables to releasing updates. But that's the way fixing bugs and beta testing works. Fixing bugs always increases the chance of breaking something else. They have only so much personnel and time to re-test every single parameter in a thousands. It's gonna happen, we the user has to also help and identify what's newly broken and just report it so they can try to fix it before X2d. That's the best the company can do. I used to be a beta tester so i know how that aspect works. I don't blame folks for being mad that CW couldn't fix and test every single bug in a thousand before releasing X1. That was impossible for them, even tho i don't like it, I know it takes a great deal of time and resources to fix every single bug in V700 system within months, that's impossible. CW have to release the next generation upgrade to Sonar on a timely basis, that can't be delayed. Fixing bugs for the VS700 can be, and was delayed unfortunately for us. I see them fixing all the bugs (they can identify) on a timely basis now that X2 is released and being maintenance'd. I don't think CW have given up on V700 just yet. I think they are just doing what they can in a scheduled timely manner. It's not as fast as we think it should be but, I see they are trying to continued maintenance releases every so often. My final verdict will come when X2d is released and not b4 even tho I understand many people believe they have the resources to fix hundreds of bugs overnight while working on a new platform that upgrades the program overall also. I feel you guys pain though, but I feel much better seeing CW bug fixes quarterly.