Okay, I did some more testing of the problem.
Step one: I set the max_key_interval in the encoder to 25 (one per second
and current fps). Xvid sends a Bitstream header with each keyframe, so the
streamer shouldn't have to wait for more than a second max for that
information.
Step two: I wrote a
Chris,
I've gotten a very similar pipe thing working. Ross was invaluable in
helping. Here are two points you may need to recall, to finally get it
working properly.
This advice relates to using H.264. It may only partially relate to your
application.
1) You must make sure that you're sending
> As far as Windows developers who use gmail...I can understand the
> anti-windows sentiment, but I don't know what you have against gmail...
This is explained clearly in the FAQ (that everyone was asked to read before
posting to the mailing list :-)
> And I code in Windows because I'm paid to
Yes, the encoder is another process (which is in turn reading raw frames
from yet another process). I'll test my pipe code in the encoder; I'm
doing it differently from in the 3D program going to the encoder.
As far as Windows developers who use gmail...I can understand the
anti-windows sentiment
> My question is this: can I safely undefine READ_FROM_FILES_SYNCHRONOUSLY
NO! You should not modify the supplied source code. (Windows developers who
use "@gmail.com" email addresses should especially not modify the supplied
source code :-)
The whole point of this code is that, in Windows, r
