SlideSync is a webcast tool that is entirely operated through the browser. It can stream content from any video or audio equipment that produces RTMP or RTMPS. There’s no additional software to install.
The RTMP(S) content is streamed to the SlideSync servers for processing and transcoding, and distributed globally by our CDN to attendees through their browsers.
On the production site
Whenever possible, use cables on the devices doing the streaming. The quality of wireless connectivity (WIFI / LTE) can fluctuate, especially if you have an on-site audience who bring wireless devices. Or microwave ovens in nearby rooms.
On the devices used to control the tool (approve questions from the attendance, switch slides, start and stop the event…), wireless connectivity is more than sufficient.
In 720p, SlideSync will require a single-channel video bitrate of 3 Mbit/s. So the minimum recommended bandwidth is 5 Mbit/s. Don’t forget the connection will be used for a variety of other services.
In 1080p we recommend 10 Mbit/s per channel. See “backup stream” below.
On the viewer side
Video quality is adjusted to the bandwidth. However, to ensure good quality, 2 Mbps of bandwidth should be available per viewer, with a minimum of 300 kbps per viewer for low-resolution video.
For audiocast events, 100 kbps per viewer are sufficient.
To optimize internal bandwidth distribution, we recommend installing SlideSync CDN Edge nodes in the relevant company locations.
SlideSync can work with a primary and a backup stream for the same content. The distribution will seamlessly switch to backup if the primary stream becomes unavailable. For obvious reasons, the backup stream should be sent via a separate uplink when possible.
If you only have one uplink, then both primary and secondary can be sent together. However, MediaEvent Services can deliver secondary connectivity to virtually all event locations around the globe by means of a satellite uplink or a leased line. For some events, a separate backup stream is absolutely necessary. Contact us for more details.
A production using SlideSync only requires DNS service as well as outgoing (NAT) connectivity to *.slidesync.com on TCP ports 443 and 1935.
For metrics: app.getsentry.com
Please do not whitelist individual target IPs or networks as they may change due to scalability and fail-over considerations. Rather, whitelist origin devices by their internal IP and/or MAC ID.
SlideSync’s System Test will make sure everything is in order.
If Quality of Service is enforced in the company network, it might be a good idea to have a look at the rules and make sure they won’t penalize SlideSync traffic, either up or down.
If fact, you might want to add a temporary rule to prioritize it.
If you encounter issues receiving emails from SlideSync, please whitelist the following sender addresses:
If Internet Explorer is configured to use the High-security level or a custom level for the Internet zone, you may need to add *.slidesync.com to the list of Trusted sites. When in doubt, please contact our support for tailored advice.
Caching for Enterprise Networks
For content distribution over a large network, SlideSync supports multiple caching infrastructures to reduce bandwidth consumption and prevent critical overloading of Internet connections.
In fact, we can install pre-configured Edge nodes in relevant locations. Do not hesitate to contact us. However, SlideSync may also be used with existing caching proxies that meet the following requirements.
- SlideSync is delivered over HTTPS only. As such, caching proxy must support HTTPS caching.
- SlideSync uses HTTP Live Streaming via Apple HLS. Therefore, the caching proxy must either explicitly support this protocol and/or honor the Cache-Control headers returned from our platform (i.e. not enforce any higher TTLs)
The following subdomains are currently used for CDN distribution:
- https://liveplayout-prd-pri-clf-aws-eu-west-1.slidesync.com (live)
- https://assets-prd-clf-aws-eu-west-1.slidesync.com (on demand)
SlideSync events are automatically recorded on the remote server by default. However, the recording may be interrupted in the case of a network problem.
If you need to make sure that you will have a full recording of the event, you should also record locally, either via your camera if it supports it, or via dedicated hardware. If you do encounter any network issues, you can then upload your local recording to SlideSync after the event for attendees to watch later.
Note that this backup recording is unrelated to the backup stream we mentioned earlier. Ideally, the backup recording should be done locally.
Rehearse the presenter workflow
We recommend that you test the whole workflow, including interactions, with a test event. This will minimize the chances of having any problems with your event. The Presenter Guide shows you which steps a presenter should test out before their event.
Try to have someone remote to test the client-side of things.
Be available on the day of the event
Live events can be very stressful. The staff on-site will be much relieved to know you’re on call.