streaming to Switchboard Live. Again, on the right is
the Stream Link where you can switch between the
two live inputs.
2. Configure your destinations. Destinations are the
target services, and you can see the target services
I’ll be streaming to in Figure 3. There are three types
of destinations shown.
The Facebook, Periscope, and You Tube accounts
are all template-based. You click to select them, log
into your account, and give Switchboard the necessary
rights. Easy peasy.
The Ustream account is a custom RTMP account that
I manually configured by retrieving the RTMP address
and stream name from my Ustream account and con-
figuring that into Switchboard. It’s iden-
tical to the procedure you would follow if
you were streaming directly to Ustream
via a separate encoder.
The final destination type is Switchboard Delivery. This type provides an
embed code that you use to deploy the
player into your own website for HTML5
delivery. Or, you can grab the URL of an
HLS master manifest to plug into an existing player deployed on your website
3. Request third-party destinations. All
destinations shown in Figure 3 are accounts we had direct access to. To stream
to third-party sites, you add a destination type called Stream Share, which
opens the wizard shown in Figure 4. This
walks you through the process of describing the event (shown), and then sends an email to the
third party. This email contains a link they can click to
provide the necessary authorization to send video to
their account, so you can stream to their service without ever seeing their credentials. Once it’s set up, the
third-party site appears just like any other destination.
This is an incredibly powerful feature. For example, say you were planning a live interview of a candidate for a political office. Using Stream Share, you
could distribute the stream to all Facebook pages of
all organizations in the state, or even the country, so
long as they gave you permission. This would be impossible for most organizations without a service like
4. Create workflow templates. I’ll use two workflows
for this event: one for Facebook Live, the second for
all other services. The easiest way to do this is to create a template for Facebook Live, then duplicate the
template and rename as needed.
I’m creating the template in Figure 5 (on page 164),
inserting the title, description, tags, and similar content. This text and metadata will be injected into the
similar fields supported by most live-streaming services. Once I create the first template, I click the Duplicate icon on the upper right (next to the + sign),
then make any changes and save the second template.
Note that you don’t need to create a template; you
could enter all this information directly into the workflow. It’s just easier for repetitive use with the template.
5. Create workflows and configure destinations.
Every stream has its own workflow, but in this case I’ll
only configure two: one for all Facebook Live accounts,
the second for all other accounts. I’ll do this and a lot
more in the screen shown in Figure 6 (on page 164).
Here are the destinations for our streams.
Requesting access to a third-party account