> I tested the testProgs/testOnDemandRTSPServer. It does not have the odd
> port for RTCP, (i.e only 1234 port is open).
OK, I misunderstood your question. I thought you were asking about the
*output* from the RTSP server.
But yes, you're right. We should really be creating a "RTCPInsta
Ross,
I tested the testProgs/testOnDemandRTSPServer. It does not have the odd port
for RTCP, (i.e only 1234 port is open). Did I missed anything?
Regards,
Lan Zang(Sander)
From: Ross Finlayson
To: LIVE555 Streaming Media - development & use
Sent: Sunday, Fe
> I am trying to use the codes of stream
> "mpeg2TransportStreamFromUDPSourceTest" of testProgs/testOnDemandRTSPServer
> to read from a source which will send mpeg2ts over RTP, and the server do
> read data from RTP source, which is good. But I found that the RTSPServer has
> not a RTCP p
First, you should *not* modify the existing
"H264VideoFileServerMediaSubsession" code. Instead, write your own
"OnDemandServerMediaSubsession" subclass, and use that instead. This is
explained very clearly in the FAQ.
> Perhaps I should tell you the actual problem!
Sorry, but I don't have t
Ross,
Thanks for the advice.
I found MF_H264_DeviceSource::deliverFrame() as well as an old trace
statement I put in it back on my successful cobble. This is in fact the
"deep inside" I was looking for, albeit having been called back from deep
inside and now back in my code. The trace is coming
Hi,
I am trying to use the codes of stream "mpeg2TransportStreamFromUDPSourceTest"
of testProgs/testOnDemandRTSPServer to read from a source which will send
mpeg2ts over RTP, and the server do read data from RTP source, which is good.
But I found that the RTSPServer has not a RTCP port. So, is
