Open Bug 1225000 Opened 5 years ago Updated 5 years ago
Sound indicator is displayed when video stops in "seeking" ("buffering") state w/o producing any sound
>>> My Info: Win7_64, Nightly 45, 32bit, ID 20151113030248, new profile <<< STR: 1. Open a video (on the web or local) by direct link. Well, not any video, but rather a video which takes long time buffering (when you seek to another part of video, e.g. by 40%) A) I suggest to use this 1080p 60fps video: > https://upload.wikimedia.org/wikipedia/commons/transcoded/a/a9/Red-tailed_Hawk_Eating_a_Rodent_1080p_60fps.ogv/Red-tailed_Hawk_Eating_a_Rodent_1080p_60fps.ogv.1080p.webm B) If you have super-fast PC, download a 4k 60fps video from youtube, e.g. download video https://youtu.be/iNJdPyoqt8U using this download service: http://www.clipconverter.cc/ 2. Play that video 3. Quickly (= not too slow) click several times on different places of progressbar Result: Sound indicator is displayed while video is paused and doesn't produce any sound > screencast: https://dl.dropboxusercontent.com/s/x1l6ewawnlbai2m/video%20-%20Sound%20indicator%20is%20displayed%20when%20video%20stops%20without%20producing%20any%20sound.webm?dl=0 Expectations: When a video doesn't play, there should be no sound indicator in tab. Notes: 1) On the screencast, I execute that code to demonstrate mouse events 2) Sometimes even 480p 30fps videos take long time to buffer, at least on my PC
Here's more reliable (imo) STR_2: 1. Open this link > http://viblast.com/embed.html?cdn-stream=http://live.unified-streaming.com/loop/loop.isml/loop.mpd?format=mp4 2. Wait ~30 seconds Result: Sound indicator is displayed while video is paused and doesn't produce any sound I took the link from bug 1187136. It's stated there: > The stream plays for about 30 in Chrome and Safari, and then stops, but that is expected > because the stream is served by a third-party server that is not updating the media segments. But currently that stream plays fine in Firefox too, so I only use the link as a testcase here.
You need to log in before you can comment on or make changes to this bug.