Audio Buffer without latency?
-
Hello, my name is Óscar and I am a happy user of Bias Amp 2, Bias FX and Bias Pedal in their professional versions. It turns out that today I started playing and a horrible noise began to sound, like a sizzle, on some occasion the sound completely disappeared, restarts, crashes, etc. I discovered that it has to do with the audio buffer size of my audio interface, a Presonus Audiobox USB card. Bias Amp 2 and Bias FX support 16 samples. I only get a problem when I enter the cloud and press preview to hear a preset. However, Bias Pedal does not support 16 or 32 samples. I have to put it to 64 Samples. I find it a bit strange that this program, apparently simpler than the other two, does not support a latency as low as the previous ones. What audio buffer size would be the right one to play, let's say, as if by an amplifier or a digital pedalboard without noticing the latency? What latency do digital pedals really have? 64 bit latency is a good starting point? Is that in 64 I seem to notice some latency. On the other hand, could I put the sample rate to 48000 instead of 44100? Improves the sound with it? and, finally, my processor is an Intel I5 with 8 GB of ram. What processor or memory should I have to be able to use the programs without latency to 16 Samples? Thank you very much.
-
I wrote a blog article about this subject a while back. Hopefully it will help.
https://www.gigperformer.com/audio-latency-buffer-size-and-sample-rate-explained
-
Sometimes, the audio settings in BIAS up on the right, go haywire.
Check and make sure it is set on ASIO -
which i5 processor do you have specifically? I ask because Bias AMP 2 seems to be very single-thread speed dependent, and an old i5 paired with a bad audio driver (presonus struggles with usb drivers. took them 2 years to get the studio 192 right ) could be contributing to your issue.
I run at 128 samples and 48khz and don't notice any latency, but with the presonus audiobox there are hidden buffers that increase delay. Try 128, but you may notice it.
-
Hi. Thank you all for your answers. I have already learned something about what I should know about buffer and others. I had always tried to play with the lowest possible latency, I thought it was the best, but in a new update of the Presonus interface driver I could select buffer size 16 and that's when weird things started to happen. Until then I put it in 64 and everything was perfect. When I put it on 16 I heard sizzle every now and then and on some occasion it stayed mute and I had to restart the system, etc.
My processor is an Intel Core i5-2320 CPU @ 3.00 Ghz and I have 8 GB of Ram. Use Windows 7 64 bits. I only know that an i5 was better than an i3 and that an i7 would be better. I lose myself with the figures that come later. I do not know if my equipment is enough for these programs like Bias, Amplitube, etc. I wonder if it would be better to invest in more processor and ram to be able to put the latency to 16 without any problem or is really unnecessary. Maybe we are taking for granted the latencies of the digital pedalboards and maybe they are in 256 or 128, so if we are in those values in my PC, it is not necessary to play more. In addition, as the first partner said on his blog, sometimes the latency is greater because of the distance we are from an amplifier than the latency of the PC. I'm thinking aloud. What latency is considered normal and acceptable and should we be satisfied if we achieve it? Or put another way. What is the buffer size that you usually put in favor of this amount of latency?
Many thanks.
-
The "Best" buffer size will be the highest setting you can use without noticing the delay.
On a presonus interface, 64 is probably ideal. I used to have the studio 192 and 64 was ok, 128 felt a little loose.
-
Thank you very much for the help.
-
Usually you want to care about the actual round trip latency, as the same number of samples on two different interfaces can be drastically different. I made a chart to help compare http://kailuamusicschool.com/tech/round-trip-latency-roundup/
-
@pipelineaudio Thanks you.
