[FFmpeg-user] Weird FFMPEG Key-frame Issue

[Ross (MikiPro Services Ltd)]

Hi FFMPEG,

I have compiled FFMPEG from GIT:

ffmpeg version N-63716-g763e714 Copyright (c) 2000-2014 the FFmpeg 
developers
   built on Jun  7 2014 02:15:09 with gcc 4.8 (Ubuntu 4.8.2-19ubuntu1)
   configuration: --enable-gpl --enable-libx264 --enable-libmp3lame 
--enable-nonfree --enable-libaacplus
   libavutil      52. 89.100 / 52. 89.100
   libavcodec     55. 66.100 / 55. 66.100
   libavformat    55. 42.100 / 55. 42.100
   libavdevice    55. 13.101 / 55. 13.101
   libavfilter     4.  5.100 /  4.  5.100
   libswscale      2.  6.100 /  2.  6.100
   libswresample   0. 19.100 /  0. 19.100
   libpostproc    52.  3.100 / 52.  3.100


I am running this command line:

screen -d -m -S TV3 ffmpeg -i 
"udp://@224.2.12.1:1234?fifo_size=10000&overrun_nonfatal=1" -vcodec 
mpeg2video -pix_fmt yuv420p -me_method epzs -threads 16 -r 25 -g 45 -bf 
2 -trellis 2 -cmp 2 -subcmp 2 -s 720x576 -b 1500k -bt 300k -acodec mp2 
-ac 2 -ab 192k -ar 44100 -async 1 -y -f mpegts udp://224.2.89.3:1234

This has worked perfectly for over a week and I have been really happy 
with it how ever there was a weird key frame issue that popped up a 
couple of days ago and ruined 2 days worth of recordings.

Here is a copy of the error: http://103.14.142.201/ecast/shortwtf.mpg (40MB)

As you can see, the 'troll dog' key frame seems to be referenced 
throughout the rest of the transcode.

I don't know if this is a bug or an error with my setup. I am going to 
compile another version with --enable-pthreads and try using that 
version instead. Have you guys experianced something like this before? 
Does anyone use FFMPEG on a 24/7 basis?


Thanks for your time

Ross