Skip to content
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

Error 4012 and then 5005 on Dash manifest #940

Closed
lelikg opened this issue Jul 23, 2017 · 11 comments
Closed

Error 4012 and then 5005 on Dash manifest #940

lelikg opened this issue Jul 23, 2017 · 11 comments
Assignees
Labels
status: archived Archived and locked; will not be updated status: bad content Caused by invalid, broken, or unsupported content status: duplicate A duplicate of another issue; should be closed after linking to the original issue type: enhancement New feature or request
Milestone

Comments

@lelikg
Copy link

lelikg commented Jul 23, 2017

Have you read the FAQ and checked for duplicate issues:
yes

What version of Shaka Player are you using:
latest master

Can you reproduce the issue with our latest release version:
yes

Can you reproduce the issue with the latest code from master:
yes

Are you using the demo app or your own custom app:
custom app

If custom app, can you reproduce the issue using our demo app:
haven't tried

What browser and OS are you using:
chrome macos

What are the manifest and license server URIs:
http://vod.panda-os.com/1718/dash/sport1-stream1-1.mpd

(you can send the URIs to shaka-player-issues@google.com instead, but please use GitHub and the template for the rest)

What did you do?
tried to play this url in shaka player

What did you expect to happen?
the video would play

What actually happened?
got error 4012 and then error 5005

@joeyparrish
Copy link
Member

In the MPD you referenced, the video track's bandwidth is 0, and the audio track's bandwidth is 125000. The content is broken because 0 is not a valid value. See detailed analysis in #938 (comment) if you are interested.

That said, it plays in v2.0.9, and in #938 I agreed implement a work-around. Since your content only has one audio+video combination, we should still be able to play it.

I'm going to mark this as a duplicate of #938, and will close them both with the same work-around. Thanks!

@joeyparrish joeyparrish marked this as a duplicate of #938 Jul 23, 2017
@joeyparrish joeyparrish added status: bad content Caused by invalid, broken, or unsupported content status: duplicate A duplicate of another issue; should be closed after linking to the original issue type: enhancement New feature or request labels Jul 23, 2017
@joeyparrish joeyparrish self-assigned this Jul 23, 2017
@lelikg
Copy link
Author

lelikg commented Jul 23, 2017

@joeyparrish thanks for the quick reply.
So according to #938 the manifest should play audio bandwidth is 125000, however it never plays for me.
It does play in bitdash and dashif and akamai players.
I am using v2.1.5 because of an error in PlayReady that 2.1.5 fixes.
Can you please elaborate how I can implement the workaround?

@joeyparrish
Copy link
Member

@lelikg, no, I'm sorry for the confusion. According to #938, the manifest is broken because the video bandwidth is 0, which is invalid. A bandwidth of 0 produces nonsensical values according to formulas in the spec.

I will attempt to make a change in Shaka Player that will allow such content to play in spite of it being out of spec. I will use the manifest link you provided to validate that change.

What encoder/packager are you using to produce that stream? I'd like to report the bandwidth="0" issue to them, so that they have an opportunity to fix it on their end, as well.

@lelikg
Copy link
Author

lelikg commented Jul 24, 2017

@joeyparrish I'm using nginx rtmp module https://github.com/arut/nginx-rtmp-module

@joeyparrish
Copy link
Member

I filed arut/nginx-rtmp-module#1079. Thanks!

@joeyparrish
Copy link
Member

@lelikg, I am now getting a 404 error on your manifest. Can you please make it available to me again for testing purposes? I want to make sure that my workaround is correct for your content.

If you don't want to leave it up publicly, you can send a new URI to shaka-player-issues@google.com instead. Thanks!

@joeyparrish joeyparrish modified the milestones: v2.2.0, v2.3.0 Jul 24, 2017
@joeyparrish
Copy link
Member

I saw that the manifest was back up, and I was able to verify that my work-around works with your content. Thanks!

@lelikg
Copy link
Author

lelikg commented Jul 25, 2017

@joeyparrish thanks for all your help
I used lua to modify the bandwidth="0" to bandwidth="600000" as a temporary workaround, and it works.

@joeyparrish
Copy link
Member

The fix has been pushed to master, so you can try the player workaround now as well.

@lelikg
Copy link
Author

lelikg commented Jul 25, 2017

@joeyparrish will test and let you know! Thanks!

joeyparrish added a commit that referenced this issue Jul 25, 2017
Although bandwidth is a required attribute in DASH and a bandwidth
value of 0 makes no sense, we can tolerate such content in many cases
and play it regardless.  This used to work in v2.0.x, but stopped
working in v2.1.0 through v2.1.5.

Closes #938
Closes #940

Change-Id: I0c9b8eba923971f00946282cd8c138f68827961f
@joeyparrish
Copy link
Member

The work-around has been cherry-picked for v2.1.6.

@shaka-project shaka-project locked and limited conversation to collaborators Mar 22, 2018
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Apr 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: archived Archived and locked; will not be updated status: bad content Caused by invalid, broken, or unsupported content status: duplicate A duplicate of another issue; should be closed after linking to the original issue type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants