On Wed, Oct 30, 2013 at 7:02 AM, Juan Martin Runge <jmru...@gmail.com> wrote: > Hi, > I've noticed that when I do not set a profile, melted takes it from the > first clip I load in the unit.
It does? I do not expect that. It should default to dv_pal unless otherwise configured. On the other hand, a tool like melt or shotcut can do auto-profile. > That means, if I load a PAL clip (25fps), > the rest of the clips are appended as they were 25fps, regardless their real > fps (I append a NTSC clip after and using LIST command I see it as 25fps). Correct, everything is conformed to the profile regardless of whether it is explicit profile or auto-profile. > The same happends if I first load a NTSC clip and then a PAL clip. Both > show 25fps in the LIST and USTA commands. Does this mean that melted will OK, if you wrote that correctly, this is expected because it using dv_pal profile. > actually play the clip at the fps shown? I dont see the frame count change, > so I assume it will play slowly (NTSC clip at 25 fps) or quickly (PAL clip > at 29.97 fps) How affects this the sound of the clip? And the duration? If No, it does not change the apparent speed or duration (+/- one video frame duration). The sound is unaffected. Video frames are simply dropped or repeated to match the source fps to the profile fps. MLT does not support variable frame rate, and variable frame rate has no place in traditional SDI or ASI oriented broadcast playout anyway. > my NTSC clip would have 1 min lenght at 29.97 fps, if I play it at 25 fps it > will be longer and if I play my PAL clip at 29.97 it will be shorter. Can > someone clarify this for me? We're building our playout > (http://github.com/inaes-tic/mbc-playout) and we would like to sync frame > perfect our schedule time for a clip with melted, so we need to know exactly > what melted will be doing to calculate this. The length property on the producer is based on the profile fps, but the accuracy of that estimate is dependent upon the format and libavformat version. The only real way to determine an accurate length is to decode every frame and if successful (mlt_prooducer_get_image() returns 0) increment the length. MLT does not do that automatically; you need to do that if you need that. > > I hope I was clear enough. Feel free to ask for more specifications if > needed. > > Thanks in advance, > > Juan Martin Runge > ./opcode team -- +-DRD-+ ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Mlt-devel mailing list Mlt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mlt-devel
