Better still, if Unix time tracked TAI (monotonically increasing every SI second), and Leap Seconds were handled in a distributed database much like time zones - possibly even the same one we all use anyway.
That paper was published in 2014. The reference Opus encoder has certainly had a number of improvements that affect sound quality since then, whereas very few AAC implementations have.
> The reference Opus encoder has certainly had a number of improvements that affect sound quality since then…
Yes, but not for high-bitrate music applications.¹ For example, Opus 1.2 really improved the quality of music encoding at 32–48 kbps. Opus doesn't have to be great at everything to be great at what it does, just like AAC-LC doesn't have to be. (¹Opus 1.6's experimental Opus HD looks very promising for this!)
Apple's and Fraunhofer's closed-source AAC-LC encoders have seen regular, minor quality tuning, and they benefit from the research and engineering work that have been done for the AAC family of encoders (HE-AAC for bitrates down to ~48 kbps, HE-AAC v2 to 32 kbps, xHE-AAC below that).
Heh, "funrollloops" reminds me of recompiling FreeBSD 4 on my thinkpad back in the early aughts. The word made me imagine some sort of processed breakfast cereal with too many additives.
Indeed, but some scoundrel is probably scraping this page and having an LLM prepare their pitch as to how manufacturers could improve Ad / Data collection revenue by bypassing these suggestions :/
> The article seems to be insinuating that it would have.
I disagree, the article clearly states:
Montgomery and others were careful to say that Linux ID
will not magically prevent another xz‑style supply‑chain
attack, but they argue it materially raises the cost.
