On 03.11.2014 00:40, Stefano Sabatini wrote:
On date Sunday 2014-11-02 19:19:14 +0100, Lukasz Marek encoded:
TODO: bump micro
Many common codec options are not via ffm protocol.
This commit adds common A/V encoding options to protocol.
Signed-off-by: Lukasz Marek <lukasz.m.lu...@gmail.com>
---
libavformat/ffmdec.c | 78 ++++++++++++++++++++++++++++++++++++++++++++++++++++
libavformat/ffmenc.c | 60 ++++++++++++++++++++++++++++++++++++++++
2 files changed, 138 insertions(+)
My idea was to let the protocol specify the option using the AVOption
interface. This way you don't have to update the protocol every time a
new option is added to libavcodec, *AND* you can support private codec
options.
>> (in near future I will add posibility to set them)
>
> I'm curious about that, since that was in my (much neglected) todo
> list. How do you plan to do that? The only way I see is to fiddle with
> FFM.
>
To not spam other thread with offtopic I moved your question here.
I'm not sure yet. In config I wanted to something like that:
VideoCodec libx264
#common options:
AVOptionVideo flags +global_header
#private option
AVOptionVideo libx264:crf 23
In ffm my first idea was to serialize it as strings in separate section.
I haven't really thought about it yet. Maybe serializing common options
would be also good idea. And send only set values.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
