So Bias Amp only runs in 128 buffer size?
-
So weird thing. I have been trying to get the whole IAA thing jiving and tried something different.
Usually I run AUM and load a node with Tonestack and then a node with Bias amp, make sure levels arent clipping and send it to an IR loader.
Everything was 256 and i thought it was good but then I tried by loading Bias Inside of Tonestack.. well when i checked the audio preferences it then showed 128 and that it was controlled by a different app. Same thing with Aum it was running at 128.
What is the native buffer size for Bias Amp and how is it able to be changed?
-
Programs have defaults, sometimes fixed ones. I wouldn't worry about it unless you're getting artifacting. Lower buffer size is lower latency anyways.....
-
There's a dependency on the order in which you launch apps as well. You may want to try launching BIAS Amp first and setting the desired buffer size before launching other apps.
-
thats the thing though. I cant select the buffer size inside of Bias Amp. there is no option for that.
-
As far as I could tell when I was testing latency the other day, the same amp runs with much lower latency inside BiasFX than Bias Amp. I think its the open editor nature of Bias Amp that makes this happen, so once you are happy with an amp, I'd run it inside Bias FX
-
@pipelineaudio or tonestack? or in that case would i have to load it in jamup and then jamup in tonestack?
-
I would think so. Tonestack has its own latency setting but I'm not sure how it relates, if Bias' latency is added to it, or if it uses tonestacks settings. Lots of "I don;t knows on this ios stuff :(
-
I just realized that no PDC is triggered by Bias amp or Bias FX in REAPER.
-
@pipelineaudio said in So Bias Amp only runs in 128 buffer size?:
I would think so. Tonestack has its own latency setting but I'm not sure how it relates, if Bias' latency is added to it, or if it uses tonestacks settings. Lots of "I don;t knows on this ios stuff :(
totally frustrating huh lol. makes me wanna just trash it for windows. ugh lol. its all i got for now lol.
-
I think there are tests I can actually do to find this out, I am sorry for my extreme laziness on this today, I havent ridden in days, and am trying to make it out to the skatepark this afternoon...If I get a chance tonight I will try my best. Don't let me forget!
-
@pipelineaudio that's awesome. For me it's trying to get away for 20 minutes to write a riff before I have to take care of something lol
-
Running your tests right now
-
@Joe-Kuo @fooly
This is interesting, but maybe my methodology is flawed. Somehow Bias amp is less latent running inside Tonestack than on its own, or my methodology is brokenOk so
An empty tonestack project with Tonestack's buffers set at 128 = 15ms
Bias Amp, low latency, all modules bypassed = 21ms
Bias Amp, low latency, all modules in = 21msAnd now it gets weird
Bias Amp, low latency, all modules in, running as an IAA inside of Tonestack @128 = 15ms
Wait, what?
Bias Amp, normal latency, all modules in, running as an IAA inside of Tonestack @128 = 15msSo apparently Tonestack sets the buffer size for IAA FX inside it, so on to further investigation: 64 buffers in Tonestack
Bias Amp, low latency, all modules in, running as an IAA inside of Tonestack @64 = 12ms
-
Wow that is really interesting. So bias sample rate is determined by its host?
-
@brian-dress said in So Bias Amp only runs in 128 buffer size?:
Wow that is really interesting. So bias sample rate is determined by its host?
I believe this usually is the case, although I've experienced cases in which the host buffer size was dictated by another app. In those cases, I'd have to close both apps, launch the host, set the host's buffer size, then launch the other app within the host.
-
Just to be pedantic: buffer size, not sample rate.
-
@pipelineaudio said in So Bias Amp only runs in 128 buffer size?:
I havent ridden in days, and am trying to make it out to the skatepark this afternoon...
Ten minutes with the Royal Court, daily. No ride nor skate, nor even leave da howse, necessary.