On Wed, Apr 01, 2015 at 05:32:04PM -0700, Philip Langdale wrote:
> On Thu, 2 Apr 2015 00:04:07 +0200
> Timo Rothenpieler wrote:
>
> > It was not possible to set a profile before, the builtin profile
> > parameter does not seem to work propperly.
> > To be compatible with libx264, this overlays i
On Thu, 2 Apr 2015 00:04:07 +0200
Timo Rothenpieler wrote:
> It was not possible to set a profile before, the builtin profile
> parameter does not seem to work propperly.
> To be compatible with libx264, this overlays it with a local parameter
> that expects a string, instead of an int, that tak
> Did you try to adding the FF_PROFILE_H264* and FF_PROFILE_HEVC* values to
> options_table.h?
> Currently it only has entries for aac, dts, mpeg2 and mpeg4.
While that would propably work, i'm more interested in staying
compatible with libx264 here, which accepts stuff like "-profile:v
high", wh
On Thu, Apr 2, 2015 at 12:08 AM, James Almer wrote:
> On 01/04/15 7:04 PM, Timo Rothenpieler wrote:
>> It was not possible to set a profile before, the builtin profile
>> parameter does not seem to work propperly.
>> To be compatible with libx264, this overlays it with a local parameter
>> that ex
On 01/04/15 7:04 PM, Timo Rothenpieler wrote:
> It was not possible to set a profile before, the builtin profile
> parameter does not seem to work propperly.
> To be compatible with libx264, this overlays it with a local parameter
> that expects a string, instead of an int, that takes the well know
It was not possible to set a profile before, the builtin profile
parameter does not seem to work propperly.
To be compatible with libx264, this overlays it with a local parameter
that expects a string, instead of an int, that takes the well known values
"high", "main" or "baseline".
---
libavcodec
