Mystic38
Fine, no more Sonar development.
Did your copy break?.. nope.
You know I keep hearing this argument, and it is kind of unfair. Did my copy break?
Yes it did. It was always broken. While I am not worried about windows updates like some other folks were (there's ways around that), there are
many serious bugs, and hundreds of other minor issues, some that cause a lot of hard crashes and loss of work and time. I really enjoyed the monthly update program because it led me to believe that others cared about this software and were going to make it better, and I did my part to contribute bug fixes, crash dumps, and feature requests. Now that development has stopped,
it will be broken forever! Now there are plenty of folks who have stable installs, and with a config freeze they could keep using their copy for a very long time. I'm very excited for them, but that strategy doesn't work for me because I am an early adopter. I like new features, and adapt to them right away, usually relishing how certain things get easier, and the new things I can do!
In particular, Cakewalk was embarking on a multi-phase project to introduce non-linear, non-destructive editing to Sonar. Comping improvements, Synth and PRV improvements, multi-track ARA, and region effect comping -- all wonderful things, and all immediately indispensable to my workflow. I love this stuff, it's how I think, it's part of my songwriting process, and things take a lot longer when I don't have access to these tools.
Take Melodyne. It is the source of probably 80%+ of my crashes. And why? Because I don't bounce the region effects, I keep them open
forever. And I have 30+ instances in some projects. And if we had one more Sonar monthly release in our hands, I would probably be splitting, comping, cloning, and shifting active region effects all over the place. Why? Because that's how I write music. I might mess with harmonies and vocal doubles for months, and use one part as a reference behind a newer part, so I never render them. But the advice I get on this forum continually is keep melodyne instances to a minimum, and always render them. But I don't want to do that from a work flow perspective, and also, it is destructive editing. Melodyne introduces a lot of phase error, and other transients, and adding and rendering multiple melodyne edits is like saving a mp3 dozens of times -- stuff gets muddy fast. After all, what's the point of having non-destructive editing capability if you're not going to use it? It's powerful, and unlike some other folks here, I prefer - perhaps need - to use it.
So in the end, I'm stuck with a DAW that's broken. I have many projects to complete in Sonar, and will keep using it. Probably for a very long time. But I need to get faster at my music, and I need my tools to keep up with me, so I am adding another DAW to my arsenal in place of starting new projects in Sonar.
Also, while we're at it, don't discount the really unfair effects of putting people in terrible position to risk losing money by buying or not buying a product at a reduced price on Black Friday - my feeling is that probably half the fever people experienced was due to the timing and the dilemma of choice placed upon them. That doesn't bring out the best in people.