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: Sat, 1 Jan 2022 15:15:39 -0800
Message-ID: <CAF_7JxBLTF3RBU6uKJLFk7ue5-pY-Z2cZKAzBLfR46A51S6dXw@mail.gmail.com> (raw)
In-Reply-To: <fa7dda6-507f-d6c9-ae28-a1478289860@passwd.hu>
On Sat, Jan 1, 2022 at 11:32 AM Marton Balint <cus@passwd.hu> wrote:
>
>
>
> On Wed, 22 Dec 2021, Pierre-Anthony Lemieux wrote:
>
> > 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:
> >> >
> >> >
> >> > 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.
>
> I am not sure, if 1 month is enough for things to settle.
>
> Anyway, I have sent a patch which has MCA info but without reordering. We
> could merge that now, and later, when the API is in place, add support for
> non-native channel ordering.
Sounds good to me. I have made two minor suggestions on the proposed patch.
>
> 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".
_______________________________________________
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:[~2022-01-01 23:16 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
2022-01-01 19:32 ` Marton Balint
2022-01-01 23:15 ` Pierre-Anthony Lemieux [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=CAF_7JxBLTF3RBU6uKJLFk7ue5-pY-Z2cZKAzBLfR46A51S6dXw@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