On Mon, Jun 27, 2016 at 02:28:16PM +0100, Mark Thompson wrote:
> On 26/06/16 23:49, Michael Niedermayer wrote:
> > On Tue, Jun 07, 2016 at 07:51:18PM +0100, Mark Thompson wrote:
> >> Fixes ticket 5286.
> >>
> >> Uses the global -hwaccel_lax_profile_check option (may be misnamed
> >> for this purpos
Hendrik Leppkes gmail.com> writes:
> > We need a patch that changes the default to "no check
> > of level".
>
> Changing the default is unrelated to offering an option
> to override, and another discussion entirely.
It may be another discussion, it certainly is the most
relevant discussion of
On Mon, Jun 27, 2016 at 5:06 PM, Carl Eugen Hoyos wrote:
> Michael Niedermayer niedermayer.cc> writes:
>
>> is anyone against applying this ?
>
> As explained by Philip, this patch is not ok:
> We need a patch that changes the default to "no check
> of level".
>
Changing the default is unrelated
Michael Niedermayer niedermayer.cc> writes:
> is anyone against applying this ?
As explained by Philip, this patch is not ok:
We need a patch that changes the default to "no check
of level".
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmp
On 26/06/16 23:49, Michael Niedermayer wrote:
> On Tue, Jun 07, 2016 at 07:51:18PM +0100, Mark Thompson wrote:
>> Fixes ticket 5286.
>>
>> Uses the global -hwaccel_lax_profile_check option (may be misnamed
>> for this purpose, but it has the right spirit).
>> ---
>> Only compile tested (no hardware
Michael Niedermayer wrote:
On Tue, Jun 07, 2016 at 07:51:18PM +0100, Mark Thompson wrote:
Fixes ticket 5286.
Uses the global -hwaccel_lax_profile_check option (may be misnamed
for this purpose, but it has the right spirit).
---
Only compile tested (no hardware).
Maybe -hwaccel_lax_profile_chec
On Tue, Jun 07, 2016 at 07:51:18PM +0100, Mark Thompson wrote:
> Fixes ticket 5286.
>
> Uses the global -hwaccel_lax_profile_check option (may be misnamed
> for this purpose, but it has the right spirit).
> ---
> Only compile tested (no hardware).
>
> Maybe -hwaccel_lax_profile_check should be re
On 2016-06-08 21:54, Mark Thompson wrote:
On 08/06/16 13:59, Carl Eugen Hoyos wrote:
Mark Thompson jkqxz.net> writes:
Uses the global -hwaccel_lax_profile_check option (may be
misnamed for this purpose, but it has the right spirit).
Iirc, all old x264 files have a very high profile set (5.0
Mark Thompson jkqxz.net> writes:
> The point here is that the driver has declared its
> capabilities, and the given stream is not within those
> capabilities so the hwaccel should not be used because
> it will not work
Can you explain how it "will not work"?
On my nvidia hardware, any level c
On 08/06/16 13:59, Carl Eugen Hoyos wrote:
> Mark Thompson jkqxz.net> writes:
>
>> Uses the global -hwaccel_lax_profile_check option (may be
>> misnamed for this purpose, but it has the right spirit).
>
> Iirc, all old x264 files have a very high profile set (5.0?).
> Is there a usecase for the
Mark Thompson jkqxz.net> writes:
> Uses the global -hwaccel_lax_profile_check option (may be
> misnamed for this purpose, but it has the right spirit).
Iirc, all old x264 files have a very high profile set (5.0?).
Is there a usecase for the default not being to accept any
profile?
Carl Eugen
Fixes ticket 5286.
Uses the global -hwaccel_lax_profile_check option (may be misnamed
for this purpose, but it has the right spirit).
---
Only compile tested (no hardware).
Maybe -hwaccel_lax_profile_check should be renamed to something a bit more
general - it was named for the specific VAAPI ca
12 matches
Mail list logo
