Skip to content

Official support for LG WebOS TV #1330

Open

Description

@kingctan

Does this player support LG WebOS TV for DASH&playready combination?
Thanks.

Activity

  1. chrisfillmore commented on Mar 2, 2018

    @chrisfillmore
    Contributor

    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.

  2. joeyparrish commented on Mar 2, 2018

    @joeyparrish
    Member

    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.

  3. avelad commented on Mar 2, 2018

    @avelad
    Member

    We are using ShakaPlayer with WebOS 3.5 and DASH+Widevine without any problem.

  4. ismena commented on Mar 19, 2018

    @ismena
    Contributor

    @kingctan Does this answer your question? Is there anything else we can do?

  5. chrisfillmore commented on Mar 23, 2018

    @chrisfillmore
    Contributor

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

  6. avelad commented on Mar 23, 2018

    @avelad
    Member

    @chrisfillmore , What versions of WebOS have you tried? I only tried WebOS 3.5.

  7. ismena commented on Mar 23, 2018

    @ismena
    Contributor

    Let's get our TL to consider it!
    @joeyparrish

  8. shaka-bot commented on Mar 27, 2018

    @shaka-bot
    Collaborator

    @kingctan Does this answer all your questions? Can we close the issue?

  9. joeyparrish commented on Mar 27, 2018

    @joeyparrish
    Member

    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.

  10. shaka-bot commented on Mar 31, 2018

    @shaka-bot
    Collaborator

    @kingctan Does this answer all your questions? Can we close the issue?

  11. 56 remaining items

  12. avelad commented on Apr 29, 2024

    @avelad
    Member

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

  13. stuartflanagan commented on Apr 29, 2024

    @stuartflanagan

    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 4032 error.
    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 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?

        this.player
          .load(mediaItem.manifest, startTime)
          .then(() => {
            handlePlayerReady();
          })
          .catch(error => {
            this.error = error;
            this.dispatchEvent(new Event('error'));
          }); 
    
  14. avelad commented on Apr 29, 2024

    @avelad
    Member

    Are you using fMP4 or TS?

  15. stuartflanagan commented on Apr 29, 2024

    @stuartflanagan

    TS

  16. avelad commented on Apr 29, 2024

    @avelad
    Member

    The commit that may impact is: #6382

  17. stuartflanagan commented on Apr 29, 2024

    @stuartflanagan

    Thank you I will see how I go.

  18. stuartflanagan commented on Apr 30, 2024

    @stuartflanagan

    Seems to be affecting MPEGDASH and DRM as well.
    Same error 4032.

  19. stuartflanagan commented on May 2, 2024

    @stuartflanagan

    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-player lib 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.

  20. rampratapyadav91 commented on Jul 22, 2024

    @rampratapyadav91

    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 ?

  21. changed the issue type fromtoon Jul 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    flag: seeking PRWe are actively seeking PRs for this; we do not currently expect the core team will resolve thisplatform: WebOSIssues affecting WebOS

    Type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions