![]() In this scenario, Bob would end up missing some program content when catching up with Alice. Or she can continue with the main program and Bob would then jump ahead to catch up with Alice so that they stay in sync. Once Alice finishes her ad, she can then wait for Bob's ad to finish before resuming together in sync. So now, if they were to play in sync, one of two experiences is possible. But sometimes they might get ads of different durations, or one of them may not have any ads at all. Now, after watching the ad, both of them would resume playback in sync. ![]() This would be our preferred experience as well. For that to be possible, we'd expect the durations of the ads to match. In the ideal case, the experience shouldn't be too different from where they were watching the program alone. For this let's consider a simpler timeline where each of them have just the single ad stitched in. Now let's take a moment to think about the user experiences that would be possible in scenarios such as these. And if we were to look at some arbitrary time in the presentation timeline, they would be watching completely different portions of the content. For Bob, the network banner might appear at the very beginning, but for Alice, it would appear only after the warnings are shown. We can now see how this might pose a challenge when trying to get them to play in sync. It could be that these ads are of different durations. But now, let's say Alice's geography requires that the service show some statutory warnings before the start of the program, and there might also be ads scheduled at different points within the program. This is fairly typical, and since the recap segments and the banners match for Alice and Bob, coordinated playback is still achievable. Now lets say each of them have a program recap segment stitched in, which is preceded by the studio or network banner. You'd simply associate the groupSession with the playbackCoordinator, and you'd be good to go. If it is only the program content that they're watching, then it should be pretty straightforward to achieve coordinated playback. Now what we see here are the presentation timelines at their respective ends. While this works well if all the participants are watching the same content, what would happen if some of them have ads? Now let's take a look at the case where Alice and Bob are trying to watch some program content. So while participants are in a FaceTime call, the playback control commands originating on one participant's device are shared across group so that they all play in sync. Lets see how coordinated playback works in SharePlay. And to conclude, we'll go over some best practices that you can use to provide people with a really compelling SharePlay experience. And we'll also see how HLS interstitials work with coordinated playback. We'll then see how one might achieve these for stitched-in ads. Following that, we'll discuss the different viewing experiences that are possible when watching ads. ![]() Then we'll go over the challenges associated with ads and other interstitials in coordinated playback. In this talk we'll start by going over how coordinated playback works. So if you're interested in scheduling ads and other interstitials for coordinated playback in SharePlay, you've tuned in to the right session. However, some of you might have targeted ads or other interstitials scheduled in the content timeline, making it a challenge to coordinate playback between participants that receive ads of different durations or say between a mixed set of participants where some receive ads and some don't. With the introduction of SharePlay, you can provide people with a connected viewing experience that lets them navigate through and interact with content in real time all while staying completely in sync with the SharePlay group. I'm an AVFoundation Engineer, and welcome to WWDC2022. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |