-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
unable to cycle segments of different bit rates #100
Comments
The appspot demo does not have an uncompiled mode at the moment, so it does not generate logs. Sorry about that. Please try that manifest on a local build and see what the logs have to say. I tried your manifest (without your content, obviously), and Shaka Player was able to parse all of the Representations just fine. I see 5 video tracks listed under "Available video tracks" in the test app UI. Is the problem that you only have one track to choose from, or that it never switches? Which track does it play? |
I only have one choice of track: 640x360 656625 bits/s Tested in Opera beta 30.0 and the hosted demo: http://shaka-player-demo.appspot.com/. Will try downloading a debug build. |
With a local build of v1.3.0-debug, same thing; just one track, no errors in the console. Would sharing my assets be helpful? |
Yes, please share your assets. We have not tested in Opera before, so that sounds like an important detail. Could you also please share the full JavaScript log from your session? Not just errors, but warnings and even mime-type-support info could be very important. |
assets + console log (18MB): https://www.dropbox.com/s/d8h1h1pnbfsdaj9/assets.zip.gz?dl=0 |
sorry, this does work in Opera. Other issues in other browsers such as #101. will file other issues. |
See also: axiomatic-systems/Bento4#13 and Dash-Industry-Forum/dash.js#587
my manifest looks like:
but the demos at:
all seem to only fetch and only be able to play the lowest possible resolution. Bug in the manifest generator, or the client?
I do not see any errors in the console.
The text was updated successfully, but these errors were encountered: