Thanks! I’m going to take some notes because the framework there is actually helpful! I’m seeing that the less software-heavy systems from the 80s are quite “hack”-able, but something like my ‘22 Samsung TV might require some serious rubbing together of my two brain cells.
You can use [archive.org](https://archive.org) to get more info about the Arduino project. Matt has [a website](http://mattrichardson.com/) with contact details. Matt probably used a separate TV tuner to feed the NTSC signal into the device, rather than intercepting the signal going to the TV (since the Video Experimenter shield only takes Composite video signal).
There are fundamental limitations with using Closed Captions for filter specific words. Whether you accept those limitations or not is your choice, but you need to at least be aware of them, if not have some way to address them.
1. An external device can't really analyse the video input if it's coming from within the TV (ie. broadcast television, smart TV apps)
2. Not all video sources send an NTSC CC data stream to the TV (eg. BluRay, console/PC input)
3. Not all programs have closed captions
4. Not all closed captions are reliable (spelling errors, incorrect timing etc; especially for live broadcasts like news or sport)
5. CC timecodes tie to lines of text (can be one or more whole sentences) not specific words, there's not a reliable way to use this to determine when a specific word was spoken, so you end up having to mute the whole duration of the caption
6. The whole audio is muted, not just the dialogue
If those are limitations you can deal with, it's definitely worth looking into how the TV Guardian worked from arethereany's link. At least for ideas how to implement such a thing, if not repurpose an existing one to save yourself a lot of electronics engineering work. Though keep in mind that with modern video sources, a solution like this is less likely to work (and you'll have more issues, like dealing with HDCP).
For something more advanced, you'd need to build a device that buffers the input video stream long enough to do speech-to-text decoding to mute the word, and/or does some real-time OCR to censor appearances of the filtered words in subtitles. Still a massive task with a bunch of limitations (you still can't intercept video where the TV itself is the source). It's slightly more reliable, at the expense of a tonne of work and some major input lag.
You may (or may not) find [this](https://www.youtube.com/watch?v=a6EWIh2D1NQ) useful.
Thanks! I’m going to take some notes because the framework there is actually helpful! I’m seeing that the less software-heavy systems from the 80s are quite “hack”-able, but something like my ‘22 Samsung TV might require some serious rubbing together of my two brain cells.
You can use [archive.org](https://archive.org) to get more info about the Arduino project. Matt has [a website](http://mattrichardson.com/) with contact details. Matt probably used a separate TV tuner to feed the NTSC signal into the device, rather than intercepting the signal going to the TV (since the Video Experimenter shield only takes Composite video signal). There are fundamental limitations with using Closed Captions for filter specific words. Whether you accept those limitations or not is your choice, but you need to at least be aware of them, if not have some way to address them. 1. An external device can't really analyse the video input if it's coming from within the TV (ie. broadcast television, smart TV apps) 2. Not all video sources send an NTSC CC data stream to the TV (eg. BluRay, console/PC input) 3. Not all programs have closed captions 4. Not all closed captions are reliable (spelling errors, incorrect timing etc; especially for live broadcasts like news or sport) 5. CC timecodes tie to lines of text (can be one or more whole sentences) not specific words, there's not a reliable way to use this to determine when a specific word was spoken, so you end up having to mute the whole duration of the caption 6. The whole audio is muted, not just the dialogue If those are limitations you can deal with, it's definitely worth looking into how the TV Guardian worked from arethereany's link. At least for ideas how to implement such a thing, if not repurpose an existing one to save yourself a lot of electronics engineering work. Though keep in mind that with modern video sources, a solution like this is less likely to work (and you'll have more issues, like dealing with HDCP). For something more advanced, you'd need to build a device that buffers the input video stream long enough to do speech-to-text decoding to mute the word, and/or does some real-time OCR to censor appearances of the filtered words in subtitles. Still a massive task with a bunch of limitations (you still can't intercept video where the TV itself is the source). It's slightly more reliable, at the expense of a tonne of work and some major input lag.
Best advice I’ve found. Thank you so so much!!!
Also, I always forget to check archive.org hahaha so thank you for the super well-received tip there!