I have update the wiki to read <q>First you need to reduce the CPU usage which helps reduce the chances of data under-run which causes the audio cut out. This can be done by turning off the Reverb and Chorus with the flags '-C0 -R0' and also by halving the sample rate with the flag '-r22050'. </q>
I have just retested it and halving the sample rate helps more than removing the Reverb and Chorus with the under-run. I am running on an eeePC 901 + EEEBUNTU On Sat, May 23, 2009 at 8:08 PM, Pedro Lopez-Cabanillas <[email protected]> wrote: > On Saturday, May 23, 2009, Louis B. wrote: >> Thanks for the info. I have just update the wiki with information on >> how to run fluid on a netbook. see >> http://fluidsynth.resonance.org/trac/wiki/LowLatency. Please correct >> it if it is wrong or you want to add anything else. > > "Also halving the sample rate with the flag '-r22050' helps a lot." > > I doubt the above advice would be beneficial for latency. On the contrary, > running FluidSynth with a native sound card sample rate will give the better > results, because reducing the sample rate requires ALSA to perform software > interpolation (by the plughw: layer) to transform the buffers into the native > frequency before sending it to the hardware. This requires larger buffers and > consumes CPU cycles. On the other hand, using the native frequency allows you > to use the hw: interface directly. > > By the way, which netbook are we talking about? Which Linux distro? > > Regards, > Pedro > _______________________________________________ fluid-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/fluid-dev
