Processing many AVIs - a bug ?

Processing many AVIs - a bug ? 

He said if he keeps the number down, his scripts open fine. He's only getting that error because he's opening many, many clips. I think it's a known issue that we discussed before. Try it yourself and see: Code:

What happens if you use: setmemorymax(128) or something like that?

You've hit the maximum number of dll's a process can load - it's about 72, and there isn't much to do about it unfortunately. You could try loading additional videos by using DirectShowSource, but I'm not sure how much it'll help.

Setmemorymax does nothing. New version of Avisynth does not help. 2 sh0dan : why there's a need of loading a separate dll for every avi file ? And if this is unavoidable problem, then what could be done ? Would Import() launch another process that will be able to load its own 72 files then ?

Shubin, As sh0dan say's there are limits. The other limit around the 50 files mark is the VFW codec table space. I have been caught by this before and I have a note to myself to add an option to SegmentedAviSource() and SegmentedDirectShowSource() to "stack" the input files into a single codec like VirtualDub does. The bad news it probably won't happen until 2.5.7. IanB

I see a possible solution : it is possible to detect that the given fragment (clip) will be used only in one place of a resulting clip. Thus it is possible to close it, freeing the slot. Processing many files is so far the best way to make video out of home-made DV source. Programs for downloading video can split it into scenes. This makes processing much easier.

To remedy and even experience an initial loading efficiency boost; Pop these dependencies extracted from a recent distribution into the directory or direct path of your application(s) that will (also) be hosting avisynth's dynamic link library. msvfw32.dll winmm.dll