On Wed, Jan 22, 2014 at 11:59 AM, Brian Matherly <pez4br...@yahoo.com> wrote: >> 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? > > I think the base64 and hash ideas are both worth exploring. First, I'm going > to look into storing the results in a separate file and see how that could > fit into a typical application workflow. > > I really want to come up with a generalized method for 2 pass filters so > that we can make all 2 pass filters work mostly the same (eventually).
OK, but I do not want all 2 pass filters to require an external data file. Also, keep in mind that avformat consumer supports dual pass, and stores to a configurable external data file that it uniquely removes at end of second pass. Consistency is not king, but backwards compatibility might be. -- +-DRD-+ ------------------------------------------------------------------------------ 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
