Bridged version consumes ~30% more cpu than native. Tried with Nectar 圆4 native and x32 bridged. In mixing mode, compressors, gates and other modules use look-ahead algorithms for better results, thus incurring latency. I did not find that running in tracking mode (zero latency) or mixing mode (721 samples latency 44.1kHz) makes a big difference in cpu consumption. The default preset "Motown Power" uses 2 compressors in solidstate mode and saturation/limiter/delay modules on top of eq/compressors and cpu goes up to 2,3% When advanced options or modules are enabled in Nectar, cpu goes up. Measured with Alloy/Nectar only eq/gate/compressor modules enabled, only one compressor and set to digital. Reaper fx chain (eq, gate, compressor): 0,25% fx cpu I find that Nectar consumes way more cpu than Alloy, or a comparable chain with Reaper plugins, but nothing like what you are seeing:
IZOTOPE NECTAR 3 SPECS PRO
Windows 7 Pro 圆4 with Reaper 圆4 v35a, same Nectar version as you have. Upgrading from 29 to 35a makes iZotope Nectar unusable in the project, I upgraded from 24 to 29 and that really made CPU usage jump quite a bit. I only gave it a testdrive, but found out that i manage better with classic plug chain. Yes if you use the plug often i would suggest you contact the support at Izotope. I'll check their forums to see if it is a known issue.
The post from Janne83 is an indication that this isn't really REAPER-related at all, and that's sort of a relief.īTW, I do agree that the iZotope plugins can be quite CPU hungry, but they tend to be at least semi deterministic, the behavior I'm currently seeing is really odd. It's no problem for me to re-open the project if it solves the problem temporarily, and wait for a new build of Nectar if it is the culprit. Of course, it could be completely unrelated, I tend to have my projects open for a long time, and when it works it works splendidly, so this might be a false alarm. It's happened twice, and it's always been right after upgrading the alpha builds of REAPER. Disabling Nectar drops the CPU usage down to almost nothing. Have the performance meter up, and it indicates 38-40% CPU on the vocal group. Hey! I'm running 圆4 REAPER and 圆4 iZotope Nectar.
I don't have any answers (sorry) but that info will help the devs get to the bottom of it better.Īlso is the cpu usage actually on the track (check in reaper's performance meter) or showing up only on say the total cpu usage? PS: I've also tried to turn off anticipative FX processing, but that made it worse.Īre you running 32bit reaper or 64bit reaper and do you have izotope bridged? The OS is 圆4 Windows 7 Ultimate, the CPU is a Q6600, the machine has 4GB RAM and the project, OS and REAPER itself runs off an SSD. If not, I'll mess around with the older versions of the alphas to try to pinpoint exactly where this starts happening. It would be cool if anyone had the same experience as me, especially with the different versions of the alphas.
IZOTOPE NECTAR 3 SPECS HOW TO
The version of Nectar I'm running is reported to be "V 1.0.0.772 V 1.0.0.785" in the help-file not quite sure how to read those numbers.Īs far as I can tell, the last downloadable version of Nectar is 1.00. Playback on a fairly modest project (at least compared to what I could do with previous versions of REAPER) can do 80% on my machine (specs below). On playback, the CPU usage is fairly similar, but audio is not longer fluid at all. Total CPU usage is at around 55% for the project. Upgrading from 29 to 35a makes iZotope Nectar unusable in the project, making it use upto ~40% CPU in "mixing mode" and hovering at ~38% CPU in "tracking mode" (low latency, easier on the CPU).
Seems like this could be a problem that "comes and goes". Important info: Reloading the project seems to have fixed the issue, lowering the CPU usage of the vocal group to ~17% CPU, and total down to ~50%.