Camaleón wrote:
On Wed, 29 Dec 2010 09:52:25 -0600, Hugo Vanwoerkom wrote:Camaleón wrote:Does it happen with any other audio file you play or just specifically when running "saytime"?Just when running saytimeOkay. Have you tried any of this? (read below) ↓↓↓↓You can try by restarting the sound server service. It could be that the sound device is being catched/occupied by the application... "lsof | grep snd" will tell :-?
'lsof | grep snd' before executing saytme: hugo@Debian:/$ more 11.lsof.snd.beforemplayer 2522 root mem CHR 116,5 4324 /dev/snd/pcmC0D0p mplayer 2522 root mem REG 8,3 403940 762176 /usr/lib/libsndfile.so.1.0.23 mplayer 2522 root 5r CHR 116,2 0t0 3875 /dev/snd/timer mplayer 2522 root 6u CHR 116,5 0t0 4324 /dev/snd/pcmC0D0p mplayer 2522 root 7u CHR 116,8 0t0 4327 /dev/snd/controlC0 mplayer 2529 root mem REG 8,3 403940 762176 /usr/lib/libsndfile.so.1.0.23 konsole 12946 hugo mem REG 8,3 403940 762176 /usr/lib/libsndfile.so.1.0.23 grep 18046 root 1w REG 8,3 0 36 /11.lsof.snd.before grep 18046 root 2w REG 8,3 0 36 /11.lsof.snd.before
'lsof | grep snd' after executing saytime and sound disappears:mplayer 2522 root mem CHR 116,5 4324 /dev/snd/pcmC0D0p mplayer 2522 root mem REG 8,3 403940 762176 /usr/lib/libsndfile.so.1.0.23 mplayer 2522 root 5r CHR 116,2 0t0 3875 /dev/snd/timer mplayer 2522 root 6u CHR 116,5 0t0 4324 /dev/snd/pcmC0D0p mplayer 2522 root 7u CHR 116,8 0t0 4327 /dev/snd/controlC0 mplayer 2529 root mem REG 8,3 403940 762176 /usr/lib/libsndfile.so.1.0.23 grep 8387 root 1w REG 8,3 0 37 /11.lsof.snd.after grep 8387 root 2w REG 8,3 0 37 /11.lsof.snd.after
Appears not to show a solution... Hugo