From: Dave Rice <dave@dericed.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] avformat/mxfenc: SMPTE RDD 48:2018 Amd 1:2022 (FFV1 in MXF) support
Date: Fri, 24 Mar 2023 09:59:13 -0400
Message-ID: <6E30885E-F161-4514-8CBE-BC0798ECCFC7@dericed.com> (raw)
In-Reply-To: <a5dcd117514d755997f55685213f0429002ef5b0.camel@haerdin.se>
> On Mar 15, 2023, at 10:00 AM, Tomas Härdin <git@haerdin.se> wrote:
>
> tis 2023-03-14 klockan 10:52 +0100 skrev Jerome Martinez:
>> On 31/01/2023 15:53, Tomas Härdin wrote:
>>> sön 2023-01-29 klockan 11:36 -0500 skrev Dave Rice:
>>>>
>>>> I'm just nudging on the consideration of merging this patch. I've
>>>> been testing it over the last week with ffv1/mxf content and have
>>>> found this demuxing support very helpful.
>>> Surely you mean muxing?
>>>
>>> Some FATE tests would be nice.
>>
>>
>> Apologizes for the huge delay.
>> Attached is an updated patch with a FATE test.
>
> Test passes. Maybe someone who knows more about FFV1 wants to chime in?
I can add that in the development of this patch, a contributor to SMPTE RDD 48:2018 Amd 1:2022 reviewed and approved the output ffv1/mxf files of this patch.
Kind Regards,
Dave Rice
_______________________________________________
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:[~2023-03-24 13:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 15:45 Jerome Martinez
2023-01-16 14:00 ` Tomas Härdin
2023-01-16 14:17 ` Jerome Martinez
2023-01-18 10:12 ` Tomas Härdin
2023-01-18 14:25 ` Jerome Martinez
2023-01-18 13:40 ` Tomas Härdin
2023-01-18 14:15 ` Jerome Martinez
2023-01-20 15:17 ` Tomas Härdin
2023-01-29 16:36 ` Dave Rice
2023-01-31 14:53 ` Tomas Härdin
2023-03-14 9:52 ` Jerome Martinez
2023-03-15 14:00 ` Tomas Härdin
2023-03-24 13:59 ` Dave Rice [this message]
2023-03-25 18:29 ` Tomas Härdin
2023-04-01 14:37 ` Michael Niedermayer
2023-04-01 15:20 ` Jerome Martinez
2023-04-01 15:43 ` Michael Niedermayer
2023-04-01 17:11 ` Jerome Martinez
2023-04-02 20:07 ` Michael Niedermayer
2023-04-02 22:07 ` Jerome Martinez
2023-04-04 14:43 ` Michael Niedermayer
2023-04-04 14:57 ` Jerome Martinez
2023-04-04 17:32 ` Michael Niedermayer
2023-04-04 21:37 ` Jerome Martinez
2023-04-05 12:31 ` Michael Niedermayer
2023-04-05 12:42 ` 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=6E30885E-F161-4514-8CBE-BC0798ECCFC7@dericed.com \
--to=dave@dericed.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