Andrey Semashev (2018-11-29): > It does. avformat_open_input, avio_open and ffurl_open[_whitelist] docs all > say it's an URL and they don't perform any conversion. So the file backend > should be prepared to receive a URL, with a scheme and authority.
So either the docs are slightly wrong or the code is. Do you have an argument to decide it is one rather than the other? I do: > It will probably currently fail because of the escape sequence. Exactly. Since escaping, a very basic feature of URIs, is not handled at all, it is a clear indication that the paths are NOT meant to be considered URIs. The documentation was added much later, and made the same mistake you are doing now; same goes for a few private function names. > Escape sequences, if needed, can be fixed separately. That would break a lot of working applications and is therefore not a good idea. Regards, -- Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel