You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
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").
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.
I've seen enough attempts to bring this up, from myself and from others. Ball's in your court. That encoder sucks, and anyone doing basic tests with a few nontrivial samples can see that. If you pretend everything's fine while being rude to those who notice, that's your problem.
Unfair to tar the whole project based on the actions of one dev
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.
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).
Here's another recent user with the *same* *exact* *problem*:https://twitter.com/dosnostalgic/status/1262884834822819850 …
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
