From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] lavfi/vf_libplacebo: add vulkan device import fallback
Date: Thu, 11 May 2023 11:32:27 +0200 (CEST)
Message-ID: <NV98tXt--3-9@lynne.ee> (raw)
In-Reply-To: <20230511083902.7262-1-ffmpeg@haasn.xyz>
May 11, 2023, 10:39 by ffmpeg@haasn.xyz:
> From: Niklas Haas <git@haasn.dev>
>
> Recent versions of libplacebo have required Vulkan versions incompatible
> with lavu Vulkan hwcontexts. While this is expected to change
> eventually, breaking vf_libplacebo every time there is such a transition
> period is obviously undesired behavior, as the following sea of bug
> reports shows.
>
> This commit adds a fallback path for pl_vulkan_import failures which
> simply creates an internal device instead. Also useful when no interop
> with lavu vulkan hwframes is needed or desired.
>
> Fixes: https://github.com/haasn/libplacebo/issues/170
> Fixes: https://github.com/mpv-player/mpv/issues/9589#issuecomment-1535432185
> Fixes: https://code.videolan.org/videolan/libplacebo/-/issues/270
>
NAK. The whole point of the hwcontext infrastructure is to be
explicit, and creating a new device behind the scenes is anything but that.
Granted, this period of instability has gone too far, but I think we should
work together to make sure there's interoperability, and after my
patchset gets merged, there won't be much need to change anything
in terms of enabled features for a while.
Both libplacebo and the hwcontext have had a ton of changes recently,
but before we started making changes, they were working fine for
over a year.
_______________________________________________
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-05-11 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 8:28 [FFmpeg-devel] [PATCH] " Niklas Haas
2023-05-11 8:39 ` [FFmpeg-devel] [PATCH v2] " Niklas Haas
2023-05-11 9:32 ` Lynne [this message]
2023-05-11 11:21 ` Hendrik Leppkes
2023-05-11 11:57 ` Dennis Mungai
2023-05-11 12:01 ` Lynne
2023-05-11 12:10 ` Niklas Haas
2023-05-11 9:53 ` Anton Khirnov
2023-05-11 10:10 ` 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=NV98tXt--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