> Right now the way that I am using testMPEG2TransportReceiver is by first > running testMPEG2TransportStreamer on a server side and run > testMPEG2TransportReceiver on the client side. It spits out on the stdout the > stream in test.ts with no RTP headers. That works fine! > In my environment, the WIFI Display server generates a stream that contains > RTP headers and TS data. The WIFI Display client is expecting a stream with > no RTP headers. So I am thinking of using the testMPEG2TransportReceiver code > to extract/stream out the RTP headers before the WIFI Display client consumes > the stream. Is that possible?
Yes of course. You can just change the "testMPEG2TransportReceiver" code to use a different multicast address/port, or (perhaps) to receive via unicast instead of multicast. See <http://www.live555.com/liveMedia/faq.html#unicast> 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
