False AUDIO ENGINE STOPPED error in Expanded

ba_midi


Has anyone else (using Expanded) seen a condition where Sonar puts up an error dialogue box saying the "Audio Engine has stopped unexpectedly ....(etc)" when in fact the audio is playing back just fine?

I've seen this a few times now -- very randomly.   It seems like a bug to me (one that obviously is difficult to reproduce though).

Anyone else?

I have never seen this myself, Billy.

Nope. Not seen that one yet.

Yes this has happend to me many times. I am on win 7 64 bit, external ua 25 sound card. 4 core 3.2 ghz and 8 gigs of ram, but still, I get this error probably 1 time every 4 or 5 projects. Now idea what to do. Ben

Brando

ba_midi


Has anyone else (using Expanded) seen a condition where Sonar puts up an error dialogue box saying the "Audio Engine has stopped unexpectedly ....(etc)" when in fact the audio is playing back just fine?

I've seen this a few times now -- very randomly.   It seems like a bug to me (one that obviously is difficult to reproduce though).

Anyone else?

I have never seen this myself, Billy.

Please let me know if ya do ;)

FastBikerBoy


Not seen that one but in a previous version B I think, I used to get a message about the sound interface not operating at the sample rate, even though it was playing .

Very occasional and random - not seen it since one of the quickfixes or patch, can't remember now.

The sample rate error message is different than the one I'm seeing but I wonder if it's related.   Only the minds at Cake would know ;)

bensworld


Hi Ba_Midi, At the moment I am getting multiple errors between Sonar x1 and East West PLAY software, a total nightmare. Some of the notes are not triggered on time and other times the Audio engine crashes, I have had no luck with win 7, I would have been better of keeping win xp 64 bit. Which sound card do you have? I have a UA-25, anything similar? Thanks, Ben

I"m still using XP 32bit here.  I am literally in the process of building a new system to convert to Win 7 64bit - though I'm not doing so for any other reason than wanting to get more memory going.   I don't really see any "great" advantage to going 64bit in a DAW other than that, yet.

I use the MOTU Ultralite MKiii (firewire version) but I keep my buffers at 512 - since I don't do much vocal or mic'd recordings, 512 plays nice with all the synths I use and still doesn't "feel" awkward.

E/W Play -- what version are you using, and what is your latency setting?  Also what is your "playback buffers" set to in PReferences (Sonar) ?  These all make a difference overall.   Also what is your MIDI Prepare Buffer set to?

My settings are:  
AUdio buffers 512 (latency)
Playback (and record) Buffers 256 ( I used to use 512 for playback but it seems 256 is ok since using Expanded)
MIDI Buffers 350 (I use to use 250 but find 350 works well too)

I suspect this "Audio Engine Dropout" error message is somehow related to streaming synths / samplers (like PLAY, etc) but I can't be sure.

The question is -- will Cakewalk find this error and correct, as it's difficult to repro in a bug report.

JazzSinger


Something to do with the Play Trails setting?

I don't use that setting (ie, it's not on).

And, I get this error even just by hitting play - or by doing a bouncedown, or by sitting back and listening and it randomly comes up.

It doesn't seem to be happening in every project, so there's obviously some set of circumstance that has to exist for it to kick in.  I somehow (again) think it's related to big synths like Omnisphere, etc.