not quite sure what to do about xruns..
my recording laptop is a lenovo t440p 8gb ram running a behringer 404hd, and had a few questions about xruns
- if i can't hear them does it actually matter? (having xruns while recording)
- my understanding is they generally happened when the computer was maxed out, however I find they happen even when the processors are at around 65% and ram consumption is about 2gb, i would have thought there was plenty of processing 'headroom' to not have them?
I've read a bit about xruns and watched some yt vids but none of the advice seems to help (except setting the latency ridiculously high)
i've tried plugging the 404hd into different usb slots, and changing the usb3 to legacy mode in the bios (apparently that helps sometimes?) None of that seems to make any difference
I've tried all different combinations of frames and period settings, currently have 64/4 (5.8ms) which is about as slow as I want it to be.
if i'ts giving xruns without hte cpus being maxed that means something else is wrong? (also if it helps it often xruns when DSP load is only in the 20s)
any ideas?
AVL-MXE - xruns quetsions
Re: AVL-MXE - xruns quetsions
so i may have answered my own question,
i tried the periods/buffer at 3 because I remember reading (i think in the manual?) that usb interfaces often prefer that, with no luck.
i tried 2 and it seemed to like it better, so i tried it with 1 period/buffer (listed as 'default") and i can get it down to 2.9ms without xruns which.
for some reason the behringer seems to prefer low periods/buffer and high frames/period.
i tried the periods/buffer at 3 because I remember reading (i think in the manual?) that usb interfaces often prefer that, with no luck.
i tried 2 and it seemed to like it better, so i tried it with 1 period/buffer (listed as 'default") and i can get it down to 2.9ms without xruns which.
for some reason the behringer seems to prefer low periods/buffer and high frames/period.
Re: AVL-MXE - xruns quetsions
Hi,
Something I've learned in doing AVL for this many years is that you can provide a standardized system with all the tweaks, special kernels and boot options and the difference in how it behaves on different computers will be anything but standard. I have 3 main computers that run AVL and they all have different tolerances for Xruns, I have an old Samsung laptop that Xruns like crazy if WiFi is enabled and the problem instantly disappears if I switch off the WiFi adaptor.
The hardware and chipsets on the system, how the IRQ's are allocated and shared and numerous other factors will determine if it's a good Audio computer, a fast CPU and lots of RAM will make no difference on a system sharing the Audio device on the same IRQ as something else..
In the end what's left to do is exactly what you've done... experiment!
Something I've learned in doing AVL for this many years is that you can provide a standardized system with all the tweaks, special kernels and boot options and the difference in how it behaves on different computers will be anything but standard. I have 3 main computers that run AVL and they all have different tolerances for Xruns, I have an old Samsung laptop that Xruns like crazy if WiFi is enabled and the problem instantly disappears if I switch off the WiFi adaptor.
The hardware and chipsets on the system, how the IRQ's are allocated and shared and numerous other factors will determine if it's a good Audio computer, a fast CPU and lots of RAM will make no difference on a system sharing the Audio device on the same IRQ as something else..
In the end what's left to do is exactly what you've done... experiment!
Re: AVL-MXE - xruns quetsions
Yeah I figured since it was xrunnning without maxing out the ram/cpu there was something weird going on.
Don't know why I didn't think of trying it with lower frames/buffers number earlier, oh well sorted now :)
I also tried with a rt kernel in case that helped a little but I found it made it waaay worse, opening a decent sized project would max out all the cpu cores and ram so I guess I have my answer there :)
Don't know why I didn't think of trying it with lower frames/buffers number earlier, oh well sorted now :)
I also tried with a rt kernel in case that helped a little but I found it made it waaay worse, opening a decent sized project would max out all the cpu cores and ram so I guess I have my answer there :)