Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Jerome Martinez <jerome@mediaarea.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] avformat/mxfenc: SMPTE RDD 48:2018 Amd 1:2022 (FFV1 in MXF) support
Date: Mon, 16 Jan 2023 15:17:42 +0100
Message-ID: <bc9364cb-f6e2-4a61-6d69-23db9e3cadc5@mediaarea.net> (raw)
In-Reply-To: <68df0e62c454d1c92bef7cae9abc255bad6f5d51.camel@haerdin.se>

On 16/01/2023 15:00, Tomas Härdin wrote:
> JPEG2000 will also need an RGBA descriptor filled out, might be good to
> prepare for that.

this was the idea behind the way it is coded, so there is only a new 
mxf_write_jpeg2000_desc function to write, like the one for FFV1 i.e.
static void mxf_write_jpeg2000_desc(AVFormatContext *s, AVStream *st)
     is_rgb = desc->flags & AV_PIX_FMT_FLAG_RGB;
     pos = mxf_write_cdci_common(s, st, is_rgb ? mxf_rgba_descriptor_key 
: mxf_cdci_descriptor_key);
}

to add.


>
> The ffv1 parsing code in this patch makes me nervous. Isn't the version
> available in metadata?

I implemented a way similar to e.g. mxf_parse_mpeg2_frame by parsing a 
bit the frame.
version and micro_version are available in FFV1Context so could be used 
but I don't know how to get FFV1Context from AVStream or other, need 
help there.


>
>> +        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, 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.

Jérôme
_______________________________________________
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".

  reply	other threads:[~2023-01-16 14:17 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 [this message]
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
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=bc9364cb-f6e2-4a61-6d69-23db9e3cadc5@mediaarea.net \
    --to=jerome@mediaarea.net \
    --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