We are testing Proclaim and are very attracted to the ability to collaborate during the week from different locations on the same presentation. Music, video, and announcements can now be inserted by the authors rather than the central media guy. Great!
But I notice that Proclaim is downloading the presentation (locally?) when I log in to a different machine. So I've created the test program in my office and am viewing it in the worship center. The download, while not burdensome, is lengthy. Help me understand what is happening.
1) Does Proclaim download the scheduled program content on each machine running the GUI?
2) Does that mean Proclaim can be run without an internet connection (once the download has finished)?
3) Does this download need to complete before we go "On Air"? What happens if we roll without the download completing? (Some conferences might have several missionary videos making the entire presentation quite large). Sadly, if our sound guy is running late at work on Wednesday night, he might pop in to our Bible study 5 minutes before service time. (just sayin' [:'(])What then?
4) To what location does all this content download? Can that be defined by the user? Should disk space be a concern after a year of running the software? Is there a best practice on how many presentations should be loaded?
I'm trying to understand so we can better anticipate our work flow when we go live. We anticipate purchasing a license at some point.
PS - The ability to integrate DVD into the presentation is a really big deal to us. We have visiting missionaries come with presentations that we need to figure out how to schedule in the service. Would be nice not to have to flick the projector over to the DVD player, leaving the worship program.
