2014/1/20 Brian Matherly <pez4br...@yahoo.com>
>
> That is a good observation. I can confirm that it can take a long time to
> load results on the second pass. I considered reusing the localmotions. My
> only concern is what should be done if the application sets the results
> property externally. For example, in Shotcut, the application runs the
> first pass in a separate process, extracts the "results" property from the
> resulting XML file and then applies that string to the filter. So I don't
> know how to handle the potential situation where the results property and
> localmotions both exist and are different. Always loading from the results
> property avoids that potential problem but has the disadvantage of slowness.
>
> I'm open to ideas.
>
> ~Brian
>
>
Well, in that case, the Base64 encoding is the only thing that comes to
mind. I'm sure it would improve performance, and reduce the file size too.
After all, we don't need a human readable results, do we?
--
Regards,
Jakub Ksiezniak
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Mlt-devel mailing list
Mlt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlt-devel
