Follow

Setting up Live Stream with the Worship Stream upgrade

Congratulations on upgrading your Custom Church App with live streaming! This upgrade provides a cost-effective solution for broadcasting your services to users of your mobile app.

Setup Your Streaming Encoder

This document covers setup of two different streaming encoders:

 

Setup Adobe Media Live Encoder

You can get Adobe Media Live Encoder from Adobe’s web site at http://www.adobe.com/products/media-encoder.html.

Once you have installed and run the application, select your video device and audio device. After that, your video should be showing in the monitors at the top of the program. Here are some suggested settings for streaming to your app:

  1. Set the video format to H.264. Next to this box, click the “wrench” icon and set to Baseline, 3.1, and 5 seconds
  2. Frame rate: 30 fps
  3. Input size will be based on your video setup, but we recommend something between 640 X 480 and 1280 X 720
  4. Bit rate should be set to 300-500 kbps
  5. Output size should be set to match whatever you used for input size in Step 3
  6. If you have the option to check the “Deinterlace” box in the bottom left, do so.
  7. Audio format should be AAC if possible; if not, use MP3
  8. Channels: Stereo
  9. Sample rate: 44100
  10. Audio bit rate: 64-96 kbps
  11. Enter the FMS URL (obtained from the “Live Streaming” section of your Custom Church App console) into the box on the right side of the program. It is best to copy and paste this info, but please make sure there are no spaces or any other characters at the beginning or end of what you paste into this box. Here is a sample:

    FMS URL: rtmp://fso.lax.XXXXX.alphacdn.net/20XXXXX

    *** NOTE: The “lax” in the code above can be replaced with “dca”. Either should work, but we recommend using “dca” if you are streaming from the eastern half of the US/Canada and using “lax” if you are streaming from the western half of the US/Canada. ***

  12. Enter the Stream Name (obtained from the “Live Streaming” section of your Custom Church App console) in the box labeled Stream. Here is a sample:

    Stream Name: cca2x4x6x?w0gfVaqYP4R93GJY

  13. Once this is done, you should be ready to stream! Simply click the Connect button on the right hand side, and then click the Start button at the bottom. It can take about 30-45 seconds for the stream to appear in your app.

Setup Wirecast

You can find out more about Wirecast and purchase it from Telestream’s web site at http://www.telestream.net/wirecast/overview.htm. Once you have installed the app, perform the following steps:

  1. Select Output Settings from the Output menu at the top.
  2. Destination should be RTMP Server; click OK
  3. In the address box, you need to put your FMS URL (obtained from the “Live Streaming” section of your Custom Church App console). Here is a sample:

    FMS URL: rtmp://fso.lax.XXXXX.alphacdn.net/20XXXXX

    *** NOTE: The “lax” in the code above can be replaced with “dca”. Either should work, but we recommend using “dca” if you are streaming from the eastern half of the US/Canada and using “lax” if you are streaming from the western half of the US/Canada. ***

  4. Under the Address box, delete whatever is in the Stream box. Then copy and paste your Stream Name (obtained from the “Live Streaming” section of your Custom Church App console) in this location. Here is a sample Stream Name:

    Stream Name: cca2x4x6x?w0gfVaqYP4R93GJY

  5. Above the the Address box there is a drop-down menu for Encoding; click the little gear icon beside it that is off to the right side and select View Details. Make the following changes to these settings:

    • Encoder: MainConcept H.264
    • Width and Height will be based on what your video set up is. We would recommend using something between 640 X 480 and 1280 X 720.
    • Frames per second: 30
    • Average bit rate: for mobile in-app streaming we would recommend setting this in the 300 – 500 kbps range
    • Profile: Baseline
    • Key frame every: 240 frames
    • Audio settings to: Stereo; 64 kbps; and 44.100
    • Once those settings are changed, click the Save As button at the bottom and name the new preset (call it WorshipStream 1, or something like that)
    • Then you can click to close the window
  6. Click the Encoding drop-down menu right above the Address box and select the new preset you just created (WorshipStream 1). It will probably be at the top of the options.
  7. At this point you should be ready to stream! Simply click the Stream button at the top left of the program to start streaming. It may take 30-45 seconds for the stream to appear in your app.

Setup Your Mobile App To View Live Streaming

You can configure your live stream upgrade on any button or tab. In this example we will add a new home screen button for this.

  1. On the Home Screen section, find the Button Container component and click it to open its properties.

  2. To add a new button, click the “+ add” button. You will see an editor like the one below.

  3. Edit your button’s icon and Label however you wish.
  4. Under the Click Action selector, choose “Display a media source”.
  5. Under Media Source, select “+ New Media Source”.
  6. Click the “Add Media Source” button. You’ll be presented with a set of media sources to choose from.

  7. Select the “Live Stream” item. You’ll see an editor like the one below.

  8. Edit the Title of your stream. This is only for your own reference.
  9. Under the WorshipStream banner, check the “Use your Live Stream Upgrade from WorshipStream” checkbox. Some of the options in this screen will disappear since they are configured automatically at this point.

  10. Click the “Done” button at the bottom to exit each editing page and return to the Home Screen section.
  11. Click the yellow “Save Changes” button in the upper right area of the console.
  12. Click the green “Go Live” button in the upper right area when you are ready for your changes to show up in the app.
  13. Now try using your stream encoder software to start a live stream, and then try out the new button in your mobile app.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request