Repository navigation
Description
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.
- [webOS 5.6.2 / k6lp] Playing error 100 after accepted Load on 4K H.264 direct play #954 4K H.264 on webOS 5.6.2 (60UN7310). The first report was error 100 after an accepted Load; on nightly 20261110 the Load is refused before any picture with 104
fail to create AVProxy, and the HLS fallback plays. A separate stop in the fallback's quality upgrade is fixed in fix(playback): preserve HLS when an ABR candidate is cancelled #1326. The 104 refusal is still being investigated; waiting for a retest on a build with fix(playback): preserve HLS when an ABR candidate is cancelled #1326 (0.10.0 has it). On 2026-11-16 the maintainer asked the reporter for three short tries (the first play after opening the app, a play after a 1080p title, and optionally the Experimental engine) to separate "4K" from "first play"; no answer yet. On nightly 20261113 the 60UN7310's owner reported positive first impressions, and the report says that is not a confirmation that 4K H.264 direct play is fixed. - URI: Dolby Vision MP4 can stall after a seek on webOS 5.5.0-19 (IDR-first splitter) #1426 URI backend: a Dolby Vision MP4 can stall after a seek on webOS 5.5.0-19 (e.g. LG CX). From the firmware (static reading, not yet seen on a set): the TV's
dvbinbuilds advsplitterthat accepts only IDR pictures (NAL 19/20) as the first picture after a flush, so a seek that lands on a CRA sync sample can stall, the way Every seek or resume hangs on Buffering #1166 did on Feed. Feed already withdraws its Dolby Vision declaration at such a landing (Playback: a Dolby Vision resume or seek that lands on a CRA plays the HDR10 base layer #1263); the URI backend has no counterpart. The report names two possible fixes (decline URI for a Dolby Vision MP4 on IDR-first firmware, or reload without Dolby Vision on a stalled landing) and needs a repro on a 5.5.0-19 set; testers for URI mode on webOS 5 and newer are collected in URI mode on webOS 5+: looking for testers with a newer TV #1064. The open PR URI: declare Dolby Vision on the Load as Standard does #1399 (the URI Load declares Dolby Vision as Standard does, so a C1 reports Dolby Vision instead of HDR10) is a separate piece: URI: Dolby Vision MP4 can stall after a seek on webOS 5.5.0-19 (IDR-first splitter) #1426 notes the stall does not depend on that node.
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
- [webOS 9.2.2/OLED55B2] regression: direct play of basic H264 no longer functional with 0.9.0, 0.10.0 nightlies #1096 H.264 Direct Play buffers indefinitely (webOS 9.2.2, OLED55B2): the cause in the reporter's logs is fixed in Preserve baseline audio codecs and size converted Opus on webOS #1133 (0.10.0), and a second set with the same failure (32LQ63006LA, webOS TV Lite 7.6.0) direct plays. Closed 2026-11-14; the original reporter has not confirmed.
- Every seek or resume hangs on Buffering #1166 Every seek or resume hangs on Buffering (webOS 5.5, OLED55CX): fixed in Playback: a Dolby Vision resume or seek that lands on a CRA plays the HDR10 base layer #1263.
- [webOS 10.3.1 / O22] 1080p H.264/AAC MP4 hangs indefinitely on Direct Play (abnormal audio timestamps, missing PPS) #1084 1080p H.264/AAC MP4 hangs on Direct Play (webOS 10.3.1): fixed in Playback: an MPEG-TS stream under a .mp4 name direct-plays, with its framing, audio and clock (#1084) #1190.
Activity