Doom9's Forum - View Single Post

Richard Berg · 6th April 2006, 02:43

I'm not sure you understand how x264 (or VDub for that matter) work either. x264's backend will always be slower than disk I/O, so adding buffers would just be a waste of memory. It loads Avisynth, which does have PVideoFrames (equivalent to one of VDub's pipelines), but since it's a nonlinear editor the allocation is much much more complex than VDub. There's no way to fit the concept of a static # of pipelines into Avisynth: the number of frames and clips in the system is dynamic, and it also has an aggressive cache. The closest equivalent would be the SetMemoryMax function, but as the name implies, that's a maximum rather than a static #.

All of these programs are open source. If you come up with any workable ideas, submit a patch.

6th April 2006, 02:43	#360 \| Link
Richard Berg developer wannabe Join Date: Nov 2001 Location: Brooklyn, NY Posts: 1,211	I'm not sure you understand how x264 (or VDub for that matter) work either. x264's backend will always be slower than disk I/O, so adding buffers would just be a waste of memory. It loads Avisynth, which does have PVideoFrames (equivalent to one of VDub's pipelines), but since it's a nonlinear editor the allocation is much much more complex than VDub. There's no way to fit the concept of a static # of pipelines into Avisynth: the number of frames and clips in the system is dynamic, and it also has an aggressive cache. The closest equivalent would be the SetMemoryMax function, but as the name implies, that's a maximum rather than a static #. All of these programs are open source. If you come up with any workable ideas, submit a patch.