From: Cosmin Stejerean via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>
Cc: "Cosmin Stejerean" <cosmin@cosmin.at>
Subject: Re: [FFmpeg-devel] [PATCH] aacdec: padding skip improvements
Date: Thu, 5 Oct 2023 17:22:43 +0000
Message-ID: <0101018b00dcf9aa-91fd01f2-137d-4300-990f-fdfde163c27f-000000@us-west-2.amazonses.com> (raw)
In-Reply-To: <NfxgiVF--3-9@lynne.ee>
> On Oct 4, 2023, at 7:37 PM, Lynne <dev@lynne.ee> wrote:
>
> 2048 is just more widely encountered. I'm posting these patches
> to get an opinion:
> - do we cut nothing at all (currently)
> - do we cut 1024 (required by the standard/algorithm, and currently what our AAC ENcoder outputs)
> - do we cut 2048 (what is most widely expected)
>
> My preference would be 1024. Note: this is only for raw AAC
> streams outside of a container. Streams inside of a container are currently
> correctly cut, with this value being overridden.
I think it would be good by default to have the ffmpeg encoder and decoder roundtrip correctly, and then leverage an option to specify a different padding if a different encoder was used. I think the important property is that if we take a PCM input, encode it to raw AAC with ffmpeg and then decode it to PCM output that we have the same number of PCM samples and they're all properly aligned.
Since we can't correctly handle unknown encoders (that might be using 2048 or 2112 priming samples) for the option to override the priming samples should be used in that case (which could also be set to 0 if someone really wants potentially distorted output before the decoder was properly primed).
- Cosmin
_______________________________________________
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:[~2023-10-05 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 4:07 Lynne
2023-10-03 16:40 ` Andreas Rheinhardt
2023-10-05 2:37 ` Lynne
[not found] ` <216A8695-AE2C-4CB1-8704-DA82139B4C75@cosmin.at>
2023-10-05 17:22 ` Cosmin Stejerean via ffmpeg-devel [this message]
2023-10-05 12:24 ` Derek Buitenhuis
2023-10-05 17:32 ` Lynne
2023-10-06 17:01 ` Derek Buitenhuis
2023-10-06 18:58 ` Thierry Foucu
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=0101018b00dcf9aa-91fd01f2-137d-4300-990f-fdfde163c27f-000000@us-west-2.amazonses.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=cosmin@cosmin.at \
/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