> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: November 8, 2017 5:01 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added HW accel
2017-11-08 19:25 GMT+01:00 mmironov :
> Changelog|3 +-
> diff --git a/Changelog b/Changelog
> index 6592d86..f0d22fa 100644
> --- a/Changelog
> +++ b/Changelog
> @@ -6,7 +6,8 @@ version :
> - Dropped support for OpenJPEG versions 2.0 and below. Using OpenJPEG now
>require
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: November 7, 2017 4:44 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added HW accel
2017-11-07 17:17 GMT+01:00 mmironov :
> diff --git a/Changelog b/Changelog
> index 6592d86..f0d22fa 100644
> --- a/Changelog
> +++ b/Changelog
> @@ -6,7 +6,8 @@ version :
> - Dropped support for OpenJPEG versions 2.0 and below. Using OpenJPEG now
>requires 2.1 (or later) and pkg-config.
> -
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: October 29, 2017 5:51 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Added - HW accelerated H.264 and HEVC
> encoding for AMD
On 29/10/17 20:48, Mironov, Mikhail wrote:
>> -Original Message-
>> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
>> Of Mark Thompson
>> Sent: October 29, 2017 3:36 PM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-dev
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: October 29, 2017 5:01 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added - HW accel
2017-10-29 21:48 GMT+01:00 Mironov, Mikhail :
> VAAPI on Linux is available in open source driver. AMF version will be
> implemented via
> Vulkan and will follow Vulkan implementation in the driver and in open
> source policy.
Does that mean that at least in theory, the driver may also work on
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: October 29, 2017 3:49 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Added - HW accelerated H.264 and HEVC
> encoding for AMD
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: October 29, 2017 3:36 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Added - HW accelerated H.264 and HEVC
> encoding for AMD
mpeg.org>
>> Subject: Re: [FFmpeg-devel] Added - HW accelerated H.264 and HEVC
>> encoding for AMD GPUs based on AMF SDK
>>
>> 2017-10-27 20:09 GMT+02:00 mmironov :
>>> +const enum AVPixelFormat ff_amf_pix_fmts[] = {
>>> +AV_PIX_FMT_NV12,
>>
>
On 29/10/17 18:39, Mironov, Mikhail wrote:
>>> REGISTER_ENCODER(H263_V4L2M2M, h263_v4l2m2m);
>>> REGISTER_ENCDEC (LIBOPENH264, libopenh264);
>>> +REGISTER_ENCODER(H264_AMF, h264_amf);
>>> + REGISTER_ENCODER(H264_AMF, h264_amf_d3d11va);
>>
>> No tabs. Wh
> > REGISTER_ENCODER(H263_V4L2M2M, h263_v4l2m2m);
> > REGISTER_ENCDEC (LIBOPENH264, libopenh264);
> > +REGISTER_ENCODER(H264_AMF, h264_amf);
> > + REGISTER_ENCODER(H264_AMF, h264_amf_d3d11va);
>
> No tabs. Why is the d3d11 version separate? The encode
2017-10-29 16:43 GMT+01:00 Mironov, Mikhail :
>> >> > +const enum AVPixelFormat ff_amf_pix_fmts[] = {
>> >> > +AV_PIX_FMT_NV12,
>> >>
>> >> > +AV_PIX_FMT_BGRA,
>> >> > +AV_PIX_FMT_ARGB,
>> >> > +AV_PIX_FMT_RGBA,
>> >>
>> >> This is wrong, your encoders do not convert transparency i
; Sent: October 28, 2017 3:19 PM
> >> To: FFmpeg development discussions and patches >> de...@ffmpeg.org>
> >> Subject: Re: [FFmpeg-devel] Added - HW accelerated H.264 and HEVC
> >> encoding for AMD GPUs based on AMF SDK
> >>
> >
de...@ffmpeg.org>
>> Subject: Re: [FFmpeg-devel] Added - HW accelerated H.264 and HEVC
>> encoding for AMD GPUs based on AMF SDK
>>
>> 2017-10-27 20:09 GMT+02:00 mmironov :
>> > +const enum AVPixelFormat ff_amf_pix_fmts[] = {
>> > +AV_PIX_FMT_NV12,
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: October 28, 2017 5:29 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Added - HW accelerated H.264 and HEVC
> encoding for AMD
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: October 28, 2017 3:19 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added - HW accel
On 27/10/17 19:09, mmironov wrote:
> From b1b697aed459947cfa04bccdca0f7cfb5c8be72c Mon Sep 17 00:00:00 2001
> From: mmironov
> Date: Fri, 27 Oct 2017 13:03:15 -0400
> Subject: [PATCH] Added: HW accelerated H.264 and HEVC encoding for AMD GPUs
> based on AMF SDK
There isn't any sense in which thi
2017-10-27 20:09 GMT+02:00 mmironov :
> +const enum AVPixelFormat ff_amf_pix_fmts[] = {
> +AV_PIX_FMT_NV12,
> +AV_PIX_FMT_BGRA,
> +AV_PIX_FMT_ARGB,
> +AV_PIX_FMT_RGBA,
This is wrong, your encoders do not convert transparency
information, there are 32 rgb formats without alpha chan
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: October 26, 2017 6:32 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added HW accel
;> Sent: September 29, 2017 12:57 PM
> >> To: ffmpeg-devel@ffmpeg.org
> >> Subject: Re: [FFmpeg-devel] Added HW accelerated H.264 and HEVC
> >> encoding for AMD GPUs based on AMF SDK
> >>
> >> On Fri, 29 Sep 2017 15:04:00 +
> >> "Mironov, Mikh
On Fri, Oct 27, 2017 at 12:32 AM, Carl Eugen Hoyos wrote:
> 2017-10-26 23:58 GMT+02:00 Hendrik Leppkes :
>
>> 1) Is there a "need" to include the headers, so the feature can be used?
>>
>> Obviously this is a bit of a flexible argument, but if for example
>> headers are publicly and freely availab
2017-10-26 23:58 GMT+02:00 Hendrik Leppkes :
> 1) Is there a "need" to include the headers, so the feature can be used?
>
> Obviously this is a bit of a flexible argument, but if for example
> headers are publicly and freely available, or even packaged and
> distributed by linux distributions, the
On 26/10/17 19:03, Mironov, Mikhail wrote:
>> -Original Message-
>> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
>> Of wm4
>> Sent: September 29, 2017 12:57 PM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-devel]
On Thu, Oct 26, 2017 at 8:03 PM, Mironov, Mikhail
wrote:
>> -Original Message-
>> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
>> Of wm4
>> Sent: September 29, 2017 12:57 PM
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmp
On 2017-09-29 09:56, wm4 wrote:
On Fri, 29 Sep 2017 15:04:00 +
"Mironov, Mikhail" wrote:
I would like to understand better the nature of the concern. The
license is MIT. The paragraph in question is a notice, not limiting
the usage of the SDK.
I can definitely reduce number of headers. I
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of wm4
> Sent: September 29, 2017 12:57 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Added HW accelerated H.264 and HEVC
> encoding for AMD GPUs based on AM
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: September 29, 2017 11:47 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added HW accel
On Fri, 29 Sep 2017 15:04:00 +
"Mironov, Mikhail" wrote:
> I would like to understand better the nature of the concern. The license is
> MIT. The paragraph in question is a notice, not limiting the usage of the SDK.
> I can definitely reduce number of headers. I can merge all necessary
> in
2017-09-29 17:04 GMT+02:00 Mironov, Mikhail :
> I would like to understand better the nature of the
> concern. The license is MIT.
(I don't think this is correct, but see below.)
> The paragraph in question is a notice, not limiting
> the usage of the SDK.
I don't think this is true (I am not a
. Which way would
you prefer?
Thanks,
Mikhail
-Original Message-
From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf Of Carl
Eugen Hoyos
Sent: September 28, 2017 5:08 PM
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] Added HW accelerated H.264
2017-09-28 20:58 GMT+02:00 mmironov :
> +++ b/compat/amd/amf/LICENSE.txt
> @@ -0,0 +1,31 @@
> +Notice Regarding Standards. AMD does not provide a license or sublicense to
> +any Intellectual Property Rights relating to any standards, including but not
> +limited to any audio and/or video codec te
On Thu, 28 Sep 2017 13:58:02 -0500
mmironov wrote:
> From 4a47f0e1ee57239fbbc597c0084f486e815ec267 Mon Sep 17 00:00:00 2001
> From: mmironov
> Date: Thu, 28 Sep 2017 12:30:30 -0400
> Subject: [PATCH] Added HW accelerated H.264 and HEVC encoding for AMD GPUs
> based on AMF SDK
>
> Signed-off-by
34 matches
Mail list logo
