[FFmpeg-trac] #2504(undetermined:new): Audio glitches and distortion when recording and direct play

FFmpeg trac at avcodec.org
Tue May 21 22:20:19 CEST 2013


#2504: Audio glitches and distortion when recording and direct play
-------------------------------------+-------------------------------------
             Reporter:  MrNice       |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  unspecified  |  undetermined
             Keywords:               |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by cehoyos):

 Replying to [comment:24 MrNice]:
 > {{{
 > $ ffmpeg -f alsa -ac 2 -i hw:0,0 out.wav
 > FFmpeg version UNKNOWN, Copyright (c) 2000-2009 Fabrice Bellard, et al.
 >   configuration: --prefix=/opt/ffmpeg-opt/usr --bindir=/opt/ffmpeg-
 opt/usr/bin --datadir=/opt/ffmpeg-opt/usr/share/ffmpeg-opt --incdir=/opt
 /ffmpeg-opt/usr/include/ffmpeg-opt --libdir=/opt/ffmpeg-opt/usr/lib64
 --mandir=/opt/ffmpeg-opt/usr/share/man --shlibdir=/opt/ffmpeg-
 opt/usr/lib64 --arch=x86_64
 >   libavutil     49.14. 0 / 49.14. 0
 >   libavcodec    52.11. 0 / 52.11. 0
 >   libavformat   52.25. 0 / 52.25. 0
 >   libavdevice   52. 1. 0 / 52. 1. 0
 >   built on May 21 2013 15:29:58, gcc: 4.4.7 20120313 (Red Hat 4.4.7-3)
 > Input #0, alsa, from 'hw:0,0':
 >   Duration: N/A, start: 46721.105014, bitrate: N/A
 >     Stream #0.0: Audio: pcm_s16le, 44100 Hz, stereo, s16, 1411 kb/s
 > Output #0, wav, to 'out.wav':
 >     Stream #0.0: Audio: pcm_s16le, 44100 Hz, stereo, s16, 1411 kb/s
 > Stream mapping:
 >   Stream #0.0 -> #0.0
 > Press [q] to stop encoding
 > size=    2516kB time=14.61 bitrate=1411.2kbits/s
 > video:0kB audio:2516kB global headers:0kB muxing overhead 0.001708%
 > }}}
 > Now audio is good :-)

 Then please use git bisect to find the change introducing the problem.
 (And please do not waste time with other tests, I really don't think they
 make any sense if you want to solve the problem.)

 git bisect sometimes doesn't work well with FFmpeg, I will help you if
 necessary.

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2504#comment:25>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list