https://bugs.winehq.org/show_bug.cgi?id=52769
--- Comment #7 from Nikolay Sivov bunglehead@gmail.com --- (In reply to yshuiv7 from comment #6)
(In reply to Nikolay Sivov from comment #5)
It's normally a property of the container to provide multiple streams, not the protocol. Same as a disk file having one video and multiple audio streams, still exposed as a single bytestream. Is that somehow different for rtsp? Do you mean it's impossible to create a bytestream object for rtsp url at all?
Yes. The server tells you what streams there are, and the client would (usually) establish separate connections for each stream.
https://datatracker.ietf.org/doc/html/rfc2326#page-5:
The Real-Time Streaming Protocol (RTSP) establishes and controls either a single or several time-synchronized streams of continuous media such as audio and video.
The question is how it's reflected in media foundation API, e.g. what data will be returned from bytestream created with CreateObjectFromURL("rtsp://..."), and if it's possible for application to configure which streams are requested.
Did you find an application that depends on this protocol handler? Except for ones that accept any url, including rtsp.
...
Starting with http/https is fine.
Is it worth it if we ended up using gstreamer for rtsp anyway?
I don't think we should be doing that.