Announcement

Collapse
No announcement yet.

Error 702 with AV1 HDR10+ Content for MKV (The case for upgrading ffmpeg)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Netflix Error 702 with AV1 HDR10+ Content for MKV (The case for upgrading ffmpeg)

    This was discussed with back and forth between Germania and I. Still no resolution, so posting a formal issue.

    AV1 SDR is available on all plans, but Premium has AV1 HDR10+

    If you try to download content in AV1 with a Premium plan, StreamFab is served the version with HDR10+ (if available of course)

    StreamFab downloads it, but doesn't show the HDR10 pill. When it tries to assemble the chunks (Processing) before remuxing to MKV, StreamFab returns error code 702.

    Relevant StreamFab.log entries:

    Code:
    [Info]: Remux show module: "Netflix"
    [Info]: Remux show showname: "Designated Survivor"
    [Info]: Remux show seasontext: "Season 3"
    [Info]: Remux show episodename: "#thesystemisbroken"
    [Info]: Remux show episodetext: "Season 3"
    [Info]: Remux show seasonnumber: 3
    [Info]: Remux show episodenumber: 1
    [Info]: Remux show year: "2019"
    [Info]: Remux show resolution: "1080P"
    [Info]: Remux show videocodec: "AV1"
    [Info]: Remux show videorange: "SDR"
    [Info]: Remux show audiocodec: "EAC3"
    [Info]: Remux show resolutionwidth: 1920
    [Info]: Remux show resolutionheight: 1080
    [Info]: Remux show showname after change:  "Designated Survivor"
    [Info]: Remux show seasontext after change:  "Season 3"
    [Info]: Remux show episodename after change:  "#thesystemisbroken"
    ​...
    ...
    ...
    [Info]: [CefMedia]  Invalid Mastering Display Color Volume box\r\n[mov,mp4,m4a,3gp,3g2,mj2 @ 0000014b239276c0] error reading header\r\nD:/StreamFab/Temp/outputTemp/Netflix/2025_04_30_16_05_09_81015334/video/1392399577: Invalid data found when processing input\r\n
    [Info]: [CefMedia] StartRemuxMultiAudioSrtMetaUtil BROKEN_PIPE exit.
    As you may or may not know, in order to generate an HDR10+ file, you need to pass the metadata, and it looks like the ffmpeg version used doesn't do that for MKV.

    For MP4, it does work, although the metadata for HDR is in triplicate, and other meta is in duplicate:

    Click image for larger version  Name:	image.png Views:	0 Size:	294.2 KB ID:	462461
    If i use MP4, the resulting file has HDR10 metadata but Kodi cannot play the file. MPC-HC does play the file. The extra metadata might be why Kodi fails as it does support HDR10 is trying to play it correctly while MPC-HC does tone mapping...

    If i use MKVToolnix 92 to remux the StreamFab mp4 to mkv, the resulting file is HDR10 and it has proper metadata:

    Click image for larger version  Name:	image.png Views:	0 Size:	58.5 KB ID:	462462

    If i then take the mkvtoolnix file and use ffmpeg to remux back into an mp4, the metadata is fixed and it plays in Kodi

    Observations and findings:
    • When StreamFab remuxes the AV1 HDR10+ file to MP4, the remux progress bar fills up and restarts 3-4 times.
    • Upgrading StreamFab's ffmpeg to ffmpeg version 7.1.1, the remux to MKV now works.
    • Upgrading StreamFab's mp4box to mp4box 2.4-rev0-g5d70253a-master does not fix the metadata or Kodi playback
    All this to say, ffmpeg inside StreamFab needs to be updated ( @Cats4U) ! I was testing as i was writing this so when i actually fixed it, i had written a lot so i just edited it a bit to add ffmpeg info as i didn't want to have wasted my time

    There probably should be a new option added to the Netflix codec selection/settings:
    • Rename AVI to AV1 - SDR
    • Add AV1 - HDR10+

    #2
    In summary: confirmed (not surprising)

    OK, I tried Designated Survivor.s03e01 with unchanged SF 6234
    (btw: I never get the AV1 Standard offer with Premium plan)

    I get the same (Original + changed) values with mp4 created by mp4box:

    Track name + Performer (?) = epi title
    Code:
    HDR format : SMPTE ST 2086, HDR10 compatible / SMPTE ST 2086, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
    MasteringDisplayColorPrimaries_Original + MasteringDisplay_Luminance_Original + MaxCLL_Original + MaxFALL_Original
    with mkv (ffmpeg) I get error 702 "Invalid Mastering Display Color Volume box" (ffmpeg 6.0)
    with mkv (mkvtoolnix) all fine and correct entries (mkvmerge v68)

    After replace ffmpeg with 7.1.1 error 702 is away
    HDR format : SMPTE ST 2086, HDR10 compatible
    and like mp4box (but without MasteringDisplayColorPrimaries_Original)
    MasteringDisplay_Luminance_Original + MaxCLL_Original + MaxFALL_Original
    and new => VENDOR_ID : [0][0][0][0]

    With my standard player mpc-hc it is only slightly darker ..
    .. but I think mkvmerge should be the best choice for Kodi at the moment

    I have never experienced an SF problem with the current ffmpeg​

    Comment


      #3
      So FFMPEG is a different sub-app? I usually replace MKVMerge each time I update SF. No longer doing MP4Box due to the same error code 702 on Disney+.
      I have been following the FFMPEG release notes so I do see where you are coming from.

      Wilson.Wang are we able to see the module updated?

      Comment


        #4
        Originally posted by MrGrackle View Post
        So FFMPEG is a different sub-app?
        see also: Programs under the hood

        If you only use mkv (MKVToolnix) aka mkvmerge, ffmpeg is not used by SF


        > are we able to see the module updated?

        The only app that is regularly updated is the modified yt-dlp
        (as YoutubeToMP3Process)​

        Comment


          #5
          Originally posted by Germania View Post
          see also: Programs under the hood

          If you only use mkv (MKVToolnix) aka mkvmerge, ffmpeg is not used by SF


          > are we able to see the module updated?

          The only app that is regularly updated is the modified yt-dlp
          (as YoutubeToMP3Process)​
          So one has to force MKVToolnix in the download options to get it to work correctly? One ASSumes when you do that, that you have to replace the obsolete v68 with a later one (90 or 91) ?

          Comment


            #6
            Originally posted by MrGrackle View Post
            So one has to force MKVToolnix in the download options to get it to work correctly?
            Nope, you wrote: "replace MKVMerge each time I update SF"
            So I assumed that mkv (mkvtoolnix) is your default
            then it would make no sense to update (in this case unused) ffmpeg

            > One ASSumes when you do that, that you have to replace the obsolete v68 with a later one (90 or 91) ?

            Originally posted by Germania View Post
            I've never found a mkvmerge problem (from other users) ..
            .. that could be fixed by me with current mkvmerge release​
            ​​
            btw: currently stable is v92

            Comment


              #7
              Originally posted by Germania View Post


              > One ASSumes when you do that, that you have to replace the obsolete v68 with a later one (90 or 91) ?

              ​​
              btw: currently stable is v92
              I am stuck at 91 as it has not reminded me yet of a new version available. Maybe it's set to check once a month.

              Comment


                #8
                Originally posted by MrGrackle View Post
                I am stuck at 91 as it has not reminded me yet of a new version available. Maybe it's set to check once a month.
                I received the information in GUI automatically after released 2025-04-26



                You can force with Help => Check for updates

                I can't see a setting for update check interval
                but in mkvtoolnix-gui.ini
                Code:
                updates\checkForUpdates=true
                updates\lastUpdateCheck=@DateTime(\0\0\0\x10\0\0\0\0\0\0%\x8c\x7f\x4\x9a\x6w\0)


                edit
                MKVToolNix GUI does a check for updates right when it starts if no check was done within the last 24 hours​
                Last edited by Germania; 05-04-2025, 04:01 PM.

                Comment


                  #9
                  Originally posted by Germania View Post
                  In summary: confirmed (not surprising)

                  OK, I tried Designated Survivor.s03e01 with unchanged SF 6234
                  (btw: I never get the AV1 Standard offer with Premium plan)
                  What I meant was, unlike the current state of H265, you can get AV1 SDR and AV1 HDR10+ when you have the Premium plan.

                  If you remember, at some point, you could get H265 SDR or H265 HDR10 for all titles made by Netflix. Things not made by Netflix only had H264 and VP9. Eventually, Netflix removed the H265 SDR profile and we could only get those in H264 or VP9.

                  With AV1 SDR, you can pretty much get that with everything on Netflix. Makes sense since Netflix helped create AV1, the successor to VP9.

                  You get AV1 HDR10+ for Netflix made shows and movies.

                  So the new rules for modern codecs (H265 & AV1) are:
                  • Netflix made TV Shows and Movies: H265 HDR10, H265 Dolby Vision, AV1 SDR, AV1 HDR10+
                  • Non-Netflix made TV Shows and Movies: AV1 SDR
                  For example,

                  The Rookie is new but not a Netflix show and only has AV1 SDR
                  Dark is a Netflix show but it is older so it also has AV1 SDR
                  Britain and The Blitz is a new Netflix movie and it has H265 HDR10, H265 Dolby Vision, AV1 HDR10+

                  Comment


                    #10
                    Originally posted by jpp72 View Post
                    There probably should be a new option added to the Netflix codec selection/settings:​
                    • Rename AVI to AV1 - SDR
                    • Add AV1 - HDR10+
                    Unfortunately, I can't see the benefit of an AV1 split in SDR/HDR10+
                    when there doesn't seem to be a choice.

                    If the title is only offered in AV1 SDR (Standard or Premium) ..
                    .. you cannot use/select HDR10+.
                    And if the title is offered with Premium in HDR10+ ,,
                    .. there will apparently be no SDR to choose from.

                    Anyway, I cannot detect the SDR bitrates of an (with Premium)
                    HDR10+ available title after API call in Streamfab.log.
                    And this also applies to old SF versions before AV1 HDR10+
                    was announced and therefore not explicitly queried in SF.

                    If there should be a possibility to offer both for same title, this is of course invalid


                    On the other hand, however, I see the next problem on the horizon
                    if only single episodes of a season offer HDR10+, as is/was the case here

                    Comment


                      #11
                      Originally posted by jpp72 View Post

                      So the new rules for modern codecs (H265 & AV1) are:
                      • Netflix made TV Shows and Movies: H265 HDR10, H265 Dolby Vision, AV1 SDR, AV1 HDR10+
                      • Non-Netflix made TV Shows and Movies: AV1 SDR
                      For example,


                      Did the audio issues get sorted out when AV1 is selected? Certain audio streams were unavailable when AV1 was selected. There were several threads on the topic. I would love to replace my h264 encodes with AV1 versions.

                      As someone that has several Sony branded 4K TVs in the house, I go all in on DoVi. I have a personal F-U reserved for Samsung and their refusal to support it, even if it was offered as an aftermarket licensing fee. Refusing to offer the option of a standard format is just a dickish move. Looks like their next movie is to snip Dolby Atmos from their offerings as well and replacing it with Google's spatial audio. Again, Atmos is a widely accepted standard.

                      Nowadays on youtube, if something is not offered in an AV1 option I am a bit miffed. Sometimes you stumble across something that is still on h264.

                      Of course anything at all from SF I always check the scene anyway, in case there's 4K available.

                      Comment


                        #12
                        Originally posted by MrGrackle View Post
                        Did the audio issues get sorted out when AV1 is selected?
                        I have never had an audio problem with NF with or without AV1 since 6227 here

                        And the missed AAC 128k here has nothing todo with selected video codec

                        Comment


                          #13
                          I will ask the dev to update ffmpeg and MKVToolNix to the latest version, may can be released at next week.

                          Wilson
                          Please post your logs the default location is:
                          For DVDFab 13: C:\Users\User Name\My Documents\DVDFab\DVDFab13\Log
                          For StreamFab: C:\Users\User Name\My Documents\DVDFab\StreamFab\log
                          Please use attachment button and attach your most recent, Internal log and post right here.
                          If it's the burning issue, please also attach burn log.

                          Thanks!

                          Comment


                            #14
                            Originally posted by Wilson.Wang View Post
                            I will ask the dev to update ffmpeg and MKVToolNix to the latest version, may can be released at next week.

                            Wilson
                            Hello,

                            mp4box should be upgraded too... With the current one I'm getting different output than it should be...

                            e.g.: should be (downloaded with non-public scripts):
                            Bits/(Pixel*Frame) : 0.100
                            Stream size : 3.16 GiB (78%)

                            and I've got:
                            Bits/(Pixel*Frame) : 0.095
                            Stream size : 3.07 GiB (68%)

                            After manual update of mp4box are the outputs same...

                            Comment


                              #15
                              Originally posted by Wilson.Wang View Post
                              I will ask the dev to update ffmpeg and MKVToolNix to the latest version, may can be released at next week.
                              Wonderful! After 3 years of my manually updating files every week, I may not have to do it anymore if the dev can get in the habit of doing it. Much appreciated.

                              Also, we need an updated YoutubeToMP3Process.exe every week using the latest YT-DLP nightly source (preferred) or the most recently released stable.
                              Others that need updating are MediaInfo, Shaka-packager, Aria2c, and Atomic Parsley. And while you're at it, update CEF (Chromium) every time a new version comes out.

                              As for mp4box, I lost interest in it after it was found to be causing 702 errors. Perhaps take a look again at Bento4? SF used to use it. I'm not a developer, so, I'm not aware of the advantages of either program compared to the other.

                              Comment

                              Working...