Skip to content

Direct Play hangs or fails on newer firmware: tracking issue #1259

Open
3 of 5 issues completed
Open

Description

@GLinnik21

Goal

Direct Play starts, resumes and seeks reliably on webOS 5 and newer, on the TV models reported below.

Reports

Grouped so the pieces stay together. The causes are not confirmed to be the same; each report stays open until its own cause is found.

Related, not a Direct Play failure: #1327 (closed 2026-11-16). On the same 32LQ63006LA set, the detail page's facts row described the first version while Play started the one the set can decode (#1245); fixed in #1379 (merged 2026-11-16). #1421 (merged 2026-11-17) makes the version choice judge each version's Dolby Vision as the direct-play gate does. The same Play Version list was the subject of #1404 (webOS 9.2.0, OLED65G49LS, 0.10.0, a different server; closed 2026-11-18): the detail read sent no client identity, so a server that tailors Media[] per client (the reporter's is Ether, a Plex-compatible server) listed fewer versions in the picker than playback saw. Fixed in #1456 (merged 2026-11-18): metadata reads now carry the same client identity as playback. A loopback test shows the difference; the Ether result itself is the reporter's.

Also related, not a Direct Play failure: #1378. On a webOS 6.5.3 set (75QNED91TPA) the app cannot read the firmware's codec-capability file from its sandbox, so it plans playback against another set's decoder profile. The cause of the missing file is not determined yet. #954's log (webOS 5.6.2) also shows the fallback to that profile; whether the reason is the same unreadable file is not known.

Also related, not a Direct Play failure: #1427. docs/dolby-vision.md and devcaps::EXCLUSIONS list webOS 6.5.3-47 (LG C1) as IDR-first, so Feed withdraws Dolby Vision at a landing that is not an IDR picture there. From that firmware image (static reading), nothing builds the splitter the rule comes from, so the exclusion may cost the C1 its Dolby Vision for nothing. It is the other side of #1426 and of the fix in #1263, and it needs a check on a C1.

Also related, not confirmed as a Direct Play failure: #1475 (webOS 10.3.2-34, 55UA7050PUB, nightly 20261119, a remote server). With Force Direct Play on, the play stops with "The server didn't allow the original file to play", and the log reads original: no candidate (forced direct play): the server answered the direct-play decision with a conversion. The reporter's server limits remote streams to 1080p, so the leading suspect is that bitrate cap, not the set. The cause is not confirmed yet. The reporter will retry with Limit remote stream bitrate at Original (No limit) and send the decision: lines. If the server still refuses, it becomes a report here.

Done

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingplaybackPlayback, the player and its controls

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions