Skip to content

Shaka letting native player to do work even if preferNativeHls is set to false #8579

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

Open
tra83 opened this issue May 9, 2025 · 14 comments
Open
Labels
platform: WebOS Issues affecting WebOS status: unable to reproduce Issue could not be reproduced by the team type: question A question from the community

Comments

@tra83
Copy link

tra83 commented May 9, 2025

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 tra83 added the type: question A question from the community label May 9, 2025
@tykus160
Copy link
Member

@tra83 can you give URL for the content that caues the issue for you?

@avelad avelad added the status: waiting on response Waiting on a response from the reporter(s) of the issue label May 13, 2025
@tra83
Copy link
Author

tra83 commented May 13, 2025

@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.

@shaka-bot shaka-bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label May 13, 2025
@avelad
Copy link
Member

avelad commented May 14, 2025

Do you have the same issue with our Demo contents? DO you have the same issue with our latest release or the main branch?

@avelad avelad added the status: waiting on response Waiting on a response from the reporter(s) of the issue label May 14, 2025
@tra83
Copy link
Author

tra83 commented May 14, 2025

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.

@shaka-bot shaka-bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label May 14, 2025
@avelad
Copy link
Member

avelad commented May 20, 2025

@tra83 do you reproduce the same issue in other WebOS versions?

@avelad avelad added the status: waiting on response Waiting on a response from the reporter(s) of the issue label May 20, 2025
@tra83
Copy link
Author

tra83 commented May 23, 2025

@avelad haven't tested on other versions.

@shaka-bot shaka-bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label May 23, 2025
@tra83
Copy link
Author

tra83 commented May 27, 2025

Do you know what is the latest WebOS version Shaka works correctly when prefereNativeHls is set to false?

@avelad avelad added the platform: WebOS Issues affecting WebOS label Jun 2, 2025
@avelad
Copy link
Member

avelad commented Jun 2, 2025

@tykus160 ?

@tykus160
Copy link
Member

tykus160 commented Jun 2, 2025

Cannot reproduce it on any of my devices unfortunately.

@avelad avelad added status: unable to reproduce Issue could not be reproduced by the team status: waiting on response Waiting on a response from the reporter(s) of the issue labels Jun 2, 2025
@tra83
Copy link
Author

tra83 commented Jun 6, 2025

@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) ?

@shaka-bot shaka-bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label Jun 6, 2025
@tykus160
Copy link
Member

tykus160 commented Jun 6, 2025

@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?

@tra83
Copy link
Author

tra83 commented Jun 6, 2025

@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
Copy link
Member

avelad commented Jun 9, 2025

I don't see any problem in the logs...

@avelad avelad added the status: waiting on response Waiting on a response from the reporter(s) of the issue label Jun 9, 2025
@tra83
Copy link
Author

tra83 commented Jun 10, 2025

@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?

@shaka-bot shaka-bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform: WebOS Issues affecting WebOS status: unable to reproduce Issue could not be reproduced by the team type: question A question from the community
Projects
None yet
Development

No branches or pull requests

4 participants