From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 001/279 v2] Add a new channel layout API
Date: Thu, 16 Dec 2021 19:31:53 +0100
Message-ID: <CAPYw7P4aZNAkCM1Etc16yCgRw=p80L_3=EwG04ncPC1DfPxZfw@mail.gmail.com> (raw)
In-Reply-To: <e7e01ca7-06ee-7662-ed68-06270c87c878@gmail.com>
On Thu, Dec 16, 2021 at 7:28 PM James Almer <jamrial@gmail.com> wrote:
>
>
> On 12/16/2021 2:20 PM, Paul B Mahol wrote:
> > You can not use '|' as separator for channel layout definition.
> > Use '+' instead.
>
> Is there a technical reason, or just a preference?
>
Only for cases when you need to provide multiple channel layouts at once as
string.
How it is currently done with this set?
> _______________________________________________
> 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-16 18:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 13:21 [FFmpeg-devel] [PATCH 000/279 v2] New " James Almer
2021-12-16 13:21 ` [FFmpeg-devel] [PATCH 001/279 v2] Add a new " James Almer
2021-12-16 17:20 ` Paul B Mahol
2021-12-16 18:27 ` James Almer
2021-12-16 18:31 ` Paul B Mahol [this message]
2021-12-16 19:14 ` James Almer
2021-12-16 23:27 ` Marton Balint
2021-12-17 2:34 ` James Almer
2021-12-17 12:43 ` James Almer
2021-12-16 13:21 ` [FFmpeg-devel] [PATCH 002/279 v2] fate: add a channel_layout API test James Almer
2021-12-17 0:04 ` [FFmpeg-devel] [PATCH 000/279 v2] New channel layout API Marton Balint
2021-12-17 2:37 ` James Almer
2021-12-17 19:20 ` Marton Balint
2021-12-17 19:32 ` James Almer
2021-12-17 11:24 ` Michael Niedermayer
2021-12-17 18:04 ` Marton Balint
2021-12-18 13:36 ` Michael Niedermayer
2021-12-18 14:15 ` Michael Niedermayer
2021-12-19 11:35 ` Marton Balint
2021-12-19 12:51 ` 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='CAPYw7P4aZNAkCM1Etc16yCgRw=p80L_3=EwG04ncPC1DfPxZfw@mail.gmail.com' \
--to=onemda@gmail.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