I have tried second approach. I ran openRTSP with -b 40000 -r -v rtsp:<host>/media but it doesnt seems to be working. Anyway I will keep this as a fall back mechanishm. I would like to know more about creating a subclass of MediaSink, could you please elaborate more on this.
On Tue, Dec 1, 2009 at 12:16 PM, Ross Finlayson <finlay...@live555.com>wrote: > I believe it is possible to have the streams in buffer but not clear how? I >> went through RTPSource class which has a function pointer >> setAuxilliaryReadHandler(). As I understand this is for registering a >> handler for processing RTP read. >> > > "setAuxilliaryReadHandler()" is a hack that should not be used. I don't > think anyone uses it anymore, and it will likely be removed from a future > release of the code. In any case, it provides access to raw RTP packets > (i.e., including RTP headers) - and that's *not* what you want. > > > > After long discussion and research we had decided to make use of live555 >> stack as it is widely used (and tested). I have gone through the >> openRTSP.cpp which actually saves all the streams to a file. I do not want >> to record streams in a file and read from the file as this will have >> latency. >> > > OK, then your solution is straightforward. You need to write your own > subclass of "MediaSink" that does whatever you want to do with the incoming > data, and use that *instead of* "FileSink". > > (Or, if your incoming stream is video-only (or audio-only), then you could > use the "-v" (or "-a") option to "openRTSP", and pipe it into a separate > application (that reads from stdin) that processes it.) > > -- > > 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
