The SelectRanges thing accepts single frame or ranges, ie
#######
27
43 44
52,53
79
99,100
121 122
#######
Will not choke (test long time ago parsed 40,000 single frames in about 1 second), lots of ranges/frames no more likely to choke than a single one.
If you give me till maybe midnight (got to leave in a little while), I'll knock up a script compatible to convert frame/ranges and extract those plus maybe
1 frame before and one after Interpolated frames.
Oh, the SelectRanges script may also require FrameSel.
EDIT: Memory not that great (below from Prune docs)
Quote:
I have tested the speed at which Prune() can do it's two pass parse on a command file of 30,000 frames, 42 of which were
omitted by the writefile script and the input of 30,000 single frame trims was coalesced to 8 trims overall
with an overhead of about 1.5 seconds on my less than powerful machine. In most cases, I think you are unlikely
to be wanting to feed in 30,000 or more trims to Prune, but the above example shows it can be done without effort.
Above timing was with dv=0, ie DebugView output off (a couple of seconds longer with full debug on).
|