Page 199 of 253

Re: Dolby Vision now possible through MP4 Mux.

Posted: Wed Sep 16, 2020 6:37 pm
by kws53
Second .ts question - is there a "forced" flag available for SRT subtitles? I am in the process of converting my DV ISO's to .ts format (Yusesope tool+0406fix) for play through my Nvidia Pro Shield 2019 (from PLEX Server on Desktop), Denon AVR and OLED77CX. A number of them (MI 4 for example) have some English forced subtitles.

Re: Dolby Vision now possible through MP4 Mux.

Posted: Wed Sep 16, 2020 6:56 pm
by pitrako
I realised that If I turn off the TV the colors turns wrong again and If I want to watch the movie right I have to play first the Joker for example (MEL movie) and then switch to 1917 (FEL movie), all this in the internal native player, anyone knows what's might happening? Maybe the TV needs an update to fix this? Or the TV is defective?

Re: Dolby Vision now possible through MP4 Mux.

Posted: Wed Sep 16, 2020 9:50 pm
by MastaG
There's 04.06, 05.06 and 08.06 fixed versions of TSMuxer.

Could somebody please invest some time in explaining what they actually fix (and for which device(s)) ?
And perhaps show what's changed in the source code so I can decide if I require this fix and build it myself based on the latest version of TSMuxer (which carries many improvements and corrections btw).

Re: Dolby Vision now possible through MP4 Mux.

Posted: Wed Sep 16, 2020 10:06 pm
by shawnc22
MastaG wrote:
Wed Sep 16, 2020 9:50 pm
There's 04.06, 05.06 and 08.06 fixed versions of TSMuxer.

Could somebody please invest some time in explaining what they actually fix (and for which device(s)) ?
And perhaps show what's changed in the source code so I can decide if I require this fix and build it myself based on the latest version of TSMuxer (which carries many improvements and corrections btw).
They're not really fixing anything. The 04.06 version is an old version (circa ~March/April) that assigned BL+EL+RPU streams as profile 4. The current version nightly assigns them as profile 6. The 05.06 version is I think a user modified version that forcibly assigns a BL+RPU stream as profile 5 instead of 8 for playback on AppleTVs. I don't know what the 08.06 version is, but if it's forcibly assigning streams as profile 8, then I wouldn't go near it. The current nightly correctly labels BL+RPU streams as profile 8 and that's about the only thing that should be labeled as profile 8.

Re: Dolby Vision now possible through MP4 Mux.

Posted: Thu Sep 17, 2020 10:16 am
by DaMacFunkin
kws53 wrote:
Wed Sep 16, 2020 6:37 pm
Second .ts question - is there a "forced" flag available for SRT subtitles? I am in the process of converting my DV ISO's to .ts format (Yusesope tool+0406fix) for play through my Nvidia Pro Shield 2019 (from PLEX Server on Desktop), Denon AVR and OLED77CX. A number of them (MI 4 for example) have some English forced subtitles.
<movie name>.eng.forced.srt

Re: Dolby Vision now possible through MP4 Mux.

Posted: Thu Sep 17, 2020 2:59 pm
by yusesope
Good afternoon everyone.
The weekend is approaching so it seemed appropriate to me to release something for you to play with.

I start by thanking @jcdr428 (from TsMuxeR a.k.a a5180007) who gave me the possibility to use and modify his code for parsing the NALU RPUs.

As anticipated some posts ago, maybe I found the way to "convert" a FEL file to MEL.
This latest innovation together with the previous idea of ​​combining the two layers (BL and EL_RPU) in a single track, should guarantee the possibility of playing any FEL UHD-BD backup on Android devices equipped with a Dolby Vision decoder and capable of playing THIS file (+ my ExoPlayer) or THIS file.

Fingers crossed!

Forgive immediately any error in the code but this time I'm just out of my comfort zone: the pure python implementation of the new idea would have resulted in an extension of the times from 20 minutes (with the CPU always at 100%) up to 60-80 minutes. I had to rewrite the new idea in C++, cutting the time down to less than 60 seconds. Theoretically therefore, you shouldn't notice any difference in timing compared to previous versions of my tool.
I don't have a mac and I can't (want :roll: ) compile my code for macOS users. For now the latter cannot use this version of my tool (the problem is easily solved if some of you with a mac compile my code).

UPDATE 02/10/20
I added the possibility to "convert" a UHD-BD (MEL or FEL, it doesn't matter) into a profile 8.1 file (Single Track Single Layer)

UPDATE 16/10/20
Thanks to @quietvoid it is now possible to discard HDR10+ metadata in case your device (ex: FireStick 4k) does not like DoVi + HDR10+.
Those who want to skip HDR10+ metadata have to edit all ".bat" files (right click -> edit) by adding the -skip_hdr10plus switch

UPDATE 17/10/20
Added Experimental Muxer
More details HERE

HERE is the new version (FEL to MEL + UHD-BD to 8.1 + SKIP HDR10+ + Experimental Muxer) (I don't update my original post because I wait for your tests first).
These are the steps I followed to make the test videos that some of you tried a few days ago (once again HERE).
You need FFmpeg (the executable is in the bin folder), this version of TsMuxeR, this version of mp4muxer and MakeMKV (v1.15.3). Before testing an entire film I advise you to work with 120 second cuts.
  1. FEL TO MEL

    It goes without saying that these tests must be done on FEL titles. Do not use titles that are already MEL !!!!!

    • In the case of a Dual Track Dual Layer DV file (e.g. an m2ts file in the BDMV\STREAM folder)
      • Extract the base layer and the enhancement layer

        Code: Select all

        ffmpeg -i path\to\the\file.m2ts -ss 0 -t 120 -map 0:0 -c copy path\to\BL.hevc
        ffmpeg -i path\to\the\file.m2ts -ss 0 -t 120 -map 0:1 -c copy path\to\EL.hevc
      • Using my tool, double click on the MUX_AND_CONVERT_TO_MEL.bat file and follow the instructions on the screen.
        You will get a BL_EL_RPU.hevc file
      • Create a TS file using the BL_EL_RPU.hevc file and TsMuxeR

        EXTRA (MP4):
        In case TsMuxeR does not return a working file, create an mp4 file

        Code: Select all

        mp4muxer -i path\to\BL_EL_RPU.hevc --dv-profile 7 -o path\to\TEST_FILE.mp4
        EXTRA (MKV):
        Using my tool, double click on "DEMUX.bat" and drag and drop BL_EL_RPU.hevc
        You will get a BL.hevc file and a EL_RPU.hevc file
        Import the two BL.hevc (as first) and EL_RPU.hevc (as second) into TsMuxeR and create an ISO file.
        Open the ISO with MakeMKV
    • In the case of a Single Track Dual Layer DV file (e.g. mkv, ts, mp4 file previously modified using MakeMKV and/or TsMuxeR and/or my tool)
      • Extract the BL_EL_RPU.hevc file

        Code: Select all

        ffmpeg -i path\to\the\file.mp4 -ss 0 -t 120 -map 0:0 -c copy path\to\BL_EL_RPU.hevc
      • Using my tool, double click on the DEMUX_AND_CONVERT_TO_MEL.bat file and follow the instructions on the screen.
        You will get a BL.hevc file and a EL_RPU.hevc file
      • Using my tool, double click on the MUX.bat file (and NOT MUX_AND_CONVERT_TO_MEL.bat) and follow the instructions on the screen.
        You will get a BL_EL_RPU.hevc file
      • Create a TS file using the BL_EL_RPU.hevc file and TsMuxeR

        EXTRA (MP4):
        In case TsMuxeR does not return a working file, create an mp4 file

        Code: Select all

        mp4muxer -i path\to\BL_EL_RPU.hevc --dv-profile 7 -o path\to\TEST_FILE.mp4
        EXTRA (MKV):
        Right after using DEMUX_AND_CONVERT_TO_MEL.bat, import the two BL.hevc (as first) and EL_RPU.hevc (as second) into TsMuxeR and create an ISO file.
        Open the ISO with MakeMKV
  2. UHD-BD TO PROFILE 8.1

    You can use both UHD-BD MEL and FEL
    • In the case of a Dual Track Dual Layer DV file (e.g. an m2ts file in the BDMV\STREAM folder)
      • Extract the base layer and the enhancement layer

        Code: Select all

        ffmpeg -i path\to\the\file.m2ts -ss 0 -t 120 -map 0:0 -c copy path\to\BL.hevc
        ffmpeg -i path\to\the\file.m2ts -ss 0 -t 120 -map 0:1 -c copy path\to\EL.hevc
      • Using my tool, double click on the MUX_AND_CONVERT_TO_PROFILE_81.bat file and follow the instructions on the screen.
        You will get a BL_EL_RPU.hevc file.
        Actually, the file does not contain EL (it's just BL+RPU).
        BL_EL_RPU is just the filename !!!
        Let's put it this way, you are too lazy to use the command line and I am too lazy to add lines of code for the purpose of renaming a file :mrgreen: !
      • Create a TS file using the BL_EL_RPU.hevc file and TsMuxeR

        EXTRA (MP4):
        In case TsMuxeR does not return a working file, create an mp4 file

        Code: Select all

        mp4muxer -i path\to\BL_EL_RPU.hevc --dv-profile 8 --dv-bl-compatible-id 1 -o path\to\TEST_FILE.mp4
        EXTRA (MKV):
        Simply, create an ISO using BL_EL_RPU and TsMuxeR.
        Open the ISO with MakeMKV
    • In the case of a Single Track Dual Layer DV file (e.g. mkv, ts, mp4 file previously modified using MakeMKV and/or TsMuxeR and/or my tool)
      • Extract the BL_EL_RPU.hevc file

        Code: Select all

        ffmpeg -i path\to\the\file.mp4 -ss 0 -t 120 -map 0:0 -c copy path\to\BL_EL_RPU.hevc
      • Using my tool, double click on the DEMUX.bat file and follow the instructions on the screen.
        You will get a BL.hevc file and a EL_RPU.hevc file
      • Using my tool, double click on the MUX_AND_CONVERT_TO_PROFILE_81.bat file and follow the instructions on the screen.
        You will get a BL_EL_RPU.hevc file. Regarding the name BL_EL_RPU, the same considerations apply as before!
      • Create a TS file using the BL_EL_RPU.hevc file and TsMuxeR

        EXTRA (MP4):
        In case TsMuxeR does not return a working file, create an mp4 file

        Code: Select all

        mp4muxer -i path\to\BL_EL_RPU.hevc --dv-profile 8 --dv-bl-compatible-id 1 -o path\to\TEST_FILE.mp4
        EXTRA (MKV):
        Simply, create an ISO using BL_EL_RPU and TsMuxeR.
        Open the ISO with MakeMKV


To avoid problems, if you can, use my version of ExoPlayer (HERE).

Happy testing!

Re: Dolby Vision now possible through MP4 Mux.

Posted: Thu Sep 17, 2020 3:32 pm
by kws53
DaMacFunkin wrote:
Thu Sep 17, 2020 10:16 am
<movie name>.eng.forced.srt
Thank you for the response. So using tsmuxer to mux my MI4.HEVC, MI4.AC3, and MI4.eng.forced.srt together into MI4.ts will result in PLEX playing the subtitles automatically?

Re: Dolby Vision now possible through MP4 Mux.

Posted: Thu Sep 17, 2020 3:48 pm
by kws53
shawnc22 wrote:
Wed Sep 16, 2020 10:06 pm
They're not really fixing anything. The 04.06 version is an old version (circa ~March/April) that assigned BL+EL+RPU streams as profile 4. The current version nightly assigns them as profile 6. The 05.06 version is I think a user modified version that forcibly assigns a BL+RPU stream as profile 5 instead of 8 for playback on AppleTVs. I don't know what the 08.06 version is, but if it's forcibly assigning streams as profile 8, then I wouldn't go near it. The current nightly correctly labels BL+RPU streams as profile 8 and that's about the only thing that should be labeled as profile 8.
What would you recommend using for BL+EL+RPU.hevc made from Yusesope's tool with a Shield Pro 2019? I'm currently using 0406fix but currently have no way of verifying its efficacy as my 77CX is enroute. Are you suggesting using the 06.06fix (or as an alternative, the current nightly) for my purposes?

Re: Dolby Vision now possible through MP4 Mux.

Posted: Thu Sep 17, 2020 3:58 pm
by pitrako
yusesope wrote:
Thu Sep 17, 2020 2:59 pm
Good afternoon everyone.
The weekend is approaching so it seemed appropriate to me to release something for you to play with.

I start by thanking @jcdr428 (from TsMuxeR a.k.a a5180007) who gave me the possibility to use and modify his code for parsing the NALU RPUs.

As anticipated some posts ago, maybe I found the way to "convert" a FEL file to MEL.
This latest innovation together with the previous idea of ​​combining the two layers (BL and EL_RPU) in a single track, should guarantee the possibility of playing any FEL UHD-BD backup on Android devices equipped with a Dolby Vision decoder and capable of playing THIS file (+ my ExoPlayer) or THIS file.

Fingers crossed!

Forgive immediately any error in the code but this time I'm just out of my comfort zone: the pure python implementation of the new idea would have resulted in an extension of the times from 20 minutes (with the CPU always at 100%) up to 60-80 minutes. I had to rewrite the new idea in C++, cutting the time down to less than 60 seconds. Theoretically therefore, you shouldn't notice any difference in timing compared to previous versions of my tool.
I don't have a mac and I can't (want :roll: ) compile my code for macOS users. For now the latter cannot use this version of my tool (the problem is easily solved if some of you with a mac compile my code).


HERE is the new version (I don't update my original post because I wait for your tests first) and these are the steps I followed to make the test videos that some of you tried a few days ago (once again HERE).
You need FFmpeg (the executable is in the bin folder) and this version of mp4muxer. Before testing an entire film I advise you to work with 120 second cuts.

It goes without saying that these tests must be done on FEL titles. Do not use titles that are already MEL !!!!!


In the case of a Dual Track Dual Layer DV file (e.g. an m2ts file in the BDMV\STREAM folder)
  • Extract the base layer and the enhancement layer

    Code: Select all

    ffmpeg -i path\to\the\file.m2ts -ss 0 -t 120 -map 0:0 -c copy path\to\BL.hevc
    ffmpeg -i path\to\the\file.m2ts -ss 0 -t 120 -map 0:1 -c copy path\to\EL.hevc
  • Using my tool, double click on the MUX_AND_CONVERT_TO_MEL.bat file and follow the instructions on the screen.
    You will get a BL_EL_RPU.hevc file
  • Create an mp4 file

    Code: Select all

    mp4muxer -i path\to\BL_EL_RPU.hevc --dv-profile 7 -o path\to\TEST_FILE.mp4

In the case of a Single Track Dual Layer DV file (e.g. mkv, ts, mp4 file previously modified using MakeMKV and/or TsMuxeR and/or my tool)
  • Extract the BL_EL_RPU.hevc file

    Code: Select all

    ffmpeg -i path\to\the\file.mp4 -ss 0 -t 120 -map 0:0 -c copy path\to\BL_EL_RPU.hevc
  • Using my tool, double click on the DEMUX_AND_CONVERT_TO_MEL.bat file and follow the instructions on the screen.
    You will get a BL.hevc file and a EL_RPU.hevc file
  • Using my tool, double click on the MUX.bat file (and NOT MUX_AND_CONVERT_TO_MEL.bat) and follow the instructions on the screen.
    You will get a BL_EL_RPU.hevc file
  • Create an mp4 file

    Code: Select all

    mp4muxer -i path\to\BL_EL_RPU.hevc --dv-profile 7 -o path\to\TEST_FILE.mp4


To avoid problems, if you can, use my version of ExoPlayer (HERE).

I purposely didn't use TsMuxeR because the final output wouldn't have profile 7.
If my gimmick works maybe @jcdr428 can modify TsMuxeR once again to make files with profile 7 thus eliminating all those versions (04.fix, 06.fix, 08.fix) that are circulating and that only confuse ideas.

Happy testing!
Exception in thread Thread-5:SIS: 0.0% BL_EL_RPU WRITING: 0.0% (BL AUs: 244 EL AUs: 571)
Traceback (most recent call last):
File "D:\Dolby Vision\v0.0.4_BETA\python-3.7.6.amd64\lib\threading.py", line 926, in _bootstrap_inner
self.run()
File "src\app.py", line 395, in run
self.cpp_lib = self.init_cpp_lib()
File "src\app.py", line 342, in init_cpp_lib
cpp_lib = cdll.LoadLibrary(cpp_lib_path)
File "D:\Dolby Vision\v0.0.4_BETA\python-3.7.6.amd64\lib\ctypes\__init__.py", line 442, in LoadLibrary
return self._dlltype(name)
File "D:\Dolby Vision\v0.0.4_BETA\python-3.7.6.amd64\lib\ctypes\__init__.py", line 364, in __init__
self._handle = _dlopen(self._name, mode)
OSError: [WinError 126] Cannot find the specified module

BL_ANALYSIS: 0.0% EL_ANALYSIS: 0.0% BL_EL_RPU WRITING: 0.0% (BL AUs: 509 EL AUs: 571)

Error for me and stuck.

Re: Dolby Vision now possible through MP4 Mux.

Posted: Thu Sep 17, 2020 4:19 pm
by quietvoid
yusesope wrote:
Thu Sep 17, 2020 2:59 pm
It goes without saying that these tests must be done on FEL titles. Do not use titles that are already MEL !!!!!
Just tried this and it works on the FireTV Stick 4K.

On archlinux, my steps (starting from a mode1 muxed BL_EL_RPU.hevc file):
Mux to mkv, split to make smaller.
Demux to hevc.
python app.py -lbf 50 -demux -fel_to_mel -if video.hevc
python app.py -lbf 50 -mux -bl BL.hevc -el EL_RPU.hevc
mp4muxer_64bits -i BL_EL_RPU.hevc --dv-profile 7 -o test.mp4

And it plays in Dolby Vision with ExoPlayer. :)
PS: there should probably be an indication or something to stop instead of just "Wait...", the default -lbf value just hanged because the file sample is small.

Re: Dolby Vision now possible through MP4 Mux.

Posted: Thu Sep 17, 2020 5:12 pm
by jcdr428
yusesope wrote:
Thu Sep 17, 2020 2:59 pm
I purposely didn't use TsMuxeR because the final output wouldn't have profile 7.
If my gimmick works maybe @jcdr428 can modify TsMuxeR once again to make files with profile 7 thus eliminating all those versions (04.fix, 06.fix, 08.fix) that are circulating and that only confuse ideas.
Hi @yusesope, so you need tsMuxer to register profile 6 as profile 4 to be read by ExoPlayer, is this correct ?
I am still reluctant to push this hack to tsMuxer as profile 4 BL should be SDR, not HDR10. Then AppleTV users will still need to use 05.06 fix to register profile 8 as profile 5.
Why not push a commit to ExoPlayer to read profile 6 (DvheDth) ?

Re: Dolby Vision now possible through MP4 Mux.

Posted: Thu Sep 17, 2020 5:17 pm
by pitrako
I need some .dll or something? MUX.bat works but MUX_AND_CONVERT_TO_MEL.bat doesn't work, It shows the error I posted above.

Re: Dolby Vision now possible through MP4 Mux.

Posted: Thu Sep 17, 2020 5:31 pm
by PapitaHD
Exception in thread Thread-5:SIS: 0.0% BL_EL_RPU WRITING: 0.0% (BL AUs: 244 EL AUs: 571)
Traceback (most recent call last):
File "D:\Dolby Vision\v0.0.4_BETA\python-3.7.6.amd64\lib\threading.py", line 926, in _bootstrap_inner
self.run()
File "src\app.py", line 395, in run
self.cpp_lib = self.init_cpp_lib()
File "src\app.py", line 342, in init_cpp_lib
cpp_lib = cdll.LoadLibrary(cpp_lib_path)
File "D:\Dolby Vision\v0.0.4_BETA\python-3.7.6.amd64\lib\ctypes\__init__.py", line 442, in LoadLibrary
return self._dlltype(name)
File "D:\Dolby Vision\v0.0.4_BETA\python-3.7.6.amd64\lib\ctypes\__init__.py", line 364, in __init__
self._handle = _dlopen(self._name, mode)
OSError: [WinError 126] Cannot find the specified module

BL_ANALYSIS: 0.0% EL_ANALYSIS: 0.0% BL_EL_RPU WRITING: 0.0% (BL AUs: 509 EL AUs: 571)

Error for me and stuck.
Same error for me. I'm trying to convert/remux Gemini Man from a full UHD BluRay backup. Officially it's a FEL title, although it has about the lowest bitrare a FEL can have.
Later I'll try Saving Private Ryan.

Re: Dolby Vision now possible through MP4 Mux.

Posted: Thu Sep 17, 2020 5:39 pm
by shawnc22
kws53 wrote:
Thu Sep 17, 2020 3:48 pm
shawnc22 wrote:
Wed Sep 16, 2020 10:06 pm
They're not really fixing anything. The 04.06 version is an old version (circa ~March/April) that assigned BL+EL+RPU streams as profile 4. The current version nightly assigns them as profile 6. The 05.06 version is I think a user modified version that forcibly assigns a BL+RPU stream as profile 5 instead of 8 for playback on AppleTVs. I don't know what the 08.06 version is, but if it's forcibly assigning streams as profile 8, then I wouldn't go near it. The current nightly correctly labels BL+RPU streams as profile 8 and that's about the only thing that should be labeled as profile 8.
What would you recommend using for BL+EL+RPU.hevc made from Yusesope's tool with a Shield Pro 2019? I'm currently using 0406fix but currently have no way of verifying its efficacy as my 77CX is enroute. Are you suggesting using the 06.06fix (or as an alternative, the current nightly) for my purposes?
You're good, but either should work without issue, though.
jcdr428 wrote:
Thu Sep 17, 2020 5:12 pm
yusesope wrote:
Thu Sep 17, 2020 2:59 pm
I purposely didn't use TsMuxeR because the final output wouldn't have profile 7.
If my gimmick works maybe @jcdr428 can modify TsMuxeR once again to make files with profile 7 thus eliminating all those versions (04.fix, 06.fix, 08.fix) that are circulating and that only confuse ideas.
Hi @yusesope, so you need tsMuxer to register profile 6 as profile 4 to be read by ExoPlayer, is this correct ?
I am still reluctant to push this hack to tsMuxer as profile 4 BL should be SDR, not HDR10. Then AppleTV users will still need to use 05.06 fix to register profile 8 as profile 5.
Why not push a commit to ExoPlayer to read profile 6 (DvheDth) ?
Please correct me if I'm wrong, but I think yusecope is suggesting that what tsmuxer is currently registering as profile 6 should go back to being registered as profile 7. It's currently what MakeMKV is doing with the same BL+EL+EPU tracks and it seems to have had no ill effects on playback capabilities (on the Shield w/Exoplayer at least). Mike has mentioned in that past the dual track vs single track transport methods of BL,EL+RPU should have no bearing on profile choice, so I think with the deprecation of profile 6, 7 should technically be the correct assignment for these files.

Re: Dolby Vision now possible through MP4 Mux.

Posted: Thu Sep 17, 2020 5:54 pm
by yusesope
quietvoid wrote:
Thu Sep 17, 2020 4:19 pm
Just tried this and it works on the FireTV Stick 4K...On archlinux...And it plays in Dolby Vision with ExoPlayer. :)
It always warms the heart to see "archlinux" written somewhere :D . Thanks for your feedback.
pitrako wrote:
Thu Sep 17, 2020 5:17 pm
I need some .dll or something? MUX.bat works but MUX_AND_CONVERT_TO_MEL.bat doesn't work, It shows the error I posted above.
PapitaHD wrote:
Thu Sep 17, 2020 5:31 pm
Same error for me. I'm trying to convert/remux Gemini Man from a full UHD BluRay backup. Officially it's a FEL title, although it has about the lowest bitrare a FEL can have.
Later I'll try Saving Private Ryan.
Yes you are right. Your Windows needs THESE libraries (unpack the archive and place the two dll files where there are the files MUX.bat, DEMUX.bat, etc ...). It's not an elegant solution but it should at least work for these days of testing.
Let me know!
jcdr428 wrote:
Thu Sep 17, 2020 5:12 pm
Hi @yusesope, so you need tsMuxer to register profile 6 as profile 4 to be read by ExoPlayer, is this correct?
The files that are created by this latest version have as VUI:
0,9,16,9,2 for the Base layer
0,9,16,9,2 for the Enhancement layer.
The correct profile should therefore be 7.
Now I don't remember well but it seems to me that TsMuxeR currently generates files with profile 6 (but, I repeat myself, I could be wrong). If my tool proves to work, in my opinion, we should try to mark the ts files with profile 7 (and not 6).
shawnc22 wrote:
Thu Sep 17, 2020 5:39 pm
I think yusecope is suggesting that what tsmuxer is currently registering as profile 6 should go back to being registered as profile 7
Yep, Exactly!