@absturztaube Hiya. Sorry, emote-poor instance here 😕
Lockdown really sucks, life won't go back to normal for a long time 😟
@wolf480pl Yeah. There are worse ones out there, like Dolby-E in S302M in WAV. Unfortunately, a commonly used broadcast standard which will blow your ears if you listen to it without properly decoding, which you can't do because WAV tells you its just standard PCM.
@wolf480pl H.264/HEVC/AV1 all have an Annex-B which specifies a minimal container. Because some companies are complete idiots and only understand files, and don't get minimal containers like IVF.
And some idiots who don't understand put Annex-B packets into full containers like MP4 so you end up with files you can't play and can't detect why.
AAC also has this (LATM) which is even worse because it doesn't carry profile data, so decoders hardcode AAC-LC and won't play the more common AAC-HE.
#TLMC Amateras Records - Purely
Amateras are a solid and well known circle. They're less house-orientated than Alstroemeria but they'll occasionally do something like this.
Mastodon have implemented mandatory H264+AAC transcoding for any .mp4 that isn't H264+AAC. Apart from being stupid because AV1 is now being used and Opus has been used for half a decade now, it also opens an easy DDOS attack possibility.
Just encode low bitrate JPEG2000 video in .mp4 (yes, its in spec). The ffmpeg j2k decoder is RIDICULOUSLY slow. Decoding even a few j2k frames will take an eternity.
Of course, I'll permit all codecs in my instance. Something doesn't decode? Not my problem.
Codec researcher, x86 assembly and Vulkan expert. As expected.
Had nothing to do with x264. Most unexpected.
A Mastodon instance for people interested in multimedia, codecs, assembly, SIMD, and the occasional weeb stuff.