Google says SRV3 was causing playback errors, so it has "temporarily" disabled them.
See full article...
See full article...
So Google has graduated from deliberately killing useful feature sets for vaguely defined reasons to accidentally killing useful feature sets for vaguely defined reasons.
Heat. Heat. foreignAnd sure, automatic captions exist, and they're better than nothing, but they're wildly inferior to human-made captions to the point of making some videos completely incomprehensible.
There are some good reasons that wouldn't make too much sense unless you've spent some time doing subtitle timing work.The real question in my mind is, why create yet another caption format? Why YTT instead of the existing SSA?
Proprietary formats to make it a paid feature?The real question in my mind is, why create yet another caption format? Why YTT instead of the existing SSA?
There are some good reasons that wouldn't make too much sense unless you've spent some time doing subtitle timing work.
SRV3 has some things that make soft-subbing with formatted text much more reasonable for videos that can have varying display resolutions. It's a YouTube problem, hence why a YT solution was necessary.
The real problem here isn't SRV3. They've disabled pretty much all add-on subtitle file capabilities that allow for formatting text. Like someone else mentioned, the impression is this is likely to combat AI poisoning since these soft-sub files would make it possible to include a lot of text no real user would see.
I watched a video about poisoning AI scrapers using carefully positioned SRV3 subtitles that were located and rendered to be invisible to a normal (human) viewer; maybe the disabling is related to that?
Oh wow -- I had to google for that -- and apparently there's one's that is still up.Looks like they already delisted the version of Bad Apple made entirely out of subtitles.
Being a deaf person, I'm subject to various accessibility glitches.This sort of crap always happens with accessibility features.
It's so obvious how tech workers think about things when you don't live they way they expect you to: In a city with always-available high speed mobile data. For instance, the way that Google Maps offline mode likes to break in ways that are unfixable until the next time you get an internet connection, and that Apple Maps didn't even have an offline mode at all in 2022. Tech workers don't use their own products offline very often, so offline access is often an afterthought, if it is present at all.This sort of crap always happens with accessibility features. Companies don't test with accessibility in mind, so updates break things and fixes are treated as low priority. After all, it's easy for someone with no disabilities to consider captions a nice-to-have feature instead of absolutely essential for understanding the content.
And sure, automatic captions exist, and they're better than nothing, but they're wildly inferior to human-made captions to the point of making some videos completely incomprehensible.
People, you're voting up a newly created bot account that's posting AI SEO slop.The technique involves injecting an 'AI poison pill' into video content by embedding hidden data within high-end subtitle formats (like .ass or Advanced SubStation Alpha). By positioning text outside the visible screen area or setting its opacity to zero, creators can feed gibberish or 'noise' directly to AI crawlers—which scrape the raw text file—while leaving the experience unchanged for human viewers. This essentially 'gaslights' the model, causing it to fail at summarizing or categorizing the video correctly."
well... they're implying/claim it was accidental. Given Google's track record , let's just say I'm suspicious.So Google has graduated from deliberately killing useful feature sets for vaguely defined reasons to accidentally killing useful feature sets for vaguely defined reasons.
Quite possible. Gemini seems to be Googles current pet "must succeed at all cost" project, so anything that might threaten their data scraping is going to be a target for "counter measures"I watched a video about poisoning AI scrapers using carefully positioned SRV3 subtitles that were located and rendered to be invisible to a normal (human) viewer; maybe the disabling is related to that?
I'm sure your issue is far more annoying (since I can actually see) but I've been having the opposite issue with the official Youtube android app and website version (in Firefox) where it keeps turning ON CC even though I don't want/need them for English or Dutch.The YouTube app on Amazon FireTV randomly turns off CC even though I try to have CC permanently turned on.
I don't know why it happens that CC is randomly turned off right after an advertisement break.
Oh wow -- I had to google for that -- and apparently there's one's that is still up.
(or was un-delisted manually):
View: https://www.youtube.com/watch?v=GJ5yMg1l5Bg
Make sure to enable "CC" to see Bad Apple rendered in rapidly updating ASCII subtitles.
Now "Music" gets put in the middle of text and "Thank you very much" often appears at the end. I suspect someone had the great idea of hooking the audio track up to an LLM instead of TTS.Heat. Heat. foreign
For those who are confused, these are what YouTube's auto-generated subtitles spit out during moments of silence or other non-vocal sounds. Yes, "Heat" is always capitalised and often followed by a full stop. Yes, "foreign" is always uncapitalised.
Heat. Heat. foreign
For those who are confused, these are what YouTube's auto-generated subtitles spit out during moments of silence or other non-vocal sounds. Yes, "Heat" is always capitalised and often followed by a full stop. Yes, "foreign" is always uncapitalised.
Heat. Heat. foreign
For those who are confused, these are what YouTube's auto-generated subtitles spit out during moments of silence or other non-vocal sounds. Yes, "Heat" is always capitalised and often followed by a full stop. Yes, "foreign" is always uncapitalised.
I will take nothing any day. CC should be off by default.This sort of crap always happens with accessibility features. Companies don't test with accessibility in mind, so updates break things and fixes are treated as low priority. After all, it's easy for someone with no disabilities to consider captions a nice-to-have feature instead of absolutely essential for understanding the content.
And sure, automatic captions exist, and they're better than nothing, but they're wildly inferior to human-made captions to the point of making some videos completely incomprehensible.
The exact opposite. CC MUST be provided in order for some specific people being able to use the service. Which... was the point of the person you were replying to. You are clearly not disabled here, and don't comprehend that this is NOT something optional for some people. And... this is the exact same attitude which Google appears to have as well.I will take nothing any day. CC should be off by default.
Depending on how yu view it - if you wish to not assume malice, the ability to update, modify, and troubleshoot YTT as the website changes over the static SSA library.The real question in my mind is, why create yet another caption format? Why YTT instead of the existing SSA?
I realize you hypothetically may be sole downvoter of my mainly upvoted deaf post -- but the way it is /supposed/ to work is that it should be possible for the default CC setting to be be configurable by the end user (in a settings screen somewhere) to be permanently OFF or permanently ON.I will take nothing any day. CC should be off by default.
That's probably exactly what they did. Honestly, it's not as terrible an idea as it seems at first glance; it makes sense to me to use a transformer neural network to convert audio directly to text. They were originally developed for language translation, after all, and a token's a token. However, the pitfalls of training extensively on "content" found on YouTube can be clearly seen in these hallucinations (still have no idea about "Heat."; are there that many videos about furnaces on YT?)Now "Music" gets put in the middle of text and "Thank you very much" often appears at the end. I suspect someone had the great idea of hooking the audio track up to an LLM instead of TTS.
If this is indeed the case--then wouldn't it make far more sense to back out that breaking change until it can be fixed? Software regression issues happen all the time. The solution is a rollback.That’s pretty vague, but it sounds like developers made a change to the platform without taking into account how it might interfere with SRV3 captions.
If this is indeed the case--then wouldn't it make far more sense to back out that breaking change until it can be fixed? Software regression issues happen all the time. The solution is a rollback.
From what I've found, there was no "playback failure" to begin with EXCEPT on the official android app. Some videos exist with SRV3 subtitles still. They crash my android app and don't display subtitles at all. But it's not a device issue. I have an s25 Ultra. I open the exact same video in the Firefox app and it works 100% fine - no crashing, fancy subtitles. It works fine on my PC too. So my testing is showing me YouTube is punishing EVERYONE because their app sucks.
View: https://youtu.be/8Oos6D4_Bjo