[mythtv-commits] Ticket #11213: cutting and lossless mpeg2 transcoding generate strange files
MythTV
noreply at mythtv.org
Mon Oct 14 16:49:38 UTC 2013
#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 finlay@…):
Using the fixes/0.27 mythffprobe to check the original file and assuming
that the frame count is 0-based I see that mythffprobe sees keyframes at a
number one less than the cut points. I have been trying to use mythffmpeg
to slice up the video file (using -f segment) and find that I have to
specify cut point frame numbers one less than the myth cut point frame
numbers in order to get mythffmpeg to slice the file at the desired
keyframe. This suggests that mythffprobe and mythffmpeg have a consistent
count of frames that is 0-based but this count is one less than the count
that the myth editor is using. Does the myth editor use a 1-based frame
count? I can't see why I have to add one to the cut point frame numbers
for mythtranscode to not convert B and P frames.
--
Ticket URL: <http://code.mythtv.org/trac/ticket/11213#comment:9>
MythTV <http://www.mythtv.org>
MythTV Media Center
More information about the mythtv-commits
mailing list