From: "Tomas Härdin" <git@haerdin.se> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] MXF - Add jpeg2000 subdescriptor - Sponsored by INA Date: Wed, 05 Apr 2023 15:53:19 +0200 Message-ID: <be983d481c5f939a268ed6163932215a1a0db87c.camel@haerdin.se> (raw) In-Reply-To: <ac8ded6b-ba5b-9189-9d26-a23b6c4ff1ae@ektacom.com> ons 2023-04-05 klockan 15:05 +0200 skrev Cédric Le Barz: > Le 03/04/2023 à 17:14, Michael Niedermayer a écrit : > > On Mon, Apr 03, 2023 at 10:08:25AM +0200, Cédric Le Barz wrote: > > > Hi, > > > > > > I've attached the patch to this mail, in order to solve newlines > > insertion > > > issue. > > Please make sure each patch also updates the fate tests so > > make fate > > doesnt fail > I've attached to this mail the new patch. Fate test issue is fixed. > Please avoid top posting. I was actually about to suggest merging these two patches but I see you read my mind :) > @@ -1131,9 +1164,9 @@ static const UID mxf_aes3_descriptor_key = > { 0x06,0x0E,0x2B,0x34,0x02,0x53, > static const UID mxf_cdci_descriptor_key = { > 0x06,0x0E,0x2B,0x34,0x02,0x53,0x01,0x01,0x0D,0x01,0x01,0x01,0x01,0x01 > ,0x28,0x00 }; > static const UID mxf_rgba_descriptor_key = { > 0x06,0x0E,0x2B,0x34,0x02,0x53,0x01,0x01,0x0D,0x01,0x01,0x01,0x01,0x01 > ,0x29,0x00 }; > static const UID mxf_generic_sound_descriptor_key = { > 0x06,0x0E,0x2B,0x34,0x02,0x53,0x01,0x01,0x0D,0x01,0x01,0x01,0x01,0x01 > ,0x42,0x00 }; > - Stray line deletion > + mxf_write_local_tag(s, 2, 0x8401); > + avio_wb16(pb, 0x0000); > + mxf_write_local_tag(s, 4, 0x8402); > + avio_wb32(pb, st->codecpar->width); > + mxf_write_local_tag(s, 4, 0x8403); > + avio_wb32(pb, st->codecpar->height); > + mxf_write_local_tag(s, 4, 0x8404); > + avio_wb32(pb, 0); > + mxf_write_local_tag(s, 4, 0x8405); > + avio_wb32(pb, 0); > + mxf_write_local_tag(s, 4, 0x8406); > + avio_wb32(pb, st->codecpar->width); > + mxf_write_local_tag(s, 4, 0x8407); > + avio_wb32(pb, st->codecpar->height); > + mxf_write_local_tag(s, 4, 0x8408); > + avio_wb32(pb, 0); > + mxf_write_local_tag(s, 4, 0x8409); > + avio_wb32(pb, 0); > + mxf_write_local_tag(s, 2, 0x840A); > + avio_wb16(pb, component_count); A comment on each of these explaining what they are would be nice. > + { > + char _desc [3][3]= { {0x09,0x01,0x01} , {0x09,0x02,0x01} , > {0x09,0x02,0x01} }; > + int comp = 0; > + for ( comp = 0; comp< component_count ;comp++ ) { > + avio_write(pb, _desc[comp%3] , 3); > + } > + } Maybe just a style nit but you could move the char desc[] into the loop body, int comp to the start of the function and then you can remove the extra {} around this. Also you could make desc static const. > + { > + char _layout[16] = { 'Y' , '\n', 'U' , '\n', 'V' , '\n', > 'F' , 0x02, > + 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, > 0x00, 0x00 }; > + avio_write(pb, _layout , 16); > + } Again there is the issue of RGB(A) /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-04-05 13:53 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-29 20:54 Cédric Le Barz 2023-03-31 21:47 ` Michael Niedermayer 2023-04-03 8:08 ` Cédric Le Barz 2023-04-03 15:14 ` Michael Niedermayer 2023-04-05 13:05 ` Cédric Le Barz 2023-04-05 13:53 ` Tomas Härdin [this message] 2023-04-25 14:33 ` Cédric Le Barz 2023-04-27 12:45 ` Tomas Härdin 2023-05-02 15:43 ` Cédric Le Barz 2023-05-09 9:49 ` Tomas Härdin 2023-05-09 14:28 ` Pierre-Anthony Lemieux 2023-06-01 15:19 ` Cédric Le Barz 2023-06-04 18:24 ` Tomas Härdin 2023-09-22 9:26 ` Cédric Le Barz 2023-04-05 12:39 ` Tomas Härdin 2023-04-23 1:07 ` Pierre-Anthony Lemieux
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=be983d481c5f939a268ed6163932215a1a0db87c.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