360 DASH videos not working in Chrome on Android, Shaka player complaining about media type

475 views
Skip to first unread message

Yang Zuo

unread,
Oct 3, 2017, 2:43:34 AM10/3/17
to Shaka Player Users

I am trying to build a demo with Shaka player and A-frame to display 360 videos that support DASH. It works fine in Chrome on Windows and Linux but on an Android device it always complains about

"CustomEvent {isTrusted: false, detail: Error: The browser does not support the media content. at V.k.Vb (https://blueflow.info:8090/dem…, …}
bubbles
:
true
cancelBubble
:
false
cancelable
:
false
composed
:
false
defaultPrevented
:
false
detail
:
Error: The browser does not support the media content. at V.k.Vb (https://blueflow.info:8090/demo/shaka-player.compiled.js:182:293)
eventPhase
:
0
isTrusted
:
false
path
:
[]
returnValue
:
true
timeStamp
:
109396.58000000002
type
:
"error"
currentTarget
:
(...)
srcElement
:
(...)
target
:
(...)
get currentTarget
:
ƒ ()
set currentTarget
:
ƒ (a)
get srcElement
:
ƒ ()
get target
:
ƒ ()
set target
:
ƒ (a)
__proto__
:
CustomEvent".

The video file is a normal 360 video downloaded from the Internet and then re-encoded with MP4Box and X264. What could be the trick to get it working? I believe A-frame has no problems cause other DASH video downloaded from the dataset can be displayed on the sphere and displayed normally. The question is really what is what might be the cause for the issue? Seems Shaka player on an android device is not working the same way as is on a desktop.

Joey Parrish

unread,
Oct 3, 2017, 2:17:52 PM10/3/17
to Shaka Player Users
Hi Yang,

"The browser does not support the media content" is an error message from Shaka v1.  Shaka v2 has been out for more than a year.  I highly recommend you upgrade.  We have an upgrade guide you can use to make the transition.

Generally, when the browser fails to play back a piece of content, the media can't be demuxed or decoded by the browser.  This is out of Shaka's hands, and is usually caused by a bad encoding.  Sometimes, the content is encoded in a way that works for progressive playback (video.src = ...), but not for MediaSource (as Shaka uses).

In Chrome, you can get details about the error by opening a tab and typing "chrome:media-internals" in the address bar.  Find the button whose label matches the value of "video.src" and click it.  Details will appear in tables at the bottom of the page.

If you need help understanding the data from media-internals, we can help you.

Does this help?

Thanks,
Joey



--
You received this message because you are subscribed to the Google Groups "Shaka Player Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to shaka-player-users+unsub...@googlegroups.com.
To post to this group, send email to shaka-player-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/shaka-player-users/accfc386-51f3-4474-9059-10ebc43b9a92%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages