Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavc: export flag for MPEG audio dual channel
Date: Thu, 22 Sep 2022 14:43:50 +0200
Message-ID: <166385063040.3205.9615866563475198287@lain.khirnov.net> (raw)
In-Reply-To: <b586fbb8-d2b9-f8ba-a849-6351a663f292@gmail.com>

Quoting Scott Theisen (2022-09-22 03:04:16)
> On 9/21/22 15:51, James Almer wrote:
> > On 9/21/2022 4:44 PM, Rémi Denis-Courmont wrote:
> >> Le keskiviikkona 21. syyskuuta 2022, 22.26.11 EEST Scott Theisen a 
> >> écrit :
> >>> diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
> >>> index 7db5d1b1c5..bcf3a845a8 100644
> >>> --- a/libavcodec/avcodec.h
> >>> +++ b/libavcodec/avcodec.h
> >>> @@ -2076,6 +2076,17 @@ typedef struct AVCodecContext {
> >>>        *             The decoder can then override during decoding 
> >>> as needed.
> >>> */
> >>>       AVChannelLayout ch_layout;
> >>> +
> >>> +    /**
> >>> +     * Audio only.  This flag is set when MPEG audio mode dual 
> >>> channel has
> >>> been detected. +     * This signals that the audio is two 
> >>> independent mono
> >>> channels. +     *
> >>> +     * 0 normally, 1 if dual channel flag is set.
> >>> +     *
> >>> +     * - encoding: currently unused (functionally equivalent to 
> >>> stereo,
> >>> patch welcome) +     * - decoding: set by lavc
> >>> +     */
> >>> +    int mpeg_audio_mode_dual_channel;
> >>>   } AVCodecContext;
> >>
> >> I agree that the dual mono flag should be exposed to the application 
> >> somehow,
> >> but isn't this a slient ABI break?
> >
> > It's not a break, but it's overkill for what's essentially a flag.
> 
> This is how MythTV customized FFmpeg (in 2006) for this and this way was 
> probably the easiest.  It /is/ a flag, so maybe adding an int as a 
> bitset instead of as a bool so other flags could be added if necessary?
> 
> >
> > The proper way to do this would be to signal such a layout as an 
> > actual channel layout, using a custom order one where both channels 
> > are set as Front Center. But i don't know if until the old channel 
> > layout API fields are gone we should have decoders setting something 
> > only new API users will understand. Old API field users would look at 
> > channels and see a 2, and channel_layout and see it's empty, but then 
> > old and new API values would technically conflict, so I'd like to hear 
> > some opinions.
> 
> I'm not very familiar with either channel layout API, but the audio is 
> encoded identically to stereo other than the flag, so could we add 
> another entry, e.g. AV_CHANNEL_ORDER_MONO, to the `enum AVChannelOrder` 
> to signify that each channel is independent, but is otherwise identical 
> to AV_CHANNEL_ORDER_NATIVE?

The whole point is that it's NOT identical to AV_CHANNEL_ORDER_NATIVE.
ORDER_CUSTOM with two FC channels is exactly the right way to handle
this IMO.

-- 
Anton Khirnov
_______________________________________________
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".

  reply	other threads:[~2022-09-22 12:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 19:26 Scott Theisen
2022-09-21 19:44 ` Rémi Denis-Courmont
2022-09-21 19:51   ` James Almer
2022-09-22  1:04     ` Scott Theisen
2022-09-22 12:43       ` Anton Khirnov [this message]
2022-09-22 20:02         ` Scott Theisen
2022-09-21 19:51   ` Andreas Rheinhardt

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=166385063040.3205.9615866563475198287@lain.khirnov.net \
    --to=anton@khirnov.net \
    --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