this post was submitted on 23 Sep 2024
553 points (97.3% liked)
Technology
59314 readers
4603 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It wouldn't cost any CPU with custom software that Google can afford to write. The video is streamed by delivering blocks of data from drives where the data isn't contiguous. It's split across multiple drives on multiple servers. Video files are made of key frames and P frames and B in between the key frames. Splicing at key frames need no processing. The video server when sending the next block only needs a change to send blocks based on key frames. It can then inject ads without any CPU overhead.
Wouldn't it still need overhead to chose those blocks and send them instead of the video? Especially if they're also trying to do it in a way that prevents the user from just hitting the "skip 10 seconds" button like they might if it was served as part of the regular video.
It has to know which blocks to chose to get the next part of the file anyway. Except the next part of the file is an ad. So yes there is overhead but not for the video stream server. It doesn't need to re encode the video. It's not any more taxing than adding the non skip ads at the beginning that they already do.
Compared to the cost of reencoding the video (or even segments of it) it would be basically nothing, though.
You're forgetting the part where the video is coming from a cache server that isn't designed to do this
They're already appending ads to the front of the video. Instead of appending an ad at key frame 1 they append the ad at key frame 30,000.