[FFmpeg-trac] #1253(FFmpeg:closed): FFMpeg don't handle files with some characters
FFmpeg
trac at avcodec.org
Sat Apr 28 10:42:24 CEST 2012
#1253: FFMpeg don't handle files with some characters
--------------------------------+--------------------------------------
Reporter: Uno | Owner:
Type: defect | Status: closed
Priority: normal | Component: FFmpeg
Version: 0.10.2 | Resolution: worksforme
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
--------------------------------+--------------------------------------
Comment (by Uno):
Replying to [comment:7 mjs973]:
> Replying to [comment:6 Uno]:
> > Replying to [comment:5 cehoyos]:
> > > Did you already test the following?
> > > $ ffmpeg -i file:hello\:goofy.avi
> >
> > It works! But shouldn't it work also without the "file:" prefix?
>
>
> No. In ffmpeg, a filename is structured like [protocol:]filename
>
> A protocol says how to interpret the filename which follows. Examples of
protocols are file:, pipe:, http:, udp: and rtp:. As a special case,
single letter protocols, like c:, are interpreted as a Windows drive
letter.
>
> So, in your example, ffmpeg was looking for a protocol named "hello:",
and when it couldn't find one by that name, it printed an error message.
>
I thought it should be that the reason, but shouldn't it answer: "hello:
wrong protocol" instead of "hello:goofy.avi: No such file or directory"?
Like this, is a quite confusing...
However I suggest to the developers to treat the unknown protocol as
probably file, so just then show an error message if missing!
Thanks for the explanation.
P.s.
Still a weird think: why does it works for "cehoyos"?
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1253#comment:8>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list