Thank you very much for taking the time to respond!
I hate JPEG streaming too, but the unfortunate part is we have a lot of
customers with investments with (old) MJPEG video encoders. It's a slow, but
eventual process in moving them to H264 encoders.
You are also 100% correct with your assessm
> I don’t like the idea of modifying the Live555 code and I don’t like changing
> things that were coded a certain way for a reason. I was wondering what the
> side effects may be and I was hoping someone may have any idea of what is
> going wrong (besides using Windows hehe) and if there was
First, I want to apologize for bringing up this list's favorite topics, Windows
Server and JPEG streaming. =)
Using the latest (10.24.2012) Live555, I was having an odd issue streaming JPEG
over TCP from any Windows Server 2003 box, even a Server 2003 VM running on the
same machine. I would on
can i change RTPInterface's implementation?
Of course you can. The code is Open Source, licensed under the LGPL.
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live5
dear friends.
can i change RTPInterface's implementation?
i saw RTPInterface was using like this.
class RTPSink: public MediaSink {
RTPInterface fRTPInterface;
};
any way to change it?
or i can't change it for some reason?
regards___
l
Thanks for the quick answer.
If the RTP-over-TCP data is well-formed, then there shouldn't be any
blocking, because the data should be present in the correct format:
'$';1-byte stream channel id; 2-byte packet size; packet data. Perhaps
the data that you are sending is not well-formed (though
I'm using livemedia to stream over TCP. In the RTPInterface file
there is a function tcpReadHandler() which handles all the data
received from the client (reports, commands, ...). This function
tries to read a '$' through a non-blocking call to readSocket().
Afterwards several more bytes are re
Hi.
I'm using livemedia to stream over TCP. In the RTPInterface file there
is a function tcpReadHandler() which handles all the data received from
the client (reports, commands, ...). This function tries to read a '$'
through a non-blocking call to readSocket(). Afterwards several more
bytes
