From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2 2/2] avcodec: add a ffv1 parser
Date: Thu, 6 Feb 2025 16:28:15 -0300
Message-ID: <5d707089-bbc6-4783-bdb7-a7ac42f61bff@gmail.com> (raw)
In-Reply-To: <27f54fa5-c0d2-43ea-a333-d22cc09accba@mediaarea.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 542 bytes --]
On 2/6/2025 4:25 PM, Jerome Martinez wrote:
> Le 06/02/2025 à 16:52, Michael Niedermayer a écrit :
>> On Sun, Feb 02, 2025 at 11:16:03PM -0300, James Almer wrote:
>>> [...]
>>> + s->pict_type = AV_PICTURE_TYPE_I; //FIXME I vs. P, see ffv1dec.c
>> id remove the comment, also in ffv1dec.c
>
> For your information this resolves the issue with non working demux (raw
> copy) of FFV1 in MXF
> https://trac.ffmpeg.org/ticket/10161
That problem was what prompted me to write it, but i wasn't aware this
ticket existed.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 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-02-06 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 2:16 [FFmpeg-devel] [PATCH 1/2] avcodec/ffv1: split off and share frame header parsing code James Almer
2025-02-03 2:16 ` [FFmpeg-devel] [PATCH v2 2/2] avcodec: add a ffv1 parser James Almer
2025-02-03 5:42 ` Lynne
2025-02-03 13:00 ` James Almer
2025-02-06 15:52 ` Michael Niedermayer
2025-02-06 17:10 ` James Almer
2025-02-06 19:25 ` Jerome Martinez
2025-02-06 19:28 ` James Almer [this message]
2025-02-06 15:49 ` [FFmpeg-devel] [PATCH 1/2] avcodec/ffv1: split off and share frame header parsing code 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=5d707089-bbc6-4783-bdb7-a7ac42f61bff@gmail.com \
--to=jamrial@gmail.com \
--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