Dolby Vision now possible through MP4 Mux.

[deadchip12]

Could someone pls summarize what has just been discussed in the last couple of pages? Is there a new method of muxing dolby vision? What are the advantages over the original method in the 1st page? Thanks.

[mrhollywood]

At this point, what is the best way to prepare DV movie for LG B8?

What I currently try to do:

• Rip 4K Blu-ray Disc as a file folder

• Open biggest .m2ts file from STREAM folder with usual latest tsMuxer, extract two .hevc files from it — one at ~60 gig, other is at ~6 gig

• Use Dolby's mp4muxer to create profile 7 .mp4 file

And the resulting file just doesn't play, Plex just freezes and doesn't launch the playback. What am I doing wrong? Should I use try to use modified txMuxer that appeared earlier on this thread, or switch to ffmpeg tool? Should I try new --profile 7.06? Or it's not the right profile for Plex on LG webOS?

Any advice would be appreciated, thanks.

What are you using for an audio track? profile 7 works just fine for me on the C9

[JonathanX64]

At this point, what is the best way to prepare DV movie for LG B8?

What I currently try to do:

• Rip 4K Blu-ray Disc as a file folder

• Open biggest .m2ts file from STREAM folder with usual latest tsMuxer, extract two .hevc files from it — one at ~60 gig, other is at ~6 gig

• Use Dolby's mp4muxer to create profile 7 .mp4 file

And the resulting file just doesn't play, Plex just freezes and doesn't launch the playback. What am I doing wrong? Should I use try to use modified txMuxer that appeared earlier on this thread, or switch to ffmpeg tool? Should I try new --profile 7.06? Or it's not the right profile for Plex on LG webOS?

Any advice would be appreciated, thanks.

What are you using for an audio track? profile 7 works just fine for me on the C9

Audio is .ac3, as I'm limited to ARC connection anyway.

I noticed that profile 7 usually works for everyone; can't figure out what exactly am I doing wrong

Going to try same process from scratch with ffmpeg and yusesope's tool to create an .mp4 file, maybe it will work better.

[mattmarsden]

I've just test Power Rangers single layer on my Shield versus the DL player on my LG C9 and you can see that the Dolby vision data is being ignored when looking at the end credits. On the DL version they are bright white but on the single layer they are grey just like the standard HDR version unfortunately.

[ATD555]

Could someone pls summarize what has just been discussed in the last couple of pages? Is there a new method of muxing dolby vision? What are the advantages over the original method in the 1st page? Thanks.

I will try my best.

The method at the beginning of this thread was either using DVDFab or two HEVCs from the video and remuxing it into an MP4 container using Dolby's remuxer. Users reported that DVDFab coloring was incorrect but there was really no choice if they wanted to play Dolby Vision (Single Layer) on devices other than Oppo 203 or Oppo 205 or some LG OLED TVs. It was then discovered that if you remuxed the .m2ts files from the UHD Disc Rips to .ts you can play this file (Dual Layer Dolby Vision) on the Sony x700 UBP Blu-ray Player with all audio profiles present on the disc. The user 'yusesope' then created a tool to create a proper single layer HEVC file from the two HEVCs in the original video file that retains all of the proper colors etc. into a single layer Dolby Vision. You can now use his tool + TSMuxer to make a .ts file that will play on other Dolby Vision capable devices as well as retaining all of the audio profiles from the original video file.

Hopefully this is a decent breakdown of what happened.

Edit: It will also save you money since you no longer need to use DVDFab which is a fairly expensive program.

[box4m]

When trying the bl_el_rpu_builder from yusesope (big thanks, awesome job), i get an outputfile that doesnt appear to be dual layer, its the same size as only the BL and when dropping it into txmuxer for example, its just 1 stream.

Do all counters reach 100%?
What movie are you trying to mux?
Try also with the new version of my tool.

Im trying with Atomic Blonde and im getting:

Code: Select all

Exception in thread Thread-1:LYSIS: 91.1%     BL_EL_RPU WRITING: 89.9%
Traceback (most recent call last):
  File "D:\bl_el_rpu_builder_v0.0.2\python-3.7.6.amd64\lib\threading.py", line 926, in _bootstrap_inner
    self.run()
  File "src\bl_el_rpu_builder.py", line 188, in run
    self.read()
  File "src\bl_el_rpu_builder.py", line 174, in read
    self.get_nal_info(mm,length,global_offset)
  File "src\bl_el_rpu_builder.py", line 149, in get_nal_info
    nal_type = self.get_nal_type(mmap_obj[(nal_offset + 3):(nal_offset + 5)])
  File "src\bl_el_rpu_builder.py", line 139, in get_nal_type
    nuh_layer_id = b_stream.read('uint:6')
  File "D:\bl_el_rpu_builder_v0.0.2\python-3.7.6.amd64\lib\site-packages\bitstring.py", line 3902, in read
    value, self._pos = self._readtoken(name, self._pos, length)
  File "D:\bl_el_rpu_builder_v0.0.2\python-3.7.6.amd64\lib\site-packages\bitstring.py", line 2016, in _readtoken
    "Tried to read {0} bits when only {1} available.".format(int(length), self.length - pos))
bitstring.ReadError: Reading off the end of the data. Tried to read 6 bits when only 1 available.
BL ANALYSIS: 89.7%     EL ANALYSIS: 91.1%     BL_EL_RPU WRITING: 89.9%
Exception in thread Thread-2:LYSIS: 91.3%     BL_EL_RPU WRITING: 90.1%
Traceback (most recent call last):
  File "D:\bl_el_rpu_builder_v0.0.2\python-3.7.6.amd64\lib\threading.py", line 926, in _bootstrap_inner
    self.run()
  File "src\bl_el_rpu_builder.py", line 188, in run
    self.read()
  File "src\bl_el_rpu_builder.py", line 174, in read
    self.get_nal_info(mm,length,global_offset)
  File "src\bl_el_rpu_builder.py", line 149, in get_nal_info
    nal_type = self.get_nal_type(mmap_obj[(nal_offset + 3):(nal_offset + 5)])
  File "src\bl_el_rpu_builder.py", line 139, in get_nal_type
    nuh_layer_id = b_stream.read('uint:6')
  File "D:\bl_el_rpu_builder_v0.0.2\python-3.7.6.amd64\lib\site-packages\bitstring.py", line 3902, in read
    value, self._pos = self._readtoken(name, self._pos, length)
  File "D:\bl_el_rpu_builder_v0.0.2\python-3.7.6.amd64\lib\site-packages\bitstring.py", line 2016, in _readtoken
    "Tried to read {0} bits when only {1} available.".format(int(length), self.length - pos))
bitstring.ReadError: Reading off the end of the data. Tried to read 6 bits when only 1 available.
BL ANALYSIS: 89.8%     EL ANALYSIS: 91.3%     BL_EL_RPU WRITING: 90.1%
BL ANALYSIS: 100.0%    EL ANALYSIS: 100.0%    BL_EL_RPU WRITING: 100.0%

ELAPSED TIME: 341.4 seconds
Press a button to exit

[Arbigator]

@yusesope

Thanks for guiding me. I did that and it's returning the following message "OSError: [WinError 123] The filename, directory name or syntax is incorrect"

It's putting 2 slashes in the directory where there should only be one.
eg. "c:\\path\\to\\the\\hevc\\files.hevc"

Seems like a strange problem, any idea how to fix that? Sorry, but I know nothing about this stuff otherwise I would try.

bl_el_rpu builder error.jpg (154.47 KiB) Viewed 31157 times

[yusesope]

..."OSError: [WinError 123] The filename, directory name or syntax is incorrect"....

the problem is represented by the spaces present in the file name and in the name of the folder hosting my program.

To work around the problem:

• download Notepad ++ (HERE)

• Unpack the archive

• start notepad ++. exe

• Open (in notepad ++) the "bl_el_rpu_builder.py" file inside the "src" folder of my program

• Scroll down to lines 295 and 296 and edit them (bottom image) by adding to both the string:

  Code: Select all

  .replace("\"","")

• Save your changes and close Notepad ++

• Start my program normally.

Code: Select all

Exception in thread Thread-1:LYSIS: 91.1%     BL_EL_RPU WRITING: 89.9%
Traceback (most recent call last):
  File "D:\bl_el_rpu_builder_v0.0.2\python-3.7.6.amd64\lib\threading.py", line 926, in _bootstrap_inner
    self.run()
  File "src\bl_el_rpu_builder.py", line 188, in run
    self.read()
  File "src\bl_el_rpu_builder.py", line 174, in read
    self.get_nal_info(mm,length,global_offset)
  File "src\bl_el_rpu_builder.py", line 149, in get_nal_info
    nal_type = self.get_nal_type(mmap_obj[(nal_offset + 3):(nal_offset + 5)])
  File "src\bl_el_rpu_builder.py", line 139, in get_nal_type
    nuh_layer_id = b_stream.read('uint:6')
  File "D:\bl_el_rpu_builder_v0.0.2\python-3.7.6.amd64\lib\site-packages\bitstring.py", line 3902, in read
    value, self._pos = self._readtoken(name, self._pos, length)
  File "D:\bl_el_rpu_builder_v0.0.2\python-3.7.6.amd64\lib\site-packages\bitstring.py", line 2016, in _readtoken
    "Tried to read {0} bits when only {1} available.".format(int(length), self.length - pos))
bitstring.ReadError: Reading off the end of the data. Tried to read 6 bits when only 1 available.
BL ANALYSIS: 89.7%     EL ANALYSIS: 91.1%     BL_EL_RPU WRITING: 89.9%
Exception in thread Thread-2:LYSIS: 91.3%     BL_EL_RPU WRITING: 90.1%
Traceback (most recent call last):
  File "D:\bl_el_rpu_builder_v0.0.2\python-3.7.6.amd64\lib\threading.py", line 926, in _bootstrap_inner
    self.run()
  File "src\bl_el_rpu_builder.py", line 188, in run
    self.read()
  File "src\bl_el_rpu_builder.py", line 174, in read
    self.get_nal_info(mm,length,global_offset)
  File "src\bl_el_rpu_builder.py", line 149, in get_nal_info
    nal_type = self.get_nal_type(mmap_obj[(nal_offset + 3):(nal_offset + 5)])
  File "src\bl_el_rpu_builder.py", line 139, in get_nal_type
    nuh_layer_id = b_stream.read('uint:6')
  File "D:\bl_el_rpu_builder_v0.0.2\python-3.7.6.amd64\lib\site-packages\bitstring.py", line 3902, in read
    value, self._pos = self._readtoken(name, self._pos, length)
  File "D:\bl_el_rpu_builder_v0.0.2\python-3.7.6.amd64\lib\site-packages\bitstring.py", line 2016, in _readtoken
    "Tried to read {0} bits when only {1} available.".format(int(length), self.length - pos))
bitstring.ReadError: Reading off the end of the data. Tried to read 6 bits when only 1 available.
BL ANALYSIS: 89.8%     EL ANALYSIS: 91.3%     BL_EL_RPU WRITING: 90.1%
BL ANALYSIS: 100.0%    EL ANALYSIS: 100.0%    BL_EL_RPU WRITING: 100.0%

ELAPSED TIME: 341.4 seconds
Press a button to exit

Another user had a similar problem: take a look HERE (end of the post)

[Arbigator]

That worked, thank you!

However, after muxing to .ts I'm still only able to get playback in HDR on the 2019 Shield with Plex and on my B9, the dolby vision flag never popped up.

[shawnc22]

That worked, thank you!

However, after muxing to .ts I'm still only able to get playback in HDR on the 2019 Shield with Plex and on my B9, the dolby vision flag never popped up.

I had this issue earlier, and it was because my Plex app wasn't up to date on the Shield. Even though I had auto updates on, I had to go into the play store and manually search for the Plex app to update. The updated app includes the new exoplayer that should now support DV videos.

[Arbigator]

That worked, thank you!

However, after muxing to .ts I'm still only able to get playback in HDR on the 2019 Shield with Plex and on my B9, the dolby vision flag never popped up.

I had this issue earlier, and it was because my Plex app wasn't up to date on the Shield. Even though I had auto updates on, I had to go into the play store and manually search for the Plex app to update. The updated app includes the new exoplayer that should now support DV videos.

There was an update, but unfortunately that didn't fix it... I'm going to try another movie and see what happens

[baker99]

I've just test Power Rangers single layer on my Shield versus the DL player on my LG C9 and you can see that the Dolby vision data is being ignored when looking at the end credits. On the DL version they are bright white but on the single layer they are grey just like the standard HDR version unfortunately.

That's concerning, was it a SL with EL+BL+RPU or just BL+RPU? Also mp4 or ts?

[smartrobot]

@yusesope I think I found my issue from a few posts ago
The tool always seemed to fail at 99% for both the BL and EL Layers

With the error "Reading off the end of the data. Tried to read 6 bits when only 1 available"
and fails at "BL ANALYSIS: 99.0% EL ANALYSIS: 98.8% BL_EL_RPU WRITING: 99.0%"

The issue was not the path like the other user were having.
The error was definitely occurring due to issues with my input files

When examining the BL and EL layers in a Hex editor the last line always was not complete.

BL Layer


EL Layer


When I fill the empty bytes with 00 on the last lines

BL Layer


EL Layer


Everything worked perfectly

[deadchip12]

Could someone pls summarize what has just been discussed in the last couple of pages? Is there a new method of muxing dolby vision? What are the advantages over the original method in the 1st page? Thanks.

I will try my best.

The method at the beginning of this thread was either using DVDFab or two HEVCs from the video and remuxing it into an MP4 container using Dolby's remuxer. Users reported that DVDFab coloring was incorrect but there was really no choice if they wanted to play Dolby Vision (Single Layer) on devices other than Oppo 203 or Oppo 205 or some LG OLED TVs. It was then discovered that if you remuxed the .m2ts files from the UHD Disc Rips to .ts you can play this file (Dual Layer Dolby Vision) on the Sony x700 UBP Blu-ray Player with all audio profiles present on the disc. The user 'yusesope' then created a tool to create a proper single layer HEVC file from the two HEVCs in the original video file that retains all of the proper colors etc. into a single layer Dolby Vision. You can now use his tool + TSMuxer to make a .ts file that will play on other Dolby Vision capable devices as well as retaining all of the audio profiles from the original video file.

Hopefully this is a decent breakdown of what happened.

Edit: It will also save you money since you no longer need to use DVDFab which is a fairly expensive program.

Thanks for the summary.

I guess for users like me who don’t need the original audio it’s not necessary to use the new tool then?

[jkatchy2]

this modified version of tsMuxer(thanks a5180007) now retains the EL when using yusesope tool.

Great news. To verify the correct implementation, however, make comparisons with the versions obtained through mp4muxer.

In the meantime, I release version 0.0.2 of my tool (refer to the original post HERE).
For more information take a look at the changelog.
I will not invest much energy in updating the tool (unless a serious error is discovered) because, if my idea proves valid, it will certainly be implemented in "more professional" tools (my code is open and the idea has been explained in detail).

When trying the bl_el_rpu_builder from yusesope (big thanks, awesome job), i get an outputfile that doesnt appear to be dual layer, its the same size as only the BL and when dropping it into txmuxer for example, its just 1 stream.

Do all counters reach 100%?
What movie are you trying to mux?
Try also with the new version of my tool.

I am trying to mux Braveheart ( which has FEL layer ) using your tool but the process stopped and exists at
BL ANALYSYS: 100.0% EL ANALYSYS 0.0% BL_EL_RPU WRITING 89.8%
used the latest tsMuxer build to extract the BL.hevc and EL.hevc from the remux mkv file . Trying to play DV in my B9 through USB. Am i doing anything wrong here ?