#1529 closed enhancement (fixed)
easier access to (ex: libx264) presets available
Reported by: | Roger Pack | Owned by: | |
---|---|---|---|
Priority: | wish | Component: | avcodec |
Version: | git-master | Keywords: | x264 |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
Hello. Currently the "help" output refers one to the binary x264 (which may not be available, ex: on windows) for a list of presets. It would be convenient to have some way to enumerate them without needing a second executable.
ref: https://lists.ffmpeg.org/pipermail/ffmpeg-user/2012-June/007365.html
Or auto-add them to docu, etc.
Change History (6)
comment:1 by , 12 years ago
Keywords: | x264 added |
---|---|
Priority: | normal → wish |
Version: | unspecified → git-master |
comment:2 by , 12 years ago
comment:3 by , 12 years ago
Component: | undetermined → avcodec |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Afaict, this was fixed by Nicolas, please reopen if the solution is insufficient.
follow-up: 5 comment:4 by , 12 years ago
Thanks this is great!
A few minor additions that might be helpful:
Since there are some "file based" presets that aren't listed (https://github.com/FFmpeg/FFmpeg/tree/master/presets ) the output text might be better served as "Possible tunes (doesn't include external files):" or something like that.
Also a similar help output message for bad h264 profiles would be convenient, as well, but not necessary. Thanks!
comment:5 by , 12 years ago
Replying to rogerdpack:
Since there are some "file based" presets that aren't listed (https://github.com/FFmpeg/FFmpeg/tree/master/presets ) the output text might be better served as "Possible tunes (doesn't include external files):" or something like that.
I am afraid this is difficult: -vpre
and its presets is specific to the ffmpeg
command-line tool, while this error message comes from the library, and could appear in another application that does not have that kind of presets.
Also a similar help output message for bad h264 profiles would be convenient, as well, but not necessary. Thanks!
Patch for that posted:
http://ffmpeg.org/pipermail/ffmpeg-devel/2012-July/128463.html
It will be possible to fix your name in the commit message if you want until this is pushed in the official repository.
comment:6 by , 12 years ago
Ok that makes sense (changing the error message to say "Possible internal tunes" might still be a small improvement.
Patch looks great.
Thanks for doing that!
-roger-
In the laetst Git version, setting an invalid preset or tune will print the list:
Note that
help
orlist
are invalid, and thus will have that result.If this is acceptable to you, you can close the bug.