If you have ever given a live presentation at a conference or meetup then you know only too well that the number of problems you experience with your slides, microphone, remote control device, etc. is directly proportional to the size and importance of your audience ;-)
GitPitch understands your pain. And offers the following pain-killers for common scenarios:
Depending on the conference Wifi to serve your slides reliably when standing on stage in front of a live audience can be a little like walking a tightrope without the benefit of a safety net. While possible. It is rarely recommended.
Breaking all dependencies on the conference Wifi and network connections in general is one great way to keep the demo gods at bay. And for this, GitPitch offers comprehensive offline support.
GitPitch Desktop is a dedicated desktop tool for working and presenting offline. It can be used to develop, preview, and present slides offline. With zero dependencies on the network. This makes it the perfect antidote to the demo gods. You can learn more about GitPitch Desktop here.
There are times when a conference organizer will insist that you present your slides using a dedicated conference laptop that is pre-configured and pre-connected to the conference audio and display systems.
In these circumstances you rarely have the luxury of installing your own presentation software, such as GitPitch Desktop, on their device. Which typically means you will be downloading your slideshow over the network to the conference laptop prior to going on stage. More often than not, during a pre-conference A/V check.
If this is the situation you are likely to face then it is important that you understand a little about GitPitch lazy-loading policies. These policies apply to the loading of slideshow assets, such as images and videos that you display on your slides.
By default, GitPitch uses a lazy-loading strategy for slideshow assets. This means that only a small number of the images used by your slideshow are loaded when you first open your slideshow in your browser. Only when you start moving through your slides, GitPitch detects upcoming slides that need to display image assets and it will automatically fetch those images. You can think of this as a just-in-time loading strategy for your slideshow assets.
This strategy makes a lot of sense when you are sharing your slideshows online. But in the context of a live slideshow presentation when you first load your slides during an A/V check potentially hours before going live on stage, this just-in-time strategy may leave you exposed to the demo gods if the network goes down at any point after your initial check.
For this eventuality, GitPitch supports an eager-loading slideshow setting. It can be activated in the PITCHME.yaml for any presentation as follows:
eager-loading : true
When activated, this setting ensures that all slideshow assets are loaded over the network when you first open your presentation in the browser. This greatly reduces the risk inherent in unreliable conference Wifi when you are live on-stage.
Note, this approach still runs the risk of the browser on the conference laptop evicting your slideshow asset dependencies from the browser cache before you go live on-stage. For this reason, this eager-loading approach is only recommended if you can not export and present your slide deck as PTTX or PDF.
Sometimes conference organizers will insist all slideshow presentations be submitted ahead of time as Microsoft PowerPoint (PPTX) or PDF files. GitPitch Pro users can use Desktop Pro to export your slide deck as a Microsoft PowerPoint slideshow or PDF.
For further details, see the Desktop Pro Guide.