From: Marton Balint <cus@passwd.hu> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avformat/mov_chan: respect channel order when parsing and creating chan atom Date: Sat, 23 Mar 2024 12:17:28 +0100 (CET) Message-ID: <b8c5e017-91fe-cb6b-a804-d3a1c5b2b093@passwd.hu> (raw) In-Reply-To: <383e7f14-4393-47b9-c138-069b8357b832@passwd.hu> On Mon, 18 Mar 2024, Marton Balint wrote: > > > On Mon, 18 Mar 2024, Andreas Rheinhardt wrote: > >> Marton Balint: >>> Previously we always assumed that the channels are in native order, even >>> if >>> they were not. The new channel layout API allows us to signal the proper >>> channel order, so let's do so. >>> >>> Fixes ticket #98. >>> --- >>> libavformat/mov_chan.c | 464 +++++++++++++++++++---------------------- >>> 1 file changed, 211 insertions(+), 253 deletions(-) >>> [...] >>> +#define TAG(_0) (struct >>> MovChannelLayoutMap){.tag = _0} >>> +#define ID(_0) (struct >>> MovChannelLayoutMap){.id = c_##_0} >> >> Code like >> >> typedef struct Foo { >> int a; >> } Foo; >> >> Foo bar[] = { >> (Foo) {.a = 1}, >> }; >> >> is not valid C11 (or C17), because initializers for static objects are >> subject to severe restrictions; in particular, compound literals are not >> allowed. GCC and Clang ignore this except when using -pedantic, but MSVC >> does not: https://godbolt.org/z/hvnrh63za >> Just remove the "(MovChannelLayoutMap)". > > Ok, will do, thanks. Will apply. Regards, Marton _______________________________________________ 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".
prev parent reply other threads:[~2024-03-23 11:17 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-17 19:56 Marton Balint 2024-03-17 23:47 ` Andreas Rheinhardt 2024-03-17 23:57 ` Marton Balint 2024-03-23 11:17 ` Marton Balint [this message]
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=b8c5e017-91fe-cb6b-a804-d3a1c5b2b093@passwd.hu \ --to=cus@passwd.hu \ --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