shaka-project
Shaka letting native player to do work even if preferNativeHls is set to false
Have you read the Tutorials? Yes
Have you read the FAQ and checked for duplicate open issues? Yes
If the question is related to FairPlay, have you read the tutorial?
Not related
What version of Shaka Player are you using? 4.7.13
What browser and OS are you using? WebOS 24
Please ask your question How come Shaka is not responsible for things like downloading segments on WebOS 24 platform even if preferNativeHls flag is set to false? I don't see any segments being fetched when looking at network tab of Chrome dev tools. Only if I play DRM protected content using Shaka segments are being loaded by Shaka.
@tra83 can you give URL for the content that caues the issue for you?
@tykus160 Unfortunately no as all our streams require authentication but I would guess any non-DRM HLS or DASH content would behave same letting native player of WebOS to take care of loading and playing segments.
Do you have the same issue with our Demo contents? DO you have the same issue with our latest release or the main branch?
I just tested demo content https://storage.googleapis.com/shaka-demo-assets/bbb-dark-truths-hls/hls.m3u8 with both Shaka 4.7.13 and latest 4.14.12 and in both cases on WebOS 24 it is native player which loads segments and not Shaka.
Do you know what is the latest WebOS version Shaka works correctly when prefereNativeHls is set to false?
@tykus160 when you say you cannot reproduce, does it mean that on your WebOS devices Shaka is responsible for playing HLS and you are able to see segments being fetched by Shaka (and not platform's native player) ?
@tra83 I don't have webOS device now unforunately. I've tried to replicate it on Tizen but without a success. Can you give it another try on 4.15?
@tykus160 even latest Shaka 4.15.1 is letting native player to handle task. This is what's being printed to console when using debug build:
Using native ARIAMixin interface. MediaSource.install Device: WebOS v24; Type: TV Using native MSE as-is. <---------- !!! Using native screen.orientation randomUUID.install RandomUUID: Native window.crypto.randomUUID() support found. Symbol.install VideoPlayPromise.install Using native VTTCue. MediaCapabilities: install
@avelad problem is that it is not Shaka player which handles playback but native player of WebOS. I think this row from the logs indicates it pretty clear: Using native MSE as-is.
Shouldn't Shaka handle everything when preferNativeHls is set to false?
Using native MSE as-is. is the log from our polyfill. This does not indicate that the playback is using one thing or the other.
To see what it is actually using I recommend you use the getLoadMode function
Can you fill out the following table for us?
| preferNativeHls | getLoadMode |
|---|---|
| true | ? |
| value | ? |
Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including @shaka-bot reopen in a comment.
