From: Lynne via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: Dmitrii Ovchinnikov <ovchinnikov.dmitrii@gmail.com>, FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Lynne <dev@lynne.ee> Subject: Re: [FFmpeg-devel] [PATCH 01/10, v3] avutil: add hwcontext_amf. Date: Thu, 30 May 2024 18:48:59 +0200 Message-ID: <c5703892-73d0-4fd5-b250-c282455cd901@lynne.ee> (raw) In-Reply-To: <CADXbNkQsV=1Q-GSH8j_wsjeWUD0rgdkDvjxt1R4we3jzVRof_A@mail.gmail.com> [-- Attachment #1.1.1.1: Type: text/plain, Size: 1313 bytes --] On 30/05/2024 18:06, Dmitrii Ovchinnikov wrote: > DX12 and Vulkan native encoders will expose less features compare to > AMF,____ > > at least in foreseeable feature. The missing features include low > latency,____ That's plainly not true. > PreAnalysis including look-ahead etc. AMF context on Windows allows > fully____ > > enable SAV - ability to utilize VCNs in dGPU and APU in a single > session.____ You should try talking internally to learn what is in progress. > AMF components including encoder and decoder has some internal > optimizations ____ > > in the area of memory access for APUs that are not available in standard > ____ > > 3D APIs.____ This isn't OpenGL. > Eventually specialized multimedia AMD cards could be added seamlessly to____ > > FFmpeg with AMF integration.____ > > AMF FSR(VSR) includes YUV version with focus on videos which is not____ > > available in AMD FSR aimed for gaming.____ Why don't you open source it then? > More advanced filters that are not available in standard 3D APIs are > coming. __ We could have them as Vulkan filters. I'm not objecting on this patch, but I am concerned that it's more proprietary code which is soon going to be redundant. I will have to review it properly at some point. [-- Attachment #1.1.1.2: OpenPGP public key --] [-- Type: application/pgp-keys, Size: 637 bytes --] [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 236 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-05-30 16:49 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-30 13:08 Dmitrii Ovchinnikov 2024-05-30 13:08 ` [FFmpeg-devel] [PATCH 02/10, v3] avcodec: add amfdec Dmitrii Ovchinnikov 2024-06-04 19:25 ` Mark Thompson 2024-05-30 13:08 ` [FFmpeg-devel] [PATCH 03/10, v3] avcodec/amfenc: Fixes the color information in the output Dmitrii Ovchinnikov 2024-05-30 13:08 ` [FFmpeg-devel] [PATCH 04/10, v3] avcodec/amfenc: HDR metadata Dmitrii Ovchinnikov 2024-05-30 13:08 ` [FFmpeg-devel] [PATCH 05/10, v3] avcodec/amfenc: add 10 bit encoding in av1_amf Dmitrii Ovchinnikov 2024-05-30 13:08 ` [FFmpeg-devel] [PATCH 06/10, v3] avcodec/amfenc: GPU driver version check Dmitrii Ovchinnikov 2024-05-30 13:08 ` [FFmpeg-devel] [PATCH 07/10, v3] avcodec/amfenc: add smart access video option Dmitrii Ovchinnikov 2024-05-30 13:08 ` [FFmpeg-devel] [PATCH 08/10, v3] avcodec/amfenc: redesign to use hwcontext_amf Dmitrii Ovchinnikov 2024-05-30 13:08 ` [FFmpeg-devel] [PATCH 09/10, v3] avfilter/scale_amf: Add AMF VPP & super resolution filters Dmitrii Ovchinnikov 2024-05-30 13:08 ` [FFmpeg-devel] [PATCH 10/10, v3] doc/filters: Add documentation for AMF filters Dmitrii Ovchinnikov 2024-05-30 14:04 ` [FFmpeg-devel] [PATCH 01/10, v3] avutil: add hwcontext_amf Andreas Rheinhardt 2024-05-30 14:34 ` Lynne via ffmpeg-devel 2024-05-30 16:06 ` Dmitrii Ovchinnikov 2024-05-30 16:48 ` Lynne via ffmpeg-devel [this message] 2024-05-30 19:51 ` Dmitrii Ovchinnikov 2024-06-04 18:58 ` Mark Thompson
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=c5703892-73d0-4fd5-b250-c282455cd901@lynne.ee \ --to=ffmpeg-devel@ffmpeg.org \ --cc=dev@lynne.ee \ --cc=ovchinnikov.dmitrii@gmail.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git