From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2 v2] avutil: add a Tile Grid API
Date: Sun, 21 Jan 2024 07:27:00 +0100
Message-ID: <170581842075.8914.15090755160718905890@lain.khirnov.net> (raw)
In-Reply-To: <20240120220407.64141-1-jamrial@gmail.com>
Quoting James Almer (2024-01-20 23:04:06)
> This includes a struct and helpers. It will be used to support container level
> cropping and tiled image formats, but should be generic enough for general
> usage.
>
> Signed-off-by: James Almer <jamrial@gmail.com>
> ---
> Extended to include fields used for cropping. Should make the struct reusable
> even for non tiled images, e.g. setting both rows and tiles to 1, in which case
> tile width and height would become analogous to coded_{witdh,height}.
But why? What does cropping have to do with tiling? What advantage is
there to handling them in one struct?
--
Anton Khirnov
_______________________________________________
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-01-21 6:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 22:04 James Almer
2024-01-20 22:04 ` [FFmpeg-devel] [PATCH 2/2 v2] avformat: add a Tile Grid stream group type James Almer
2024-01-21 6:27 ` Anton Khirnov [this message]
2024-01-21 12:06 ` [FFmpeg-devel] [PATCH 1/2 v2] avutil: add a Tile Grid API James Almer
2024-01-21 17:29 ` Anton Khirnov
2024-01-21 17:47 ` James Almer
2024-01-21 18:29 ` Anton Khirnov
2024-01-21 18:38 ` James Almer
2024-01-21 19:02 ` Anton Khirnov
2024-01-21 19:29 ` James Almer
2024-01-21 21:03 ` James Almer
2024-01-22 10:38 ` Anton Khirnov
2024-01-22 12:12 ` James Almer
2024-01-22 10:32 ` Anton Khirnov
2024-01-22 11:59 ` James Almer
2024-01-25 17:13 ` Anton Khirnov
2024-01-25 17:31 ` James Almer
2024-01-22 12:08 ` James Almer
2024-01-25 17:17 ` Anton Khirnov
2024-01-25 17:26 ` James Almer
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=170581842075.8914.15090755160718905890@lain.khirnov.net \
--to=anton@khirnov.net \
--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