#6148 closed enhancement (fixed)
ffmpeg-protocols should say how to use options
Reported by: | Dan Jacobson | Owned by: | |
---|---|---|---|
Priority: | wish | Component: | documentation |
Version: | git-master | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
On the ffmpeg-protocols man page,
there are many
This protocol accepts the following options:
but no examples of how to use them on the command line.
Change History (4)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Priority: | normal → wish |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Type: | defect → enhancement |
Fixed in fb32c561c3820f3bc8833d0c3629388539fe4798.
comment:4 by , 8 years ago
This bug tracker isn't a user help resource, but you need to learn the basics first. Option placement matters: input options should be placed before the input. As it is, your example would apply to the output. See the synopsis:
http://ffmpeg.org/ffmpeg.html#Synopsis
So an example may look like:
ffmpeg -blocksize 1000 -i pipe:0 output.mkv
If you have further usage questions please ask the ffmpeg-user mailing list or visit the #ffmpeg IRC channel.
The user digs and digs
and only finds
something like ...?options.
But that might be only for URLs.
So he tries ?blocksize:11111 or is it blocksize=11111 who knows.
So he thinks maybe file:0?blocksize=11111 is not right or is it.