On Wed, Dec 19, 2012 at 11:07 AM, Janne Liljeblad
<[email protected]> wrote:
> Hi,
>
> I just added image sequence producer to Flowblade with something like:
>
>     producer = mlt.Producer(profile,
> "/home/janne/test/blue_green_screen/GSPlate.%04d.png?begin=0000")
>
> and it worked correctly, but when I did:
>
>   length =  producer.get_length()
>
> I always got 15000. Is this a bug? Clip played ok, but looped after
> frames ended.

If a producer does not set a length, this is the default length, and
the application can override it by setting the out and length
properties. If we had defaulted the length to INT_MAX, then loading
some producers may cause apps to have a really long clip duration,
which sometimes manifests in odd, unexpected ways in GUIs. And the
image producers do not try to see how many files are in a sequence as
that could incur quite a performance penalty upon loading a project
and long sequences.

> Also, without the "?begin=0000" in it, the producer often started from
> the wrong place.

Without it, it is supposed to attempt to locate the first image within
100 (arbitrary limit for performance reasons). If there is no image
within the first 100, then it falls back into a deprecated mode that
was retained for backwards compatibility with kdenlive projects. The
deprecated mode will set begin = 4!

> The "?begin=0000" is a recent addition, and
> http://mltframework.blogspot.fi/2012/11/version-086-released.html
> didn't mention it, so it's going to be in 0.8.8 release right?

correct

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Mlt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mlt-devel

Reply via email to