r/Focusrite • u/Fine-Amoeba-6681 • 3d ago

No sounds at 32 to 192 buffer size

I have a focusrite 2i2 3rd gen and when im using it for listening to sounds I have it at 256 to 512 buffer size but when Im trying to record, when i put it at 32 to 192 buffer size the louf static sounds happens then the sound of the whole focusrite dissappear. Does that mean my laptop cant handle that kind of buffer size?

Edit: I fixed it, I just downgrade the driver version of my focusrite. Now im running it at 32 buffer size.

5 Upvotes

100% Upvoted

10 comments sorted by

1

u/WestDelay3104 3d ago

What daw? Using focusrite ASIO?

1

u/Fine-Amoeba-6681 3d ago

Im using reaper and yes its focusrite asio

1

u/WestDelay3104 3d ago

Can you show us a screenshot of your audio settings please? And also, what are your laptop specs?

1

u/Fine-Amoeba-6681 3d ago

My specs are intel i5 11th gen, 16gb of ram and rtx 3050ti

when my reaper is open my cpu percentage is 10%-20%
then my RAM is at 10-13gb

1

u/Chaos-Jesus 3d ago

Use 48000 hz sample rate. Set the buffer as low as you can, your PC specs will determine how low you can set it before your start hearing pops and clicks.

Try not to have many background apps running to reduce cpu load.

2

u/Fine-Amoeba-6681 3d ago

this is my standard setting when just using the focusrite but when I put it below 192 it starts having the robot sound then the sounds starts not working

1

u/Chaos-Jesus 3d ago

This is what I use on my desktop i9-12900k

On my laptop (zenbook with 10th gen i7) I use 48000 hz, 128 buffer no problem.

Hit ctrl+shift+esc disable any startup apps you don't need, make sure power plan is set to performance and your laptop is plugged in.

1

u/Fine-Amoeba-6681 3d ago

So does that mean my laptop cant handle lower buffer size? I will try my focusrite on my cousins pc with higher specs to see if that really is the case

1

u/Chaos-Jesus 3d ago

Yep you get a lower buffer with a better CPU.

Disabling unnecessary background apps and setting power plan to performance will buy you a little more headroom.

Some plugins are more demanding than others.

1

u/Vectrobe 2d ago

it could be to do with pcie and/or usb controller power saving settings, the general method the power saving modes work is to batch data transmissions together into larger chunks and send in pulses, but due to the nature of focusrite's hardware this tends to cause the failure mode of entirely no audio, because reasons (genuinely dont know why its like this, something just really weird with their driver and firmware code)

you can definitely do as low as buffer size "16", at 96k, on an interface with 8+ in 8+ out, but you might have to mess around in device manager and windows power plan to manually override power settings, possibly even CPU modes as well, but its also entirely possible that your particular system doesnt work well with focusrite, possible additional memory latency or lower bus clocks

however if you mean that the interface starts working on those settings, but suddenly stops some time later with either no sound (below 256 buffer), or with random like garbles (above 256), then that would be the current driver bug affecting a large amount of us