Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Philip Langdale <philipl@overt.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] vulkan_decode: do not align the image dimensions
Date: Sun, 28 May 2023 20:11:39 -0700
Message-ID: <20230528201139.7182a26a@fido7> (raw)
In-Reply-To: <NW_FqkU--3-9@lynne.ee>

On Mon, 29 May 2023 04:08:17 +0200 (CEST)
Lynne <dev@lynne.ee> wrote:

> According to Dave Airlie:
> 
> > <airlied> but I think ignoring it should be fine, I can't see any
> > other way to get the imaeg extents correct for other usage
> > <Lynne> what width/height should be used for the images?
> > the final presentable dimensions, or the coded dimensions?
> > <airlied> if you don't want noise I think the presentable dims
> > <airlied> the driver should round up the allocations internally,
> > but if you are going to sample from the images then w/h have to be
> > the bounds of the image you want
> > <airlied> since otherwise there's no way to stop the sampler from
> > going outside the edges
> 

Works fine on nvidia here. I agree with the logic - it doesn't seem
reasonable to handle it the other way.

--phil
_______________________________________________
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-29  3:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29  2:08 Lynne
2023-05-29  3:11 ` Philip Langdale [this message]
2023-05-29  3:13   ` Lynne

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=20230528201139.7182a26a@fido7 \
    --to=philipl@overt.org \
    --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