You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't think that Shaka team has investigated this platform specifically. Generally speaking, Shaka supports any platform that is spec-compliant, but in my experience these kinds of smart TV platforms are not very mature and require extensive testing, validation, and workarounds. Things are getting better, though.
We will soon be investigating LG WebOS for DASH-PR, so you may soon see tickets related to this platform, and you'll get a better sense for whether or not Shaka will work on these TV's.
@ismena I have a question. It seems there are at least 3 projects using Shaka on LG WebOS: @kingctan, @avelad, and me. Would Shaka team be willing to adopt this as an officially supported platform?
If you can send us some documentation on WebOS testing, we could consider adding a WebOS device to our test lab. We can't call it an officially supported platform until we are running tests on it nightly to make sure we don't break it. But in general, expanding our platform coverage is a Good Thing:tm:.
In particular, we would appreciate any tips on how to automate directing the device to an arbitrary URL. That's a key part of the testing process with Karma.
The error occurs in thePlayer load sequence. Has there been any change to the isSupported method used?
It seems it is now returning false for webOS this is webOS3 through webOS2024
Happy to have a look at this. Can you please point me to any commits that may have impacted isSupported method?
minimumUpdatePeriod is 30 for live content which is causing delayed playback start if I am keeping rebufferinggoal as 30 and if set ignoreminbuffertime true then seeing a stall during playback, how to configure shaka for lower webos so that there is not any delayed playback start as well as any stall ?
Activity
chrisfillmore commentedon Mar 2, 2018
I don't think that Shaka team has investigated this platform specifically. Generally speaking, Shaka supports any platform that is spec-compliant, but in my experience these kinds of smart TV platforms are not very mature and require extensive testing, validation, and workarounds. Things are getting better, though.
We will soon be investigating LG WebOS for DASH-PR, so you may soon see tickets related to this platform, and you'll get a better sense for whether or not Shaka will work on these TV's.
joeyparrish commentedon Mar 2, 2018
We have never tested Shaka Player on this platform, but you can help by running our support page and sending a screenshot: https://shaka-player-demo.appspot.com/support.html
This will tell us whether or not the platform has the basic capabilities we need, and if so, what specific containers, codecs, and DRM systems it has.
avelad commentedon Mar 2, 2018
We are using ShakaPlayer with WebOS 3.5 and DASH+Widevine without any problem.
ismena commentedon Mar 19, 2018
@kingctan Does this answer your question? Is there anything else we can do?
chrisfillmore commentedon Mar 23, 2018
@ismena I have a question. It seems there are at least 3 projects using Shaka on LG WebOS: @kingctan, @avelad, and me. Would Shaka team be willing to adopt this as an officially supported platform?
avelad commentedon Mar 23, 2018
@chrisfillmore , What versions of WebOS have you tried? I only tried WebOS 3.5.
ismena commentedon Mar 23, 2018
Let's get our TL to consider it!
@joeyparrish
shaka-bot commentedon Mar 27, 2018
@kingctan Does this answer all your questions? Can we close the issue?
joeyparrish commentedon Mar 27, 2018
If you can send us some documentation on WebOS testing, we could consider adding a WebOS device to our test lab. We can't call it an officially supported platform until we are running tests on it nightly to make sure we don't break it. But in general, expanding our platform coverage is a Good Thing:tm:.
In particular, we would appreciate any tips on how to automate directing the device to an arbitrary URL. That's a key part of the testing process with Karma.
shaka-bot commentedon Mar 31, 2018
@kingctan Does this answer all your questions? Can we close the issue?
56 remaining items
avelad commentedon Apr 29, 2024
@stuartflanagan In 4.8.0 there are the following related changes:
Anyway to fix any bug we need a test stream.
Please note that this is an unofficially supported platform, so if you want to submit a PR to fix this, we'd be happy to review it.
stuartflanagan commentedon Apr 29, 2024
Thanks @avelad.
The issue actually occurs with any HLS stream. not just AES encrypted.
But here is a demo stream from unified that also triggers the
4032error.https://demo.unified-streaming.com/k8s/features/stable/video/tears-of-steel/tears-of-steel-aes.ism/.m3u8
The error occurs in thePlayer load sequence. Has there been any change to the
isSupportedmethod used?It seems it is now returning false for
webOSthis is webOS3 throughwebOS2024Happy to have a look at this. Can you please point me to any commits that may have impacted
isSupportedmethod?avelad commentedon Apr 29, 2024
Are you using fMP4 or TS?
stuartflanagan commentedon Apr 29, 2024
TS
avelad commentedon Apr 29, 2024
The commit that may impact is: #6382
stuartflanagan commentedon Apr 29, 2024
Thank you I will see how I go.
stuartflanagan commentedon Apr 30, 2024
Seems to be affecting MPEGDASH and DRM as well.
Same error 4032.
stuartflanagan commentedon May 2, 2024
Hi @avelad just wondering if I can get some help contributing for this issue.
I realise this ticket is probably not the place to do it as it is regarding offical support.
At present I have the
shaka-playerlib forked and it is building.webOS is returning 4032 for manifest media types
HLS: https://demo.unified-streaming.com/k8s/features/stable/usp-s3-storage/tears-of-steel/tears-of-steel.ism/.m3u8
MPD: https://storage.googleapis.com/shaka-demo-assets/angel-one/dash.mpd
The interesting thing is when I switch to the debug player to investigate the logs playback is fine with no 4032 error code.
rampratapyadav91 commentedon Jul 22, 2024
minimumUpdatePeriod is 30 for live content which is causing delayed playback start if I am keeping rebufferinggoal as 30 and if set ignoreminbuffertime true then seeing a stall during playback, how to configure shaka for lower webos so that there is not any delayed playback start as well as any stall ?