-
-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New category: Robot/Artificial voice #1321
Comments
I don't think this is suitable for the current category system |
Why is this category required? Does it matter whether a video has artificial voiceover or not? |
Well, yes. You can see from the votes (before YouTube removed downvotes) that they are not perceived as equal to human voice-overs. They are usually very low quality in terms of intonation and I usually skip them when I encounter them as its super hard to follow the robotic voice any length of time. That's why I think this could be an interesting category for this plugin as well. I know that there are good "AI speaker" channels out there, but I haven't found a single good "voice-over" channel yet. They are 100% bad up to absolutely terrible. Example: Where half of the comments make fun of the bad narration. |
Doesn't seem to fit... Generally whole videos use artificial voices, rather than parts of videos. So it doesn't really fit the categorisation of SponsorBlock imo |
Piggybacking on this issue: I want to block or flag videos that use particular hash tags (as well as hide them from search results, if possible), e.g. "hdremastered" (as popularised by Vevo). I can find no official way of achieving this within YouTube. Yes, probably out of scope for SponsorBlock, but can anyone suggest a workable solution? |
check out Blocktube |
I noticed that more and more videos are using artificial voices (I guess due to their creators feel like they have a bad accent or not enough practice speaking English).
It would be nice if videos could be flagged as a whole when this type of voice over is used.
The text was updated successfully, but these errors were encountered: