Freezing Synth causes crazy overload, noises, crashes audio engine requiring Sonar restart

Hi all,
   Sorry if this issue has been resolved elsewhere. I looked around and couldn't find it.

When I freeze a synth (in this case it was Z3TA+ 2, but it happens with others as well), the operation is quick appears to work as expected. But as soon as I hit play, the audio engine freaks out (massive overload on the Master Bus and Hardware Out, but nowhere else). The meters stay maxxed out for about 10 seconds, then there's a huge wash of static, and then they come down again, and playback then generates only pops/clicks. Having read about other people's issues with the Control bar/various display problems sometimes interfering with bouncing (weird, but I guess rather common at one point), I tried hiding the control bar. But that did not prevent the behavior.

Using the audio engine button to turn it off and back on has no effect. I thought it might be a driver issue, so I tried switching to WDM drivers just to see if I could get playback working again, but no dice. I thought I read somewhere that there's a way to force a full audio driver reload, which seems like it would be an acceptable workaround for the time being, but I can't find how to do that. The only thing that gets it working again is quitting Sonar and reloading. When I do that, the frozen track is correctly frozen and everything plays back just fine. Unfreezing it works exactly like it should. I'm pretty baffled. Any ideas?

Windows 7x64
Sonar X1d build 533
Running 48 kHz, 24bits, factory ASIO drivers using a Focusrite Saffire 6 connected via USB.

Other than that, I've found the program to be stable and work well. But this is a real drag as not being able to freeze efficiently is a real workflow problem for me.

Any thoughts? Thanks for any help. 

EDIT: I found that closing the project (without exiting Sonar) and reloading it also gets things working again. Still not a very good option, but thought that might be useful information. 

Various experts in different fields come and go through a twenty four hour period, so it may be that the right person hasn't seen this yet. I, for one, cannot help you with this. I have issues of my own, but nothing like this one.

It might be a good idea to give even more details about your system and set-up than you already have. More details of your audio workstation, X1 settings, that sort of thing.

Good luck


andy

Hi,
   Thanks for the response. The track in question is a simple instrument track using Z3ta+ 2 with no FX.

Fast Bounce causes the same problem. Real-time bounce-to-track does work, but real-time freeze does not.

I think I've narrowed this to a delay compensation problem. It looks specifically like a conflict between Kontakt and high-latency plugins (LP64 EQ and PerfectSpace, to name 2). If I increase my latency all the way and freeze, it works fine. But returning the latency to its pre-bounce value brings the noise back. Disabling all FX stops it, but it will restart when I enable FX and hit play, unless I remove LP64 and/or PerfectSpace. I can have one of these two plugins, but not both.

What's odd is that I can have all these plugins and more if I reload the project after freezing. No problems. So it seems like PDC to Kontakt is getting temporarily confused somehow in the bounce?



A little more about my system:
2nd Gen i7 (4 cores) w/ 8 GB ram and dual 500GB HD's

Sonar X1dx64

Thanks.

The HD's are both 7200rpm w/ integrated Solid State for the first few gigs.
To my knowledge, Sonar doesn't profile the audio card when using ASIO drivers. Latency is set through the ASIO panel on the focusrite. I've got it at 6ms, with a total reported roundtrip latency of 32ms.

This doesn't seem to be a computer performance-related problem, since I can re-open the project without changing a thing, and it works just fine.  I don't necessarily need the LP64 at this point, but it's not the only one causing the problem. Any plugin that introduces much latency seems to fight with Kontakt after freezing. Very odd.

Check to make sure you have the "unload synth on disconnect" option enabled.