[mythtv-users] mytharchive ffmpeg problem?

[George Mari]

On 10/20/2009 07:31 PM, Richard Shaw wrote:
> I was trying to archive the latest episode to Glee to dvd and ran into
> this problem for the first time. I'm running 0.21 fixes on a F10
> x86_64 system using an HDHomeRun for OTA HD. Below is a snippet of the
> relevant portion of the log.
>
> <---mythburn.log--->
> Press [q] to stop encoding
> [dvd @ 0x1f53f50]buffer underflow i=1 bufi=889 size=1792ate= 365.7kbits/s
>      Last message repeated 2 times147056kB time=228.32 bitrate=5276.3kbits/s
> [dvd @ 0x1f53f50]buffer underflow i=1 bufi=1482 size=1792
>      Last message repeated 10 times52344kB time=543.55 bitrate=5310.3kbits/s
> [dvd @ 0x1f53f50]buffer underflow i=1 bufi=1228 size=1792
> frame=35730 fps= 61 q=10.5 size=  773530kB time=1192.10
> bitrate=5315.6kbits/s       Last message repeated 11 times81388kB
> time=1199.14 bitrate=5338.1kbits/s
> [dvd @ 0x1f53f50]buffer underflow i=1 bufi=1394 size=1792
>      Last message repeated 5 times404010kB time=2151.23 bitrate=5346.5kbits/s
> [mpeg2video @ 0x1f70600]ac-tex damaged at 24 22
> [mpeg2video @ 0x1f70600]Warning MVs not available
> [mpeg2video @ 0x1f70600]concealing 80 DC, 80 AC, 80 MV errors
> [NULL @ 0x1f55ad0]error, non monotone timestamps 217160638>= 217159042its/s
> av_interleaved_write_frame(): Error while opening file
> ************************************************************
> ERROR: Failed while running ffmpeg to re-encode video.
> Command was ffmpeg -threads 2 -v 1 -i
> "/home/mythuser/temp/work/1/newfile.mpg" -r ntsc -target dvd -b 4771k
> -s 720x480 -acodec copy -copyts -aspect 16:9
> "/home/mythuser/temp/work/1/newfile2.mpg" -map 0:0 -map 0:1
> ************************************************************
> <---end--->
>
> Any ideas? I did some googling and this seemed to be an issue with
> earlier versions of ffmpeg (my package/version is 0.5-30.fc10). I
> ended up using devede which appears to have worked. I'm not sure what
> it uses to create the dvd mpeg2.
>
> Thanks,
> Richard
> _______________________________________________

I ran into this a few months ago, but I can't remember what I did 
exactly to work around it.  I think I may have re-encoded using a 
different profile (lower bitrate), but I'm not sure.

Google seemed to think an update to ffmpeg was in order, when I did the 
research back then.