On Tue, Oct 12, 2010 at 10:38 PM, Carl Karsten <[email protected]> wrote: > This example shows something weird. in/out is in frames, but I think > it is getting converted to time, and then converted back to frames,
nah > and a different fps used for the 2 conversions. I haven't done the > math yet, and my ntsc math is questionable anyway. > > Also not sure how the auto_profile thing you mentioned will effect > this. It may hide it, but I don't think it will fix it. or something. > > melt -profile dv_ntsc -producer color:red out=1300 meta.attr.titles=1 > meta.attr.titles.markup=#timecode# -attach data_show dynamic=1 > -progress -consumer avformat:bar.dv pix_fmt=yuv411p There was a bug in the frame number to timecode converter with non-integral frame rates. I just committed a fix. I also committed a change to add support for #frame# > melt -profile dv_ntsc bar.dv in=1000 out=1000 > # I see 00:00:34:14 Using #frame# this now shows 1000. > melt bar.dv in=1000 out=1000 > # I see 00:00:41:10 And this obviously does not show 1000 but rather 1199. Thanks for helping to locate a bug here. Good thing that timecode converter was not used for anything critical with MLT's timing. Instead, it was only used for this timecode burn-in filter. -- +-DRD-+ ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Mlt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mlt-devel
