Dolby Vision now possible through MP4 Mux.

[RESET_9999]

I would love to do it in TS, but srt external subtitles are only suitable when it comes to one track, and if there are many of them? Therefore, this solution is not suitable.

No you can add as many as you want with PLEX

[TheEqualizer]

RESET_9999, unfortunately, this is also not an option, the task is to have everything already inside the container, since this is not for personal use, but for public use, for myself I can do at least in mkv dv and watch from the media player)

[dapope]

Just for fun, I thought I would try generating DV metadata for the Hitchcock film "Rear Window" using the new 3-1 frame by frame option. This movie was only released in HDR, with no DV. The film is in 1:66:1 (5:3) aspect ratio, so am I correct in entering the L5 offsets as:
Left L5 offset 120, Right L5 offset 120, Top L5 offset 0, Bottom L5 offset 0
?
Thank you so much!

[Mattl0]

I am right that dv p7 mel, converted to p8.1
, will have a better output on a c1 internal player versus original p7 mel on sony x800m2? Because of l1 and l2 metadata?

[RESET_9999]

Just for fun, I thought I would try generating DV metadata for the Hitchcock film "Rear Window" using the new 3-1 frame by frame option. This movie was only released in HDR, with no DV. The film is in 1:66:1 (5:3) aspect ratio, so am I correct in entering the L5 offsets as:
Left L5 offset 120, Right L5 offset 120, Top L5 offset 0, Bottom L5 offset 0
?
Thank you so much!

you have to measure the black bars manually in Avspmod. I didn't generate the RPU I have but it's set to:

Code: Select all

          "Level5": {
            "active_area_left_offset": 124,
            "active_area_right_offset": 125,
            "active_area_top_offset": 0,
            "active_area_bottom_offset": 0
          }

I am right that dv p7 mel, converted to p8.1
, will have a better output on a c1 internal player versus original p7 mel on sony x800m2? Because of l1 and l2 metadata?

The metadata response will be slightly different but I really don't know which one is more accurate.
If you have a good audio system, I would not sacrifice lossless audio.

[Mattl0]

Thank you !!

[dapope]

Just for fun, I thought I would try generating DV metadata for the Hitchcock film "Rear Window" using the new 3-1 frame by frame option. This movie was only released in HDR, with no DV. The film is in 1:66:1 (5:3) aspect ratio, so am I correct in entering the L5 offsets as:
Left L5 offset 120, Right L5 offset 120, Top L5 offset 0, Bottom L5 offset 0
?
Thank you so much!

you have to measure the black bars manually in Avspmod. I didn't generate the RPU I have but it's set to:

Code: Select all

          "Level5": {
            "active_area_left_offset": 124,
            "active_area_right_offset": 125,
            "active_area_top_offset": 0,
            "active_area_bottom_offset": 0
          }

Thank you. I got about the same result when I measured it except I had left as 125 and right as 124.

Unfortunately the file only played fine up until about the 1h20m mark. The audio kept playing but the picture froze. This is on the LG CX internal player after muxing to a .ts file. Seems like it has trouble seeking through the file, like it thinks the video is shorter than it actually is. Of course on VLC it plays fine.

[DiscoD]

@RESET_9999 On the Dolby vision excel file, you posted the L5 IMAX edits for Guardians of the Galaxy. How and where to use it? Thanks in advance.

you edit all the frames to 0,0,276,276 with a json file and then you edit all the Imax frames to 0,0,68,68 with another json file.

dovi_tool.exe editor -i D:\input.bin -j D:\276.edits.json --rpu-out D:\276.edits.bin
dovi_tool.exe editor -i D:\276.edits.bin -j D:\68.edits.json --rpu-out D:\final.RPU.bin

276/276 json

Code: Select all

{
    "mode": 0,
    "active_area": {
        "presets": [
            {
                "id": 1,
                "left": 0,
                "right": 0,
                "top": 276,
                "bottom": 276
            }
        ],
        "edits": {
            "all": 1
        }
    }
}

68/68 json

Code: Select all

{
    "mode": 0,
    "active_area": {
        "presets": [
            {
                "id": 1,
                "left": 0,
                "right": 0,
                "top": 68,
                "bottom": 68
            }
        ],
        "edits": {
            "2313-8290": 1,
            "12867-20599": 1,
            "29662-30346": 1,
            "44226-50210": 1,
            "62482-71703": 1,
            "90855-94414": 1,
            "114450-114880": 1,
            "120568-130909": 1,
            "150232-163186": 1,
            "180560-180982": 1,
            "184049-187882": 1,
            "197234-205633": 1
        }
    }
}

So if im encoding this and cropping away the 68px for the imax scenes should my RPU be 0,0,0,0 for the imax scenes and 208 for the normal scenes to make up for the difference?

[bbeny123]

I've improved mp4muxer (official dlb_mp4base) a bit.

The main improvement is a significant boost in the performance of muxing hevc files.
In the official version, after reading the input files, the mp4muxer looks like it goes idle (low CPU usage, minimal disk usage).
During the "inactivity" the program does n * n loops (where n = number of video frames) - so the longer (not bigger) the input video, the longer the idleness period. After my fixes, such a loop is made only once (by using a map-like data structure).
This fix significantly reduces the time needed to mux hevc files, the "idle" time has been reduced to almost 0. Muxing performance now depends almost only on the speed of the used disk.

Other changes:

• Fixed codec id for EL layer (codec id for the EL layer is again 'dvhe' and not 'hev1') - in this aspect, the behavior is the same as in the old 'mp4muxer_64bits' version (1.0.0)
• Support for .eac3 audio input
• Muxing progress logging

Source code, binaries, full changelog: https://github.com/bbeny123/mp4muxer

[RESET_9999]

So if im encoding this and cropping away the 68px for the imax scenes should my RPU be 0,0,0,0 for the imax scenes and 208 for the normal scenes to make up for the difference?

I don't know I never tried with cropped content but 208 for the non-imax shots sounds right. Test it on an LG TV internal player.

[dapope]

Just for fun, I thought I would try generating DV metadata for the Hitchcock film "Rear Window" using the new 3-1 frame by frame option. This movie was only released in HDR, with no DV. The film is in 1:66:1 (5:3) aspect ratio, so am I correct in entering the L5 offsets as:
Left L5 offset 120, Right L5 offset 120, Top L5 offset 0, Bottom L5 offset 0
?
Thank you so much!

you have to measure the black bars manually in Avspmod. I didn't generate the RPU I have but it's set to:

Code: Select all

          "Level5": {
            "active_area_left_offset": 124,
            "active_area_right_offset": 125,
            "active_area_top_offset": 0,
            "active_area_bottom_offset": 0
          }

Thank you. I got about the same result when I measured it except I had left as 125 and right as 124.

Unfortunately the file only played fine up until about the 1h20m mark. The audio kept playing but the picture froze. This is on the LG CX internal player after muxing to a .ts file. Seems like it has trouble seeking through the file, like it thinks the video is shorter than it actually is. Of course on VLC it plays fine.

@RESET_9999 Do you have any idea why this might be the case? Any help would be appreciated.
Also I would check if there isn't a bug in your program switching the left and right offset. I'm sure I entered the left offset as 125 and the right offset as 124, but now the metadata is saying it's reversed (like the one you posted).

[legosoff]

Hi, RESET_9999! mp4box subtitles iPhone и iPad it will work tx3g and sbtl. @jamiew just saved my life!
test.srt:lang=eng:layout=0x60x0x-1:group=2:hdlr=sbtl:tx3g

[RESET_9999]

@RESET_9999 Do you have any idea why this might be the case? Any help would be appreciated.

I don't know...
Network issue? HDD issue? Maybe the player choked at some point because of frame-by-frame?

Also I would check if there isn't a bug in your program switching the left and right offset. I'm sure I entered the left offset as 125 and the right offset as 124, but now the metadata is saying it's reversed (like the one you posted).

Because when you set uneven L5 offsets in resolve or cm_analyze, the dovi_tool(XML to rpu) has no way to calculate exactly which position the offsets go because the XML file works with aspect ratio values only.
This is exactly the reason why the script (1-1) has an option to edit L5 with XML inputs.

[RESET_9999]

I've improved mp4muxer (official dlb_mp4base) a bit.

The main improvement is a significant boost in the performance of muxing hevc files.
In the official version, after reading the input files, the mp4muxer looks like it goes idle (low CPU usage, minimal disk usage).
During the "inactivity" the program does n * n loops (where n = number of video frames) - so the longer (not bigger) the input video, the longer the idleness period. After my fixes, such a loop is made only once (by using a map-like data structure).
This fix significantly reduces the time needed to mux hevc files, the "idle" time has been reduced to almost 0. Muxing performance now depends almost only on the speed of the used disk.

Other changes:

• Fixed codec id for EL layer (codec id for the EL layer is again 'dvhe' and not 'hev1') - in this aspect, the behavior is the same as in the old 'mp4muxer_64bits' version (1.0.0)
• Support for .eac3 audio input
• Muxing progress logging

Source code, binaries, full changelog: https://github.com/bbeny123/mp4muxer

thanks, I'll try it.
Have you tested if the file works on older LG TVs ? (2018 or older)

[FonduemangVI]

@RESET_9999 Hey would you be able to explain what the FraMeSToR illegal L5 change at frame 203356 for GotG Vol 3 is?/why it's illegal?