In terms of CPU munching, Sonar went from among the best, to dead worst due to UA dropping support for DXI!
This is a post from another thread in regards to testing the CPU munchiness of Sonar, Acid Pro, & Sonar when using the AUD-1s...
SONAR 6.2.1: 75%-83% DSP load before dropouts/crackling with a propensity for massive native CPU munching when pushing over 50% load.
ACID Pro 6d: 80-85% DSP load before dropouts/crackling with a propensity for major native CPU when pushing over 20% DSP load.
REAPER 1.865: 90%-95% DSP load before crackling in the audio (no dropouts, no native CPU munching, in fact native CPU usage is negligiblel).
When it comes to getting the most out of (4) UAD-1 cards with zero performance issues REAPER beats SONAR & ACID hands down!
Due to the DXI format in Sonar, I used to not worry too much about munching because I could push upwards of 95-98%!
But unfortunately, I'm in the process of switching from DXI to VST in Sonar 6.2... so after I read that post I had to run a test...
I took a finished mix of a song that I had done with the DXI versions of the UA plug-ins, re-inserted the plug-ins as VTS's and attempted to play the song... then….*AAARGH!!!* .. it happened... I had to freeze a gang of tracks until it was about a 50% load on the UA meter...
Very very disturbing, considering that when I play the original song (with DX plug-ins) it was pushing 95% and running smooth!
I'm running Sonar 6.2 on an ASUS P4C800-E Deluxe motherboard system, with 3.2 GHz P4, 2 GB RAM, Win XP Pro. The audio cards I am using are the Gina 3G and RME Multiface II. In addition to the 2 UDA-1 Cards, I am also using TC's Powercore fully stocked with 4 DSP cards.
I've been stranded with UA's v3.9.0 for the longest, due my apprehension towards undergoing the arduous task of saving every DX plug-in setting I've ever created as an FXP file, only to reload them back in the form of VSTz...
Well, upon the release of all the new stuff lately, I finally caved in and decided to make the jump to version 4.7... After a week of putting in at least 2 hrs a day (one day was 6hrs), I finally finished saving all of my 1587 plug-in settings as FXPz...
That’s right, OneTHOUSAND FiveHUNDRED andEightySeven!!!
...all in seperate folders within each Cakewalk session in respect to track/bus, after which, another folder was created according to sound, then named according to what plug-in being used and where it lies in the chain.... Too much fun!
All that hard work and this is what I get
:evil: