I don't know of any solutions, but I think i can tell you why they are CPU hogs.
At least for me anyway.
I run Cubase 9 with BIAS FX and BIAS AMP 2. I like to use AMP 2 within FX so I can use the FX with the nicer sounding amp models.
Turns out the BIAS plugs only seem to be optimized for 2 thread operation, so it pegs my first 2 CPU cores, while my other 2 physical cores (and 4 hyperthread threads) don't do squat. Total CPU usage will be less than 30%, but core one and 2 are pegged out and the VST engine is overloaded due to the plugin.
I'm using an RME UFX II. super stable drivers. I7-7700k, one of the fastest single thread CPU's out there even still (just barely slower then the 8700k). I also have it overclocked to 5.0ghz (stock is 4.2).
If i run one dual tone which means 2 total instances of bias amp 2 within Bias FX, at a 128 buffer, VST engine goes to 80+ percent. It's absolutely ridiculous.
You could have a $2000 CPU (i9-7980xe for istance) and still peg out your VST engine because of this plugin.
I isolated it to AMP 2. It was fine with any of the included Bias FX amps. When running 2 instances of AMP 2, the same effect occurs.
I am going to start a new thread about it, but thought I would post here in case you missed it.
With clean tones, there isn't much difference between IRs - but with overdriven tones, IRs, various mics and moving them, using post eq......grossly change the response, the ambient quality of the sound (how close it sounds to you, and how 'big an object it appears to be in the space'), as well as the vocal tone (for example, the nose-pinched farty sound that signatures Satriani). Then there's the basic tone of the IR, which in most cases is some variation of trying to push sound through a grate-covered horn bell.
The stock G25 still has the realest and open-est sound and saggiest yet non-flubby response of any IR I've tried. It could be more elegant in how it handles the treble.
Thanks! I learned a lot working on that piece, and am learning more as I go... hope to have another ready in the next couple weeks.
Got to say, the Artist setups from Tosin Abasi and Paul Masvidal have been particularly helpful to me, seeing how they set up their chains, how they tweaked each effect, to get those particular tones. The tone I'm getting on my new project is already significantly better (or at least, more like what I hear in my head )!
Real quick, in options /prefs/plugins/vst, is the path existing there where your actual bias amp, in my case, BIAS_AMP2_x64.dll, is residing?
In my case this is C:\Program Files\VSTPlugins
I'm suspecting Bias amp 1 dll is still hiding in one of the paths that REAPER has listed in its plugin paths as well. But you shouldn't need to get rid of it, REAPER will happily run both in the same RPP
Hi. I've been working up some new tones with B2, a few amp eq schemes and mic positions culminating in a mix of an eq scheme that started with one mic position, with the mic position that came from another eq scheme.
The sound, the quality of the timbre, I have in my head is like this: Imagine a solid metal wire, six feet long, an inch or so thick. Instead of striking it with a mallet, one pulls a baton back and forth over the [string]. The attack is naturally smoother. From attack through release, articulation has a broader range, and I imagine tastier. Having that timbre, and sliding the pick across like two cams coming together, rolling, and donging when they separate. Clear tone emerging from them.