Jlien X

vintagevibe

jscomposerPardon my ignorance, but what the hell is the big issue???? I'm a professional user, and frankly, it is a total turn off whenever I pop onto this forum. I have gained a lot of good tips here over years, but the complaining is getting to the point where it's just downright ridiculous. Are your systems to the point where Sonar has crippled your workflow? Is your system the issue? What exactly is the elusive "bug" fix that is going to magically fix your issues? And then when the next patch gets released it will be like "my system is not working now, I keep getting crashes, blah, blah, blah". I can honestly say Sonar, all the way from Cake 3.0 to X2a, has always been SOLID. It sucks there are no substantial scoring-to-picture features (which is I why I use alternate DAW's for that work), but that is not a bug, and I'm okay with that. I've also NEVER experienced issues from tech support over the years....tickets always get answered and resolved. What am I missing??

You're missing the fact that others do have real problems that need to be fixed.

I agree. I've seen a number of users who had no problem running other daws but couldn't get Sonar to work, so I'm starting to consider myself just one of the lucky ones. But I have some tickets not answered/resolved. That's a fact.

Sadly, this is true with every software.... sometimes they don't work on a particular system as cleanly or easily as others and only time and communication can bring these issues to a happy ending...
 
I have never yet built a workstation for Sonar that didn't work within reason of expectations.... and I've been using since Cakewalk For Windows 1.0 and building workstations for many people besides myself...
 
thinking about it, I've always managed to get every DAW software installed and working regardless of manufacturer...
 
Funny, but even on a Mac where the hardware variations are far smaller than on a Windows machine, I've found issues with some machines and not others... I can't count how many Mac users I've worked with over the years that had numerous problems running PT or others...
 
Keni
 

vintagevibe

jscomposer
Pardon my ignorance, but what the hell is the big issue???? I'm a professional user, and frankly, it is a total turn off whenever I pop onto this forum. I have gained a lot of good tips here over years, but the complaining is getting to the point where it's just downright ridiculous. Are your systems to the point where Sonar has crippled your workflow? Is your system the issue? What exactly is the elusive "bug" fix that is going to magically fix your issues? And then when the next patch gets released it will be like "my system is not working now, I keep getting crashes, blah, blah, blah". I can honestly say Sonar, all the way from Cake 3.0 to X2a, has always been SOLID. It sucks there are no substantial scoring-to-picture features (which is I why I use alternate DAW's for that work), but that is not a bug, and I'm okay with that. I've also NEVER experienced issues from tech support over the years....tickets always get answered and resolved.
 
What am I missing??

You're missing the fact that others do have real problems that need to be fixed.

But that's the thing.....what are the REAL PROBLEMS? Is there a major bug that is preventing a key programming feature? Perhaps there is, but I have yet to hear about anything like that. Like Keni mentioned, there are issues with every single piece of software out there. There is never going to be a release of Sonar that is absolutely perfect, but that's what will be expected over and over again.
 
As far as tickets not getting responded to or resolved, that is unfortunate, but I personally have never had issues with Cake support for many, many years.

Again, what are some examples of these bugs that inhibit workflow?? Just curious.

vintagevibe
There is not one show stopper but a lot of really annoying bugs that inhibit workflow.  If you don' have them that's great.  But that means you are in a poor position to imply that they aren't there or don't matter.  They are there and they need to be fixed.  The tired line that all software has issues is irrelevant here, especially if you are not one of the ones having problems.

But I think that's part of the problem... Accepting that no DAW is bug-free, then which specific SONAR bugs are the ones that need to be fixed?   I'd imagine CW has numbers related to how any times certain issues are reported, and are hopefully using that information to schedule fixes for future releases.   But I sometimes wonder if the "obvious" bugs often referred to here on the forums are actually not the ones that they've scheduled.    Hmmm...
 

vintagevibe
 
There is not one show stopper but a lot of really annoying bugs that inhibit workflow.  If you don' have them that's great.  But that means you are in a poor position to imply that they aren't there or don't matter.  They are there and they need to be fixed.  The tired line that all software has issues is irrelevant here, especially if you are not one of the ones having problems.

+1. If stability issues continues with X 2b/3 I will surely abandon CW with which I have been making music with since 2004. No more official beta testing for me.

Bob, it crashes now and then maybe one of five times. Very rarely BSOD though thank heavens.
It could be 32 bit plugins (I use JBridge), it could be third party VSTi:s like Kontakt or Trillian.
It should really not matter. These plugs are very common and if not tested with Sonar sufficiently before release of a new version
it's like not taking their costumers seriously. I do know you help a lot of people here and I respect that but plze don't give me that you shouldn't do this or that in order to get the system work. This should have been decently tested before and relaease of a new DAW. 

equality
Bob, it crashes now and then maybe one of five times. Very rarely BSOD though thank heavens.
It could be 32 bit plugins (I use JBridge), it could be third party VSTi:s like Kontakt or Trillian.
It should really not matter. These plugs are very common and if not tested with Sonar sufficiently before release of a new version
it's like not taking their costumers seriously. I do know you help a lot of people here and I respect that but plze don't give me that you shouldn't do this or that in order to get the system work. This should have been decently tested before and relaease of a new DAW. 

I am not going to tell you one way or another what to do or not do.
 
I WILL  indicate that there are indeed issues with some 32-bit plugins running in 64-bit Sonar.  I use some 32-bit plugins, but only myself use ones that I have tested out and found to work well with BitBridge.  (I have considered but not purchased JBridge as of yet).
 
In any of the posts I have seen where Cakewalk technical support has examined dump files and commented back on them, none of those I have seen ended up being the fault of Sonar, rather, those particular errors had been caused by improper coding of those particular 32-bit plugins, although those errors were exposed during use with 64-bit Sonar.
 
The above certainly does not prove that Sonar doesn't have any programming errors in handling 32-bit plugins, but it DOES mean that there are in fact some 32-bit plugins that are not properly following the VST 2 spec, or have coding problems otherwise.
 
I will also state that it is not Sonar's responsibility to handle errors caused by faulty plugins, as control is passed to these plugins and if THEY are in control and fail, then there isn't much Sonar can do about it.  
 
I believe that there have been cases where even though it is not Sonar's responsibility, that they HAVE on occasion put in special code to handle bad coding from some plugins, but I would certainly not expect them to build custom code for the thousands of plugins that are out there and available for inclusion in Sonar.
 
What I did for MY system is to avoid the blanket use of 32-bit plugins in my 64-bit Sonar, and I also specifically test out those 32-bit plugins that I do have interest in seeing if will work in my 64-bit install.  That seems to work for me, though it does limit the choice of plugins I use, if I choose to work with the project in 64-bit Sonar.
 
If the above works for you, and is something you choose to try, I hope that it works for you.
 
If the above is not an option you choose to or otherwise cannot implement, then I do not know of other choices then swapping out for different plugins, or for projects that require those plugins that you work with them in 32-bit Sonar, to avoid bridging issues.
 
In any case, I DO wish you every opportunity for things to work as seamlessly and stable as possible, so that you can make/produce music in an enjoyable and productive manner.
 
Good luck, 
 
Bob Bone
 

robert_e_bone
 
What I did for MY system is to avoid the blanket use of 32-bit plugins in my 64-bit Sonar, and I also specifically test out those 32-bit plugins that I do have interest in seeing if will work in my 64-bit install.  That seems to work for me, though it does limit the choice of plugins I use, if I choose to work with the project in 64-bit Sonar.
 

+2.
 
The converse is true for me in this fashion; I have installed every 64bit plug's 32bit little brother/sister in the event I need to use 32bit SONAR to get over a hump of a badly behaved 32bit plug. Fortunately for me I've yet to have to do this. Unfortunately for me it sometimes means double install of plugs/VSTi updates.
 
Lastly, I no longer acquire any "free" plugs by anybody that does not already have a reputation for quality/stability. So my list of 32bit only plugs is limited to:
 
IKMultimedia (Sampletank, Miroslav, SampleTron, SampleMoog, SonicSynth)
Drumagog
Antares AVOX Evo
IRCAM Flux
HeadCase
Bluenoise Plugings (Metal and Rock Drumkits)
Elevayta's Spaceboy
Empress Tremelo
SoundToys (Radiator & Little Radiator)
Voxengo Boogex
FerricTDS
mda_Leslie
VB3
 
The first four are highly likely to become 64bit before the end 2014 (maybe even before the year is out)
The next two are less likely to become 64bit anytime soon due to their development platform.
The rest may never become 64bit and I only keep these around for project compatibility (one day i'll replace them, but there is no rush as these all work on my system as it stands today).