Mikerowaved wrote:I was going to suggest that. We had a case where there was video without audio at one receive site. A quick refresh on the notebook's webpage restored everything to normal.
A followup. Through experimentation the following day, using a link available for a webcast that we did not show to our stake, I loaded the page and started watching. Then I minimized the page to do something else while I listened to the webcast. Returning a few minutes later, I noticed that the audio was a little behind the video. I left the page again to do other things, including watching a previously downloaded Book of Mormon video.
Returning once again to the webcast, the audio was significantly delayed. A page refresh put them back in sync.
It appears that Firefox is not able to keep the audio up to speed when something else is happening. I do not know if this is solely a FF/laptop problem, or if the church player is not sending some kind of audio/video sync signal to keep things in check. This does not happen when I have other AV things running (think YouTube or other streaming sites). It has only happened while streaming from the church site.
Returning to the problem of Friday evening, I originally loaded the webcast, then showed another previously downloaded short video to the congregation, instead of running the noisy webcast chapel source. (I was running the other videos using the Windows 10 Movies and TV app).
When the webcast began a few minutes after the local video, I noticed it was slightly out of sync, but it got progressively worse until I reloaded the page toward the end of the webcast. The audio itself was nearly perfect, and I did not want to disturb the flow of the spoken word. Also, the delay was only noticeable when the camera was presenting a tight shot from the pulpit, which did not happen very often during this particular meeting.
So at the least, it appears Firefox has a problem, which may possibly be exacerbated by something that is (or is not) in the church webcast stream itself.
I share this so that others who experience the same problem are aware of what happened and may determine to attempt a page reload. Fortunately, the reload can be done and the webcast restarted in about three seconds.