[mythtv-users] Long delays with remote occasionally
jmastron at gmail.com
Wed Jun 17 20:38:18 UTC 2009
On Wed, Jun 17, 2009 at 12:58 PM, Yeechang Lee <ylee at pobox.com> wrote:
> Josh Mastronarde <jmastron at gmail.com> says:
> > Can you give more details -- perhaps the command line you used for the
> > transcode,
> The built-in mythtranscode, with the MPEG-4 codec. The transcodes were
> and the output of "ffmpeg -i <file>.mp4"?
> Input #0, mpeg, from
> Duration: N/A, start: 47715.723144, bitrate: N/A
> Stream #0.0[0x1e0]: Video: mpeg2video, yuv420p, 1920x1080 [PAR 1:1
> DAR 16:9], 14000 kb/s, 59.94 tbr, 90k tbn, 59.94 tbc
> I don't know why the first one is labeled mpeg2video when, as noted, I
> always used MPEG-4 when transcoding.
I think that's exactly the problem: Current ffmpeg (and my patched
probe code from it) sees these as "mpeg2video" when they might not be.
I patched in). If I'm right, you'll have the same issue with 0.22
(or trunk today). Either the files have a wrong tag somewhere, or the
ffmpeg code is broken (or I'm crazy). Do these files play in any
other player? Can you re-transcode one using ffmpeg and play the
Can you try transcoding one of the recent files using the same method
on your current install, and see what *that* result looks like to
More information about the mythtv-users