SilkTone
Andrew Rossa [Cakewalk]
Instead of trying to find ways to crash the program, why don't you just use it to create music and have fun. If you run into a problem, send us a bug report. SONAR X3 has been very stable. Of course it's possible to crash any program but why don't you focus on just creating music?
We are working on a new patch, SONAR X3d, that will have lots of fixes and enhancements to an already stable program. You asked us to focus on stability, and we responded. I don't understand the purpose of this thread at all.
I think the OP's point is that he is trying to "just use it to make music and have fun". However for him Sonar crashes randomly for no apparent reason, and he is trying to understand what all the known causes for Sonar crashing are. Once he knows that he can try to determine if any of those apply in his case, and then use the known work-arounds so that he can get to the point where can "just use it to make music and have fun".
I think it is a valid question to ask. The title can be a bit misleading but if you read the 1st post it makes sense.
Guys, please calm down!
I just returned from long hours working with Sonar having no issues - and was quite shocked which turn this thread took so quickly. I did not want to get any mud throwing started, I was just asking for potentially unsafe operations.
I admit the thread's title is provocative - with the intention to get some attention and people posting, yet I was trying to get technical feedback on things I have to be careful with.
To set things straight: Sonar X3c works quite well for me, but not 100%. Still I'm far from
having random crashes. I can work for days/weeks without any issue and then I do something I don't regularly do, and the thing crashes and loses me a couple of hours trying to figure out why it does that. Lately all those mysterious issues revolve around using bits from previous projects and freezing synths. I understand that this doesn't happen on everybody's DAW since my templates, plugs, and combinations thereof are different to anyone else's.
When reporting issues via the problem reporter I receive mostly silence for weeks (e.g. CWBRN-21497). Sorry, I can't get on the phone and talk for hours to support. The phone bill would surmount to something higher than I'd pay for a different DAW software (hey, that was irony in case it doesn't get noticed
).
When coming here to ask, I mostly get replies to fix my system. Hey, these suggestions were all good and valid and I did check on them, yet there are situations where it's not the system that's faulty (just look at the long list of crash fixes with recent patches). So here I was merely hoping that someone chimes in saying something like "yeah, I use that Kontakt thingy and when having that patch XY and that routing I get dubious behaviour, so better try this instead ..." Wishful thinking, probably ...
For the record: I crash Microsoft applications regularly (no worries, it's not the DAW computer
), but I don't expect anybody at Microsoft to care about. I know I get these crashes because I go beyond average Joe functionality, but it's also functionality that used to work perfectly in previous versions and got broken when they put all these fancy colours and joyful looking buttons in ...
Issues I have with X3c fall into a similar category: it relates to functionality I used before troublefree in X2a/X1d and I'm sort of expecting them to work OK again with X3d or X3e - whatever the last free update will be.
All that said, I think Sonar is a great product and incredible value for its price. I honestly believe - and I know I'll be hit for that now - it's sold way too cheap. Personally, I'd pay a multiple of the upgrade fee if I could go straight to a release in a shape like X1d or what X3e will be. It would save us a lot of time and useless discussions ...
OK, I better get lost before I pour too much gasoline into already way too high flames of this thread.
Rob