From: Lynne <dev@lynne.ee> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v3 2/2] fftools/ffplay: add hwaccel decoding support Date: Sun, 29 Oct 2023 04:18:32 +0100 (CET) Message-ID: <NhtRARW--3-9@lynne.ee> (raw) In-Reply-To: <tencent_FB359ADE40269AAF9F5AABC24E53700B2D08@qq.com> Oct 29, 2023, 03:31 by quinkblack@foxmail.com: > > On 2023/10/29 03:32, Lynne wrote: > >> Oct 28, 2023, 20:14 byquinkblack@foxmail.com: >> > > Fixed in patch v4. > > Maybe we should export optional_device_exts in API. > Patch welcome. >> >> Is there no option to let libavutil create the hwdevice for both SDL and libplacebo? >> That way, that code path can also be tested. >> > > libplacebo doesn't support that: > It does. It's how vf_libplacebo runs, and I also use it in my sample library (txproto). You should do it this way. > // Creates a new vulkan device based on the given parameters and initializes > // a new GPU. This function will internally initialize a VkDevice. There is > // currently no way to share a vulkan device with the caller. If `params` is > // left as NULL, it defaults to &pl_vulkan_default_params. > // > // Thread-safety: Safe > PL_API pl_vulkan pl_vulkan_create(pl_log log, const struct pl_vulkan_params *params); > > I think share instance or vkImage without support from vulkan spec is hard to implementation, > > if not impossible. > > https://www.yosoygames.com.ar/wp/2022/07/vulkan-integration-between-multiple-libraries-e-g-qt-ogrenext/ > That's why we have locking callbacks for AVVkFrame, and for VkQueues. It's all done for you, as long as you use the pl_map_avframe_ex(). _______________________________________________ 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:[~2023-10-29 3:18 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20231028181341.13090-1-quinkblack@foxmail.com> 2023-10-28 18:13 ` Zhao Zhili 2023-10-28 19:32 ` Lynne 2023-10-29 2:23 ` [FFmpeg-devel] [PATCH v4 1/2] fftools/ffplay: add vulkan renderer via libplacebo Zhao Zhili [not found] ` <20231029022347.15243-1-quinkblack@foxmail.com> 2023-10-29 2:23 ` [FFmpeg-devel] [PATCH v4 2/2] fftools/ffplay: add hwaccel decoding support Zhao Zhili 2023-10-29 2:31 ` [FFmpeg-devel] [PATCH v3 " Zhao Zhili 2023-10-29 3:18 ` Lynne [this message] 2023-10-29 11:12 ` Niklas Haas
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=NhtRARW--3-9@lynne.ee \ --to=dev@lynne.ee \ --cc=ffmpeg-devel@ffmpeg.org \ /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