From: "Tomas Härdin" <git@haerdin.se>
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: Wed, 18 Jan 2023 11:12:41 +0100
Message-ID: <7d1f211d6d8fa82463e8bd562c8508642767930b.camel@haerdin.se> (raw)
In-Reply-To: <bc9364cb-f6e2-4a61-6d69-23db9e3cadc5@mediaarea.net>
mån 2023-01-16 klockan 15:17 +0100 skrev Jerome Martinez:
> On 16/01/2023 15:00, Tomas Härdin wrote:
> >
> > > + ff_build_rac_states(&c, 0.05 * (1LL << 32), 256 - 8);
> > (1LL << 32) / 20 ?
>
> Could be, I don't really care, but this line is copied from ffv1dec.c
Yeah I figured as much after doing some more grepping
> I
> think it may be relevant to keep the exact same code for the exact
> same
> purpose.
> Would be no more relevant if version and micro_version can be taken
> from
> FFV1Context.
Perhaps we can have the ffv1 code in lavc expose a function for this? I
don't really like that we have this kind of parsing inside the muxers.
This goes for MPEG-2 and H.264 as well.
/Tomas
_______________________________________________
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-01-18 10:12 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 [this message]
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
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=7d1f211d6d8fa82463e8bd562c8508642767930b.camel@haerdin.se \
--to=git@haerdin.se \
--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