Issue with Google Slides & Timing / How does Rise Cache Presentations?

  • 1
  • Question
  • Updated 3 years ago
  • Answered
Hi there,

We are attempting to embed a Google Slides presentation with 3 slides as part of a larger schedule. There about 7 total presentations within the schedule sequence.

Our question is first: does Rise load each presentation (and associated playlist items) when the entire schedule is called the first time? I have to assume yes, because:

When our Google Slides presentation comes up (third in the schedule) it does not land on slide 1. It lands on slide 3, and then loops back to one. Each slide is given a full 20 seconds (as specified in the embed code), but the third slide is broken up as follows:

Slide 3: ~6 sec
Slide 1: 20 sec
Slide 2: 20 sec
Slide 3: ~14 sec

The main issue here is: how can we get the Google Slides slides to play sequentially? If we turn loop "off" then when the schedule loops for the second iteration, it just show the last slide (for 60 seconds). Turning off auto-play is not a good option either: it would just show Slide 1 for 60 seconds.

You can see our rotation at: 9700c24b-4d0b-48ab-b19b-fe128642c4a2 

The Google Slides in question start with "Superintendent's announcements," after its intro slide.

Thank you for any assistance.
Photo of Samuel Hartman

Samuel Hartman

  • 806 Points 500 badge 2x thumb

Posted 3 years ago

  • 1
Photo of Matthew Fisher

Matthew Fisher

  • 1,420 Points 1k badge 2x thumb
Samuel,

You are correct in your first question.  All of the content is downloaded and parsed before anything begins playing (that includes sub-presentations as well).

Unfortunately, there are some flexibility limitations when using Google Slides like that.  The bottom line is that the slideshow starts at the same time as the other content in that presentation/placeholder.  The visibility is what changes when it's supposed to be on the screen.  The only way to ensure correct order and timing is to have it be visible at all times and not part of a rotation.

Thanks,

Matthew