Answers about Meetinghouse Webcast
All content on this page is moving to clerksupport.lds.org under the Meetinghouse Technology topic. This page will be deleted at the end of October.
There are many factors to consider when planning and managing meetinghouse webcasts. It is not uncommon to have questions about how to best prepare for and manage your webcast event. This is a repository of common questions and their corresponding answers. Use the "Contents" navigation box below to access answers by category. You may also find answers to your webcast questions from the following sources:
- Online webcast documentation
- Other people from your area
- Online discussion forum
- Global Service Desk(GSD)
Important Meetinghouse Webcast system updates - August 1, 2012
Several improvements to Meetinghouse Webcast were implemented the evening of August 1, 2012. These will add increased reliability to the webcast system performance. Details:
- New redundancy system: The older system that provided automatic failover and redundancy was determined to be the primary cause of Meetinghouse Webcast infrastructure failures. A newer system that is used for all Church data center applications was implemented and should provide considerably greater reliability.
- New outbound reflectors: These are the servers that webcast receiving locations connect to. It was determined that they needed to be upgraded and more closely monitored, which is now complete.
- Live monitoring system: This is an exciting development our engineering team has implemented. We have a new monitoring system that goes far beyond just pinging webcast servers to see if they are up. The system creates an actual webcast every 5 minutes in exactly the same way a user would, and monitors every step of the process to make sure the stream is successfully created, published to the outbound reflectors, and available for viewing. If any part of the process fails, our engineers and network operations center are immediately notified so that they can fix the problem.
- Update to Microsoft Expression Encoder R2: Microsoft has released a patch update to Expression Encoder, which is the encoding engine that does all of the work underneath our Meetinghouse Webcast Software. The next time you log in with Webcast Software, you will automatically be prompted to upgrade to this newer version of Encoder. The only noticeable change from within Meetinghouse Webcast Software is that this upgrade fixed a bug some users noticed when viewing some images or playing some videos - the aspect ratio would switch between 16:9 and 4:3. That no longer happens.
- Change from stream.lds.org to webcast.lds.org: With the change to the new outbound reflectors, we have changed the URLs for webcast from stream.lds.org to webcast.lds.org. In general, this should require little or no action on your part. If you use the software, the URL that is created for the receiving sites now automatically uses webcast.lds.org as the first part instead of stream.lds.org. So if you have been using the same URL for your broadcasts, you'll want to make sure your receiving sites have that new link. We have maintained some backwards compatibility with stream.lds.org for those who use the hardware Communicator and/or Receiver boxes, which are hardcoded to use stream.lds.org. We have put a rule in place to ensure those broadcasts are directed to the new servers. No action needs to be taken by users of those boxes.
- Portal URL change from webcast.ldschurch.org to webcast.lds.org: To provide URL consistency and standardization, the Meetinghouse Webcast portal address has changed from webcast.ldschurch.org to webcast.lds.org. The portal is used by stake and district presidents when approving new STS account requests. It can also be used by the STS for downloading the Meetinghouse Webcast software client, opting-in or out for e-mail notification, and viewing a table of live and historical webcasts.
What if my local area does not have Internet access speeds sufficient to support sending or viewing a webcast?
We do not recommend webcasting if your local Internet infrastructure won’t support it. Webcast technology needs a reliable high speed connection to produce a positive viewing experience. Insufficient Internet bandwidth or speed can result in a choppy, inconsistent viewing experience that will distract from the spirit of the meeting.
Our Internet connection meets the bandwidth guidelines, but we’re still encountering performance issues. What else can be done?
Check first to see if others are using the same Internet connection for other activities. For example, if several people are uploading files from the Family History Library, this will impact available bandwidth for your webcast. You can also check with your local Internet provider to determine the best way to validate the bandwidth of your connection.
What do I do when my Webcast Communicator consistently stops sending out a stream after 6-7 minutes?
Check with your Internet Service Provider (ISP) to ensure that your Internet connection is set-up to allow outbound streams. Validate that your connection is set-up to support full duplex instead of ½ duplex. To verify whether the issue you are encountering is with the Webcast Communicator or your Internet connection, try originating your webcast from a different location.
Does Meetinghouse Webcast make provisions for fluctuations in Internet bandwidth availability?
Yes, Meetinghouse Webcast builds a 60-second buffer into the transmission to help minimize the impact of fluctuations in bandwidth.
Are we required to have the Meetinghouse Firewall (Church-managed firewall) installed at the meetinghouses we are broadcasting from and broadcasting to?
Yes. Church guidelines stipulate that all meetinghouses with Internet access must employ the Meetinghouse Firewall.
Can we use a wireless access point for sending our webcast?
This approach is not recommended because variations in signal quality and bandwidth may affect the quality of the video and audio.
Can we use a wireless access point for receiving our webcast?
This approach may work for the receiving location, though a wired connection is generally preferred.
What Port does Meetinghouse Webcast use for sending a webcast?
Meetinghouse Webcast uses HTTP (TCP port 80) to send webcast stream to the Windows Media Distribution Servers.
Creating (Sending) a Webcast
See also: Meetinghouse Webcast Sending Options
How does Meetinghouse Webcast differ from other commercially available webcast solutions?
The Meetinghouse Webcast combines industry standard technologies with some customizations designed to simplify the steps of producing a webcast event. It captures and encodes the video and audio feeds and sends them directly to a set of media servers managed by the Church. These servers create multiple streams of the captured content, which can be viewed by one or many locations over the Internet. The process is similar to other live webcast solutions. The meetinghouse webcast solution is designed to simplify the process of managing the event and to provide more reliability.
Can I use the Meetinghouse Webcast for two-way video conferencing?
Meetinghouse Webcast is designed for one-way only communications. If you need two-way video communications, consider video conferencing.
How many people are needed to manage a webcast event?
The number of people will depend on your situation. We recommend that you have at least one person responsible for the technology at the webcasting location (usually the Stake Technology Specialist). You’ll also need someone to operate the camera. At each receiving location, you need someone to set up and monitor the receiving equipment (Webcast Receiver or computer, projector or TV, audio). We recommend that you have some form of personal communication in place (such as cell phones) between the locations in case one or more locations encounter an issue that needs discussion.
When setting up a webcast, can we choose our own six digit event code?
Yes. This is done by the person setting up the webcast. Local units can determine their own methodology for creating event codes. The event codes can be reused, but we recommend that you change your event code from event to event. This will help ensure that your webcast is only viewed by those who are authorized to do so.
Viewing (Receiving) a Webcast
See Also: Meetinghouse Webcast Viewing Options
How many locations can view a Meetinghouse Webcast at one time?
The Meetinghouse Webcast media servers are configured to allow up to 250 receiving locations to view a single event at one time. If you expect more receiving locations for a webcast event, contact the webcast support team at least 3 weeks in advance.
Where do I place the Meetinghouse Webcast Receiver or laptop computer in my building?
Place the computer or Webcast Receiver close to the projector or TV that you’re using. This will depend on the length of the cable available for connecting the computer or Webcast Receiver to the projector or TV. The connecting cable included with a standard projector, for example, is usually only a few feet long.
This means you will need to run a network cable from the closest point in the building where Internet access is available to the location where the event is being viewed. In some locations, it is possible to have your building wired so that there is a network jack on the side wall of the chapel stand. In this case, you could run your network cable across the floor on the stand to the podium area, where you could place the receiving device and a media projector.
In newer buildings, there is an Internet connection on the side of the chapel pulpit.
Note that no physical changes should be made to your building without consulting the LDS facilities manager that supports your area.
How fast should a laptop or personal computer be to view a meetinghouse webcast?
Generally, a personal computers or laptops with a 1.5Ghz processor or better and 256MB RAM or more running Microsoft Windows XP with Service Pack 2 will be sufficient to view the webcast. This configuration will support webcast speeds of up to 768kbps.
Can I set up the receiving device to allow people to view the webcast on more than one screen or from more than one room in the receiving location?
This is a possibility, though it will require some expertise and effort to set up. You will need something to take the video output from the Webcast Receiver or computer to plug into the meetinghouse video system. Most meetinghouse video systems use a composite video display format. Most computers do not have a composite video out port. The Meetinghouse Receiver comes with a DVI video out port and a DVI-to-VGA adapter. Purchase an interfacing device (called a scan converter) to take the output from your Webcast Receiver or computer and connect it to your meetinghouse video and audio system. You may also need to purchase a Distribution Amplifier (DA) and/or an RF modulator to show the output using projectors and TV screens throughout the receiving building.
Is it possible to view the webcast feed in the same location that I’m webcasting from (for example, view the event from a different room in the building)?
You could view the webcast at the originating building via the Internet—the same way you would at a receiving location. However, because of the delay, we recommend that you instead leverage the building’s built in video and audio system—allowing participants in the same building to view and hear the events real time.
What if my webcast stream doesn’t open in my browser?
When receiving a webcast the stream will often open automatically within a browser. However occasionally due to file type associations in browser settings the stream will not pull up in the browser. The solution for this problem varies depending on your operating system version, default browser (Internet Explorer, Firefox, Chrome, etc.), and the version of your browser. If you are using Windows 7 with Internet Explorer 8, this is your solution:
Go to Tools, then Internet Options. Click on Programs tab, then Set Programs. Look for the protocol called MMS, and set Windows Media Player as the default program.
For Firefox (Version 6.02 with Windows 7) you’ll use a different solution:
Go to the top menu bar on your Firefox browser. Click Tools, then Options. Choose the Applications tab. You will see a similar list of programs and protocols.
Change all of the Windows Media Audio/Video playlist settings over to “Use Windows Media Player (default)” instead of the embedded Windows Media Player. Now instead of showing the stream within the browser the video will automatically launch in Windows Media Player.
If these methods do not work for you or you simply want to bypass using your browser, you can always launch Windows Media Player, hit ctrl-U, and paste the link in to watch the webcast.
Is there a test stream that we can test a receive location with at any time?
You can go to http://stream.lds.org/webcast or http://stream.lds.org/webcast2. They both run 24/7 and loop a session of conference so you will get both speaking and music to test volumes with. However, please be aware that some users have reported much different audio levels coming from these test streams compared to their actual broadcast. Do not rely only on these test streams - you should test the actual broadcast well in advance to ensure audio levels are correct.
Video and cameras
See also: More on Video & Cameras
What video cables do I need to set up my webcast?
This will depend on your video camera and potentially on the wiring within the building. There are two common types of video cables: RCA composite and S-Video. Check the connections in your building and on your camera to see what you need. Some cameras support both formats, while other cameras support only one. You will need to have cables long enough to reach from the camera to the video jack usually found on the side wall near the back of the chapel (or in the overflow area). Or you’ll need to have a cable that can travel directly to the Meetinghouse Webcast Communicator.
Do I need a video mixer?
Neither the Webcast Communicator nor the Webcast Software have integrated video mixing capabilities at this time. They are designed to support webcasts using one video source. If you want to transmit video from multiple sources (such as two different cameras or a camera and a laptop), you will need to use a separate video mixer. You can then use the video output from the video mixer for the video source used by Webcast Communicator or Webcast Software.
See also: More on Audio Setup
Our audio appears to be too "hot" (or loud) and/or distorted, coming into the Webcast Communicator. What should we do?
Basically you need to lower the audio level going into the Encoder (part of the Communicator Box or Software.) If you have a mixer inline before the Communicator, then just lower the output level going to the Communicator. If you don't have a mixer inline then the Communicator Box's own audio level adjust needs to be used. NOW A WARNING MESSAGE!! Do not adjust this if you have started your Webcast for your meeting, as it will stop the Webcast and reboot the Communicator Box and you will have to restart your webcast and everyone connected will have to restart their receiving processes again. This clearly needs to be done long before your meeting begins. On the front panel display of the Communicator go to the "Setup" option and push the green check mark button, then go down to the, "Adjust input volume" option, then adjust the volume downward or to the left.
Can we use more than one microphone to capture the audio?
You can use multiple microphones if you are using an audio mixer to funnel the audio into the computer sending the webcast.
What audio mixers have been successfully used in delivering a webcast?
There are several Microphone Mixers out there that can output a consumer line level output. Before you look to spend money on a mixer, please check with your Bishop or Stake Technology Specialist for someone in your ward/stake that may already have a mixer, and that person may help you obtain your goal. Bear in mind a caution... Stay VERY conservative in the equipment you setup as to NOT become a distraction to the original intent of the meeting you are trying to support. In other words, stay out of sight or as close as you can, so that you do not draw attention to you or your equipment.
What is the difference between an EJ-8, EJ-10 and an EJ-R? And how would I use them for webcasting? And where can I get these devices?
- An EJ-R is used to put Line Level audio onto a phone line, I.E. the transmit end. (a backup audio to another building in case streaming doesn't work for some reason.)
- An EJ-8 can adapt different levels of audio into your sound system via the Microphone Jack. (I.E. could be used to adapt from your streaming receiver into your sound system.)
- An EJ-10 can do everything the EJ-8 can, AND recieve a Telephone Line audio (i.e. opposite end of the audio put on a phone line via the EJ-8) into your sound system via the Microphone Jack.
You should be able to obtain any one of these items from your Facilities Management Group. (Note most buildings should already have an EJ-10 or Crab box or something very similar to it. Check with your librarian or Stake Technology Specialist.)
Can I plug the chapel audio system’s speaker amplifier or speaker wiring directly into the Meetinghouse Webcast Communicator?
No. They operate at different voltages. This will damage the components in the Webcast Communicator and require you to purchase a replacement Webcast Communicator.
I have verified that I'm using all the correct cables and that the audio coming into the Webcast Communicator correctly. But the Webcast Communicator doesn't seem to be picking up the audio correctly. What should I do?
Occasionally, a pop-up control from the Realtex Audio Card can pop-up when an audio device is inserted into one of the audio input jacks. The activation of this window will prevent the audio from working correctly until the window is closed. One can address this issue by using a mouse, keyboard and monitor to view the WindowsXP interface. Find the Realtex pop-up and close it. Go into the toolbar for Realtex and disable the audio control.
How can I verify that the audio is working correctly on my Webcast Communicator?
Use Microsoft's test function found on the Control Panel:
- Attach a mouse, keyboard, monitor, speakers and a sound source such as a MP3 player to the Line In port, a microphone should also be attached to the Mic In port.
- Navigate to the Control Panel
- Select Sounds and Audio Devices
- If the Control Panel is in Category View, select Sounds, Speech and Audio Devices. Then select Sounds and Audio Devices.
- If the Control Panel is in Classic View, select Sounds and Audio Devices
- Select the Voice Tab
- Click on the Test Hardware button.
- Follow the wizard. It will guide you through the process of recording a paragraph from the Mic and testing the Line In as well as the speakers.
I hear a soft “clicking or popping” noise in the background of the webcast. How can I fix that?
- Go to the Control Panel and Start the "RealTek HD Sound Effect Manager"
- Select the "Mixer" tab
- Click and mute the icons below each of these slider bars: Wave, SW Synth, CD Player, Front Mic, Mic Volume, and Stereo Mix.
- DO NOT Mute the "Line Volume" Slider bar.
- Mute the Playback Volume below the playback volume knob.
- Turn the Record Volume knob to approximately 75%
- Select "Audio I/O" Tab
- Click on the blue tool icon next to the right of the Analog label
- Remove the Check from the box labeled "Enable auto popup dialog..."
- Click on OK
- Click on OK
- Exit control Panel
Some Webcast boxes need a driver update to solve the clicking noise that is noticable with music. See readme (ftp://ftp.iocorp.com/LDS_Church/CommunicatorAudio) and follow directions below
If the "RealTek HD Sound Effect Manager" is not installed follow these steps before the steps above:
- Download and extract to a USB Drive the LDS_Communicator_Audio.zip file from ftp://ftp.iocorp.com/LDS_Church/CommunicatorAudio
- Plug in a keyboard, mouse and monitor to the communicator
- Open the Windows XPe Control Panel
- Select 'Add or Remove Programs"
- Select the "Realtek High Definition Audio Driver" and click on the "Remove" button
- After the driver has been removed, select the option to re-boot the system
- On re-boot, click 'Cancel' to the "Found New Hardware Wizard". Do not let Windows try to Automatically install the drivers.
- Maximize and close the command window that is labeled "do not close". THis disables the program that runs the front panel of the Communicator.
- Insert into the back of your Communicator the USB Drive that contains the unzipped contents of the LDS_Communicator_Audio.zip file.
- Run the Setup.exe file
- During the installation process, the install will need a couple of windows system files. ksuser.dll is located in the folder c:\Windows\System32 and ks.sys is located in the folder c:\Windows\System32\DRIVERS
- Allow the installation program to reboot your system. After initial shutdown, remember to remove the USB drive from the back of the Communicator.
Can I use a 1/8” audio cable to connect the audio into my Webcast Communicator?
You can use a 1/8” inch stereo cable jack to feed audio to the Webcast Communicator—a mono 1/8 inch jack will not work.
What do I do to keep people from tripping over the audio, video, and power cables?
Try to keep cables out of high-traffic foot paths. When cables do have to cross where people walk, use gaffer tape (or equivalent) to cover them. Gaffer tape is a specialized tape used by AV professionals. It is NOT the same thing as duct tape. Gaffer tape should not be used on wood or painted surfaces. Gaffer tape is available at ldscatalog.org and may be available at local stores in your area.
What audio cables do I need to set up my webcast?
This will depend on what’s already in place in your building and the option you chose for capturing audio. More on Audio.
What's the best way to capture the audio from the choir?
For large choirs I have setup two microphones on tall extended stands (or mic booms) trying not to get too close to pick up individual voices of the choir and balance it between the choir and the organ. A good recommendation is to use these microphones for your far or receive side audio only.
What's the best way to capture the audio from the organ?
Most, if not all, chapel organs do not have an audio output that you could do a direct connect to your mixer, so the only other way is, as said above, using microphones. If you are trying to pick up a choir also, you will need to place the microphones in such a way as to get a good balance of both.
What do I use to connect my audio back-up (phone) into the church audio system?
An EJ-10 (as described above) is probably the easiest and simplest way to connect a back-up phone audio into your sound system.
How do we capture audio for our webcast from the the hearing impaired system?
Use the output jack from one of the hearing impaired receivers an connect it to the Webcast Communicator or sending computer. Never connect directly into the hearing impaired transmitter. This will kill the sound capture card in the Webcast Communicator.
How do we determine what's causing the hum in our audio?
Audio hum can be caused by many things. Some of the more common include; overly long cable runs, lack of shielding of the audio cables, strong nearby electrical sources (motors, transformers, etc.), ground loops, damaged connectors and cables, and impedance and level mismatches. Hum can also be caused by a bad microphone or faulty amplifier or other equipment. Identifying the actual cause in a specific location is usually a process of elimination.
One troubleshooting step that has found success is powering down the sound system rack for 20-30 minutes and restarting.
What do we do if the audio is not working in one of our receiving locations?
If you are using a laptop or PC at that receiving location, check to ensure that you have Windows Media Player 11 or later installed on the device. Previous versions of Windows Media Player sometimes have issues playing the audio.
How do you adjust the audio at the receiving locations?
Testing and Troubleshooting
Should I disable Internet for other devices in my broadcast and receiving locations, or just have an announcement made to meeting participants not to use the Internet on their smart phones and tablets?
This is becoming an increasingly important issue to address. Without question, it is the best idea to disable all other Internet connections in both your broadcast and receiving buildings, and dedicate all of your bandwidth to the webcast. We have heard reports over and over again of webcast tests before the meeting going just fine, but then users have problems during the actual meeting. In many cases, it's because members attending the meeting connect to the wireless Internet with their iPhones, iPads, and other Internet-capable devices while in the meeting, and kill the bandwidth.
The Meetinghouse Technologies team is working on a management function on the Meetinghouse Firewall that will allow local leaders to manage Internet access through the firewalls, and shut down ports and wireless so that you can dedicate all bandwidth to the webcast. In the meantime, we strongly suggest during webcast sessions that you disable all other Internet usage in the building, including (and especially!) wireless.
How far in advance should I test our Meetinghouse Webcast implementation?
As there are many components involved in successfully delivering a meetinghouse webcast, test out your implementation well in advance of your event. Give yourself time to potentially address issues with your Internet provider, purchase needed equipment, and adjust any audio or video settings. Conducting a test on the same day of the week and at the same time of day as the actual event is also a good idea.
What should I look for when testing our Meetinghouse Webcast implementation?
The best way to test your Meetinghouse Webcast implementation is to schedule a practice event in advance of the target event. In your practice events, we recommend you do the following:
- Validate that you have all the right Meetinghouse Webcast components (including appropriate connectors and cords) in both the sending and receiving locations.
- Set-up all the Meetinghouse Webcast components as if you were setting them up for an actual event. Consider the location of the camera, cables, and sending and receiving devices in relationship to each other, the presenters, and the audience.
- Plug in the Webcast Communicator or computer and setup an event. The Webcast Communicator User Guide and the Webcast Software User Guide provide step-by-step instructions for setting up the webcast event. To view a video that shows how to set up the Webcast Communicator, click here.
- Set up the Webcast Receiver or set up a computer to view and hear the webcast.
- As you capture the webcast, validate that the configurations for the audio and video are set properly. For example, the audio may be too soft or too loud (causing distortion). While testing, try to test scenarios that may occur in the actual event. For example, if you are going to have a soloist sing over the pulpit microphone in your event, test out how that will sound.
Who should be involved in testing for the webcast event?
Because there are multiple locations involved in any webcast, the stake technology specialist needs assistants in each location. Conduct the test sessions with all the people who will provide assistance during the actual event. This will minimize any issues you might encounter and familiarize everyone with the equipment.
After we’ve completed our first webcast event, how often do I need to validate our implementation?
Testing for subsequent webcast events should not take as much time as the initial setup and testing. But you should test and validate your Meetinghouse Webcast implementation before every webcast. It’s recommended you do this at least a week before your event. You want to give yourself time to react if you encounter an issue (such as a cable that’s gone missing, an Internet connection with reduced bandwidth, or a device that’s not working correctly).
Is there anything I should do to prepare for potential issues during our Meetinghouse Webcast?
Thoroughly testing your Meetinghouse Webcast event before the actual event will be your best preparation for potential issues. Most potential issues will be identified during this testing and can be addressed before the event. Testing ahead of your event will also help you become familiar with the equipment you are using. This will help you address issues should they occur.
Take time before your event to consider what you would do if you encountered an issue during the actual event. Talk with those who are assisting you about the potential issues and how you’d resolve them. For example, if the laptop at a receiving building freezes, how will you handle this situation?
If you have a reliable Internet connection and have properly tested your implementation, it will be unusual for you encounter serious technical issues during the actual event. However, it is always good to be prepared and plan as best you can for an unexpected issue.
What should I do if the Meetinghouse Webcast Communicator dies?
Meetinghouse Webcast Software can be installed on multiple computers to provide a back-up webcasting solution. In addition, you should always have a phone line or audio bridge set up in advance in case your Internet connection fails. You will need to interface between the telephone and chapel audio in each building. If you are webcasting to multiple buildings, you will need an audio bridge:
- In the US, Please work with National, local, or online audio bridge providers.
- Outside the US, you’ll need to work with a national or local audio bridge provider.
Contact the Church's Global Service Center (GSC) for further investigation if it appears your Webcast Communicator has failed.
What happens if the Meetinghouse Webcast Receiver dies?
You can use a computer with Windows Media Player as a back-up receiving solution. Contact the Church's Global Service Center (GSC) for further investigation if it appears your Webcast Receiver has failed.
What happens if the Meetinghouse Webcast Receiver freezes?
If the Webcast Receiver freezes, try turning it off and then back on.
Why does my media stream keep breaking up?
If you are having disruptions in the webcast stream of your event, one of the following situations may have occurred:
- Your Internet connection could be insufficient or experiencing temporary issues (check to verify that your Internet connection is working properly)
- Other resources in the building could be competing for your Internet connection’s available bandwidth (check to verify that the Internet bandwidth is not being used by other resources in the building—for example, the family history library)
- If using the Webcast Communicator, the webcast could have been set-up in “Test mode” instead of “Webcast mode” (check the Meetinghouse Webcast Communicator to verify the webcast has been created in “Webcast mode”)
Because multiple Internet connections are involved, it’s good to establish whether one receiving location is encountering issues or if all the receiving locations are encountering issues.
Why can’t any of the receiving locations connect to the webcast?
There could be a couple reasons for this issue:
- Verify that the Internet connection of at the Webcast location is working properly
- Verify that all the cables are properly connected
- Verify that the receiving locations have the correct webcast identifiers(Keep in mind that when you set up the event in the Meetinghouse Webcast Communicator, if you enter in less than 6 digits for the event ID, the system will add zeros in front of the number you entered to reach a total of six digits. For example, if you put in 325 as the event ID, the system would change this to 000325.)
What do I do if I’m getting an Internet failure message on the Meetinghouse Webcast Communicator?
First, verify whether or not the failure is with the meetinghouse Internet connection or with the Webcast Communicator itself. To determine this, do the following:
- Use a computer connected to the Internet in that building to verify that you can connect to the Internet
- Using Command Prompt, ping instream.lds.org. If you cannot ping, you need to contact your ISP.
- Open a web browser to stream.lds.org/server.txt. If you cannot get to this page, check to see if you have a separate content filter.
- If yes, bypass the filter. Try to get to google.com and do a search. Try the Internet test from the main menu on the Webcast Communicator.
- If there is no filter, reboot your Meetinghouse Internet device. Go to the main menu in the Webcast Communicator and try the Internet test.
What if none of the receiving sites are receiving audio?
Review the Audio documentation and verify that you are following the setup instructions. Check the audio devices and cables used in your implementation. Some audio devices (such as the meetinghouse audio system) will have volume controls; try adjusting these. If you are unable to get the audio working, try implementing one of the other four audio options identified in the Guide.
The Video Preview screen in the Webcast Software is black; what can I do to get the video to show up? Try the following steps to resolve this issue:
- In the Meetinghouse Webcast Software, go to Edit Settings and then select the Audio/Video tab
- Select the Configure button for the Video Source
- Switch Video Standard from current to a different standard.
- Examples: change NTSC_M to PAL_B OR change PAL_B to NTSC_M_J
- Select Apply and/or Ok
Note: The menu that appears when you select Video Source: Configure is based on your video source. This means that this menu will vary based on your camera type or the video capture card you are using. The steps detailed above may not apply to your specific webcast hardware/software combination.
I’m have trouble getting the video or audio to work correctly while using the Meetinghouse Webcast Software—what can I do? Driver compatibility issues sometimes prevent the video/audio capture card, your PC, and the software used for webcasting from working well together. To troubleshoot potential driver issues, try the following steps (note: these instructions were written based on Microsoft Windows 7 menus).
- Verify that the video and audio are available under Windows Media Encoder
- Open Windows Media Encoder (Start -> All Programs -> Windows Media -> Windows Media Encoder)
- Select Broadcast a Live Event for the session
- Select the video and audio devices that you want to use for your event
- If you have a video or audio device connected to your computer, but the device doesn’t show up on the respective video/audio list, then proceed to step 2: Install correct video/audio drivers
- If the connected video and audio devices are available in Windows Media Encoder, they should be available in the Meetinghouse Webcast Software
- If they are not available, please send the following information to email@example.com:
- Video/audio capture card type, Operating System name/version, processor architecture and Meetinghouse Webcast Software version, and a brief description of what you are experiencing
- Install correct video/audio drivers
- Open Device Manager
- Right click on My Computer and select Manage
- Under System Tools select Device Manager
- Expand Sound, video and game controllers in the Device Manager menu tree
- Right click your video or audio device in question and select Uninstall
- Note: for capture devices that do both video and audio, repeat the process for both video and audio drivers
- After the device has been uninstalled
- Right click Sound, video and game controllers and select Scan for hardware changes
- Your device should show up under Other devices in the Device Manager menu tree
- Right click the device and select Update Driver Software…
- Select Search Automatically (this should find and install driver automatically)
- Open Device Manager
- Note: If Windows Update cannot find a driver for the device, you will need to obtain the driver from the specific vendor. Most companies have the latest drivers available for download from their websites. For example,
- Note: Some cards display the video source but not audio. You can also check this by:
- Right clicking the Speaker icon in your system tray (if visible)
- Select Recording devices
- Verify that your recording device is present in the device list and is showing responses in its VU meter.
When should I stop a Webcast from the transmitting location?
When stopping a webcast from the transmitting location, the receiving locations will also stop. This means that receiving locations will end before playing through the remaining buffer. After your meeting ends (eg. after the closing prayer), it is recommended that you wait a few minutes (at minimum one minute) before ending the Webcast from the transmitting location.
I’ve reviewed the Meetinghouse Webcast documentation, but I’m still having trouble getting our Meetinghouse Webcast implementation working properly. Where can I get additional help?
You can get support in two ways: call the Global Service Center for telephone at +1 (801) 240-4357, or send an e-mail request to firstname.lastname@example.org.
Is telephone support from the Global Service Center available on Sundays?
No. We recommend that you test your Meetinghouse Webcast implementation in advance of your weekend event. This will allow you to work out any potential issues and make calls to support before the weekend event.
I’m having trouble viewing the webcast using my personal computer or laptop. Will the Global Service Center help me?
The Global Service Center does not provide support for personal computers or laptops.
We’ve implemented our own webcast solution but we’re having trouble with it. Can we get support from the Global Service Center?
No, the Global Service Center is not prepared to support other webcast solutions.