Dear Ross,
> The call to Medium::close(subsession->sink);
> in "subsessionAfterPlaying()" should be causing
> AMRDeinterleaver::doStopGettingFrames()
> to get called, and that should in turn be stopping the reception (and
> thus handling) of any more AMR/RTP packets.
Actually, the call to AMRDei
Hi,
Im very interested :) i need for my phd thesis to do an streaming of SVC RTP
multisession, for that i need the LIVE555 library to do SVC RTP (MST).
best regards
Joao
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live5
Re: [Live-devel] RTSPClient::fBaseURL and RTSPClient::sessHi Ross,
Many thanks for getting back.
A short word about application I'm writing. It is intended to run for
indefinitely long time, until the end user shuts it down manually. Most of time
it is going to be awaiting for some specific eve
Using separate RTSPClient objects - that's exacty I'm going to do.
Ok, seems I have found a solution: RTSPClient class is derived from
Medium class and there is Medium::name() available which returns
unique value.
Alternatively, you could subclass "RTSPClient", and store your
information in f
