[mythtv-commits] Ticket #11213: cutting and lossless mpeg2 transcoding generate strange files

[MythTV]

#11213: cutting and lossless mpeg2 transcoding generate strange files
------------------------------------+----------------------------
 Reporter:  mythtv@…                |          Owner:
     Type:  Bug Report - General    |         Status:  new
 Priority:  minor                   |      Milestone:  unknown
Component:  MythTV - Mythtranscode  |        Version:  0.26-fixes
 Severity:  medium                  |     Resolution:
 Keywords:                          |  Ticket locked:  0
------------------------------------+----------------------------

Comment (by John Pilkington <J.Pilk@…>):

 I think this ties in with what I see using
 http://www.mythtv.org/wiki/MythDVBcut

 As I use it, with dvb-t SD recordings in the UK, the cutlist gives the
 frame number of the first or last keyframe showing wanted content.  The
 byte-offset passed to Project-X is 1 packet after the first keyframe after
 a frame-marker that is set a few frames before the one from the cutlist.

 Project-X reports that it is dropping useless B-frames and says that it
 has used a cut-in byte offset which is identical to that of the next
 keyframe.

 Perhaps the logic here could be improved now, but it works pretty well.

 This doesn't shed light on what mythtranscode is doing but it does perhaps
 suggest that there's still something not quite right about the link
 between counting keyframes by the display and the editor; and of course,
 in these recordings, they aren't always evenly spaced.

--
Ticket URL: <http://code.mythtv.org/trac/ticket/11213#comment:8>
MythTV <http://www.mythtv.org>
MythTV Media Center