From: Emma Worley <emma@emma.gg>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v4 3/3] lavc/dxvenc: improve compatibility with Resolume products
Date: Tue, 22 Apr 2025 01:14:14 -0700
Message-ID: <CAFQzNw7-WY9o4i_s_Py--hyVBMNLmv5SkWQVf7chRRbtrMti-g@mail.gmail.com> (raw)
In-Reply-To: <GV1P250MB07376A4D09A031A34A8D108C8FBB2@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
On Tue, Apr 22, 2025 at 1:00 AM Andreas Rheinhardt
<andreas.rheinhardt@outlook.com> wrote:
> Did you try to avoid the above by modifying
> ff_texturedsp_exec_compress_threads()?
I considered it but adding support to substitute in padding seemed
like a rather large refactor.
_______________________________________________
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:[~2025-04-22 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 7:42 [FFmpeg-devel] [PATCH v4 1/3] lavc/hashtable: create generic robin hood hash table Emma Worley
2025-04-22 7:42 ` [FFmpeg-devel] [PATCH v4 2/3] lavc/dxvenc: migrate DXT1 encoder to lavc hashtable Emma Worley
2025-04-22 7:42 ` [FFmpeg-devel] [PATCH v4 3/3] lavc/dxvenc: improve compatibility with Resolume products Emma Worley
2025-04-22 7:59 ` Andreas Rheinhardt
2025-04-22 8:14 ` Emma Worley [this message]
2025-04-22 17:24 ` [FFmpeg-devel] [PATCH v4 1/3] lavc/hashtable: create generic robin hood hash table Nicolas George
2025-04-22 17:57 ` Emma Worley
2025-04-22 22:04 ` Nicolas George
2025-04-22 22:02 ` Nicolas George
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=CAFQzNw7-WY9o4i_s_Py--hyVBMNLmv5SkWQVf7chRRbtrMti-g@mail.gmail.com \
--to=emma@emma.gg \
--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