Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

MPEG-DASH streaming from wowza is broken in Chrome after upgrade to JW Player 7.7


Hi,
we have a problem after upgrading to JW Player 7.7. MPEG-DASH streams stop working in HTML5 player (e.g. Chrome). There is a problem, JW Player download correct manifest file, but after that starts downloading incorrect chunks. It ignores protocol (use http instead of https) and port (use 80 instead of 1936), so it get 404. We are using wowza streaning server version 4.4 and it works well with our prev JW Player version 7.2.4.
You can try it with stream https://media.mojemedicina.cz:1936/vod/videos/smil:2015_ipad_petr_mara/manifest.mpd
Where is a problem?
Thanks for help!
Dominik

15 Community Answers

d...

Best Answer 

Solved with Wowza support, shaka v2.0.0 changed MPEG-DASH implementation and now works with location tag in manifest, where has to be set correct URL. We have wowza server behind proxy server, where is terminated https too. So protocol could be set in Wowza app HTTPStreamer properties mpegdashPlaylistHostProtocol and mpegdashChunkHostProtocol. Port has to set in Host header on proxy.

View in conversation

Donni

JW Player Support Agent  
0 rated :

Hi Dominik, it looks like that stream is failing the DASHIF conformance tool as well. This is a link to the tool I used to validate your stream. This is a link to the specific error log for your stream.

Let me know if that helps.

d...

User  
0 rated :

Hi,
stream is generated by Wowza streming server and works well with prev JWPlayer versions (7.6.1), I guess that the problem is related to new version of shaka provider. Player starts downloading chunks on wrong protocol and port. Do you test MPEG-DASH stream generated by wowza streaming server with JWP 7.7? We have multiple qualities there.
Related post on wowza forum: https://www.wowza.com/forums/showthread.php?44604-Why-Wowza-server-generate-invalid-mpd-files

Alex

JW Player Support Agent  
0 rated :

Hi Dominik,

Donni is out of the office for the rest of the week, but I will be more than happy to take over for him.

We do test Wowza-generated DASH streams with our player when a new version is released. With that being said, if your stream is not passing the DASH Consortium’s Conformance Validator, then it cannot be expected to play properly in our player, regardless if it had played previously. You are correct that JW Player 7.7 did include an updated version of the Shaka provider. Part of the update to the provider does make the player require streams to more strictly adhere to the DASH specification, making whether or not the stream passes the validator more important.

If you are able to resolve the issues and have the stream pass the DASH validator fully and find that the stream is still not able to play in JW Player, please let us know.

Thank you.

d...

User  
0 rated :

Hi Alex,
thanks, we'll try to update to the newest wowza version, if it solves our problems and generated stream is valid. I'll let you know, if it fixed our problems.
Dominik

Alex

JW Player Support Agent  
0 rated :

Sounds good, Dominik!

info

User  
0 rated :

Hi Alex,
wowza is upgraded to version 4.5, manifest should be valid, but MPEG-DASH stream doesn't play in JW Player version 7.7.2:( We are streaming over https and that's the problem. I have tested streaming over http and it works well.
Do you have any idea what is wrong?

Alex

JW Player Support Agent  
0 rated :

I can try to take a look but we are not experts on the actual creation of streams. As long as the stream is valid, it should play in the player, but if it doesn’t play not only in our player but other players, then we have to assume there’s an issue with the stream itself.

Can you provide me the URL to the stream encoded with the new version of Wowza?

d...

User  
0 rated :

Stream URL is the same: https://media.mojemedicina.cz:1936/vod/videos/smil:2015_ipad_petr_mara/manifest.mpd
Tested in wowza build-in player and it plays without any problem, same in JWPlayer 7.6, but it doesn't play in JWPlayer 7.7. If you are able to use the newest shaka library, it could fix the problem. I guess, that shaka library is a root of our problems.

d...

User  
0 rated :

Edge browser plays it too without any problems.

Donni

JW Player Support Agent  
0 rated :

Hi Dominik, the stream still does not pass the DASHIF validator tool. Are you able to follow any of the recommendation by the validator tool?

d...

User  
0 rated :

Hi Donni,
validator tool is very chaotic for me, I don't see there any recommendations:( We are using the latest version (4.5.0.03 (build 19252)) of wowza server as streaming server, so if you could recommend me some config changes in wowza server, I can try them, but it's everythnig what can I do.
I hope that wowza generates MPEG-DASH streams working in JWPlayer if they are both testing together.
IMO problem is not in the stream, same "invalid" stream over http protocol works well, but over https it doesn't work. Try http://media.mojemedicina.cz:1935/vod/videos/smil:2015_ipad_petr_mara/manifest.mpd

Donni

JW Player Support Agent  
0 rated :

Have you contacted wowza about this? The errors with the stream are happening in the conformance tool and outside of our player so I would defer to them for troubleshooting your stream.

d...

User  
0 rated :

No, because stream plays in Edge browser, wowza build-in player and older JWPlayer too:) But I'll try it there.
Thanks!

Donni

JW Player Support Agent  
0 rated :

Additionally, you should run the stream in the DASHIF validator tool and then go to the Shaka issues page since your stream doesn’t work on Shaka’s test player.

d...

Best Answer  User  
0 rated :

Solved with Wowza support, shaka v2.0.0 changed MPEG-DASH implementation and now works with location tag in manifest, where has to be set correct URL. We have wowza server behind proxy server, where is terminated https too. So protocol could be set in Wowza app HTTPStreamer properties mpegdashPlaylistHostProtocol and mpegdashChunkHostProtocol. Port has to set in Host header on proxy.

This question has received the maximum number of answers.