Hi there - all the sudden with no reason - I get 'An internal error occurred while processing the mixdown. The operation was unsuccessful.' when trying to EXPORT my mix.
Any ideas?

3 things come to mind
1. you have a plugin that doesn't like multi-core processing engine
2. you have a plugin that doesn't like the 64bit internal floating point engine
3. Or a plugin doesn't like fast bounce

Its easy to rule them out. Just disable them one at at time until it works.
Cj

Thanks
Everything worked yesterday with all those features and nothing has changed - Just all of the sudden wont export I loaded up a blank template with just a single audio file and turned off everything and still same result.
Although I can trick it and bounce down my mix and go grab it from the audio folder - but still I'd like to know why it decided to do this all the sudden

I changed the sample rate to 24 bit and not it works... strange.. hehe

Actually that wasnt it - I was exporting to an external USB drive when I got the problem. But when I exported to another it worked fine - so maybe the drive is failing.

Or maybe the drive is full
Cj

Still had pleny of room - but it was a cheap drive so I guess that was it. I'm relieved though! :)

hey i have the same problem can export my audio internal error occurred while processing the mixdown. The operation was unsuccessful can't save

SONAR 8.5.3  kompelet 6 vsts 
WINDOWS 7 windows 7 ultimate (86bit)
Intel Core 2 Quad CPU Q8200 2.34 GHZ 
4 GB Of RAM 
nvidia

can you help

Sometimes I get that error when I'm approaching my memory limit or the memory has got fragmented from a long session.

It doesn't help none when trying to save a project, but if approaching memory limits is the cause, firing up Sonar from a fresh reboot will minimize the likelyhood of it happening during a memory intensive session.

It can also explain why a project will seem OK one minute and not the next as Windows memory management is allocating and freeing memory handles automatically in the background.  And whilst Sonar is pretty good at assessing it's own memory requirements some (most notably) VSTi's can cause surprises that leave Sonar baffled (hence that particular vague message) as the plug hasn't reported back in a way that Sonar can understand, what the problem was.

Ergo ***t happens and starting from a clean slate can mitigate it somewhat.

Save revisions and save often, we all know that, but I don't do it either...

edit: I meant to say freezing some soft-synths if possible will help there too.

yeh i know what u mean just before i loaded up windows 7 its was fine tryed to freeze it to nothings happing. don't have problem with sonar 8.5.3 just not exporting my audio files to mp3 or wave. don't know what to do now?