[AMD Official Use Only - AMD Internal Distribution Only]
> Why yet another crappy hardware API? There is a million of those.
> Why yet another crappy special snowflake hardware decoder? We have more of
> those than we want (which is 0).
>
> As Mark has also previously commented, the hwcontext impl
I am OK with Alex Kravchenko taking the official ownership of AMF integration.
I am still involved in AMD AMF implementation and monitor FFmpeg changes.
Mikhail Mironov
From: ffmpeg-devel on behalf of Alexander
Kravchenko
Sent: Wednesday, July 3, 2019 6:53 PM
To: ffmpeg-devel@ffmpeg.o
: ffmpeg-devel on behalf of James
Courtier-Dutton
Sent: Sunday, December 9, 2018 7:04:55 PM
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] AMD Vega 56, UVD and OpenCL
On Sun, 9 Dec 2018 at 23:21, Mironov, Mikhail
wrote:
> There is one potential way to do it:
> Decode
There is one potential way to do it:
Decode using AMF on Vulkan, then Vulkan has interop to OpenGL and OpenGL has
interop to OpenCL.
AMF on Vulkan on Linux was released (decoder and encoder).
To integrate it to FFmpeg we need FFmpeg AMF context committed. It is waiting
for Mark to commit for qui
Behalf Of
> Mironov, Mikhail
> Sent: November 29, 2018 10:52 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [INFO]AMD D3D11 to OpenCL interop extension
> for NV12 and P010 textures - split planes
>
> HI,
> I've wro
hompson
> Sent: November 27, 2018 7:05 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [INFO]AMD D3D11 to OpenCL interop extension
> for NV12 and P010 textures - split planes
>
> On 26/11/2018 15:32, Mironov, Mikhail wrote:
> > You assume that device ID returne
n Behalf Of
> Mark Thompson
> Sent: November 25, 2018 5:22 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [INFO]AMD D3D11 to OpenCL interop extension
> for NV12 and P010 textures - split planes
>
> On 25/11/2018 21:28, Mironov, Mikhail wrote:
> > It s
3D11 to OpenCL interop extension
> for NV12 and P010 textures - split planes
>
> On 24/05/2018 15:26, Mironov, Mikhail wrote:
> > AMD has published OpenCL extension which allows split D3D11 texture
> interoped as a single 2D image into two 2D images representing Y and UV
>
Subject: Re: [FFmpeg-devel] [INFO]AMD D3D11 to OpenCL interop
> > extension for NV12 and P010 textures - split planes
> >
> > On 27/05/18 07:57, Alexander Kravchenko wrote:
> > > сб, 26 мая 2018 г. в 19:45, Mark Thompson :
> > >
> > >> On 24/05/18 15:26,
AMD has published OpenCL extension which allows split D3D11 texture interoped
as a single 2D image into two 2D images representing Y and UV planes.
https://www.khronos.org/registry/OpenCL/extensions/amd/cl_amd_planar_yuv.txt
Mikhail
___
ffmpeg-devel mai
> -Original Message-
> From: James Almer [mailto:jamr...@gmail.com]
> Sent: January 28, 2018 6:32 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Mironov, Mikhail
> Subject: Re: [FFmpeg-devel] [PATCH] Add HW H.264 and HEVC encoding for
> AMD GPUs based on AMF SDK
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: January 23, 2018 10:50 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [RFC] amfenc: Add support for OpenCL input
>
> On 23/01/18
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: January 23, 2018 10:41 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [RFC] amfenc: Add support for OpenCL input
>
> On 23/01/18
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: January 23, 2018 10:21 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [RFC] amfenc: Add support for OpenCL input
>
> On 23/01/18
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: January 23, 2018 10:21 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [RFC] amfenc: Add support for OpenCL input
>
> On 23/01/18
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mironov, Mikhail
> Sent: January 23, 2018 10:04 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [RFC] amfenc: Add sup
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: January 22, 2018 6:57 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: [FFmpeg-devel] [RFC] amfenc: Add support for OpenCL input
>
> ---
From: ffmpeg-devel on behalf of Compn
Sent: Friday, December 15, 2017 9:27 AM
To: FFmpeg development discussions and patches
Subject: Re: [FFmpeg-devel] AMD external header
On Fri, 15 Dec 2017 00:31:27 +, "Mironov, Mikhail"
wrote:
> Do you t
n Wed, 29 Nov 2017 15:45:28 +, "Mironov, Mikhail"
> wrote:
> > May I suggest to go down to business of enabling HW encoders by default?
> > Yesterday Mark submitted the initial implementation and I really want
> > to thank him for his mentoring and participation
Moved bitrate parameters set before Init() call because bitrate is used in
profile level correction code inside Init().
Signed-off-by: Mikhail Mironov
---
libavcodec/amfenc_h264.c | 10 +-
libavcodec/amfenc_hevc.c | 8
2 files changed, 9 insertions(+), 9 deletions(-)
diff --g
n Wed, 29 Nov 2017 18:06:46 +, "Mironov, Mikhail"
> wrote:
>
> > This was a suggestion in one of the posts, not my idea. I personally would
> prefer to include headers.
>
> i also prefer including headers into ffmpeg. only for the big 3 intel amd and
> nvidi
>
> It also should be made clear that nvidia does not somehow receive preferred
> treatment over other vendors.
Respectfully, but it does by inaction.
Thanks,
Mikhail
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listi
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of wm4
> Sent: November 29, 2017 11:06 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] AMD external header
>
> On Wed, 29 Nov 2017 15:45:28 +
>
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Paul B Mahol
> Sent: November 29, 2017 10:16 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] AMD external header
>
> On 11/29/17, Carl Euge
>
> > +{ AV_PIX_FMT_D3D11, AMF_SURFACE_NV12 },
>
> Wut, really? It's not a typo? It looks tricky.
>
> I assume AMF has D3D11 input, but then it'd still need to exclude P010.
> I don't think this is ever done, and sending a P010 frame probably
> crashes the thing?
>
> > +};
There is a
>
> Pavel Koshevoy (2017-11-27):
> > That is unnecessarily un-diplomatic and will likely offend the
> > contributors from nvidia and amd.
>
> Well, I find offensive that they benefit from my work yet make extra efforts
> to make sure I cannot benefit from theirs. Maybe I should start putting my
>
> Ok; done, plus some trivial testing to make sure it works. If you're happy
> with this and noone else says anything then I'll push it tomorrow.
OK.
> Relatedly: your name on patches does not match your full name - I've
> preserved the patch one here, but was that intended?
No, it was how
AMF SDK
>
> On 27/11/17 23:34, Mironov, Mikhail wrote:
> >> -Original Message-
> >> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
> Behalf
> >> Of Mark Thompson
> >> Sent: November 27, 2017 6:25 PM
> >> To: ffmpeg-deve
AMF SDK
>
> On 27/11/17 22:35, Mironov, Mikhail wrote:
> >>> -Original Message-
> >>> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
> >>> Behalf Of Mark Thompson
> >>> Sent: November 27, 2017 3:11 PM
> >>&
> > -Original Message-
> > From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> > Of Mark Thompson
> > Sent: November 27, 2017 3:11 PM
> > To: FFmpeg development discussions and patches > de...@ffmpeg.org>
> > Subject: [FFmpeg-devel] [PATCH] Add HW H.264 and HEVC encodin
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: November 27, 2017 3:11 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: [FFmpeg-devel] [PATCH] Add HW H.264 and HEVC encoding for AMD
> GP
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Timo Rothenpieler
> Sent: November 27, 2017 5:08 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] AMD external header
>
> Am 27.11.2017 um 03:15 schrieb
> >
> > I also noticed that recently there is a lot of activity to add full Nvidia
> decoders to FFmpeg (VC1, MPEG4, VP8, VP9 etc.).
> > I am guessing this is to overcome DXVA or VAAPI shortcoming. What about
> AMD? We also have them.
> >
> >
>
> DXVA2/D3D11VA work perfectly fine, on Windows i se
HEVC encoding for AMD
> GPUs based on AMF SDK
>
> 2017-11-27 4:06 GMT+01:00 Mironov, Mikhail
> :
>
> > I think as a side affect we can help integrate Vulkan acceleration to
> > FFmpeg.
> > It is much better then OpenCL for multimedia from performance
> perspecti
>
> Nobody is against adding AMD specific encoders and hwaccels. The issue for
> some seems to be the inclusion of external headers.
>
> Currently, nothing in our policy is against it, and as I and Philip already
> stated, your additions shouldn't be gated on a potential future policy change
> ab
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: November 26, 2017 9:57 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added HW H.264 and HEVC encoding for AMD
> G
>
> 2017-11-27 3:32 GMT+01:00 Mironov, Mikhail
> :
> >> -Original Message-
> >> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
> Behalf
> >> Of Carl Eugen Hoyos
>
> >> Also, imo you have not really explained which users would
>
> 2017-11-27 3:15 GMT+01:00 Mironov, Mikhail
> :
>
> > I will skip all arguments, you already read them.
>
> That's great, but I believe you forgot to add the fourth option.
I just wanted to start a discussion. Please state what is fourth option?
Though, I put it a
>
> A few minor fixups below. I would be happy to apply this if it didn't contain
> the external header.
>
> Thanks,
>
> - Mark
>
>
I will resubmit the changes you mentioned.
As of header inclusion issue I've sent a separate email.
Thanks,
Mikhail
_
Hi,
I would like to summarize thoughts on several threads on this forum related
to the issue of including AMD/AMF header file into FFmpeg source tree.
It looks like they reflect some policies formal or informal.
Mark tried to create some policy regarding this issue but wasn't successful.
I belie
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Timo Rothenpieler
> Sent: November 22, 2017 5:36 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Added HW H.264 and HEVC encoding for AMD
> GPUs based on AMF SDK
>
> Am 17.11.20
K
>
> On 21/11/17 23:08, Timo Rothenpieler wrote:
> > Am 21.11.2017 um 16:32 schrieb Mironov, Mikhail:
> >>
> >> Are you all busy right now? Any hint on timing?
> >> Thanks,
> >> Mikhail
> >
> > I cannot test this patch due to lack of
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Are you all busy right now? Any hint on timing?
Thanks,
Mikhail
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listin
K
>
> On 14/11/17 22:10, Mironov, Mikhail wrote:
> >> On 14/11/17 17:14, Mironov, Mikhail wrote:
> >>>>>>>>> +res = ctx->factory->pVtbl->CreateContext(ctx->factory,
> >>>>>>>>> + &ctx-
> >>&
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Hendrik Leppkes
> Sent: November 14, 2017 5:32 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added HW H.264 and HEVC encoding for AMD
> GP
> On 14/11/17 17:14, Mironov, Mikhail wrote:
> >>>>>>> +res = ctx->factory->pVtbl->CreateContext(ctx->factory,
> >>>>>>> + &ctx-
> >>>>> context);
> >>>>>>> +AMF_RET
> > +res = ctx->factory->pVtbl->CreateContext(ctx->factory, &ctx-
> >>> context);
> > +AMF_RETURN_IF_FALSE(ctx, res == AMF_OK,
> AVERROR_UNKNOWN,
> "CreateContext() failed with error %d\n", res);
> > +// try to reuse existing DX device
> > +if (avctx->hw_frames_
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mironov, Mikhail
> Sent: November 14, 2017 10:51 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added HW H.264 and
K
>
> On 13/11/17 23:00, Mironov, Mikhail wrote:
> >>> +res = ctx->factory->pVtbl->CreateContext(ctx->factory, &ctx-
> >context);
> >>> +AMF_RETURN_IF_FALSE(ctx, res == AMF_OK, AVERROR_UNKNOWN,
> >> "CreateContext() fai
> > +res = ctx->factory->pVtbl->CreateContext(ctx->factory, &ctx->context);
> > +AMF_RETURN_IF_FALSE(ctx, res == AMF_OK, AVERROR_UNKNOWN,
> "CreateContext() failed with error %d\n", res);
> > +// try to reuse existing DX device
> > +if (avctx->hw_frames_ctx) {
> > +AVHWFrame
> -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 accelerated H.264 and HEVC
> encodin
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Mark Thompson
> Sent: November 8, 2017 10:15 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] Added HW H.264 and HEVC encoding for AMD
> GPUs based on AMF SDK
>
> On 06/11/17 22:
> -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 accelerated H.264 and HEVC
> encodin
HEVC encoding for AMD
> GPUs based on AMF SDK
>
> On Tue, Nov 7, 2017 at 12:28 AM, Mironov, Mikhail
> wrote:
> >> -Original Message-
> >> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
> Behalf
> >> Of Michael Niedermayer
> >>
> theres no match for ID3D11VideoContext in my d3d11.h
> my mingw stuff should be just the official packages from
> ubuntu LTS 14.04
Then how would you compile hwcontext_d3d11va.h where ID3D11DeviceContext and
ID3D11VideoDevice are used?
Thanks,
Mikhail
__
HEVC encoding for AMD
> GPUs based on AMF SDK
>
> On Sun, Nov 05, 2017 at 02:41:54 +, Mironov, Mikhail wrote:
>
> > > > +{ "quality","", 0, AV_OPT_TYPE_CONST, { .i64 =
> > > AMF_VIDEO_ENCODER_HEVC_QUALITY_PRESET_QUALITY }, 0, 0, V
> > +//
> > +
> > +// Reduced AMF API
> > +//
> > +// Full version of AMF SDK and the latest version of this file
> > +// can be found at https://github.com/GPUOpen-LibrariesAndSDKs/AMF
>
> On further consideration I am against including this header. Just ask the
> user
> to get it from this lin
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of mmironov
> Sent: October 31, 2017 3:39 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: [FFmpeg-devel] Added HW H.264 and HEVC encoding for AMD GPUs
> based on AMF SDK
>
> From 8640b995634f827eb39a
coding for AMD
> GPUs based on AMF SDK
>
>
> On Tue, 31 Oct 2017, Mironov, Mikhail wrote:
>
> [...]
>
> >> I see some confusion. The user can call send_frame/receive_packet in
> >> any order, and you can implement send_frame and receive_packet any
> &g
> >>> +AMF_ASSIGN_PROPERTY_BOOL(res, ctx->encoder,
> >> AMF_VIDEO_ENCODER_HEVC_DE_BLOCKING_FILTER_DISABLE,
> >> deblocking_filter);
> >>
> >> What about SAO?
> >
> > SAO ???
>
> You're looking at AV_CODEC_FLAG_LOOP_FILTER to disable this, so you
> might want to consider both loop filters in H
coding for AMD
> GPUs based on AMF SDK
>
>
>
> On Mon, 30 Oct 2017, Mironov, Mikhail wrote:
>
> [...]
>
> >>>> I still think this would be much better off using the
> >>>> send_frame()/receive_packet() API. Even if your API doesn'
> >>> +
> >>> +int ff_amf_encode_frame(AVCodecContext *avctx, AVPacket *pkt,
> >>> +const AVFrame *frame, int *got_packet) {
> >>> +int ret = 0;
> >>> +AMF_RESULT res = AMF_OK;
> >>> +AmfContext *ctx = avctx->priv_data;
> >>> +AMFSurface
Mikhail
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On Behalf
> Of Carl Eugen Hoyos
> Sent: October 30, 2017 6:19 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Added HW H.264 and HEVC encoding f
> > +static void AMF_CDECL_CALL AMFTraceWriter_Write(AMFTraceWriter
> *pThis,
> > +const wchar_t *scope, const wchar_t *message)
> > +{
> > +AmfTraceWriter *tracer = (AmfTraceWriter*)pThis;
> > +av_log(tracer->avctx, AV_LOG_DEBUG, "%ls: %ls", scope, message);
>
> Does the message neces
GPUs based on AMF SDK
>
> 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
erated H.264 and HEVC
> encoding for AMD GPUs based on AMF SDK
>
> 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
GPUs based on AMF SDK
>
> On 29/10/17 14:54, Mironov, Mikhail wrote:
> >> -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: FF
GPUs based on AMF SDK
>
> 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(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
erated H.264 and HEVC
> encoding for AMD GPUs based on AMF SDK
>
> 2017-10-29 15:54 GMT+01:00 Mironov, Mikhail
> :
> >> -Original Message-
> >> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
> Behalf
> >> Of Carl Eugen Hoyos
> >>
> -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 GPUs based on AMF SDK
>
> On
> -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 accelerated H.264 and HEVC
> encod
> -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 accelerated H.264 and HEVC
> encodin
erated H.264 and HEVC
> encoding for AMD GPUs based on AMF SDK
>
> 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
> >
F SDK
>
> 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 defi
erated H.264 and HEVC
> encoding for AMD GPUs based on AMF SDK
>
> 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.)
>
> &
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 interfaces
into one header, though maintenance will take more resources.
77 matches
Mail list logo
