I am not quite sure the point of the OP, but I try to read most of the SONAR forum for the past year or so (about 3 months before X3 was released). Most issues have boiled down to pilot error, drivers, plugin-specific, or system-specific issues, many of which were subsequently resolved. Lump summing this into a comment of "SONAR blows up regularly" is a bit out there.

gswitz
oh whatever.

 +1 that was smooth 
 
Kenny

I hate Sonar, it's complicated, you have to know all kinds of stuff about your windows box to get it to work reasonably well.
 
 
 It's like that with all DAW, Video and Gaming software.  It's no different for Mac users.  A more proprietary environment is more stable buy less free.
 
Yeah, I've got some bug reports that only I can reproduce (missing patch 54) and maybe it's a problem with my graphics card but no one else is missing patch 54 (Pro Tools, Live, Reason, etc).
 
  This must be unique that it may be only happening to you and I can understand your rant. I never heard of this error.
 
Unfortunately the stuff that comes with it hasn't been updated in a long time (None of the signature synths have been updated in years). The only new stuff is from 3rdParty vendors.
 
You have a point there.
 
Finally at last glance, who are the artists endorsing and using Sonar? With the exception of Craig who I've been following since the 80's, who are these guys? When was the last time they charted?
 
Most people who listen to music really don't care.  I've never needed to know an artist endorsement to feel better about an app I use.  All commercial releases are ran through Pro Tools before they reach the listener. Those doing the mastering are not the artists.
 
 
 
 

mettelus
I am not quite sure the point of the OP, but I try to read most of the SONAR forum for the past year or so (about 3 months before X3 was released). Most issues have boiled down to pilot error, drivers, plugin-specific, or system-specific issues, many of which were subsequently resolved. Lump summing this into a comment of "SONAR blows up regularly" is a bit out there.

Yes, which underscores my point about Windows. 200 bpm, I think I have sufficient background to justify my claim that "running on Windows machines is more problematic." I wrote the manual for Ableton Live 2.0, have consulted to Avid as well as to Magix (who make Samplitude), and you can see my applications videos about Mixcraft and mastering with Studio One Pro on their respective sites. I have an excellent relationship with Steinberg, which licenses my Quadrafuzz multiband distortion (and just updated it for Cubase 8). It's not my fault if Samplitude users, as well as SONAR users, sometimes find running on Windows problematic. In fact when I had problems with Samplitude and CD burning many years ago, the program's developers came to my house because they wanted to analyze the problem as it was an important part of the program and they were among the first to build CD burning into a DAW. They gave up and could not find the reason. Obviously the function works fine now, but there is no doubt it was a Windows issue that was beyond the scope of their software to accommodate.
 
If you disagree with my assessment about Windows, that's fine but then I don't share your opinion.
 
I use both Mac and Windows, and have definite opinions about which platform is initially "friendlier" for music. That said, Windows machines are more cost-effective, more customizable, and easier to repair/replace when on deadline. Many people also consider them more powerful. However, with that power comes a price, which is converting a machine that was never really designed with music in mind to be suitable for high-performance music and media applications.

Macs don't have touch.

mettelus
I am not quite sure the point of the OP, but I try to read most of the SONAR forum for the past year or so (about 3 months before X3 was released). Most issues have boiled down to pilot error, drivers, plugin-specific, or system-specific issues, many of which were subsequently resolved. Lump summing this into a comment of "SONAR blows up regularly" is a bit out there.

 You should visit other DAW forums. I see these type of posts in Live, Sony and Image Line.  There are some here whose first response is to defend Sonar instead of asking an OP "how can we fix it for you?" despite their negative comments.
 Crashes are often not pilot error unless you open two separate apps that use the same driver or bad resource management in a project.  There are plugin developers that cater more to specific DAWs. (see Waves)
 People get really frustrated when their DAW is not working. They make irrational comments and valuable posters settle them down.  You should see me go off when a developer loses my account or licenses.
 
   

all my previous kidding aside ,
I do understand the OP's frustration in a few areas …
I spent almost a whole year fed up with Windows and X3 due to the fact that I didn't really have a great windows machine to begin with …it took a lot of help from the people here on the forum to help me get it configured to where it was usable enough to at least keep me in the running ….
once some of the long standing configuration issues were solved , I was able to gell w X3 enough to appreciate how deep the program (X3 ) is compared to everything else that is currently out there (on both platforms PC and Mac )
most of the other programs that people love to compare to SONAR I do have w the exception of Abelton …..
sure maybe some of the Cakewalk plugs and instruments may have been around for a while .
The fact is they show up in all my other DAW's and are usable ….even some of the bundled 3 rd party stuff shows up across multiple DAW's ….Melodyne, Addictive Drums ……
that is not something I can say about any of the plugs and instruments I have from Samplitude 
I'm also able to run both PC and Mac DAW's since that's what I have …..been running what people consider to be the main competition from the other OS…..
I'm certainly not looking to take sides or argue w anybody 
the thing is Craig has been shooting straight from the hip on the differences between configuring the audio on both OS's …
one OS is a pain in the a$$ to configure the audio on …the other isn't …..I would not be using Windows if it wasn't for SONAR 
 
 
Kenny
 
 
 

 

mettelus
I am not quite sure the point of the OP, but I try to read most of the SONAR forum for the past year or so (about 3 months before X3 was released). Most issues have boiled down to pilot error, drivers, plugin-specific, or system-specific issues, many of which were subsequently resolved. Lump summing this into a comment of "SONAR blows up regularly" is a bit out there.

 

kitekrazy1
 You should visit other DAW forums. I see these type of posts in Live, Sony and Image Line.  There are some here whose first response is to defend Sonar instead of asking an OP "how can we fix it for you?" despite their negative comments.

 
I haven't seen much of that to be honest, if there are any recent examples let me know. The reality is if the issue isn't reproducible by another member of the community it probably isn't a Sonar issue. When I hear about machines freezing up it's almost always drivers or hardware. When it's transport screwing up it's almost certainly drivers or plugins.
 

kitekrazy1
Crashes are often not pilot error unless you open two separate apps that use the same driver or bad resource management in a project.  There are plugin developers that cater more to specific DAWs. (see Waves)

 
The only crashes I've seen in these forums recently are related plugins/drivers/firmware/hardware related. I've documented perhaps three ways to reproduce a Sonar crash since X3E and that's it. That's why when somebody points fingers at Sonar the first thing I look at are the external factors (I don't care who's to blame btw, I care about resolving the OP's issue as most do). If a bug is found within Sonar I regard it as a win because an identifiable bug means it can be fixed. Where it gets tricky is when the OP explains their issue in little detail (rather they just explain the symptoms), and then self diagnose Sonar at fault without any evidence to back it up, or any member of the community able to reproduce.
 

kitekrazy1
People get really frustrated when their DAW is not working. They make irrational comments and valuable posters settle them down.  You should see me go off when a developer loses my account or licenses. 

Yup but most often their DAW is working fine, it's what's hooking into it that's causing the indigestion.
 
Ta

kitekrazy1
I hate Sonar, it's complicated, you have to know all kinds of stuff about your windows box to get it to work reasonably well.
 
 
 It's like that with all DAW, Video and Gaming software.  It's no different for Mac users.  A more proprietary environment is more stable buy less free.

This might seem controversial as everybody thinks Macs are just perfect but I've had more crashes with Pro Tools than Sonar, and yes same old chestnut was at fault... plugins... drivers... etc etc. So not Pro Tools fault.
 
Bottomline is all software is buggy, and both PC and Mac run on Intel. Mac's are PC's.

 "Hey, I turned on SONAR, and it's working. I'm doing some recording."
 
Actually, ..... that would be 100% true today! ......well, except trying to figure out some things about MIDI, but I digress ....... 
 
I've had and continue to have my issues when using Sonar (and every other program I own). But I would also add that about 99% of the time, the problem is NOT the software. The problem most always turns out to be ME! Sometimes it's my hardware, but mostly it's my misunderstanding, my lack of knowledge or just plain brain farts!
 
Just sayin'