WebOS Struggles w/ DS4K+HDR Content

[bitmap]

Do you by any chance agreed to everything under the terms of service for the TV? I had terrible performance issues on the JF app, manifesting itself similar to what you describe, until I deselected everything under the terms agreements and only kept the required terms. Turns out selecting all of that stuff makes your TV eat through a lot of memory and is specially noticeable during 4K HDR Playback in which audio is being transcoded or if you are using complex ASS subtitles, at least that was my experience.

You may also want to unplug the TV for around 5 mins to clear out some memory just in case.

Nope, the bare minimum to get Jellyfin installed. Most of that stuff is blocked on my network anywho.

On the encoding front, I tried encoding using av1_qsv and the DV metadata still appears in the video stream:

Code:

  Stream #0:0: Video: av1, 1 reference frame (AV01 / 0x31305641), qsv(tv, bt2020nc/bt2020/smpte2084, progressive, topleft), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 23.98 fps, 1k tbn (default)
      Metadata:
        BPS            : 64976076
        DURATION        : 02:01:30.033000000
        NUMBER_OF_FRAMES: 174786
        NUMBER_OF_BYTES : 59209717365
        SOURCE_ID      : 001011
        _STATISTICS_WRITING_APP: mkvmerge v88.0 ('All I Know') 64-bit
        _STATISTICS_WRITING_DATE_UTC: 2024-10-26 03:02:25
        _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES SOURCE_ID
        title          : AV1 Encoding by nAV1s
        encoder        : Lavc61.3.100 av1_qsv
      Side data:
        DOVI configuration record: version: 1.0, profile: 7, level: 6, rpu flag: 1, el flag: 1, bl flag: 1, compatibility id: 6

While in my experience, this can be mostly harmless, WebOS seems to sometimes interpret it as actual metadata -- or there are other issues beyond my current understanding -- and it completely blows out the picture to bright magenta. Am I doing something incorrectly to strip this out automatically? Even if the metadata is persistent, how would I even verify whether the media has the DV layer intact?

[TheDreadPirate]

What is "jffmpeg" aliased to? Is it attached to something other than jellyfin-ffmpeg 7.0.2-5?

My understanding is simply using av1_qsv with DV 7.6 and 8 will automatically strip the DV RPU and EL.

Code:

Stream #0:0(eng): Video: av1 (libdav1d) (Main), yuv420p10le(tv, bt2020nc/bt2020/smpte2084, progressive), 3840x1600, SAR 1:1 DAR 12:5, 23.98 fps, 23.98 tbr, 1k tbn
      Metadata:
        BPS-eng         : 59752391
        DURATION-eng    : 02:35:26.608958333
        NUMBER_OF_FRAMES-eng: 223615
        NUMBER_OF_BYTES-eng: 69660891904
        SOURCE_ID-eng   : 001011
        _STATISTICS_WRITING_APP-eng: MakeMKV v1.17.7 win(x64-release)
        _STATISTICS_WRITING_DATE_UTC-eng: 2024-08-24 17:31:16
        _STATISTICS_TAGS-eng: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES SOURCE_ID
        ENCODER         : Lavc61.3.100 av1_qsv
        DURATION        : 02:35:26.609000000

However, I also am using different filters than you and am I not scaling the video. I'm wondering if how you use filters is causing the DV BSF to not trigger.

Don't use any of your filters and scaling and see what happens. If that does work, this would probably be something that needs to be fixed.

[bitmap]

What is "jffmpeg" aliased to?  Is it attached to something other than jellyfin-ffmpeg 7.0.2-5?

Code:

alias jffmpeg="/usr/lib/jellyfin-ffmpeg/ffmpeg -y -hide_banner -v verbose -stats"

I'll give it a shot without filters today.

[gnattu]

Again, it is not related to DV, it is webOS HLS player in general. There is no easy fix unless you pre-transcode your file and let the webOS direct play it.