This last Sunday, our wireless may have bounced off then on again in our worship space. By the time we got ready to move into a liturgy sequence (a couple of songs bookending a couple of content slides), the songs weren't there, nothing appeared on the screen. The service content had just vanished, or so I was told by our AV person. I had a moment where I could take a look at the AV computer mid service, and the slide backgrounds had disappeared. I closed Proclaim, opened it again and the backgrounds loaded. I think we had white type on white backgrounds and hence the appearance of "vanishing" content. My question is whether the elements used to build a particular service are cached locally or always downloaded from the Bellingham servers. I think something happened during the service, that connection was momentarily broken and that interruption stopped Proclaim from streaming in the backgrounds. Can those elements be cached locally so minor interruptions are not game stoppers? We're starting to question the wisdom of the SaaS model with something as mission critical as Proclaim is on Sunday mornings. I'm struggling to answer the "why not just put the presentation on a thumb drive and run it locally?" question.
