mytharchive problem with ffmpeg > 0.4.9_p20060530 [SOLVED]

[volumen1]

After a lot of head scratching, I've had to mask ffmpeg later than 0.4.9_p20060530. What I noticed with later versions (like 0.4.9_p20061016, for example) was that ffmpeg was creating tiny and super-compressed video streams. So, mytharchive was dying on the growisofs stage because the created DVD was only going to be like 800M instead of ~4G.

When I revert to the older ffmpeg, mytharchive works just fine. I have a feeling it's related to the "-b" options in /usr/share/mythtv/mytharchive/encoder_profiles/ffmpeg_dvd_ntsc.xml? Maybe the significance of these numbers has changed in the new version?

Has anyone else seen this?
_________________
I was born with a freakin' dice bag on my belt.
-- www.howsyournetwork.com

[gerd.badur]

Seems to be an ffmpeg bug in v0.4.9 (which should already be fixed).
See: http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2004-December/040721.html

[volumen1]

Hmm... that doesn't make sense. Your posting is from 2004? I can verify that if this is a bug, it definitely exists in version 0.4.9_p20061016. That's the version from oct 16 2006. 0.4.9_p20060530 works just fine.
_________________
I was born with a freakin' dice bag on my belt.
-- www.howsyournetwork.com

[Hobbes-X]

[Hobbes-X]

Duh... Easier to search trac: Ticket 2451.

Mytharchive was corrected in revision 11396, but it looks like the patch was never backported to fixes, which seems to be where the official e-builds come from. From the patch, it looks like you can just add a 'k' to the bitrate specified in /usr/share/mythtv/mytharchive/encoder_profiles/ffmpeg_dvd_ntsc.xml.

EDIT: New bug.

[volumen1]

Nice! That explains it. Thanks, I should have checked the man page for that -b option.
_________________
I was born with a freakin' dice bag on my belt.
-- www.howsyournetwork.com

[depontius]

[Hobbes-X]

Yeah- It got marked as resolved before I could verify whether it was fixed or not. Turns out that it was applied to fixes, just as part of a different patchset and I missed it. I've since seen reports that people were having the same problem, but I haven't confirmed whether it's actually been fixed or not.

I'm due for a major update session pretty soon, so I may just go back to using the portage version of myth and test it completely.

[depontius]

I'll just have to say that I'm finally burning DVDs with mytharchive. As far as I know, all myth-related components are amd64, none ~amd64. So at first blush it would appear that your problem is resolved.

At this point, I'm having 2 problems:

First, I'm getting partial shows some of the time. It seems to be fairly consistent for a given show. The Doctor Who episode, "The Rise of the Cybermen" stopped after 10 minutes the first time, and after 13 minutes when I burned it alone. On the first burn it was the first of 2 episodes, and the second was OK. I deleted and re-recorded it, and was able to burn both "The Rise of the Cybermen" and "Age of Steel" (a 2-parter) on a DVD successfully. I've had other attempts crap out 35 or 40 minutes in, etc. This seems to be during transcoding or somewhere, but not during the burn itself.

Second, and actually more important... I'm recording exercise shows for my wife. The motion is jerky and the lips don't match the sound. She says it isn't this way when viewing directly on myth, so it must be in the dvd creation.

Are these problems a matter of ffmpeg flags, or might I be better off with nuvexport, and then use something like tovid, instead of mytharchive?

I'll probably refile these as separate thread heads eventually, to minimize thread drift and track them better.
_________________
.sigs waste space and bandwidth