From: Pierre-Anthony Lemieux <pal@sandflow.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/2] avformat/mxf: support MCA audio information Date: Wed, 22 Dec 2021 07:53:35 -0800 Message-ID: <CAF_7JxA5HnfaaxJGkLVAGPmP1XirRm2bYyjO0fi09Ywi43N3yA@mail.gmail.com> (raw) In-Reply-To: <be60791d02bd7e2fd831e629caa9ca3bd823c501.camel@acc.umu.se> On Wed, Dec 22, 2021 at 4:38 AM Tomas Härdin <tjoppen@acc.umu.se> wrote: > > tis 2021-12-21 klockan 21:24 +0100 skrev Marton Balint: > > > > > > On Tue, 21 Dec 2021, Tomas Härdin wrote: > > > > > tis 2021-12-21 klockan 11:44 +0100 skrev Marc-Antoine ARNAUD: > > > > Le ven. 17 déc. 2021 à 19:12, Marton Balint <cus@passwd.hu> a > > > > écrit : > > > > > > > > > > > > > > > > > > > On Fri, 17 Dec 2021, Marc-Antoine ARNAUD wrote: > > > > > > > > > > > Hi all, > > > > > > > > > > > > Can I have an update on this patch submission ? > > > > > > Is something required to be done before it can be merged ? > > > > > > > > > > New channel layout API is on its way, which makes in-demuxer > > > > > channel > > > > > reordering uneeded. Therefore the reordering option should not > > > > > be > > > > > added > > > > > as it is in this patch. I can rework the patch after the > > > > > channel > > > > > layout > > > > > API is in. (should happen in a couple of weeks at most). > > > > > > > > > > Regards, > > > > > Marton > > > > > > > > > > > > > So it will happen only after the release 5 of FFMpeg right ? > > > > Not sure. There were people who wanted the merge the channel layout > > api > > before the release. > > > > > > > > > > Is it possible to merge it, and we can rework it after the new > > > > API is > > > > released ? > > > > Patches are related to IMF (new format) patches, and if FFmpeg > > > > can > > > > accept > > > > IMF without MCA support it will generate a lot of errors in audio > > > > mapping. > > > > So even if it's not performant for now, is it possible to imagine > > > > to > > > > merge > > > > patches and rework after ? > > > > > > I suspect this might create problems for the people writing the > > > reordering API > > > > It is not matter of performance, we should not introduce a hack such > > as > > reordering PCM channels in a demuxer if there is a better solution on > > the > > horizon. Yes, it feels like channel reordering should be a framework-level feature and not a per-demuxer feature. What about a roadmap where the channel-reordering-in-MXF patch is scheduled to be merged after some reasonable time (1 month?) if the channel API has not landed by then? This would allow contributors and users to plan ahead. > > > > If this is urgent, we could merge it without reordering support. > > I think we can trust our users to maintain their own forks if they need > special hacks > > /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". _______________________________________________ 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:[~2021-12-22 15:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20211203095742.16108-1-marc-antoine.arnaud@luminvent.com> 2021-12-17 16:58 ` Marc-Antoine ARNAUD 2021-12-17 18:12 ` Marton Balint 2021-12-21 10:44 ` Marc-Antoine ARNAUD 2021-12-21 13:53 ` Tomas Härdin 2021-12-21 20:24 ` Marton Balint 2021-12-22 12:37 ` Tomas Härdin 2021-12-22 15:53 ` Pierre-Anthony Lemieux [this message] 2022-01-01 19:32 ` Marton Balint 2022-01-01 23:15 ` 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=CAF_7JxA5HnfaaxJGkLVAGPmP1XirRm2bYyjO0fi09Ywi43N3yA@mail.gmail.com \ --to=pal@sandflow.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