Mytharchive's mythburn.py assumes constant frame rate when using Project-X to apply a cutlist

[jonner@…]

Mytharchive has the option to use Project-X instead of mythtranscode to apply the MythTV cutlist to a recording while creating a Video DVD. It first transcodes the recording to a DVD-compliant encoding using ffmpeg, which must change the video frame rate if the source isn't one of the standard DVD ones. Then, it demuxes the transcoded file using Project-X, applying the cutlist from the MythTV database. Since the cutlist is based on frame numbers, the cut points are incorrect if the frame rate has changed from the original recording.

I've encountered this when creating a Video DVD from a recording of a local ATSC station broadcasting 720p59.94.

[brandons_at_geonautics_dot_com]

I've been working on mythburn.py to run projectx before ffmpeg is used on mpeg files. I'm working on this for two reasons, less video for ffmpeg to encode if commercials are cut, and also to extract subtitles. Preliminary tests show that the video is more stable (due to bad reception) than previous due to projectx fixing the timing before ffmpeg is used.

I'll submit a patch under a new ticket shortly.

[brandons@…]

I've posted a patch under ticket #6236 that changes how projectx handles mpeg files. Most of the patch was related to subtitles, but part of the outcome is that projectx is run before ffmpeg reecodes the video.

[paulh]

I guess if no one has fixed this in 5 years it's not going to get fixed