Marton Balint (12021-03-21): > Same what I did with AVFormat->filename / AVFormat->url.
By the way, about that: at some point, we will need to clarify what part of our API uses real URLs and what parts uses fake URLs. Because as it is, a lot of code looks like it uses URLs but really it does not. The worst offender is "file:" it looks like an URL, the prefix is a 100% standard URL scheme. Yet, it will not find file:///home/user/Some%20Movie.mkv because it does not obey to the standard syntax of file:// URLs. I had the vague intent of proposing a migration path, but never time to work on it. It involves: 1. Introduce the fs: protocol as a synonym for file:. 2. For some time, detect if the behavior is likely to change in the next step and warn the user. 3. Detect file:// and treat it like a standard file:// URL, including skipping the server, query and fragment part and performing %-unescaping; keep file: without the double slash as an alias for fs:. 4. For some more time, warn users if they are using file: but not file://. 5. Remove the compatibility file: → fs: alias. Regards, -- Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
