Nick Daily wrote: > Simply add: > > -o audio.alsa.device=hw:0 > > to your standard fluidsynth parameters, the 100% cpu usage is related > to an error in the ALSA code.
Unfortunately this doesn't solve the problem for me. Starting Fluidsynth with "/usr/bin/fluidsynth -m alsa_seq -a alsa -o audio.alsa.device=hw:0" still shows the issue. Passing "-a oss" instead seems to make the problem disappear, so Nick's diagnostic appears to be right. Note that I pass hw:0 to gstreamer's default sink, so I know that works with my hardware. Greetings, -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
