Today in "ffmpeg's AAC encoder is still a embarrassment and nobody should ever use it": OBS on Windows using it, at 320kbps, makes music sound like a low bitrate mp3 (metallic hi-hats, etc). No problem with a custom OBS build on Gentoo with libfdk_aac enabled, at *160* kbps.
-
Show this thread
-
Replying to @marcan42
Make sure you're not using an ancient ffmpeg version. How can this issue be duplicated? Need an input file. Need your command. Need the complete console output ("log").
1 reply 0 retweets 5 likes -
Replying to @FFmpeg
Yeah, no. The last ticket I saw on your tracker about AAC from another user, they were rudely and incorrectly accused of not reading the docs (while that person had in fact incorrectly read the ticket). The AAC encoder dev has also accused me of making up audiophile BS.
3 replies 0 retweets 9 likes -
Replying to @marcan42
Despite no clue how to duplicate whatever issue you're experiencing I did a few lazytests and didn't notice a huge difference between aac and libfdk_aac. Sounded fine to me. So at this point all we can offer are apologies for the behavior of the encoder and the rude developer.
1 reply 0 retweets 1 like -
Replying to @FFmpeg
If you're serious about listening and fixing this and willing to listen and either improve the encoder or change the documentation to stop claiming it's better than libfdk_aac, I can put together some samples (not now though, busy organizing an event).
2 replies 0 retweets 6 likes -
Replying to @marcan42
Where does it say it is better than libfdk_aac? I am not aware of such a statement anywhere. The samples would be helpful, but no hurry. Thanks.
1 reply 0 retweets 0 likes -
Ah, there is the sample and command in your later tweet... But still curious about first question.
1 reply 0 retweets 0 likes
Right in the official docs. https://www.ffmpeg.org/ffmpeg-codecs.html#aac … This is really what irks me the most. I am not demanding ffmpeg have perfect or even good encoders. This stuff takes time and effort and AAC sucks. But *please* don't tell users the codec is good when it isn't.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.