Opened 6 years ago
Closed 6 years ago
#7739 closed defect (fixed)
Explain stream specifier usage for codec and other global options
Reported by: | Ulf Zibis | Owned by: | Gyan |
---|---|---|---|
Priority: | minor | Component: | documentation |
Version: | git-master | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
Summary of the bug:
At https://www.ffmpeg.org/ffmpeg-codecs.html#Codec-Options there is no hint that options should be postfixed by a stream specifier in case of ambiguity. An example would be helpful too.
At https://www.ffmpeg.org/ffmpeg.html#AVOptions the given example doesn't reflect the statement: "... a stream specifier should be attached ...", so "... in case of ambiguity" should be amended.
For https://ffmpeg.org/ffmpeg-formats.html#Format-Options the same applies.
How to reproduce:
% ffmpeg -i input -level:a 5 output # avoid ambiguity with video codec level ffmpeg version: current
Change History (3)
comment:1 by , 6 years ago
Priority: | normal → minor |
---|---|
Version: | unspecified → git-master |
comment:2 by , 6 years ago
Owner: | set to |
---|---|
Status: | new → open |
comment:3 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | open → closed |
Example added in a9452fe6dc2ecf5b2249aae6d770655095b4e232
Note:
See TracTickets
for help on using tickets.
That example applies a format option. I'll add a new example for codec options.