Live Stream Platform


The Live Stream Platform provides the ability to reliably stream content to web viewers via Resi’s Encoders. This process uses the same dependable transport technology found in the Multsite Platform, while also leveraging innovative cloud transcoding to provide adaptive bitrate content to web viewers. Our Live Stream Platform is always being improved upon. To find the most up to date release notes, visit

Web Events

Resi’s Live Stream Platform is an event-based platform, as opposed to a 24×7 streaming platform. Each time you start the encoding process a new event is created that holds the information and media associated with the event. There is no limit on the number of events you can create. The following are the different types of Web Events currently available.

Recurring Live Events

Recurring live events are repeatable events that pull their settings from a specified Web EventProfile.  To simplify video management of recurring live events, a single embed code may be reused from week to week, or from event to event. In these cases, the broadcast would use the embed code from the Web Event profile, which will always point to the most recent event until a new event is started (or until the previous event expires).

Individual Events

A unique embed code is created each time a Web Event is started that can be used to point directly to that Web Event. This embed code is found on the Events tab of Control under “Details” of that Web Event. The individual Web Event embed code is only good until the Web Event’s “Remove Time” which is also listed under “Details”.

Simulated Live

Simulated Live or “Sim-Live” is a broadcast replay of a previously completed event which is intended to appear to the audience as if the event were live. The difference between video-on-demand and Sim-Live, is that with Sim-Live, the viewer is not able to fast forward past the point of the replay that is currently live. For example, if the Sim-Live event started at 9:00 AM, at 9:15 AM the viewer would only be able to see the first 15 minutes of the “replay”, and it appears to be live to the viewer.

Web Event Profiles

Web Event Profiles specify settings for Web Events and provide an embed code for use on a customer hosted website, or through providers such as the Church Online Platform. Web Event Profile embed codes will always point to the most recent (calendar date) Web Event.  New Web Events inherit the following properties of the “Web Event Profile” which was used to create the Web Event:

  • Profile Name – The name of a new Web Event will adopt the name of the Web Event Profile.
  • Embed Code – A snippet of HTML that is “embedded” into a website and creates a video object. The Web Event Profile embed code will always point to the newest (date/clock time) Web Event.
  • Delete After / Remove Time – A Web Event’s “Remove Time” is calculated based on the “Delete After {X} Days” value of the Web Event Profile that was used to create the event. To change how long future Web Events will remain before being deleted, you can modify the Web Event Profile’s “Delete After [x] days” value on the Event Profiles tab under Web Event Profiles in Control for any future Encoded Events.
  • Persistent DASH/HLS URL’s – These URL’s can be used to watch events within an app, or on a device such as Roku and Apple TV respectively. This feature is available on the Pro + Social Web or Enterprise Web plans and can be enabled by submitting a request to Resi’s support team.

Web Event Profile Types

There are 3 types of Web Event Profiles that can be configured within your account in Control: Public, Return Feed, or Social Media Only.

  • Public – A Public Web Event Profile does not have a tag after the name as this is typically the Profile that is set up. Public Web Event Profiles can be used to send to Embed Codes, Social Media Destinations, and Persistsent URL’s. Publc Web Event Profiles are set up to transcode different resolutions and bitrates of video based on the Web Plan (3 for Pro Web and 5 for Enterprise Web) and are viewable by any number of viewers (1-10,000+).
  • Return Feed [RF] – A Return Feed Web Event Profile is a profile that is set up to be used by an additional Encoder set up at a remote site for supervision or Q/A through Web Events. Return Feed Web Event Profiles have multiple bitrate transcoding and are capable of handling a small number of viewers at a time (1-5 Simultaneous)
  • Social Media Only [SOC] – A Social Media Only Profile is configured to only send the highest quality video to YouTube and Facebook individually. The Social Media Only Profile does not provide an Embed Code nor Stream URL’s.

Web Encoder Profiles

Web Encoder Profiles can be selected when scheduling a Web Event, or starting a Web Event manually. Web Encoder Profiles can be made by the Support Team by submitting a support request here. There are a couple options that can be configured for each Web Encoder Profile: Video Field, Deinterlace, and Audio Channel Selection.

  • Video Field – If using a dual channel Encoder and Encoder Profile, we can select a specific video channel to be sent to a Web Event (left or right). The Default selection is the 2nd Encoder input for a dual channel Encoder started with a dual channel Encoder Profile.
  • Deinterlace – In the case that an interlaced Encoder Profile is set up and not deinterlaced on the Encoder itself, the Encoder Event will be interlaced video. Using a Web Encoder profile set to deinterlace will produce progressive video content to the Web (ie. A 1080 interlaced 59.94fps Encoder Event will be deinterlaced into 1080 progressive 29.97fps Web Event.)
  • Audio Channel Selection – In order to send separate audio channels to the Web (audio embedded via SDI or HDMI on audio channels other than 1 and 2.) for use such as a second translated language.

Manually Starting Web Events

Web Events can be started and stopped manually via the Events tab in Control. This is useful in situations where a schedule has not been previously configured. Both live and on demand Encoder Events can be used to start a new Web Event. An Encoder Event must be created in order for a Web Event to be started.

Starting Web Events

1. Within Control, go to the Events tab on the left.

2. Under Events, locate the event with which you would like to create a Web Event, and click the Actions button.

3. Select “Start Web Event”


Each time a Web Event is selected to be started manually, you can choose a variety of options for how and where that video is played back. You can enter a custom Web Event Name, choose the appropriate Web Event Profile, select an additional Web Encoder Profile, select cues for start and stop positions, select playback options, and include Social Media Destinations.

4. Enter a name for your Web Event

5. Select an appropriate Web Event Profile whether that be a Return Feed [RF], Social Media Only [SOC] or Public (no tag).

6. Choose a Web Encoder Profile – This can be used to deinterlace video from an interlaced Encoder Event, or select specific audio channels other than the Default.

7. Start and Stop positions default to the beginning and end of the Encoder Event but can be set to use Cues* added in the Encoder Event Watch Page, Web Event Watch Page, or a Decoder.

8. Choose your Playback option, this will only affect the Embed Code and Stream URL’s as Social Media only receives video in real time.

Realtime playout – Choosing this option will start a Web Event that plays back in real time to the Embed Code. This is ideal for the first live playback of a pre-recorded event or a previous Encoder Event.

Faster than realtime (ASAP), event active immediately – Choosing this option starts a Web Event that can be seen immediately while it’s processed and appears in On Demand format once complete.

Faster than realtime (ASAP), use for next scheduled sim-live – Choosing this options will start a Web Event that is hidden on the Embed Code and Stream URL’s until a Sim-Live schedule replays this Web Event.

9. Add Social Media Destinations.

*Note: The start and stop position specifies the position of the Encoder Event where the Web Event will be started and subsequently stopped. Additional options can be added using cues. Cues for that specific event can be used to as Start and Stop Positions for your Web Event.

Stopping Web Events

1. Within Control, go to the Events tab on the left.

2. Locate a currently running Web Event in your Web Events list.

3. Click on the Actions button.

4. Select Stop to stop the Web Event.

Stopping a Web Event manually that is sending to Social Media Destinations may end at different points in time at the destinations based on how Social Media streams are stopped (immediately) verses the Embed Code (plays out what the Transcoder has received.)

This final confirmation page prevents accidental stopping of the Web Event. Click [Stop Event] to stop your Web Event.

Social Media Destinations are not included in this page.

Web Event Scheduling

Web Event scheduling allows your Web Events to be configured with a one-time or regularly scheduled start-time, and will automatically stop after a predesignated duration. Web Events are designated by a globe to the left of the Web Event description. Web Events are a subset of Encoder Events and are required to be scheduled within the Encoder Event duration. For instructions on scheduling an Encoder Event, please reference encoder scheduling.

Scheduling Web Events

  1. Select or create an Encoder Event with which you would like to create a Web Event.
  2. Click “Edit Schedule” in the bottom left, then click “Add Web Event”.
  3. Add a description for the Web Event schedule. This does not affect the Web Event name. By default, your Web Events will reflect the name of the Web Event Profile used.
  4. Select your preferred Web Encoder Profile and Web Event Profile from the drop down menus.
  5. Designate the Web Event start time and duration.
  6. Add any Social Media Destinations you would like to stream to for the Scheduled Web Event.
  7. Click “Done”, then click “Save Changes”.

Note: If your Encoder Event is configured to be a recurring event, then your Web Event will also be recurring.

Creating a Scheduled Simulated Live Event

To schedule a Sim-Live event…

  1. Go to the Scheduling tab with Control.
  2. Select “Schedule Event” then “Sim-Live Web Schedule” in the top right.
  3. Give the sim-live schedule a description.
  4. Select a Web Event Profile to replay. *
  5. Designate the Sim-Live event start time.
  6. Add any Social Media Destinations you would like to stream to for the Sim-Live Web Event.
  7. Click “Create Schedule”

A sim-live event will play back the most recent Web Event associated with the selected Web Event Profile.

Viewing Web Events

Resi’s platform uses next-generation DASH streaming, and also supports HLS for devices which do not support DASH (iOS, tvOS).

Embedding Web Events on a Website

Customer Hosted Website:

Resi will provide an embed code which will need to be inserted into your desired web page. The embed code will produce a video player with a web stream suitable for your viewers. Your embed code can be found under the Details page next to your Web Event Profile on the Event Profiles tab in Control. Here is an example embed code:

<div id=”Resi-video-player” data-embed-id=”b4291f27-3d5e-1334-a088-ba593eafac33″></div>
<script type=”application/javascript” data-main=”//” src=”//”></script>

Third Party Hosted Services:

  • We recommend trying out the Church Online Platform due to it’s integrated tools and ease of use, plus its free!

Previewing Web Events in Control

Web Events can be previewed in Control for testing and quality assurance. You can also view and test cues set by Multisite Decoders. Web events can be viewed individually via the Events tab, or you can choose to preview the content from the Web Event Profile itself which will always show the live (or most recent) content. The Web Event Profile can be found on the Event Profiles tab.

Video Review

Resi Video Review

Video Review can be set up on any user account in your organization. Video Review can be used to view any current Web Event in your account, without having access to start or stop the Encoder, Schedule, or change passwords. This is particularly useful for viewing and supervising Web Events from multiple campuses. Your Video Reviewers can add Web Cues at any time in the Web Event to highlight different spots in your service. 

Device Support

Because the Live Stream Platform technologies are forward-looking, older technologies which are no longer being updated by their manufacture may not be supported. All media content conforms to the Common Media Application Format (CMAF) specification.

Unsupported devices may include:

As of February 2018, real-world observation and analysis has shown that over 94% of viewers are able to participate in live events when using next-generation DASH streaming.


Event analytics show viewer data for the given Web Event. This data includes total viewership, viewer resolution, and duration of the Embed Code only. This information does not include views on third-party players which use a Persistent (DASH or HLS) URL nor Social Media views. Event analytics can be accessed in Control by navigating to the Events tab and selecting Analytics next to your desired Web Event. This page auto refreshes once every minute while the Web Event is live to keep up to date with new viewers.

The analytics for each Web Event is based off of the views of the Embed Code only. Each view is counted after 90 seconds of watch time. The data we show includes Views, Unique Viewers, Average Watch Time, Watch Time, and Resolution. A CSV report can be downloaded by clicking “Detailed Report.” Analytics Reports will show a timestamp of the view, location data, watch time, resolution, and device and browser information. Viewers by Location breaks up in to three catagories: City, Region, and Country.

  • Views: Counts all views of the Embed Code, this number includes if the viewer refreshes.
  • Unique Viewers: Counts all unique viewers of the embed code. Each unique viewer is only counted once even if they refresh.

Geolocation information is accurate to a city level based on the location of each viewer, exact location cannot be determined. There are two catagories to view geolocation information: Heatmap and Location Pins.

  • Heatmap: Uses color to highlight the number of viewers in each city. A city with a small number of viewers will be green, and a city with a high number of viewers will be red.
  • Location Pins: A pin appears on each city which has 1 viewer or more. You can hover over a pin to see how many viewers were associated with that city, and you can click on a pin to permanently display the viewer count across multiple pins.


Resi uses YouTube API Services  for Live Stream Platform content to be streamed to a YouTube channel via a Stream Now event. Please view their Privacy Policy here: Google Privacy Policy, and please review YouTube’s Terms of Service here: YouTube ToS.

Similar to the Live Stream Platform, YouTube content is delayed by two minutes to improve playback reliability. Your YouTube channel will need to be configured for YouTube Live if you have not already done so. YouTube requires a 24 hour waiting period for live streaming. Check out YouTube’s setup instructions here. We will make the following changes to the YouTube event when starting a stream:

  • Title (based on Control setting)
  • Privacy (based on Control setting)
  • Latency forced to “normal”

The steps for configuring YouTube integration in Control are detailed below.

Linking your YouTube account

  1. In Control, click “Social Media” in the left menu.
  2. Under YouTube Accounts, click “Add YouTube Account”.
  3. Click “Continue to YouTube” to sign into your account.


The “Status” column indicates the current status information for the associated social media accounts. You can expect to see the following: 

  • Access verified: We verified this channel has live streaming enabled. 
  • Not allowed to Live Stream: We verified we have access to this channel, but the user hasn’t enabled Live Streaming yet (or hasn’t waited 24 hours after requesting it to be enabled).
  • No access: We cannot access this channel. This usually happens if the Resi app permissions have been revoked, or access has expired. You can re-authenticate to regain access to the channel. 

Scheduling YouTube Events

To schedule YouTube alongside your Web Events:

  1. Go to “Scheduling” in the left menu.
  2. Create a new Encoder and Web Event schedule, or select an existing one.
  3. Under Web Events, click “Edit” next to the desired web event.
  4. Click “Add Social Media Destination” and confirm your settings.
  5. Once the social media destination has been added, click “Done” and then “Save Changes”.

Web events with social media enabled should be scheduled with five minutes of leeway between previous and future web events.


Facebook integration allows for Web Events to be streamed to a Facebook Page, Group, or Timeline for anyone within North America, Europe, and Australia . Facebook accepts streams up to 1080p at 60fps from Resi with stereo audio. Facebook Streams play back approximately 2 minutes behind live.


Privacy: Privacy within Facebook that allows certain viewers to see Posts made by the user (Public, Friends of Friends, Friends, Only Me).

Published: Video can be seen by anyone who has access to it set by the Privacy.

Unpublished: Video is not live to Facebook and will can not be seen by anyone, regardless of Privacy.

Web Event preview window: A preview of the Web Event that can be found under the Watch action button.

Facebook Policy Reminder

By using Resi to stream to Facebook you are agreeing to Facebook’s ToS – including: not streaming copyrighted content, not including third-party advertisements in your video content, not streaming looping images or static slides, and clearly distinguishing any pre-recorded content from live content.

Authorizing a Facebook Account

Resi uses Facebook Accounts to stream to Facebook Pages, Groups or Timelines. Users will need admin access to the Pages or Groups they wish to stream to, Resi requires access to stream to account timelines in order to stream to Groups or Pages. Posts to Pages appear as the Page going “live” and Posts to Groups appear as from the admin account, Posts to Timelines appear on the linked admin account’s timeline.

In order to send to your Facebook account through Resi, you will be required to give permission to Resi to post on your behalf.

  1. Within Control, navigate to the Social Media tab.
  2. Click “Add Facebook Account,” and then “Continue to Facebook.”
  3. Once redirected to Facebook, “Continue as Yourself.”
  4. Set the privacy of all posts that are created, this is the maximum availability for all subsequent Facebook Streams. Setting this as Public is recommended.
    1. Posts to Pages are required to be set as Public.
    2. Posts to Timelines and Groups can be set to a lower privacy than this original setting, but not a higher one.
    3. An account will need to be removed and re-authorized to change this setting.
  5. Allow access to the groups/pages where the live video will post.
    1. Select specific groups here by clicking “Choose what you allow” and toggling which pages can receive content.
    2. This can be changed at a later date within Facebook under Settings >> Business Integrations >> Resi >> View and Edit.

Scheduling a Stream to Facebook

The easiest way to setup a Facebook stream is through a Schedule in Control.

  1. Create a new Schedule or edit an existing Schedule with a Web Event.
  2. Within the Schedule’s Web Event section, click “Add Social Media Destination”

3. Select the following settings.

    1. Social Media Account
    2. Destination (Group, Page, or Timeline)
    3. Privacy – Pages can only be posted to as Public. Timelines and Groups can be set to a more private audience (Friends of Friends, Friends, or Only Me.)
    4. Publish Status – If you choose Published, the Facebook feed will be visible from the beginning of the Web Event. If you choose Unpublished, you will have to manually transition the feed to Published in order for your viewers to see the feed.
    5. Title – Fill in your video title here as it will appear on Facebook. This will display on the live video.
    6. Description – Fill in your video description here as it will appear on Facebook. This can be seen on the Facebook live video as well as the Facebook post.

4. Click “Done” to save those settings.
5. Once those changes are saved, “Create Schedule” or “Save Changes” 

Manually Starting a Stream to Facebook

In order to manually start a Facebook Stream a new Web Event will need to be created with a Social Media Destination of Facebook.

  1. Within Control, navigate to the Events tab.
  2. In the Actions on the Encoder Event you want to stream to Facebook, click “Start Web Event”

3. Configure your Start and End points to reflect what will be streamed to Facebook whether that’s from the beginning of the Encoder Event or from a Cue.
4. Add your Social Media Destination and set the following properties:

    1. Social Media Account
    2. Destination (Group, Page, or Timeline)
    3. Privacy – Pages can only be posted to as Public. Timelines and Groups can be set to a more private audience (Friends of Friends, Friends, or Only Me.)
    4. Publish Status – If you choose Published, the Facebook feed will be visible from the beginning of the Web Event. If you choose Unpublished, you will have to manually transition the feed to Published in order for your viewers to see the feed.

5. Click “Done” to save those settings.
6. “Start Web Event” will start a Web Event based on the Start Position and Stop Position. This Event will play back in real time to any Social Media Destinations.

Publishing a Stream to Facebook

In order to comply with copyright restrictions, Web Events sent to Facebook can be Published at a specific time after a Web Event starts. Start by previewing and then Publishing a Facebook Feed from Control, in the Web Event preview window. This can be found in the Events page by clicking the Watch button on the specific Web Event. 

On this page, there will be a link to the video within Facebook once the Web Event is Published. If the Event is currently Unpublished, it can transition to the Published state on this page by clicking “Publish / Go Live.” The Facebook feed will start Publishing to Facebook from within 10 seconds of the content which is showing in the Facebook preview window.

Stopping a Stream to Facebook

Whether a Facebook Stream was started from a Schedule or started manually, stopping a Facebook stream can be done within the Web Event preview window. There is a “Stop” button next to the “Publish / Go Live” button. Pressing this will bring up a confirmation window to initiate the stopping process.

Once the stopping process has been initiated, the Social Media Destination will stop in approximately 30 seconds. Selecting the Cancel option will not stop Social Media Destination to Facebook.

To stop the all Social Media Destinations as well as the Web Event, simply stop the Web Event in the Actions drop down menu. 

Sending a Stream to Facebook Groups

In order to Post to Facebook Groups, a Group admin will be required to add the Resi Facebook Application to your Group. Without permission for the Resi Facebook Application to post, the Facebook Stream will not be able to start.


  1. Navigate to your Group Settings.
  2. In the “Apps” section, click “Add Apps”
  3. Search for and add the “Resi” Application.

Crossposting to Multiple Facebook Pages

Crossposting can happen between two Facebook Pages that have permissions set within Facebook. Facebook’s own documentation on how to set up Crossposting can be seen here:

In order to Crosspost through Resi, the Social Media Destination must be set to a Facebook Page. Crossposting options will not show up if a Timeline or Group is selected as a Destination or the selected Page has no Crossposting relationships.

The number of Crossposts on a Web Event can be seen in a couple different areas: the Web Event Details, the Web Event preview window, and the Schedule view/edit page.

Web Event Download

Within Control you are able to directly download your Web Events. To download a specific Web Event in Control, head to the Events tab. Click on the Watch button for your Web Event, this will take you to the Web Event Preview Window.

Click the “Download” button under the embedded player, this will bring up different options to download the Web Event.

  • Video: Video options will show you the available resolutions and bitrates available for download, this will vary with your Web plan as well as the Web Event Profile that was set up.
  • Audio: Audio options will show a stereo feed, which will be your source audio or a transcoded version of the first and second audio channels if you’re using an Encoder Profile with 4 or more audio channels.
  • Start Position: Sets the beginning point of the download. This can be a Web Event Cue or the beginning of the Web Event.
  • Stop Position: Sets the end point for the download to stop. This can be a Web Event Cue or the end of the Web Event.

Once your download options are finalized, click the “Download MP4” button. This will start the download in the background and a confirmation notification will appear at the top of the window. You can then close the window and wait for your download to complete.


  • Web Event Downloaded files are up to ISO 14496-12:2012/2015 specification for mp4 files but may not show audio properly if brought directly into Adobe Premiere and should be re-encoded first with Handbrake (using the same codec and constant framerate) or ffmpeg (using -c copy to re-contain the video and audio.)
  • If you are attempting to download a Web Event that’s currently live, a web event cue must be set as the Stop Position. The “End of Event” option is not available.
  • If your Download uses Cues for a Start or Stop Position, there may be up to 6 seconds before or after the selected Start Position Cue or Stop Position Cue respectively.

Previous Page


Next Page

User Management