• SONAR
  • Cannot bounce tracks or entire mix, cannot export to mp3 etc. (p.2)
2014/06/17 09:52:22
markyzno
WhiteSheet
Ok I tried it on several projects now, but I had no drop-outs whatsoever, none :/




I would troubleshoot ONE project you know for certain that has this bounce issue.
 
Gswitz's steps are great above but I fear, ultimately will lead to a corrupted session or bug.
 
When I have had this across a few projects, everytime there was no relationship with the corruption between them.
 
Very frustrating...So, I just found a work around in each instance (to my annoyance) and carried on working.... I am VERY bad at contacting support tho...Not sure if I have ever done it.
 
"An internal error occured" is the most unhelpful annoying error message there is.
2014/06/17 10:36:05
WhiteSheet
at jmasno5: the messages are from Sonar X3, plus
at gswitz: I'm not sure what you are referring to but if you mean the 64-bit engine, I have never even had it activated, don't even know what it is........
 
   at everybody: I just found out what the PROBLEM is: I bypassed all effects, then both bouncing and exporting worked. Still it was way too slow compared to how it used to work. And also this is no solution. I NEED to be able to bounce with effects ACTIVATED. So does this help?
   Maybe I DO need to install the x3e update, but the last time I updated (which was in Sonar X1), EVERYTHING WAS MESSED UP, some plugins didn't work anymore, some buttons couldn't be clicked and stuff like that, so I'm VEEEERY cautious with updating Sonar X3. I hope I don't have to.
 
   And also: changing preferences and settings should neither be root of the problem nor a solution, because the problem I now have just turned up randomly. Over night. I didn't change anything. I didn't install any new plug ins. I didn't install any new programs EXCEPT Kaspersky. But I'll eat my hat if that's got anything to do with it....
2014/06/17 10:40:06
dwardzala
You definitely need to install the X3e update as it fixed a number of these type issues.
 
Also, since you have identified that it is a plug-in you can troubleshoot to determine which one is causing the issue.
 
And it may, in fact, be Kaspersky - anti virus programs and sonar don't often play well with each other.
2014/06/17 10:54:30
WhiteSheet
at dwardzala: I don't think that it is a SPECIFIC fxplugin but rather effects as such.
And even though anti virus programs and sonar might not play well together, I really don't think that that's causing the issue because kaspersky is not showing anything when scanning sonar x3, if you know what i mean?
So I could try to deinstall kaspersky and install the x3e update, but I have a bad feeling about it, I will wait for a reply of the tech support...
 
Thanks everybody so far!
 
2014/06/17 11:03:11
jmasno5
WhiteSheet
   I NEED to be able to bounce with effects ACTIVATED.
   Maybe I DO need to install the x3e update,

 
x3e update:
Set an new system restore point in Windows first then install the update.  Worst case you can go back but the E update is good here.
 
SLOW RENDERING:
Go to Edit/Preferences/Audio/Configuration File   - Change BounceBuf SizeMsec number.  This worked for me when bouncing a tune took forever.
 
I got this from https://www.cakewalk.com/...different-from-playbac
 
"At a value of 0, the bounce buffer is the same size as the Mixing Latency value that you set in Edit > Preferences > Audio - Driver Settings. If you find that bouncing tracks, especially with certain soft synths, takes a very long time, you can set this value to 100, or some value between 0 and 350 so that the bounce buffer will use a more efficient size for bouncing, which has different requirements from normal playback latency."
 
2014/06/17 11:16:01
lawp
WhiteSheetI didn't install any new programs EXCEPT Kaspersky. But I'll eat my hat if that's got anything to do with it....



you want mayonnaise with that?
2014/06/17 11:44:09
gswitz
Easy enough to disable Kaspersky as a test.
 
In Kaspersky you can specify files not to scan... folders not to scan. That's pretty useful.
 
2014/06/17 11:50:12
dwardzala
WhiteSheet
at dwardzala: I don't think that it is a SPECIFIC fxplugin but rather effects as such.
And even though anti virus programs and sonar might not play well together, I really don't think that that's causing the issue because kaspersky is not showing anything when scanning sonar x3, if you know what i mean?
So I could try to deinstall kaspersky and install the x3e update, but I have a bad feeling about it, I will wait for a reply of the tech support...
 
Thanks everybody so far!
 


I'll let one of the IT experts on here explain why anit virus software and sonar are not a good mix as I won't do it justice.
I do know that many similar issues have been fixed when AV software has been disabled and that most of us on here *try* to run sonar on machines without AV active (and off-line in general).
 
If you look at it strictly from a what changed standpoint - Kaspersky is the most likely cause.
2014/06/17 11:53:00
gswitz
idk... I think getting on the latest patch for Sonar is your best bet.
 
If kaspersky were to cause a problem, I would expect it would be with IO latency. In other words, Kaspersky would decide to scan all your new WAV files to make sure they don't contain viruses. Because the files are big, it would take 10 minutes or so during which you would basically not be able to play back your project for more than a minute or two. Once the problem was solved, you could play it back just fine.
 
I suppose it could cause probs scanning active RAM, but ...
 
Pull up on X3e and give a report, WhiteSheet. Let's see if that doesn't do the trick.

G
 
2014/07/16 01:44:19
soundtweaker
I get the "internal error occurred" on mixdowns in some projects made it X3. The problem has to do with splitting audio tracks. The timeline will stop in the same spot every time. It actually stops a bar before the actual corrupted clip. For me it doesn't have anything to do with latency, buffers or FX. The fix was to delete the split audio clip and slip edit the previous clip to show the deleted waveform. This is a bad bad bug.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account