There is a known problem (with any source filter) when you hit some limit on file open count, it seems to be a system resource limit and may
be different for each source filter.
Here a thread on it:-
https://forum.doom9.org/showthread.p...it#post1532807
x64 probably just has a higher limit and so you have escaped so far. Modify your method, ie dont open the same file gazillions of times.
More:
https://forum.doom9.org/showthread.p...+resouce+limit
[See IanB post]
https://forum.doom9.org/showthread.p...+resouce+limit
There are probably many more threads mentioning the problem.
Quote:
Originally Posted by IanB
@hinsdale1,
Yes it is the number of Direct Show environments created by each DirectshowSource() that is killing you. Each one is sizeable.
The error message indicates severe lack of free memory in the process address space.
The call was for an 8Mb chunk, SetMemoryMax was 512Mb, but there was only 64Mb already allocated (probably as 8 of 8Mb buffers) in the frame cache so far. So the address space is pretty maxed out, 64MB is about 3% of the 2GB address space.
Options:-
If you environment supports it you could try the 3GB hack. This might give you upto 50% more address space.
Try SetMemoryMax(32), this will force very aggressive reuse of the existing buffers.
Assuming the shape and sizes are compatible, externally splice your individual .mkv sources into a single big mkv source so you only need a single Direct Show environment. You could then cut the single input clip back into component clips to maintain your work flow.
Try a different source filter technology, like ffmeg or DG, that may be less memory intensive.
|