Matt Hepworth said:
Quite a few SONAR users are reporting crackles and gaps on export with 4.7.1 with the SONAR Compatibility button engaged. Please post your experiences here.
I can also confirm the gapping issue in rendered files with the SONAR mode enabled. I believe UA added the SONAR Compatibility Mode to specifically deal with the native CPU munching during playback. Native CPU munching is not an issue when doing an export of a project. So the modus operandi should be:
1) For those experiencing the native CPU munch, during playback, keep the SONAR Compatibility Mode enabled
2) When rendering, simply disable this option, from the UAD-1 Performance Meter.
It only takes a moment to change the option. I always keep my UAD-1 Performance Meter open (in
Always on Top mode) anyway so I can easily monitor & adjust UAD-1 performance, on the fly. If you are mixing and want to do a quick render, just deselect the option, from the UAD-1 PM, after you stop playback and then go tho the SONAR Export dialog. After the render simply re-enable the option and continue mixing. You never have to close SONAR or the project.
I suppose UA should have put in the 4.7.1 readme, that
the new SONAR Compatibility Mode is to be used during playback/mixing to alleviate native CPU munching, just to avoid any confusion.
I am just thankful there is now a way to finally get rid of the native CPU munching when playing/mixing a project. This is something I have been asking for since 2003, since I got my first UAD-1 card and SONAR 2.2 was current version. Better late than never I guess.
At least, now you have the option to fully mix with UAD-1 plugins without that native CPU munching BS, during playback.
PS: I even found the
UAD-1 compatibilty mode to work in ACID Pro 6, as well. Other than a brief native CPU spike, when you first start playback, it totally eliminates the native CPU munch. This has always been a constant problem (even moreso than in SONAR) whenever mixng in ACID and using more than handful of UAD-1 plugins.
Nice job UA! :wink: