Difference between revisions of "Collegedale Community Church Webcast"
Line 1: | Line 1: | ||
= Introduction = | = Introduction = | ||
− | We started our first test broadcast at [http://www.collegedalecommunity.com Collegedale Community Church] in late 2007 and have come a long way since. This page is an attempt to document how we do things now, as well as some of the lessons learned along the way. To read how we got started you can skip to the [[Collegedale Community Church Webcast#History|History]] section. | + | We started our first test broadcast at [http://www.collegedalecommunity.com Collegedale Community Church] in late 2007, and have come a long way since. This page is an attempt to document how we do things now, as well as some of the lessons learned along the way. To read how we got started you can skip to the [[Collegedale Community Church Webcast#History|History]] section. |
= Current = | = Current = |
Revision as of 15:57, 12 October 2016
Contents
Introduction
We started our first test broadcast at Collegedale Community Church in late 2007, and have come a long way since. This page is an attempt to document how we do things now, as well as some of the lessons learned along the way. To read how we got started you can skip to the History section.
Current
Switching
At the core of our workflow is the Newtek Tricaster 8000 with the TC8000 Control Surface. The Tricaster is connected to two 22 inch LCD displays, one for control and the other for previews. The Tricaster handles all of our switching, titles, and picture in picture shots.
Inputs
Cameras
We currently have three HD PTZ camera systems by Vaddio called the WallVIEW CCU Z700. The system includes a Sony Z700 camera and all the hardware to handle video, PTZ control, and power over 3 CAT5 cables. In addition each camera system comes with a rack mounted device for controlling and storing picture settings like brightness, white balance, etc. We also have two ProductionVIEW Precision Camera Controller joysticks. The controllers can switch between and control multiple cameras, but we decided to get two so that we could set up the next shot, while still following the speaker with the live shot.
Additional Video Sources
In addition to the camera feeds we also have a direct DVD player input, and an analog house video feed from an Extron VSC500 Scan Converter which gives us slides and whatever else is displayed in the sanctuary.
Audio
We use 4 different audio inputs including the main mix output from our house sound board, a feed for the soundtrack sources used during special music, and audience microphones to pick up congregational singing. These are fed into a small hardware mixer, which is then fed into the Tricaster. The external mixer makes it easier for the camera operator or another volunteer to help with audio levels while someone else stays focused on the video switching.
Output & Recording
Recording to Disk
We record to disk locally on the Tricaster, primarily for backup purposes.
Streaming, Playback & Online Recording
We use a custom multiple bit rate streaming profile provided by ChurchStreaming.tv (detailed steps for importing this profile are here: Newtek_Tricaster). ChurchStreaming.tv also provides a player for our website, online stream recording, and online tools for trimming the recorded broadcasts.
Archiving
After the live webcast we trim and post the sermon using the ChurchStreaming.tv service. Older sermons are eventually migrated to our archives using the SermonSpeaker Joomla component with the files stored on Amazon AWS.
Closed Circuit
We feed an S-video output from the Tricaster to an AV-400SV distribution amplifier, which splits the signal for distribution to different in house displays. We don't display this feed in the sanctuary since the room isn't big enough to need it, but we do show the video feed in the foyer, and can put it on screens in a couple of overflow rooms as needed. Additionally we have a small LCD display connected in front of the camera controls for an extra additional program out view.
External Hardware Recorder
We also have tested recording from one of the s-video outputs using a hardware DVD recorder. We could skip the extra time and processing needed to create a DVD on the computer, and go straight to DVD duplication for distribution using this method, although it would be lower quality.
History
First Tests
We conducted our very first test broadcasts in late 2007 using existing hardware on hand and some free software. The only expense to get started was a PCI firewire card and a memory upgrade which was needed anyway. We used a single camera connected via firewire to a PC running Windows Media Encoder. We experimented with streaming directly from the PC and also with a free hosted service called Streamwebtown. We also experimented with using a webcam which provided a nice wide angle shot, but the focus was not so good. It quickly became apparent that we would need more switching features (titles, transitions, etc) and a more reliable way to stream.
Going Live
After much research and some trials we purchased Wirecast switching/streaming software and built a powerful new PC to run the software in February, 2009. We decided to publish our stream using flash for ease of use and cross platform compatibility. We looked at several different hosted streaming options but decided to use an Amazon EC2 based instance of Wowza Media Server. The most attractive aspect of this hosting solution is the pay as you go pricing model. Since we didn't know how many viewers would tune in we really liked the idea of only paying for actual usage while still being able to support over 100 viewers if needed. For playing the stream we tried several free flash players before settling on JWPlayer from LongTail Video. We also added a second borrowed firewire camera to the mix so that we could have two different shots and railing mounted tripods for both cameras. After about a month of testing we went live and added the stream to our public website in March, 2009.
Adding Cameras
In April of 2009 after a couple months of streaming we purchased a pair of new consumer grade Canon ZR960 cameras which improved our image quality and got us away from using borrowed equipment.
Growing Pains
The Wirecast software is not a bad way to go for webcasting on a budget. However, due to a number of problems and limitations and lackluster customer support (see the Wirecast article for more details) we started looking for a replacement switching solution.
We looked at the Newtek Tricaster products, hardware based switchers from Vaddio and other options but ended up going with VT5 software/hardware which we got off ebay. We liked the flexibility and cost savings of still using our existing PC for switching. We had also learned that firewire may not be the best option for real time video for a couple of reasons. First, s-video arguably has better image quality than firewire and also doesn't suffer from any of the lag problems that firewire has. Wirecast seems to fix this, but on VT5 we would have to delay the audio feed or bring it in via a firewire camera to get it in sync with the video. Additionally if we used any firewire inputs all inputs would need to be firewire or else the firewire cameras would be delayed relative to the analog cameras.
For streaming we switched to the free Adobe Flash Media Live Encoder (FMLE) software to stream to our Amazon EC2 Wowza Media Server. FMLE (or any other encoder) can see the VT5 video and audio devices as inputs in windows which allows for very flexible streaming/recording options.
In order to fully utilize the new VT5 system we added 3 more monitors, one to expand the desktop, one for 4 camera previews and another smaller one for the main output preview.
Sound Improvements
Since the VT5 system includes an audio mixer we were able to split out the soundtracks from our main house mix which allows us to independently control the soundtrack levels for special music. Often what sounds good in the room is overpowering on the webcast so it was helpful to get our own level control. About the same time we also added two audience microphones which are able to pick up congregational singing during praise time and helps us avoid a studio sound for this part of the service.
Adding Cameras Again
In order to improve image quality, provide multiple angles and prepare for a possible move from a balcony pew to a more permanent switching location we researched and purchased our first new HD capable PTZ camera system by Vaddio called the WallVIEW CCU Z700. The system includes a Sony Z700 camera and all the hardware to handle video, control and power over 3 CAT5 cables. We also added an optional SD breakout box (part number 440-6207-000) which enables s-video support in addition to composite and got a ProductionVIEW Precision Camera Controller joystick.
We started using the new camera system in February, 2010 and have been really happy with it in terms of control (it's easier to follow the speaker with the joystick) and image quality (our viewers definitely notice the difference compared to our consumer grade cameras). The lower mounting position also gives us a more head on angle than before which is nice.
Thanks to generous donations we were able to add a second controller and camera which we started using in April, 2010 and a third camera in December, 2013. The controllers can switch between and control multiple cameras, but we decided to get a second controller so that we could set up the next shot while still following with the live shot.
New Room
After a few months of planning and waiting we had the first broadcast from our new dedicated Video Control Room on August 14, 2010. We decided not to connect the consumer grade cameras after the move, which put us back to just two cameras again. We've really enjoyed having more space and being able to make cable changes without crawling under a pew.
New Streaming Service
After using the free Adobe Flash Media Live Encoder (FMLE) software to stream to an Amazon EC2 instance of Wowza Media Server for several years, in March of 2015 we moved to ChurchStreaming.tv using Wirecast for encoding. On Adobe FMLE we were encoding a high quality stream at 720x480 1000k video, 128k audio for a total of 1256k and a second stream for slower connections and older computers at 360x240 200k video, 56k audio for a total of 256k.
Reasons for the switch included the availability of technical support from a managed service with extra features like chat, automatic recording/archiving and automatic bitrate switching. Although we could setup and configure the same functionality on our own to save a little money, the time savings and the dedicated support staff made the decision easy.
Prior to the switch we used JWPlayer from LongTail Video for live playback. After the live webcast we would then trim the recorded file down to just the sermon, and use the free MPEG Stream Clip to re-encode to 500k H.264 video and 128k audio for posting to the church website. Both the player and the trimming are now handled via the ChurchStreaming.tv service.
Tricaster Upgrade
In July of 2016 we transitioned from VT5 & Wirecast to the Tricaster 8000 with control surface. This new platform eliminated our need for Wirecast, and also allowed us to switch and encode in full HD. We stopped using the optional SD breakout box (part number 440-6207-000) which had enabled s-video support in addition to simultaneous composite output for the cameras, and instead switched to the original HD breakout boxes. We also stopped using the Quad DVR for split screen view & recording, since we could use the Tricaster second display for preview instead.
Workflow before the upgrade
Splitting & Recording (pre switching)
DVR
From each camera we feed a composite cable into a Quad DVR which does two things for us. First of all, it takes 4 inputs and can output them all in a grid via VGA and composite. This allows us to preview 4 cameras on a single VGA LCD display without a separate splitter. The picture quality leaves much to be desired in the grid view, but it works well enough to set up shots.
Second, the DVR records all for inputs simultaneously. We have configured it to record whenever there is motion so that drive space isn't used during the week when the cameras are powered down. Actually using the recorded video has been a challenge, but the idea was to have a last resort backup in case of a system crash or other technical problem on the VT5 side. Additionally you might be able to splice in a video clip if a shot was missed due to switching for whatever reason.
We have used video from the DVR once or twice, but the quality is rather poor when compared to our normal recording methods. The DVR supports copying video to a USB drive and then you can use a special player that comes with the device to export a .avi file on a PC, although I've had trouble with longer recordings. I ended up playing back the segment using the DVR menu and then recording with VT5 via the composite output to get around the slow/problematic USB transfer/conversion. I was also able to crop the video slightly to remove some on screen information using this method.
We'll probably try to set up a different method of recording the camera feed in the future but this was a fairly inexpensive short term solution and we may be able to re-use the DVR for a security camera application later.
Splitting
We use AV-400SV distribution amplifiers to split the camera video signals so that we can have two copies of the same camera on the switcher. This allows us to configure one regular input and another with liveset overlays enabled. We *could* just enable/disable the livesets within VT5 for a single input, but it's a bit cumbersome to do during a live event and with the split input setup we can use transitions between the same camera view with or without the liveset overlay. These distribution amplifiers support both s-video and composite formats and we have actually used a single amplifier with one composite camera and one s-video camera going through it at the same time without a problem.
Switching
For switching we use Newtek VT5 software with the companion PCI card installed in a 2.66 GHz Intel Core i7-920 desktop PC with 6GB of RAM running Windows Vista. We also use the SX-84 breakout board (BOB) which provides multiple audio and video inputs and outputs.
Audio
We use 4 different audio inputs including the main mix output from our house sound board, a feed for the soundtrack sources used during special music and audience microphones to pick up congregational singing. We have also configured preset mixes for different parts of the service such as speaking, congregational singing and special music. We label the inputs and presents using stickers on the computer monitor since we haven't found a way to rename them in VT5.
Video
We currently use 9 video inputs although 3 of them are duplicate camera inputs (one with liveset and one without). One of the inputs is from a DVD player and the rest are cameras. We use the liveset feature for picture in picture shots, mostly to display Bible verses during the sermon. See this article on how we created our own custom angled picture in picture layout.
We also have 1 iVGA input from a presentation PC running EasyWorship and a Title Templates input.
In order to create the Title Templates we imported a 720x480 pixel transparent image with our appropriately positioned lower thirds graphic to the CG Designer module. We then added text fields and exported two versions as title templates. The first has a single line of text and the other uses a smaller font and has 2 lines of text for longer messages. The wording can be changed on the fly each week within the Title Template module. We use the downstream key to overlay title templates describing the speaker, offering, prayer time and special music at the appropriate time during the service and we also have full screen intro and closing slides.
Displays
The PC is connected to two 22 inch LCD displays and the VT5 desktop stretches across both of them which allows plenty of space for the different control modules. Additionally we have one 19 inch LCD for the 4 camera split screen previews and 1 smaller LCD to display our main program output post switcher.
Future Plans
In the future we may look into adding additional cameras, possibly even iPod or iPhones as network cameras.