Le 19/11/2017 à 8:28 PM, Michael Niedermayer a écrit :
On Sun, Nov 19, 2017 at 11:01:37AM +0100, pkv.stream wrote:
[...]
@@ -3674,6 +3697,10 @@ const OptionDef options[] = {
{ "channel_layout", OPT_AUDIO | HAS_ARG | OPT_EXPERT | OPT_PERFILE |
OPT_INPUT | OPT_OUTPUT,
{ .func_arg = opt_channel_layout },
"set channel layout", "layout" },
+ { "channel_layout_uint64", OPT_AUDIO | HAS_ARG | OPT_INT64 | OPT_SPEC |
i mean as "channel_layout"
does it work with both using the same name so the option is routed
to both the field and callback or am i missing something why this is
not intended?
I assumed options in the same OptionDef should have unique names (seems
to be the case at the moment).
I've just tried what you suggest but there are errors parsing and
writing the option when the channel layout is specified as a string
(quad, octagonal, hexadecagonal ...)
In opt_channel_layout, the function parse_option assumes the first
channel_layout option (non Spec), while we need the second one. So this
generates errors.
If the order of the options is reversed, the string is not recognized
any more.
Maybe it can be done with some more work. I don't really know. Tell me
if you want me to investigate this some more.
Thanks.
[...]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
