ffmpeg developer: "Using <extremely common use case> is invalid to prove anything." Why do I even waste my time on this?https://twitter.com/BMahol/status/1255867904475750401 …
Show this thread
-
This Tweet is unavailable.
-
For what it's worth, my original "something is wrong, this sounds odd" moment this time around was when listening to 256kbps MP3 -> 320kbps ffaac (A) -> 320kbps ffaac (B) and (B) sounded poor, then I compared to (A) and (A) -> 320kbps fdk_aac (which sounded similar).
I knew the ffmpeg aac encoder was (in other lower bitrate experiments, single encode) worse than libfdk_aac (and had already been dismissed by ffmpeg devs about this), but I was hoping 320kbps would be enough to keep it transparent through a few encodes. I was wrong.
-
-
My 4x 128kbps test is my attempt at making the issue *very obvious* because when I tried pointing out subtler artifacts last time to ffmpeg developers, I was dismissed as making stuff up because they couldn't tell the difference.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.