Closed MastaG closed 2 years ago
Here's the first 200MB from the .TS file created using the hevc file from yusesope's tool: https://mega.nz/file/X09DXKYS#MSncO4lcoGK8Rj2jC7VS7CrpsyEqgDnGlIbTKto-CQg
Here's the first 200MV from the .TS file created by remuxing the MKV created by makemkv (from the same disc): https://mega.nz/file/mkkBWQBQ#tlh2drUG55mhotsVdL5QwzE_yN4CsigoCNR0MrwZUj8
Like I said before, both contain the dual layer DV as a single track, only the first one was extracted and merged using yusesope's python tool and the second one was remuxed from makemkv. I'd like to know if it's possible to see why the second one doesn't work, because makemkv can merge both layers much faster.
This is not an issue related to tsMuxer. MakeMKV simply forgets to add the Access Unit Delimiters -which yusesope tool does correctly.
Ah thanks for explaining bro. Should I report this to the makemkv devs then?
Yes, Mike should be able to fix this.
Hi,
I can use yusesope's tool, to merge both BL+EL layers from the original bluray disc into a single hevc file. When I open this hevc file and mux this into a .TS file, it will trigger DV on my LG TV.
This is a bit cumbersome as the python tool is a bit slow and it requires extra space to first extract both layers form the disc, then merge them togerther into a single file.
I can also use makemkv to create a MKV file straight from the same disc. It will also combine both DV layers into a single track/pid.
However when I remux the MKV produced by makemkv into a .TS file, this will not trigger DV on my TV. I've tried a few discs, but it just doesn't work.
If I compare the mediainfo from the .TS file created using the .hevc file from yusesope's tool and the .TS file created from the MKV (from makemkv) the only difference I can see is that the latter has a language tag inside the video pid. This is the .TS file created from the MKV file:
Any ideas?