Church live video and audio streaming

It's time to stream

Our Wowza Streaming service uses the award-winning Wowza Streaming Engine to provide you with high-powered live broadcast and on-demand video streaming. Wowza effortlessly streams to flash player, silverlight, iPhone, iPad, Android and Blackberry devices. Our Wowza control system gives you statistical bandwidth/viewer graphs and even GeoIP viewer maps you can embed in your website.

live video/audio streaming pricing

Lean Stream

 25/month

Live Video Streaming

50GB Monthly Bandwidth

No Bitrate Limit

Unlimited Viewers

Free Setup

supreme stream

 50/month

Live Video Streaming

100GB Monthly Bandwidth

No Bitrate Limit

Unlimited Viewers

Free Setup

extreme stream

 75/month

Live Video Streaming

125GB Monthly Bandwidth

No Bitrate Limit

Unlimited Viewers

Free Setup

scream stream

 100/month

Live Video Streaming

150GB Monthly Bandwidth

No Bitrate Limit

Unlimited Viewers

Free Setup

AMAZING FEATURES


Streaming bandwidth / user statistics reports / GeoIP statistics allow you to map your viewers / Embed player, viewer map and more into your websites 

iPhone / iPad / Android compatible.

Maximum Reach

Today's online media consumers are just as likely to be visiting your website with a tablet or smartphone as with a traditional computer and web browser. Wowza Media Server provides native support for Apple iOS devices, Android and Blackberry, so you can accommodate your mobile viewers. The popular JW Player flash player has native iOS detection and support, and we provide sample players deployed to new service as well as knowledge-base articles with instructions for configuring JW player for both flash and iOS compatibility.

Usage Statistics

We record current streaming connection counts every single minute of every single day. Within your Greedbegone online account you can view connection details and stay on top of concurrent connection trends. We even break it down by type of connection (flash, Silverlight, iOS, RTSP, etc.) For more detailed analysis of your streaming users, we recommend CasterStats Reporter, a third party product which provides a wealth of details about your streaming users.

Cast Control Panel

Control of your Wowza streaming is handled by the Cast Control streaming control panel. Within Cast Control you'll have access to your streaming details, usage graphs, live GeoIP viewer maps, and more. Cast Control will provide you with embed code for browsers and mobile devices. If you are using IP cameras you'll be able to set the URL to your camera from within Cast Control.

HARDWARE RECOMMENDATIONS


Below are some hardware recommendations that we've had experience working with.  We highly recommend researching the brands that best suit your budget and application.  Should you have any questions with regards to anything listed below, please feel free to contact us.


Canon VIXIA RF700

Discover a world of new shooting possibilities with VIXIA HF R500 camcorder's giant 57x Advanced Zoom! Get up close from virtually anywhere and feel free to walk while shooting: the camcorder's SuperRange Optical Image Stabilizer will keep your video sharp and steady. Capture truly impressive, amazingly realistic 1920 x 1080 Full HD video with the Canon 3.28 Megapixel Full HD CMOS Image Sensor and DIGIC DV 4 Image Processor....


Magewell XI100DUSB-HDMI [ Mac & PC ]

USB3.0 HDMI/SDI capture dongle does not need a driver (real plug and play devices). They are compatible with Windows/Mac OS/Linux, USB3.0/2.0 and various stream media applications and provide users with many audio/video processing features.


Kanexpro HDMI Extender Over Cat 5E/6 [ 165' ]

The KanexPro HDMI Extender over CAT 5e/6 (165') sends and receives DVI/HDMI signals beyond the ability of a standard HDMI/ DVI cable, and extends both video and audio over a single 165’ (50 m) CAT5e/6 cable. You can auto-adjust, buffer, and equalize signals to maintain pixel-perfect resolution up to HD 1080p/60.

FAQ'S

Yes, you can! Wowza has created GoCoder, a streaming encoder that utilizes the camera on your iPhone or iPad to stream video through our servers running Wowza Streaming Engine.  The app is available at https://itunes.apple.com/us/app/wowza-gocoder/id640338185?mt=8

When you sign up for flash streaming, we send you live broadcasting instructions for Adobe Live Encoder version 2.5. We also set up a sample page with an embedded flash player which sources from your live streaming. Using the Wirecast encoder is similar to using Adobe Live Encoder, but there are a couple minor changes that need to be made.

 

First, make a modification to the live streaming sample player page, so that instead of "livestream" being the final portion of the content variable, it's "livestream.sdp".

 

Then, fire up Wirecast and use the following broadcast settings:

 

Encoder Preset: Choose one of the existing H.264 presets, or choose Edit from the drop down list and create your own - just make sure H.264 is the chosen encoder format for your preset.

Destination: Announce to Quicktime Streaming Server

Host Name: Use domain:1935, where domain is the primary domain name off your flash streaming plan. You can use the IP address of your flash streaming plan if your domain is not pointed to us yet. To get the IP address, log in to your cpanel control panel and look down the left side of the control panel homepage for the IP assigned to your plan.

File Location: live/livestream.sdp

Username: The username assigned to your flash streaming (see the instructional email we sent)

Password: The password assigned to your flash streaming (see the instructional email we sent)

Broadcast over TCP: Leave this unchecked!

 

Click save and you can then begin broadcasting, and your broadcast should be view-able on the live sample player page we installed for you. You can take the code from that page and incorporated it anywhere into your website.

If you've ordered service and are now wondering how to get started, hopefully this article will help get you up and running. We have already created sample players for you to use, so your first task should be to simply verify that everything is working using those sample players.

 

To test live streaming using the sample player, simply follow these steps:

 

1. Download and install Adobe FMLE (free encoder) from Adobe's Website.

 

2. Retrieve your streaming details from within your Greedbegone account. To do this, log in to the services area of your account here, click the View Details button next to your streaming service, and then click the Streaming Details tab. This page contains the information you'll use in your encoder in step 3.

 

3. Launch Adobe FMLE and set your encoder settings:

A. In the video section, choose your capture/video device, change the format from VP6 to H.264, and click the Wrench icon to the right of the format and make sure the H.264 profile is set to baseline 3, so your video will be iOS compatible.

 

B. In the audio section, choose AAC if it is available (Mac only) or Mp3 if it isn't. If you've chosen Mp3, make sure Channels is set to Stereo, and Sample Rate is set to 44100 Hz, or the streaming won't be iOS/Android compatible.

 

C. In the Flash Media Server section, set the FMS URL to the Live FMS URL value located in your service details. The Stream value should default to livestream (if it's not set to livestream please change it.)

 

D. Click the Connect button, and when prompted for a username and password, enter the values found in your service details. Once you are connected, click the green Start button at the bottom of the FMLE window, and you're live!

 

4. Visit the live sample player URL from your service details to see the results.

 

If everything works, you're now ready to embed the video player wherever you plan to display your live streaming. That may be the same website where the sample player is located, if we're hosting it, or it may be an external website. To embed the player you can either copy the sample player page to your own website and then tweak it to match the look and feel, or you can copy the embed code from your service details into an existing page of your website.

 

If you have any problems getting your own player page to work, simply open a ticket and let us know the URL to your player, and we can check your code.

Rebuffering is often caused by poor routing between the location of your encoder and our data center, or between the streaming viewer and the data center. It can also be caused by not having enough upload speed on your internet connection for the bitrate at which you are encoding, or by exceeding the available bit rate or overtaxing your encoder when combining broadcasting with video recording.

 

If you encounter frequent rebuffering of your streaming, here are the steps you should take to troubleshoot before opening a support ticket:

 

Make sure you enable auto-adjust and set it to degrade quality

In the event that any of the below issues affect your ability to push data to the streaming server, you want your encoder to be able to auto-adjust to keep the stream going. It's best to degrade quality rather than drop frames. in Adobe FMLE these settings are located on the right hand side of the encoder window under the section where you specify your FMS URL.

 

Streaming bitrate must be 1,024 kbps or lower

Our service provides up to 1,024 kbps (1 mbps) of bandwidth usage per stream. This means each stream you encode must be at or below 1,024 kbps. If you are streaming at multiple bitrates, each bitrate can be up to 1,024 kbps. With the Adobe Flash Media Live Encoder this usually just means you have to set the bitrate at 1,024 kbps or lower and you'll be fine. However, some encoders, particularly Wirecast, will encode with a variable bitrate that can far exceed the bitrate you've chosen in the encoder. Recent troubleshooting with a client showed that even at 600 kbps, the bitrate would sometimes pop up over 1,024 kbps. If your encoding bitrate ever exceeds 1,024 kbps, your encoder may be disconnected.

 

Determine your upload speed

First, make sure that your internet upload speed is sufficient for the bitrate at which you are broadcasting. To do this, visit a speed testing site such as http://speedtest.net, and run at least three tests, then average them together. Make sure the average speed is greater than the bitrate at which you are broadcasting. If not, you'll need to bring your encoding bitrate down.

 

Be aware that your upload speed can also be consumed by other activity on your network. It is recommended that before you begin streaming, you power cycle your internet router or modem by unplugging it and then plugging it back in, to reboot it and give it a fresh start. This can also help ensure other network activity that is using your upload speed is halted (though it's possible it may resume depending on the nature of such activity.)

 

Check for packet loss along the route

If you are using a Windows system to encode, or have a Windows computer on the same network as the encoder, there is a handy pathping command you can use to thoroughly check the routing between your location and us. To us this command, open a command prompt, (Run -> All Programs -> Accessories -> Command Prompt), and run this command: pathping

 

Replace with the actual domain name which points to your streaming.

 

This command will run for several minutes, and will eventually produce a summary that looks something like this:

 

Copy the complete output and paste it into a support ticket and we'll see if it indicates packet loss. If so, you'll generally need to contact your ISP and provide them with the evidence of packet loss so they can work with the affected network hop to clear it up.

 

Packet loss can be intermittent, so please run at least three pathping commands and provide complete output from each to us.

 

If you are on a Mac, the pathping command is not available, unless you can run Windows via Bootcamp, Parallels or VMWare Fusion. If you cannot access the pathping command, run these two commands instead:

 

traceroute

 

ping -n 100

 

The output is not as detailed, but still may help reveal packet loss.

 

Is your encoder up to the task?

Finally, ensure that your encoding system is not being over-tasked. If you are both streaming and recording the broadcast at the same time, the load on your encoding system could result in encoder disconnects and/or random distortions or drop outs in the recorded video. For example, troubleshooting with a client recently who was broadcasting live with Wirecast, and recording to Apple ProRes 422 at a higher bitrate for later video editing, revealed that his system was simply unable to handle both jobs well. The client was able to switch to a different video format for his recording which didn't tax his system as much, and his live broadcasting trouble went away.

 

Is your encoder wireless or wired? (Wired is better)

It's definitely best that your encoder be connected via physical ethernet cable to your network, not via WiFi. There are so many radio signals that can degrade WiFi throughput that even though your ISP is providing good upload speeds, your WiFi connection might not consistently provide those speeds from your encoder to the internet modem/router.

 

Are you allowing public use of WiFI connected to your network?

It's also far better to NOT have public use of your network via WiFi while you are encoding. For example, sometimes churches will allow a congregation to connect to their network via a guest WiFi access point. This is not a good idea, as you cannot guarantee that usage won't interfere with bandwidth available to streaming. Additionally, you would be surprised at how many computers have hidden malware their users aren't aware of, that will launch attacks through your network and cause your network IP to be blacklisted.

 

Allowing guest WiFi use of your primary internet connection is a bad idea all the way around. If you must, consider installing a secondary internet service for this to avoid disruption to streaming and other important connectivity the church may need for day to day operations.

 

If the above does not help, contact us for troubleshooting assistance

If you have been through these troubleshooting steps and have not been able to identify the problem, please open a support ticket and we'll be happy to help you troubleshoot.