[FFmpeg-trac] #2504(avdevice:new): Audio glitches and distortion when recording alsa
FFmpeg
trac at avcodec.org
Thu Jun 27 09:24:54 CEST 2013
#2504: Audio glitches and distortion when recording alsa
------------------------------------+------------------------------------
Reporter: MrNice | Owner:
Type: defect | Status: new
Priority: important | Component: avdevice
Version: git-master | Resolution:
Keywords: regression | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
------------------------------------+------------------------------------
Comment (by MrNice):
I am running the bisec and did more than 100 loops.
I use the scrip
{{{
#!/bin/bash
let loopnb=100
while true;
do
let loopnb+=1
./configure --disable-protocols --disable-decoders --disable-encoders
--disable-demuxers --disable-muxers --disable-outdevs --disable-bsfs
--disable-parsers --enable-protocol=file --enable-decoder=pcm_s16le
--enable-encoder=pcm_s16le --enable-muxer=wav --disable-filters && make
ffmpeg
./ffmpeg -f alsa -ac 2 -i hw:0,0 -y out.wav -t 0:0:10
mplayer out.wav -loop 10
echo "loops num:" $loopnb
echo [g]ood or [b]ad sound? [e]xit [p]lay
read KB
case $KB in
g)
make distclean && git bisect good
echo GOOD;;
b)
make distclean && git bisect bad
echo BAD;;
p)
mplayer out.wav -loop 4
echo;;
e)
exit;;
esac
done
}}}
I can count the loop number but I can't see the bisecting progress.
1) Could you let me know what command I could add in the loop to check
there is a change between every test.
2) Do you know how many loops there are between f2f35d3 and 743b389. I
started from f2f35d3 and I assume I'll reach 743b389, so I hope I am going
in the good way.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2504#comment:95>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list