Hi, CJ van den Berg <[EMAIL PROTECTED]> writes: > Having said that though, there is one way to avoid this overhead. You can > use the autoload feature to make pulseaudio only load the -sink/-source > modules when a client requests them and unload them again when the last > client disconnects. This should give you close to 0% cpu when pulseaudio is > idle, but will probably pop and/or crackle when a stream starts playback.
aha, thanks! Simply commenting out add-autoload-sink output module-alsa-sink sink_name=output add-autoload-source input module-alsa-source source_name=input in /etc/pulse/default.pa but pulseaudio still keeps e.g. /dev/snd/pcmC0D0c open and consumes cpu time. Also, before this change my default.pa did not refer to alsa at all: $ grep -v "^[#;]" /etc/pulse/default.pa |grep -v "^$" .ifexists /usr/lib/pulse-0.9/modules/module-hal-detect.so load-module module-hal-detect .else load-module module-detect .endif .ifexists /usr/lib/pulse-0.9/modules/module-esound-protocol-unix.so load-module module-esound-protocol-unix .endif load-module module-native-protocol-unix load-module module-volume-restore load-module module-rescue-streams .nofail load-sample x11-bell /usr/share/sounds/gtk-events/activate.wav load-module module-gconf load-module module-esound-protocol-tcp auth-anonymous=1 load-module module-native-protocol-tcp auth-anonymous=1 so is this "use alsa for output and keep the device open" somehow implicit even if the configuration file does not mention alsa? If I comment out load-module module-detect then the alsa devices won't get opened so maybe this does "load-module module-alsa-sink" internally this making it not possible to "add-autoload-sink" it later? (I am wildly guessing here since I don't know pulseaudio much) best regards, Timo Lindfors -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
