I’m pretty sure it’s not too hard to implement an ASS → PNG renderer (especially considering vibe coding is now a thing). Then, just need to split out subs that can be actual text somehow from the ones that have to be overlays.
Apart from that... surely they could at least keep ASS subs for the players that support it, and serve “fallback” subs for low-end devices?
You can also use the same kind of segment-based playlist approach on Blu-ray if you wanted to, though theoretically you should be able to use the Blu-ray Picture-in-Picture feature to store the typesetting in a separate partially transparent video stream entirely that is then overlaid on top of the clean video during playback.
We did do inlaid server-side ads that way for a while.
IT just takes an excessive amount of work.
The real solution is just the full support of ASS/TTML/VTT subtitles on all platforms. Usually smart devices are kind of only partially supported.
For instance - casting to a chromecast fallsback to SRT.
You'd see playback issues go up by 1000%.
In the nicest possible way, it is pretty clear that this article was written by somebody who has only ever looked at video distribution as a hobbyist and not deploying it at scale to paying customers who quite reasonably get very upset at things not working reliably.
Only english is the most popular and just keep it. Most of the good hard subs are made for english and that is what people want.
It's really tough when you need to scale these things across 20 platforms.
