Skip to content

URI: Dolby Vision MP4 can stall after a seek on webOS 5.5.0-19 (IDR-first splitter) #1426

Open

Description

@GLinnik21

On webOS 5.5.0-19 (jhericurl-jervisbay, e.g. LG CX on 04.50.90) the URI backend can hang a Dolby Vision MP4 after a seek or resume, the same way #1166 hung Feed. It does not depend on the DolbyHdrInfo node (#1399).

From the firmware (static reading, not yet seen on a set):

  • On the URI path the TV's qtdemux reads the file's dvcC/dvvC and, when the set reports Dolby Vision support, sets caps dolby-vision=TRUE + dolby-vision-profile (profile 5/8/9; profile 7 is excluded from 5.5 on).
  • dvbin (libgstlxvideodec, rank 291) builds dvsplitter → dvmdparse → dualsequencer from those caps.
  • That dvsplitter (0cda1717…) accepts only NAL 19/20 as the first picture after FLUSH_STOP. A seek lands on the sync sample stss lists; if that is a CRA, every buffer is skipped.
  • Feed handles this by withdrawing its declaration (dv_start); the URI backend has no counterpart, and the TV builds the chain from the file whether or not we declare anything.

Same gate on 3.4.3 and 3.9.2. 4.4.3, 4.10.2 and 5.6.2 accept 16–21; 6.5.3 and later build no splitter.

Repro to try on a 5.5.0-19 set: URI play of a P8.1 MP4 whose random-access points after the first are CRAs, seek mid-file.

Possible fixes: decline URI for a Dolby Vision MP4 on IDR-first firmwares (Caps::dv_first_picture), or reload without Dolby Vision on a stalled landing.

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

    bugSomething isn't workingplaybackPlayback, the player and its controlswebos-3webOS 3.x TVs (2016-2017 models)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions