The x264.exe encoder, in CRF mode, has a lookahead function. I think this means that, while it encodes frame 321 for example, perhaps at the same time it's algorithms need to check for something in frames 322 to 352.
But in order for x264 to get frames 321 to 352, first Premiere Pro or Vegas Pro must render them, then debugmode must write them to hdd as uncompressed avi. And at the same time, the CPU is used by the NLE for rendering, by avisynth for filtering, and by x264 for encoding.
What if x264 needs frames 321 to 352 but doesn't get them all exactly when x264 needs them ? Is this possible ? If yes, will this affect the eficiency of compression ? Or x264 will somehow wait for the signpost to get the frames requested ?
But in order for x264 to get frames 321 to 352, first Premiere Pro or Vegas Pro must render them, then debugmode must write them to hdd as uncompressed avi. And at the same time, the CPU is used by the NLE for rendering, by avisynth for filtering, and by x264 for encoding.
What if x264 needs frames 321 to 352 but doesn't get them all exactly when x264 needs them ? Is this possible ? If yes, will this affect the eficiency of compression ? Or x264 will somehow wait for the signpost to get the frames requested ?