Shadyside Presbyterian Church

Troubleshooting Audio Problems

The sermon keeps pausing or stopping

If the sermon keeps pausing or stopping it usually means that the sermon is not downloading as quickly as it is playing and the audio player you are using has to pause and wait for the next part of the sermon to download before it can be played. This will happen if the computer's connection to the Internet is slow or interuptted and there are two things you can do. The first option is to right-click (ctrl-click on a Mac) on the link to the sermon and choose "Save Target As..." from the options menu. Save the file to your computer and then open it in your player of choice. The second option is to try to visit the site when there is less traffic on your network or your connection is more stable.

The sermon keeps stopping in the same place

Sometimes during the download or streaming process a file becomes corrupted and can not play past a certain point. The best thing to try to download or stream the file again by clicking on the link. If that does not solve the problem you should clear your temporary Internet files since the file may be cached on a proxy server or on your local machine. In Internet Expolerer you do this by going to Tools > Internet Options... where you will choose the General tab if is not already selected. The click the Delete Files button, click the Delete Offline Content checkbox, then click the OK button. Then try downloading or streaming the file again.

I still can't play the file

If you need additional help e-mail the webmaster at webmaster@shadysidepres.org. Please include as much information as possible to help us figure out your problem. Some things you should try to include are:

  1. Are you using a PC or Mac?
  2. What browser are you using? (Internet Explorer, Netscape, Safari, etc.) Include a version number if you know it.
  3. What player are you using to play the audio file? (RealOne, Windows Media Player, etc.)
  4. Did you try to stream the audio or download it and play it from your local machine?
  5. Did you get an error message? If so, what was it?