If they care about startup latency, they should be paying attention to ALSA's period_size, rather than buffer_size - IIRC, it is the period_size that has to be filled with data before the sound can begin to be played.
Usual values (as in the config in my sig):
period_size 1024
buffer_size 8192
Interesting - what buffer size does it otherwise use?]
512, more details here: https://code.google.com/p/chromium/issu … ?id=178626
]]>cat /proc/asound/card0/pcm0p/sub0/hw_params
try launching chromium with --audio-buffer-size=2048
Awesome. That made all the difference! :-)
Thanks so much!
]]>Is this a known issue? Is there a solution?
This only happens on my 32-bit Arch install. My 64-bit install is fine...
]]>