That's it! I hereby declare all our Sonar whoas are due to the local power grids. DIRTY POWER is the culprit! Your level of dirt may vary from mine.
 
Most of us experience a variety of Sonar glitches un-reproduceable by users in different regional locations.That's because each area has it's own power generation, right? They all use different methods to make that power. ie: oil, coal, water, wind, nuclear waste  (my favorite), and so on. Then there's the wires, transmission lines, relay stations, etc. all made, installed, and maintained by different companies with different philosophies and agendas.
 
We're not all on the same grid which means we're not all on the same page when it comes to software bugs. 
 
Sure you can blame things like different system configurations, corrupted installations, out of date drivers, bad clusters, unevenly parsed memory modules, and good ol' user error, but the bottom line is you get out of something what you put into it. Where does it all start? In this case... dirty power!
 
Case closed! 'Nuff said! End of story! My work here is done!
 
Curious how many of us are using power conditioners or regulators on our systems? I'm not.
 
 

I'm not

I blame it all on global warming. Al Gore told me so.

soens


Curious how many of us are using power conditioners or regulators on our systems? I'm not.
 
 

I would NEVER run any critical computer-based system without an uninterruptible power supply. I got into the habit during ADAT days, when people would talk about all these weird things that would happen with their ADATs...and I was one of them. Anyway, I lived in an area that often had lightning storms and such, so I got myself an uninterruptible power supply. Like magic, immediately thereafter my ADATs started behaving perfectly...so I took that as a hint.

Still waiting for the meters to be fixed & track lanes for me are just well.. I won't go into it.
I use a 600w backup & PL-PLUS DMC Power conditioner on my small setup & it's proved to be invaluable over the years.

Fanboys such as myself don't experience bugs. Bugs are impossible :-) 

soens

That's it! I hereby declare all our Sonar whoas are due to the local power grids. DIRTY POWER is the culprit! Your level of dirt may vary from mine.
 
Most of us experience a variety of Sonar glitches un-reproduceable by users in different regional locations.That's because each area has it's own power generation, right? They all use different methods to make that power. ie: oil, coal, water, wind, nuclear waste  (my favorite), and so on. Then there's the wires, transmission lines, relay stations, etc. all made, installed, and maintained by different companies with different philosophies and agendas.
 
We're not all on the same grid which means we're not all on the same page when it comes to software bugs. 
 
Sure you can blame things like different system configurations, corrupted installations, out of date drivers, bad clusters, unevenly parsed memory modules, and good ol' user error, but the bottom line is you get out of something what you put into it. Where does it all start? In this case... dirty power!
 
Case closed! 'Nuff said! End of story! My work here is done!
 
Curious how many of us are using power conditioners or regulators on our systems? I'm not.
 
 

I use an online uninterruptible power supply, one that uses both a rectifier and an inverter. In the USA utilities commonly deviate from 120 volts by up to 15%. Larger deviations occur during load switching and ground faults. Then there is reactive power and the effect it can have on critical electronics. imho an online UPS is an absolute necessity for a stable DAW.

Why does Audiosnap continue to operate even after all such attempts have been disabled? I try AS, give up and undo all the work... when I next open the song, I get the AS messages regarding "Processing Audio"...

 
I get that too Keni and I hate it. Your best bet is...if you haven't done anything in AS that's worth saving, or you're unsuccessful using it, close out without a save. I find the only time I get this message is when I save something after initiating AS.
 
In response to the OP, wow...that's a lot of bothersome stuff there. I don't get any of that. I got a few crashes before the quick-fix, but I've not had any issues since then. You should definitely work up some bug reports if you haven't already. Even if by chance you are the only one seeing some of this stuff, it would be worth investigating and looking into. Are there crash files or .dmp files that are created after a crash? That stuff may be helpful.
 
Another thing I think is important which I'll be doing in the event I see any weird anomalies with X2....video shots.
 
If any of us experience crashing in the same manner time and time again, if it's not too much trouble, running a cam capture program would be great for stuff like this. I know it can be drive intensive, but sometimes when we have issues with this stuff, there aren't enough clues. I figure, I can always edit my video's to get to the point in which the crash happened and just zip them up and send to support. If it's something that happens all the time, it shouldn't take much video time to get to it, ya know?
 
Since we all have so many different systems and configurations, I think we do the product justice by taking part in these things that happen to us instead of being one of those guys that just rants (not saying you Rasure or anyone in this thread, just speaking in general) about them and then goes off to use another DAW with even more problems. At least that's how I'm going about it these days. It's actually helped me quite a few times when support has contacted me after a bug report and I can say "yeah, here's what I see and how it happens." I figure it can't hurt anything and I want to see Sonar rock solid...so that's what I do. :)
 
-Danny

I do use a UPS with surge and power filtering. So i cant blame the power.
Mind you we do get lots birds sitting on the overhead power lines outside our house!
I think i will get an air rifle to shoot them off, and see if the computer glitches go away!

It's my understanding, though I might be wrong (again!) that Audiosnap will always be active until you do a Bounce to Clip - this removes it