What a mess [EDIT] applies to VST version only..
-
@felix Ok, here are my system specs and operation/launch times using a (digital stopwatch)
Late 2012 (27-inch) iMac
2.9GHz Intel Core i5 (4 threads)
Memory - 16GB 1600 MHz DDR3
Graphics - NVIDIA GeForce GTX 660m 512mb
Samsung 850 EVO 250GB SSD (drive for apps and OS)
macOS High Sierra 10.13.3
Latest BA2 and BFX standalones & pluginsOk, here are the launch times in seconds:
Bias Amp 2 Standalone - (19.02)....second try (18.15)
Bias FX Standalone - (12.08)....second try (11.20)
Bias Amp 2 plugin - (18.25)...second instance (18.66)
Bias FX plugin - (12.05)...second instance (12.01)
Amp replacement menu (right click ) BiasFX - (2.84)
Selecting BA2 amp menu to see amps in BiasFX - (1.12)
Selecting amp (time before it changes) Bias FX - (0.79)
Also, scrolling through the BA2 amp selection in BiasFX is frequently choppy and so are some of the control knob graphics in BA2. Also the amp menu tabs in Bias FX become highlighted sporadically before my mouse pointer even gets close to them just after the menu appears when choosing to replace an amp. The BA2 amp order in BiasFX does not feel/look organized (at least nothing stands out as a helpful organization to speed things up if you know what type or name you want?)
All the plugins from other companies on my computer take an average of just a few seconds to load in standalone or as a AU plugin. My computer BOOT time from OFF takes only 23 seconds on average! So yes, BIAS startup times are Very long...especially when you have lots of instances of bias plugins in your project and want to get to work tweaking tones after first opening a project.
These recent Bias programs are the only programs that make me feel like I need to buy a new computer...but I know that's not the issue. Every other software company I use on my computer is snappy and fast like the day I bought my machine. My Spectrasonics Omnisphere 2 plugin loads in 2.13 seconds (initial opening after opening daw project) and that includes loading a 106mb sound sample to memory at the same time. My EZDRUMMER plugin takes 3.1 (from initial opening) and that too includes the loading of the drum samples from the ssd. I have over a dozen more popular third party brands of software instruments and Effects and they open as fast as the two I mentioned above or even faster.
-
@anthony-newcomb : none of that is slow. Forty-five seconds would be slow. I think UI load on mine is closer to thirty, but the rest is about the same. I'm surprised Macs are that slow. Not so great now is thay? Also, less coffee (or none) might help remedy jiggedy hand reaction time.
-
@tannhauser Haha Nice try with the stab at Mac ;). My Mac runs just fine thank you and has paid for itself over and over again. That said, I strongly disagree when you say that my Bias load times are not slow. When my computer boot time is "nearly" the same as BA2 load time, something strange is going on imo
Side note: I also had my coffee intake/overload "after" I ran my tests ;)
-
@anthony-newcomb : It was a satiric jest on the nature of that debate. I use PC for convenience and familiarity of OS. Yeah, load time is about the same as boot time. Eh.
-
Update: Have confirmed with PG tech support via a ticket that a large count of BA2 and BA1 amps slow down FX functions related to amp selection. Will vary due to a number of factors but it is a real thing.
I have purged all of my Bias 1 amps (uninstalled 1 completely after migrating any presets of interest) and culled my 2 amp set for now and it is usable, although in my opinion auditioning amps is still slow enough to be frustrating so I am just picking amps of interest and jamming them into an FX preset and then working with them from there. Once the amp is loaded in the FX signal chain I get no issues with speed of the FX app or plugin.