> I have to integrate live555 RTSP client into an existing application
> that decodes H.264 video and sends it to display. The application
> is multithreaded, with separate threads for decoding and display
> tasks.
>
> I was thinking of using testRTSPClient code as a base, putting
> it into separ
On 6/2/2012 12:55 AM, Ross Finlayson wrote:
the command
genMakefiles freebsd
should be putting this space character in the Makefiles OK.
Sure, but that doesn't fix the fact that BSD make will strip them right
back out. I think that's what the OP has run into.
I said it before in this threa
Hi Ross,
x-dimensions header is required to work with resolutions > 2048. I saw
some devices which relied on it for megapixel streaming (IIRC they just
sent lower bits in standard JPEG over RTP header) and liveMedia handled
this correctly if the header present.
Regards,
Yuri
On 04.06.2012 1
I suppose that if you did TS over RTP that might work, it's a pretty
inefficent way of streaming.
Typically RTSP splits each stream of data into it's own RTP stream,
however I had forgotten that people do stream TS directly over RTP
without demuxing it first. I don't know what the status of Live
My limited understanding of KLV is that it is muxed into the Transport Stream.
So if I understand it correctly would it not just be passed along as part of
the stream with the rest of the TS video information through the Live555
Dynamic RTSP server and onto the client to handle Demuxing the KLV
> I work with live555 and stream H264 coded video via RTP. I need force IDR
> frame on encoder when each new client connected to my RTSP server.
>
> Please let me know how I can to do it – what is best way (on server side) in
> live555 to detect client connection / disconnection to my RTSP serve
> After the RTSP connection IP-based cameras to send a reply with the
> line "a=x-dimensions:640,480", but when you connect to LIVE555 Proxy
> Server, this line is missing. For some decoders need to know the width
> and height, and this is a problem.
A camera should not depend upon its server incl
I believe the answer is it won't handle it at all.
Last time I checked the KLV profile for RTP (IETF draft status) had not
been accepted as a standard and I don't think it's all that interesting
outside of the MISB standards body so no effort has been made to make
it a part of this library.
Yo
