BFX2: Poping and crackling caused by high CPU
-
Hi!
Yesterday I upgraded from BFX1 and I have very high CPU usage in Bias FX 2 compared to Bias FX. For example if I open Google Chrome while Bias FX 2 is running, it pops and crackles. This also sometimes happens when changing between presets. With Bias FX 1 I never had these problems.
I tested the 32 and 64 bit version; I also tested two different audio interfaces (Yamaha CI2+ and Behringer UNC204HD) and different audio qualities. The result was always the same.
My notebook has an I7 (Dual Core) at 2,7 GHz, 24 GB RAM and only SSD drives. The CPU usage is around 30 percent (with BIAS FX around 15%).
Any hints? Since BFX1 and Guitar Rig are working without problems on this machine I think it is a BIASFX2 problem.
Thx in advance, Jörn
-
I did a video comparing resource use, including realtime CPU use on several of these types of plugins and yeah, Bias FX2 could stand a serious efficiency pass! The cabinet/IR loader is insane in its hunger compared to other IR loaders, that's probably a really good place to start.
-
@pipelineaudio Yes this is right - I also recognized that the cab simulation is sometimes the bottleneck - especially for presets, where two cabinets are simulated. If I deactivate them, the CPU usage decreases significantly.
-
We've improved the overall performance in the next update, please give it a try when it's available, thanks!
-
@Mike Thank you very much - I'm looking forward to the new version and I'll give you a feedback!
-
woohoo!! looking forward to the update... Christmas in july/august.
-
Awesome! Cant wait!
-
-
When is update expected to be out?
-
@jpishtey68 In mid-late August, but I can provide a beta version once it's available, thanks!
-
@mike Having a "beta" version sticky topic would be very cool. Cockos does that for Reaper and it is very much appreciated by the community, plus, you would get "free" feedback ;-)
-
@mike I've tried the new version, but sadly there is still the problem as described - especially when using two cabs :(
-
The IR loader uses as much Realtime CPU as it ever has and that is problem numero uno for my popping and crackling in low latency recording mode. Turning off the cabs and using another IR loader lets me record in peace. NADIR is free and works well for this.
