On Tue, Nov 1, 2011 at 3:33 PM, Martin Storsjö <[email protected]> wrote: > On Tue, 1 Nov 2011, Martin Storsjö wrote: > > It seems to work just fine for me, both for RTSP and for SDP. > > A general question is whether this is the right approach to solve the issue. > We've got AVStream discard flags, that convey the same thing, more or less, > and these are already used to choose which streams to receive for RealRTSP. > However, for that case, the rtsp demuxer would first have to configure and > set up receiving all streams (since none can be set to discarded until then > _open() function returns the control to the caller), and then if some of > them are undesired, some of the streams could be closed (can one close and > resetup streams in normal RTSP?). >
API-wise, I agree that would be a cleaner approach, but setting up and destroying the unwanted streams would be unacceptable. As Luca noted, it would require disproportionate effort to delay SETUP until after the application has a chance to reject streams. I had originally imagined an application-defined callback (providing what we know from the SDP), but that's a clunky API and I couldn't find any case that would justify the effort; all servers I've seen that provide multiple stream options use separate SDP paths. For the immediate use-case, I think this is the best approach. Thanks, - John _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
