• Hey Guys!
    Just curious how people are using the plugin..? It seems like using it as a “Plugin” on an audio (Egtr) track works pretty well (obviously). However, as you record more Gtr tracks you are adding more instances of it as a “Plugin”... hence more and more of your DSP power is getting used up with each new track.
    I’m currently using it in PT-2018 on a new Mac Mini i7 with 32Gb of ram. Could it be used on an Aux input and buss the signal to various recording tracks? Thereby using only one instance of Bias FX instead of multiple ones? Or, (if I’m correct) the plugin needs the DI audio of the recorded Egtr to work properly? I understand you probably wouldn’t be able to edit the sound once it’s recorded using this method.

    I’m looking for solutions that keep me from blowing out all my DSP in the computer just to have a bunch of Gtr tracks going at the same time. I like the idea of not having to “commit” to the sound that I tracked an idea with.

    Has anyone had any luck using the “Freeze” track command in PT..? Seems like this would be the best/only way to not have to commit to any sounds while saving your DSP for other tasks until you’re sure what you’ve got is working in the track. Does this actually work like I think it should..?

    Any thoughts? I’m interested in how best to use it to maximize DSP in sessions with a bunch of tracks running other Plugins. How many instances can you run..? Not finding any insight about this on the PG website.

  • A2

    It really depends on the effect. Some of Bias FX's modules are awesome enough that I like to send to them from multiple tracks, but obviously, that doesn't apply to all of them.

    I'm going to do another video about Bias FX2's resource use and hopefully we can encourage PG to do some efficiency passes, especially regarding the amount of hash these plugins write to the host project file