-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Abnormally long start up time with Firefox with live content #1486
Comments
FWIW, I get decoding errors sometimes in other browsers too, especially at initializiation, sometimes fatal, sometimes not. Nearly always, there's a brief moment showing artifacts and/or green screen at startup: |
I can't play this stream with DASH.js v2.2.0 in Firefox 47 or 50 (Nightly) or Chrome (50?) on OS X 10.11.5. I get a |
@peterso - it works sometimes, if you're feeling lucky ;-) or sometimes audio only, so I suspect a muxing glitch. |
Firefox Nightly (50) WFM, with a similar startup time to Chrome, using v2.1.1 and dev latest. Edit: I have noticed the occasional |
Thanks guys for your input. FYI this stream is taken from the live services list from the Reference Client 2.2.0 but I am seeing the same "long startup issue" with our sample streams coming from Wowza (https://streamingrmp-1479.kxcdn.com/testlive/smil:live.smil/manifest.mpd) on Firefox. I ran some more test:
Seems this one could be on the MSE side of the browser ... |
I'm aware of at least some intermittent problems with live streams in stable FF on OSX that appear to not exist in nightlies - so I do believe this is a UA bug. It seems to specifically be related to seeking at startup. |
I raised https://bugzilla.mozilla.org/show_bug.cgi?id=1285904 this morning and discussed it with them for a while. Do you see the issue in FF nightly on OSXX? As I don't with my test stream. |
On FF 50.0a1 Mac OS X 10.11
However when I reload the page and load the stream again it starts with a green screen glitch for 2-3 seconds and then stream seems to be ok. Clearing my cache/history and reloading the page does reproduce the issue (black screen with error message). Our sample live stream works without delay on FF 50.0a1 but with a green screen glitch at startup: https://streamingrmp-1479.kxcdn.com/testlive/smil:live.smil/manifest.mpd. This is much better with FF nightly (no 30 sec. delay). This other stream starts as expected without delay or green screen: http://vm2.dashif.org/livesim/testpic_2s/Manifest.mpd (first from live services: SegmentTemplate without manifest updates (livesim)). |
I'm trying play Wowza live stream with Reference Player (2.3.0) and only Firefox browser on some operating system. The wowza server version is 4.3. |
@kissferenc It sounds like you're seeing #1482. On Ubuntu, see #546 (comment) for a good explanation on what an unsupported codec means. If it's not that issue, please raise a new one and provide more details on "not working" - the issue form will ask you for the information that will enable us to help you. |
I've just re-read the second part of your comment, and it sounds like #1482 is unrelated then. The comment about codecs support is though. |
Yes, I only want to draw attention to the Wowza update. |
@kissferenc, you probably need to install mpeg codecs for your distro. Google's official Chrome builds bundle their own H.264 and AAC codecs, but Firefox and (AFAIK Chromium) rely on system codecs being installed. Does Chromium have a similar failure on your Linux machine? |
The original issue seems to be solved now on FF 49 Win 10 with dash.js 2.3. Closing. |
Environment
Steps to reproduce
Go to http://dashif.org/reference/players/javascript/v2.2.0/samples/dash-if-reference-player/index.html and input the above live MPEG-DASH stream.
Observed behaviour
See it can take more than 30 seconds for the stream to start up on Firefox. On Chrome and Edge the stream starts within less than 5 seconds. This seems to happen only for live stream (ie VOD streams start fine). This issue also occurs with dash.js 2.1.1.
Console output
It just seems to download chunks but stream never starts before a minimum of 30 seconds :/
The text was updated successfully, but these errors were encountered: