Problem with ffmpeg or the source?

Andy Bircumshaw andy at networkned.co.uk
Fri Dec 17 12:19:44 EST 2010


On 17/12/2010, at 3:59pm, Shevek wrote:
> On 17 December 2010 15:54, Andy Bircumshaw <andy at networkned.co.uk> wrote:
>> 
>> Have the logs for those files shown the "brainfart" message?
> 
> logs?
> 
> does get_iplayer save a log by default? I haven't specifically enabled it.

Sorry, I meant this:

...
953454.642 kB / 3550.68 sec (99.7%)
953518.642 kB / 3551.60 sec (99.7%)
953582.642 kB / 3554.64 sec (99.8%)
953646.642 kB / 3558.14 sec (99.9%)
953685.298 kB / 3559.51 sec (99.9%)
Download complete
FFmpeg version 0.6, Copyright (c) 2000-2010 the FFmpeg developers
 built on Oct  8 2010 15:03:47 with gcc 4.4.3
 configuration: --prefix=/usr --libdir=/usr/lib --shlibdir=/usr/lib --mandir=/usr/share/man --enable-static --enable-shared --cc=i686-pc-linux-gnu-gcc --disable-debug --disable-ffplay --disable-network --enable-libmp3lame --enable-libvorbis --enable-libtheora --enable-libx264 --enable-libxvid --disable-indev=v4l --disable-indev=v4l2 --disable-indev=alsa --disable-indev=oss --disable-indev=jack --disable-outdev=alsa --disable-outdev=oss --enable-libopencore-amrwb --enable-libopencore-amrnb --enable-libschroedinger --disable-vdpau --disable-vdpau --disable-vaapi --disable-altivec --cpu=pentium-m --enable-gpl --enable-version3 --enable-postproc --enable-avfilter --enable-avfilter-lavf --disable-stripping --enable-hardcoded-tables
 libavutil     50.15. 1 / 50.15. 1
 libavcodec    52.72. 2 / 52.72. 2
 libavformat   52.64. 2 / 52.64. 2
 libavdevice   52. 2. 0 / 52. 2. 0
 libavfilter    1.19. 0 /  1.19. 0
 libswscale     0.11. 0 /  0.11. 0
 libpostproc   51. 2. 0 / 51. 2. 0
[h264 @ 0x9661670]brainfart cropping not supported, this could look slightly wrong ...
[aac @ 0x9661c00]Transition from an ONLY_LONG or LONG_STOP to an EIGHT_SHORT sequence detected. If you heard an audible artifact, please submit the sample to the FFmpeg developers.
   Last message repeated 1 times
[flv @ 0x9660420]Estimating duration from bitrate, this may be inaccurate
...

Only relatively infrequently do I use get_iplayer in "real time". I receive a daily email of my favourite "--since 24" search preset (check out get_iplayer's "--email" option - I'm really pleased with it), I just "--pvr-queue" programmes that I'm interested in (or add series using --pvr-add) and then run `get_iplayer --pvr` in a nightly cron job.

Each morning when the --pvr run is completed the full output from get_iplayer - about 3 or 4 meg of text like the above - is emailed to me. I think of that as the "log".

How long have you been using get_iplayer? Have you never noticed this visual corruption before? Is it only me that has? I perceive video artefacts as quite a common problem.

aB.




More information about the get_iplayer mailing list