> > Though passing the data through stdin is ugly solution > I don?t think it?s ugly at all. In fact, it?s quite clean, because it uses > familiar Unix I/O stdio and pipes, rather than requiring extra programming.
Returning to the stdout->stdin approach: the same SPS/PPS problem is present here too. We have the H264 SIP RTP subsession without any sprops, so call to subsession->fmtp_spropparametersets() is useless in playSIP : ... fileSink = H264VideoFileSink::(outFileName, subsession->fmtp_spropparametersets(), fileSinkBufferSize, oneFilePerFrame); subsession->sink = fileSink; subsession->sink->startPlaying(*(subsession->readSource()), subsessionAfterPlaying, subsession); ... How to make the subsession->fmtp_spropparametersets() returns something usefull in playSIP for SIP H264 RTP ? TIA, Rus > > > - this is the > > first thing I've tried, but it do not works too. The main issue as I see > > is that playSIP outputs the buggy (just two 00000001) raw h264 if the > > sprop-parameter-sets is not presenet in SDP but the testOnDemandRTSPServer > > always expects byte-stream h264 format. The SIP servers ususally do > > not / never supply the sprop-parameter-sets but the profile-level-id > > fmtp entry only. > > > > Is there a way to fix this and make at least stdin approach to work with > > SIP ? > > If you know the SPS and PPS NAL units ahead of time, then you can add them as > (otherwise optional) parameters to the call to > ?H264VideoRTPSink::createNew()? in ?playCommon.cpp?. > > > Ross Finlayson > Live Networks, Inc. > http://www.live555.com/ > > > _______________________________________________ > live-devel mailing list > live-devel@lists.live555.com > http://lists.live555.com/mailman/listinfo/live-devel > _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel