On Saturday 11 February 2012 23:09:25 Dan Dennedy wrote: > On Tue, Feb 7, 2012 at 4:04 PM, Dan Dennedy <[email protected]> wrote: > > On Tue, Feb 7, 2012 at 2:06 PM, j-b-m <[email protected]> wrote: > >> On Tuesday 07 February 2012 10:32:24 Dan Dennedy wrote: > >>> On Tue, Feb 7, 2012 at 10:08 AM, j-b-m <[email protected]> wrote: > >>> > Hello. > >>> > > >>> > Trying to improve image sequence support in Kdenlive, I discovered > >>> > that > >>> > MLT > >> > >>> > cannot currently load a sequence with files like this: > >> (...) > >> > >>> We could simply increase the hard-coded 100 to something much higher > >>> like INT_MAX. If you can do that and see how long it takes to fail on > >>> an invalid input, that would be great. Of course, it will actually > >>> vary depending on the machine, but just to get an idea... > >> > >> I tried increasing the max limit to INT_MAX but it then takes several > >> minutes on a modern laptop (core I7). > > > > yeah, not good :) > > > >> Setting a max limit of 1 million, it takes between 1 and 8 seconds to > >> process all possible file names, depending on the computer load. > > I have a new idea. In addition to the existing scanf-style heuristic, > add a new one where you embed the begin value between the % and the > 'd'. Then, set the begin property, make a new scanf format string > based on the length of begin, and run the scanf heuristic again. For > example, foo%01000d.png becomes begin=1000, and filename becomes > foo%05d.png. Checks for 'i' and 'u' and other relevant characters will > be supported as well.
Seems like a good idea to me. However we need to keep compatibility with older project files. Kdenlive currently uses the following pattern: foo%.5d.jpg So maybe the new format you proposed should have an extra character or something else to let MLT know that it has to do a 2 step processing.. > >> the pixbuf producer is initialized, then closed and initialized again, > >> which means that the filename processing routine is called twice. > > > > Not surprising to me at all. Melt is trying to do a safer approach to > > auto-profile by re-opening the composition instead of just asking all > > producers in the composition for the first frame again. Maybe it is > > not really necessary. Do you think I should change melt now to not do > > that? Maybe it will have a bad effect on kdenlive rendering. Or, do > > you always specify a -profile to melt, which bypasses the auto-profile > > step? > > I feel the re-open is probably not really necessary, but we can change > that behavior after this release to give it more time before the next > release. Yes, no need to hurry on this issue, we can make some tests after the release.. regards jb ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Mlt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mlt-devel
