On 5/30/2012 7:22 AM, Anthony Brown wrote:
rewriting main() to use stdin
would allow it to be used on the end of a pipe or redirection yes?
This much looks easy to do. The indexer gets its input data from a
ByteStreamFileSource, and one of its virtual ctors (createNew()) takes a
FILE* in
Hi,
I have an application that streams audio from a microphone to other
machines on the network via RTSP. Users control the stream with a
"Start" and "Stop" button. When making the first "call" the quality is
perfect (calls start by clicking "start" and end by clicking "stop").
The second call
Is it possible to use MPEG2TransportStreamIndexer either reading from a
pipe (named or unnamed) or from stdin? A brief look at the source
suggests that a named pipe would work, unless seeking is used somewhere.
If it would work from a named pipe then rewriting main() to use stdin
would allow
> I have tested one of my camera with live 555 for RTSP over http.
> But i face some problem on RTCP side.
> The "RR" packet was sent over GET side not on the POST side.
> Also i have varified this on wireshardk.
> Because of that problem server stops sending data after session time out.
You have
Hello Ross,
does it mean that we don't have any means to handle tool-low-bandwidth
network case? I can imagine for instance for the live view the following
scenario - we monitor the output queue length and when it's overflown or
close to the top - start to skip all incoming frames till the next k
