> The encoder was mainly optimized for 48Khz audio. Get over it. It's 2026, resampling is free, 48Khz is the standard. 44.1Khz will work, and so will 96Khz but use 48Khz if you want the best quality. Is 48kHz really the standard nowadays?
Pretty much all DACs run at 48Khz by default due to operating systems picking it as a sane default.
FFmpeg 9.1's new AAC encoder
121–130 of 162 posts
Re: FFmpeg 9.1's new AAC encoder
#122Man what a showcase for Opus this is. Don't get me wrong, this sort of thing is a valuable exercise and we are better off with better encoders for these older codecs. But look at the numbers for Opus on this benchmark. It simply blows all the AAC encoders out of the water even at 64 kbps.
> Man what a showcase for Opus this is. I take it you mean this Opus ( https://en.wikipedia.org/wiki/Opus_(audio_format) ) not that Opus ( https://en.wikipedia.org/wiki/Claude_(AI) ). I read almost all the way through your comment thinking there was a decent probability you were saying this new AAC encoder was written with Claude Opus.
Re: FFmpeg 9.1's new AAC encoder
#123Man what a showcase for Opus this is. Don't get me wrong, this sort of thing is a valuable exercise and we are better off with better encoders for these older codecs. But look at the numbers for Opus on this benchmark. It simply blows all the AAC encoders out of the water even at 64 kbps.
Re: FFmpeg 9.1's new AAC encoder
#124Earlier quoted context omitted.
The biggest advantage for having a good AAC encoder isn't efficiency, it's that for nearly the past 2 decades the de facto standard for live streamed video has been RTMP with H.264 video and AAC audio. There is basically no support for any other codecs. If you want to send a video stream to Youtube or Twitch, you will be sending H.264 and AAC. If you want an idea of how ubiquitous this is, I just checked in OBS and i…
YouTube actually supports H.265 and VP9 ingest, depending on the streaming protocol. I can actually stream 4K@60 H.265 from my Mac Studio with https://developers.google.com/youtube/v3/live/guides/ingesti...
YouTube serves vp9 but it always re-encodes my videos as AV1. Annoying.
(I would upload as AV1 but the encoder is slooooooooow.)
Re: FFmpeg 9.1's new AAC encoder
#125Man what a showcase for Opus this is. Don't get me wrong, this sort of thing is a valuable exercise and we are better off with better encoders for these older codecs. But look at the numbers for Opus on this benchmark. It simply blows all the AAC encoders out of the water even at 64 kbps.
> Man what a showcase for Opus this is. I take it you mean this Opus ( https://en.wikipedia.org/wiki/Opus_(audio_format) ) not that Opus ( https://en.wikipedia.org/wiki/Claude_(AI) ). I read almost all the way through your comment thinking there was a decent probability you were saying this new AAC encoder was written with Claude Opus.
Re: FFmpeg 9.1's new AAC encoder
#126Earlier quoted context omitted.
I think the biggest issue with Opus is the problem with its specification being lacking, see: https://nothings.org/stb/stb_opus.html This essentially causes opus to never be used in games or in things in stores that may have issues with specific licenses.
That’s going a bit far. I’m in the games industry and have used opus regularly, it’s a great codec for games, often the hardware decoding is so restricted that we’re using software regardless so we might as well use something like opus. The licensing restriction is unfortunate, but only restrictive for those with very specific goals, under normal conditions BSD is a wonderful license for game devs since you’re free t…
Re: FFmpeg 9.1's new AAC encoder
#127Man what a showcase for Opus this is. Don't get me wrong, this sort of thing is a valuable exercise and we are better off with better encoders for these older codecs. But look at the numbers for Opus on this benchmark. It simply blows all the AAC encoders out of the water even at 64 kbps.
Definitely thought you meant claude opus but now from reading a couple other comments it sounds like you mean something else called opus?
Re: FFmpeg 9.1's new AAC encoder
#128Man what a showcase for Opus this is. Don't get me wrong, this sort of thing is a valuable exercise and we are better off with better encoders for these older codecs. But look at the numbers for Opus on this benchmark. It simply blows all the AAC encoders out of the water even at 64 kbps.
Definitely thought you meant claude opus but now from reading a couple other comments it sounds like you mean something else called opus?
Been around a lot longer than Claude Opus.
Re: FFmpeg 9.1's new AAC encoder
#129Earlier quoted context omitted.
On a microcontroller doing nothing else sure. But on a phone, a tablet, a laptop, you absolutely want hardware decode to preserve your battery life.
That's their point though. Basically no modern phone/laptop/tablet other than Apple offloads audio decoding (of any codec) to hardware. You can check this on Android phones by installing the Codec Info app.
If the OS/platform doesn't use it that could be another thing, but those chips do offer audio coded decoding, including aac
Re: FFmpeg 9.1's new AAC encoder
#130Earlier quoted context omitted.
Sample accurate editing is with AAC is a pain though. Especially if you also have video, because frame rates are usually incompatible. If you want flexibility without fully transcoding both audio and video, Opus is your friend
Editing with any playback-only format like AAC or H.264/5 is a pain. Everyone I've seen complaining about slow choppy playback in DaVinci Resolve appears to be using long-GOP codecs which require a massive amount of processing to decode. It's something like playing out two seconds of video to access every single frame.