[Live-devel] Re-streaming RTP as RAW-UDP multicast transported as MPEGTS

[Shyam Kaundinya]

Thank you for your response.

1/ Re: your response
Re: a
I just want to clear the air on the misunderstanding/miscommunication reg. modification of supplied code. I did not modify the supplied source code. I took testRTSPClient.cpp and made my own version of it, which follows the example of functions in H265VideoRTPSink namely createNew that calls fmtp_spropvps(),sps,pps and passes the output to  parseSPropParameterSets (the createNew in H265VideoRTPSink uses a fragment but, I don't/won't need that in my RTSPClient for parsingSPropParamSets is what I meant) and auxSDPLine for example of building the propset string (which from your explanation is no longer required). I am not using H265VideoRTPSink for anything else other than as an example reference code for use of spropvps, and parseSPropParameterSets functions that is recommended by the FAQ for decoding received data in RTSPclient : http://www.live555.com/liveMedia/faq.html#testRTSPClient-how-to-decode-data

Re: b
Noted. Thank you.


2/ Since I am sinking with UDP multicast, there is no concept of "a client establishing a connection. As such would I need to send out the prop-sets (VPS+SPS+PPS) before sending out every incoming frame or every i-frame or at some kind of interval as a background handler ?



3/ I was under the impression that I would need a container around RAW-UDP for that to be possible and hence chose to use a MPEGTS framer source. Sorry to have mischaracterized this on my earlier post. But, based on your responses so far, it appears that if I send out the prop-set stuff properly, I may not need the MPEGTS wrapper at all in order for a VLC client to be able to play it. Is my understanding correct ?



Regards

Shyam

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20180828/4778d9d9/attachment-0001.html>