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
My *actual* "I noticed the ffmpeg aac encoder is bad again" use case that brought things up again, this time, was 256kbps MP3 -> 320kbps ffaac -> 320kbps ffaac, which is much gentler and I *expected* it to be transparent, but it wasn't. The second ffaac had quite noticeable loss.
But the last time I tried to bring loss of that level up to the person working on the AAC encoder at the time I was dismissed, so here I am saying "okay, let me do it 4 times at 128kbps to try to prove my point in a way anyone can hear".
By the way, I do not consider it acceptable to recommend the AAC encoder if it has this kind of generational loss. Transcoding is *very* common. People *should* be afraid to use it if it's going to do this to audio when transcoding. We live in a remix culture.
On top of that, 1-gen losses are bad enough compared to ffaac that I believe multi-generation tesets are a good proxy for the overall quality difference. It's not just a case of "fdk knows not to throw away more data on subsequent encodes". Both compound, ffaac is just worse.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
