FlushOnStop - Anybody know what this Aud.ini setting does ??

play effect tails after stopping http://forum.cakewalk.com/FindPost/3637515

Wookiee
That AUD.INI setting does not seem appear in SONAR Platinum looking at the S-Plat AUD.INI it seems to have been replaced with AlwaysStreamAudioThroughFx.  At a guess it probably has something to do with clearing the AUDIO buffers.

The option "Play Effect Tails After Stopping" is no longer in S-Plats preferences it has been replaced by Always Stream Audio Through Fx

can confirm

I am quite curious as to why your system is occasionally locking up.  I cannot even dimly recall when the last time Sonar locked up or crashed on me, and if there were some easily stumbled into recipe for that happening, I would think we would see a whole bunch of other similar reports.
 
That makes me think that whatever IS sometimes locking up your Sonar, is something local to your situation.
 
The things that come to mind for that would include:
 
1) Possible failing when using a 3rd party 32-bit plugin in a 64-bit Sonar environment.  To use a 32-bit plugin in a 64-bit Sonar, the plugin must be used with bridging software - Sonar includes a free piece of software called BitBridge to provide that functionality, HOWEVER, not all 32-bit plugins are stable when running bridged with BitBridge.  There is a commercially available program called JBridge, that also provides bridging for 32-bit plugins, and for SOME 32-bit plugins that fail under BitBridge, they end up being able to work using JBridge, HOWEVER, some 32-bit plugins STILL fail no matter which bridging software is used.  Many, if not most, folks have made a deliberate decision to completely move away from using 32-bit plugins in 64-bit Sonar.  Most of the decent plugins also come in a 64-bit flavor - as a free download if one already has the 32-bit version.  I do still use a small number of 32-bit plugins, but I have those split off into their own folder with only that 32-bit folder added to the 64-bit Sonar plugin search path.  Those plugins were thoroughly tested by me, to make sure they were working, before I added them  to be able to be used in my 64-bit Sonar projects.
 
2) Possible failure with some 3rd-party 64-bit plugin.  There HAVE been some 64-bit plugins that don't always play nice in Sonar.  Try to see if any plugin shows up in any Windows Event Viewer messages at the time of failure, and see if you can spot any consistent presence of any particular plugins across multiple failing projects.
 
3) Make sure Windows and your plugins are all at current maintenance levels.
 
There are undoubtedly additional things others can think of suggesting you look at, but I DO think with some digging, and possible assistance from forum folks, that you might be able to get your environment stabilized.
 
Bob Bone

BTW, lock up never happens during playing or recording, ever.  Usually after stopping the transport, or more typically when hitting rewind while the transport is currently playing (instead of hitting stop first).  Often the lockup is not immediately apparent because many times i don't realize until I click on something and then Sonar locks up - but it wasn't what I clicked on that caused it, rather Sonar had already locked up when the transport last stopped - but isn't apparent until you later click on something and Sonar no longer responds.   Many times the green PLAY button on the toolbar is still lit, as if Sonar was unable to complete the STOP sequence and got locked up.
 
Sonic

I had a similar issue with an older XP install. It would lock up randomly when using a pretty Ram intensive VST instrument. It would not crash.... but lock up for maybe up to 30 seconds. Something about the way the memory was allocated could be a problem. Maybe check to see if  your disk cache the same as your w2K install?

I'm going to let the machine sit next time for an hour and see if it ever recovers.  Haven't tried that yet.
 
What about Windows DEP?  Should I turn that on for all processes and see if maybe it catches something?  Kind of nervous about enabling that, never messed with it before, no idea what side effects it may introduce.
 
Also, what about the "Arm For Recording" feature in Sonar (or whatever it is called)?  I don't see anywhere in S5 it can be configured, but I was thinking maybe when a track starts or stops playing a lockup could be related to that feature creating/deleting the file that is associated with the feature (allowing the enabling of recording while already playing)   Probably didn't describe that too well, but hopefully you guys know what i'm referring to.  Sonar creates, then cleans up, a file in the audio directory every time a start/stop sequence occurs.  I suppose if the creation or deletion of that file went wrong during a start/stop operation, it could cause Sonar to hang.
 
My gut is telling me this is either a sound or video card issue WRT the motherboard (collision) or SP3 is at fault (should have stayed at SP2 where the file dates and RTL's pre-date Sonar).  Could well be that Microsoft made changes to RTL's that aren't playing right with drivers or Sonar or Plugs that pre-dated SP3.  Wouldn't you know I erased the SP2 uninstall so I can't even reverse it now.  Ugh.    It maybe could be an audio hard drive problem I suppose as well, maybe the drive is not responding to an I/O request.    I wish there was some way to troubleshoot the system once Sonar hangs, to figure out WHERE it is hung, even in a general sense that would make a huge difference in figuring out what area to narrow the sleuthing.
 
 
*** UPDATE ***
 
PROBLEM IDENTIFIED:
 
The issue is related to multi-processor (core) operation.  There is a component (I believe Directixer) that is not playing well on a multi-processor machine.  When I force Sonar to run in single-processor mode, no problems.