How Twitch mutes a VOD.
Twitch runs an audio recognition system over VODs and clips. When it detects copyrighted audio, that portion of the VOD is muted and the associated clips are deleted. The video keeps playing, the sound drops out, and the muted range shows as red lines in the Video Producer timeline.
The important part for a 24/7 channel: the muting happens to the recording, not to the live stream that produced it. Your original broadcast went out with sound. The copy Twitch kept is the one with holes in it.
Twitch exposes that result through its API. Helix Get Videos returns a muted_segments list on every VOD, each entry carrying an offset and a duration in seconds. That is a count and a set of ranges, nothing more. It does not name the track, the rights holder, or the reason.
What the count does and does not mean.
A count of zero means Twitch flagged nothing in that recording. It does not mean the VOD is clear. Recognition is a machine listening for known fingerprints, and a rights holder can act without one.
A high count means several stretches were flagged. That is a useful sorting key. It is not a verdict on any individual track.
A rerun is a new broadcast.
This is the part people skip. Playing a recording of a song to an audience is a public performance, and doing it again on a second day is a second performance. The archive being old changes nothing about the moment it goes out.
So the rerun channel carries its own exposure. It has its own broadcast history, its own VODs, its own clips, and its own record with Twitch. A problem raised against the replay is raised against that channel.
The practical consequence is small and easy to state. Treat the 24/7 channel like a channel you are streaming on today, because you are. The content is a repeat; the broadcast is not.
What to check before queuing.
Four checks cover most of it, and all four take seconds once the catalogue is synced. None of them require watching the VOD.
The first is the muted-segment count, sorted descending. The VODs at the top of that list are the ones worth a second look before they go into rotation.
- Muted segments: how many stretches Twitch already silenced in this recording, and where they fall.
- The games and segments: a music-heavy category, a listening session or a reaction stretch is a different risk from a solo gameplay run.
- Your own music setup at the time: if the broadcast used a licensed-for-Twitch music tool, the stretches covered by it are a known quantity, and the rest of the audio is not.
- Third-party content: watch-alongs, uploaded videos and other people’s streams need a written licence, whatever the muted count says.
Old VODs are the awkward ones.
A catalogue reaching back years was recorded under habits you no longer have. The music policy you follow today was not in force in 2018, and the recording does not know that.
The oldest slice of the archive is the slice to review first. It is also the slice with the highest sentimental value, which is exactly why it ends up in rotation by default.
What VOD247 does, exactly.
Some tools in this space sell a DMCA safety net. VOD247 does not. It replays each VOD in the format Twitch stored it, bit for bit.
So the list is short: signals and switches, not protections.
- It reads the muted segments from Twitch on every catalogue sync, and keeps the count on the VOD.
- It shows that count in the dashboard catalogue, next to the title, as a risk signal you can sort on.
- It replays the VOD exactly as Twitch stored it: a muted stretch airs muted, and nothing is re-encoded.
- It lets you block a VOD, with a reason and a free-text note. A blocked VOD leaves both archiving and playout.
- It does not detect music, scan audio, or identify tracks. Twitch already did the only detection in the chain.
- It does not cut, skip or trim a segment. The playout queue moves whole files.
- It does not replace audio, add narration, or overlay anything.
- It does not decide what is risky for you. The blocklist is the tool; the judgement is yours.
What to do with a risky VOD.
Two options, and both are one click. Block it, or air it with the muted stretch.
Blocking removes it from the catalogue for good, in both directions: it will not be archived and it cannot be selected for the queue. The reason and the note stay attached, which is what makes the decision explainable six months later.
Airing it means a stretch of silence goes out with the video. That is less bad than it sounds on a replay channel. The title carries the replay mention, the tags carry Rediffusion and replay, and the audience already knows it is watching an archive.
Trimming is not an option. VOD247 plays whole files: a VOD airs in full, or not at all.
The checklist.
Run this once on the whole catalogue, then once a month on what the sync adds.
- Sort the dashboard catalogue by muted segments, descending.
- Open the top of that list and decide, VOD by VOD: rotation or blocklist.
- Review everything older than your current music habits, muted count or not.
- Block anything with third-party content you have no written licence for.
- Confirm the replay labelling is on: Rediffusion and replay tags, and the mention in the title.
- Re-run the sort after each full catalogue sync, because Twitch can mute a VOD after the fact.