Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: Ted Meyer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Add AAC_xHE case to aacdec_template.c for demuxing
Date: Wed, 3 Apr 2024 06:04:48 +0200 (CEST)
Message-ID: <NuX7Mzt--3-9@lynne.ee> (raw)
In-Reply-To: <20240402214435.3928635-1-tmathmeyer@google.com>

Apr 2, 2024, 23:45 by ffmpeg-devel@ffmpeg.org:

> From: Ted Meyer <tmathmeyer@chromium.org>
>
> The parser needs to be able to be created when demuxing, otherwise the
> channel count and layout can't be successfully generated.
>
> Signed-off-by: Ted Meyer <tmathmeyer@chromium.org>
> ---
>  libavcodec/aacdec_template.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/libavcodec/aacdec_template.c b/libavcodec/aacdec_template.c
> index aa856d7fe1..9afa3aba83 100644
> --- a/libavcodec/aacdec_template.c
> +++ b/libavcodec/aacdec_template.c
> @@ -1022,6 +1022,7 @@ static int decode_audio_specific_config_gb(AACDecContext *ac,
>  case AOT_AAC_LTP:
>  case AOT_ER_AAC_LC:
>  case AOT_ER_AAC_LD:
> +    case AOT_USAC_NOSBR:
>  if ((ret = decode_ga_specific_config(ac, avctx, gb, get_bit_alignment,
>  m4ac, m4ac->chan_config)) < 0)
>  return ret;
>

That's a really invalid workaround which also disables warning users
that xHE-AAC is not implemented.
The xHE-AAC header is not an extension of the GA header to decode
anything properly, even without SBR.

I'll be posting patches in a few days to add xHE-AAC decoding support
which also fixes remuxing.
_______________________________________________
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:[~2024-04-03  4:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 21:44 Ted Meyer via ffmpeg-devel
2024-04-03  4:04 ` Lynne [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=NuX7Mzt--3-9@lynne.ee \
    --to=dev@lynne.ee \
    --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