Re: [Live-devel] testOnDemandRTSPServer multicast question

2012-12-16 Thread Ross Finlayson
> I have just noticed something - when the first client connects, there is an > IGMP membership report issued to join the group I have specified for any > sources. > > However, when that first (and only) client tears down the session, there is > no IGMP membership report for the 'Leave'. That'

Re: [Live-devel] testOnDemandRTSPServer multicast question

2012-12-16 Thread Tim J Shackleton
On 17/12/12 12:18, Ross Finlayson wrote: If you do this, then, yes, the input source object will get closed (and its destructor called) whenever the last RTSP client leaves. This is the proper behavior, because we want the input source to be closed when noone is requesting its data. (Similarl

Re: [Live-devel] testOnDemandRTSPServer multicast question

2012-12-16 Thread Tim J Shackleton
On 17/12/12 12:18, Ross Finlayson wrote: Since the "testOnDemandRTSPServer" demonstrates how to stream from *files* to (unicast) clients, it does not 'demonstrate' multicast to unicast RTSP relaying at all. Therefore, you must have modified the supplied application's code in some (unspecified)

Re: [Live-devel] testOnDemandRTSPServer multicast question

2012-12-16 Thread Ross Finlayson
> I have been experimenting with a multicast to unicast RTSP relay, as > demonstrated in testOnDemandRTSPServer. Since the "testOnDemandRTSPServer" demonstrates how to stream from *files* to (unicast) clients, it does not 'demonstrate' multicast to unicast RTSP relaying at all. Therefore, you

[Live-devel] testOnDemandRTSPServer multicast question

2012-12-16 Thread Tim J Shackleton
Hi Ross, I have been experimenting with a multicast to unicast RTSP relay, as demonstrated in testOnDemandRTSPServer. A behaviour I have noticed, is that the first client connects and receives the stream correctly, and all subsequent connections do too - they can SETUP, PLAY and TEARDOWN to