On Sat, Sep 01, 2012 at 01:53:18AM -0400, Joe Gidi wrote: > On Sat, September 1, 2012 1:35 am, Tomas Bodzar wrote: > > On Sat, Sep 1, 2012 at 7:11 AM, Joe Gidi <[email protected]> wrote: > >> I'm running 5.1/amd64 on a ThinkPad 410. sndiod is started in > >> /etc/rc.conf > >> with the default 'sndiod_flags=""' entry. I have working audio from mpd, > >> mplayer, and assorted other applications. Everything "just works." > >> > > > > Did you try to run with sndiod -d if there will be something more in > > console? > > Thanks for the suggestion. I ran "sndiod -d" then started playing a song > with mpd. Output looked like this: > > snd0.default: rec=0:1 play=0:1 vol=32768 join midi/in midi/out > snd0: recording s16le,0:1,48000 > snd0: playing s16le,0:1,48000 > snd0: block size is 960 frames, using 9 blocks > mpd0: buffer size = 8820, play = s16le,0:1,44100 > starting device > > Then the music stopped playing, and I got: > > sock: read 40 bytes in 22330us >
something has stolen the cpu for 22ms, but that's OK; but this is a strange coincidence though > At that point I tried pausing and restarting the song, which produced: > > snd0: device stopped > snd0: closing device > snd0: recording s16le,0:1,48000 > snd0: playing s16le,0:1,48000 > snd0: block size is 960 frames, using 9 blocks > mpd0: buffer size = 8820, play = s16le,0:1,44100 > starting device > snd0: device stopped > snd0: closing device > > Though there was no audio actually playing. > Could it be a program changing the mixer in the background? Could you check whether the mixer has changed by comparing mixerctl output before and after the sound stops? -- Alexandre
