• 0 Posts
  • 398 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle




  • Streaming allow caching a bit ahead, yes. But the “a bit ahead” part does not mean you can get everything; a server could very well decide to not send more than a few seconds of buffer compared to the realtime play. So, if you’re at 00:00:20 in your video and an 30 second ad is present in the video stream, the server could decide to not send anything beyond the 00:00:55 tag until 30 seconds have elapsed, for example.

    It would be very annoying to code server side, and very annoying for people with spotty internet, but it’s very doable.



  • It’s costly; either you prepare encodes ahead of time with different ads and serve that appropriately, or you splice ads live for each request, which is also costly in resources. You can’t get away with just a few variation; ads are usually targeted. It also come with other issues, like, it is mandatory in a lot of place to clearly identify ads, so there should be an obvious marker somewhere. If it’s in the UI, it can be detected and replaced live by a video of kittens for the duration of the ad, so I suppose they also have to handle any signal in the video… (It’s speculation, I didn’t get any of these yet).

    I’m curious to see if this will hold, and how we will run around it in the long run.