Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3] lavfi/vf_libplacebo: allow operation without avhwdevice
Date: Sat, 13 May 2023 20:00:08 +0200 (CEST)
Message-ID: <NVLGGoV--3-9@lynne.ee> (raw)
In-Reply-To: <20230513154230.27485-1-ffmpeg@haasn.xyz>

May 13, 2023, 17:42 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 init_vulkan failures which simply
> creates an internal device if there was no user-supplied Vulkan hwaccel.
> Useful when no interop with lavu vulkan hwframes is needed or desired,
> and makes using this filter easier inside certain applications.
>
> Fixes: https://github.com/haasn/libplacebo/issues/170
> Fixes: https://github.com/mpv-player/mpv/issues/9589#issuecomment-1535432185
> Fixes: https://github.com/mpv-player/mpv/issues/11363
> Fixes: https://github.com/mpv-player/mpv/issues/11685#issuecomment-1546627082
> Closes: https://code.videolan.org/videolan/libplacebo/-/issues/270
>

Looks good to me now
Thanks
_______________________________________________
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".

      reply	other threads:[~2023-05-13 18:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-13 15:42 Niklas Haas
2023-05-13 18:00 ` Lynne [this message]

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=NVLGGoV--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