[Kdenlive-devel] [Mlt-devel] Framerate Issue on MTS files ?
g.marco at freenet.de
Tue Dec 22 17:21:41 UTC 2009
some more test showed:
enable/disable the h264 skip frames feature in kdenlive setting will have no effect to the .kdenlive file (always off there).
but when render to script (.mlt file, to have all ffmpeg parameters in for rendering in the script too) the skip_frame values depends on the skip setting in kdenlive.
so only render to script must be fixed, to not set this value.
Am 22.12.2009 um 16:49 schrieb Dan Dennedy:
> On Sun, Dec 20, 2009 at 10:13 PM, Marco Gittler <g.marco at freenet.de> wrote:
>> Am 21.12.2009 um 02:46 schrieb Dan Dennedy:
>>> On Sun, Dec 20, 2009 at 1:23 PM, Marco Gittler <g.marco at freenet.de> wrote:
>>>> i found the piece, that caused the render in double frame rate of the video.
>>>> it is setting:
>>>> skip_frame:bidir (which is an ffmpeg option)
>>> is it set to 1 or empty string?
>> it is set to "bidir"
>> looks like
>> <property name="skip_frame" >bidir</property>
>> in the xml file
>>>> is this still needed to be set in the .kdenlive file or was this only needed in earlier versions of ffmpeg ?
>>> It is not needed by anything. However, it is still a valid option to
>>> improve seeking and playback performance especially for H.264, but it
>>> should be placed into MLT XML files which will be used to make a final
> Dang it! I meant to write it should NOT "be placed into MLT XML files...."
>> yes it is placed in mlt xml, when i disable in mlt file to render, it works right. having this enabled, these MTS files will render the video in double fps.
>> during cutting/seeking with kdenlive it seems to be usefull, but setting this in the mlt file to render, it does not work here as expected.
> Last time I checked, which was not too long ago, I have this H.264
> performance option enabled in Kdenlive settings, but it would always
> write the property into the MLT part of the XML project file with an
> empty string, which is as it should be IMO. I am not exactly sure how
> Kdenlive is toggling this property on the MLT API. Maybe there is a
> bug where it was actually doing nothing for a long time, that was
> fixed, and now it appears during render as well, which is not good.
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> Kdenlive-devel mailing list
> Kdenlive-devel at lists.sourceforge.net
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3914 bytes
Desc: not available
More information about the Kdenlive