Please, please, please (no this is not James Brown imitation),

only post actual results/observations with what you did to DropoutMsec in AUD.INI and the effect it had on Sonar (good or bad).

Again, please refrain from jokes, inuendo's and non-sequitors. I'm interested in any hard and fast results that any one has had. And maybe this will help others to afraid to ask.

Why? I read the default is 250, and that a CW rep (Noel?) said maybe setting it 10 will help. That did nothing for my problem:

audio engine halting only when I have a project with 2 tracks saved with Echo Input: On and I open the project and simply minimize Sonar or wait about 3-5 minutes with the project idle the audio engine will halt.

This seems to happen at low latency (i.e < 5.8 ms). As some of you know, if you "Record" arm another track this will not happen at low latencies (pretty lame work around, if you ask me). Or this will not happen when using ASIO (track in ASIO, mix in WDM: also pretty lame, IMHO).

BTW, I've reported this to CW on a problem report but have yet to hear anything (but it's only been a week).

TIA for your replies with real world experience on the changing of DropoutMsec.

1000 (click here it's a real long story but it ends with DropoutMsec=1000).

Bassmanx
1000 (click here it's a real long story but it ends with DropoutMsec=1000).

Link is dead 
 
My DropoutMsec is 250 and i am not quite sure what  raising it to 1000 will do : i believe it will give platinum ( 250x4 =1000 ) so 4 x the length of time before platinum will drop out .
But then i get confused because it says in the negative value -2 it will give platinum twice the buffer size ? does that mean that if my sound card buffer is 2048 and DropoutMsec is -2 that platinum will use 4096 before a drop out ? or have i gone off the track !
 
1) which way is better longer drop out time 1000 or -2 = twice the buffer size
2) why cant we have both or is that silly

This is a very old thread, probably explains the broken link.

bapu
Please, please, please (no this is not James Brown imitation),

only post actual results/observations with what you did to DropoutMsec in AUD.INI and the effect it had on Sonar (good or bad).

Again, please refrain from jokes, inuendo's and non-sequitors. I'm interested in any hard and fast results that any one has had. And maybe this will help others to afraid to ask.

Why? I read the default is 250, and that a CW rep (Noel?) said maybe setting it 10 will help. That did nothing for my problem:

It's old, but it's hilarious to read this post and see how the Bapu has turned out. Obviously this post changed him. 

taccess

Bassmanx
1000 (click here it's a real long story but it ends with DropoutMsec=1000).

Link is dead

Just an old method, the better way is use the permalinks provided by the msg numbers at the bottom right of each post. In this case, the user should have used http://forum.cakewalk.com/FindPost/1266357
 

I use 500 ms.
 
A few years ago I was a beta tester for Kaleidoscope. At that time it was a serious CPU hog (it still is, but not nearly so bad).
 
I tried changing this a bit at the time. I forget the details, but I've kept it at 500 since then.
 
I'm always messing with serious Reaktor heavy CPU projects which stress my system.
 
I don't have much issue with dropout until I reach 90+% CPU utilization.

I suspect the issue reared itself when Bapu upgraded to the Sonar 7.0.2 the week before the OP.
 
...you know, when he had 30 vst's 

And a post count of 92.
 
(Sorry, Bapu, couldn't help myself).
 
Bob Bone
 

ampfixer

bapu

Again, please refrain from jokes, inuendo's and non-sequitors. I'm interested in any hard and fast results that any one has had. And maybe this will help others to afraid to ask.

 

It's old, but it's hilarious to read this post and see how the Bapu has turned out. Obviously this post changed him. 

LOL! I was just thinking...of all the people.........