From: Lynne <dev@lynne.ee>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] ffv1dec: use dedicated pix_fmt field and call ff_get_format
Date: Sat, 25 Jan 2025 11:06:43 +0900
Message-ID: <c83f6591-3878-4dfb-a340-0e1d9886ae81@lynne.ee> (raw)
In-Reply-To: <20250124215441.GD2768425@pb2>
[-- Attachment #1.1.1.1: Type: text/plain, Size: 1081 bytes --]
On 25/01/2025 06:54, Michael Niedermayer wrote:
> On Tue, Jan 21, 2025 at 03:10:47PM +0000, Lynne wrote:
>> ffmpeg | branch: master | Lynne <dev@lynne.ee> | Sun Jan 5 13:42:47 2025 +0900| [7187eadf8c0f0c640f1d23811c55fad0cba60aa5] | committer: Lynne
>>
>> ffv1dec: use dedicated pix_fmt field and call ff_get_format
>>
>> Adding support for hwaccels means that avctx->pix_fmt will indicate
>> hardware formats.
>>
>>> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=7187eadf8c0f0c640f1d23811c55fad0cba60aa5
>> ---
>>
>> libavcodec/ffv1.h | 1 +
>> libavcodec/ffv1dec.c | 140 ++++++++++++++++++++++++++++-----------------------
>> 2 files changed, 78 insertions(+), 63 deletions(-)
>
> breaks:
> ./ffmpeg -y -i mm-short.mpg -an -vcodec ffv1 -slices 4 -t 1 -coder 1 -level 3 -slicecrc 0 -context 0 -pix_fmt ya8 -bitexact out.nut
> ./ffplay out.nut
>
> (and others)
> slices seem to decode in the wrong locations and jump randomly around
>
> thx
Thanks.
Is it this specific patch, or is it the patchset as a whole that did it?
[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 637 bytes --]
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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-01-25 2:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250121151048.CC69B4127EF@natalya.videolan.org>
2025-01-24 21:54 ` Michael Niedermayer
2025-01-25 2:06 ` Lynne [this message]
2025-01-25 17:18 ` Michael Niedermayer
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=c83f6591-3878-4dfb-a340-0e1d9886ae81@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