tsMuxer Open Source

[justdan96]

So I've managed to contact the original author of tsMuxer and he has agreed to turn tsMuxer into an open source project.

You can find the project's home at GitHub here:
https://github.com/justdan96/tsMuxer

You can download the latest nightly build from here:
https://github.com/justdan96/tsMuxer/releases

Now the latest nightly build: https://github.com/justdan96/tsMuxer/releases
Because: https://forum.doom9.org/showthread.php?p=1935864#post1935864

Please post any bugs or enhancement requests either in this thread or as issues on the GitHub repo.

[videoh]

Just release the code and stop trying to take private control over it!

[justdan96]

I'm not exercising control over it. In its current state the code does not compile and is effectively unusable. Releasing it in that state would not really do anyone any good.

[Groucho2004]

I'm not exercising control over it. In its current state the code does not compile and is effectively unusable. Releasing it in that state would not really do anyone any good.As I understand from your first post, it doesn't compile on/for Linux. No mention of Windows so I presume it can be built for Windows.

So, why are you not releasing the code?

[justdan96]

It doesn't compile on any platform, I'd like to get it into a working state before it goes up publicly and the author expressed a wish for it to be released responsibly so I am trying to follow through on that.

[filler56789]

I'm not exercising control over it. In its current state the code does not compile and is effectively unusable.
Releasing it in that state would not really do anyone any good.

You are mistaken. Just release the current source-code and add an appropriate big-fat disclaimer or something.
And for the time being at least, don't use GitHub, use a file sharing site such as Mediafire.
In this way ordinary users won't even try to compile it and the experienced programmers may try to make it work.

[videoh]

Maybe others can straighten things out faster than you. ;)

[justdan96]

Releasing on GitHub was what the author requested. From the sounds of things people want the code released regardless of whether it is in a working state or not so I'll give the author a bit more time to send over the missing header files, but if I don't get a response I'll release with a disclaimer that the code doesn't work (in its current state).

I appreciate the feedback, since the program will be soon owned by the community it's good to gauge how people want it to be handled.

[videoh]

Missing files is quite a bit different from "it doesn't compile"!

[StainlessS]

Maybe you could at least name the missing headers. [maybe they are standard ones, EDIT: From DirectX SDK or something]

[justdan96]

The program used non-standard libraries for types, files, queues, threads and more - and these weren't included with the code. I made a bit more progress with switching them for the standard libraries last night and added a to do list to the readme.

I'll give the author a bit more time to respond to my message and otherwise will release it on the weekend.

[filler56789]

The program used non-standard libraries for types, files, queues, threads and more - and these weren't included with the code. I made a bit more progress with switching them for the standard libraries last night and added a to do list to the readme.

That's good. :thanks:

I'll give the author a bit more time to respond to my message and otherwise will release it on the weekend.

Please define weekend.
Or which weekend...

[justdan96]

Sorry I meant to release it last Sunday but things got on top of me. The author shared the missing headers - but it still doesn't compile. I'll revert the code to the original sources and just add the todo items to the readme for switching to standard libraries. I'll also add an issue to get past the specific compile error I am having. Once that's done I'll make the repo public. I hope I can get that done this week.

[videoh]

Thank you, justdan96. Your efforts are greatly appreciated!

[justdan96]

I managed to make a lot of progress tonight - fixed the compiler error, figured out how to get the 32-bit libraries needed to compile on Ubuntu and finally got a working build of both tsMuxer and tsMuxerGUI!
I have now made the repository public so you can all try compiling for your platform or just hack away at the code: https://github.com/justdan96/tsMuxer
Thanks to everyone for being so patient, hopefully this will lead to a lot of healthy discussion and collaboration!

[filler56789]

I managed to make a lot of progress tonight - fixed the compiler error, figured out how to get the 32-bit libraries needed to compile on Ubuntu and finally got a working build of both tsMuxer and tsMuxerGUI!
I have now made the repository public so you can all try compiling for your platform or just hack away at the code: https://github.com/justdan96/tsMuxer
Thanks to everyone for being so patient, hopefully this will lead to a lot of healthy discussion and collaboration!

:thanks: — I starred the project.

[justdan96]

I have it compiling in Visual Studio 2017 - I'll update the repo soon.

[filler56789]

1)
I have it compiling in Visual Studio 2017 - I'll update the repo soon.
Nice! :)

2) Suggestion: create a TODO list :sly:
For example, TSmuxer doesn't support MPEG-4 ASP, even though MPEG-4 ASP is defined in the TS specification;
and it doesn't support Opus audio either :-/
Besides, it has a problem with some types of DTS Express: https://forum.doom9.org/showthread.php?p=1703668#post1703668

[justdan96]

Thanks for those, I'll create a section in the readme for that information.

[SeeMoreDigital]

1)

Nice! :)

2) Suggestion: create a TODO list :sly:
For example, TSmuxer doesn't support MPEG-4 ASP, even though MPEG-4 ASP is defined in the TS specification;
and it doesn't support Opus audio either :-/
Besides, it has a problem with some types of DTS Express: https://forum.doom9.org/showthread.php?p=1703668#post1703668
And... TSmuxer does not support HEVC of-course.

[filler56789]

And... TSmuxer does not support HEVC of-course.
What :confused:

Yes, it does! But not for Ultra HD Blu-ray authoring, for example.

https://github.com/justdan96/tsMuxer/blob/master/CHANGELOG.md#tsmuxer-255

[SeeMoreDigital]

What :confused:

Yes, it does! But not for Ultra HD Blu-ray authoring, for example.

https://github.com/justdan96/tsMuxer/blob/master/CHANGELOG.md#tsmuxer-255And there-in lies the problem :(

Plus the 4K UHD HEVC in .m2ts muxes that TSmuxer currently generates are a little unstable in some hardware playback devices...

[jdobbs]

What :confused:

Yes, it does! But not for Ultra HD Blu-ray authoring, for example.

https://github.com/justdan96/tsMuxer/blob/master/CHANGELOG.md#tsmuxer-255It will mux HEVC/UHD. But it has several muxing bugs when doing a HEVC/UHD stream. For example it flags them as 1080p and it misses frames, or more accurately it thinks some frames are a part of a previous frame and muxes them as a part of it. The result is a stream that gets progressively more out of sync (at least those that are encoded for blu-ray UHD by X265). It also uses the wrong stream type, needs to update the headers to version 3, and add UHD extension data to the clpi files and index.bdmv.

With that said... the last publicly released version was 2.6.12 -- so I'm not sure what has changed since then, there seems to have been three minor version updates since then.

I've been working on an algorithm that remuxes TSMUXER output to make it UHD compliant. I'm happy to see the release of the code. I'd rather help fix the original code than have to scan through a 50GB M2TS file fixing issues as I find them.

[justdan96]

Sorry I've been very busy recently but I'll be updating the documentation in the repo very soon. Jdobbs it sounds like you have a good idea of the issue so I'll be stealing your description to add to the todo list :)

[Selur]

Thanks for releasing the code!

[r0lZ]

As far as I know, there are at least 2 bugs related to the subtitles in the demux function:
Do NOT use v2.6.11 or v2.6.12 as they have a big bug with the time codes of the subtitle streams of some BDs. AFAIK, v2.6.10 has never been released publicly, so the last known good version is v2.6.9, for Windows and Linux. However, even v2.6.9 has some bugs, notably the association of the subtitles with the 3D-Plane numbers, often wrong. (But this bug affects only the info and the remux of the 3D BDs.)
As noted in the other thread, v2.6.11 and v2.6.12 produce often wrong timecodes when demuxing a 3D bluray. (I don't know if that bug affects also the 2D blurays.) Unfortunately, I don't remember what BD is a good example of the problem. V2.6.9 is the last version without that bug, so if you have the sources of that version, it should be easy to find the origin of the bug.

The other important bug with the subtitles is also related to the 3D BD. The MPLS file contains the extensions with the 3D-specific information, like what tsMuxeR calls the "3D-Planes", in fact the "Offset Sequences" necessary to display the subtitles at the correct depth on screen. There is usually one 3D-Plane per subtitle stream, although it's not mandatory as the same 3D-Plane can be used for several streams. The bug is that tsMuxeR assumes that the 3D-Planes are assigned to the subtitles streams in the order of their UID. It's not correct. The MPLS file describes precisely the subtitle streams, ans they do not have to be in the order of their UID, although it's often the case.

So, for example, if there are 4 subtitle streams in the BD, stored in the MPLS in the standard order, tsMuxeR will assign the 4 first 3D-Planes to that 4 streams, and it will probably be correct. But if the 4 streams are presented in the MPLS in another order, it will be wrong. And if the same 3D-Plane is assigned to several subtitle streams in the MPLS, it will assign it only once, and the last subtitle streams will not have any 3D-Plane at all. To summarize, tsMuxeR ignores the content of the MPLS when it assigns the 3D-Planes to the subtitle streams. That's an important bug, although the wrong information is only displayed, and never used during the demux operation. I don't know if tsMuxeR does the same error when it remuxes a 3D-BD, but I suppose so.

[staina]

As far as I know, there are at least 2 bugs related to the subtitles in the demux function:

As noted in the other thread, v2.6.11 and v2.6.12 produce often wrong timecodes when demuxing a 3D bluray. (I don't know if that bug affects also the 2D blurays.) Unfortunately, I don't remember what BD is a good example of the problem. V2.6.9 is the last version without that bug, so if you have the sources of that version, it should be easy to find the origin of the bug.

The other important bug with the subtitles is also related to the 3D BD. The MPLS file contains the extensions with the 3D-specific information, like what tsMuxeR calls the "3D-Planes", in fact the "Offset Sequences" necessary to display the subtitles at the correct depth on screen. There is usually one 3D-Plane per subtitle stream, although it's not mandatory as the same 3D-Plane can be used for several streams. The bug is that tsMuxeR assumes that the 3D-Planes are assigned to the subtitles streams in the order of their UID. It's not correct. The MPLS file describes precisely the subtitle streams, ans they do not have to be in the order of their UID, although it's often the case.

So, for example, if there are 4 subtitle streams in the BD, stored in the MPLS in the standard order, tsMuxeR will assign the 4 first 3D-Planes to that 4 streams, and it will probably be correct. But if the 4 streams are presented in the MPLS in another order, it will be wrong. And if the same 3D-Plane is assigned to several subtitle streams in the MPLS, it will assign it only once, and the last subtitle streams will not have any 3D-Plane at all. To summarize, tsMuxeR ignores the content of the MPLS when it assigns the 3D-Planes to the subtitle streams. That's an important bug, although the wrong information is only displayed, and never used during the demux operation. I don't know if tsMuxeR does the same error when it remuxes a 3D-BD, but I suppose so.

At Remux from 3D Bluray disk stays 3D-Planes at subtitles streams so as to original 3D Bluray.

[filler56789]

1) In the README of TSMuxer, instead of "To compile tsMuxer and tsMuxerGUI on Windows..." you should have written "To compile tsMuxer and tsMuxerGUI with Microsoft Visual Studio". Stop denying the existence of MSYS2 and MinGW-w64 :)

2) even though I don't like CMake, perhaps it will be the best (or only) way to please all the possible "building environments" at the same time...

[justdan96]

1) Yeah that wording makes sense. I'm trying to create a Makefile for nmake currently but there doesn't appear to be an easy way to convert a VC++ project to a Makefile, so it's taking a bit of time. I initially tried an Msys2 compile but it didn't work, I can give it another go, though.

2) I'm open to suggestions on that. My original idea was to use dockcross but there's a lot of dependencies to factor in. Linux, Mac and Windows are all supposed to be supported and right now I'm just compiling in VMs on VirtualBox, but that will be difficult to turn into a reproducible pipeline without some trickery.

Edit: An update on 1) - I did manage to get it working with Msys2. I will be updating the readme and Makefiles in the repos but I think this should replace the VC++ method as it will be way easier to create a pipeline with Msys2 over VC++.

[qyot27]

It only took a couple hours (because I was going in blind and starting from scratch, essentially), but I went ahead and whipped up a very barebones CMakeLists.txt to get the ball rolling (and because I'm partial to anything that can use Ninja, regardless of the size of the project; the only other option there is meson, AFAIK, but I don't have any Python skills to speak of). I was able to verify that there were no problems building libmediation and the tsmuxer cli for 64-bit. The pull request is already live, but it could easily remain a WIP unmerged thing until the major kinks are hammered out.

[justdan96]

I'll try this out when I get back from holiday, great to see how people are taking the project forward!

[r0lZ]

At Remux from 3D Bluray disk stays 3D-Planes at subtitles streams so as to original 3D Bluray.
No, the problem is when tsMuxeR shows the information from the ORIGINAL BD 3D. Since that information is not always correct, if you demux the streams and then remux them with the incorrect information, the result is wrong, and the 3D-Planes are not assigned to the correct streams any more.

[filler56789]

I have it compiling in Visual Studio 2017 - I'll update the repo soon.

So, ¿why haven't you released the .EXEs (both the CLI and the GUI) version 2.6.15? :confused:

[staina]

No, the problem is when tsMuxeR shows the information from the ORIGINAL BD 3D. Since that information is not always correct, if you demux the streams and then remux them with the incorrect information, the result is wrong, and the 3D-Planes are not assigned to the correct streams any more.

So this with me never yet not happened to. Into tsMuxer I'm load playlist with main movie, selected audio and subtitles, that I want leave and created new Bluray folder or Bluray ISO and 3D- Planes were to be associated as with original Bluray.

For example:

Original Bluray

1. subtitle stream ENG - 3D-Planes 1
2. subtitle stream JPN - 3D-Planes 2
3. subtitle stream TUR - 3D-Planes 3
4. subtitle stream RUS - 3D-Planes 4
5. subtitle stream POL - 3D-Planes 5

Remux Bluray select subtitle stream 1,3,5

1. subtitle stream ENG - 3D-Planes 1
2. subtitle stream TUR - 3D-Planes 3
3. subtitle stream POL - 3D-Planes 5

[justdan96]

So, ¿why haven't you released the .EXEs (both the CLI and the GUI) version 2.6.15? :confused:

I'd been prioritising the build pipeline work and getting some of the cruft out of the repo like the use of non-standard libraries.

If you need any help with compiling with Msys2 please let me know.

[r0lZ]

So this with me never yet not happened to. Into tsMuxer I'm load playlist with main movie, selected audio and subtitles, that I want leave and created new Bluray folder or Bluray ISO and 3D- Planes were to be associated as with original Bluray.

For example:

Original Bluray

1. subtitle stream ENG - 3D-Planes 1
2. subtitle stream JPN - 3D-Planes 2
3. subtitle stream TUR - 3D-Planes 3
4. subtitle stream RUS - 3D-Planes 4
5. subtitle stream POL - 3D-Planes 5

Remux Bluray select subtitle stream 1,3,5

1. subtitle stream ENG - 3D-Planes 1
2. subtitle stream TUR - 3D-Planes 3
3. subtitle stream POL - 3D-Planes 5
Most of the times, it works fine, because the subtitles streams are stored in the MPLS in the order of their PID, like this:
(The first number is the order in the playlist, the second is the PID.)
1. 4608 ENG - 3D-Planes 1
2. 4609 JPN - 3D-Planes 2
3, 4610 TUR - 3D-Planes 3
4. 4611 RUS - 3D-Planes 4
5. 4612 POL - 3D-Planes 5
But that order is not at all mandatory. The streams can be stored in the MPLS in a different order, like this:
1. 4608 ENG - 3D-Planes 1
2, 4610 TUR - 3D-Planes 2
3. 4609 JPN - 3D-Planes 3
4. 4611 RUS - 3D-Planes 4
5. 4612 POL - 3D-Planes 5
Note the inversion of the PID of streams 2 and 3. The two streams are stored in a relatively unusual order, but it's perfectly legal, and that happens! In the example above, the 3D-Planes are correctly assigned, because they are tied to the correct stream, in the order of the playlist. But tsMuxeR fails, when it show the information for such a 3D BD, because it assumes that the streams are stored in the order of their PID:
1. 4608 ENG - 3D-Planes 1
3, 4609 JPN - 3D-Planes 2
2. 4610 TUR - 3D-Planes 3
4. 4611 RUS - 3D-Planes 4
5. 4612 POL - 3D-Planes 5
The effect is that, in this example, streams 2 and 3 have the wrong 3D-Planes.

Note also that sometimes, a MPLS doesn't references all streams. Some subtitle streams are present in the M2TS, but not in the MPLS, like this:
1. 4608 ENG - 3D-Planes 1
X. 4609 JPN
2. 4610 TUR - 3D-Planes 2
3. 4611 RUS - 3D-Planes 3
4. 4612 POL - 3D-Planes 4
In this example, the JPN track is not referenced in the MPLS, and therefore it cannot be selected when that MPLS is played with a real BD player. I call it a "phantom stream", present in the M2TS, but not in the MPLS. Usually, another MPLS references that stream normally. I have no idea why some BDs are authored that way, but it's relatively frequent, especially for the Japanese language.
As a consequence, in this example, the JPN track has no 3D-Plane assigned (in this MPLS of course). TsMuxeR should simply omit it, and display only the streams referenced in the MPLS, like this:
1. 4608 ENG - 3D-Planes 1
2. 4610 TUR - 3D-Planes 2
3. 4611 RUS - 3D-Planes 3
4. 4612 POL - 3D-Planes 4
But it doesn't do that. Again, it assumes wrongly that the 3D-Planes must be assigned one at a time to all streams in the M2TS, in the order of their PID, and it shows this:
1. 4608 ENG - 3D-Planes 1
X. 4609 JPN - 3D-Planes 2
2. 4610 TUR - 3D-Planes 3
3. 4611 RUS - 3D-Planes 4
4. 4612 POL
Again, it's completely wrong (except for the first track). The unreferenced JPN track appears where it should be hidden, and it inherits the 3D-Plane of the next stream. Then, all 3D-Planes are off by 1. And the POL stream has lost its 3D-Plane completely.

I think that the problem is that tsMuxeR doesn't use really the MPLS to retrieve its information, at least for the stuff related to the 3D-Planes. Since it is a muxer/demuxer, it prefers to trust what it finds in the M2TS (or SSIF) files, and it assumes that the PIDs of the streams determines their order. But that's not correct. The 3D-Plane numbers are stored in the MPLS and are based on the information and order from the same MPLS.

Trust me, I have studied closely that bug, after several problems I have encountered when I have written BD3D2MK3D. It's obviously a major bug. BTW, you can use my program to examine how the 3D-Planes are assigned to the subtitle streams. I have written my own MPLS parser, because it was impossible to trust the 3D-Planes information displayed by tsMuxeR.

[filler56789]

I'd been prioritising the build pipeline work and getting some of the cruft out of the repo like the use of non-standard libraries.

Actually I was thinking less of my own curiosity and more of the curiosity of most users of tsMuxer... I bet most /all of them would like to test v2.6.15 and compare it to v2.60.12, and we already know they don't have the interest in "creating the binaries with their own hands" so to speak...

If you need any help with compiling with Msys2 please let me know.

Getting only the command-line .EXE compiled would be sufficient for my current level of curiosity. Until some days ago (I don't remember how many) I could only compile the libmediation stuff and satisfy the needs of the matroska-thing — of course the old error messages were replaced with the new ones, but that was a start and I intended to learn with them later... but now that there is a CMakeLists.txt, "nothing works anymore" :–/, CMake only says the configuring job contained errors and had to be stopped...

My original goal was download and install the other "dependencies" of tsMuxer's source-code and try again, but those dependencies should be in their, let's say, «original form», not in their mingw-blah-blah-name-of-the-package form. I have been using MSYS2 regularly since 2016 and until recently I never had to deal the mingw-prefixed packages which are "installed" in the mingw32 and mingw64 directories and not only look very-misplaced but also can mean a waste of HDD space (because of unnecessarily-duplicated files).

[filler56789]

Update 1:

This time I ignored the CMake stuff, and after building libmediation, I tried to build tsmuxer.exe, and this is what I got:

<MINGW32> make
make: *** No rule to make target 'src/textSubtitlesRenderWin32.cpp', needed by 'all'. Stop.

[qyot27]

I don't know why the CMakeLists.txt was merged, it was still a WIP pull request and I hadn't done any further work on it (including testing it on anything other than native Linux); a couple of files in tsmuxer's CLI directory had to be moved to a subdirectory so that they wouldn't get globbed into the file list and choke GCC with platform-irrelevant errors. But the Makefile hadn't been made aware of this move yet. In the meantime, just search for textSubtitlesRenderFT.cpp and textSubtitlesRenderWin32.cpp in the Makefile and change the path from src/ to src/osdep/.

[filler56789]

@qyot27: many thanks for the useful post *THUMBS UP*

Modifying the tsMuxer CLI makefile worked; but I also had to add another edit so that it could find "path-to/include/freetype2".
Now I get these errors :mad:

r:/msys2x86/gccs32/zer0th/bin/../lib/gcc/i686-w64-mingw32/9.2.0/../../../../i686-w64-mingw32/bin/ld.exe: cannot find -lz
r:/msys2x86/gccs32/zer0th/bin/../lib/gcc/i686-w64-mingw32/9.2.0/../../../../i686-w64-mingw32/bin/ld.exe: cannot find -lfreetype
collect2.exe: error: ld returned 1 exit status
make: *** [Makefile:74: ../bin/tsMuxeR.exe] Error 1

[filler56789]

Update 2:

I had to copy the zlib and the freetype libraries to the "......./i686-w64-mingw32/lib" directory, and now finally there exists a tsMuxeR.exe v2.6.15.

tsMuxeR version 2.6.15. github.com/justdan96/tsMuxer

But nope, there is no reason for celebrating yet.

[justdan96]

@qyot27 I merged the CMake stuff a bit early as I wanted to test the cross compilation, sorry should have done that on a separate branch.

@filler56789 Good to see you got the 32 bit zlib and Freetype libraries set up and the compile working. Once the crossbuild stuff is finished we should be able to generate Windows, Linux and Mac binaries easily using Docker.

[filler56789]

At last, here goes the pesky binary...
Play at your own risk :rolleyes:

http://www.mediafire.com/file/3pc2y8mab9ykhge/tsMuxeR-2.6.15-CLI.7z/file

[manolito]

Thanks very much for this build... :D

On my ancient computer (CPU without SSE2 support, WinXP) all the tsMuxeR.exe CLI executables from v.1.10.6 upwards crashed. This one doesn't, and the CLI works nicely with the older 2.6.12 GUI.

Only one thing does not work: Trying to create a BluRay ISO file directly results in a broken ISO and this error message:
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
terminate called after throwing an instance of 'std::runtime_error'
what(): Wrong Parameter.
No big deal...


Cheers
manolito

[filler56789]

@manolito: you're welcome :)

And to whom this may interest, here goes a 64-bit build:

http://www.mediafire.com/file/nq6nffseb4nyu87/tsMuxeR-2.6.15-CLI-64.7z/file

P.S.:

@justdan96: time to update the README.md alright.

"the program currently only compiles 32-bit executables, even on 64-bit systems"

[filler56789]

Only one thing does not work: Trying to create a BluRay ISO file directly results in a broken ISO and this error message:

Creating Blu-ray stream info and seek index
Creating Blu-ray playlist
Mux successful complete
Finalize ISO disk
terminate called after throwing an instance of 'std::runtime_error'
what(): The parameter is incorrect.


This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

Very interesting indeed, I have just confirmed the problem exists...

On the other hand, the 64-bit edition seems to be okay :confused:

Creating Blu-ray stream info and seek index
Creating Blu-ray playlist
Mux successful complete
Finalize ISO disk
Muxing time: 5 sec

The resulting .ISO is recognized by WinRAR, MediaInfo, and it is "playable" as well.

[manolito]

I just tested the official v. 2.6.12 on a different computer, and when trying to directly create a BD ISO there is no error message at all, but the resulting ISO is just as broken. The only difference when using your 2.6.15 CLI executable is the error message followed by Win7-64 telling me that the application is not working any more and must be closed.

So this error must already have been there before 2.6.15.


//EDIT//
Sorry I have to correct myself... :confused:
The ISO files created by v. 2.6.12 do work, they play in all the players I threw them at. What does not work is trying to open them in 7-Zip, and I am not sure if this has something to do with my 7-Zip version (19.00 x64). I remember that I was able to open ISOs in 7-Zip, but with an older 32-bit version.

But the 64-bit CLI version indeed works flawlessly for me under the 32-bit GUI.


(Probably stupid) question:
Can I use your 64-bit CLI version under the 32-bit GUI?

[filler56789]

I just tested the official v. 2.6.12 on a different computer, and when trying to directly create a BD ISO there is no error message at all, but the resulting ISO is just as broken. The only difference when using your 2.6.15 CLI executable is the error message followed by Win7-64 telling me that the application is not working any more and must be closed.

So this error must already have been there before 2.6.15.

Thanks for reporting. I had no use for the ISO feature of TSMuxer, so I had never tried it.

(Probably stupid) question:
Can I use your 64-bit CLI version under the 32-bit GUI?

I thought the answer should be "no", but because I am stubborn, I ran a quick test, and discovered that the answer is "yes" :eek:

[manolito]

:p:p:p:p

[outgoing]

Thanks for reporting. I had no use for the ISO feature of TSMuxer, so I had never tried it.

The feature to create the .iso is basic to create a 3D bluray image, without this function will not work to build a 3D.

[filler56789]

Very well, I've managed to make the CLI "stuff" somewhat less messy...
now the bundle includes the source-codes of both zlib and freetype2, in the same way it already included libmediation. Besides, I removed the GUI directory and the Visual Studio & Mac files. All the user has to do is run the autobuild.sh script. CMake is required for building zlib.

Evidently, I modified (i.e., simplified) tsMuxer's makefile (even more). But something strange happened: the mingw32 compiler built the .EXE normally (again), but the mingw64 one stopped the job because of something that it didn't like in the file tsMuxer/src/bitStream.cpp:

for (; len >= 8 && ((unsigned long) src % sizeof(unsigned)) != 0; len -= 8) {


It is strange because yesterday the problem didn't appear when I compiled the 64-bit .exe "manually" :confused:

So I added the cflag "-fpermissive" to the makefile and now the 64-bit compiler doesn't complain anymore.
I know this is not the actual solution to the problem, but it's all that I can do for the time being.

Download the archive from Mediafire:

http://www.mediafire.com/file/ep7zekj2sidq0a8/tsMuxer-CLI-2.6-15-src.7z/file

[gonca]

@manolito
I have the same version of 7zip as you and it opens iso files just fine

[filler56789]

Background: yesterday I intended to do some hexedit(s) in tsMuxerGUI.exe v2.6.12 and so I unpacked (upx -d) it. But then I discovered that the unpacked .EXE crashes when double-clicked :confused:

Question (@justdan96) — does the GUI v2.6.15 have this same "feature" (or design flaw) as the previous one? :confused:

[manolito]

@manolito
I have the same version of 7zip as you and it opens iso files just fine

Yes, mine does, too...

ImgBurn revealed the issue:
Normal ISO files use the ISO9660 + UDF1.02 file system, and 7-Zip opens these ISO files without problems. BluRay ISO files use the UDF2.50 file system, and this ISO format is not compatible with 7-Zip. This even happens on a Win7-64 computer which has built-in support for UDF2.50 (for WinXP users need to install a separate UDF2.50 driver).

So this issue is not the fault of tsMuxeR.

[justdan96]

I'm in the process of fixing up the CMake configuration so the binaries can be built via an automated pipeline for each OS & architecture, once I am home I'll see if filler56789's changes can merge easily into what I've already done so far. Also UPX won't be used in future builds.

[filler56789]

Feature request OR enhancement suggestion (whichever you prefer):

make tsMuxer accept and deal-with pure TrueHD streams, i.e., .thd files without an AC-3 substream. tsMuxer already accepts "coreless" DTS-HD streams, therefore...

Remember, .thd+ac3 is mandatory only for Blu-Ray authoring, not for generic .ts /.m2ts files.

[outgoing]

Another very nice feature to add, long ago Roman commented that he was going to implement but unfortunately did not it finally, is to keep the SubPath of the main playlist that has IG menu (pop up menu) linked in, whenever there is one with this feature ends up losing it. Sometimes it can be restored with bdedit but sometimes it is not fully compatible.

[ryu34]

Feature request OR enhancement suggestion (whichever you prefer):

make tsMuxer accept and deal-with pure TrueHD streams, i.e., .thd files without an AC-3 substream. tsMuxer already accepts "coreless" DTS-HD streams, therefore...

Remember, .thd+ac3 is mandatory only for Blu-Ray authoring, not for generic .ts /.m2ts files.

Would love this feature +1

[SeeMoreDigital]

While we're on the subject of feature requests...

The ability to create compliant HEVC video stream muxes would be nice.

[Gser]

Feature request OR enhancement suggestion (whichever you prefer):

make tsMuxer accept and deal-with pure TrueHD streams, i.e., .thd files without an AC-3 substream. tsMuxer already accepts "coreless" DTS-HD streams, therefore...

Remember, .thd+ac3 is mandatory only for Blu-Ray authoring, not for generic .ts /.m2ts files.

Demuxing DTS-HD files with the lossless part included also produces non-compliant .dts files (should be .dtshd) that DTS-HD Master Audio Suite fails to recognize. eac3to and mkvextract also have this problem.

[filler56789]

Demuxing DTS-HD files with the lossless part included also produces non-compliant .dts files (should be .dtshd) that DTS-HD Master Audio Suite fails to recognize. eac3to and mkvextract also have this problem.

IIRC, it's because the Master Audio Suite and the certified BD authoring tools expect that the .DTSHD files
(High-Resolution Audio, Lossless with or without the "core", and DTS Express)
include a header and a footer — but the containers, even the Blu-Ray transport stream, are not expected to store the DTSHD header and footer.

EDIT — I wrote "even the Blu-Ray transport stream" but
I should have written «especially the Blu-Ray transport stream», because
a transport stream cannot have global headers.

[outgoing]

any progress in the tsMuxer project?

[TEB]

I have access on a Harmonic A/V Analyser at work, and i can run through some TS files and check for compliancy if its needed!

[filler56789]

any progress in the tsMuxer project?

Not yet, sadly :(

But while the bug fixes and the enhancements don't happen, I have a couple of suggestions:

1) an overdue update to the README.md — for example, the instructions for building tsMuxer with MinGW-w64 && MSYS2 are not entirely correct, in fact they are a bit misleading;

2) forget the QT-based GUI and replace it with a .NET/Mono one — I think stax76 could do this :)

[Selur]

forget the QT-based GUI and replace it with a .NET/Mono one
Why? (personally I prefer Qt/C++ over .NET)

[filler56789]

Why? (personally I prefer Qt/C++ over .NET)

Good question :)
In other words, I don't have a good answer for that.

Personally I would like a GUI which could be [easily] compiled in MinGW-w64, just like Xvid's VfW configuration dialog can...
but then perhaps I would be "asking for too much" :)

[filler56789]

And FWIW, a new issue has been opened
(but not by me)

https://github.com/justdan96/tsMuxer/issues/9

[justdan96]

I've been able to get a build pipeline working to easily create Windows and Linux builds using Docker, I'll next try to add Mac and if that all appears to work I'll push to the repo. The readme will have to be updated for sure but it's going to make compiling a heck of a lot easier. I'll add the binaries that are produced to the repo as well.

Sorry for the recent lack of updates, my job has been keeping me very busy recently. If there is anyone else who wants to get involved please do - pull requests are always welcome!

[staina]

When will release new version supporting UHD Bluray, eventually how is far her development?

Thank you Staina

[justdan96]

At the moment I'm focusing on being able to consistently produce binaries for all platforms (Windows, Linux, Mac) and ensuring that the output is bug-free.

[outgoing]

Thanks anyway to everyone involved in the development of this excellent program.

[staina]

Most of the times, it works fine, because the subtitles streams are stored in the MPLS in the order of their PID, like this:
(The first number is the order in the playlist, the second is the PID.)
1. 4608 ENG - 3D-Planes 1
2. 4609 JPN - 3D-Planes 2
3, 4610 TUR - 3D-Planes 3
4. 4611 RUS - 3D-Planes 4
5. 4612 POL - 3D-Planes 5
But that order is not at all mandatory. The streams can be stored in the MPLS in a different order, like this:
1. 4608 ENG - 3D-Planes 1
2, 4610 TUR - 3D-Planes 2
3. 4609 JPN - 3D-Planes 3
4. 4611 RUS - 3D-Planes 4
5. 4612 POL - 3D-Planes 5
Note the inversion of the PID of streams 2 and 3. The two streams are stored in a relatively unusual order, but it's perfectly legal, and that happens! In the example above, the 3D-Planes are correctly assigned, because they are tied to the correct stream, in the order of the playlist. But tsMuxeR fails, when it show the information for such a 3D BD, because it assumes that the streams are stored in the order of their PID:
1. 4608 ENG - 3D-Planes 1
3, 4609 JPN - 3D-Planes 2
2. 4610 TUR - 3D-Planes 3
4. 4611 RUS - 3D-Planes 4
5. 4612 POL - 3D-Planes 5
The effect is that, in this example, streams 2 and 3 have the wrong 3D-Planes.

Note also that sometimes, a MPLS doesn't references all streams. Some subtitle streams are present in the M2TS, but not in the MPLS, like this:
1. 4608 ENG - 3D-Planes 1
X. 4609 JPN
2. 4610 TUR - 3D-Planes 2
3. 4611 RUS - 3D-Planes 3
4. 4612 POL - 3D-Planes 4
In this example, the JPN track is not referenced in the MPLS, and therefore it cannot be selected when that MPLS is played with a real BD player. I call it a "phantom stream", present in the M2TS, but not in the MPLS. Usually, another MPLS references that stream normally. I have no idea why some BDs are authored that way, but it's relatively frequent, especially for the Japanese language.
As a consequence, in this example, the JPN track has no 3D-Plane assigned (in this MPLS of course). BDSup2Sub should simply omit it, and display only the streams referenced in the MPLS, like this:
1. 4608 ENG - 3D-Planes 1
2. 4610 TUR - 3D-Planes 2
3. 4611 RUS - 3D-Planes 3
4. 4612 POL - 3D-Planes 4
But it doesn't do that. Again, it assumes wrongly that the 3D-Planes must be assigned one at a time to all streams in the M2TS, in the order of their PID, and it shows this:
1. 4608 ENG - 3D-Planes 1
X. 4609 JPN - 3D-Planes 2
2. 4610 TUR - 3D-Planes 3
3. 4611 RUS - 3D-Planes 4
4. 4612 POL
Again, it's completely wrong (except for the first track). The unreferenced JPN track appears where it should be hidden, and it inherits the 3D-Plane of the next stream. Then, all 3D-Planes are off by 1. And the POL stream has lost its 3D-Plane completely.

I think that the problem is that tsMuxeR doesn't use really the MPLS to retrieve its information, at least for the stuff related to the 3D-Planes. Since it is a muxer/demuxer, it prefers to trust what it finds in the M2TS (or SSIF) files, and it assumes that the PIDs of the streams determines their order. But that's not correct. The 3D-Plane numbers are stored in the MPLS and are based on the information and order from the same MPLS.

Trust me, I have studied closely that bug, after several problems I have encountered when I have written BD3D2MK3D. It's obviously a major bug. BTW, you can use my program to examine how the 3D-Planes are assigned to the subtitle streams. I have written my own MPLS parser, because it was impossible to trust the 3D-Planes information displayed by tsMuxeR.

You're right, checked I'm my 3D movies and at some is 3D-plane other in tsMuxer compared to BD3D2MK3D. I hope that the BD3D2MK3D displays these value right so I shall have to these 3D movies recreate.

[r0lZ]

Yes, the 3D-Plane list is right in BD3D2MK3D, because it is extracted from the MPLS file, and not guessed blindly like with tsMuxer.

@ developers: This is an important bug. Please do not forget it when you will fix the tsMuxer bugs. Thanks in advance.

[a5180007]

Hi all, before all I thank the tsMuxer developer for his fantastic software, and for accepting to release the source code.

it misses frames, or more accurately it thinks some frames are a part of a previous frame and muxes them as a part of it. The result is a stream that gets progressively more out of sync (at least those that are encoded for blu-ray UHD by X265)

There is a bug creating unsynchronized AV with some HEVC files, due to insufficient size of coded picture buffer.
In brief, when reading a nal the end of the buffer is reached before finding the next nal start_code, and the PTS is not incremented for this nal.

(Edit: correction changed)
I have corrected the bug on my side by simply changing the line 7 in avPacket.h from:

const static int MAX_AV_PACKET_SIZE = 32768;

to

const static int MAX_AV_PACKET_SIZE = 800000;


I am not a developer and have limited coding knowledge, so I won't submit a patch.

[a5180007]

It also uses the wrong stream type

Replace lines 41 and 42 in tsPacket.h

//static const uint8_t STREAM_TYPE_VIDEO_H265 = 0x24;
static const uint8_t STREAM_TYPE_VIDEO_H265 = 0x06;

with

static const uint8_t STREAM_TYPE_VIDEO_H265 = 0x24;
// static const uint8_t STREAM_TYPE_VIDEO_H265 = 0x25; /* HEVC conforming to profile */

Edit note: should normally be 0x25, but seems to be 0x24 in UHD Blu-rays

[justdan96]

What would be the simplest way to check that these changes have resolved the issues?

[filler56789]

Replace lines 41 and 42 in tsPacket.h

//static const uint8_t STREAM_TYPE_VIDEO_H265 = 0x24;
static const uint8_t STREAM_TYPE_VIDEO_H265 = 0x06;

with

static const uint8_t STREAM_TYPE_VIDEO_H265 = 0x24;
// static const uint8_t STREAM_TYPE_VIDEO_H265 = 0x25; /* HEVC conforming to profile */

Edit note: should normally be 0x25, but seems to be 0x24 in UHD Blu-rays

Thanks for chiming in.
But an actual solution should be not a mere replacement, but an additional possibility plus a "Select_Case" thing

(apologies for the VBspeak :o :D ).

Because tsMuxer is a transport stream multiplexer, not only a basic Blu-Ray authoring tool.

[filler56789]

When will release new version supporting UHD Bluray, eventually how is far her development?

Very far, sadly.

And the fact that the new tsMuxeR is becoming Linux-centric (so to speak) only makes things worse IMNSHO.

[filler56789]

Okay, since the GitHub repository was created 3.5 months ago and the owner has released ZERO binaries thus far, here go two CLI .exes built from the "improved" source-code...
Notice, the "improved" source-code requires a POSIX-threaded compiler, so I had to download old packages from the MinGW-w64 project @ SourceForge and use them in my MSYS2 environment; no way I would screw my MSYS2 setup with the "toolchains" provided by the MSYS2 devilopers.
The 32-bit binary seems to be OK; the 64-bit .EXE requires the three DLLs included in the archive.
No GUI because I have no interest in downloading the terabyte-sized QT5 stuff.

LINK: http://www.mediafire.com/file/mx0pzjne721x28u/tsMuxer-2.6.15-posixthreads.rar/file

[filler56789]

Its a shame that they don't want to implement the stuff with native threading. winpthreads is kinda crappy.
Especially since someone already did all the work and made a header file with std::thread support for win32 threading model as well.

https://github.com/meganz/mingw-std-threads

Many thanks for the useful post, nevcairiel :goodpost: :thanks:

I followed the instructions and managed to build the new tsMuxeR with the Win32-threaded GCC :sly:

[justdan96]

In case anyone is wondering why there haven't been any binaries produced so far it's primarily because how long it has taken for me to produce a build pipeline.

I wanted to use dockcross and osxcross Docker containers but ran into all sorts of issues getting them set up to build the project. After a while I had to scrap the whole effort and start over.

I set things up in a VM to get Linux, Windows and MacOS builds all being produced successfully, I'm now transferring that setup over to a new, clean Docker container. Once that's all completed and tested I'll use GitHub Actions to get builds created automatically on each push.

It's taking a while I know but the upshot will make things a lot easier to manage going forward!

[filler56789]

...
I set things up in a VM to get Linux, Windows and MacOS builds all being produced successfully, I'm now transferring that setup over to a new, clean Docker container. Once that's all completed and tested I'll use GitHub Actions to get builds created automatically on each push.

Have you checked that the Windows binaries that you've managed to build DO NOT depend on external libraries?

Namely, on winpthreads, seh and libstdc++.

Because when I use the winpthread-ed GCC from the MinGW-w64 project with MSYS2, the 64-bit .EXE is not linked statically to those libraries; and when I used the "toolchain" provided by pacman, even zlib could not be linked statically.

[qyot27]

-DCMAKE_EXE_LINKER_FLAGS="-static-libstdc++ -static -pthread" when configuring resolves it with vanilla MSys2 with default repo packages.

Comparison with ldd:
'plain' build without the additional linker flags:
$ ldd tsmuxer-plain.exe
ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7fff09500000)
KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7fff09400000)
KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7fff065f0000)
GDI32.dll => /c/WINDOWS/System32/GDI32.dll (0x7fff07910000)
win32u.dll => /c/WINDOWS/System32/win32u.dll (0x7fff072f0000)
gdi32full.dll => /c/WINDOWS/System32/gdi32full.dll (0x7fff07350000)
zlib1.dll => /mingw64/bin/zlib1.dll (0x62e80000)
msvcrt.dll => /c/WINDOWS/System32/msvcrt.dll (0x7fff08d10000)
msvcp_win.dll => /c/WINDOWS/System32/msvcp_win.dll (0x7fff07510000)
ucrtbase.dll => /c/WINDOWS/System32/ucrtbase.dll (0x7fff06490000)
USER32.dll => /c/WINDOWS/System32/USER32.dll (0x7fff07b40000)
gdiplus.dll => /c/WINDOWS/WinSxS/amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.18362.418_none_17b1a56c6d9fd02b/gdiplus.dll (0x7ffed5a00000)
libgcc_s_seh-1.dll => /mingw64/bin/libgcc_s_seh-1.dll (0x61440000)
libwinpthread-1.dll => /mingw64/bin/libwinpthread-1.dll (0x64940000)
libstdc++-6.dll => /mingw64/bin/libstdc++-6.dll (0x6fc40000)
combase.dll => /c/WINDOWS/System32/combase.dll (0x7fff089d0000)
RPCRT4.dll => /c/WINDOWS/System32/RPCRT4.dll (0x7fff08000000)
bcryptPrimitives.dll => /c/WINDOWS/System32/bcryptPrimitives.dll (0x7fff06af0000)

With the linker flags given above:
$ ldd tsmuxer.exe
ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7fff09500000)
KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7fff09400000)
KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7fff065f0000)
GDI32.dll => /c/WINDOWS/System32/GDI32.dll (0x7fff07910000)
win32u.dll => /c/WINDOWS/System32/win32u.dll (0x7fff072f0000)
gdi32full.dll => /c/WINDOWS/System32/gdi32full.dll (0x7fff07350000)
msvcp_win.dll => /c/WINDOWS/System32/msvcp_win.dll (0x7fff07510000)
ucrtbase.dll => /c/WINDOWS/System32/ucrtbase.dll (0x7fff06490000)
USER32.dll => /c/WINDOWS/System32/USER32.dll (0x7fff07b40000)
msvcrt.dll => /c/WINDOWS/System32/msvcrt.dll (0x7fff08d10000)
gdiplus.dll => /c/WINDOWS/WinSxS/amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.18362.418_none_17b1a56c6d9fd02b/gdiplus.dll (0x7ffed5a00000)
combase.dll => /c/WINDOWS/System32/combase.dll (0x7fff089d0000)
RPCRT4.dll => /c/WINDOWS/System32/RPCRT4.dll (0x7fff08000000)
bcryptPrimitives.dll => /c/WINDOWS/System32/bcryptPrimitives.dll (0x7fff06af0000)


The actual filesizes also corroborate this; the binary using the above linker flags is a whole 3MB larger (before stripping).

[justdan96]

You should be able to set the CMake flag "TSMUXER_STATIC_BUILD", which should generate a static build automatically.

For the Docker container specifically the Windows builds produced only use static dependencies and don't have any sort of external dependencies - I checked with Dependency Walker.

[qyot27]

You should be able to set the CMake flag "TSMUXER_STATIC_BUILD", which should generate a static build automatically.
That'll work too. I didn't remember that CMakeLists for each subdir had been added.

[filler56789]

I followed the instructions and managed to build the new tsMuxeR with the Win32-threaded GCC :sly:

I've just updated my GitHub repository accordingly:

https://github.com/filler56789/RV-tsMuxeR

[justdan96]

I've started creating the GitHub actions to create the builds for all 3 platforms. I haven't quite finished yet but if people could test the builds produced I'd really appreciate it!
https://github.com/justdan96/tsMuxer/actions

Just check the "Artifacts" on the latest run of "Build for Linux", "Build for Windows" and "Build for Mac".

[filler56789]

https://github.com/justdan96/tsMuxer/actions

Just check the "Artifacts" on the latest run of "Build for Linux", "Build for Windows" and "Build for Mac".

Hummm, only the 64-bit .EXE, that's not good for the users of Windows XP :)

(I know, XP should be dead and buried, but don't forget tsMuxeR had been a 32-bit-only application since its zer0th day...)

P.S.: ¿¿¿ where is the new GUI ???

[justdan96]

Hummm, only the 64-bit .EXE, that's not good for the users of Windows XP :)

If they are dedicated enough to use an operating system that went out of support over 5 years ago I'd like to think they are dedicated enough to compile it themselves :)

P.S.: ¿¿¿ where is the new GUI ???

I haven't added Qt5 to the Docker container yet. For Windows it would be straightforward, Linux a bit more difficult as I'd need to compile Qt5 as static and Mac even more complicated as I'd have to compile Qt5 as static with osxcross.

Long story short, I'll get it sorted but it could take some time.

[qyot27]

If they are dedicated enough to use an operating system that went out of support over 5 years ago I'd like to think they are dedicated enough to compile it themselves :)
There are modern-ish platforms that use 32-bit Windows 10. Kind of but not really niche things like the Quantum Byte/Byte Plus or other mini-PCs. A lot of them (like the Byte3) have since moved to 64-bit Windows 10 or Ubuntu or leave OS installation to the user, but the first couple generations from ~2015-2017 used 32-bit Windows and 32-bit UEFI.

That means either having a separate i686-w64-mingw32 toolchain that needs to be invoked, or the existing toolchain needs to be multilib-enabled (in which case it's just a matter of throwing in some -m32 flags and telling it where the /lib directory is for i686, sometimes it might require overriding the CMAKE_SYSROOT, but not often).

What would be a showstopper specifically for XP is if MXE builds its toolchain with Secure API support turned on in MinGW-w64, as that will restrict everything it builds to Vista+.

[a5180007]

Hi all,

Another bug for aac muxing. In brief, the aac frame size is written on 13 bits (bits 31-43 in the frame), however tsMuxeR takes into account only the first 11 bits. So when the aac frame size is above 2048 bytes, tsMuxeR incorrectly reports a bad frame and discards it.

In aac.cpp, replace line 52:

int AACCodec::getFrameSize(uint8_t* buffer)
{
return buffer[4]*8 + (buffer[5] >> 5);
}

with

int AACCodec::getFrameSize(uint8_t* buffer)
{
return ((buffer[3] & 0x03) << 11) + (buffer[4] << 3) + (buffer[5] >> 5);
}

[SeeMoreDigital]

Another bug for aac muxing.
LC-AAC or HE-AAC?

[a5180007]

LC-AAC or HE-AAC?

All AAC types.
Edit: I've just tried and I can confirm, tsMuxeR accepts LC and HE and the above fixes both.

[justdan96]

That means either having a separate i686-w64-mingw32 toolchain that needs to be invoked, or the existing toolchain needs to be multilib-enabled (in which case it's just a matter of throwing in some -m32 flags and telling it where the /lib directory is for i686, sometimes it might require overriding the CMAKE_SYSROOT, but not often).

I suppose I can look at making a CMake option for it, if the demand is there.

Also @a5180007 thanks for the bug reports, I'll get those created in GitHub as issues so we can take a closer look at them.

Additionally I've taken a close look at tsMuxerGUI and there aren't any actual code dependencies on tsMuxer - so a drop-in replacement could be created. Qt is pretty heavyweight for a simple application. My preference would be an application that can be made cross-platform with ease that doesn't depend on large GUI frameworks. I don't think we can swap out Qt for something like Nuklear that easily within the existing application so it may even be easier to rewrite it (if someone out there can prove me wrong I'd be very thankful!).

I'll create an issue for it so we can track it.

[a5180007]

Also tsMuxeR cannot demux correctly mp4 aac 5.1 : the problem seems to be linked to a bug from ffmpeg. tsMuxeR takes the channel count from 'mp4a' atom (cf. movDemuxer.cpp line 1252), but as noted here (http://ffmpeg.org/pipermail/ffmpeg-user/2019-February/043300.html) ffmpeg sets the channel count to 2 in 'mp4a' atom even for aac 5.1, and the correct channel count has to be taken from 'esds' atom.

The following should correct the bug, could anybody please test and report:
In movDemuxer.cpp add line 186 as follows:

if (isAAC) {
m_aacRaw.m_channels = m_sc->channels; // added line
m_aacRaw.buildADTSHeader(dst, frameSize + AAC_HEADER_LEN);
memcpy(dst + AAC_HEADER_LEN, buff, frameSize);
dst += frameSize + AAC_HEADER_LEN;
}
and add line 1454 as follows:

if (st->parsed_priv_data) {
((MovParsedAudioTrackData*)st->parsed_priv_data)->isAAC = true;
st->parsed_priv_data->setPrivData(st->codec_priv, st->codec_priv_size);
st->channels = (st->codec_priv[1] >> 3) & 0x0f; // added line: copy channel count from 'esds' AudioSpecificConfig
}

[a5180007]

I have corrected the bug on my side by simply changing the line 7 in avPacket.h from:

const static int MAX_AV_PACKET_SIZE = 32768;

to

const static int MAX_AV_PACKET_SIZE = 800000;



Ok, so I have tried to get totally rid of the max frame size limitation, as HEVC UHD frames can be several MBs.

The following should do the trick, could anybody please test and report:

In mpegStreamReader.cpp at line 130:

//if (m_bufEnd - m_curPos < MAX_AV_PACKET_SIZE) { // remove condition : size of frame is now checked for all frames
uint8_t* nextNal = NALUnit::findNALWithStartCode(min(m_curPos + 3,m_bufEnd), m_bufEnd, m_longCodesAllowed);
if (nextNal == m_bufEnd) {
storeBufferRest();
return NEED_MORE_DATA;
}
//}

and at line 65, remove truncating of last frame:

avPacket.size = m_tmpBufferLen; //changed from min(MAX_AV_PACKET_SIZE, m_tmpBufferLen);
}
/*if (m_tmpBufferLen > MAX_AV_PACKET_SIZE) {
LTRACE(LT_ERROR, 2, "Too large last buffer (" << m_tmpBufferLen << " bytes). Truncate buffer to " <<
MAX_AV_PACKET_SIZE << " bytes. It does not have to be!");
} */

With this fix the MAX_AV_PACKET_SIZE can be left = 32768 (although I don't know where this value comes from...)

[justdan96]

Thank you so much a5180007, I'll test these fixes myself and if they are resolved I'll publish the test cases as well.

[FilipeAmadeuO]

Thank you so much a5180007, I'll test these fixes myself and if they are resolved I'll publish the test cases as well.
Can you publish new binaries here for testing ?
Any plan to build with GUI ?

[Hart2hart]

To go back a step and sorry if I missed it...

Were binaries produced that would be “like” V2.6.12 so we can compare results to the long exiting binary files. This would provide a great starting point for enhancements to 3D and HEVC 4K images.

Excellent that TSMuxeR has been released to community. I’ll jump in at some point.

[justdan96]

Sorry I didn't update fully here, here is the quote from the readme:

To download the pre-compiled binaries head over to the following URL (you must be logged in) https://github.com/justdan96/tsMuxer/actions and click on the latest action for your chosen platform (Windows, Mac or Linux). In the Artifacts section in the top-right you can download a ZIP file containing the executable for tsMuxer.

At the moment only the CLI is included, the GUI is not yet available.

We've had quite a few good enhancements and bug fixes go into the repo recently so I think we are close to a release of 2.6.16. I want to get a nice automated workflow for creating the releases in GitHub so it may take a while for me to develop it.

Yes the binaries will be similar to 2.6.12, you can test the CLI now and use the older GUI if you can't (or don't want to) compile it yourself. Once I get the automated builds in GitHub working with tsMuxerGUI as well you can use the official binaries for that as well.

It would be fantastic if people can compare the older versions to the latest, you can post the results to this forum thread or if you encounter a specific issue with what you think is the root cause you can create an issue on GitHub.

[a5180007]

Hi justdan96, could you please hold to 2.6.15 as I will keep on submitting commits over the week-end for the additional UHD formats/fps.
Can anybody share the ExtensionData formatting info (Jdobbs ? Pelican ?) for HDR10+, Dolby Vision and SL-HDR so that we can incorporate it into .clpi/.mpls/.bdmv as required.

[justdan96]

Sure, we still have some things to sort out before the point release anyway so I don't mind holding off for a bit.

[Hart2hart]

I can see you guys are busy over at GitHub!
Before I dive in two questions:

o Do you think any of the custom libraries you replaced with standard version would have included custom versions of named functions?

o Is there a module/object interaction diagram or would it be simpler to just pull all source into an ide like visual studio and let it build one?

Thanks!

[jdobbs]

Hi justdan96, could you please hold to 2.6.15 as I will keep on submitting commits over the week-end for the additional UHD formats/fps.
Can anybody share the ExtensionData formatting info (Jddobs ? Pelican ?) for HDR10+, Dolby Vision and SL-HDR so that we can incorporate it into .clpi/.mpls/.bdmv as required.Here's what I found for the MPLS extension based on looking at a number of original discs:

00 00 00 38 Length of ExtensionData()
00 00 00 18 Data block start address
00 00 00 01 24 bits reserved followed by number_of_ext_data_entries (1)
00 03 00 05 ID1 (0x3) and ID2 (0x5) of the extension
00 00 00 18 ext_data_start_address
00 00 00 24 ext_data_length
00 00 00 20 length of following data (?)
01 00 00 00
10 00 00 00
HDR_DATA 24 bytes

Example of HDR_DATA:
33 C2 86 C4 Master Display=G(13250,34500)
1D 4C 0B B8 B(7500,3000)
84 D0 3E 80 R(34000,16000)
3D 13 40 42 WP(15635,16450)
0F A0 00 32 L(40000000,50) = Mastering display luminance: min: 0.0050 cd/m2, max: 4000 cd/m2 = 4000/50
07 8D 02 C5 cll=1933,709Note that the luminance is stored using factors of 10,000 (min * 10,000 and max / 10,000) -- I don't know why. I would assume so they can fit in a 16 bit integer.

Dolby seems to use the same extension, not sure about SL-HDR.

Here is the extension for index.bdmv

00 00 00 20 Length of ExtensionData()
00 00 00 18 Data block start address
00 00 00 01 24 bits reserved followed by number_of_ext_data_entries (1)
00 03 00 01 ID1 (0x3) and ID2 (0x1) of the extension
00 00 00 18 ext_data_start_address
00 00 00 0C ext_data_length
00 00 00 08 I think this is length of following info
21 00 03 00 upper nibble of first byte is disc type (0x2 = BD25/50), not sure about 0x03*
00 00 00 00 seems to be reserved...

*Made a correction to the index.bdmv extension data. I'd put a value of 0x20 at offset 24, and it should have been 0x21

[12/13/2019]

Please note also that for UHD the version_number of the .index, clpi, and MPLS files have to be set to "0300" instead of "0200". In addition the video_format variable in the CLPI's ProgramInfo() table must be set to 0x8 for 2160p. Currently TSMUXER sets it to 0x6 (1080p). The stream_coding_type must be set to 0x24 for HEVC.

In order to do dolby vision, TSMUXER will have to be modified so the stream id for the dolby vision extension stream is set to 4117 and an additional entry for dolby vision must be added to the STN_table()

*Made a correction to the index.bdmv extension data. I'd put a value of 0x20 at offset 24, and it should have been 0x21
[Dec 13, 2019]

[justdan96]

o Do you think any of the custom libraries you replaced with standard version would have included custom versions of named functions?


I'm not too sure actually - but I did pick out the pull requests where the replacements were made so you should be able to check it yourself:
https://github.com/justdan96/tsMuxer/pull/16/commits/b098a6de41fdaaa2aee9f6d9f7a15072f17cf780
https://github.com/justdan96/tsMuxer/pull/22/commits/0fd3b37746af0836ae59bffecf0d75cc53add9cc
https://github.com/justdan96/tsMuxer/pull/21/commits/721d5c12d9591cd48d376b28f19ace39b8fc6cf1


o Is there a module/object interaction diagram or would it be simpler to just pull all source into an ide like visual studio and let it build one?


There isn't a diagram currently. I just had a quick search around and it looks like maybe Doxygen can be used together with Graphviz to generate one. Something for me to think about!

[a5180007]

@jdobbs thanks, this HDR metadata info is exactly what I was looking for!

Current progress:
- The patch for changing BD version to 0300 has already been merged in the master;
- The patch for setting coding_type to 0x24 has also already been merged in the master;
- I've just submitted the patch for setting video_format to 8 for UHD;
- Also bugs were corrected for frame size limitation, and for MP4/AAC and EAC3 bitrates and channels.

@justdan96 tsMuxeR should now be able to author UHD but without HDR.
The HDR modifs in .clpi, .mpls and .bdmv will require a bit of time, first I need to understand how to extract the HDR metadata info from the HEVC SEI.
Let's say HDR (excl. Dolby Vision) will be my objective for 2.6.17...

[staina]

Where it is possible download new version for Windows?
How is far full support UHD Bluray including HDR, Dolby Vision, Dolby Atmos?
Is already fixed loaded 3D - plane at 3D Bluray?

Thank for answer. Staina

[Video Dude]

Hopefully there will be a reconsideration and 32 bit binaries can be built. One main way to capture transport streams from hardware is the 1394 firewire port. There are no Windows 64 bit drivers that work. Using a Windows 32 bit version is a must. Users don't want to capture on 1 PC and then transfer to stream to a second machine to mux.

[filler56789]

Hopefully there will be a reconsideration and 32 bit binaries can be built.

32-bit binaries CAN be built. The problem is, justdan96 simply doesn't care about them. Also, his workflow became *nix-centric, which means even the Windows builds of tsMuxeR now require a posix-threaded compiler.

[a5180007]

@xavery @justdan96 under Windows/MSVC I can't remove #include "stdafx.h" from textSubtitles.cpp without having 171 errors (!!), see file:
Error.Log.txt (https://github.com/justdan96/tsMuxer/files/3907591/Error.Log.txt)

Any alternative to get rid of stdafx.h ?

Edit : found the solution: actually the "rarely-used stuff from Windows headers" is still required i.e. we need to add #define WIN32_LEAN_AND_MEAN in textSubtitles.h

[Richard1485]

Additionally I've taken a close look at tsMuxerGUI and there aren't any actual code dependencies on tsMuxer - so a drop-in replacement could be created.

That would be useful. On Linux, I found that the GUI worked fine but threw a series of errors upon first use, most of which seemed to relate to cosmetic aspects of the interface. (At the time, I was using 2.6.9 for reasons outlined earlier in the thread.)

[justdan96]

I didn't think there would be much demand for 32-bit binaries, it does look like the demand is there so I'm pretty sure it would be easy enough to set up in CMake and I can just create a separate build.

Latest (64-bit) binaries for the CLI are available on GitHub, I'm still working on getting the GUI created automatically but I now know how I'll get tsMuxerGUI builds made for Linux and Windows so it's just MacOS where I need to do some more experimenting.

Also I moved house over the weekend so things may be a bit slower the next couple of weeks while I get broadband set up.

[hubblec4]

Hi justdan96

Very nice to see this project is going on. Could you tell me where I can download the latest version?

[filler56789]

Could you tell me where I can download the latest version?

From my Mediafire folder:

http://www.mediafire.com/file/4nlp9ap0wijbhqb/tsMuxeR64-2.6.15.b-.rar/file

[justdan96]

Hi justdan96

Very nice to see this project is going on. Could you tell me where I can download the latest version?

Official binaries are available on GitHub, take a look at the readme for more details!

https://github.com/justdan96/tsMuxer

[filler56789]

Official binaries are available on GitHub, take a look at the readme for more details!

https://github.com/justdan96/tsMuxer

Evidently justdan96 ignores the fact that not everybody has /wants-to-create a GitHub account.

To download the pre-compiled binaries head over to the following URL (YOU MUST BE LOGGED IN)

[FilipeAmadeuO]

Evidently justdan96 ignores the fact that not everybody has /wants-to-create a GitHub account.
I must say that i do agree :)
Any chance to download binary without sign in to GitHub ?

[hubblec4]

Official binaries are available on GitHub, take a look at the readme for more details!

https://github.com/justdan96/tsMuxer

Was not so easy to find, but I found it. It seems there is a tsMuxer.exe only at the moment, right?

I'm mostly interested in demuxing. How good works the new tsMuxeR?

Seamless branching disc's supported? Remove/Skip identical frames?
I had read that the last old rev of tsMuxeR has issues with subtitle streams, this issues are fixed?

E-AC3 EX support?

[Video Dude]

I didn't think there would be much demand for 32-bit binaries, it does look like the demand is there so I'm pretty sure it would be easy enough to set up in CMake and I can just create a separate build.


Thank you justdan96. Much appreciated.

[r0lZ]

I'm mostly interested in demuxing. How good works the new tsMuxeR?
I have just tried it to demux a few 3D DBs (not UHD), and it seems to work correctly.

Seamless branching disc's supported? Remove/Skip identical frames?

I suppose that the code that does that in the original version has not been modified, so I guess it's OK.

I had read that the last old rev of tsMuxeR has issues with subtitle streams, this issues are fixed?

Unfortunately, that bug has been added in v2.6.10 or v2.6.11, and I suppose that the latest closed source version (v2.6.12) has been used as the basis for the open source development. So, I suppose that the bug is still present. Unfortunately, that bug happens only in some relatively rare cases, and I don't remember what BD has caused it, so I have been unable to check if the bug is still present. I will try to find a good example and report it here, but that may take some time. Currently, if you want to be sure, I suggest to use v2.6.9 (although it has other bugs with the 3D-planes, not important for a 2D BD, but that should be fixed too). Or, use the new version and verify carefully the subtitles timings. If you find an example of bad timings, report it yourself, to help the developers.

[hubblec4]

Thanks for your answer r0IZ. When I have a bit time I will test some BDs and report issues.

[r0lZ]

BTW, I've found the post I wrote about that subtitle timing bug. You can read it here (https://forum.doom9.org/showthread.php?p=1689236#post1689236).
As you can see, it happens only with movies with several parts (multi-angle, multi-story or simply split for protection purpose), and furthermore it's not always the case. For example, the multi-angle Disney BD are not affected. Difficult to test in that conditions, but you can exclude all BDs made of only a single M2TS.

[hubblec4]

OK, I read this post, interesting. I hope justdan96 can fix all this issues.
Mostly BDs are authored with one m2ts file, but all the great movies have often multiple editions and for me is it a must to store all editions in a single mkv.

[justdan96]

I must say that i do agree :)
Any chance to download binary without sign in to GitHub ?

I'm working on it! I've opened an issue in GitHub to track it and I just today got a tsMuxerGUI build working on MacOSX so the official binaries for the CLI and GUI should be going into the "Releases" section on GitHub soon.

It will just be slow progress for a while, there's lots of things we still need to sort out for my house move - least of all broadband!

[FilipeAmadeuO]

I'm working on it! I've opened an issue in GitHub to track it and I just today got a tsMuxerGUI build working on MacOSX so the official binaries for the CLI and GUI should be going into the "Releases" section on GitHub soon.

It will just be slow progress for a while, there's lots of things we still need to sort out for my house move - least of all broadband!
Perfect. I am GUI type user so take your time :)

[filler56789]

FWIW... Baldrick is sharing the "unofficial" 2.6.15 binaries for Mac, Linux and Windows — but no GUI yet (sadly - ?)

https://www.videohelp.com/software/tsMuxeR

[gonca]

You can always try the GUI from 2.6.12 with tsMuxeR.exe 2.6.15.
Seems to work ok

[jdobbs]

To those who are making changes:

How hard would it be to flag a secondary video track and set its PID as 4117? I'm testing using v2.6.15 in creation of the UHD Blu-Ray's M2TS (so that BD Rebuilder doesn't have to remux/correct the video streams and PMT packets again afterward). I have it working for non-DolbyVision sources, but in order to support DolbyVision, I need to be able to have the dolby stream's PID be 4117 in the packet headers and the PMT.

Any help would be deeply appreciated.

[BloodyRipper]

To those who are making changes:

How hard would it be to flag a secondary video track and set its PID as 4117? I'm testing using v2.6.15 in creation of the UHD Blu-Ray's M2TS (so that BD Rebuilder doesn't have to remux/correct the video streams and PMT packets again afterward). I have it working for non-DolbyVision sources, but in order to support DolbyVision, I need to be able to have the dolby stream's PID be 4117 in the packet headers and the PMT.

Any help would be deeply appreciated.
The code actually looks ready for setting custom PIDs for the elementary streams making up the TS, but these are currently hardcoded to a number of base values which are then offset by the number of the given streams already in the TS, according to its type.

Would you be okay with setting a custom PID via the meta file? Sounds like it could suit your use case.

[jdobbs]

The code actually looks ready for setting custom PIDs for the elementary streams making up the TS, but these are currently hardcoded to a number of base values which are then offset by the number of the given streams already in the TS, according to its type.

Would you be okay with setting a custom PID via the meta file? Sounds like it could suit your use case.That would be perfect.

[a5180007]

How hard would it be to flag a secondary video track and set its PID as 4117? I'm testing using v2.6.15 in creation of the UHD Blu-Ray's M2TS (so that BD Rebuilder doesn't have to remux/correct the video streams and PMT packets again afterward).

@jdobbs I am working on it: it needs an early scan of the hevc streams -to detect the DV \x62 (+\x01) nal_unit_type- before tsMuxer assigns the new video PIDs.

I'll push the patch as soon as the patch for HDR10/HDR10+ has been merged/tested.

[filler56789]

@justdan96:

the 24-bit DTS-Express muxing bug in the GUI, ¿has it been fixed?

[jdobbs]

@jdobbs I am working on it: it needs an early scan of the hevc streams -to detect the DV \x62 (+\x01) nal_unit_type- before tsMuxer assigns the new video PIDs.

I'll push the patch as soon as the patch for HDR10/HDR10+ has been merged/tested.Can you give me a heads up when it gets integrated?

This new version sure makes BD-RB's life easier. All it has to do now is do updates to the MPLS & CLPI after a TSMUXER run (except, of course, for DV). That's the easy (and quick) part. If you need anything from me, just let me know.

Thanks!

[jdobbs]

@jdobbs I am working on it: it needs an early scan of the hevc streams -to detect the DV \x62 (+\x01) nal_unit_type- before tsMuxer assigns the new video PIDs.

I'll push the patch as soon as the patch for HDR10/HDR10+ has been merged/tested.Also, please note that I corrected a mistake I had in the post about extensions. I'd mistakenly put a value of 0x20 instead of 0x21 in one bye of the index.bdmv extension.

[BloodyRipper]

Can you give me a heads up when it gets integrated?

This new version sure makes BD-RB's life easier. All it has to do now is do updates to the MPLS & CLPI after a TSMUXER run (except, of course, for DV). That's the easy (and quick) part. If you need anything from me, just let me know.

Thanks!
I took the liberty of implementing this via an explicit parameter in the meta file. The pull request (https://github.com/justdan96/tsMuxer/pull/74) is already there, but will probably be merged to master only after I add support in the GUI as well. You can download the experimental build here (https://drive.google.com/open?id=1GrqSNIJP_1wU4ND69FkDCMTaJGI_jQaQ). PIDs can be assigned to streams by adding a simple numeric parameter called "pid" to the stream description in the meta file, for example :


V_MPEG4/ISO/AVC, "raw/video.h264", insertSEI, contSPS, pid=666
A_AC3, "raw/audio01.ac3", pid=0xf0f

Perhaps you can test if everything works fine while proper support for DV streams is in the works. The custom PIDs are of course also used in the PMT.

[filler56789]

Ouch, it seems justdan96 really loves to complicate things :scared:

Create Way of Downloading Binaries without Sign-In

https://github.com/justdan96/tsMuxer/issues/60

Why he doesn't simply upload the releases to GitHub OR share the "beta binaries" on Google Drive /Mediafire /whatever is beyond me.

[a5180007]

Also, please note that I corrected a mistake I had in the post about extensions. I'd mistakenly put a value of 0x20 instead of 0x21 in one bye of the index.bdmv extension.

@jdobbs, in fact I've put 0x51 in the commit (5=66/100 GB disk 123 Mbps, 1=4k). The patch includes reading of HDR10/HDR10+ metadata in the hevc SEI nal, detection of DV nal_unit, adding the HDR10/HDR10+ attribute in the .mpls and .clpi, the additional DV field in the playlist STN table, and the extention data to .mpls and .bdmv. So the change to the DV PID is really all what is missing.

The best would be that justdan96 pushes the HDR commit to an alternative branch for thorough testing.

Edit:
21 00 03 00 upper nibble of first byte is disc type (0x2 = BD25/50), not sure about 0x03*
The new BDEdit has been of great help, thanks pelican. The second byte in the .bdmv is : 3-bit zero/reserved, isHDR10+, isSL-HDR2, isDV, isHDR10, isSDR.

Are there any Blu-ray already released with SL-HDR2 ?

[jdobbs]

@jdobbs, in fact I've put 0x51 in the commit (5=66/100 GB disk 123 Mbps, 1=4k). The patch includes reading of HDR10/HDR10+ metadata in the hevc SEI nal, detection of DV nal_unit, adding the HDR10/HDR10+ attribute in the .mpls and .clpi, the additional DV field in the playlist STN table, and the extention data to .mpls and .bdmv. So the change to the DV PID is really all what is missing.

The best would be that justdan96 pushes the HDR commit to an alternative branch for thorough testing.

Edit:

The new BDEdit has been of great help, thanks pelican. The second byte in the .bdmv is : 3-bit zero/reserved, isHDR10+, isSL-HDR2, isDV, isHDR10, isSDR.

Are there any Blu-ray already released with SL-HDR2 ?Can the 0x51 be modified to 0x21? Most of the reencodes I do are output to BD-25/50. I don't even have a burner that supports 66/100. If not, I can do it after the fact, I guess (as I do now).

When will this patch show up in the nightly releases (if that is the plan)?

Where do I get a copy of the latest BDEDIT? I looked at the BDEDIT thread and it looked like the last edit was many years ago. I use BDEDIT all the time. It's really useful software.

[jdobbs]

I took the liberty of implementing this via an explicit parameter in the meta file. The pull request (https://github.com/justdan96/tsMuxer/pull/74) is already there, but will probably be merged to master only after I add support in the GUI as well. You can download the experimental build here (https://drive.google.com/open?id=1GrqSNIJP_1wU4ND69FkDCMTaJGI_jQaQ). PIDs can be assigned to streams by adding a simple numeric parameter called "pid" to the stream description in the meta file, for example :


V_MPEG4/ISO/AVC, "raw/video.h264", insertSEI, contSPS, pid=666
A_AC3, "raw/audio01.ac3", pid=0xf0f

Perhaps you can test if everything works fine while proper support for DV streams is in the works. The custom PIDs are of course also used in the PMT.Thanks! I'll test it. Does this version also have the other changes made recently (like the correction for muxing HEVC UHD so it doesn't lose frames)?

[mood]

with lastest "w32-nightly-2019-12-14--14-44-59" build give me "tsMuxeR not found!" error and I have the "tsMuxeR.exe" and "tsMuxerGUI.exe" in the same folder.

Anyone can help??

[justdan96]

with lastest "w32-nightly-2019-12-14--14-44-59" build give me "tsMuxeR not found!" error and I have the "tsMuxeR.exe" and "tsMuxerGUI.exe" in the same folder.

I can see you've opened an issue, I'll respond in there.

Also I can see people have found the Bintray location for the nightly builds - that automated workflow is still a work in progress but once I have fully updated the documentation and have it all working correctly I'll post it here!

[BloodyRipper]

Thanks! I'll test it. Does this version also have the other changes made recently (like the correction for muxing HEVC UHD so it doesn't lose frames)?
No, not yet, since this build was made from the master with my "custom PID" patch applied. The UHD patch is still waiting to be merged, though I could prepare a build that includes it if you'd like to test it out.

[jdobbs]

I've noticed that a lot of UHD sources get this error:

- Bitstream exception std::exception. It does not have to be! Please contact application support team for more information.

Does anyone have an idea what causes this? Interestingly, if I take the same streams, mux them into an MKV, and then use the MKV as the source for TSMUXER -- the error goes away.

[Edit] It looks like this is a bug in TSMUXER's scanning of the bitstream. When it gets run through MKVMERGE the Access Unit Delimiter (AUD) is removed. That changes the whole stream. Since the AUD is required for UHD-BD this doesn't represent a solution. When I run my own remuxing routine the output works correctly, so it isn't a problem with the stream itself. Too bad.

Does anyone have the time to take a look at this? I could provide an hevc stream that causes the error (although it is about 20GB).

[jdobbs]

No, not yet, since this build was made from the master with my "custom PID" patch applied. The UHD patch is still waiting to be merged, though I could prepare a build that includes it if you'd like to test it out.Yes, please. For it to be useful for UHD muxing, it would need to have both the track designation for DolbyVision and a working (no "hidden"/"lost" frames) M2TS.

But, if it is too much work, I can just wait for the changes that a5180007 is submitting.

[jdobbs]

The second byte in the .bdmv is : 3-bit zero/reserved, isHDR10+, isSL-HDR2, isDV, isHDR10, isSDR.So after reading this I looked at the value on a group of discs with Dolby Vision. There doesn't seem to be a lot of consistency. Here are some examples of values I found: Alita: 0x16, Aquaman:0x06, Gridelwald: 0x06, Matrix Rev: 0x07, MI: 0x07, Mortal Engines: 0x07

The value in "Alita" makes you think there are at least 4 bits involved. They all had bits 1 & 2 set, so I guess that's what is needed for Dolby Vision -- but it makes me wonder what bits 0 and 3 mean. A guess would be that bit 1 is the indicator for HDR10, since it is there as a baseline with the Dolby -- and bit 2 is the flag for DV.

Does the new BDEDIT explain them?

[Edit] Looked at a couple standard HDR10 discs, and bit 1 (only) is set... so that is consistent with what I guessed above. In BD-Rebuilder I kept the original values for full backups, but used 0x03 for DV on movie-only -- that explains why I got a report that DV wasn't working on movie-only. That's good to know.

[SeeMoreDigital]

With regard to Dolby Vision encoded discs...

Would the fact that some have been encoded using MEL (10-bit minimal enhancement layer) or FEL (12-bit full enhancement layer) make any difference when generating re-muxes?

Disc info: https://forum.blu-ray.com/showthread.php?t=276448


Cheers

[jdobbs]

With regard to Dolby Vision encoded discs...

Would the fact that some have been encoded using MEL (10-bit minimal enhancement layer) or FEL (12-bit full enhancement layer) make any difference when generating re-muxes?

Disc info: https://forum.blu-ray.com/showthread.php?t=276448


CheersGood question... but I don't have an answer. Anyone else?

[a5180007]

Can the 0x51 be modified to 0x21? Most of the reencodes I do are output to BD-25/50. I don't even have a burner that supports 66/100. If not, I can do it after the fact, I guess (as I do now).

It can easily be changed to 0x21, but what gives the most compatibility? If we change to 0x21, wouldn't it limit all plays to BD-25/50 disks ?

When will this patch show up in the nightly releases (if that is the plan)?

justdan96 advised on some conflicts with previous commits (the omission of "overrides"...) from @BloodyRipper. I sent you a PM with my latest build, which includes Dolby Vision. If you can test and report any issues...

Where do I get a copy of the latest BDEDIT? I looked at the BDEDIT thread and it looked like the last edit was many years ago. I use BDEDIT all the time. It's really useful software.

You go on http://bdedit.pel.hu/ , kindly donate 10EUR and ask pelican to send you the link. Largely worth it !!

So after reading this I looked at the value on a group of discs with Dolby Vision. There doesn't seem to be a lot of consistency. Here are some examples of values I found: Alita: 0x16, Aquaman:0x06, Gridelwald: 0x06, Matrix Rev: 0x07, MI: 0x07, Mortal Engines: 0x07

The value in "Alita" makes you think there are at least 4 bits involved. They all had bits 1 & 2 set, so I guess that's what is needed for Dolby Vision -- but it makes me wonder what bits 0 and 3 mean. A guess would be that bit 1 is the indicator for HDR10, since it is there as a baseline with the Dolby -- and bit 2 is the flag for DV.

Does the new BDEDIT explain them?

0x06 = DV + HDR10 : Ok for Aquaman and Grindewald.
0x07 = DV + HDR10 + SDR : Ok for Mortal Engines and MI.
0x16 = HDR10+ : Alita BD is authored incorrectly.

[Edit : see correction below. Alita is also correct HDR10+ + DV + HDR10]

The baseline should be SDR -there are quite a few UHD that are BT709. And yes, BDEdit shows these flags in the index.bdmv extension data -and shows the mpls HDR metadata (color primaries, maxCLL etc).

[FilipeAmadeuO]

Alita UHD 4K has both HDR10+ and Dolby Vision. Probably that’s why it’s 0x16...

[jdobbs]

It can easily be changed to 0x21, but what gives the most compatibility? If we change to 0x21, wouldn't it limit all plays to BD-25/50 disks ? It's probably best to just leave it. I can modify it as needed.

Just a note, though. You may have already thought of this... but if you set this value to 0x51 it will also affect the value to be used in TS_recording_rate in the ClipInfo() table of the CLPI.

[justdan96]

I've noticed that a lot of UHD sources get this error:

- Bitstream exception std::exception. It does not have to be! Please contact application support team for more information.

Does anyone have an idea what causes this? Interestingly, if I take the same streams, mux them into an MKV, and then use the MKV as the source for TSMUXER -- the error goes away.


Sorry I meant to reply on this one earlier - if you can run it through with valgrind and strace we should be able to pinpoint where exactly it is failing and look at a fix. If you raise an issue on GitHub we can track it properly on there.

[a5180007]

0x16 = HDR10+ : Alita BD is authored incorrectly.


My mistake : 0x16 = 10110 = HDR10+, !SL-HDR2, DV, HDR10, !SDR: this is also correct !

[justdan96]

The nightly build documentation is now live: https://github.com/justdan96/tsMuxer/blob/master/README.md

If anyone has issues using these builds please let me know!

[filler56789]

.............

If anyone has issues using these builds please let me know!

Suggestions:

-- add a blank tsMuxeRGUI.ini to the archive, because as everybody already knows, the Windows Registry is evil;

-- please change some stupid default settings, such as "soundEnabled=true";

-- please fix some spelling errors, such as "famaly=Arial";

P.S.:

-- be straight-to-the-point, change the download URL to

bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly#files

-- place the newest builds at the top of the list;

[jdobbs]

Sorry I meant to reply on this one earlier - if you can run it through with valgrind and strace we should be able to pinpoint where exactly it is failing and look at a fix. If you raise an issue on GitHub we can track it properly on there.Sorry for my ignorance. But I'm not that familiar with GitHub, and I don't know how! :o

[stax76]

Sorry for my ignorance. But I'm not that familiar with GitHub, and I don't know how! :o

Github projects have an issue tracker for feature requests, bug reports and any kind of issue, it's very easy to find and use, you just have to register at github and create an issue.

[tebasuna51]

Long time ago I submit a bug report about lpcm and tsMuxeR.
Testing that new open source version I see the same behaviour.
I'm checking the source code now available but still without found the bug.

By the moment I recommend load PCM audio in W64 format.
When load in WAV format tsMuxeR store extra silence at end of stream. WAV format is also limited to 4GB size.
We can use also the special pcm format make by Pcm2Tsmu (https://forum.doom9.org/showthread.php?p=1137225#post1137225), but is more complicated.

Never use tsMuxeR to extract LPCM audio, it add garbage at end and create wav header incorrect (data not multiple of channels*bytedepth).
Use always eac3to to extract LPCM bit-identical to the source uploaded like W64.

[HaDiHo]

Bug report: Film "LUCY German UHD" Playlist 800, ... Media player Oppo203 with Jailbreak, ... No HDR is recognized.
Setting TS-Muxer UHD Iso

TS Muxer Version 19.12.2019

[FilipeAmadeuO]

Bug report: Film "LUCY German UHD" Playlist 800, ... Media player Oppo203 with Jalibreak, ... No HDR is recognized.
Setting TS-Muxer UHD Iso

TS Muxer Version 19.12.2019
I think HDR is still on testing and not integrated on trunk version.

[justdan96]

Long time ago I submit a bug report about lpcm and tsMuxeR.
Testing that new open source version I see the same behaviour.
I'm checking the source code now available but still without found the bug.

Can you please supply the exact steps to reproduce that issue? Preferably using Big Buck Bunny as a source?

[tebasuna51]

Can you please supply the exact steps to reproduce that issue? Preferably using Big Buck Bunny as a source?
Ok.
I have a BBB free source like this:

bbb.m2ts
------------------------------------------------------------------------------
M2TS, 1 video track, 1 audio track, 0:10:34, 30p
1: h264/AVC, 1080p30 (16:9)
2: AC3, 231, 5.1 channels, 320kbps, 48kHz

I decode the AC3 to .wav, .w64 and .pcm (with Pcm2Tsmu):
17/12/2019 14:07 548.407.732 bbb.pcm
17/12/2019 14:05 547.900.544 bbb.w64
17/12/2019 14:06 547.900.484 bbb.wav

The behaviour with .w64 and .pcm is the same, then omit data about .pcm track.

File ........: C:\tmp\tsMuxeR\bbb.wav C:\tmp\tsMuxeR\bbb.w64
Size ........: 547900484 bytes 547900544 bytes

---------------------------------------------- Header Info ------------------------------- Header Info
ChunkID .....: RIFF riff
RiffLength ..: 547900476 547900544
Container ...: WAVE wave
SubchunkID ..: fmt (Length: 40) fmt (Length: 40)
AudioFormat .: 65534 (WAVE_FORMAT_EXTENSIBLE) 65534 (WAVE_FORMAT_EXTENSIBLE)
NumChannels .: 6 6
SampleRate ..: 48000 48000
ByteRate ....: 864000 864000
BlockAlign ..: 18 18
BitsPerSample: 24 24
ValidBitsPS .: 24 24
MaskChannels : 1551 (FL FR FC LF SL SR) 1551 (FL FR FC LF SL SR)
SubType .....: 1 (Integer) 1 (Integer)
SubchunkID ..: data (Length: 547900416) data (Length: 547900416)
Offset data .: 68 128
Duration ....: 634.144 sec., (0h. 10m. 34.144s.) 634.144 sec., (0h. 10m. 34.144s.)

Like you see the raw data are 547900416 bytes ( 3 bytes * 6 channels * 30 438 912 samples) 634,144 sec. at 48 KHz

I use tsMuxeR to replace the AC3 track with the 3 PCM tracks to obtain:
bbb_w.m2ts
------------------------------------------------------------------------------
M2TS, 1 video track, 3 audio tracks, 0:10:34, 30p
1: h264/AVC, 1080p30 (16:9)
2: RAW/PCM, 5.1 channels, 24 bits, 48kHz (from wav)
3: RAW/PCM, 5.1 channels, 24 bits, 48kHz (from w64)
4: RAW/PCM, 5.1 channels, 24 bits, 48kHz (from pcm)

When I extract the tracks with tsMuseR I obtain files like this:

File ........: C:\tmp\tsMuxeR\bbb_w.track_4352.wav C:\tmp\tsMuxeR\bbb_w.track_4353.wav
Size ........: 547901348 bytes (from wav) 547900488 bytes (from w64)

---------------------------------------------- Header Info ------------------------------- Header Info
ChunkID .....: RIFF RIFF
RiffLength ..: 547901340 547900480
Container ...: WAVE WAVE
SubchunkID ..: fmt (Length: 40) fmt (Length: 40)
AudioFormat .: 65534 (WAVE_FORMAT_EXTENSIBLE) 65534 (WAVE_FORMAT_EXTENSIBLE)
NumChannels .: 6 6
SampleRate ..: 48000 48000
ByteRate ....: 864000 864000
BlockAlign ..: 18 18
BitsPerSample: 24 24
ValidBitsPS .: 24 24
MaskChannels : 1551 (FL FR FC LF SL SR) 1551 (FL FR FC LF SL SR)
SubType .....: 1 (Integer) 1 (Integer)
SubchunkID ..: data (Length: 547901280) + 864 (1 ms) ? data (Length: 547900420) +4 ?
Offset data .: 68 68
Duration ....: 634.145 sec., (0h. 10m. 34.145s.) 634.144 sec., (0h. 10m. 34.144s.)

The 864 extra bytes in first track are silence (to 0).
The second track have a invalid data length and the 4 last ms are garbage (see the attached image).

If I use eac3to to extrack the tracks, the first one have also 1 ms extra, but the second track is bit-identical to original bbb.wav

[a5180007]

I think HDR is still on testing and not integrated on trunk version.

In the meantime, you can test HDR10 integration and report on the fork https://github.com/jcdr428/tsMuxer/actions (GitHub account needed).

[justdan96]

@tebasana51: We probably have enough information to get an issue created to track that, thanks a lot for the detailed explanation!

Also the changelog needs an update but UHD HDR10 and HDR10+ has been merged, we've fixed an issue with finding the tsMuxer executable on Windows and fixed a bug with language codes not being handled correctly. Soon we should be merging corrections to TS descriptors, automatic V3 for HEVC Blu-Ray and allowing explicit PIDs to be specified via the meta file.

[outgoing]

Great work, can't wait for a Gui version. Thank you very much for all your time.

[SeeMoreDigital]

I don't know about anybody else but currently if you want to create back-ups of UHD discs with Dolby Vision, the only way is by using MakeMKV GUI in 'full disc' mode... Which creates huge files!

So with regard to future versions of TSmuxer GUI, the 'holy grail' for me would be the ability to create 'movie only' re-muxes with Dolby Vision containing only the audio and subtitle streams I require.

Cheers all

[gonca]

ability to create 'movie only' re-muxes with Dolby Vision containing only the audio and subtitle streams I require.
Apparently BD_RB might have something to help
With the help of a5180007 jdobbs uses a patched version of tsMuxer to do that

[a5180007]

ability to create 'movie only' re-muxes with Dolby Vision containing only the audio and subtitle streams I require.

The HDR10 patch has been merged to the master, so you should already be able to do this with the latest build https://bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly#files

There are still many bugs / BD non-compliance with the TS muxer, which will take weeks to get rid of.

[SeeMoreDigital]

The HDR10 patch has been merged to the master, so you should already be able to do this with the latest build https://bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly#files

There are still many bugs / BD non-compliance with the TS muxer, which will take weeks to get rid of.Indeed... Today I have tried the 'w64-nightly-2019-12-30--01-10-40.zip' build to create an 'UHD Blu-ray folder' re-mux of '2001 A Space Odyssey' with Dolby Vision (at 72.4GB).

Sadly when I try to play the re-mux with my OPPO UDP-203, all I get is a black screen with the player saying 'Loading....'. Which eventually locks up the player too.

On the plus side.... This is actually an improvement over previous builds ;)

[a5180007]

Sadly when I try to play the re-mux with my OPPO UDP-203, all I get is a black screen with the player saying 'Loading....'. Which eventually locks up the player too.

@SeeMoreDigital No reason for the player not to read at least the first video track. Are you sure your reader is compatible with the BD-R XL ? Do you have the same issue with a smaller DV remux burnt on a BD-50 (Edit: or with file on two layers i.e. < 66 GB) ?

[SeeMoreDigital]

@SeeMoreDigital No reason for the player not to read at least the first video track. Are you sure your reader is compatible with the BD-R XL ? Do you have the same issue with a smaller DV remux burnt on a BD-50 (Edit: or with file on two layers i.e. < 66 GB) ?To clarify... I'm not creating disc's, I'm creating 'UHD folder' back-ups, that can be read via a USB connected HDD.

The OPPO UDP-203/205 players are able to read 'full disc' UHD folder back-ups just fine. But currently not re-muxed 'movie only' UHD folder back-ups.

[justdan96]

I don't suppose you have logs from the player we could try to analyse?

[SeeMoreDigital]

I don't suppose you have logs from the player we could try to analyse?No... Indeed I'm not aware of any Blu-ray disc player being able to generate logs.

[ocean]

Hi, first of all thank you for the work done, trying with the latest version "w64-nightly-2019-12-30--01-10-40", on oppo 203 and PowerDVD, the problem is in the main file * .mpls after the mux, in the presence of Dolby Vision as the second track, instructions are missing from the main mpls.
Inserting after the mux, the original main mpls file of the film, renaming it, trying again on oppo 203, everything works with Dolby Vision.

I leave you 2 files, original and after the mux, in json format, to check the differences:
http://www.mediafire.com/file/8jh1gr80q6edsb8/Original.rar/file

[FilipeAmadeuO]

Hi, first of all thank you for the work done, trying with the latest version "w64-nightly-2019-12-30--01-10-40", on oppo 203 and PowerDVD, the problem is in the main file * .mpls after the mux, in the presence of Dolby Vision as the second track, instructions are missing from the main mpls.
Inserting after the mux, the original main mpls file of the film, renaming it, trying again on oppo 203, everything works with Dolby Vision.

I leave you 2 files, original and after the mux, in json format, to check the differences:
http://www.mediafire.com/file/8jh1gr80q6edsb8/Original.rar/file
I think there is no Dolby Vision support yet on tsmuxer.

[tymoxa]

The OPPO get stuck on DV UHD remux (when using latest github tsmuxer) because there is mention about DV substream in STN table, but no actual subpath in playlist.
In terms of BDtools next part should be added to playlist to start works on OPPO:
"SubPath": [
{
"reserved01": 0,
"SubPath_type": 10,
"reserved02": 0,
"is_repeat_SubPath": 0,
"reserved03": 0,
"SubPlayItem": [
{
"Clip_Information_file_name": "00000",
"Clip_codec_identifier": "M2TS",
"ref_to_STC_id": 0,
"reserved01": 0,
"is_multi_Clip_entries": 0,
"sp_connection_condition": 1,
"SubPlayItem_IN_time": 27000000,
"SubPlayItem_OUT_time": 32384745,
"sync_PlayItem_id": 0,
"sync_start_PTS_of_PlayItem": 0
}
]
}
]
SubPlayItem_IN_time|SubPlayItem_OUT_time should be the same as in main Playitem.
But unfortunately, bdtools cannot correctly assemble it's json back to mpls, it adds subpath, but "forgets" about STN. The only tool for now i'm aware of which can do it correctly - latest bdedit.

[ocean]

Hi tymoxa, happy new year to everyone, exactly, and this also blocks the reading of the first video track on oppo, in the presence of movie with Dolby Vision.

[a5180007]

Happy new year to you all. Yes the HDR10 and HDR10+ patch has been pushed, but integration of DV was not finalized.

@ocean @jdobbs @tymoxa @FilipeAmadeuO @SeeMoreDigital could you please test and report on my latest build https://github.com/jcdr428/tsMuxer/actions which includes corrections for DV SubPath / UOFlags / AUD at start of PES / Arrival TimeStamps. If conclusive I will push the patch to @justdan96 master.

Also in case 4K is detected, setting is 66-100 GB Disk / Transfer Rate 13.625 MB/s, otherwise it remains as 25-50 GB Disk / TR 6 MB/s.
There might still be a BD non-compliance with the ClipInf EP Fine Entries "I_end_position_offset", maybe someone can clarify the connexion with the TS_Recording_Rate.

[SeeMoreDigital]

@ocean @jdobbs @tymoxa @FilipeAmadeuO @SeeMoreDigital could you please test and report on my latest build https://github.com/jcdr428/tsMuxer/actions which includes corrections for DV SubPath / UOFlags / AUD at start of PES / Arrival TimeStamps.Hello...

Sadly the the link reports "page not found"...

[FilipeAmadeuO]

Hello...

Sadly the the link reports "page not found"...

You need to register...

[a5180007]

So this is the way tsMuxer currently calculates the EP fine entries I_end (=endCode), for a TS_Recording_Rate of 6000000:


if (indexData.m_frameLen < 131072)
endCode = 1;
else if (indexData.m_frameLen < 262144)
endCode = 2;
else if (indexData.m_frameLen < 393216)
endCode = 3;
else if (indexData.m_frameLen < 589824)
endCode = 4;
else if (indexData.m_frameLen < 917504)
endCode = 5;
else if (indexData.m_frameLen < 1310720)
endCode = 6;
else
endCode = 7;


Anybody would know the table of frameLen to use for a TS_Recording_Rate above 6000000 ?

[filler56789]

You need to register...

That's just one of the problems with the current tsmuxer githubbers...

they happily assume everyone has /must have /wants to have a GitHub account.

[ocean]

Happy new year to you all. Yes the HDR10 and HDR10+ patch has been pushed, but integration of DV was not finalized.

@ocean @jdobbs @tymoxa @FilipeAmadeuO @SeeMoreDigital could you please test and report on my latest build https://github.com/jcdr428/tsMuxer/actions which includes corrections for DV SubPath / UOFlags / AUD at start of PES / Arrival TimeStamps. If conclusive I will push the patch to @justdan96 master..


Yes a5180007, tested on oppo, now Dolby Vision is detected and the movie starts normally.

[SeeMoreDigital]

Yes a5180007, tested on oppo, now Dolby Vision is detected and the movie starts normally.Hmmm...

I would like to test this too but I don't have/need a GitHub account :(

[FilipeAmadeuO]

Yes a5180007, tested on oppo, now Dolby Vision is detected and the movie starts normally.
Same here

[SeeMoreDigital]

Oh wow,

Thanks for the PM @ocean, I've just tested a5180007's Dolby Vision friendly build and it works "a treat" with the first two test files I've tried :)

I'm going to try some more obscure Dolby Vision test files......

[SeeMoreDigital]

@ocean @jdobbs @tymoxa @FilipeAmadeuO @SeeMoreDigital could you please test and report on my latest build https://github.com/jcdr428/tsMuxer/actions which includes corrections for DV SubPath / UOFlags / AUD at start of PES / Arrival TimeStamps. If conclusive I will push the patch to @justdan96 master.
Many thanks.... Dolby Vision re-muxing works. Which is great news :D

Try as I might though, I've not been able to create re-muxes with chapters.


Cheers

[filler56789]

Many thanks.... Dolby Vision re-muxing works. Which is great news :D

Good news indeed :)

Let's hope justdan96 will release the first «official» binaries of the new tsMuxeR before 2038 A.D...
If he is waiting for the source-code to be absolutely bug-free and future-proof, probably he doesn't know how the real development of real software works :sly:

[ocean]

Let's hope justdan96 will release the first «official» binaries of the new tsMuxeR before 2038 A.D...


Hi filler56789 :)

@SeeMoreDigital

Have you tried checking the list under Blu-ray, this is after remux:

https://i.ibb.co/SVPxpnC/Immagine.png (https://ibb.co/SVPxpnC)

[SeeMoreDigital]

@SeeMoreDigital

Have you tried checking the list under Blu-ray, this is after remux:

https://i.ibb.co/SVPxpnC/Immagine.png (https://ibb.co/SVPxpnC)Thanks...

I've just checked and can confirm that the 'chapter import' option functions correctly when selecting the 'Blu-ray ISO' or 'Blu-ray Folder' output options. But it does not function correctly when selecting the 'UHD Blu-ray ISO' or 'UHD Blu-ray Folder' output options.

EDIT: I can now also confirm that the 'Blu-ray Folder' output Dolby Vision re-muxes (with chapters) work perfectly with my OPPO UDP-203. This is going to please a lot of people.


Very nice work and many thanks to all concerned...

[a5180007]

it does not function correctly when selecting the 'UHD Blu-ray ISO' or 'UHD Blu-ray Folder' output options.

@SeeMoreDigital I can't help, chapter function works well on my Windows 10 in UHD.
Anybody else having the same symptom (chapters not working with UHD Bluray option) ?

[gonca]

Just did UHD folder to UHD folder
Keeping video, one audio and one pgs
Chapters are visible in Blu Ray tab
Result has only one chapter
Media info attached

General
Complete name : F:\New folder\BDMV\PLAYLIST\00000.mpls
Format : Blu-ray Playlist
File size : 246 Bytes
Duration : 2 h 3 min
Overall bit rate mode : Variable
Overall bit rate : 0 b/s

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 2 h 3 min
Bit rate : 52.6 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.264
Stream size : 45.2 GiB
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
format_identifier : HDMV
Source : 00000.m2ts / 00000.m2ts

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : AC-3 MLP FBA 16-ch
Format/Info : Audio Coding 3 + Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Muxing mode : Stream extension
Codec ID : 131
Duration : 2 h 3 min
Bit rate mode : Variable
Bit rate : 640 kb/s
Maximum bit rate : 6 165 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : 4 ms
Stream size : 563 MiB
Language : English
Service kind : Complete Main
Number of dynamic objects : 13
Bed channel count : 1
Bed channel count : 1 channel
Bed channel configuration : LFE
bsid : 6
dialnorm : -31
dialnorm : -31 dB
compr : 6.02
compr : 6.02 dB
dynrng : 6.02
dynrng : 6.02 dB
acmod : 7
lfeon : 1
dialnorm_Average : -31
dialnorm_Average : -31 dB
dialnorm_Minimum : -31
dialnorm_Minimum : -31 dB
dialnorm_Maximum : -31
dialnorm_Maximum : -31 dB
dialnorm_Count : 1150
compr_Average : 4.94
compr_Average : 4.94 dB
compr_Minimum : 0.53
compr_Minimum : 0.53 dB
compr_Maximum : 6.02
compr_Maximum : 6.02 dB
compr_Count : 876
dynrng_Average : 4.18
dynrng_Average : 4.18 dB
dynrng_Minimum : 0.00
dynrng_Minimum : 0.00 dB
dynrng_Maximum : 6.02
dynrng_Maximum : 6.02 dB
dynrng_Count : 1150
format_identifier : AC-3
Source : 00000.m2ts / 00000.m2ts

Text
ID : 4608 (0x1200)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144
Duration : 2 h 3 min
Language : English
Source : 00000.m2ts / 00000.m2ts

Menu
00:00:00.000 : Chapter 1

[HaDiHo]

@SeeMoreDigital I can't help, chapter function works well on my Windows 10 in UHD.
Anybody else having the same symptom (chapters not working with UHD Bluray option) ?

MKV to UHD Iso ... I Have no chapters

[ocean]

Yes, the problem in folder transport, in that ISO should create them.

Meta file:

UHD BLU-Ray ISO

MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray-v3 --vbr --custom-chapters=00:00:00.000;00:06:14.290;00:16:42.208;00:21:09.183;00:31:16.708;00:35:25.831;00:45:57.336;00:53:43.260;01:00:52.73
;01:08:39.907;01:14:24.083;01:24:15.132;01:28:36.519;01:36:36.582;01:46:36.390;01:51:04.783;01:58:59.340 --vbv-len=500 --start-time=524280

UHD BLU-Ray folder

MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray-v3 --vbr --vbv-len=500 --start-time=524280

[gonca]

Yep.
When the output is ISO the chapters are there

[a5180007]

So the chapter problem was in the GUI, which is why I couldn't see it as I work only with the CLI.
Easy fix, I've pushed the commit to @justdan96 tsMuxer, pending merge.
Edit: in the meantime, you can use the non-UHD Bluray Folder option, as it automatically switches to UHD/V3 when HEVC is detected.

[SeeMoreDigital]

So the chapter problem was in the GUI, which is why I couldn't see it as I work only with the CLI.
Easy fix, I've pushed the commit to @justdan96 tsMuxer, pending merge.Thanks again. I've re-muxed just about all of my UHD discs encoded with Dolby Vision and managed to save around 150GB of disk space so far...

Out of interest. Is this suggestion by @filler56789 (https://forum.doom9.org/showthread.php?p=1883550#post1883550) possible to implement?

Cheers all

[Michi]

I tested several UHD-DV remuxes on my Sony X800M2 and the Sony crashed on all DV remuxes. UHD remuxes without DV plays the Sony without problems.

[a5180007]

I tested several UHD-DV remuxes on my Sony X800M2 and the Sony crashed on all DV remuxes. UHD remuxes without DV plays the Sony without problems.

@Michi DV patch has not been pushed to @justdan96 master, waiting for two previous commits to be merged.
Could you please confirm that you've tested the version from my fork https://github.com/jcdr428/tsMuxer/actions -not the versions from bintray or https://github.com/justdan96/tsMuxer/actions.

[Michi]

@Michi DV patch has not been pushed to @justdan96 master, waiting for two previous commits to be merged.
Could you please confirm that you've tested the version from my fork https://github.com/jcdr428/tsMuxer/actions -not the versions from bintray or https://github.com/justdan96/tsMuxer/actions.

I used the version 2.6.15 2020-01-02 Nightly from videohelp:

https://bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly/_latestVersion#files

Edit:
Just I see a newer version on this link

[a5180007]

@Michi again: the bintray version does not currenty include the DV patch. Only my Github fork does.

I've re-muxed just about all of my UHD discs encoded with Dolby Vision and managed to save around 150GB of disk space so far.

For PC use, current version should be ok. Please don't forget there are still some bugs (eg incorrect CPI EP table) that might compromise the reading on a Bluray player.

Out of interest. Is this suggestion by @filler56789 (https://forum.doom9.org/showthread.php?p=1883550#post1883550) possible to implement?

@SeeMoreDigital I thought having fixed this weeks ago. Have you tried to mux TrueHD+AC3 core with latest version ?

[SeeMoreDigital]

I tested several UHD-DV remuxes on my Sony X800M2 and the Sony crashed on all DV remuxes. UHD remuxes without DV plays the Sony without problems.How are you playing these Dolby Vision UHD re-muxes. Are you burning discs?

[Michi]

How are you playing these Dolby Vision UHD re-muxes. Are you burning discs?

I burn the remuxes on BD-RE 50

[SeeMoreDigital]

@SeeMoreDigital I thought having fixed this weeks ago. Have you tried to mux TrueHD+AC3 core with latest version ?To confirm...

THD with AC3 core works fine. This is what I see when I try to import a Dolby TrueHD elementary stream without core, which is what @filler56789 was asking about: -

https://i.ibb.co/g7qBHkj/sadly-yes.png


Cheers

[outgoing]

With the last build (nightly-2020-01-02--01-10-53) in some tests the bluray remux have the correct stn table, which was not the case with the penultimate build (nightly-2020-01-01--01-10-57). On the other hand, without being exhaustive, when I make a negative delay for syn for more than a 1000 ms (pe: -1234) in DTS-HDMA audios the final remux does not play well in the players. If I apply this delay with the eac3to it makes valid remux.

[SeeMoreDigital]

I've just tested '2020-01-04--01-10-41' with some Dolby Vision sources and sadly it's not able to create muxes that can be played with my OPPO :(

[Michi]

DV remuxes with the github version plays my Sony X800M2 without problems. I used Bluray-Folder for muxing and I have chapters.

[Bandits]

Request if someone can post a copy of a Meta file output from a UHD disc with DV, all tracks selected, chapters present, and output set to Blu-Ray folder.

I do not own any UHD disc's but I would like to see the new Meta file settings for UHD with DV.

[xledentaldj]

Fury UHD BDMV meta from MacOS
jan.5th nightly build:
https://mega.nz/#!QYpUQKzT!l2AcTzu30yNsTJ2gzPq5uAcivwUJkjur-4fkOZML39M

Ive noticed a my MacOS 10.13.6 tsmuxer GUI bug when trying to save as UHD BDMV folder it tries to save to a folder
location as a .ts file. Also if you use UHD BD iso
you get no option to create Volume Lable of movie
iso.

[Bandits]

Fury UHD BDMV meta from MacOS
jan.5th nightly build:
https://mega.nz/#!QYpUQKzT!l2AcTzu30yNsTJ2gzPq5uAcivwUJkjur-4fkOZML39M

Ive noticed a my MacOS 10.13.6 tsmuxer GUI bug when trying to save as UHD BDMV folder it tries to save to a folder
location as a .ts file. Also if you use UHD BD iso
you get no option to create Volume Lable of movie
iso.

That meta file doesn't seem to show Dolby Vision. Also the output options and video type seem strange for a UHD movie.

[maxibon]

Hi
I´ve tested latest build 2020-01-05--01-10-23 trying to replace audio and subtitles in a UHD Bluray folder but with no succes.
Audio is fine but subtitles disappear, chapters remain
Tested on Oppo 203

[HaDiHo]

Mkv to UHDIso (Player 0ppo203) now and then pixel errors in the film when changing chapters

https://s19.directupload.net/images/200105/8nmjgsrk.jpg

[SeeMoreDigital]

I've just tested the '2020-01-05--01-10-23 w64-nightly' build with some Dolby Vision sources and it's not able to create muxes that can be played with my OPPO...

[xledentaldj]

That meta file doesn't seem to show Dolby Vision. Also the output options and video type seem strange for a UHD movie.

Oops, I though Fury had DV, My Halloween does but once I add
the playlist, MacOS TsMuxer build spits up an error:

Assertion failed: (num<=Int_Bit), Function skipbits, file /_w/tsmuxer/tsmuxer/tsmuxerbitstream.h, line 119.

[tymoxa]

Mkv to UHDIso (Player 0ppo203) now and then pixel errors in the film when changing chapters

That's because NAL AUD was stripped when movie was muxed into mkv. Presence of NAL AUD is mandatory in UHD-BD. mkv>udh-bd is always bad idea without proper reconstructing nal-aud.

[SeeMoreDigital]

Mkv to UHDIso (Player 0ppo203) now and then pixel errors in the film when changing chapters
Out of interest, what application was used to create the .MKV file in the first place?

[a5180007]

Mkv to UHDIso (Player 0ppo203) now and then pixel errors in the film when changing chapters

@HaDiHo The hevc stream must repeat the AUD and SEI nals between each frame, plus VPS/SPS/PPS before each I-frame (which must be at the start of each chapter). If your stream has been mkv-muxed (or re-encoded) then it possibly does not follow these specs.

Edit: In the future, tsMuxer might include automatic inclusion of AUD nal if absent.

EDIT 2 : Chapters now work with UHD Bluray folder option in latest bintray build.

[sandrino3867]

I try to add srt. subtitle to UHD movie and i got this error: video-width, video-height and fps parameters MUST be provided for SRT tracks. TsMuxer w64-nightly-2020-01-05--01-10-23 can add subtitle to UHD Movie 4K and how ? Sorry for my bad english.

[a5180007]

I try to add srt. subtitle to UHD movie and i got this error: video-width, video-height and fps parameters MUST be provided for SRT tracks. TsMuxer w64-nightly-2020-01-05--01-10-23 can add subtitle to UHD Movie 4K and how ? Sorry for my bad english.

@sandrino3867 please cut the first 20MB of the m2ts with an hex editor (e.g. HxD), zip it with the srt, upload it somewhere and send me the link via PM.

[MrVideo]

Minor fixes for GUI:

1) The About doesn't show that the program has support for the HEVC codec.

2) Cannot correctly set the fps for 720p/59.94 HEVC elementary stream. Since the frame rate can't be found in a HEVC stream, the frame rate must be forced, but there is no option for 60000/1001.

[MrVideo]

How about adding a link in the first post to the bintray location of the nightly builds?

[Emulgator]

Just throwing this in here unrelated (not in time, but better to be not overlooked, since it was in a different thread).
Has probably been implemented already successfully, I guess...
It is pelican9's finding about the location of some DV relevant parameters:
https://forum.doom9.org/showthread.php?p=1889392#post1889392

[HaDiHo]

@HaDiHo The hevc stream must repeat the AUD and SEI nals between each frame, plus VPS/SPS/PPS before each I-frame (which must be at the start of each chapter). If your stream has been mkv-muxed (or re-encoded) then it possibly does not follow t.........

the pixel errors at the chapter ends are fixed ...
Thank you very much:thanks::)

[justdan96]

How about adding a link in the first post to the bintray location of the nightly builds?

That's a good idea, I'll get on that!

[Richard1485]

To whoever made the nightly build for Linux an AppImage and got the GUI working, massive thanks! It's great to be able to use tsMuxeR without installing 32-bit architecture and having to jump through various other hoops to get it working.

[SeeMoreDigital]

Just throwing this in here unrelated (not in time, but better to be not overlooked, since it was in a different thread).
Has probably been implemented already successfully, I guess...
It is pelican9's finding about the location of some DV relevant parameters:
https://forum.doom9.org/showthread.php?p=1889392#post1889392
Just-so-people know....

This version of TSmuxer GUI (http://www.mediafire.com/file/l4h3cky54u0v3t9/TsmuxeR_Dolby_Vision.rar/file) that ocean obtained from GitHub (on Thu 02 Jan 2020) works fine with Dolby Vision 4K UHD Blu-ray sources ;)

[a5180007]

Has probably been implemented already successfully, I guess... It is pelican9's finding about the location of some DV relevant parameters[/URL]

Yes DV has been implemented (successfully hopefully), many thanks to Pel and his BDEdit.
And a big thank also to tymoxa for his help in verifying the BD outputs.

I still need some help to work on the TS buffer management, as TsMuxer simply divides the PCR gap between two frames by the corresponding number of AV packets to calculate the Arrival Time Stamps.
I don't know if @drmpeg is still around...

[turntoyou]

I dont know what you are sometimes talking about, but a big big thank you all here working hard on tsmuxer to get it running with DV

:thanks:

[FilipeAmadeuO]

Dolby Vision integrated today on nightly versions.

[SeeMoreDigital]

Dolby Vision integrated today on nightly versions.Nice one :)

[jdobbs]

Yes DV has been implemented (successfully hopefully), many thanks to Pel and his BDEdit.
And a big thank also to tymoxa for his help in verifying the BD outputs.

I still need some help to work on the TS buffer management, as TsMuxer simply divides the PCR gap between two frames by the corresponding number of AV packets to calculate the Arrival Time Stamps.
I don't know if @drmpeg is still around...Have you looked at the source code for TSREMUX (https://github.com/antiochus/tsremux) to see how it does it?

[HaDiHo]

Dolby Vision integrated today on nightly versions.
MKV to ISO
Dolby Vision > Yes
Dolby Atmos > No

[a5180007]

MKV to ISO
Dolby Vision > Yes
Dolby Atmos > No

@HaDiHo this is because mkvtoolnix separates the thd and the ac3 streams. I doubt that TSmuxing standalone thd streams will be implemented any time soon.

[filler56789]

I doubt that TSmuxing standalone thd streams will be implemented any time soon.

Can't you (basically) just copy the "recipe" from ffmpeg? :confused:

[SeeMoreDigital]

@HaDiHo this is because mkvtoolnix separates the thd and the ac3 streams. I doubt that TSmuxing standalone thd streams will be implemented any time soon.Can't you (basically) just copy the "recipe" from ffmpeg? :confused:Agreed...

[jdobbs]

Here's a little information (https://forum.doom9.org/showthread.php?p=1895093#post1895093) I found interesting for those who like to play and push the envelope a little. The new TSMUXER versions make it possible. Warning, though, I've only tried it on a few sources and a single UHD-BD player -- so mileage may vary.

[zeropc]

Feedback from the nightly build nightly-2020-01-07--01-09-43

- You can't create a folder from tsMuxer
- macOS version doesn't work. When adding a file/playlist it shows an error message
https://imgur.com/iU1Km6i.png

- Feature Request: Add option to make a specific audio the default track and a specific subtitle track a forced track

[MrVideo]

- Feature Request: Add option to make a specific audio the default track
Can't you accomplish that by just changing the order within the list? Make it the first audio track after the video track.

[justdan96]

@zeropc: I can't see the screenshot but if you can create an Issue over at GitHub we can take a look.

I need to go through this thread and transfer over all the reported issues to GitHub at some point but if people can report via GitHub it would help me out!

[zeropc]

Can't you accomplish that by just changing the order within the list? Make it the first audio track after the video track.

Audio tracks yes, but not for forced subtitles

@zeropc: I can't see the screenshot but if you can create an Issue over at GitHub we can take a look.


Should work now

[a5180007]

Can't you (basically) just copy the "recipe" from ffmpeg? :confused:

Good idea, you could ask somebody from ffmpeg to do it.

As an alternative, Madshi gave the eac3to solution to interweave the TrueHD stream with its low-bitrate AC3 (eg 64k if you don't want to use it) counterpart in 2008:
http://forum.doom9.net/showthread.php?p=1177600#post1177600

[SeeMoreDigital]

I have a question regarding an .m2ts streams overhead.

Since the launch of the Blu-ray disc format, way back in mid 2006, has anybody found a way to reduce an .m2ts streams overhead for non disc based applications. Or is its design set in stone?


Cheers

[a5180007]

Since the launch of the Blu-ray disc format, way back in mid 2006, has anybody found a way to reduce an .m2ts streams overhead for non disc based applications. Or is its design set in stone?

Yes it is set in stone: at a minimum, on each 192-byte packet there is 8 to 10 bytes of time stamp/header. Plus 3 to 4 additional packets (PMT/PAT/PCR/NIT) at least every 100 ms. Plus sync to sector size, etc.

The main purpose of a transport stream (aimed at broadcasting) is to be error resilient, so there are tons of flags and timestamps along the stream.

[SeeMoreDigital]

The main purpose of a transport stream (aimed at broadcasting) is to be error resilient, so there are tons of flags and timestamps along the stream.Yep... I can understand why broadcast TV requires to very error resistant but I find it weird that the Blu-ray disc format and the more recent AVCHD camcorder format requires the same level of resilience...

[filler56789]

Yep... I can understand why broadcast TV requires to very error resistant but I find it weird that the Blu-ray disc format and the more recent AVCHD camcorder format requires the same level of resilience...

Probably the transport stream format was chosen not because of its "resilience" but because it can contain more than one program
(read: the secondary (P.I.P.) video feature).

[a5180007]

In the new nightly 09-01, the V3 option has been put in the Blu-ray tab option, as tsMuxer now switches automatically to V3 for HEVC. The manual V3 option can still be needed e.g. to mux AVC streams, to include the m2ts along with other V3 m2ts on a disk.

[tymoxa]

- Feature Request: Add option to make a specific audio the default track and a specific subtitle track a forced track

Actually, you can do it yourself in any HEX editor. Open MovieObject.bdmv, find 42 82 00 00 00 00 00 00 00 00 00 0A and insert next digits BEFORE 42 82 00 00 00 00 00 00 00 00 00 0A:

51 C0 00 01 80 01 C0 01 00 00 00 00
where:
1 - number of default audio track
1 - number of default subtitle track
C - all elements in selected PGS are shown. If you need to show only elements that marked with Forced="True" flag - you need to use 8 instead of C

Additionally it is needed to replace 03 80 00 00 05 for 03 80 00 00 06

But i agree that it would be more convinient to select needed default and forced tracks from gui or cli.

[outgoing]

Actually, you can do it yourself in any HEX editor. Open MovieObject.bdmv, find 42 82 00 00 00 00 00 00 00 00 00 0A and insert next digits BEFORE 42 82 00 00 00 00 00 00 00 00 00 0A:

51 C0 00 01 80 01 C0 01 00 00 00 00
where:
1 - number of default audio track
1 - number of default subtitle track
C - all elements in selected PGS are shown. If you need to show only elements that marked with Forced="True" flag - you need to use 8 instead of C

Additionally it is needed to replace 03 80 00 00 05 for 03 80 00 00 06

But i agree that it would be more convinient to select needed default and forced tracks from gui or cli.

Hi tymoxa, what you're explaining is also valid if it's a bluray java?

[tymoxa]

Hi tymoxa, what you're explaining is also valid if it's a bluray java?
No. It's only for remuxes made by tsmuxer.

[outgoing]

No. It's only for remuxes made by tsmuxer.

I thought maybe I could put it all together to make a menu bluray and keep that condition with the audio/subtitle. Thank you for the clarification.

[a5180007]

But i agree that it would be more convinient to select needed default and forced tracks from gui or cli.

Doesn't seem too difficult. I've put it as an enhancement issue on Github for the record.

Edit: the additional command can also be easily added on BDEdit.

[ocean]

- Feature Request: Add option to make a specific audio the default track and a specific subtitle track a forced track


Hi, if you want a simple thing, both ISO and folder there is the Rotty program:

http://www.mediafire.com/file/7ne0c2ts4q07l5i/sub_forced.rar/file

Edit: I' sorry, I read that you are using the Apple system.

[tymoxa]

Edit: the additional command can also be easily added on BDEdit.
Sure, but not for BD3D.iso

[imhh11]

many thanks for the update. DV remux works great on my Sony x700.

but I'm having an issue with srt subtitles which was fine using the old tsmuxer.


https://extraimage.net/images/2020/01/10/c3dc5bf065340a3468e152cb527ffdc1.md.png (https://extraimage.net/image/y2iA)


https://extraimage.net/images/2020/01/10/c38e13e9546b475f6327e13c2afe3d08.md.png (https://extraimage.net/image/y2iW)


https://extraimage.net/images/2020/01/10/d2c523b74b833cf68f358275c90264ba.md.png (https://extraimage.net/image/y20I)

Hi, if you want a simple thing, both ISO and folder there is the Rotty program:

http://www.mediafire.com/file/7ne0c2ts4q07l5i/sub_forced.rar/file

Edit: I' sorry, I read that you are using the Apple system.
thanks but that tool doesnt seem to work with uhd-bd iso

[justdan96]

many thanks for the update. DV remux works great on my Sony x700.

but I'm having an issue with srt subtitles which was fine using the old tsmuxer.

It looks like an issue someone raised on GitHub - is your locale set to one which uses commas for decimals?

[imhh11]

It looks like an issue someone raised on GitHub - is your locale set to one which uses commas for decimals?

yep commas. changed that and now its working properly. thank you

https://extraimage.net/images/2020/01/11/aa0accd4b0a98f07e6c408875771166e.md.png (https://extraimage.net/image/yNQF)

[zeropc]

Was the UHD Folder/ISO removed on purpose or better say merged with Blu-ray Folder/ISO on the nightly build from w64-nightly-2020-01-11--01-10-45?

[BloodyRipper]

Was the UHD Folder/ISO removed on purpose or better say merged with Blu-ray Folder/ISO on the nightly build from w64-nightly-2020-01-11--01-10-45?
Blu-ray version is now automatically switched to V3 in case HEVC is detected, so the additional combo box was unnecessary. Perhaps this pull request (https://github.com/justdan96/tsMuxer/pull/120) gives you some more information.

[zeropc]

Blu-ray version is now automatically switched to V3 in case HEVC is detected, so the additional combo box was unnecessary. Perhaps this pull request (https://github.com/justdan96/tsMuxer/pull/120) gives you some more information.

So when I remux a UHD I need to check V3 under Blu-ray pane?

[filler56789]

Giving a try to the latest sub-pseudo-"release", I found:

1) the archive still doesn't include a blank .INI file; as I said before, the current developer of Roman's tsMuxeR doesn't want to know very well how Windows works and what the Windows users expect;

2) the typos weren't fixed and the stupid default settings weren't changed;

3) the "About" tab doesn't list MPEG-1 audio as a supported audio format;

4) apparently the UPX compression doesn't harm the .EXEs so I don't know why justdan96 doesn't use it. Probably he sent me to his IgnoreList because I am not sufficiently "civil" :rolleyes: for his pusillanimous taste...

[SeeMoreDigital]

Was the UHD Folder/ISO removed on purpose or better say merged with Blu-ray Folder/ISO on the nightly build from w64-nightly-2020-01-11--01-10-45Blu-ray version is now automatically switched to V3 in case HEVC is detected, so the additional combo box was unnecessary. Perhaps this pull request (https://github.com/justdan96/tsMuxer/pull/120) gives you some more information.Following on from this....

I've never really understood the logic behind the 'AVCHD folder' output option, as it's never been capable of generating muxes that are compatible with the AVCHD camcorder specification (which is supposed to place all content within a 'PRIVATE' folder). Does anybody actually use this output option? Is there any point keeping it?

That being said... As I'm an OPPO player owner, it would be handy to have an 'OPPO Player' output option that created an AVCHD folder for you ;)


Cheers

[Yordan5]

Giving a try to the latest sub-pseudo-"release", I found:

1) the archive still doesn't include a blank .INI file; as I said before, the current developer of Roman's tsMuxeR doesn't want to know very well how Windows works and what the Windows users expect;

2) the typos weren't fixed and the stupid default settings weren't changed;

3) the "About" tab doesn't list MPEG-1 audio as a supported audio format;

4) apparently the UPX compression doesn't harm the .EXEs so I don't know why justdan96 doesn't use it. Probably he sent me to his IgnoreList because I am not sufficiently "civil" :rolleyes: for his pusillanimous taste...

After reading your post I will also put you on my "IgnoreList".
Complete lack of appreciation for the time and effort the developer puts in so we can all use this software free of charge.

[DaveO88]

what's the problem here (new version 12.1.2020)

[filler56789]

After reading your post I will also put you on my "IgnoreList".

I don't care.

Complete lack of appreciation for the time and effort the developer puts in so we can all use this software free of charge.

That's just your stupid opinion of course. Evidently you haven't read carefully this entire thread nor followed my posts in his GitHub tsMuxeR directory.

[imhh11]

Following on from this....

I've never really understood the logic behind the 'AVCHD folder' output option, as it's never been capable of generating muxes that are compatible with the AVCHD camcorder specification (which is supposed to place all content within a 'PRIVATE' folder). Does anybody actually use this output option? Is there any point keeping it?

That being said... As I'm an OPPO player owner, it would be handy to have an 'OPPO Player' output option that created an AVCHD folder for you ;)


Cheers

I use it for HD content on DVD media.

[SeeMoreDigital]

I use it for HD content on DVD media.Wow okay...

I must admit I haven't tried creating AVCHD DVD's... I've only tried creating AVCHD content for SD cards.

If the current output option works okay for disc based media then perhaps the output name could be changed to reflect this.

That being said... If you're burning AVCHD DVD's, wouldn't an 'AVCHD ISO' option be preferable?

[staina]

Greetings, would be possible to into 1st post insert information, whether is already supported HDR10, HDR10+, Dolby Vision and next for UHD Bluray, eventually whether with to introduced functions yet works.

Release coming - out almost every day, but nowhere information whether already work above - cited function and it is possible perform remux UHD Bluray. Eventually issue option 2.6.16 which already this supports.

Thank for answer Staina

[staina]

Blu-ray version is now automatically switched to V3 in case HEVC is detected, so the additional combo box was unnecessary. Perhaps this pull request (https://github.com/justdan96/tsMuxer/pull/120) gives you some more information.

No automatically switched to V3 in case HEVC. Tested to Fifty Shades of Grey and Blade Runner 2049.

[a5180007]

No automatically switched to V3 in case HEVC. Tested to...

Edit:
@staina please copy the console output during mux, and also send me a link to download sample (20 MB cut with Hex Editor eg HxD (https://mh-nexus.de/en/hxd/)). Which nightly build did you use ?
To cut 20 MB you drag&drop the file in the hex editor, select bytes from address 0 to 0140 000, Ctrl C, open new tab, Ctrl V, save.

[SeeMoreDigital]

Greetings, would be possible to into 1st post insert information, whether is already supported HDR10, HDR10+, Dolby Vision and next for UHD Bluray, eventually whether with to introduced functions yet works.
I can confirm this works well with 7th January 2020 and newer builds...

[a5180007]

Never use tsMuxeR to extract LPCM audio, it add garbage at end and create wav header incorrect (data not multiple of channels*bytedepth).

Hi @tebasuna51, txMuxer considers lpcm frames of 5ms. So in your example, zeros have effectively been added to your wav of 34.144 s. to align it to 35.145 s. This seems to be standard, I have checked few blu-rays and the end of the lpcm stream is usually padded with zeros.

The bug on the wav64 (incorrect data length) should be fixed in the next nightly builds.

[tebasuna51]

txMuxer considers lpcm frames of 5ms. So in your example, zeros have effectively been added to your wav of 34.144 s. to align it to 35.145 s. This seems to be standard, I have checked few blu-rays and the end of the lpcm stream is usually padded with zeros.
Curious.
Well add silence at end is not a problem.

The bug on the wav64 (incorrect data length) should be fixed in the next nightly builds.
Thanks.

[staina]

Edit:
@staina please copy the console output during mux, and also send me a link to download sample (20 MB cut with Hex Editor eg HxD (https://mh-nexus.de/en/hxd/)). Which nightly build did you use ?
To cut 20 MB you drag&drop the file in the hex editor, select bytes from address 0 to 0140 000, Ctrl C, open new tab, Ctrl V, save.

Tested I'm and next movies and at of no with automatically check option: BD - ROM V3 format

Tested to latest available nightly version: w64-nightly-2020-01-12--01-09-24

[ocean]

Hi Staina, it's normal, you have to look here:

https://i.ibb.co/y8fc080/Blade-Runner-2049.png (https://ibb.co/y8fc080)

[meihuaxiao]

How do I keep the original menu with a tsMuxeR 2.6.15 package UHD disk?

[SeeMoreDigital]

How do I keep the original menu with a tsMuxeR 2.6.15 package UHD disk?
TSmuxer is a transport stream muxing application not an disc authoring application.

[a5180007]

I think that the problem is that tsMuxeR doesn't use really the MPLS to retrieve its information, at least for the stuff related to the 3D-Planes. Since it is a muxer/demuxer, it prefers to trust what it finds in the M2TS (or SSIF) files, and it assumes that the PIDs of the streams determines their order. But that's not correct. The 3D-Plane numbers are stored in the MPLS and are based on the information and order from the same MPLS.

Trust me, I have studied closely that bug, after several problems I have encountered when I have written BD3D2MK3D. It's obviously a major bug. BTW, you can use my program to examine how the 3D-Planes are assigned to the subtitle streams. I have written my own MPLS parser, because it was impossible to trust the 3D-Planes information displayed by tsMuxeR.

@r0lZ @staina please test my latest build https://github.com/jcdr428/tsMuxer/actions . Once you've confirmed that the bug is solved, the patch will be merged to the master.

Edit: patch has been merged to master ;)

[zeropc]

The macOS version still doesn't work when adding a file. Same error as before.

https://i.imgur.com/iU1Km6i.png

[staina]

Would be possible to into tsMuxeru add option for default audio and subtitle track, possibly as check box before track.Is it only one command extra into file MovieObject.bdmv.
Now I have to uselessly circuitously create Bluray so that the first yourself Bluray create as Bluray folder, BDEdit set the default audio and subtitle track and then create from Bluray folder to Bluray ISO.

Thank for answer Staina

[a5180007]

@staina it's already been entered as issue #126 (https://github.com/justdan96/tsMuxer/issues/126). We just need somebody to work on it.

Have you had time to test whether the 3D-plane bug has been solved with the latest bintray build ?

[imhh11]

''Ability to detect audio delay for TS/M2TS/MPG/VOB/EVO sources;''

Could it be possible to add support to this ability for MKV sources as well ?
sorry if it has already been asked.

Thank's!

[staina]

@staina it's already been entered as issue #126 (https://github.com/justdan96/tsMuxer/issues/126). We just need somebody to work on it.

Have you had time to test whether the 3D-plane bug has been solved with the latest bintray build ?


Here described progress is same as while using BDEdit either it is impossible immediately from tsMuxer create Bluray ISO. Issue #126 is old already 10 days and yet no work :(

Test 3D-plane - keep on don't work right.

Will added and support for Dolby Atmos without core used in the MKV?

Always test with latest available version. Thank for answer Staina

[r0lZ]

Test 3D-plane - keep on don't work right.
What BD3D do you use for your tests ?

[staina]

What BD3D do you use for your tests ?

Use The Hobbit: The Battle of the Five Armies and The Hobbit: The Desolation of Smaug

[a5180007]

Here described progress is same as while using BDEdit either it is impossible immediately from tsMuxer create Bluray ISO.

Test 3D-plane - keep on don't work right.

@staina This commit (https://github.com/justdan96/tsMuxer/pull/151) should hopefully solve the bug -waiting for merge.

Issue #126 is old already 10 days and yet no work :(
Will added and support for Dolby Atmos without core used in the MKV?

Lots of code to write. Maybe there will be some good wills to do it, but it is above my c++ and Qt5 abilities.

[a5180007]

@staina This commit (https://github.com/justdan96/tsMuxer/pull/151) should hopefully solve the bug -waiting for merge.

@staina @r0lZ could you please test the latest nightly bintray build.

[staina]

@staina @r0lZ could you please test the latest nightly bintray build.

Test 3D-plane - keep on don't work right. Testing The Hobbit: The Desolation of Smaug - red is different.

LOG from BD3D2MK3D

Streams of 00100.mpls, 1:36:05, 24 chapters, 00049.ssif :

Video : Und AVC, 1080p, 23.976 fps, right-eye
Video : Und MVC, 1080p, 23.976 fps, left-eye (32 3D-Planes)
Audio : Eng DTS-HD-Master, Multi-channel, 48 Khz
Audio : Ces AC3, Multi-channel, 48 Khz
Audio : Hun AC3, Multi-channel, 48 Khz
Audio : Pol AC3, Multi-channel, 48 Khz
Audio : Rus AC3, Multi-channel, 48 Khz
Subtitle: Eng PGS, 3D-plane: 1
Subtitle: Ara PGS, 3D-plane: 2
Subtitle: Ces PGS, 3D-plane: 3
Subtitle: Dan PGS, 3D-plane: 4
Subtitle: Est PGS, 3D-plane: 5
Subtitle: Fin PGS, 3D-plane: 6
Subtitle: Heb PGS, 3D-plane: 7
Subtitle: Hun PGS, 3D-plane: 8
Subtitle: Isl PGS, 3D-plane: 9
Subtitle: Nor PGS, 3D-plane: 10
Subtitle: Pol PGS, 3D-plane: 11
Subtitle: Por PGS, 3D-plane: 12
Subtitle: Ron PGS, 3D-plane: 12
Subtitle: Rus PGS, 3D-plane: 13
Subtitle: Swe PGS, 3D-plane: 14
Subtitle: Ces PGS, 3D-plane: 3
Subtitle: Hun PGS, 3D-plane: 8
Subtitle: Pol PGS, 3D-plane: 11
Subtitle: Rus PGS, 3D-plane: 13

LOG from tsMuxeR

V_MPEG4/ISO/MVC, "H:\BDMV\PLAYLIST\00100.mpls", insertSEI, contSPS, track=4114
V_MPEG4/ISO/AVC, "H:\BDMV\PLAYLIST\00100.mpls", insertSEI, contSPS, track=4113
A_DTS, "H:\BDMV\PLAYLIST\00100.mpls", track=4352, lang=eng
A_AC3, "H:\BDMV\PLAYLIST\00100.mpls", track=4353, lang=ces
A_AC3, "H:\BDMV\PLAYLIST\00100.mpls", track=4354, lang=hun
A_AC3, "H:\BDMV\PLAYLIST\00100.mpls", track=4355, lang=pol
A_AC3, "H:\BDMV\PLAYLIST\00100.mpls", track=4356, lang=rus
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=1, track=4608, lang=eng
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=2, track=4609, lang=ces
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=3, track=4610, lang=ara
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=4, track=4611, lang=dan
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=5, track=4612, lang=est
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=6, track=4613, lang=fin
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=7, track=4614, lang=heb
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=8, track=4615, lang=hun
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=9, track=4616, lang=isl
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=10, track=4617, lang=nor
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=11, track=4618, lang=pol
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=12, track=4619, lang=por
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=12, track=4620, lang=ron
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=13, track=4621, lang=rus
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=14, track=4622, lang=swe
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=3, track=4623, lang=ces
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=8, track=4624, lang=hun
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=11, track=4625, lang=pol
S_HDMV/PGS, "H:\BDMV\PLAYLIST\00100.mpls", fps=23.976, 3d-plane=13, track=4626, lang=rus

[a5180007]

@staina thanks for the details, I have reproduced the bug with Hobbit Smaug and this patch (https://github.com/justdan96/tsMuxer/pull/157) should definitely correct it.
Edit: you can test the build on my fork https://github.com/jcdr428/tsMuxer/actions

[staina]

@staina thanks for the details, I have reproduced the bug with Hobbit Smaug and this patch (https://github.com/justdan96/tsMuxer/pull/157) should definitely correct it.
Edit: you can test the build on my fork https://github.com/jcdr428/tsMuxer/actions

3D-plane is OK.

[BloodyRipper]

yep commas. changed that and now its working properly. thank you
You shouldn't need to change locale settings - fix for this issue was merged a dozen commits back, and it shouldn't occur with the latest nightly builds.

[r0lZ]

@staina thanks for the details, I have reproduced the bug with Hobbit Smaug and this patch (https://github.com/justdan96/tsMuxer/pull/157) should definitely correct it.
Edit: you can test the build on my fork https://github.com/jcdr428/tsMuxer/actions
I can confirm that there are no 3D-Planes bugs any more in your fork.
And the "phantom streams" (present in the M2TS but unreferenced in the MPLS) are now clearly identified as such with "(PID not in MPLS)" instead of the confusing "3D-Plane: zero".
Great work ! Thanks !

[a5180007]

''Ability to detect audio delay for TS/M2TS/MPG/VOB/EVO sources;''

Could it be possible to add support to this ability for MKV sources as well ?

@imhh11 Please try last build 8052afb on my fork https://github.com/jcdr428/tsMuxer/actions .
I will push the patch when it is confirmed it is working well.

[imhh11]

@imhh11 Please try last build 8052afb on my fork https://github.com/jcdr428/tsMuxer/actions .
I will push the patch when it is confirmed it is working well.

Yes, it's working.
Awesome work, thank you !

[a5180007]

Yes, it's working.
Awesome work, thank you !

Good ! The patch has been merged and is in the nightly-2020-01-23--01-09-23.

[manolito]

Thanks very much a5180007 for this latest nightly... :thanks:

On my ancient computer (P3 without SSE2, WinXP) the last working tsMuxeR version used to be 2.6.12 from 2014.

Your builds are different. The GUI does not work (as expected), but the CLI executable works like a charm. And it runs beautifully under the old GUI, I have not found any issues so far.


Thanks again
manolito

[FilipeAmadeuO]

Thanks very much a5180007 for this latest nightly... :thanks:

On my ancient computer (P3 without SSE2, WinXP) the last working tsMuxeR version used to be 2.6.12 from 2014.

Your builds are different. The GUI does not work (as expected), but the CLI executable works like a charm. And it runs beautifully under the old GUI, I have not found any issues so far.


Thanks again
manolito

Have you tried the latest versions from here:
https://www.videohelp.com/software/tsMuxeR

[manolito]

Have you tried the latest versions from here:
https://www.videohelp.com/software/tsMuxeR

These versions are identical.

[BloodyRipper]

On my ancient computer (P3 without SSE2, WinXP) the last working tsMuxeR version used to be 2.6.12 from 2014.

Your builds are different. The GUI does not work (as expected), but the CLI executable works like a charm. And it runs beautifully under the old GUI, I have not found any issues so far.The GUI will keep on working as long as the "protocol" used to communicate between the CLI and the GUI isn't changed. This isn't planned so far, but keep in mind that it might change without notice. Any new features also *might* impact the "protocol" so that something stops working suddenly when using the old GUI.

Unfortunately, I'm afraid I don't have good news for you regarding the GUI : Qt has required SSE2 support in all builds since version 5.3.0 (https://lists.qt-project.org/pipermail/development/2013-November/014085.html). As for the CLI, it's a consequence of building the Windows versions with MinGW, which uses legacy x87 instructions by default. MSVC, on the other hand, has enabled SSE2 by default since Visual Studio 2012 or so. Roman's own tsMuxeR builds were most possibly made with MSVC.

[maxibon]

Could someone check please?, TSMuxer hide subtitles when I try to replace the spa (latin) with spa (spain). For instance:
Source: PLAYLIST REPORT:

Name: 00700.MPLS
Length: 2:13:04.976 (h:m:s.ms)
Size: 55,198,617,600 bytes
Total Bitrate: 55.30 Mbps

VIDEO:

Codec Bitrate Description
----- ------- -----------
MPEG-H HEVC Video 46163 kbps 2160p / 23.976 fps / 16:9 / Main 10 @ Level 5.1 @ High / 10 bits / HDR10 / BT.2020

AUDIO:

Codec Language Bitrate Description
----- -------- ------- -----------
DTS-HD Master Audio English 4545 kbps 7.1 / 48 kHz / 4545 kbps / 24-bit (DTS Core: 5.1 / 48 kHz / 1509 kbps / 24-bit)
Dolby Digital Audio English 448 kbps 5.1 / 48 kHz / 448 kbps / DN -31dB
Dolby Digital Audio Spanish 448 kbps 5.1 / 48 kHz / 448 kbps / DN -31dB
Dolby Digital Audio French 448 kbps 5.1 / 48 kHz / 448 kbps / DN -31dB
Dolby Digital Audio English 224 kbps 2.0 / 48 kHz / 224 kbps / DN -31dB

SUBTITLES:

Codec Language Bitrate Description
----- -------- ------- -----------
Presentation Graphics English 53.456 kbps
Presentation Graphics Spanish 38.371 kbps
Presentation Graphics French 41.440 kbps
Presentation Graphics English 81.546 kbps
Presentation Graphics Spanish 71.088 kbps
Presentation Graphics French 76.848 kbps

After replace clpi, m2ts and preserving the mpls the result is:

Disc Title: XXXXXXXX
Disc Label:XXXXXXXXXXXX
Disc Size: 57,680,873,663 bytes
Protection: AACS2
Playlist: 00800.MPLS
Size: 0 bytes
Length: 2:13:04.976
Total Bitrate: 0.00 Mbps
Video: MPEG-H HEVC Video / 0 kbps / 2160p / 23.976 fps / 16:9 / Main 10 @ Level 5.1 @ High / 10 bits / HDR10 / BT.2020
Audio: English / DTS-HD Master Audio / 7.1 / 48 kHz / 24-bit (DTS Core: 5.1 / 48 kHz / 1509 kbps / 24-bit)
Audio: English / Dolby Digital Audio / 5.1 / 48 kHz / 448 kbps / DN -31dB
Audio: Spanish / DTS Audio / 5.1 / 48 kHz / 768 kbps / 24-bit
Audio: French / Dolby Digital Audio / 5.1 / 48 kHz / 448 kbps / DN -31dB
Audio: English / Dolby Digital Audio / 2.0 / 48 kHz / 224 kbps / DN -31dB
* Subtitle: English / 0.000 kbps
* Subtitle: Spanish / 0.000 kbps
* Subtitle: French / 0.000 kbps
* Subtitle: English / 0.000 kbps
* Subtitle: French / 0.000 kbps
* Subtitle: Spanish / 0.000 kbps

So subtitles doesn't work

Am I doing something wrong?

Regards

[Hart2hart]

Quick status that is now old news but I’ve ripped and remuxed 4 movie only from UHD disks with Dolby Vision. They all play with audio video and subtitles in sync for at least 10-30 minutes that I watched.


Don’t have a DV player or TV so can’t comment on that but it’s is in the stream.

Fantastic!

[filler56789]

Roman's own tsMuxeR builds were most possibly made with MSVC.

The Windows binaries of tsMuxeR, you meant.
Yes, you can be sure they were made with MSVC, not with MinGW-w64&&MSYS. The original source-code was messy as Hell, but at least it didn't require a posix-threaded compiler without a very-good reason.

[a5180007]

Could someone check please?, TSMuxer hide subtitles when I try to replace the spa (latin) with spa (spain).

@maxibon my bad. This is a consequence of the 3d-plane patch, I've pushed the fix.

[maxibon]

@maxibon my bad. This is a consequence of the 3d-plane patch, I've pushed the fix.

Thank you so much @a5180007 please let me know when implemented

[a5180007]

Thank you so much @a5180007 please let me know when implemented

@maxibon please try latest bintray build nightly-2020-01-26--01-10-07.zip

[maxibon]

@maxibon please try latest bintray build nightly-2020-01-26--01-10-07.zip

Hi

I´ve tried with latest build and doesn't work yet;-(

By the way chapters doesn't work as well, doesn't keep original times

Regards

[Mike-uk]

Hi, Hopefully this is the correct place to ask for tsmuxer help

ive encoded a .m2ts file to a smaller H265 file ( ive tried mp4 and mkv) using handbrake with nvenc, the resulting file plays fine, I can seek to any time of the file quickly and cleanly

the problem is if I use tsmuxer to mux to m2ts, if I try and seek to any time in the file it creats a pixulated image for 2 seconds with mphc then goes back to normal ?? vlc pauses for a few seconds befor resuming, the file just doesn't feel right

any idea why

Thanks

[a5180007]

@Mike-uk you need to add x265 options --aud --hrd --repeat-header
Edit: --repeat-headers

[Mike-uk]

@Mike-uk you need to add x265 options --aud --hrd --repeat-header

Hi, adding thouse to handbrake seem to make no difference ?

[a5180007]

Hi, adding thouse to handbrake seem to make no difference ?

@Mike-uk Please cut the first 5 MB of the m2ts with an hex editor, and send me the link to download.

[a5180007]

Hi

I´ve tried with latest build and doesn't work yet;-(

By the way chapters doesn't work as well, doesn't keep original times

Regards

@maxibon please zip and send me your .meta with original and modified .mpls and .clpi.

[Mike-uk]

@Mike-uk Please cut the first 5 MB of the m2ts with an hex editor, and send me the link to download.

hi ive sent you the output of tsmuxer, m2ts file

[a5180007]

hi ive sent you the output of tsmuxer, m2ts file

@Mike-uk as suspected there is no AUD nal in your hevc stream. Please encode with x265 options --aud --hrd --repeat-headers.
If handbrake doesn't allow these options, use another frontend, or ffmpeg/x265 cli.

[Mike-uk]

@Mike-uk as suspected there is no AUD nal in your hevc stream. Please encode with x265 options --aud --hrd --repeat-headers.
If handbrake doesn't allow these options, use another frontend, or ffmpeg/x265 cli.

ok thanks for looking

ok handbrake should except commands to the encoder but don't see to work

[glc650]

Just downloaded 2020-01-28--01-08-41 for mac but whenever I try to import a video I get the following error:

https://1drv.ms/u/s!AnsGKXR_EKR0hEP-T4GYkpyG_Upz?e=A0auoI

This is after running ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" < /dev/null 2> /dev/null brew install freetype brew install in terminal.

Thanks,

->g.

[glc650]

Just downloaded 2020-01-28--01-08-41 for mac but whenever I try to import a video I get the following error:

https://1drv.ms/u/s!AnsGKXR_EKR0hEP-T4GYkpyG_Upz?e=A0auoI

This is after running ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" < /dev/null 2> /dev/null brew install freetype brew install in terminal.

Thanks,

->g.Never mind, for some reason the command in the readme was truncated on my system (I tried FF and Safari). Once I checked the web page's source I could see the full command.

Any plans to support TrueHD/Atmos?

[filler56789]

Hummm, the tsMuxeR readme.md says:

MacOS
This ZIP file for MacOS can just be unzipped and the executables can be used after installing a couple of dependencies.

I know "nothing" about MacOS, except that it is a kind of Unix, so I have to ask:

¿is it impossible to create static builds of tsMuxeR for the Mac operating system(s)?

[varekai]

Hello!

Thanks justdan96 for picking up the torch and continuing the development of this one-of-a-kind software.
Really appreciate it, I use it a lot for my videos and Blu-ray.
As long as I've been using it I've had this problem.
Creating a subtitle .sup file using easySUP by Mr. Dean Kasabow.
--------------------------
Using tsMuxer:
In "Input" -> "add" adding an .mpls or .m2ts (24.000 FPS) video file and adding a .sup (24.000 FPS) subtitle file.
Output to Blu-ray folder.
--------------------------
The output subtitle is out of sync, it starts OK but then gradually goes out of sync.
I can't figure out what I'm doing wrong?
Could it be a bug in tsMuxer?
If I use a mediaplayer like PotPlayer or MPC-HC and load the .sup subtitle sync is perfect.
Any input is highly appreciated.

Best regards,
varekai

Edit: Problem solved, not a tsMuxer bug... sorry...:o

[koka]

justdan96, in COMPILING.md add ninja for ## Windows (Msys2):
pacman -Sy --needed $MINGW_PACKAGE_PREFIX-toolchain \
$MINGW_PACKAGE_PREFIX-cmake \
$MINGW_PACKAGE_PREFIX-freetype \
$MINGW_PACKAGE_PREFIX-zlib \
$MINGW_PACKAGE_PREFIX-ninja

and instead of
cmake . --build
use
cmake --build .

Thank you for your efforts!

[a5180007]

I´ve tried with latest build and doesn't work yet;-(

By the way chapters doesn't work as well, doesn't keep original times

@maxibon Nothing wrong with the files you sent me. The issue is you keep the original mpls with subtitle PIDs 0x12A0, 0x12A1 etc. , whereas tsMuxer creates new mpls/clpi/m2ts with PIDs 0x1200, 0x1201 etc. If you want to keep the original mpls, you have to modify the PIDs in the mpls with e.g. BDEdit or an hex editor.

I don't get how the original chapter times could be modified if you keep the original mpls: could you please expand ?

[filler56789]

justdan96, in COMPILING.md add ninja for ## Windows (Msys2):

Why he (thinks he) needs "ninja" for using MSYS2 on Windows or/and for compiling tsMuxeR is beyond me.

[koka]

filler56789, before use:
cmake ../ -G Ninja
need install it:
pacman -S $MINGW_PACKAGE_PREFIX-ninja

[mattmarsden]

Is there any possibility of making this work with single layer Dolby Vision?

[filler56789]

filler56789, before use:
cmake ../ -G Ninja
need install it:
pacman -S $MINGW_PACKAGE_PREFIX-ninja

You don't get it.
ninja is not strictly-required by tsMuxeR's source-code, justdan96 (or someone else) simply invented that artificial need.
Much in the same way a posix-threaded compiler was not needed by tsMuxeR,
but justdan96 modified the source-code so that now it requires a posix-threaded compiler.

[justdan96]

@varekai: if you could provide a sample we might be able to figure out where that issue is coming from.

@koka: I'll have to review the existing documentation, thanks for the input!

[koka]

And how do you like this, @elonmusk?

out.meta:
MUXOPT --no-pcr-on-video-pid --demux --vbr --vbv-len=500
V_MPEG4/ISO/AVC, "D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 202850 Галина Борисовна.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 202912 Николай Борисович.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 202929 Лена и Андрей.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203022 Нина Петровна.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203310 Галюшка.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203414 Юлечка.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203624 Таня.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203723 Саша.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203856 Алла.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 204010 Ирина.mkv", track=1
A_LPCM, "D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 202850 Галина Борисовна.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 202912 Николай Борисович.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 202929 Лена и Андрей.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203022 Нина Петровна.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203310 Галюшка.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203414 Юлечка.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203624 Таня.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203723 Саша.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203856 Алла.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 204010 Ирина.mkv", track=2, lang=rus
S_HDMV/PGS, "D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 202850 Галина Борисовна.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 202912 Николай Борисович.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 202929 Лена и Андрей.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203022 Нина Петровна.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203310 Галюшка.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203414 Юлечка.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203624 Таня.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203723 Саша.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 203856 Алла.mkv"+"D:\AV\2020\20200111 ДР Аллы\film\20200111 ДР Аллы 204010 Ирина.mkv", fps=50.0, track=3, lang=rus

d:\AV\2020\20200111 ДР Аллы\film>"C:\YandexDisk\PortableApps\tsMuxeR\tsMuxeR.exe" out.meta ""
tsMuxeR version git-39bb829. github.com/justdan96/tsMuxer
Decoding H264 stream (track 1): Profile: High@4.2 Resolution: 1920:1080p Frame rate: 50
H.264 muxing fps is not set. Get fps from stream. Value: 50
Can't create output file 20200111 „ђ Ђ««л 202850 ѓ «Ё* Ѓ®аЁб®ў* +20200111 „ђ Ђ««л 202912 ЌЁЄ®« © Ѓ®аЁб®ўЁз+20200111 „ђ Ђ««л 202929 ‹Ґ* Ё Ђ*¤аҐ©+20200111 „ђ Ђ««л 203022 ЌЁ* ЏҐва®ў* +20200111 „ђ Ђ««л 203310 ѓ «оиЄ +20200111 „ђ Ђ««л 203414 ћ«ҐзЄ +20200111 „ђ Ђ««л 203624 ’ *п+20200111 „ђ Ђ««л 203723 ‘ и +20200111 „ђ Ђ««л 203856 Ђ«« +20200111 „ђ Ђ««л 204010 €аЁ* .track_1.264

The problem is not even in сyrillic, but in file name overflow when demuxing concatenating parts with long file names
justdan96, please replace in tsMuxer\singleFileMuxer.cpp
for (int i = 0; i < (int)fileList.size(); i++)
{
if (i > 0)
fileName += '+';
fileName += extractFileName(fileList[i]);
}
with
fileName = extractFileName(fileList[0]);/*
for (int i = 0; i < (int)fileList.size(); i++)
{
if (i > 0)
fileName += '+';
fileName += extractFileName(fileList[i]);
}*/

Thank you for your efforts!

[koka]

You don't get it.
You're right, for your repository
https://github.com/filler56789/RV-tsMuxeR
not needed
pacman -S $ MINGW_PACKAGE_PREFIX-ninja
Everything compiles fine thanks to your makefile!
But before assembly
https://github.com/justdan96/tsMuxer
need to install ninja

Thanks for the hard work!

[varekai]

@varekai: if you could provide a sample we might be able to figure out where that issue is coming from.
Hello!
Thanks for the quick reply, appreciate it!
Will a short clip do?
It's the same sequence as used in the screendumps.
https://workupload.com/file/mwYEsyEC
test_files.7z (19.37 MB) (test.m2ts + test.sup)
The out of sync will not show up in such a short clip.

Best regards,
varekai

Edit: Problem solved, not a tsMuxer bug... sorry...:o

[justdan96]

@varekai: ah, in that case with the original file can you say the length of the video and when the out of sync audio starts?

I can update documentation on build dependencies and make it more clear the user can choose the CMake output for their preference, as per cmake-generators.

[filler56789]

To whom this may concern...

*nightly-2020-01-28--01-08-41.zip

still has the GUI design-flaw regarding 24-bit DTS-Express

--- i.e., the secondary audio track checkbox remains greyed out.

[staina]

At creation Bluray from Bluray sources where MPLS includes more M2TS so tsMuxer in some frames remove from audio streams any part see:

DTS-HD stream (track 2): overlapped frame detected at position 00:42:14,666. Remove frame.
DTS stream (track 3): overlapped frame detected at position 00:42:14,666. Remove frame.
DTS-HD stream (track 2): overlapped frame detected at position 00:55:05,770. Remove frame.
DTS stream (track 3): overlapped frame detected at position 00:55:05,770. Remove frame.
DTS-HD stream (track 2): overlapped frame detected at position 00:57:14,687. Remove frame.
DTS stream (track 3): overlapped frame detected at position 00:57:14,687. Remove frame.
DTS-HD stream (track 2): overlapped frame detected at position 01:17:11,637. Remove frame.
DTS stream (track 3): overlapped frame detected at position 01:17:11,637. Remove frame.
DTS-HD stream (track 2): overlapped frame detected at position 01:59:46,101. Remove frame.
DTS stream (track 3): overlapped frame detected at position 01:59:46,101. Remove frame.

For example: MKV Toolnix or DVDFab nothing not remove and audio stream at comparing is other than from tsMuxer.
Will process tsMuxer audio stream right and MKV Toolnix and DVDFab wrong and or is in tsMuxer error?

Thank for answer Staina

[varekai]

@varekai: ah, in that case with the original file can you say the length of the video and when the out of sync audio starts?

I can update documentation on build dependencies and make it more clear the user can choose the CMake output for their preference, as per cmake-generators.

Hello!

Sorry for the late reply, but here goes...

Read about cmake and cmake-generators and I have to admit that's waay above my head...
I have absolutely no clue!
I'm very much dependant using on using a GUI I'm afraid.
So I can't be much of a help...

Best regards,
varekai
The video length is 02:32:10:958
Using PotPlayer's ->Adjust Subtitle Sync (ms):<- feature.
At start the video+sup, sup start is set to 500ms (faster) and sup is in sync.
Sync is off at 00:30:29
Applying 1000ms sup is in sync at 00:30:29
Sync is off at 01:03:20
Applying 2000ms sup is in sync at 02:08:32
It is really tricky to adjust timings in PotPlayer, not as correct as I hoped.
So these sup timings are very rough.


Edit: Problem solved, not a tsMuxer bug... sorry...:o

[tebasuna51]

@staina
You can check that with eac3to DTS extract. If is the same then tsMuxeR is right.
Some explain https://forum.doom9.org/showthread.php?p=1600694#post1600694

If MKV Toolnix or DVDFab don't remove the 5 frames you obtain 53 extra ms of duration and 5 points with possible glitches.

[staina]

@staina
You can check that with eac3to DTS extract. If is the same then tsMuxeR is right.
Some explain https://forum.doom9.org/showthread.php?p=1600694#post1600694

If MKV Toolnix or DVDFab don't remove the 5 frames you obtain 53 extra ms of duration and 5 points with possible glitches.

Checked I'm it via eac3to that either some warning message displayed in log and output file is not to be same with file from tsMuxer even with files from MKV Toolnix and DVDFab.

Which output file is then right?

[a5180007]

Checked I'm it via eac3to that either some warning message displayed in log and output file is not to be same with file from tsMuxer even with files from MKV Toolnix and DVDFab.

Which output file is then right?

@staina could you please show eac3to log, and zip and send me mpls/clpi files.

[staina]

@a5180007 Here is LOG from Eac3to:

eac3to v3.34
command line: "E:\eac3to334-UsEac3to129\eac3to.exe" "F:\Bluray\BDMV\PLAYLIST\00801.mpls" 1) 3: "E:\Test\00801.mpls_3eng.dts" -progressnumbers -log="E:\eac3to334-UsEac3to129\UsEac3To.log"
------------------------------------------------------------------------------
M2TS, 1 video track, 5 audio tracks, 14 subtitle tracks, 2:08:31, 11.988p
1: Chapters, 20 chapters
2: h265/HEVC, 2160p24 /1.001 (16:9), 10 bits
3: DTS Master Audio, English, 7.1 channels, 24 bits, 48kHz
(core: DTS, 5.1 channels, 1509kbps, 48kHz)
4: DTS, English, 2.0 channels, 255kbps, 48kHz
5: DTS, French, 5.1 channels, 768kbps, 48kHz
6: DTS, Czech, 5.1 channels, 768kbps, 48kHz
7: DTS, Polish, 5.1 channels, 768kbps, 48kHz
8: Subtitle (PGS), English
9: Subtitle (PGS), French
10: Subtitle (PGS), Dutch
11: Subtitle (PGS), Danish
12: Subtitle (PGS), Finnish
13: Subtitle (PGS), Norwegian
14: Subtitle (PGS), Swedish
15: Subtitle (PGS), Czech
16: Subtitle (PGS), Polish
17: Subtitle (PGS), Chinese
18: Subtitle (PGS), Modern Greek
19: Subtitle (PGS), French
20: Subtitle (PGS), Czech
21: Subtitle (PGS), Polish
[a03] Extracting audio track number 3...
[a03] Creating file "E:\Test\00801.mpls_3eng.dts"...
[a03] Audio has a gap of 31ms at playtime 0:42:15. <WARNING>
[a03] Audio has a gap of 31ms at playtime 0:46:42. <WARNING>
[a03] Audio has a gap of 31ms at playtime 0:55:06. <WARNING>
[a03] Audio has a gap of 31ms at playtime 0:57:15. <WARNING>
[a03] Audio has a gap of 31ms at playtime 0:59:42. <WARNING>
[a03] Audio has a gap of 31ms at playtime 1:05:47. <WARNING>
[a03] Audio has a gap of 31ms at playtime 1:17:12. <WARNING>
[a03] Audio has a gap of 31ms at playtime 1:18:18. <WARNING>
[a03] Audio has a gap of 31ms at playtime 1:27:34. <WARNING>
[a03] Audio has a gap of 31ms at playtime 1:30:48. <WARNING>
[a03] Audio has a gap of 31ms at playtime 1:37:16. <WARNING>
[a03] Audio has a gap of 31ms at playtime 1:38:42. <WARNING>
[a03] Audio has a gap of 31ms at playtime 1:59:47. <WARNING>
[a03] Starting 2nd pass...
[a03] Realizing DTS gaps...
[a03] Creating file "E:\Test\00801.mpls_3eng.dts"...
Video track 2 contains 184856 frames.
eac3to processing took exactly 8 minutes.
Done.


Here is LOG from tsMuxer:

tsMuxeR version git-e58b4de. github.com/justdan96/tsMuxer
HEVC muxing fps is not set. Get fps from stream. Value: 23.976
Decoding DTS-HD stream (track 2): Bitrate: 1536Kbps core + MLP data.Sample Rate: 48KHz Channels: 7.1 (DTS Master Audio 24bit)
B-pyramid level 2 detected. Shift DTS to 3 frames
DTS-HD stream (track 2): overlapped frame detected at position 00:42:14,666. Remove frame.
DTS-HD stream (track 2): overlapped frame detected at position 00:55:05,770. Remove frame.
DTS-HD stream (track 2): overlapped frame detected at position 00:57:14,687. Remove frame.
DTS-HD stream (track 2): overlapped frame detected at position 01:05:46,783. Remove frame.
DTS-HD stream (track 2): overlapped frame detected at position 01:17:11,637. Remove frame.
DTS-HD stream (track 2): overlapped frame detected at position 01:27:33,589. Remove frame.
DTS-HD stream (track 2): overlapped frame detected at position 01:59:46,101. Remove frame.
Processed 184880 video frames
Flushing write buffer
Creating Blu-ray stream info and seek index
Creating Blu-ray playlist
Mux successful complete
Muxing time: 6 min 40 sec

Attach file with MPLS and CLPI files

[a5180007]

@staina video frame duration is 41.708ms, whereas audio frame duration is 10.667 ms. In each m2ts, video and audio cannot stop stricly at the same time, and the last audio frame goes slightly beyond the last video frame.

eac3to gives a warning for each m2ts, whereas tsMuxer gives a warning -and omits last audio frames- only when the AV offset is greater than 1/2 audio frame ; which seems correct to me.

Note that the number of video frames reported by eac3to is incorrect : total mpls duration is 02:08:31.030 = 184880 frames.

[staina]

@a5180007 Thank you, so that optimal is used tsMuxer. DVDFab and MKV Toolnix it work badly for when nothing not remove and Eac3to again that remove more than is need.

Only one more query tsMuxer the audio stream encodes only remove overflowing frame YES?

Thank for answer staina

[a5180007]

@staina yes, tsMuxer removes only the overlapping frames.
And I don't think eac3to removes more than needed (code is not open source), only it issues a warning for each m2ts.

[staina]

@a5180007 Why then there's not DTS file from tsMuxer same as DTS file from Eac3to? To point where with remove frame are the same and then are there differences, therefore I'm with asked at it coding.

Stay on then at tsMuxer I hope that the keep quality audio streams.

Thank for answer staina

[tebasuna51]

eac3to work fine with all my test over BD's, but seems don't work with UHD ones.
The number of frames, the extrange fps 11.988p, ...

[yannick92]

Good morning all.

I noticed a new option on the latest versions of Tsmuxer?
Note that this option only appears on E-AC3 tracks, because on all other audio tracks it is grayed out and cannot be used.
What is it and what can it be used for?

Thank you in advance for all your passionate work.

17186

[yannick92]

Other strange things too:

The information for track E-AC3 is ok on the old 2.6.12, but not on the latest version?
I tested with several .mkv with an E-AC3 track and there is always the same error.
Why?
thank you

17187

17188

[guest]

Hey guys,

I'm hoping someone here can help me...I have wasted so much time trying to get this joined properly.

So as some of you may know, some long 3D movies (eg:- The Hobbit, Titanic, etc) are in 2 parts.

Seems pretty straight forward, you just append them using tsmuxer, and in practice, it does, HOWEVER, after running it thru, if you navigate to the "join point", there is a noticeable approx 1 second of "black", then when the 2nd part starts, the audio is out of sync...the same length as the "black" section that somehow appears when joined.

Is there some way that this "black" section doesn't happen ??

[a5180007]

@Pauly Dunne just to be sure, you added the mpls file in tsMuxer, rather than add the first m2ts and "append" the second m2ts file ?

[a5180007]

Creating a subtitle .sup file using easySUP by Mr. Dean Kasabow.
--------------------------
Using tsMuxer:
In "Input" -> "add" adding an .mpls or .m2ts (24.000 FPS) video file and adding a .sup (24.000 FPS) subtitle file.
Output to Blu-ray folder.
--------------------------
The output subtitle is out of sync, it starts OK but then gradually goes out of sync.
I can't figure out what I'm doing wrong?
Could it be a bug in tsMuxer?
If I use a mediaplayer like PotPlayer or MPC-HC and load the .sup subtitle sync is perfect.

Screendumps here: https://imgur.com/a/lXNXMmp


@varekai not sure to understand... if your player shows the sup subtitle perfectly synced, it means it already has the images timestamps for 24fps -although the file is marked as 23.976. So when you convert from 23.976 to 24 fps with tsMuxer, it becomes out of sync.

Edit : seems to be linked to this easysup bug https://forum.doom9.org/showthread.php?p=1451113#post1451113

[guest]

@Pauly Dunne just to be sure, you added the mpls file in tsMuxer, rather than add the first m2ts and "append" the second m2ts file ?

Hi, I just knew someone would ask that, and tbh I should have said so !!!!

Yes, I've tried both methods, several times, same result :(

[Hart2hart]

Hey guys,



I'm hoping someone here can help me...I have wasted so much time trying to get this joined properly.



So as some of you may know, some long 3D movies (eg:- The Hobbit, Titanic, etc) are in 2 parts.



Seems pretty straight forward, you just append them using tsmuxer, and in practice, it does, HOWEVER, after running it thru, if you navigate to the "join point", there is a noticeable approx 1 second of "black", then when the 2nd part starts, the audio is out of sync...the same length as the "black" section that somehow appears when joined.



Is there some way that this "black" section doesn't happen ??



I posted a way to do this a few years ago. Instead of joining playlists join ssif files. The results are seamless. Only thing I had to do was to fix chapter marks on second half. I’ll see if I can locate it and post link here.


It’s post 9 in this thread


https://forum.redfox.bz/threads/3d-blu-ray-with-multiple-disks.70932/

[varekai]

@varekai not sure to understand... if your player shows the sup subtitle perfectly synced,
it means it already has the images timestamps for 24fps
-although the file is marked as 23.976.
So when you convert from 23.976 to 24 fps with tsMuxer, it becomes out of sync.

Edit : seems to be linked to this easysup bug https://forum.doom9.org/showthread.php?p=1451113#post1451113
Hello!

That is a good find! Thanks!
I suspected it could be a bug in easySUP.
I'm definitely gonna try bdsup2sub!

What I'm doing is I demux .sup files from a Blu-ray with tsMuxer.
Import .sup to Subtitle Edit, do some editing, and save as .srt
Opening .srt with easySUP and apply settings like font, size, style, margin, etc.
(This .sup plays in sync when playing video (.m2ts or .mpls) in PotPlayer or MPC-HC and then adding .sup.)
Then add the Blu-ray in tsMuxer, removing unwanted streams, adding one or two easySUP generated .sup files.
This is where it goes wrong.
tsMuxer auto reads (wrongly) the .sup as Frame rate: 23.976 so not anything I can control.
tsMuxer then tries to auto change the FPS .sup to 24 to match the video wich results in a out off sync .sup.
So to sum it up, tsMuxer is not the culprit... sorry... :o

Best regards,
varekai

[r0lZ]

... the audio is out of sync...the same length as the "black" section that somehow appears when joined.

Is there some way that this "black" section doesn't happen ??
IMO, it is possible to fix this problem with MkvMerge.
For the audio sync issue, there is probably a solution with the CLI argument --append-mode:

--append-mode <file|track>
Selects how mkvmerge calculates timestamps when
appending files.

I think that it uses track by default, and that means that it joins each track independently. If the durations of the video and audio tracks of the first part are notably different, the audio will be out of sync. I guess that using file mode may help. (I don't know if it is possible to provide this argument with the GUI. Perhaps in Input -> Properties -> Miscellaneous -> Additional Options, but I have never tried.)

Also, if there is a blank at the end of the first part, you can remove it with the option Multiplexer -> Output -> Splitting -> Split mode: After specific timestamps. With some luck, you can cut the blank just at the end of the audio, or a bit before, and the second part will be in sync (with a very small delay due to the different durations of the video and audio frames, but that delay is so short that it should not be noticeable).

[guest]

I posted a way to do this a few years ago. Instead of joining playlists join ssif files. The results are seamless. Only thing I had to do was to fix chapter marks on second half. I’ll see if I can locate it and post link here.


It’s post 9 in this thread


https://forum.redfox.bz/threads/3d-blu-ray-with-multiple-disks.70932/

OMG Hart2hart, that info it EXACTLY what I need, I found a post that I could have written, it spot on :)

So I can't wait to try this process, and hope I have the same success as the OP had.

edit:- unfortunately, this did not work for me, still got the black frames at the join, and hence, sync was out, after that :(

I certainly came to the right place :)

I have a couple of other 2 part 3D movies, hopefully they will go thru tsmuxer without issue, but Titanic is a problem.

Cheers

[guest]

IMO, it is possible to fix this problem with MkvMerge.
For the audio sync issue, there is probably a solution with the CLI argument --append-mode:

I think that it uses track by default, and that means that it joins each track independently. If the durations of the video and audio tracks of the first part are notably different, the audio will be out of sync. I guess that using file mode may help. (I don't know if it is possible to provide this argument with the GUI. Perhaps in Input -> Properties -> Miscellaneous -> Additional Options, but I have never tried.)

Also, if there is a blank at the end of the first part, you can remove it with the option Multiplexer -> Output -> Splitting -> Split mode: After specific timestamps. With some luck, you can cut the blank just at the end of the audio, or a bit before, and the second part will be in sync (with a very small delay due to the different durations of the video and audio frames, but that delay is so short that it should not be noticeable).

Hi r0lZ,

As far as I know, MKVToolnix/MKVmerge doesn't process MVC (SSIF) 3D movies...it leaves out the SSIF/MVC track.

The ONLY app that I have found that DOES, IS tsmuxer.

I'm pretty sure that there are not any black sections at the end of the 1st part, or the start of the 2nd part. If you watch the movie in question (Titanic), that is NOT a joined non 3D version, and watch it at the 2 part version join point, there are NO "black" frames at all.

However, I appreciate your reply & suggestions, that I will give it a try in the future.

Cheers

[a5180007]

@yannick92 the "secondary" checkbox was already there with 2.6.12. The secondary audio is for PiP (Picture-in-Picture) videos.
Edit : secondary audio is possible only with E-AC3 and DTS Express.

Patch has been submitted for fixing the bitrate and channel.

[filler56789]

AT LAST! :)

In file w64-nightly-2020-02-05--01-09-49.zip

the 24-bit DTS Express "bug" in the GUI has been "fixed"
(so to speak)

:thanks:

[r0lZ]

As far as I know, MKVToolnix/MKVmerge doesn't process MVC (SSIF) 3D movies...it leaves out the SSIF/MVC track.
You can create the AVC+MVC MKV with MakeMKV. But I don't know if you can then use MkvToolnix to join the two parts, or cut the black section.
And, of course, if you want to recreate a 3DBD, tsMuxeR is better.

[mattmarsden]

Sorry to be a pain, but would there be any chance of muxing single layer Dolby Vision?

[a5180007]

Sorry to be a pain, but would there be any chance of muxing single layer Dolby Vision?

@mattmarsden could you please be more specific ? tsMuxer already muxes single layer DV hevc streams.

Try eg dolby-vision-amaze.mp4 (https://1drv.ms/v/s!AqRZp848Q4jUga5Fj71ZWzlwEq_kSQ?e=JABEdp) (DV Profile 5) or P81_GlassBlowing2.mp4 (https://1drv.ms/v/s!AqRZp848Q4jUga5Iye9g09Uv6EJ7jg?e=cowWIa) (DV Profile 8.1)

[a5180007]

Hello!

That is a good find! Thanks!
I suspected it could be a bug in easySUP.
I'm definitely gonna try bdsup2sub!
varekai

Or you could simple load the srt in tsMuxer, conversion to sup works well on Windows.
Alternatively, open the sup produced by easysup with an hexeditor:
- bytes 14-15 are width (0x0780 = 1920)
- bytes 16-17 are height (0x0438 = 1080)
- first nibble of byte 18 is fps: = (0, 23.976, 24, 25, 29.97, 30, 50, 59.94) => change from "10" to "20"

[SeeMoreDigital]

@mattmarsden could you please be more specific ? tsMuxer already muxes single layer DV hevc streams.

Try eg dolby-vision-amaze.mp4 (https://1drv.ms/v/s!AqRZp848Q4jUga5Fj71ZWzlwEq_kSQ?e=JABEdp) (DV Profile 5) or P81_GlassBlowing2.mp4 (https://1drv.ms/v/s!AqRZp848Q4jUga5Iye9g09Uv6EJ7jg?e=cowWIa) (DV Profile 8.1)Both of those sources crash my OPPO when muxed using the 'Blu-ray Folder' output option...

[a5180007]

Both of those sources crash my OPPO when muxed using the 'Blu-ray Folder' output option...

To my knowledge, standalone players don't have to be compatible with single layer DV streams. I can't see what can be changed on tsMuxer.

[SeeMoreDigital]

To my knowledge, standalone players don't have to be compatible with single layer DV streams. I can't see what can be changed on tsMuxer.I have a few single layer Dolby Vision test files that work fine with the OPPO.

Links: -
https://4kmedia.org/lg-earth-dolby-vision-uhd-4k-demo/ [60.000fps]
https://4kmedia.org/lg-dolby-vision-uhd-4k-demo/ [30.000fps]
https://4kmedia.org/lg-dolby-comparison-uhd-4k-demo/ [24.000fps]
https://4kmedia.org/lg-amaze-dolby-vision-uhd-4k-demo/ [60.000fps]

[a5180007]

I have a few single layer Dolby Vision test files that work fine with the OPPO.

Links: -
https://4kmedia.org/lg-earth-dolby-vision-uhd-4k-demo/ [60.000fps]
https://4kmedia.org/lg-dolby-vision-uhd-4k-demo/ [30.000fps]
https://4kmedia.org/lg-dolby-comparison-uhd-4k-demo/ [24.000fps]
https://4kmedia.org/lg-amaze-dolby-vision-uhd-4k-demo/ [60.000fps]

Ok, thanks @SeeMoreDigital. I'll try to see what's different from tsMuxer outputs.

[koka]

Attention! Starting yesterday night build w*nightly-2020-02-05*.zip, tsMuxeR requires *.meta in utf8. Previously for Windows required 8-bit encoding.

[mattmarsden]

@mattmarsden could you please be more specific ? tsMuxer already muxes single layer DV hevc streams.

Try eg dolby-vision-amaze.mp4 (https://1drv.ms/v/s!AqRZp848Q4jUga5Fj71ZWzlwEq_kSQ?e=JABEdp) (DV Profile 5) or P81_GlassBlowing2.mp4 (https://1drv.ms/v/s!AqRZp848Q4jUga5Iye9g09Uv6EJ7jg?e=cowWIa) (DV Profile 8.1)

So when I add a single layer DV mp4 created by DVDFab it says the track is unknown. I will try and link to a sample.

[BloodyRipper]

Attention! Starting yesterday night build w*nightly-2020-02-05*.zip, tsMuxeR requires *.meta in utf8. Previously for Windows required 8-bit encoding.
This will be fixed in nightly-2020-02-07. tsMuxeR will now try to interpret the file names in the meta file in the system's current 8-bit encoding if they don't appear to be encoded in UTF-8.

[SeeMoreDigital]

Ok, thanks @SeeMoreDigital. I'll try to see what's different from tsMuxer outputs.My pleasure and many thanks ;)

[cogira]

So when I add a single layer DV mp4 created by DVDFab it says the track is unknown. I will try and link to a sample.

same here with single layer dolby vision mp4 created by dvdfab.

[staina]

Compared I'm MPLS files created in tsMuxer and DVDFab and found out differences see. picture.

What these different bytes mean and is some problem for when are different?

Thank for answer. staina

[varekai]

Or you could simple load the srt in tsMuxer, conversion to sup works well on Windows.
Alternatively, open the sup produced by easysup with an hexeditor:
- bytes 14-15 are width (0x0780 = 1920)
- bytes 16-17 are height (0x0438 = 1080)
- first nibble of byte 18 is fps: = (0, 23.976, 24, 25, 29.97, 30, 50, 59.94) => change from "10" to "20"
Thanks for the input, appreciate it.
I know tsMuxer can mux to a sup from srt but is has a bug with italics.
If I remember right it has it an all earlier verions aswell including the tsMuxerGUI-Nightly-2020-02-05--01-09-49.
Look at these two screendumps:
https://imgur.com/a/OiZA8F8

Also easySUP has more subtitles alternatives.
A wet dream I have is if there was a sup creator with options like in PotPlayer.
Potplayer Font Style:
https://imgur.com/a/90h7T69

I use HxD Hex Editor 2.3 but I can't find what you are refering to?
Any advice would on this would be great!

Thanks and
Best regards
varekai

[a5180007]

I use HxD Hex Editor 2.3 but I can't find what you are refering to?
Any advice would on this would be great!

On your file test.sup: the two first lines (first 32 bytes) are the PGS header.
First circle is the PGS width 0x0780, followed by the height 0x0438, followed by (second circle) 1=23.976 fps. Change it to 2=24 fps.

https://i.imgur.com/wSgKPqy.jpg

[a5180007]

What these different bytes mean and is some problem for when are different?

The bytes 00 00 00 0F 40 00 00 00 are the "UOMaskTable (https://github.com/lerks/BluRay/wiki/UOMaskTable)".
The following nibble is the four flags RandomAccess, AudioMix, LosslessBypass, MVCBaseViewR.

On a standalone player it is a problem if some of these flags are not enabled, with V3 Blu-rays they are compulsory.

[staina]

The bytes 00 00 00 0F 40 00 00 00 are the "UOMaskTable (https://github.com/lerks/BluRay/wiki/UOMaskTable)".
The following nibble is the four flags RandomAccess, AudioMix, LosslessBypass, MVCBaseViewR.

On a standalone player it is a problem if some of these flags are not enabled, with V3 Blu-rays they are compulsory.

So that tsMuxer it has right and DVDFab wrong? Yes.

[varekai]

On your file test.sup: the two first lines (first 32 bytes) are the PGS header.
First circle is the PGS width 0x0780, followed by the height 0x0438, followed by (second circle) 1=23.976 fps. Change it to 2=24 fps.
https://i.imgur.com/wSgKPqy.jpg
Excellent! That worked like a charm! :D
Thank you so much for your help, really appreciate it!
It will be an extra step in the workflow but its well worth it.
I like a goodlooking font for my movie projects.

Many thanks and
Best regards,
varekai

[a5180007]

I have a few single layer Dolby Vision test files that work fine with the OPPO.

@SeeMoreDigital I've tried some changes in the TS descriptors. Please advise whether P81_GlassBlowing2.m2ts (https://1drv.ms/v/s!AqRZp848Q4jUga5QXVbb471YcGg_3w?e=3AGtN1) works with your OPPO.

So that tsMuxer it has right and DVDFab wrong? Yes.

Yes, tsMuxer has it right and DVDFab is incorrect.

[FilipeAmadeuO]

P81_GlassBlowing2.m2ts works on on my OPPO clone player, so most probably will also work on orginal OPPO player.

[mariner]

On your file test.sup: the two first lines (first 32 bytes) are the PGS header.
First circle is the PGS width 0x0780, followed by the height 0x0438, followed by (second circle) 1=23.976 fps. Change it to 2=24 fps.

https://i.imgur.com/wSgKPqy.jpg

Greetings a5180007, thank you for the herculean effort to keep tsmuxer up to date.:thanks:
A quick question regarding the resolution of 4kUHD sup subtitle: 1920x1080 or 3840x2160?
Many thanks and best regards,

[SeeMoreDigital]

@SeeMoreDigital I've tried some changes in the TS descriptors. Please advise whether P81_GlassBlowing2.m2ts (https://1drv.ms/v/s!AqRZp848Q4jUga5QXVbb471YcGg_3w?e=3AGtN1) works with your OPPO.
The .m2ts file plays in HDR10 only...

[a5180007]

The .m2ts file plays in HDR10 only...

To understand, and know if I am on the right path: so the previous P81_GlassBlowing2.m2ts was not read at all by your player, and the new sample plays but only in HDR10 ?

[SeeMoreDigital]

To understand, and know if I am on the right path: so the previous P81_GlassBlowing2.m2ts was not read at all by your player, and the new sample plays but only in HDR10 ?

Yes, after re-muxing the 'P81_GlassBlowing2.mp4' file using TSmuxer's Blu-ray Folder output option, it crashed my OPPO.

I have also just tried re-muxing the 'P81_GlassBlowing2.m2ts' file using TSmuxer's Blu-ray Folder output option and it crashes my OPPO too.

By the way... According to MediaInfo the original 'P81_GlassBlowing2.mp4' file does not contain any Dolby Vision meta-data: -

General
Complete name : d:\SeeMoreDigital\Downloads\P81_GlassBlowing2.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/mp41)
File size : 30.6 MiB
Duration : 18 s 35 ms
Overall bit rate : 14.2 Mb/s
Writing application : Lavf58.26.101

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@Main
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : hev1
Codec ID/Info : High Efficiency Video Coding
Duration : 18 s 35 ms
Bit rate : 14.2 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 59.940 (59940/1000) FPS
Minimum frame rate : 59.940 FPS
Maximum frame rate : 59.943 FPS
Original frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.115
Stream size : 30.6 MiB (100%)
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : BT.2020
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2
Codec configuration box : hvcC

[a5180007]

@SeeMoreDigital what I need to know is if your player can read the m2ts I uploaded -the patch is not included in the master. If you can read it (even in HDR10), next step is to include the DV private data in the PMT for non-bluray mixing.

To my knowledge, only DV profile 7 DV is compatible with Blu-ray. I doubt tsMuxer can produce a compatible HDMV blu-ray folder with single layer -profile 5 and 8- DV.

As for the dvvC box missing in the mp4, ffmpeg seems to be at the same stage as tsMuxer...

Edit : do you know if your OPPO is compatible with DV profile 8.1 ? If not, the fall back to HDR10 is normal.

[a5180007]

@SeeMoreDigital what I need to know is if your player can read the m2ts I uploaded -the patch is not included in the master. If you can read it (even in HDR10), next step is to include the DV private data in the PMT for non-bluray mixing.

To my knowledge, only DV profile 7 DV is compatible with Blu-ray. I doubt tsMuxer can produce a compatible HDMV blu-ray folder with single layer -profile 5 and 8- DV.

As for the dvvC box missing in the mp4, ffmpeg seems to be at the same stage as tsMuxer...

Edit: if your OPPO is not compatible with DV profile 8.1, the fallback to HDR10 is normal.

[SeeMoreDigital]

@SeeMoreDigital what I need to know is if your player can read the m2ts I uploaded -the patch is not included in the master. If you can read it (even in HDR10), next step is to include the DV private data in the PMT for non-bluray mixing.Yes my OPPO can play the 'P81_GlassBlowing2.m2ts' file...

[a5180007]

Yes my OPPO can play the 'P81_GlassBlowing2.m2ts' file...

Thanks! So to finish the patch I need to include the 0xB0 DoVi descriptor in the PMT. Anybody knows how to extract the DoVi profile and level info from the hevc stream ? (and not from the container m2ts or mp4)

[SeeMoreDigital]

Out of interest...

What tool is used to determine the profile version of a Dolby Vision video stream?

[koka]

Thanks to @BloodyRipper, the torment with writing .srt in UTF-8 with BOM ended. Now you can write .srt in UTF-8 without BOM or even in 8-bit active code page encoding for example, in cp1251. Look https://github.com/justdan96/tsMuxer/commit/0035efb243a72a085c67c965e1fcf9637a998593

[a5180007]

What tool is used to determine the profile version of a Dolby Vision video stream?

Mediainfo reports profile and level (eg dvhe.04.06) read from m2ts or mp4 metadata. What I don't know -and I need for the PMT descriptor- is how to have these from the hevc stream.

[imhh11]

@a5180007 I hope you can make tsmuxer to remux the single layer mp4 to TS or M2TS, that would be really awesome. It would allow Atmos + DV (Even though DVDFAB's single layer remux are probably not true DV, it's still progress.)

Also, it would be nice to have the ability to go from dual-layer mp4 to UHD structure. Now we have to demux the mp4 with dlb_mp4demux and then build the UHD structure with tsmuxer.

Thank's a lot for the great work you're doing.

[ryu34]

Hey wondering if there will be support for True-HD or Atmos tracks that have had their AC-3 core separated as its own track due to MKV authoring.

[SeeMoreDigital]

Hey wondering if there will be support for True-HD or Atmos tracks that have had their AC-3 core separated as its own track due to MKV authoring.Yes this would be handy...

From what I understand .thd+ac3 is only a mandatory requirement for Blu-ray disc authoring. The AC-3 core is not necessary when creating generic .m2ts files.

[tymoxa]

Thanks to @BloodyRipper, Enhancement: Add option to make a specific audio the default track and a specific subtitle track a forced track #126 works as it intended to be (at least in cli). :thanks:

[outgoing]

Thanks to @BloodyRipper, works as it intended to be (at least in cli). :thanks:

Is this also valid for when it is assembled in a bluray with menu?

[tymoxa]

Is this also valid for when it is assembled in a bluray with menu?
No. Only for remuxes

[outgoing]

No. Only for remuxes

:thanks:

[GeorgeLucas]

It would be cool if a language could be chosen as the default (Audio & Subs). Please please insert this feature...

THX

[SeeMoreDigital]

It would be cool if a language could be chosen as the default (Audio & Subs). Please please insert this feature...

THXI'm not sure I understand what you mean!

[tymoxa]

It would be cool if a language could be chosen as the default (Audio & Subs). Please please insert this feature...

It's already there, in Blu-Ray tab. Check the latest nightly build here (https://bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly/2020-02-10--01-10-49)

[GeorgeLucas]

If I drag an mpls file into the tsmuxer, the German audio tracks and subtitles are only automatically marked, for example.

[SeeMoreDigital]

If I drag an mpls file into the tsmuxer, the German audio tracks and subtitles are only automatically marked, for example.For what Blu-ray discs? Where were they originally released?

[Hart2hart]

If I drag an mpls file into the tsmuxer, the German audio tracks and subtitles are only automatically marked, for example.



I believe George is asking for the ability to set a default language in TSMuxer. This default would be applied to the results of a playlist being added by TSMuxer preselecting tracks in that language and leaving others as not selected.

[staina]

Great work with addition setting for default audio and subtitles track. Still would it would in the same parts behind command Play PL_MK 0, GPR10 (HEX: 42 82 00 00 00 00 00 00 00 00 00 0A) change command Jump Title 1 (HEX: 21 81 00 00 00 00 00 01 00 00 00 00) to command Break (HEX: 00 02 00 00 00 00 00 00 00 00 00 00). Command Jump Title 1 playback bluray disk over and over in loop order ending playback at the end movie.

Latest nightly build tsMuxer GUI no saves position and size windows and lay-out in window see pictures.

Thanks fixed and answer, staina

[Hart2hart]

On Blu-ray tab, what does “Start mux time”represent?

Thank you

[justdan96]

@staina sorry I'm not quite sure what you are saying, is it a UI issue?

[staina]

@justdan96 Yes one saying UI issue - Red area width and overlap text.

Two saying - Still would it would in the same parts behind command Play PL_MK 0, GPR10 (HEX: 42 82 00 00 00 00 00 00 00 00 00 0A) change command Jump Title 1 (HEX: 21 81 00 00 00 00 00 01 00 00 00 00) to command Break (HEX: 00 02 00 00 00 00 00 00 00 00 00 00). Command Jump Title 1 playback bluray disk over and over in loop order ending playback at the end movie.

[imhh11]

Hi, is it possible to add an option for batch jobs ( queue) ?

[zeropc]

Doesn't anyone know how to get the app properly working on macOS?

https://i.imgur.com/iU1Km6i.png

[filler56789]

Doesn't anyone know how to get the app properly working on macOS?

https://i.imgur.com/iU1Km6i.png

According to the official README.md:

This ZIP file for MacOS can just be unzipped and the executables can be used after installing a couple of dependencies.
To install those run the commands below in the Terminal:

ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" < /dev/null 2> /dev/null
brew install freetype
brew install zlib

which in my not-so-humble opinion is not good enough.
I mean, why no static builds for the Mac operating system?

I have already asked this question but it went ignored

--- by justdan96 and by the "contributors" as well.

[zeropc]

snip...

Thanks. This worked :)

[filler56789]

Thanks. This worked :)

Great :)
Now all we have to do is give an https://forum.videohelp.com/attachments/2671-1279232225/uglylol.gif to justdan96.

[justdan96]

I haven't tried a static build on Mac, I can look into it at some point. Alternatively we could put the dynamic libraries into the app package. Xavery is working on a native build for Mac so he might be better placed to comment.

[Hombre007]

I’am using ts MuxeR 2.6.15 fore remuxing UHD discs.

I take the v.i. a Complete UHD version and select video and English audio streams and ad the Dutch subtitles. But sometimes I encounter 2 problems.

1. tsMuxer chances the frame rate from 24 too 23,976 by the video stream ab subtitles, bet not de audio. Result the audio is out of sync and the picture stutters.
2. The HDR is not done correctly in the remux. Result the UHD player says that the video stream is SDR or gives a minimum 0.000 and maximum 0.000 Nits instead of o.005 -1.000/4.000 Nits as the source file.

So is this a bug ore do I something wrong?

[a5180007]

1. tsMuxer chances the frame rate from 24 too 23,976 by the video stream ab subtitles, bet not de audio. Result the audio is out of sync and the picture stutters.

To change the audio framerate, the audio needs to be re-encoded first (eg via ffmpeg).

2. The HDR is not done correctly in the remux. Result the UHD player says that the video stream is SDR or gives a minimum 0.000 and maximum 0.000 Nits instead of o.005 -1.000/4.000 Nits as the source file.

Please provide link for a 20MB sample of the original m2ts -cut with a hex editor.

[Hombre007]

To change the audio framerate, the audio needs to be re-encoded first (eg via ffmpeg).

Please provide link for a 20MB sample of the original m2ts -cut with a hex editor.

Thanks fore responding.

Fore problem no 1. someone gave me a tip.
“Try forcing the video stream to stay in 24p with the change fps option”..
Must try if this works.

I did a Blue-ray folder remux with the full UHD of Pan (2015), Rambo 3 and T2 and they played without HDR on the Oppo-203 UHD player. Even forcing HDR in the player did not work.
But how do a make a 20mb source file?

[guest]

I posted a way to do this a few years ago. Instead of joining playlists join ssif files. The results are seamless. Only thing I had to do was to fix chapter marks on second half. I’ll see if I can locate it and post link here.


It’s post 9 in this thread


https://forum.redfox.bz/threads/3d-blu-ray-with-multiple-disks.70932/

Hi Hart2hart,

I just thought I'd get back to you to let you know that I still had NO luck getting this to join together successfully...HOWEVER, I acquired a different "version" of Titanic 3D, that was 2 iso's of approx 45Gb each. I joined the 2 SSIF files, and it worked perfectly, thank goodness.

No short black frames between parts.

There was/is obviously something wrong with the versions that most people have tried to join, with not much success.

[hubblec4]

Feature request
Is it possible in demux-mode to extract a sup-stream and the forced captions of this sup-stream simultaneously?

[a5180007]

But how do a make a 20mb source file?

Use a Hex editor e.g. HxD (https://mh-nexus.de/en/hxd/), or use simple tools such as Trunc (https://www.softpedia.com/get/System/System-Miscellaneous/Trunc.shtml).

Which version of tsMuxer are you using ?

[a5180007]

Feature request
Is it possible in demux-mode to extract a sup-stream and the forced captions of this sup-stream simultaneously?

@hubblec4 this is rather the job of a subtitle software.

From the sup in BDSup2Sub, File => Save/Export, check the box to export forced subtitles only.

[a5180007]

So when I add a single layer DV mp4 created by DVDFab it says the track is unknown.

same here with single layer dolby vision mp4 created by dvdfab.

@a5180007 I hope you can make tsmuxer to remux the single layer mp4 to TS or M2TS, that would be really awesome. It would allow Atmos + DV (Even though DVDFAB's single layer remux are probably not true DV, it's still progress.)

Also, it would be nice to have the ability to go from dual-layer mp4 to UHD structure. Now we have to demux the mp4 with dlb_mp4demux and then build the UHD structure with tsmuxer.


@mattmarsden @cogira @imhh11 could you please try latest version nightly-2020-02-24--01-10-05 and report any issue, thanks.

@SeeMoreDigital DoVi descriptors have been added for .ts files. Not for .m2ts files, which stay with HDMV descriptors.

[SeeMoreDigital]

@SeeMoreDigital DoVi descriptors have been added for .ts files. Not for .m2ts files, which stay with HDMV descriptors.Thanks for letting me know...

[koka]

Look tsmuxerCLI (https://github.com/abakum/tsmuxerCLI) is helper for tsMuxeR - like tsMuxerGUI but CLI

If I drag an mpls file into the tsmuxer, the German audio tracks and subtitles are only automatically marked, for example.
tsmuxer.py BD/BDMV/PLAYLIST/00000.mpls+ deu.meta =V + =deu ! - deu.iso

[Bandits]

Is there a reason the Dolby Vision tracks are placed as number 1 and the main video tracks are number 2? The PID's are correct, main 4113 and Dolby Vision 4117, but I would think that they would open in the correct order. I understand they can be reordered but shouldn't the default be the correct order or does the order even matter if a PID is used?

[SeeMoreDigital]

@SeeMoreDigital DoVi descriptors have been added for .ts files. Not for .m2ts files, which stay with HDMV descriptors.Thanks for letting me know...I can confirm that I have just used the 'w64-nightly [2020-02-23--01-10-39]' build to re-mux a couple of 'single layer/stream' Dolby Vision.mp4 files to the .ts container, and they work perfectly with my OPPO (and LG TV combination).

I have also used the same build to re-mux a 'double layer/stream' Dolby Vision.mp4 file to the .ts container, and it works perfectly too ;)

In a few hours time I will try the 'w64-nightly [2020-02-24--01-10-05]' build and report back.


Cheers

[a5180007]

I have also used the same build to re-mux a 'double layer/stream' Dolby Vision.mp4 file to the .ts container, and it works perfectly too ;)

Good to know. HPC and VLC seem to have problems reading the double layer .ts with Dolby Atmos, I haven't found the cause. If anybody can point me to any professionally produced .ts with double layer DV for comparison...

In a few hours time I will try the 'w64-nightly [2020-02-24--01-10-05]' build and report back.

The main change in 02-24 is detection of fragmented MP4. I have tested on few mp4; could anybody report any mp4 not properly detected.

[a5180007]

Is there a reason the Dolby Vision tracks are placed as number 1 and the main video tracks are number 2?

@Bandits this is likely because the first DV stream packet is before the first standard stream packet in the original m2ts. If you can PM me the name of the stream or a link to a 20MB sample, I can have a look.

[SeeMoreDigital]

In a few hours time I will try the 'w64-nightly [2020-02-24--01-10-05]' build and report back.The main change in 02-24 is detection of fragmented MP4. I have tested on few mp4; could anybody report any mp4 not properly detected.Just tried the aforementioned build with the same .mp4 files and I can report that TSmuxer 'stalls' and is unable to detect .mp4 files...

[a5180007]

Just tried the aforementioned build with the same .mp4 files and I can report that TSmuxer 'stalls' and is unable to detect .mp4 files...

@SeeMoreDigital could you please PM me a link to the mp4, thanks.

[SeeMoreDigital]

@SeeMoreDigital could you please PM me a link to the mp4, thanks.

Here you go: -

https://4kmedia.org/lg-earth-dolby-vision-uhd-4k-demo/ [60.000fps]

If you run the 'LG Earth Dolby Vision UHD 4K Demo' file though MediaInfo you'll discover that it's actually an .mp4 contained file, not a .ts file!

After correcting the file extension to .mp4, the 'LG Earth Dolby Vision UHD 4K Demo.mp4' file is not accepted by the 'w64-nightly [2020-02-24--01-10-05]' build.

Cheers

[videoh]

Here you go: Not available at this time:

"Sorry, you can't view or download this file at this time.

Too many users have viewed or downloaded this file recently. Please try accessing the file again later. If the file that you are trying to access is particularly large or is shared with many people, it may take up to 24 hours to be able to view or download the file. If you still can't access a file after 24 hours, contact your domain administrator."

[SeeMoreDigital]

I've also tried re-muxing the following .ts files: -

https://4kmedia.org/lg-dolby-vision-uhd-4k-demo/ [30.000fps]
https://4kmedia.org/lg-dolby-comparison-uhd-4k-demo/ [24.000fps]

The 'w64-nightly [2020-02-24--01-10-05]' build generates significantly smaller re-muxes, which confuses the hell out of the OPPO :eek:


Cheers

[SeeMoreDigital]

Not available at this time:

"Sorry, you can't view or download this file at this time.

Too many users have viewed or downloaded this file recently. Please try accessing the file again later. If the file that you are trying to access is particularly large or is shared with many people, it may take up to 24 hours to be able to view or download the file. If you still can't access a file after 24 hours, contact your domain administrator."Yes... For some reason if you have (and log into) a Gmail account, the files download fine. Bonkers!

I've just downloaded all four of the following again...

Links: -
https://4kmedia.org/lg-earth-dolby-vision-uhd-4k-demo/ [60.000fps] This is actually an .mp4 file, not a .ts file.
https://4kmedia.org/lg-dolby-vision-uhd-4k-demo/ [30.000fps]
https://4kmedia.org/lg-dolby-comparison-uhd-4k-demo/ [24.000fps]
https://4kmedia.org/lg-amaze-dolby-vision-uhd-4k-demo/ [60.000fps] This is actually an .mp4 file, not a .ts file.


Cheers

[imhh11]

thanks a5180007

where can i get 'w64-nightly [2020-02-23--01-10-39]' ? the newest one doesn't accept my DV mp4 as SeeMoreDigital noted

EDIT:
nevermind, found it here:
https://bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly#files

[cogira]

I confirm that the latest version w64-nightly-2020-02-24--01-10-05 does not accept DV dual layer mp4 and Tsmuxer crashes. Have not tested with DV single layer mp4

[a5180007]

Strange... it is working when I build with Visual Studio, but the github cmake version crashes. I'll investigate...

[imhh11]

ohh wow. I remuxed a DV UHD-BD disc to .TS (no mp4muxer) and the file plays properly in DV+ atmos on my Sony x700 bluray player (at least the 10min i watched).....

a5180007 THANK YOU!!!


https://extraimage.net/images/2020/02/24/14e6a991c34072077f509da1f10e7575.png


omplete name : D:\other\DEMOS\DL-DV-ATMOS-REMUX.ts
Format : MPEG-TS
File size : 51.8 GiB
Duration : 2 h 14 min
Overall bit rate mode : Variable
Overall bit rate : 55.1 Mb/s
Maximum Overall bit rate : 35.5 Mb/s

Video #1
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 2 h 14 min
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2

Video #2
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, EL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 2 h 14 min
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : AC-3 MLP FBA 16-ch
Format/Info : Audio Coding 3 + Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Muxing mode : Stream extension
Codec ID : 131
Duration : 2 h 14 min
Bit rate mode : Variable
Bit rate : 640 kb/s
Maximum bit rate : 7 134 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 616 MiB (1%)
Service kind : Complete Main
Number of dynamic objects : 13
Bed channel count : 1 channel
Bed channel configuration : LFE

[Bandits]

@Bandits this is likely because the first DV stream packet is before the first standard stream packet in the original m2ts. If you can PM me the name of the stream or a link to a 20MB sample, I can have a look.

2001 A Space Odyssey
Apocalypse Now (1979) Original
Apocalypse Now (1979) Redux
Apocalypse Now (1979) Final Cut

Also every extra on the same disc's that have Dolby Vision is the same way.

These are all straight from the original disc's. I have tried the CLI and the GUI, using the MPLS or the M2TS. Every way and every clip that has a Dolby Vision, the track is listed as the first track.

I could provide a sample but it seems easily reproducible.

[Stereodude]

ohh wow. I remuxed a DV UHD-BD disc to .TS (no mp4muxer) and the file plays properly in DV+ atmos on my Sony x700 bluray player (at least the 10min i watched).....

a5180007 THANK YOU!!!
How exactly did you do this? Did you demux with some software first or just drag in the decrypted .ts from the UHD BD into this new version of tsMuxer?

[imhh11]

just drag in the decrypted .ts from the UHD BD into this new version of tsMuxer?
yep using w64-nightly [2020-02-23--01-10-39]

[Stereodude]

yep using w64-nightly [2020-02-23--01-10-39]
You get no chapters during playback on the x700 of the resulting .ts correct?

[SeeMoreDigital]

You get no chapters during playback on the x700 of the resulting .ts correct?Correct. As chapter points are not stored within any transport container...

[cogira]

yep using w64-nightly [2020-02-23--01-10-39]

Can you pls upload "w64-nightly [2020-02-23--01-10-39]" somewhere?

[imhh11]

Can you pls upload "w64-nightly [2020-02-23--01-10-39]" somewhere?

all the builds are here:
https://bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly#files

direct link: https://www.mediafire.com/file/oh6volappmjkodb/lnx-nightly-2020-02-23--01-10-39.zip/file

[Taurus]

Can you pls upload "w64-nightly [2020-02-23--01-10-39]" somewhere?

A few posts upstairs you will find everything you need..

[a5180007]

Just tried the aforementioned build with the same .mp4 files and I can report that TSmuxer 'stalls' and is unable to detect .mp4 files...

Ok, I found the problem and submitted the patch.

It will allow to read fragmented mp4 such as this one (http://d3rlna7iyyu8wu.cloudfront.net/DolbyVision_Atmos/mp4/P81_GlassBlowing2_1920x1080%4059.94fps_15200kbps_fmp4.mp4), which tsMuxer currently cannot read.

[a5180007]

Is there a reason the Dolby Vision tracks are placed as number 1 and the main video tracks are number 2? The PID's are correct, main 4113 and Dolby Vision 4117, but I would think that they would open in the correct order. I understand they can be reordered but shouldn't the default be the correct order or does the order even matter if a PID is used?

@Bandits after checking: the order of the video tracks is correct in the created clpi and m2ts descriptors: so no need to reverse or change anything in the meta file.

[FilipeAmadeuO]

@Bandits after checking: the order of the video tracks is correct in the created clpi and m2ts descriptors: so no need to reverse or change anything in the meta file.

I think the problem is only cosmetics on meta file. But why not make it with the right order ?

[Bandits]

@Bandits after checking: the order of the video tracks is correct in the created clpi and m2ts descriptors: so no need to reverse or change anything in the meta file.

I think the problem is only cosmetics on meta file. But why not make it with the right order ?

That's why I was asking if it really mattered.

Would this:

V_MPEGH/ISO/HEVC, "U:\BDMV\PLAYLIST\00089.mpls", track=4117
V_MPEGH/ISO/HEVC, "U:\BDMV\PLAYLIST\00089.mpls", track=4113
A_DTS, "U:\BDMV\PLAYLIST\00089.mpls", timeshift=18ms, track=4352, lang=eng
A_AC3, "U:\BDMV\PLAYLIST\00089.mpls", track=4353, lang=eng
A_AC3, "U:\BDMV\PLAYLIST\00089.mpls", track=4354, lang=fra
A_AC3, "U:\BDMV\PLAYLIST\00089.mpls", track=4355, lang=deu

create the same disc as this:

A_AC3, "U:\BDMV\PLAYLIST\00089.mpls", track=4354, lang=fra
A_AC3, "U:\BDMV\PLAYLIST\00089.mpls", track=4355, lang=deu
V_MPEGH/ISO/HEVC, "U:\BDMV\PLAYLIST\00089.mpls", track=4117
A_DTS, "U:\BDMV\PLAYLIST\00089.mpls", timeshift=18ms, track=4352, lang=eng
A_AC3, "U:\BDMV\PLAYLIST\00089.mpls", track=4353, lang=eng
V_MPEGH/ISO/HEVC, "U:\BDMV\PLAYLIST\00089.mpls", track=4113

solely based on PID's.

If it does then it really doesn't matter. But I would think the PID order would make the order of the track list numbers. Even Mediainfo calls the Dolby Vision track ID 4117 track number 2. tsMuxer always makes it number 1.

[a5180007]

@Bandits tsMuxer adds each video track at beginning of the list, and the other tracks at the end. It then attributes the new PIDs and sorts the list in the order of these new PIDs.

In your example the video tracks would have the same order (because DV tracks are attributed PID 0x1015+), but not the audio tracks.

First scenario will give:

V_MPEGH/ISO/HEVC, "U:\BDMV\PLAYLIST\00089.mpls", track=4113
V_MPEGH/ISO/HEVC, "U:\BDMV\PLAYLIST\00089.mpls", track=4117
A_DTS, "U:\BDMV\PLAYLIST\00089.mpls", timeshift=18ms, track=4352, lang=eng
A_AC3, "U:\BDMV\PLAYLIST\00089.mpls", track=4353, lang=eng
A_AC3, "U:\BDMV\PLAYLIST\00089.mpls", track=4354, lang=fra
A_AC3, "U:\BDMV\PLAYLIST\00089.mpls", track=4355, lang=deu


Second scenario will give:

V_MPEGH/ISO/HEVC, "U:\BDMV\PLAYLIST\00089.mpls", track=4113
V_MPEGH/ISO/HEVC, "U:\BDMV\PLAYLIST\00089.mpls", track=4117
A_AC3, "U:\BDMV\PLAYLIST\00089.mpls", track=4352, lang=fra
A_AC3, "U:\BDMV\PLAYLIST\00089.mpls", track=4353, lang=deu
A_DTS, "U:\BDMV\PLAYLIST\00089.mpls", timeshift=18ms, track=4354, lang=eng
A_AC3, "U:\BDMV\PLAYLIST\00089.mpls", track=4355, lang=eng

[SeeMoreDigital]

Ok, I found the problem and submitted the patch.

It will allow to read fragmented mp4 such as this one (http://d3rlna7iyyu8wu.cloudfront.net/DolbyVision_Atmos/mp4/P81_GlassBlowing2_1920x1080%4059.94fps_15200kbps_fmp4.mp4), which tsMuxer currently cannot read.Just-so-you-know...

I managed to use the 'w64-nightly [2020-02-25--01-10-33]' build to create a .ts stream which worked okay with my OPPO.


Cheers

[a5180007]

@imhh11 @SeeMoreDigital I need to reintroduce part of the HDMV descriptors in the mpeg-ts, as there does not seem to be any adequate descriptor for the PGS subtitles and they are not detected anymore.

Could you please test this build (https://1drv.ms/u/s!AqRZp848Q4jUga5_tdJ5o3tWzrqMHA?e=yg9GcA) and tell me whether Dolby Vision is detected by your player and the subtitles are working ?

[SeeMoreDigital]

@imhh11 @SeeMoreDigital I need to reintroduce part of the HDMV descriptors in the mpeg-ts, as there does not seem to be any adequate descriptor for the PGS subtitles and they are not detected anymore.

Could you please test this build (https://1drv.ms/u/s!AqRZp848Q4jUga5_tdJ5o3tWzrqMHA?e=yg9GcA) and tell me whether Dolby Vision is detected by your player and the subtitles are working ?I'm on my way out in a few minutes but if all goes well I should be able to test in the morning if I have the time...


Cheers

[imhh11]

@imhh11 @SeeMoreDigital I need to reintroduce part of the HDMV descriptors in the mpeg-ts, as there does not seem to be any adequate descriptor for the PGS subtitles and they are not detected anymore.

Could you please test this build (https://1drv.ms/u/s!AqRZp848Q4jUga5_tdJ5o3tWzrqMHA?e=yg9GcA) and tell me whether Dolby Vision is detected by your player and the subtitles are working ?


Everything work on my end with the x700 using that build. Subtitles, DV, Atmos.
But everything (subs included) was already working with nightly-2020-02-23--01-10-39.zip

Also, fast-forwarding works like a charm. MP4 DV always instantly freeze my player when I F-F. plus it looks identical to the MP4 dual layer DV. see: https://slow.pics/c/V994dhhF so this is really a lossless DV remux.

file not supported on the OLED C8 though.

Thank You so much

[a5180007]

Everything work on my end with the x700 using that build. Subtitles, DV, Atmos.
But everything (subs included) was already working with nightly-2020-02-23--01-10-39.zip

@imhh11 thanks for the report. With 2020-02-23--01-10-39 the PGS do not work anymore in ffmpeg players (mplayer, vlc, hpc...) hence the reason for changing. Plus detection of MP4 has been fixed.

Edit:are .m2ts DV (non bluray mode) also working on the x700 ?

file not supported on the OLED C8 though.

Do you have a sample of .ts with PGS, working on your LG C8, that I can analyse ?

[a5180007]

As far as I know, there are at least 2 bugs related to the subtitles in the demux function:

As noted in the other thread, v2.6.11 and v2.6.12 produce often wrong timecodes when demuxing a 3D bluray. (I don't know if that bug affects also the 2D blurays.) Unfortunately, I don't remember what BD is a good example of the problem. V2.6.9 is the last version without that bug, so if you have the sources of that version, it should be easy to find the origin of the bug.


@r0lZ Thanks for providing the buggy sample ! One-line patch for fixing the bug submitted https://github.com/justdan96/tsMuxer/pull/213

The bug appears when joining m2ts (either via mpls or manually) which have different start times/first PTS -which is rare but does happen: tsMuxer was taking into consideration the start time of the first file only.

Edit: the other bug related to 3d-planes has already been fixed.

[imhh11]

@imhh11 thanks for the report. With 2020-02-23--01-10-39 the PGS do not work anymore in ffmpeg players (mplayer, vlc, hpc...) hence the reason for changing. Plus detection of MP4 has been fixed.

Edit:are .m2ts DV (non bluray mode) also working on the x700 ?



Do you have a sample of .ts with PGS, working on your LG C8, that I can analyse ?

I did not try m2ts but I will.

here's a DV TS sample that wont play on my C8.

https://drive.google.com/file/d/19dhHs3hz_R82kfj_X-UU1qfq0frUQcGD/view?usp=sharing


I'll try to find one that works.

[a5180007]

I know tsMuxer can mux to a sup from srt but is has a bug with italics.
If I remember right it has it an all earlier verions aswell including the tsMuxerGUI-Nightly-2020-02-05--01-09-49.
Look at these two screendumps:
https://imgur.com/a/OiZA8F8


@varekai Bug should be solved. Please try latest bintray build.

[r0lZ]

@r0lZ Thanks for providing the buggy sample ! One-line patch for fixing the bug submitted https://github.com/justdan96/tsMuxer/pull/213

The bug appears when joining m2ts (either via mpls or manually) which have different start times/first PTS -which is rare but does happen: tsMuxer was taking into consideration the start time of the first file only.

Edit: the other bug related to 3d-planes has already been fixed.
Thanks for the fix !

And credits for providing the sample should go to Nico8583. He has been able to remember what BD caused that problem, and he gave me the sample. I was just an intermediary.

[Nico8583]

Thanks for the fix !

And credits for providing the sample should go to Nico8583. He has been able to remember what BD caused that problem, and he gave me the sample. I was just an intermediary.
You're welcome :) I'm happy to see tsMuxeR development is back, it's a good news ! Thanks for the work ;)

[varekai]

@varekai Bug should be solved. Please try latest bintray build.
Wow! Excellent!
I got mad respect for all your hard work on this essential tool!!
How could we do without tsMuxer?!
Thank you so much!

Here 2 new screendumps:
https://imgur.com/a/8380z3Y
As you can see there is a small paragraph space formatting difference between easySUP and tsMuxer.
Font used with tsMuxer is Segoe UI Normal Size 58 Bottom of screen 163.
With easySUP it's size 78 and bottom 152.
The .srt used is set to encoding UTF-8-BOM.

This small formatting difference is only noticeable when comparing the two screendumps.
When watching a video I probably won't notice this.

Best regards,
varekai

[baker99uk]

Excellent work, I can now play Dual Layer rips of my Dolby Vision disks on my X700. Single Layer works on the shield plex app too, without Atmos unfortunately though. If tsmuxer could support Truehd without an ac3 core I think Atmos would also work on the shield, fingers crossed that can get added soon (or plex add ac3 core support).

Thanks again for all your hard work.

[cogira]

Latest build w64-nightly-2020-02-29--01-11-32 tsmuxer crashes when tryng to load DV mp4 files (either single layer or double layer)

[mattmarsden]

Any chance of allowing thd without embedded ac3? Plex doesnt seem to like thd with embedded ac3.

[a5180007]

Latest build w64-nightly-2020-02-29--01-11-32 tsmuxer crashes when tryng to load DV mp4 files (either single layer or double layer)

@cogira I've tried (on W64) the four MP4 samples from https://developer.dolby.com/tools-media/sample-media/video-streams/dolby-vision-streams/, they all work. Where can I find your sample ?

Edit: same for the five MP4 samples from https://www.demolandia.net/4k-video-test/dolby-vision/page-1.html

[a5180007]

I'm on my way out in a few minutes but if all goes well I should be able to test in the morning if I have the time...

@SeeMoreDigital any chance you test the build ? I'd like to push the fix.

Anybody has a mpeg-ts sample with PGS working directly on a tv ?

[imhh11]

@a5180007

1-M2TS DV files also work on the x700.

2-this DV TS file plays on my C8. The TV can see that there's a subtitle track but it wont show up.
https://drive.google.com/open?id=16CvL9XApTHqDiXjpsLOXcROpLd3LA_n_

3- this file is missing the fps and is 61mb smaller after remuxed with tsMuxer:
https://drive.google.com/open?id=1WgPnPLaWDytiFwuvPGbR83d3kdMz3_in

4- this one goes from dvhe.05.07 to dvhe.08.06 when remuxed in tsMuxer
https://drive.google.com/open?id=1pZoT6npafsJ5FacrBpamEs9MCYVVBdCy

[cogira]

@cogira I've tried (on W64) the four MP4 samples from https://developer.dolby.com/tools-media/sample-media/video-streams/dolby-vision-streams/, they all work. Where can I find your sample ?

Edit: same for the five MP4 samples from https://www.demolandia.net/4k-video-test/dolby-vision/page-1.html

I have 3 movies, Gemini man, Spiderman homecoming and Rocketman original DV UHD discs. I have done, for each movie, DV mp4 double layer using Dolby mp4muxer, DV mp4 double layer using dvdfab, DV sinle layer using dvdfab.
All these mp4 can be loaded in tsmuxer version w64-nightly-2020-02-23--01-10-39
Only mp4 made using Dolby mp4muxer can be loaded in tsmuxer version w64-nightly-2020-02-29--01-11-32.
All Mp4 made with dvdfab crash tsmuxer version w64-nightly-2020-02-29--01-11-32 but do not crash tsmuxer version w64-nightly-2020-02-23--01-10-39.
Unfortunately I dont knw how to cut a sample from my mp4 files. If someone can help on this I will be very glad to submit the samples.
You are doing an inestimable work, Thank you very much.
:):):):):)

[a5180007]

Unfortunately I dont knw how to cut a sample from my mp4 files. If someone can help on this I will be very glad to submit the samples.

@cogira you can't cut a MP4 the same way as a TS. You have to cut the streams first before muxing them to MP4.

[cogira]

@cogira you can't cut a MP4 the same way as a TS. You have to cut the streams first before muxing them to MP4.

Thanks I am not skilled for that.
I don't understand why all my mp4 are loaded in version w64-nightly-2020-02-23--01-10-39, whilst only those made with dvdfab crash the version w64-nightly-2020-02-29--01-11-32.

[SeeMoreDigital]

@SeeMoreDigital any chance you test the build ? I'd like to push the fix.Sorry not at the moment :(

[Grencola]

I have 3 movies, Gemini man, Spiderman homecoming and Rocketman original DV UHD discs. I have done, for each movie, DV mp4 double layer using Dolby mp4muxer, DV mp4 double layer using dvdfab, DV sinle layer using dvdfab.
All these mp4 can be loaded in tsmuxer version w64-nightly-2020-02-23--01-10-39
Only mp4 made using Dolby mp4muxer can be loaded in tsmuxer version w64-nightly-2020-02-29--01-11-32.
All Mp4 made with dvdfab crash tsmuxer version w64-nightly-2020-02-29--01-11-32 but do not crash tsmuxer version w64-nightly-2020-02-23--01-10-39.
Unfortunately I dont knw how to cut a sample from my mp4 files. If someone can help on this I will be very glad to submit the samples.
You are doing an inestimable work, Thank you very much.
:):):):):)
try loading the largest m2ts file from the bdmv/streams folder of your uhd disc directly into tsmuxer nightly and convert that into a ts.

[a5180007]

1-M2TS DV files also work on the x700.
Great !

2-this DV TS file plays on my C8. The TV can see that there's a subtitle track but it wont show up.
Thanks, I'll analyse the descriptors. What about the file produced by git-8bf5813, does the TV see the subtitle as well ?

Edit: ok, so the descpritors are identical to the latest bintray build outputs -and the subtitle is not detected by e.g. VLC or HPC. Which is the reason of my fork git-8bf5813...

3- this file is missing the fps and is 61mb smaller after remuxed with tsMuxer
No real change since 2.6.12 here... This is the way tsMuxer muxes the mpeg-ts, the buffer management is incorrect and most of the filler packets for CBR transmission are missing.

Edit: what do you mean by "the file is missing the fps" ? Mediainfo shows an fps of 23.976 for the resulting ts file.

4- this one goes from dvhe.05.07 to dvhe.08.06 when remuxed in tsMuxer
https://drive.google.com/open?id=1pZoT6npafsJ5FacrBpamEs9MCYVVBdCy
Seems to me that profile 08 is correct : color primaries is BT.2020. The way I understand the DV profiles, in case of profile 5 there would be no compatible color primaries (i.e. 2="unspecified" in the HEVC VUI). Cf. https://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-profiles-levels.pdf . If this is incorrect then I would have to change the way profiles are detected.

Edit: as for the level: it depends on the video size/fps. For the moment it is systematically put at level 6, I'll have to work on that.

[Bgalakazam]

.ts file with DV and TrueHD Atmos playing back on X700
Tested and works properly with PGS and fast forwarding. This is amazing. As far as I am concerned my DV needs are fully met. Thank you to all that made this possible.

[imhh11]

Great !


Thanks, I'll analyse the descriptors. What about the file produced by git-8bf5813, does the TV see the subtitle as well ?

Edit: ok, so the descpritors are identical to the latest bintray build outputs -and the subtitle is not detected by e.g. VLC or HPC. Which is the reason of my fork git-8bf5813...



Ok, I thought I used your fork git-8bf5813.
now I just tried again but the same result.

p-s I'm still using the very first working version because some of my MP4 are not recognized by the new versions.







No real change since 2.6.12 here... This is the way tsMuxer muxes the mpeg-ts, the buffer management is incorrect and most of the filler packets for CBR transmission are missing.

Edit: what do you mean by "the file is missing the fps" ? Mediainfo shows an fps of 23.976 for the resulting ts file.


bad wording, sorry for my English.

mmm strange, on my end, MediaInfo shows:
https://extraimage.net/images/2020/03/01/9c2a891d1960894e21505e58a1985b3a.png

(even though the file play properly on the TV and on pc.)

[imhh11]

.ts file with DV and TrueHD Atmos playing back on X700
Tested and works properly with PGS and fast forwarding. This is amazing. As far as I am concerned my DV needs are fully met. Thank you to all that made this possible.

my only issue is that we can only watch one movie without having to reboot the player.

Once you stop or finish a TS DV movie, you get a picture full of weird colors on anything you try to playback. Only rebooting the player fixes the issue.
Very strange bug, only happens with TS DV file created by tsMuxer... never happened with DV MP4 or DV bluray disc.

[cogira]

my only issue is that we can only watch one movie without having to reboot the player.

Once you stop or finish a TS DV movie, you get a picture full of weird colors on anything you try to playback. Only rebooting the player fixes the issue.
Very strange bug, only happens with TS DV file created by tsMuxer... never happened with DV MP4 or DV bluray disc.

I have exactly the same problem with sony x700 and Lg C8

[a5180007]

Very strange bug, only happens with TS DV file created by tsMuxer... never happened with DV MP4 or DV bluray disc.

@imhh11 could you please advise which ts have/do not have this bug:
- Professional ts, e.g. dolby-vision-lg-(www.demolandia.net).ts (https://www.demolandia.net/downloads.html?id=1039472921)
- latest Bintray 01-03 tsMuxer
- my fork git-8bf5813

[SeeMoreDigital]

Hi @a5180007,

I downloaded the 'dolby-vision-lg-(www.demolandia.net).ts (https://www.demolandia.net/downloads.html?id=1039472921)' file and can confirm it plays perfectly on my LG television.

I've also just re-muxed it using the 'git-9670fd6' build and it makes my LG television freak out (and there's no audio) :scared:

Anyway... I'm around for a couple of hours. Which new test build would you like me to use?

[a5180007]

Which new test build would you like me to use?

As per previous post, could you please try this build (https://1drv.ms/u/s!AqRZp848Q4jUga5_tdJ5o3tWzrqMHA?e=yg9GcA), thanks.

Edit: there is no DoVi descriptor in dolby-vision-lg-(www.demolandia.net).ts -just the standard HEVC decriptor. Does it plays with Dolby Vision on your x700 ? In which case, why bother with the DoVi descriptor...

[imhh11]

@imhh11 could you please advise which ts have/do not have this bug:
- Professional ts, e.g. dolby-vision-lg-(www.demolandia.net).ts (https://www.demolandia.net/downloads.html?id=1039472921)
- latest Bintray 01-03 tsMuxer
- my fork git-8bf5813

it only happens with all the DV TS remux made from UHD-BD m2ts (and dv mp4 remux). and with all the tsMuxer version

all the professional TS remuxed(or untouched) in any of the tsMuxer versions don't cause this bug.

[SeeMoreDigital]

As per previous post, could you please try this build (https://1drv.ms/u/s!AqRZp848Q4jUga5_tdJ5o3tWzrqMHA?e=yg9GcA), thanks.
I can confirm that the re-mux with 'git-8bf5813' plays slightly better on my LG television but it's still garbled and there's no audio.

The OPPO appears to play the re-mux one key frame at a time (with audio).


Cheers

[cogira]

my only issue is that we can only watch one movie without having to reboot the player.

Once you stop or finish a TS DV movie, you get a picture full of weird colors on anything you try to playback. Only rebooting the player fixes the issue.
Very strange bug, only happens with TS DV file created by tsMuxer... never happened with DV MP4 or DV bluray disc.

@a5180007,
In makemkv forum someone says this is a tsmuxer problem.
I dont know idìf they are right but, if this problem is sorted out, tsmuxer will be the first and only software capable for Dv.

[SeeMoreDigital]

@a5180007,
if this problem is sorted out, tsmuxer will be the first and only software capable for Dv.Just-so-you-know...

Many of us have already used these new 'open-source' TSmuxer builds to successfully re-mux our 4K UHD Blu-ray disc back-ups, with or without Dolby Vision!

Without knowing more detail about your sources and what you're intending to do I don't see how you can be helped!

[a5180007]

The OPPO appears to play the re-mux one key frame at a time (with audio).

Thanks @SeeMoreDigital. And does dolby-vision-lg-(www.demolandia.net).ts play with Dolby Vision on your Oppo ?

[SeeMoreDigital]

Thanks @SeeMoreDigital. And does dolby-vision-lg-(www.demolandia.net).ts play with Dolby Vision on your Oppo ?Yes, the source .ts file plays fine on both my OPPO and LG television.

[a5180007]

Yes, the source .ts file plays fine on both my OPPO and LG television.

Ok then, I'll do a build without the DoVi descriptors for testing...

Edit: ok, so after lots of trials and errors, I come to the conclusion that there seems to be no TS descriptor for PGS. And if we put back the HDMV registration descriptor to read PGS in TS would break DV compatibility with standalone players. Same for AC3/TrueHD.

So you can't have everything: PGS and interleaved AC3/TrueHD are HDMV streams and must be muxed in m2ts.

And there is no TS or HDMV descriptor for TrueHD (without AC3), so no way to include it in tsMuxer.

[Bgalakazam]

What is the issue with PGS and .TS? I was able to show PGS subs on the Sony X700 without issue from the 3/1 nightly build. Of course, my LG C8 doesn't play the generated .TS file, but I don't care as I won't have lossless TrueHD even if it did.

Thank you for your work, by the way. You solved what I was trying to do for over a year - DV and TrueHD Atmos from file playback.

[a5180007]

What is the issue with PGS and .TS? I was able to show PGS subs on the Sony X700 without issue from the 3/1 nightly build. Of course, my LG C8 doesn't play the generated .TS file, but I don't care as I won't have lossless TrueHD even if it did.

@Bgalakazam the ts (resp. m2ts) is formed of packets of 188 bytes (resp. 192 bytes). There is a PMT (program map table) packet at least every 100ms, detailing the tracks via decriptors registered with various organisations.

Edit : cf. https://en.wikipedia.org/wiki/Program-specific_information#PMT_(Program_map_specific_data)

The issue is that the PGS in TS don't play anymore in ffmpeg players (VLC, HPC, MPlayer...) without the HDMV descriptors. And if I reintroduce the HDMV descriptors (which is non-standard for TS), DV won't work anymore in the standalone players.

Which means that for PC we have to use m2ts for PGS subtitles.

[SeeMoreDigital]

Edit: ok, so after lots of trials and errors, I come to the conclusion that there seems to be no TS descriptor for PGS. And if we put back the HDMV registration descriptor to read PGS in TS would break DV compatibility with standalone players. Same for AC3/TrueHD.

So you can't have everything: PGS and interleaved AC3/TrueHD are HDMV streams and must be muxed in m2ts.

And there is no TS or HDMV descriptor for TrueHD (without AC3), so no way to include it in tsMuxer.So I guess the best we could expect is having an 'open source' build of TSmuxer that can successfully re-mux the 'dolby-vision-lg-(www.demolandia.net).ts (https://www.demolandia.net/downloads.html?id=1039472921)' file ;)

[Stereodude]

The issue is that the PGS in TS don't play anymore in ffmpeg players (VLC, HPC, MPlayer...) without the HDMV descriptors. And if I reintroduce the HDMV descriptors (which is non-standard for TS), DV won't work anymore in the standalone players.

Which means that for PC we have to use m2ts for PGS subtitles.
So is that then really an FFMPEG issue that should be corrected there? Who isn't following the spec(s), or is this a gray area in the spec(s)?

[a5180007]

So is that then really an FFMPEG issue that should be corrected there? Who isn't following the spec(s), or is this a gray area in the spec(s)?

@Stereodude PGS and AC3/trueHD are covered by the Blu-ray format specifications. But in TS, yes it is a grey area not covered by any standard (H.222.0, ATSC, DVB...) So I guess If you ask guys at ffmpeg nobody will want to implement it.

[SeeMoreDigital]

So, if I get this right...

What some people would like TSmuxer to do is have the ability to mux: HEVC video with Dolby Vision along with Dolby TrueHD audio and SUP subtitles into the .TS [188 byte packet] container, instead of into the .m2ts [192 byte packet] container?

If so... What's the point of doing this?


Cheers

[a5180007]

So I guess the best we could expect is having an 'open source' build of TSmuxer that can successfully re-mux the 'dolby-vision-lg-(www.demolandia.net).ts (https://www.demolandia.net/downloads.html?id=1039472921)' file ;)

Ok so I found the issue with the audio in this stream. The E-AC3 stream type descriptor in M2TS is 0x84, but it needs to be changed to 0x87 for TS !! https://en.wikipedia.org/wiki/Program-specific_information#Elementary_stream_types

If so... What's the point of doing this?
Good question...

[Stereodude]

If so... What's the point of doing this?
Isn't it to have a file with 2 layer Dolby Vision with Atmos (True-HD) audio that's fully playable on the Sony x700 UHD blu-ray player (and others?) enabling DV UHD BD "rips"?

Isn't the Oppo (and clones) the only consumer device capable of playing such content with proper DV 2 layer decoding and lossless Atmos (prior to making such .TS files for the Sony)?

[SeeMoreDigital]

Isn't it to have a file with 2 layer Dolby Vision with Atmos (True-HD) audio that's fully playable on the Sony x700 UHD blu-ray player (and others?) enabling DV UHD BD "rips"?
I dunno... But this would make more sense!

Okay then, so: HEVC video with 2-layer Dolby Vision along with Dolby TrueHD audio and SUP subtitles within the .TS [188 byte packet] container... I haven't tried doing this :eek:

[Stereodude]

I dunno... But this would make more sense!

Okay then, so: HEVC video with 2-layer Dolby Vision along with Dolby TrueHD audio and SUP subtitles within the .TS [188 byte packet] container... I haven't tried doing this :eek:
Isn't that what Bgalakazam and imhh11 confirmed working on the x700 with one of the recent nightly builds?

I think imhh11 said it worked in a M2TS also.

[SeeMoreDigital]

Isn't that what Bgalakazam and imhh11 confirmed working on the x700 with one of the recent nightly builds?

I think imhh11 said it worked in a M2TS also.I guess we could do with confirmation about who's players support 'HEVC video with 2-layer Dolby Vision.M2TS' file playback. And who's players only support 'HEVC video with 2-layer Dolby Vision.TS' file playback!

[Grencola]

So, if I get this right...

What some people would like TSmuxer to do is have the ability to mux: HEVC video with Dolby Vision along with Dolby TrueHD audio and SUP subtitles into the .TS [188 byte packet] container, instead of into the .m2ts [192 byte packet] container?

If so... What's the point of doing this?


Cheers
that would be amazing! It's so devices like the nvidia shield pro can playback movies in dolby vision with lossless true-hd atmos. it doesn't like when there's an ac3 core like in blurays. core-less thd atmos like in mkv play fine, but no dv obviously.

[baker99uk]

I guess we could do with confirmation about who's players support 'HEVC video with 2-layer Dolby Vision.M2TS' file playback. And who's players only support 'HEVC video with 2-layer Dolby Vision.TS' file playback!

Using the w64-nightly-2020-03-02--01-10-57 build my X700 plays 2-layer DV in ts but DV is not triggered in m2ts, I hope that's what you were asking.

[SeeMoreDigital]

Using the w64-nightly-2020-03-02--01-10-57 build my X700 plays 2-layer DV in ts but DV is not triggered in m2ts, I hope that's what you were asking.Yep.

Apart from the 2-layer Dolby Vision HEVC video stream, what other streams are in your .ts file back-ups?

[baker99uk]

General
ID : 0 (0x0)
Complete name : I:\Originals\00001.m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 54.1 GiB
Duration : 1 h 59 min
Overall bit rate mode : Variable
Overall bit rate : 65.1 Mb/s
Maximum Overall bit rate : 109 Mb/s

Video #1
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 h 59 min
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2
Maximum Content Light Level : 2013 cd/m2
Maximum Frame-Average Light Level : 393 cd/m2

Video #2
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 h 59 min
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2

Audio #1
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : AC-3 MLP FBA 16-ch
Format/Info : Audio Coding 3 + Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Muxing mode : Stream extension
Codec ID : 131
Duration : 1 h 59 min
Bit rate mode : Variable
Bit rate : 640 kb/s
Maximum bit rate : 8 469 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 545 MiB (1%)
Service kind : Complete Main
Number of dynamic objects : 11
Bed channel count : 1 channel
Bed channel configuration : LFE

Audio #2
ID : 4353 (0x1101)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 1 h 59 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : -8 ms
Stream size : 545 MiB (1%)
Service kind : Complete Main

Audio #3
ID : 4354 (0x1102)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 1 h 59 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : -8 ms
Stream size : 545 MiB (1%)
Service kind : Complete Main

Audio #4
ID : 4355 (0x1103)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 1 h 59 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : -8 ms
Stream size : 545 MiB (1%)
Service kind : Complete Main

Audio #5
ID : 4356 (0x1104)
Menu ID : 1 (0x1)
Format : DTS XLL
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Muxing mode : Stream extension
Codec ID : 134
Duration : 1 h 59 min
Bit rate mode : Variable
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossless

Audio #6
ID : 4357 (0x1105)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 1 h 59 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : -8 ms
Stream size : 545 MiB (1%)
Service kind : Complete Main

Audio #7
ID : 4358 (0x1106)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 1 h 59 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : -8 ms
Stream size : 545 MiB (1%)
Service kind : Complete Main

Audio #8
ID : 4359 (0x1107)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 1 h 59 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : -8 ms
Stream size : 545 MiB (1%)
Service kind : Complete Main

Audio #9
ID : 4360 (0x1108)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 1 h 59 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : -8 ms
Stream size : 545 MiB (1%)
Service kind : Complete Main

Audio #10
ID : 4361 (0x1109)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 1 h 59 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : -8 ms
Stream size : 545 MiB (1%)
Service kind : Complete Main

Text #1
ID : 4768 (0x12A0)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144

Text #2
ID : 4769 (0x12A1)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144


......



That's the mediainfo for the input m2ts, although I actually imported the playlist not the m2ts directly, I deselected everything except the English tracks. The output m2ts only reports a single layer though, maybe I'm not using the correct tsmuxer build?

[imhh11]

That's the mediainfo for the input m2ts, although I actually imported the playlist not the m2ts directly, I deselected everything except the English tracks. The output m2ts only reports a single layer though, maybe I'm not using the correct tsmuxer build?
only this test build can make DV m2ts. And yes, it plays on the x700

https://onedrive.live.com/?authkey=%21ALXSeaN7Vs66jBw&cid=D488433CCEA759A4&id=D488433CCEA759A4%2122399&parId=root&action=locate

but TS or m2ts, i dont really care. As long i can watch DV+ atmos via usb or my network, i'm happy...And right now I'm very happy :D

Complete name : D:\test.split.1.m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 920 MiB
Duration : 2 min 0 s
Overall bit rate mode : Variable
Overall bit rate : 64.0 Mb/s
Maximum Overall bit rate : 35.5 Mb/s

Video #1
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible
Codec ID : 36
Duration : 2 min 0 s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 745 cd/m2
Maximum Frame-Average Light Level : 47 cd/m2

Video #2
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, EL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 2 min 0 s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2

[baker99uk]

[QUOTE=imhh11;1902629]only this test build can make DV m2ts. And yes, it plays on the x700

https://onedrive.live.com/?authkey=%21ALXSeaN7Vs66jBw&cid=D488433CCEA759A4&id=D488433CCEA759A4%2122399&parId=root&action=locate

but TS or m2ts, i dont really care. As long i can watch DV+ atmos via usb or my network, i'm happy...And right now I'm very happy :D

Excellent, I'll test this version too in the morning. I'm very happy that I can finally play DV rips on my X700 as well.

[cogira]

Yes, .ts or .m2ts on the sony x700 they have the problem exposed in post 470 and 471, that is very annoying.
Also could someone explain why mediainfo reports that both videotracks are dolby vision?

17223

[imhh11]

Yes, .ts or .m2ts on the sony x700 they have the problem exposed in post 470 and 471, that is very annoying.
Also could someone explain why mediainfo reports that both videotracks are dolby vision?

17223

I was wondering about that too.

@a5180007
Could it be possible to do a test build that would put DV descriptor only on the DV layer just like the mp4muxer.
maybe that's the reason why it doesn't work on my LG C8?

Thank's

mp4muxer:

Complete name : G:\4k\Terminator.Dark.Fate.2019.DV.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (isom/mp42/dby1)
File size : 57.0 GiB
Duration : 2 h 8 min
Overall bit rate : 63.7 Mb/s
Encoded date : UTC 2020-01-18 23:49:16
Tagged date : UTC 2020-01-18 23:49:16

Video #1
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : hev1
Codec ID/Info : High Efficiency Video Coding
Duration : 2 h 8 min
Bit rate : 48.7 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.245
Stream size : 43.6 GiB (76%)
Default : No
Encoded date : UTC 2020-01-18 23:00:19
Tagged date : UTC 2020-01-18 23:51:19
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Level : 446 cd/m2
Codec configuration box : hvcC

Video #2
ID : 2
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, EL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : dvhe
Codec ID/Info : High Efficiency Video Coding with Dolby Vision
Duration : 2 h 8 min
Bit rate : 5 130 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.103
Stream size : 4.59 GiB (8%)
Default : No
Encoded date : UTC 2020-01-18 23:00:19
Tagged date : UTC 2020-01-18 23:51:19
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Codec configuration box : hvcC+dvcC




tsMuxer:

Complete name : I:\Gemini.Man.2019.DV.60FPS.ts
Format : MPEG-TS
File size : 75.6 GiB
Duration : 1 h 57 min
Overall bit rate mode : Variable
Overall bit rate : 92.5 Mb/s
Maximum Overall bit rate : 35.5 Mb/s

Video #1
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 h 57 min
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0010 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 5180 cd/m2
Maximum Frame-Average Light Level : 1577 cd/m2

Video #2
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, EL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 h 57 min
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0010 cd/m2, max: 1000 cd/m2

[SeeMoreDigital]

but TS or m2ts, i dont really care. As long i can watch DV+ atmos via usb or my network, i'm happy...And right now I'm very happy :DWell it is worth caring about because from what I'm able to determine, your Sony player (along with every other hardware player) is unable to play 'HEVC video with 2-layer Dolby Vision placed within the .M2TS container. Which means the .TS [188 byte packet] container is your only option.

And it's the same with TV's that support Dolby Vision...

[baker99uk]

Using this input file

General
ID : 0 (0x0)
Complete name : Atmos-DV.m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 68.3 GiB
Duration : 1 h 50 min
Overall bit rate mode : Variable
Overall bit rate : 88.2 Mb/s
Maximum Overall bit rate : 109 Mb/s

Video #1
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 h 50 min
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Level : 863 cd/m2

Video #2
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 h 50 min
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2

Audio #1
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : AC-3 MLP FBA 16-ch
Format/Info : Audio Coding 3 + Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Muxing mode : Stream extension
Codec ID : 131
Duration : 1 h 50 min
Bit rate mode : Variable
Bit rate : 448 kb/s
Maximum bit rate : 7 437 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 355 MiB (1%)
Service kind : Complete Main
Number of dynamic objects : 11
Bed channel count : 1 channel
Bed channel configuration : LFE

Text #1
ID : 4768 (0x12A0)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144



With the m2ts version of tsmuxer works perfectly with Atmos and DV on my X700, the output file mediainfo is

Format : BDAV
Format/Info : Blu-ray Video
File size : 68.3 GiB
Duration : 1 h 50 min
Overall bit rate mode : Variable
Overall bit rate : 88.3 Mb/s
Maximum Overall bit rate : 35.5 Mb/s

Video #1
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 h 50 min
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Level : 863 cd/m2

Video #2
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, EL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 h 50 min
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
....

[SeeMoreDigital]

Using this input file

Format : BDAV
Format/Info : Blu-ray Video
File size : 68.3 GiB
Duration : 1 h 50 min
Overall bit rate mode : Variable
Overall bit rate : 88.3 Mb/s
Maximum Overall bit rate : 35.5 Mb/s

With the m2ts version of tsmuxer works perfectly with Atmos and DV on my X700, the output file mediainfo isThe first three lines of the MediaInfo report are missing!!!

[imhh11]

your Sony player (along with every other hardware player) is unable to play 'HEVC video with 2-layer Dolby Vision

what ?
I confirmed two times that my sony player can play HEVC dual-layer DV M2TS file (or TS or MP4).

[baker99uk]

The first three lines of the MediaInfo report are missing!!!

Sorry trying to fit things in the forums character limit, I should have used two separate posts (I cut off a few PGS tracks too which hopefully doesn't matter)

General
ID : 1 (0x1)
Complete name : Atmos-DV.m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 68.3 GiB
Duration : 1 h 50 min
Overall bit rate mode : Variable
Overall bit rate : 88.3 Mb/s
Maximum Overall bit rate : 35.5 Mb/s

Video #1
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 h 50 min
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Level : 863 cd/m2

Video #2
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, EL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 h 50 min
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 1000 cd/m2

Audio #1
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : AC-3 MLP FBA 16-ch
Format/Info : Audio Coding 3 + Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Muxing mode : Stream extension
Codec ID : 131
Duration : 1 h 50 min
Bit rate mode : Variable
Bit rate : 448 kb/s
Maximum bit rate : 7 437 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 355 MiB (1%)
Language : English
Service kind : Complete Main
Number of dynamic objects : 11
Bed channel count : 1 channel
Bed channel configuration : LFE

Audio #2
ID : 4353 (0x1101)
Menu ID : 1 (0x1)
Format : E-AC-3
Format/Info : Enhanced AC-3
Commercial name : Dolby Digital Plus
Format profile : Blu-ray Disc
Muxing mode : Stream extension
Codec ID : 132
Duration : 1 h 50 min
Bit rate mode : Constant
Bit rate : 768 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : 1 ms
Stream size : 608 MiB (1%)
Service kind : Complete Main

Audio #3
ID : 4354 (0x1102)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 1 h 50 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : 1 ms
Stream size : 507 MiB (1%)
Service kind : Complete Main

Audio #4
ID : 4355 (0x1103)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 1 h 50 min
Bit rate mode : Constant
Bit rate : 192 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : 1 ms
Stream size : 152 MiB (0%)
Service kind : Complete Main

Text #1
ID : 4768 (0x12A0)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144

[BloodyRipper]

On my ancient computer (P3 without SSE2, WinXP) the last working tsMuxeR version used to be 2.6.12 from 2014.

Your builds are different. The GUI does not work (as expected), but the CLI executable works like a charm.
I might have good news for you after all.

https://files.catbox.moe/5dxxih.PNG
I managed to make a static build of the last Qt version that supports Windows XP (namely, 5.6.3) and then build the GUI with it. As you can see, it works okay on my P3 with Windows XP.

This is still a work in progress, since some stuff doesn't really work (translations and sounds - minor things, but still), but if I get everything sorted out, I don't see any hurdles in providing the GUI executable "for ancient systems" in the nightly builds. This particular build variant should run on all 32-bit processors regardless of the supported instruction set extensions, since I explicitly disable emitting them in the compiler commandline.

[cogira]

Look here;
17224

[SeeMoreDigital]

what ?
I confirmed two times that my sony player can play HEVC dual-layer DV M2TS file (or TS or MP4).Hmmm...

If '2-layer Dolby Vision.M2TS' files work with your Sony via a USB drive, why not simply use the original .M2TS file that's on the 4K UHD disc?

Indeed, can you confirm that the original '2-layer Dolby Vision.M2TS' files work okay with your Sony player via a USB drive?

And can people with Panasonic 4K UHD players confirm that they work via a USB drive too?

I can confirm that original '2-layer Dolby Vision.M2TS' files only play in HDR on my OPPO via a USB drive. And don't play at all on my LG television.

[baker99uk]

the original m2ts files from a UHD only play in HDR on the X700, if you run these files through tsmuxer then the ts files play with Dolby Vision, using the special m2ts build of tsmuxer the original m2ts is altered in some way and also strangely plays with Dolby Vision

[cogira]

Hmmm...

If '2-layer Dolby Vision.M2TS' files work with your Sony via a USB drive, why not simply use the original .M2TS file that's on the 4K UHD disc?

Indeed, can you confirm that the original '2-layer Dolby Vision.M2TS' files work okay with your Sony player via a USB drive?

And can people with Panasonic 4K UHD players confirm that they work via a USB drive too?

I can confirm that original '2-layer Dolby Vision.M2TS' files don't work via a USB drive with my OPPO or with my LG television.

I confirm what @imhh11 says as I also own a sony X700.

[SeeMoreDigital]

the original m2ts files from a UHD only play in HDR on the X700, if you run these files through tsmuxer then the ts files play with Dolby Vision...Indeed... That's the same behaviour with my OPPO. But @imhh11 is saying the following: - what ?
I confirmed two times that my sony player can play HEVC dual-layer DV M2TS file (or TS or MP4).

So what is actually correct?

[imhh11]

@SeeMoreDigital did you even follow the recent discussion here ?? https://forum.doom9.org/showpost.php?p=1902180&postcount=431

M2TS or TS DV remux is only possible since nightly-2020-02-23--01-10-39.zip.

but MP4 Dolby vision Dual layer always been supported by the x700.


And why would I confirm original m2ts playback on the x700 in a tsmuxer thread ?? we are all talking about tsmuxer remux here.

I guess my english is worse than i thought.

[SeeMoreDigital]

@SeeMoreDigital did you even follow the recent discussion here ?? https://forum.doom9.org/showpost.php?p=1902180&postcount=431

M2TS or TS DV remux is only possible since nightly-2020-02-23--01-10-39.zip.

but MP4 Dolby vision Dual layer always been supported by the x700.
According to your linked post, the MediaInfo report states that the ''2-layer Dolby Vision' re-mux is placed within the .TS container, not the .m2ts container!

Cheers

[imhh11]

According to your linked post, the MediaInfo report states that the ''2-layer Dolby Vision' re-mux is placed within the .TS container, not the .m2ts container!

Cheers

YES and I confirmed m2ts DV playback just a couple post below... smh

[SeeMoreDigital]

YES and I confirmed m2ts DV playback just a couple post below... smh
Can you please confirm your finding again?

[imhh11]

Can you please confirm your finding again?

lol, I can't tell if you are joking or not now.

let me resume what works and what doesn't work:

-Since nightly-2020-02-23--01-10-39.zip, tsmuxer allow to remux directly a UHD-BD m2ts to DV dual layer TS that works on the X700 (and you confirmed the oppo as well). This build and all the newer one cannot make m2ts DV.

- this fork build https://onedrive.live.com/?authkey=%21ALXSeaN7Vs66jBw&cid=D488433CCEA759A4&id=D488433CCEA759A4%2122399&parId=root&action=locate
allow DV m2ts and TS and both container trigger DV properly on my x700 (your oppo too probably). confirmed here:
https://forum.doom9.org/showpost.php?p=1902472&postcount=461
&
https://forum.doom9.org/showpost.php?p=1902629&postcount=497

My english is not great, I hope you understand.

[a5180007]

@a5180007
Could it be possible to do a test build that would put DV descriptor only on the DV layer just like the mp4muxer.
maybe that's the reason why it doesn't work on my LG C8?

You might be right, the DoVi descriptor for the base layer might apply only to single layer DV.
Please try https://github.com/jcdr428/tsMuxer/suites/496716797/artifacts/2484532 (needs github login).

Edit : as clarified by @imhh11, the DV in non-bluray m2ts is working only for the version in the onedrive link. If imhh11 confirms that the solution above is working, I will set the m2ts DoVi descriptor also in the justdan96 version.

[SeeMoreDigital]

I have indeed confirmed that '2-layer Dolby Vision' re-muxes placed within the .TS container work okay on my OPPO. But I have also confirmed that '2-layer Dolby Vision' re-muxes placed within the .M2TS container do not work on my OPPO!

If you have managed to get '2-layer Dolby Vision' re-muxes placed within the .M2TS container to work on your Sony, I would like this confirmed 'again' please...

And if you can't do it, perhaps somebody else can, if you upload such an .M2TS test file.


Many thanks

[imhh11]

You might be right, the DoVi descriptor for the base layer might apply only to single layer DV.
Please try https://github.com/jcdr428/tsMuxer/suites/496716797/artifacts/2484532 (needs github login).

Edit : as clarified by @imhh11, the DV in non-bluray m2ts is working only for the version in the onedrive link. If imhh11 confirms that the solution above is working, I will set the m2ts DoVi descriptor also in the justdan96 version.

Thank you so much, this looks promising.
Will try once I get home (in about 2h)... maybe someone else will confirm before me...

[a5180007]

Thank you so much, this looks promising.
Will try once I get home (in about 2h)... maybe someone else will confirm before me...

@imhh11 And this one has the single DV descriptor ported in the non-bluray m2ts https://github.com/jcdr428/tsMuxer/suites/496773377/artifacts/2485846

[iSeries]

^ page not found.

Can confirm that both .ts and .m2ts files remuxed with the fork build plays in DV on my x700.

[imhh11]

You might be right, the DoVi descriptor for the base layer might apply only to single layer DV.
Please try https://github.com/jcdr428/tsMuxer/suites/496716797/artifacts/2484532 (needs github login).

Edit : as clarified by @imhh11, the DV in non-bluray m2ts is working only for the version in the onedrive link. If imhh11 confirms that the solution above is working, I will set the m2ts DoVi descriptor also in the justdan96 version.


So this new build trigger & play in DV properly on my x700 but still not recognized on the C8 and I'm having the same bug as described here on the x700
https://forum.doom9.org/showpost.php?p=1902524&postcount=470

You probably don't need it but here's a DV TS and a DV MP4 from the same source.. Mp4 works everywhere(Vizio TV, LG TV) and without any bug on the x700 but the DV TS only plays on the x700 with the bug.

TS:
https://drive.google.com/file/d/1-d3DC-lVtUDXEgj_ow_Xyhtcwq2PbbYl/view?usp=sharing

MP4:
https://drive.google.com/open?id=11pEvB3tRmSMA_6okfpDurH7IrIVYFbgR

[a5180007]

So this new build trigger & play in DV properly on my x700 but still not recognized on the C8 and I'm having the same bug as described here on the x700
https://forum.doom9.org/showpost.php?p=1902524&postcount=470

So I'll push the change anyway, as the DoVi descriptor doesn't seem to be needed in the first of the double layer.

All parameters are the same in Mediainfo between the TS and the MP4, I am short of idea of where the bug can come from.

Edit: @imhh11 could you please try this build without the DoVi registration descriptors:
https://github.com/jcdr428/tsMuxer/suites/497543058/artifacts/2499960 (needs GitHub login)

[SeeMoreDigital]

Can somebody here please upload a '2-layer Dolby Vision.M2TS contained file (or files) that I can try with my OPPO and LG TV...

Many thanks

[imhh11]

Edit: @imhh11 could you please try this build without the DoVi registration descriptors:
https://github.com/jcdr428/tsMuxer/suites/497543058/artifacts/2499960 (needs GitHub login)

Unfortunately, same result. the file only plays on the X700.

Well, it also plays on the DV Vizio TV but in HDR10 only.

Can somebody here please upload a '2-layer Dolby Vision.M2TS contained file (or files) that I can try with my OPPO and LG TV...

Many thanks


https://drive.google.com/file/d/1oviY-99Nfk7voS_ffaVlmUCn5GjC393g/view?usp=sharing

[Stereodude]

...I'm having the same bug as described here on the x700
https://forum.doom9.org/showpost.php?p=1902524&postcount=470...
Do you or anyone else have an example of a 2 layer DV .TS or .M2TS file that plays on the X700 but doesn't have the same bug?

[cogira]

So I'll push the change anyway, as the DoVi descriptor doesn't seem to be needed in the first of the double layer.

All parameters are the same in Mediainfo between the TS and the MP4, I am short of idea of where the bug can come from.

Edit: @imhh11 could you please try this build without the DoVi registration descriptors:
https://github.com/jcdr428/tsMuxer/suites/497543058/artifacts/2499960 (needs GitHub login)

i also tried this testbuild and the bug on x700 is still there.

[cogira]

Do you or anyone else have an example of a 2 layer DV .TS or .M2TS file that plays on the X700 but doesn't have the same bug?

I dont think someone has got what you request unfortunately.

[cogira]

i made a single layer dv of gemini man with dvdfab, Then I loaded it in tsmuxer version 2020-02-23--01-10-39. added atmos track and subtitles. Then made a .ts file. It played in x700 in dolby vision/dolby atmos confirmed by the x700 display and by C8, without the bug described here: https://forum.doom9.org/showpost.php...&postcount=470...
And the quality was very good.

[a5180007]

I dont think someone has got what you request unfortunately.

This is the whole reason for this trial and error process: there seems to be no fully working double layer TS yet -and I don't own a UHD player or TV, so kind of working blind...

[cogira]

This is the:)whole reason for this trial and error process: there seems to be no fully working double layer TS yet -and I don't own a UHD player or TV, so kind of working blind...

You are an hero.:):)

[baker99uk]

So I'll push the change anyway, as the DoVi descriptor doesn't seem to be needed in the first of the double layer.

All parameters are the same in Mediainfo between the TS and the MP4, I am short of idea of where the bug can come from.

Edit: @imhh11 could you please try this build without the DoVi registration descriptors:
https://github.com/jcdr428/tsMuxer/suites/497543058/artifacts/2499960 (needs GitHub login)

Using this on X700 I get DoVi on a ts mux, hdr only with m2ts using this build (could be me messing things up so hopefully someone else will confirm)

Edit this was a dual layer mux

[imhh11]

@a5180007

this is a long shot but could the dual layer TS issues be caused by what yusesope is explaining here: https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602&start=1365#p85447


'' The part that scans the NAL units relating to the enhancement layer is not yet present in the tsMuxeR code.
(take a look HERE, only the part related to RPU metadata (NAL_DV) is taken into consideration).''

[a5180007]

@a5180007

this is a long shot but could the dual layer TS issues be caused by what yusesope is explaining here: https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602&start=1365#p85447


'' The part that scans the NAL units relating to the enhancement layer is not yet present in the tsMuxeR code.
(take a look HERE, only the part related to RPU metadata (NAL_DV) is taken into consideration).''

Thanks imhh11 !!! So NAL 62 is the RPU, and NAL 63 is the EL !
The guys at makemkv forum are correct, I've taken into account only NAL 62 -I've based my patches on analysis of the Blu-rays, which never have NAL 63.

So I still have some work to do. And yes, this could explain the bug.

[imhh11]

Great! Can't wait to try your next test build :).

keep it up , you're doing god work here.

[SeeMoreDigital]

https://drive.google.com/file/d/1oviY-99Nfk7voS_ffaVlmUCn5GjC393g/view?usp=sharingMany thanks.

I'm happy to confirm that your '2-layer Dolby Vision with TrueHD audio.m2ts' sample plays fine on my OPPO.

My LG television reports 'Unable To Play'...

This is great progress though ;)

[cogira]

Thanks imhh11 !!! So NAL 62 is the RPU, and NAL 63 is the EL !
The guys at makemkv forum are correct, I've taken into account only NAL 62 -I've based my patches on analysis of the Blu-rays, which never have NAL 63.

So I still have some work to do. And yes, this could explain the bug.

I hope you will sort the problem.
Many thanks for your deep involvment.

[cogira]

@a5180007
With the latest buid 03/06, the .ts plays in x700 as HDR and in mediainfo both video tracks format is hdr. No mention of dolby vision.
Tried 2 movies mission impossible fallout and spiderman homecoming

[SeeMoreDigital]

@a5180007
With the latest buid 03/06, the .ts plays in x700 as HDR and in mediainfo both video tracks format is hdr. No mention of dolby vision.
Tried 2 movies mission impossible fallout and spiderman homecomingI can confirm this too...

[wackopath]

Hello everyone!

First i would like to say thank you very much all you guys for reviving and improving this tool! You've done and excellent work!

I've been following this thread since the revival of tsmuxer, but i've been around doom9 since just before DivX SBC.
This is absolutely my first post ever here at doom9, so sorry if this is not relevant, but i hope i can help to contribute with some feedback!

So this is what i have done so far.
Various titles with ATMOS and Dolby Vision (2-layers) back-ups have been successfully remuxed as "blu-ray folder" with no problems.
They play directly through my Oppo UDP-203 with external drive connected to USB and the TV shows the Dolby Vision logo.

I've done various backups from normal Blu-ray (1080p) to remuxed blu-ray folder and mkv. Almost all of them works fine, except a few titles
from mkv to remuxed as "blu-ray folder" with tsmuxer and dvdfab.

one example problem:
Title; I, Robot (3D to 2D) mkv file plays fine on Oppo but if i remux it as blu-ray folder with tsmuxer or DVDFab i get pixelation when playback, but
if i start the m2ts file directly from it's blu-ray folder it plays just fine, except without chapters, or named subtitles.
I tried to re-encode it with DVDFab and the problems disappear but i would prefer to have audio/video untouched.
Is there anyone having the same problems?

This is my equipment:
Oppo UDP-203
Sony Bravia KD-75ZD9
Yamaha RX-A2080

/ W

[Bandits]

Hello everyone!

First i would like to say thank you very much all you guys for reviving and improving this tool! You've done and excellent work!

I've been following this thread since the revival of tsmuxer, but i've been around doom9 since just before DivX SBC.
This is absolutely my first post ever here at doom9, so sorry if this is not relevant, but i hope i can help to contribute with some feedback!

So this is what i have done so far.
Various titles with ATMOS and Dolby Vision (2-layers) back-ups have been successfully remuxed as "blu-ray folder" with no problems.
They play directly through my Oppo UDP-203 with external drive connected to USB and the TV shows the Dolby Vision logo.

I've done various backups from normal Blu-ray (1080p) to remuxed blu-ray folder and mkv. Almost all of them works fine, except a few titles
from mkv to remuxed as "blu-ray folder" with tsmuxer and dvdfab.

one example problem:
Title; I, Robot (3D to 2D) mkv file plays fine on Oppo but if i remux it as blu-ray folder with tsmuxer or DVDFab i get pixelation when playback, but
if i start the m2ts file directly from it's blu-ray folder it plays just fine, except without chapters, or named subtitles.
I tried to re-encode it with DVDFab and the problems disappear but i would prefer to have audio/video untouched.
Is there anyone having the same problems?

This is my equipment:
Oppo UDP-203
Sony Bravia KD-75ZD9
Yamaha RX-A2080

/ W

I find if I end up with pixilation it has to do with:

Insert SEI and VUI data if absent

This setting can affect some discs and has to be set to:

Do not change SEI and VUI data

Try it on a disc that gave you issues.

[SeeMoreDigital]

Hi all...

Using build version '2020-03-07 git-c5b3eab' I have just generated some '2-layer Dolby Vision' re-muxes into the .ts container and into the .m2ts container, and I can confirm that my OPPO plays them in HDR10 only. And MediaInfo does not report any Dolby Vision data.

Cheers

[wackopath]

I find if I end up with pixilation it has to do with:

Insert SEI and VUI data if absent

This setting can affect some discs and has to be set to:

Do not change SEI and VUI data

Try it on a disc that gave you issues.

thank Bandits for your reply!
I have tried this since i've had that problem sometimes and it works, but in this case it doesn't... any other suggestions?

/ W

[Hellboy.]

First thanks.

When i remux a 4k bluray that not contain DV to bluray folder the subtitles are okay. But when i remux a 4k bluray that contain DV, no matter is you select(check) the DV track or not, the subtitles are out of sync. Begin okay but litter a littler go out go sync. Please fix.

I read here DV single layer and DV double layer, what is the difference?

[SeeMoreDigital]

First thanks.

When i remux a 4k bluray that not contain DV to bluray folder the subtitles are okay. But when i remux a 4k bluray that contain DV, no matter is you select(check) the DV track or not, the subtitles are out of sync. Begin okay but litter a littler go out go sync. Please fix.Which version of TSmuxer are you using?

How are you playing these re-muxes?

[Hellboy.]

w64-nightly-2020-02-29--01-11-32, w64-nightly-2020-03-01--01-10-41, w64-nightly-2020-03-07--01-13-12

I use PowerDVD 19 and VLC

[a5180007]

this is a long shot but could the dual layer TS issues be caused by what yusesope is explaining here: https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602&start=1365#p85447

'' The part that scans the NAL units relating to the enhancement layer is not yet present in the tsMuxeR code.
(take a look HERE, only the part related to RPU metadata (NAL_DV) is taken into consideration).''

This should be fixed in this build (https://github.com/jcdr428/tsMuxer/suites/507015679/artifacts/2658091) (needs github login) including added descriptor for EAC3 and calculation of DV level.

I've tried to keep HDMV descriptors as much as possible so as to keep PGS, AC3/EAC3 and AC3/TrueHD working.

Please test single DV, double DV, EAC3 etc. on Bluray player and on UHD TV, thanks.

[cogira]

This should be fixed in this build (https://github.com/jcdr428/tsMuxer/suites/507015679/artifacts/2658091) (needs github login) including added descriptor for EAC3 and calculation of DV level.

I've tried to keep HDMV descriptors as much as possible so as to keep PGS, AC3/EAC3 and AC3/TrueHD working.

Please test single DV, double DV, EAC3 etc. on Bluray player and on UHD TV, thanks.

I tried this build and I get only black and white picture.
And also the X700 bug is still present.
Thank you for your efforts.

[baker99uk]

This should be fixed in this build (https://github.com/jcdr428/tsMuxer/suites/507015679/artifacts/2658091) (needs github login) including added descriptor for EAC3 and calculation of DV level.

I've tried to keep HDMV descriptors as much as possible so as to keep PGS, AC3/EAC3 and AC3/TrueHD working.

Please test single DV, double DV, EAC3 etc. on Bluray player and on UHD TV, thanks.

Hi I need to do more tests myself but here is a message from another user -

Post by powdeau » Sun Mar 08, 2020 6:08 pm

I have tried a new build by a5180007 (https://forum.doom9.org/showthread.php? ... ost1903300), but the DL DV is still only triggered on X700 and not on the LG C7.
Also the reboot bug is still present.
I have noticed that unlike in the previous builds, the second layer says only EL instead of EL+RPU.

Could you please someone inform him about that since I cannot post on that forum yet? Thank you!

[a5180007]

I tried this build and I get only black and white picture.
And also the X700 bug is still present.
Thank you for your efforts.

@cogira :
Is B&W picture on player, TV or both ?
For single or double layer ?
Is EAC3 working on player, TV or both ?

Edit: ok, I think I made a stupid mistake in swapping EL and RPU...
Please try build 5a3cd98 (https://github.com/jcdr428/tsMuxer/suites/507172214/artifacts/2660533) (github login necessary).

[imhh11]

This should be fixed in this build (https://github.com/jcdr428/tsMuxer/suites/507015679/artifacts/2658091) (needs github login) including added descriptor for EAC3 and calculation of DV level.

I've tried to keep HDMV descriptors as much as possible so as to keep PGS, AC3/EAC3 and AC3/TrueHD working.

Please test single DV, double DV, EAC3 etc. on Bluray player and on UHD TV, thanks.

like the others, DL DV triggered with washed out colors + the bug.
no go on the C8.

Perhaps because RPU is missing.

[cogira]

@cogira :
Is B&W picture on player, TV or both ?
For single or double layer ?
Is EAC3 working on player, TV or both ?

B&W both x700 player and C8 TV
Single layer
Eac3 working on both player and TV

[imhh11]

@cogira :

Edit: ok, I think I made a stupid mistake in swapping EL and RPU...
Please try build 5a3cd98 (https://github.com/jcdr428/tsMuxer/suites/507172214/artifacts/2660533) (github login necessary).

Didnt try on the x700 yet, but now it says BL +RPU instead of EL+RPU

Video #1
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 59 s 976 ms
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2
Maximum Content Light Level : 1016 cd/m2
Maximum Frame-Average Light Level : 342 cd/m2

Video #2
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 min 0 s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2

[a5180007]

@imhh11 thanks, I must be tired :D
Sorry for having to post each minor change, but no DV screen, I can't test myself...

Modified build 6c6dd72 (https://github.com/jcdr428/tsMuxer/suites/507197705/artifacts/2660978).

[baker99uk]

@cogira :
Is B&W picture on player, TV or both ?
For single or double layer ?
Is EAC3 working on player, TV or both ?

Edit: ok, I think I made a stupid mistake in swapping EL and RPU...
Please try build 5a3cd98 (https://github.com/jcdr428/tsMuxer/suites/507172214/artifacts/2660533) (github login necessary).

Neither dual layer DV or single layer DV files play on my C6.

The shield is acting remarkably well, Single Layer DV works, Dual layer DV falls back to HDR (which is what should happen).

My X700 has decided to freak out and lost it's network connection, once I have it fixed I'll test on that too.

[imhh11]

@imhh11 thanks, I must be tired :D
Sorry for having to post each minor change, but no DV screen, I can't test myself...

Modified build 6c6dd72 (https://github.com/jcdr428/tsMuxer/suites/507197705/artifacts/2660978).

haha np :)

thanks but now it says RPU only .

Complete name : I:\test.split.1.ts
Format : MPEG-TS
File size : 163 MiB
Duration : 59 s 977 ms
Overall bit rate mode : Variable
Overall bit rate : 22.8 Mb/s
Maximum Overall bit rate : 35.5 Mb/s

Video #1
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 59 s 976 ms
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2
Maximum Content Light Level : 1016 cd/m2
Maximum Frame-Average Light Level : 342 cd/m2

Video #2
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, RPU / SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 1 min 0 s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2

[a5180007]

@imhh11 My understanding is that RPU was HEVC NAL 62, and EL was NAL 63. Is there really both nal 62 and nal 63 in you double layer hevc ? Can you please pm me the link of the sample ?

[baker99uk]

Further testing on the X700 the single layer DV doesn't play, the dual layer only plays in HDR not DV. After playing the dual layer mux it didn't lock up my player though which is nice.

Be aware my X700 completely reset itself after having to keep switching it off at the mains so it may not be acting correctly anyway (it did play an old mux in DV though)

Edit: Mine also now says this

Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL+RPU / SMPTE ST 2086, HDR10 compatible

[SeeMoreDigital]

@imhh11 My understanding is that RPU was HEVC NAL 62, and EL was NAL 63. Is there really both nal 62 and nal 63 in you double layer hevc ? Can you please pm me the link of the sample ?Perhaps these terms relate to the two available types of Dolby Vision, ie: MEL (10-bit minimal enhancement layer) or FEL (12-bit full enhancement layer)...

[imhh11]

Is there really both nal 62 and nal 63 in you double layer hevc ? Can you please pm me the link of the sample ?

with the mp4muxer dual layer, yes. always EL+RPU

original m2ts:
https://drive.google.com/file/d/1-eXhJeH_7KSUXvJmaiSm6d54k6K_uOU6/view?usp=sharing


dual layer EL+RPU MP4 made from that m2ts:
https://drive.google.com/file/d/1VNQxx4mBSscpl1oZXCKRtDIRNh8LbCLW/view?usp=sharing

[a5180007]

@imhh11 the sample has nal 62 only... But I suppose it must group both RPU and EL for double layers.

Hopefully correct build 554e872 (https://github.com/jcdr428/tsMuxer/suites/507286144/artifacts/2662714), with EL and RPU always present in double layers. For single layers, RPU when nal 62, EL when nal 63.

[imhh11]

ok, now DV with proper color works again on the x700.

but still not working on LG C8. and the x700 bug is still present.

https://extraimage.net/images/2020/03/08/4881338478a4185456b9bd3359a205d4.md.jpg (https://extraimage.net/image/yoTd)

[baker99uk]

I can confirm what imhh11 says REgarding The x700, C6 also won't play the files, shield seems good

[imhh11]

maybe one last thing that could cause the bug?

the profile went from dvhe.07.06 to dvhe.07.07

[a5180007]

maybe one last thing that could cause the bug?

the profile went from dvhe.07.06 to dvhe.07.07

@imhh11 the bug was the same with level 06. Level is dependant of the image width and of the pixel rate (width * height * fps). What the document "DolbyVisionProfilesLevels_v1_3_2_2019_09_16.pdf" doesn't say is if the pixel rate is calculated on the DV layer only or on the BL+EL. As this determines compatibility of the DV chip, to be safe I've taken BL+EL, this should not modify the behavior of the player. I suppose the player will not play the file if level is above what it can decode (same as AVC or HEVC levels).

Edit: could you please report on which files work with or without bug on player or TV (single DV layers, double layers without DV, MEL files, FEL files...) so that I know where to look.

Also I would need a sample of a ts file with pure 7.1 eac3 (not hybrid bluray ac3/eac3).

[staina]

I want with only ask whether last discussion about remux files .TS and .M2TS and theirs problems has and some effect on remux into Bluray ISO or Bluray folder including HDR10, HDR10+ and Dolby Vision?

It is possible without problems perform REMUX into Bluray ISO and Bluray folder and will playable without problems?

Thank you for answer Staina

[a5180007]

It is possible without problems perform REMUX into Bluray ISO and Bluray folder and will playable without problems?

@staina In Blu-ray mode (folder or ISO), the HDMV descriptors produced by tsMuxer in the "Program Map Table" packets are all strictly identical to original. DV information is separate in BDMV (bdjo/mpls/clpi) files so no problems.

In non-bluray mode, all stream information is in the descriptors within the ts or m2ts files.

[a5180007]

Another trial... added "HEVC_timing_and_HRD_descriptor".

Please test build 289ba83 (https://github.com/jcdr428/tsMuxer/suites/509438821/artifacts/2704154).

[cogira]

Another trial... added "HEVC_timing_and_HRD_descriptor".

Please test build 289ba83 (https://github.com/jcdr428/tsMuxer/suites/509438821/artifacts/2704154).

Tried .ts DV double layer from UHD disc (john wick parabellum). On x700 excellent DV but the known bug still present.
Later will try a DV single layer and report.
Thank you.

Tried also DV single layer of the same movie. No go on x700 which starts to play and then stops.
It plays very well on C8 via plex/emby apps.

[imhh11]

@imhh11 the bug was the same with level 06. Level is dependant of the image width and of the pixel rate (width * height * fps). What the document "DolbyVisionProfilesLevels_v1_3_2_2019_09_16.pdf" doesn't say is if the pixel rate is calculated on the DV layer only or on the BL+EL. As this determines compatibility of the DV chip, to be safe I've taken BL+EL, this should not modify the behavior of the player. I suppose the player will not play the file if level is above what it can decode (same as AVC or HEVC levels).

Edit: could you please report on which files work with or without bug on player or TV (single DV layers, double layers without DV, MEL files, FEL files...) so that I know where to look.

Also I would need a sample of a ts file with pure 7.1 eac3 (not hybrid bluray ac3/eac3).
Ok, thanks for the explanation. I don't much about the DV level but I know that all the mp4 dual layer DV are 7.06 and work everywhere. But if 7.07 is fine too, im ok with that.

-Any dual layer DV TS(or m2ts) created by tsMuxer has the bug: FEL or MEL, all the same bug and won't play on LG C8.
EG: https://drive.google.com/file/d/1rz3eLRZ885Ne7eOwUtqU56B7Dv-mck2B/view?usp=sharing

-Single-layer DV TS files don't have the bug and play everywhere. (made from UHD-BD disc)
EG: https://drive.google.com/file/d/1n95g_bcRP_eCFqbzngslM3XbeTJwrkfH/view?usp=sharing

-Dual layer TS (no Dovi descriptor) files don't have the bug and play everywhere. but of course no DV
EG: https://drive.google.com/file/d/1mCIidUy0hqW4JbzaX73i0QQE8D4mR5TS/view?usp=sharing

-Pure E-AC3 7.1 TS: https://drive.google.com/file/d/1rz3eLRZ885Ne7eOwUtqU56B7Dv-mck2B/view?usp=sharing

[a5180007]

@imhh11 @cogira thank you very much, very useful.

So I guess that the single layers that have the bug are profile 5 (non compliant HDR). The single layers without bug should be profile 8 (compliant HDR).

I believe I have identified the issue: HEVC stream_type should be 0x06 for non-compliant SDR/HDR and double layer DV, and not 0x24 as for traditional HEVC.

I'll try tonight.

[cogira]

@imhh11 @cogira thank you very much, very useful.

So I guess that the single layers that have the bug are profile 5 (non compliant HDR). The single layers without bug should be profile 8 (compliant HDR).

I believe I have identified the issue: HEVC stream_type should be 0x06 for non-compliant SDR/HDR and double layer DV, and not 0x24 as for traditional HEVC.

I'll try tonight.

Just to be clear. The x700 bug already described in posts #470 and 471 only happens with .ts DV doulble layer.

[imhh11]

Just to be clear. The x700 bug already described in posts #470 and 471 only happens with .ts DV doulble layer.

correct. SL TS are fine.

I believe I have identified the issue: HEVC stream_type should be 0x06 for non-compliant SDR/HDR and double layer DV, and not 0x24 as for traditional HEVC.

I'll try tonight.

Awesome, thank you

[a5180007]

Awesome, thank you

Well, wait to try before praise :D
Build 6cd5b7a (https://github.com/jcdr428/tsMuxer/suites/512412269/artifacts/2757931) with DL DV Codec Id = 0x06 ("Rec. ITU-T H.222.0 | ISO/IEC 13818-1 PES packets containing private data"), without any guarantee...

[cogira]

Well, wait to try before praise :D
Build 6cd5b7a (https://github.com/jcdr428/tsMuxer/suites/512412269/artifacts/2757931) with DL DV Codec Id = 0x06 ("Rec. ITU-T H.222.0 | ISO/IEC 13818-1 PES packets containing private data"), without any guarantee...

tried john wick parabellum .ts DV double layer and unfortunately the X700 bug is still there.

[a5180007]

tried john wick parabellum .ts DV double layer and unfortunately the X700 bug is still there.

One last thing to try, then I run out of ideas.
Build 8223f83 (https://github.com/jcdr428/tsMuxer/suites/512577734/artifacts/2761813) adds ID dv_bl_signal_compatibility_id in DV descriptor. It is not in the Dolby single layer samples but might be needed for DL.
(link edited)

[imhh11]

bug is still there on the x700 but this time it is recognized on the C8(In HDR10 though)

[baker99uk]

yup although it didn't hard lock my x700 this time, both seem fine on the shield. Same result with C6 too, hdr triggered not DV but plays

[cogira]

One last thing to try, then I run out of ideas.
Build 8223f83 (https://github.com/jcdr428/tsMuxer/suites/512577734/artifacts/2761813) adds ID dv_bl_signal_compatibility_id in DV descriptor. It is not in the Dolby single layer samples but might be needed for DL.
(link edited)

Sorry. Again no go.

[cogira]

In the X700 settings I put Dolby Vision off, then played the .ts DV double layer files and no more known bug, albeit the reproduction is hdr.
Therefore the bug is related to the dolby vision track.
I dont know what this means.
Just to let you know.

[iSeries]

So with the x700 and the need to manually enable DV - how do we even know that DV is playing correctly? When DV is set to on, DV is output for everything, regardless of whether it is HDR or SDR

[imhh11]

So with the x700 and the need to manually enable DV - how do we even know that DV is playing correctly? When DV is set to on, DV is output for everything, regardless of whether it is HDR or SDR

player OSD say '' Dolby Vision HDR '' for real DV
player OSD say '' HDR '' for fake DV

[SeeMoreDigital]

Can somebody post some samples that I can try with my OPPO?

[Hellboy.]

Maybe this help:

yusesope wrote:
I have not converted the raw HEVC stream to m2ts because I have not followed the events related to tsMuxeR (I have not yet understood why a BL + EL + RPU stream is flagged as dvhe.08).

Quetion by shawnc22:
Is it possible that because it's being flagged as dvhe.08, the EL is being ignored on playback even though the DV flag is triggered? This could explain why somebody previously reported that the credit scene in power rangers did not look like it was in DV even though DV was on.

Answer by yusesope:
Could be.
The only profiles that support BL + EL + RPU are 4 and 7 (6 is no longer in use).
mp4muxer should be used for testing purposes.

[binba]

First of all, it's awesome that this software gets developed, forked and updated. I sometimes need to author simple BluRay discs and work on Mac, and after exhaustively researching options like Encore CS6, Architect and TMPGEnc Authoring Works, tsMuxerGUI is actually one of the best solutions out there.


I need it for assets encoded in Adobe Premiere (or Media Encoder). They work just fine in the "original" tsMuxeR 2.6.11, but in the latest build, not only do those files not work, they don't even generate an error. I filed a bug for it. https://github.com/justdan96/tsMuxer/issues/240


Is there an official or stable build for the (open-sourced) Mac version, or only nightly builds?


Is the "infamous" repeat bug fixed in the open-sourced fork? With 2.6.11, authored BluRay discs would always loop, requiring a trip to BDEdit to patch MovieObject.bdmv.

[justdan96]

No release version yet, we are gearing up for the release of 2.7.0 soon.

[a5180007]

I need it for assets encoded in Adobe Premiere (or Media Encoder). They work just fine in the "original" tsMuxeR 2.6.11, but in the latest build, not only do those files not work, they don't even generate an error. I filed a bug for it. https://github.com/justdan96/tsMuxer/issues/240
@binba I can look at this if you provide a link with a m4v.

Is the "infamous" repeat bug fixed in the open-sourced fork? With 2.6.11, authored BluRay discs would always loop, requiring a trip to BDEdit to patch MovieObject.bdmv.
[/LIST]
Any detail on this bug ?

[Stereodude]

Any detail on this bug ?
I'm pretty sure he's just referring to the fact that if you set tsMuxer to mux a Blu-ray the resulting movie loops when played by blu-ray software (or burned on a disc and played in a player). Meaning after the movie is done playing it restarts. Like the movie is on repeat.

[r0lZ]

No release version yet, we are gearing up for the release of 2.7.0 soon.
Any idea of a precise date ?

[a5180007]

-Pure E-AC3 7.1 TS: https://drive.google.com/file/d/1rz3eLRZ885Ne7eOwUtqU56B7Dv-mck2B/view?usp=sharing

@imhh11 this is an interweaved AC3/EAC3 TS, which is the bluray format. I need a pure -i.e. EAC3 only- 7.1 channels TS, to analyse and make it work in tsMuxer.

[a5180007]

Any idea of a precise date ?

I believe the only big thing left is the integration of Dolby Vision in non-Bluray mode. As I can't find any solution for the pixellisation bug with Double Layer DV when stopping the player, I guess it will have to be included as is for the moment.

Having tried every change possible, I am now persuaded that the bug does not come from the descriptors but may rather come from the way the packets are muxed. E.g. tsMuxer muxes second base layer frame before first enhancement layer frame, I haven't found out where it comes from yet.

[a5180007]

Still would it would in the same parts behind command Play PL_MK 0, GPR10 (HEX: 42 82 00 00 00 00 00 00 00 00 00 0A) change command Jump Title 1 (HEX: 21 81 00 00 00 00 00 01 00 00 00 00) to command Break (HEX: 00 02 00 00 00 00 00 00 00 00 00 00). Command Jump Title 1 playback bluray disk over and over in loop order ending playback at the end movie.

Thanks staina, pull requested https://github.com/justdan96/tsMuxer/pull/244

[SeeMoreDigital]

@imhh11 this is an interweaved AC3/EAC3 TS, which is the bluray format. I need a pure -i.e. EAC3 only- 7.1 channels TS, to analyse and make it work in tsMuxer.I tried to find a 'pure' 7.1 channel E-AC-3 audio stream several years ago but never managed to find one. Not on any HD-DVD discs or even on Dolby's web site.

So if you do find one please let me know...


Many thanks

[Stereodude]

I tried to find a 'pure' 7.1 channel E-AC-3 audio stream several years ago but never managed to find one. Not on any HD-DVD discs or even on Dolby's web site.

So if you do find one please let me know...

Many thanks
It needs to be in a .TS right? Didn't HD-DVD's have .EVO files?

[a5180007]

It needs to be in a .TS right? Didn't HD-DVD's have .EVO files?

@Stereodude yes it needs to be TS or M2TS. EAC3 7.1 are peculiar in that they have one main 5.1 stream and one 2 or 3-channel dependant stream, I don't know how the TS descriptors should be informed in the PMT (Program Management Table) packets. Until now I haven't managed to produce one TS working.

[Stereodude]

@Stereodude yes it needs to be TS or M2TS. EAC3 7.1 are peculiar in that they have one main 5.1 stream and one 2 or 3-channel dependant stream, I don't know how the TS descriptors should be informed in the PMT (Program Management Table) packets. Until now I haven't managed to produce one TS working.
What about this sample? https://mega.nz/#!cM9VmBSL!mME5qULH2H5M24vLmjqfZZkaoUjY6RsrGPiw3ultMW0

Edit: What should we see in MediaInfo for such a sample?

[SeeMoreDigital]

What about this sample? https://mega.nz/#!cM9VmBSL!mME5qULH2H5M24vLmjqfZZkaoUjY6RsrGPiw3ultMW0Sadly no... That 7.1 E-AC-3 channel sample has an (5.1 channel) AC3 core :scared:

[Stereodude]

Sadly no... That 7.1 E-AC-3 channel sample has an (5.1 channel) AC3 core :scared:
How do you determine that?

[SeeMoreDigital]

How do you determine that?If you run that particular Dolby Digital Plus file through TSmuxer you'll see it contains an (640Kbps) AC3 core, which can be extracted.

A 'pure' Dolby Digital Plus audio stream, as found on some HD-DVD.evo (program stream) files does not contain a such a core.

[Stereodude]

A 'pure' Dolby Digital Plus audio stream, as found on some HD-DVD.evo (program stream) files does not contain a such a core.
But unless I misunderstood a5180007 that won't be useful because it's not in a .TS or .m2ts file.

[SeeMoreDigital]

But unless I misunderstood a5180007 that won't be useful because it's not in a .TS or .m2ts file.I'm not entirely sure that a commercial 7.1 E-AC-3 audio without an AC-3 core muxed within an transport container actually exists.

I'm yet to find one in an elementary form...

[a5180007]

I'm not entirely sure that a commercial 7.1 E-AC-3 audio without an AC-3 core muxed within an transport container actually exists.

I'm yet to find one in an elementary form...

@SeeMoreDigital Sample of 7_pt_1.eac3 on https://samples.ffmpeg.org/A-codecs/AC3/eac3/

Maybe somebody on doom9 has access to a professional TS muxer and will manage to mux this sample...

[Stereodude]

@SeeMoreDigital Sample of 7_pt_1.eac3 on https://samples.ffmpeg.org/A-codecs/AC3/eac3/

Maybe somebody on doom9 has access to a professional TS muxer and will manage to mux this sample...
I'm not sure they will see the request in this thread. Maybe best to start a new thread?

[tymoxa]

Maybe somebody on doom9 has access to a professional TS muxer and will manage to mux this sample...

This sample encoded as Secondary audio (not usable for UHD)
Anyway, it throws error, that numblkscod shall be set to 11b (6 blocks per syncframe), but actual numblkscod is set to 0

[SeeMoreDigital]

@SeeMoreDigital Sample of 7_pt_1.eac3 on https://samples.ffmpeg.org/A-codecs/AC3/eac3/

Maybe somebody on doom9 has access to a professional TS muxer and will manage to mux this sample...Very nice find...

The version I downloaded from Dolby's web site way back in 2007 included an AC3 core, so it's great to have this version without a AC3 core too. Many thanks.

When the EAC3 audio stream is muxed together with a 24fps HEVC or AVC video stream into the .m2ts container, my findings are as follows: -

My LG TV detects the .m2ts file okay however, the audio stream is not recognised.
My OPPO detects the .m2ts file okay, however, the video runs at around twice normal speed. But the EAC3 audio stream plays perfectly.

By contrast, if I mux the same audio and video streams into the .mkv container, the LG TV and the OPPO plays them perfectly including the audio.

[a5180007]

This sample encoded as Secondary audio (not usable for UHD)
Anyway, it throws error, that numblkscod shall be set to 11b (6 blocks per syncframe), but actual numblkscod is set to 0

Thanks @tymoxa. The file is a standard 7.1 eac3 composed of a main 5.1 stream, and a dependent stream with the Lrs/Rrs channel. What's wrong in having 1 bloc per syncframe ? And do you think there is no way to have this type of 7.1 EAC3 muxed in a MPEG-TS ?

Edit: [ATSC A/52:2018 Annex G] "six blocks of audio data from every substream present in the E-AC-3 stream shall be included in the PES packet payload. As an E-AC-3 syncframe may contain fewer than six blocks of audio data, it may be necessary to group multiple syncframes to accumulate the required six blocks."

[SeeMoreDigital]

Don't all EAC3 audio streams as used with the Blu-ray disc format contain an AC3 core?

EDIT: Scratch the above... I've just backed-up the 'Black Panther' 4K UHD disc and it contains three 7.1 channel EAC3 tracks without an AC3 core!

[a5180007]

Don't all EAC3 audio streams as used with the Blu-ray disc format contain an AC3 core?

EDIT: Scratch the above... I've just backed-up the 'Black Panther' 4K UHD disc and it contains three 7.1 channel EAC3 tracks without an AC3 core!

@SeeMoreDigital I'm sceptical... I thought as well that all Blu-rays must have interweaved AC3. Could you please PM me a sample <20 MB for analysis of the descriptors ?

[SeeMoreDigital]

@SeeMoreDigital I'm sceptical... I thought as well that all Blu-rays must have interweaved AC3. Could you please PM me a sample <20 MB for analysis of the descriptors ?Sorry for the confusion. I've just checked again and the 7.1 channel EAC3 audio streams 'do' have an AC3 core. :o

[a5180007]

Is the "infamous" repeat bug fixed in the open-sourced fork? With 2.6.11, authored BluRay discs would always loop, requiring a trip to BDEdit to patch MovieObject.bdmv.
[/LIST]

@binba this has normally been fixed (as per @staina solution) in latest bintray version. Anybody could report whether this is now working as expected ?

[tymoxa]

And do you think there is no way to have this type of 7.1 EAC3 muxed in a MPEG-TS ?

As i can see, standard 7.1 eac3 can be muxed only as secondary audio in mpeg-ts for 1080 blu-ray only. I can do this but it's useless i think. For main audio we need "BD compatible" eac3 (BD target|eb3)

[cogira]

I see that there is a new gui which includes UHD-blu-ray iso and UHD.blu-ray folder, but I can't find it. Where is it for downloading? Thanks

[Hellboy.]

@binba this has normally been fixed (as per @staina solution) in latest bintray version. Anybody could report whether this is now working as expected ?

I tested 2 movies in PowerDVD 19 and is working. I never notice that was a bug.

The subtitles bug continue. When i remux a movie with DV to bluray folder the subtitles littler a littler go out of sync. Movies with no DV subtitles work ok.

baker99 say:
I regularly get the message "B-pyramid level 2 detected. Shift DTS to 3 frames", I think it's normal and to do with timestamps, some information here: https://bitmovin.com/docs/encoding/faqs/why-is-an-timestamp-offset-for-ts-muxings-applied-by-default

In a movie with DV i not see that message.

DV
tsMuxeR version git-11fcb24. github.com/justdan96/tsMuxer
HEVC muxing fps is not set. Get fps from stream. Value: 23.976
HEVC muxing fps is not set. Get fps from stream. Value: 23.976
Decoding TRUE-HD stream (track 3): AC3 core+TRUE-HD. Peak bitrate: 3363Kbps (core 448Kbps) Sample Rate: 48KHz Channels: 7.1
Decoding AC3 stream (track 4): Bitrate: 192Kbps Sample Rate: 48KHz Channels: 2
Decoding AC3 stream (track 5): Bitrate: 640Kbps Sample Rate: 48KHz Channels: 5.1
Decoding AC3 stream (track 6): Bitrate: 192Kbps Sample Rate: 48KHz Channels: 2
Decoding AC3 stream (track 7): Bitrate: 192Kbps Sample Rate: 48KHz Channels: 2
Decoding PGS stream (track 9): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 10): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 8): Resolution: 1920:1080 Frame rate: 23.976
Processed 187324 video frames
Processed 187324 video frames
Flushing write buffer
Creating Blu-ray stream info and seek index
Creating Blu-ray playlist
Mux successful complete
Muxing time: 20 min 28 sec


No DV
tsMuxeR version git-11fcb24. github.com/justdan96/tsMuxer
HEVC muxing fps is not set. Get fps from stream. Value: 23.976
Decoding TRUE-HD stream (track 2): AC3 core+TRUE-HD. Peak bitrate: 7800Kbps (core 640Kbps) Sample Rate: 48KHz Channels: 7.1
Decoding AC3 stream (track 3): Bitrate: 448Kbps Sample Rate: 48KHz Channels: 5.1
Decoding AC3 stream (track 4): Bitrate: 448Kbps Sample Rate: 48KHz Channels: 5.1
B-pyramid level 2 detected. Shift DTS to 3 frames
Decoding PGS stream (track 5): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 6): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 7): Resolution: 1920:1080 Frame rate: 23.976
AC3 stream (track 3): overlapped frame detected at position 00:11:53,823. Remove frame.
AC3 stream (track 4): overlapped frame detected at position 00:11:53,823. Remove frame.
Processed 146513 video frames
Flushing write buffer
Creating Blu-ray stream info and seek index
Creating Blu-ray playlist
Mux successful complete
Muxing time: 5 min 32 sec

[a5180007]

I see that there is a new gui which includes UHD-blu-ray iso and UHD.blu-ray folder, but I can't find it. Where is it for downloading? Thanks

@cogira this is an old GUI. V2 was former Bluray format for AVC, V3 is the newer format for HEVC/UHD. Now the V3 mode is selected automatically when HEVC is detected, and there is a checkbox option to force V3 if needed for AVC.

[staina]

@binba this has normally been fixed (as per @staina solution) in latest bintray version. Anybody could report whether this is now working as expected ?

Is it OK, only build w64-nightly-2020-03-14--01-12-04 has not information in About.

[staina]

Error in tsMuxer at following progress:

1. Add to tsMuxer UHD Bluray with HEVC and select automatically Bluray V3 format
2. Remove from tsMuxer UHD Bluray
3. Add Bluray with h.264 and Bluray V3 format is always selected (checked)

[SeeMoreDigital]

When the EAC3 audio stream is muxed together with a 24fps HEVC or AVC video stream into the .m2ts container, my findings are as follows: -

My LG TV detects the 'HEVC+EAC3.m2ts' file okay however, the audio stream is not recognised.
My OPPO detects the 'HEVC+EAC3.m2ts' file okay, however, the video runs at around twice normal speed. But the EAC3 audio stream plays perfectly.

By contrast, if I mux the same audio and video streams into the .mkv container, the LG TV and the OPPO plays them perfectly including the audio.As i can see, standard 7.1 eac3 can be muxed only as secondary audio in mpeg-ts for 1080 blu-ray only. I can do this but it's useless i think. For main audio we need "BD compatible" eac3 (BD target|eb3)I generated a new .m2ts file with a basic AC3 audio stream as the 'primary stream' and a the EAC3 audio stream as the 'secondary stream' and I can confirm the following: -

My LG TV detects the 'HEVC+AC3+EAC3.m2ts' file okay, and plays the AC3 audio stream perfectly. But it can't detect the EAC3 audio stream.
My OPPO detects the 'HEVC+AC3+EAC3.m2ts' file okay, and plays the AC3 audio stream perfectly. But as soon as I select the EAC3 audio stream the OPPO becomes unstable and plays the video a twice normal speed!

[a5180007]

@SeeMoreDigital it is normal that your version does not work with EAC3, the EAC3 patch has just been merged. Could you please carry out the test with tomorrow's bintray version. Note that 7.1 EAC3 will not work.

[SeeMoreDigital]

Okay... Will do...

[baker99uk]

From yusesope

I also took a look at the tsMuxeR code and I think I have identified the reason why your .ts files are marked with the profile dvhe.08 (the profile dvhe.04 should be the right one since dvhe.08 does not have the Enhancement Layer).

I believe the problem occurs HERE (https://github.com/justdan96/tsMuxer/blob/5e7111020630580b8166c5458e7245412a6dfb2b/tsMuxer/hevcStreamReader.cpp#L309): all Single Track Double Layer files are treated as Single Track Single Layer files.

Examples:
THIS (https://4kmedia.org/lg-dolby-comparison-uhd-4k-demo/) LG demo (dvhe.04) is remuxed in a dvhe.05 file
Joker's BL + EL + RPU raw stream that I uploaded some time ago (HERE (https://mega.nz/#!nY11SY6I!WGkaUCzQso_l7on8Mxv823MgltmeVC3WdKrZGAOZxV0)) is flagged as dvhe.08 (like your remuxes).
The choice of the profile is due to the value of "DVCompatibility"

The presence of EL should be used to distinguish a Double Layer file from a Single Layer file.

If any of you attend the tsMuxeR developer forum, could you please report it?
So they can check if I said a nonsense or not :mrgreen:

[cogira]

I report from :https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602&sid=b104964a708038e8f84cf4ef671aa18c&start=1710 (the pre-last post by @yusesope)
According to @yusesope there is some problem with tsmuxer about correct DV profile.
Sorry I am just an ambassador.
Thanks

[a5180007]

From yusesope

@baker99uk @cogira yes, yusesope is correct. Patch pushed to correct profile 4.

[cogira]

@baker99uk @cogira yes, yusesope is correct. Patch pushed to correct profile 4.

Thanks, where can I download the corrected tsmuxer?

[a5180007]

Thanks, where can I download the corrected tsmuxer?

@cogira when this pull (https://github.com/justdan96/tsMuxer/pull/250) is merged, the next day it will be part of the latest bintray version.

Edit: if you're in a hurry please try this W64 fork (https://github.com/jcdr428/tsMuxer/suites/536006969/artifacts/3174130).

[baker99uk]

@cogira when this pull (https://github.com/justdan96/tsMuxer/pull/250) is merged, the next day it will be part of the latest bintray version.

Edit: if you're in a hurry please try this W64 fork (https://github.com/jcdr428/tsMuxer/suites/536006969/artifacts/3174130).

Excellent news thank you

[cogira]

@cogira wh:)en this pull (https://github.com/justdan96/tsMuxer/pull/250) is merged, the next day it will be part of the latest bintray version.

Edit: if you're in a hurry please try this W64 fork (https://github.com/jcdr428/tsMuxer/suites/536006969/artifacts/3174130).

Thank you. Going to try now.
:)

Tried M2TS Black Panther and now mediainfo reports: HDR format Dolby Vision version 1.0, dvhe 04.06, BL+EL+RPU /SMPTE ST2086, HDR10 compatible.
Dolby Vision plays perfect in Shield TV 2019 trough Plex and also triggers Dolby Atmos.
Many many thanks @a5180007

[baker99uk]

I get a 404 on the W64 Fork link, is it merged in the daily binaries now?

[Bgalakazam]

I get a 404 on the W64 Fork link, is it merged in the daily binaries now?

Log in github first.

[imhh11]

I get a 404 on the W64 Fork link, is it merged in the daily binaries now?

you need a Github account.


Thank's a5180007 for the new version. 04.06 remains 04.06 now.

[baker99uk]

Thanks Guys, I didn't realise I was logged out, oops.

[cogira]

Gemini man. Followed the exact same procedure as for Black Panther.
It works perfectly but mediainfo indicates a DV profile 04.09
Any reason for that?
Maybe because of 60fps?

[a5180007]

Gemini man. Followed the exact same procedure as for Black Panther.
It works perfectly but mediainfo indicates a DV profile 04.09
Any reason for that?
Maybe because of 60fps?

@cogira yes, 3840 x 2160 @ 60 is level 9.

http://i.imgur.com/ik2NhTrt.jpg (https://imgur.com/ik2NhTr)

[cogira]

@cogira yes, 3840 x 2160 @ 60 is level 9.

http://i.imgur.com/ik2NhTrt.jpg (https://imgur.com/ik2NhTr)

Thank you
:script:

[a5180007]

@cogira @imhh11 Could you please test pixelisation issue on x700 / Oppo with this build (https://github.com/jcdr428/tsMuxer/suites/537646676/artifacts/3204681), thanks.

[imhh11]

thank you.

Unfortunately, it doesn't fix the pixelization bug on the x700 :(

Also, the file is no longer recognized on the LG C8

[cogira]

@cogira @imhh11 Could you please test pixelisation issue on x700 / Oppo with this build (https://github.com/jcdr428/tsMuxer/suites/537646676/artifacts/3204681), thanks.

Still the same problem unfortunately.
I will try to describe better what the problem is on my 65" LG C8.
When I restart the movie I see 2 layers on the TV. The front layer is pixelation but just behind it, on the screen edges, I can see the movie correctly reproduced. It is as the two layers are reproduced separetely one on top of the other and the front one is the pixelation layer, whilst the layer just behind it is correct.
I dont know if this rough description can help.
Thanks really for your involvement in this.:)

[Bgalakazam]

I think that describes it well. Not really a huge issue for me as I rarely have time to watch more than 1 movie a week nowadays.

[cogira]

@a5180007

Is there any reason why, if I engage the pgs subtitles in the m2ts DV, Plex stops working?
In the shield 2019

Is it possible to add .srt subtitles in tsmuxer and keep them in .srt format?

[a5180007]

Is there any reason why, if I engage the pgs subtitles in the m2ts DV, Plex stops working?
In the shield 2019
@cogira from which version has it been like this ?

Is it possible to add .srt subtitles in tsmuxer and keep them in .srt format?
It is not possible to include .srt text in ts files.

[cogira]

@cogira from which version has it been like this ?

It is not possible to include .srt text in ts files.

Thanks for reply.
Regarding pgs subtitles I never was able to use them in any version of tsmuxer in plex. If you have any suggestion pls help

[a5180007]

Thanks for reply.
Regarding pgs subtitles I never was able to use them in any version of tsmuxer in plex. If you have any suggestion pls help

@cogira the problem seems to be linked with Plex not reading pgs, whatever the container. It might make more sense using mp4 with srt on Plex.

[a5180007]

@justdan96 is ready to release 2.7.0, so anything important to be corrected before release, please advise asap !

[yannick92]

Hello,

Problem with a .MKV:
On the latest version, the file does not open, with an error window that I had not yet seen ?? ...
On the other hand, on an old version (1.10.6), the file opens without problem, curious ...

Thx
17248

17249

[cogira]

@cogira the problem seems to be linked with Plex not reading pgs, whatever the container. It might make more sense using mp4 with srt on Plex.

Yes, but I cannot use lossless audio as Dolby Atmos or DTS X

[a5180007]

Problem with a .MKV:
On the latest version, the file does not open, with an error window that I had not yet seen ?? ...
On the other hand, on an old version (1.10.6), the file opens without problem, curious ...


@yannick92 Could you please send me a link to the mkv, thanks.
Edit: when you run tsMuxer in a CMD console (tsMuxer.exe pathToMetafile.meta pathToOutput.ts), what is the error message you get ?
Was the file working with previous versions and with 2.6.12 ?

[Grencola]

Yes, but I cannot use lossless audio as Dolby Atmos or DTS X
Hey ragico, er I mean cogira, just use subtitleedit (https://github.com/SubtitleEdit/subtitleedit/releases/download/3.5.14/SE3514.zip) and make an srt with the same name as your movie file and put them both in the same folder and play it. demux your Pgs with tsmuxer, then run cmd prompt and type subtitleedit /convert yoursub.sup srt

[cogira]

Hey ragico, er I mean cogira, just use subtitleedit (https://github.com/SubtitleEdit/subtitleedit/releases/download/3.5.14/SE3514.zip) and make an srt with the same name as your movie file and put them both in the same folder and play it. demux your Pgs with tsmuxer, then run cmd prompt and type subtitleedit /convert yoursub.sup srt

Thank you

[yannick92]

@yannick92 Could you please send me a link to the mkv, thanks.
Edit: when you run tsMuxer in a CMD console (tsMuxer.exe pathToMetafile.meta pathToOutput.ts), what is the error message you get ?
Was the file working with previous versions and with 2.6.12 ?

Ok thx :)
Here is the link for a sample of my problematic .mkv
https://uptobox.com/rgbi0wit3jqy

And no, the file does not open with 2.6.12 either..., just ok with 1.10.6

Cordially.

Yannick

[yannick92]

@justdan96 is ready to release 2.7.0, so anything important to be corrected before release, please advise asap !

Hello

Little things to fix before the release of 2.7?

A little glitch, and also a problem with resizing the "Source File" column when opening a file, ok on 2.6.12 but not on the latest version.

Thx a lot ;)

17250

17251

[Hellboy.]

@justdan96 is ready to release 2.7.0, so anything important to be corrected before release, please advise asap !

I have the problem i write before about the original PGS subtitles go out of sync with DV movies in Bluray folder. Movie is Knives Out. If someone can test to know the problem is not only my. For testing you need to remux the complete movie because the subtitles go littler a littler out of sync.

[yellowolf]

I have the problem i write before about the original PGS subtitles go out of sync with DV movies in Bluray folder. Movie is Knives Out. If someone can test to know the problem is not only my. For testing you need to remux the complete movie because the subtitles go littler a littler out of sync.

is the value of time shift positive or negative in the sense of delay?

[yellowolf]

Hi,

I've noticed obvious 'out of sync' issue for some audio streams demuxed from a BD. This is the 'WALL·E' UHD blu-ray produced by Disney, and the playlist 00800.mpls consists of 42 m2ts segments 56,61,57 and so one. The audio streams out of sync include DTS-HD Master streams and Dolby ac3 streams, but with the exception of Dolby TrueHD. At the very beginning the V/A are in sync, but they lose sync gradually. At the very end, the audio streams behave a maximum delay of about -0.5s.
I have made some tests and it appears that txmuxer improprialy changes some audio frames close to the beginning of the segment #57 (but not the first frames).
17252
Attachments fig.1 is pending approval
The top track is a DTS-HD Master stream demuxed with tsmuxer from the BD and then converted to flac:
eac3to 00800.track_4353.dts 00800.track_4353.flac -mono
The second track is the DTS stream from 00061.m2ts, which is the second segment of the film.
eac3to BDMV\STREAM\00061.m2ts 3: 1_61_3.dts
eac3to 1_61_3.dts 1_61_3.flac -mono
The third track is the the DTS stream from 00057.m2ts, which is the third segment of the film.
eac3to BDMV\STREAM\00057.m2ts 3: 2_57_3.dts
eac3to 2_57_3.dts 2_57_3.flac -mono
I've aligned segments 61 and 57 so that the audio frames overlap. We can find that tsmuxer has correctly concatenate the two segments at the time about 0:1:04.100. However, at the time mark #1 (0:1:04.783) the top track begins to be different from the third track:
17253
Attachments fig.2 is pending approval
But in the next, if we align the time mark #1 of first track with the time mark #2 of the third track, the subsequent waveforms seem identical again. The duration from time mark #1 to #2 for the first track is only 6ms, but the actual duration from time mark #1 to #3 for the third track is 17ms, thus a time delay of -11ms is introduced here.
The timeshift will be accumulated by the subseqent segments, so maybe that's the very reason that why the overall time delay reaches -0.5s.
I guess that this issue is related to 'overlapped frame' so I try to cancel removing detected overlapped frame by set the correlated condition to constant false:
if (/*m_demuxMode && */ m_mplsOffset > m_halfFrameLen)
=>
if (/*m_demuxMode && */ m_mplsOffset*0 > m_halfFrameLen
in simplePacketizerReader.cpp, and results are shown below.
17254
Attachments fig.4 is pending approval
I have aligned these demuxed tracks at the very beginning of m2ts segment 57 (the 3rd segment of the BD). By checking the delay at the very end of these tracks, it shows that the introduced delay of 11 ms for the DTS stream has been eliminated. However, it seems that the AC3 stream always keep sync with the original track of m2ts, so this modification seems make no difference for the AC3 steam.
To find out the reason why AC3 streams also show an obvious timeshift (much more than that of DTS stream), the situation at the end of previous m2ts segment 61 should be checked either:
17255
Attachments fig.5 is pending approval
It seems that the original version of tsmuxer cuts 5ms from the 2nd segment when concatenating it with the 3rd segment for the AC3 stream, and the modification version shows this delay is much reduced however not eliminated.
I had found this issue for a long time, but I didn't have proper tools (here is audacity 2.3.3, a freeware) to demonstrate it until I find similar bug report in another forum.
The whole bug report can be found here (https://github.com/justdan96/tsMuxer/issues/258)
Hope that the professionals can figure out a perfect solution. Thx a lot :(

[yannick92]

Very interesting !

In my case, I will try to explain where I get this delay during a remux of a full bluray disc, and then, the "DIY" solution that I found to work around the problem ...:

1): On a .ISO (full bluray), I open the .M2TS file of the main movie with TsMuxer 2.6.12.
In my case, I need to Demux the E-AC3 track to extract the Core AC3 because my old amplifier does not decode the E-AC3 audio tracks.
Okay, so I demux the E-AC3 track by not forgetting to check "Downconvert E-AC3 to AC3", and I get my AC3 track (.ac3 file).
So far so good, I will now remux my .AC3 track with the other tracks to generate my movie in .M2TS.
Ok it's done, I have my perfectly remuxed .M2ts file (I think ...).
I launch the movie (on my PS3), and after a few minutes, the sound is slightly desynchronized, I immediately notice it because the dialogs are no longer in sync with the lips of the actors ... :(

2): Now the solution that I found and which works in my case:
I start again, but this time, I first made a .MKV of the original .M2TS file of the full bluray with MKVToolNix.
Okay, so I get my .MKV which I now open with TSMuxer 2.16.12.
So I demux my EAC-3 track, I get my .AC3 file, but this time, I remux it with MKVToolnix and I remake a .MKV.
Finally, I open my .MKV with TSMuxer to Muxer my file in .M2TS (the PS3 does not support .MKV ...)
I start playing the movie, no more desynchro!
Well, this technique works, don't ask me why, I'm not technically competent enough to explain it, but it works ...;)

Thank you all

Yannick

[a5180007]

Problem with a .MKV:
On the latest version, the file does not open, with an error window that I had not yet seen ?? ...
On the other hand, on an old version (1.10.6), the file opens without problem, curious ...

@yannick92 good find, rare bug. Fix https://github.com/justdan96/tsMuxer/pull/260 proposed for merge.

[Hellboy.]

is the value of time shift positive or negative in the sense of delay?

I don't know what is "positive or negative" but when a person speak the subtitles appears 3 seconds later.

[Hart2hart]

I don't know what is "positive or negative" but when a person speak the subtitles appears 3 seconds later.


That would be -3000 ms on the subtitle.

[no-one]

Hi,

I've noticed obvious 'out of sync' issue for some audio streams demuxed from a BD. This is the 'WALL·E' UHD blu-ray produced by Disney, and the playlist 00800.mpls consists of 42 m2ts segments 56,61,57 and so one. The audio streams out of sync include DTS-HD Master streams and Dolby ac3 streams, but with the exception of Dolby TrueHD. At the very beginning the V/A are in sync, but they lose sync gradually. At the very end, the audio streams behave a maximum delay of about -0.5s.
I have made some tests and it appears that txmuxer improprialy changes some audio frames close to the beginning of the segment #57 (but not the first frames).
17252
Attachments fig.1 is pending approval
The top track is a DTS-HD Master stream demuxed with tsmuxer from the BD and then converted to flac:
eac3to 00800.track_4353.dts 00800.track_4353.flac -mono
The second track is the DTS stream from 00061.m2ts, which is the second segment of the film.
eac3to BDMV\STREAM\00061.m2ts 3: 1_61_3.dts
eac3to 1_61_3.dts 1_61_3.flac -mono
The third track is the the DTS stream from 00057.m2ts, which is the third segment of the film.
eac3to BDMV\STREAM\00057.m2ts 3: 2_57_3.dts
eac3to 2_57_3.dts 2_57_3.flac -mono
I've aligned segments 61 and 57 so that the audio frames overlap. We can find that tsmuxer has correctly concatenate the two segments at the time about 0:1:04.100. However, at the time mark #1 (0:1:04.783) the top track begins to be different from the third track:
17253
Attachments fig.2 is pending approval
But in the next, if we align the time mark #1 of first track with the time mark #2 of the third track, the subsequent waveforms seem identical again. The duration from time mark #1 to #2 for the first track is only 6ms, but the actual duration from time mark #1 to #3 for the third track is 17ms, thus a time delay of -11ms is introduced here.
The timeshift will be accumulated by the subseqent segments, so maybe that's the very reason that why the overall time delay reaches -0.5s.
I guess that this issue is related to 'overlapped frame' so I try to cancel removing detected overlapped frame by set the correlated condition to constant false:
if (/*m_demuxMode && */ m_mplsOffset > m_halfFrameLen)
=>
if (/*m_demuxMode && */ m_mplsOffset*0 > m_halfFrameLen
in simplePacketizerReader.cpp, and results are shown below.
17254
Attachments fig.4 is pending approval
I have aligned these demuxed tracks at the very beginning of m2ts segment 57 (the 3rd segment of the BD). By checking the delay at the very end of these tracks, it shows that the introduced delay of 11 ms for the DTS stream has been eliminated. However, it seems that the AC3 stream always keep sync with the original track of m2ts, so this modification seems make no difference for the AC3 steam.
To find out the reason why AC3 streams also show an obvious timeshift (much more than that of DTS stream), the situation at the end of previous m2ts segment 61 should be checked either:
17255
Attachments fig.5 is pending approval
It seems that the original version of tsmuxer cuts 5ms from the 2nd segment when concatenating it with the 3rd segment for the AC3 stream, and the modification version shows this delay is much reduced however not eliminated.
I had found this issue for a long time, but I didn't have proper tools (here is audacity 2.3.3, a freeware) to demonstrate it until I find similar bug report in another forum.
The whole bug report can be found here (https://github.com/justdan96/tsMuxer/issues/258)
Hope that the professionals can figure out a perfect solution. Thx a lot :(

track eng dts hd , fra dolby , spa dolby in wall e UHD and Up_UHD, they delay 667 ms

[a5180007]

Problem with a .MKV:
On the latest version, the file does not open, with an error window that I had not yet seen ?? ...
On the other hand, on an old version (1.10.6), the file opens without problem, curious ...
@yannick92 should be fixed with latest version of bintray 2020-03-29, please try.
A little glitch, and also a problem with resizing the "Source File" column when opening a file, ok on 2.6.12 but not on the latest version.
@yannick92 should be fixed with latest version of bintray 2020-03-29, please try.
I have the problem i write before about the original PGS subtitles go out of sync with DV movies in Bluray folder. Movie is Knives Out. If someone can test to know the problem is not only my. For testing you need to remux the complete movie because the subtitles go littler a littler out of sync.
@Hellboy should be fixed with latest version of bintray 2020-03-29, please try.
I've noticed obvious 'out of sync' issue for some audio streams demuxed from a BD. This is the 'WALL·E' UHD blu-ray produced by Disney, and the playlist 00800.mpls consists of 42 m2ts segments 56,61,57 and so one. The audio streams out of sync include DTS-HD Master streams and Dolby ac3 streams, but with the exception of Dolby TrueHD. At the very beginning the V/A are in sync, but they lose sync gradually. At the very end, the audio streams behave a maximum delay of about -0.5s.

@yellowolf @no-one @yannick92 not sure this one has been fixed... Could you please try latest bintray 2020-03-29 and report any improvement on THD and/or AC3, thanks.

[arestarh]

Hi,

Guys, could you please take a look:
https://forum.doom9.org/showthread.php?p=1903813#post1903813

Both w32 and w64 build have empty About tab.
Only If I choose language at bottom of About tab info about application appears.
But we'll see empty About tab again on the next run.

[Hellboy.]

@Hellboy should be fixed with latest version of bintray 2020-03-29, please try.

Tested and is working great. Thanks.

[justdan96]

@arestarh: sorry but which language is your operating system in? I'm just trying to track down where the About issue is coming from.

[a5180007]

@arestarh: sorry but which language is your operating system in? I'm just trying to track down where the About issue is coming from.

@justdan96 my OS is Windows64 EnglishUS with EnglishUS locale, and I also have the empty About tab. I believe it is just a question of defining the English translation as the default in the GUI, and saving the selected language in the .ini file.

[arestarh]

@arestarh: sorry but which language is your operating system in? I'm just trying to track down where the About issue is coming from.
@justdan96 my OS is Windows64 EnglishUS with ru-RU locale.

[a5180007]

Two possible enhancements of tsMuxer for versions after 2.7.0:

1. TrueHD
Mpeg-ts is compatible with interleaved ac3/TrueHD frames. One solution to mux pure TrueHD would be to interleave empty 32kbit ac3 frames. Indeed not as good as transcoding an ac3+thd with eac3to, as the playing of the ac3 would be blank. Is it of any interest ?

2. Dolby Vision
Profile 7 dual tracks is supported by Blu-ray player SoCs only. For non-Blu-ray modes, tsMuxer could transmux those to profile 6 single track dual layer, deprecated but a priori compatible with most STB/TV SoCs. Is it of any interest ?

[imhh11]

Two possible enhancements of tsMuxer for versions after 2.7.0:

1. TrueHD
Mpeg-ts is compatible with interleaved ac3/TrueHD frames. One solution to mux pure TrueHD would be to interleave empty 32kbit ac3 frames. Indeed not as good as transcoding an ac3+thd with eac3to, as the playing of the ac3 would be blank. Is it of any interest ?

2. Dolby Vision
Profile 7 dual tracks is supported by Blu-ray player SoCs only. For non-Blu-ray modes, tsMuxer could transmux those to profile 6 single track dual layer, deprecated but a priori compatible with most STB/TV SoCs. Is it of any interest ?

+1
that would be great enhancements.

[Grencola]

+1
that would be great enhancements.
+2, that would be amazing! streamlining everything into one program to run one time is definitely the way to go.

[SeeMoreDigital]

Two possible enhancements of tsMuxer for versions after 2.7.0:

1. TrueHD
Mpeg-ts is compatible with interleaved ac3/TrueHD frames. One solution to mux pure TrueHD would be to interleave empty 32kbit ac3 frames. Indeed not as good as transcoding an ac3+thd with eac3to, as the playing of the ac3 would be blank. Is it of any interest ?
It certainly is of interest. A worthy enhancement...


2. Dolby Vision
Profile 7 dual tracks is supported by Blu-ray player SoCs only. For non-Blu-ray modes, tsMuxer could transmux those to profile 6 single track dual layer, deprecated but a priori compatible with most STB/TV SoCs. Is it of any interest ?Anything that can retain the Dolby Vision meta-data so that the transport contained muxes can function in hardware (and software) playback devices, is a worthy enhancement.

If you're up for it I have another suggestion. Could you provide support for adding 44.1kHz 16-bit LPCM audio streams. It's always seemed a bit odd to me that LC-AAC, HE-AAC and AC3 @ 44.1kHz audio streams can be added but not 44.1kHz LPCM.


Cheers

[cogira]

Two possible enhancements of tsMuxer for versions after 2.7.0:

1. TrueHD
Mpeg-ts is compatible with interleaved ac3/TrueHD frames. One solution to mux pure TrueHD would be to interleave empty 32kbit ac3 frames. Indeed not as good as transcoding an ac3+thd with eac3to, as the playing of the ac3 would be blank. Is it of any interest ?

2. Dolby Vision
Profile 7 dual tracks is supported by Blu-ray player SoCs only. For non-Blu-ray modes, tsMuxer could transmux those to profile 6 single track dual layer, deprecated but a priori compatible with most STB/TV SoCs. Is it of any interest ?

+3
thanks

[staina]

Two possible enhancements of tsMuxer for versions after 2.7.0:

1. TrueHD
Mpeg-ts is compatible with interleaved ac3/TrueHD frames. One solution to mux pure TrueHD would be to interleave empty 32kbit ac3 frames. Indeed not as good as transcoding an ac3+thd with eac3to, as the playing of the ac3 would be blank. Is it of any interest ?

2. Dolby Vision
Profile 7 dual tracks is supported by Blu-ray player SoCs only. For non-Blu-ray modes, tsMuxer could transmux those to profile 6 single track dual layer, deprecated but a priori compatible with most STB/TV SoCs. Is it of any interest ?

+4 Thanks

[SeeMoreDigital]

Am I +5 now or +3??!! Or just a rolling + ;)

[iSeries]

Two possible enhancements of tsMuxer for versions after 2.7.0:

1. TrueHD
Mpeg-ts is compatible with interleaved ac3/TrueHD frames. One solution to mux pure TrueHD would be to interleave empty 32kbit ac3 frames. Indeed not as good as transcoding an ac3+thd with eac3to, as the playing of the ac3 would be blank. Is it of any interest ?

2. Dolby Vision
Profile 7 dual tracks is supported by Blu-ray player SoCs only. For non-Blu-ray modes, tsMuxer could transmux those to profile 6 single track dual layer, deprecated but a priori compatible with most STB/TV SoCs. Is it of any interest ?

Both would be great additions!

[baker99uk]

Two possible enhancements of tsMuxer for versions after 2.7.0:

1. TrueHD
Mpeg-ts is compatible with interleaved ac3/TrueHD frames. One solution to mux pure TrueHD would be to interleave empty 32kbit ac3 frames. Indeed not as good as transcoding an ac3+thd with eac3to, as the playing of the ac3 would be blank. Is it of any interest ?

2. Dolby Vision
Profile 7 dual tracks is supported by Blu-ray player SoCs only. For non-Blu-ray modes, tsMuxer could transmux those to profile 6 single track dual layer, deprecated but a priori compatible with most STB/TV SoCs. Is it of any interest ?

+6 ? Yes please

[a5180007]

Ok, I've entered the requests for these two enhancements in GitHub. I'll start working on it after release of 2.7.0.

[staina]

You can me write what has changed at creation output Bluray ISO?

Compared I'm UHD Bluray created in tsMuxeR GUI git-99b4679 and in tsMuxeR GUI git-2ff96ce (latest version) and be here difference in CLPI and M2TS file.

A either write if will correctly playback UHD Bluray ISO created in tsMuxeR GUI git-99b4679?

Thank for answer Staina

[priitv8]

As an appleTV 4K user I have these 2 questions:Two possible enhancements of tsMuxer for versions after 2.7.0:

1. TrueHD
Mpeg-ts is compatible with interleaved ac3/TrueHD frames. One solution to mux pure TrueHD would be to interleave empty 32kbit ac3 frames. Indeed not as good as transcoding an ac3+thd with eac3to, as the playing of the ac3 would be blank. Is it of any interest ?

2. Dolby Vision
Profile 7 dual tracks is supported by Blu-ray player SoCs only. For non-Blu-ray modes, tsMuxer could transmux those to profile 6 single track dual layer, deprecated but a priori compatible with most STB/TV SoCs. Is it of any interest ?
1. If this functionality could be expanded with re-encode to E-AC-3 with JOC, then that would be awesome. Finally would I be able to import them UHD rips into my local library and retain Atmos. But this involves more than just re-muxing of existing bits, I know.
2. +1 if this can be done.

[koka]

tsmuxer.py BD --blu-ray 42.ts+43.ts
glues 42.ts and 43.ts into the blu-ray directory `BD`

tsmuxer.py MT --blu-ray 42.ts+ --mplsOffset=1 --m2tsOffset=10
tsmuxer.py MT --blu-ray 43.ts+ --mplsOffset=2 --m2tsOffset=20
tsmuxer.py MT
makes 2-title blu-ray directory `MT` where `tsmuxer.py MT` rebuild index.bdmv and MovieObject.bdmv
with help of MPLS2JSON.exe (https://forum.doom9.org/showthread.php?t=174563)
Look https://github.com/abakum/tsmuxerCLI#ex

[B1gD4ddy]

hey guys...new here...


2. Dolby Vision
Profile 7 dual tracks is supported by Blu-ray player SoCs only. For non-Blu-ray modes, tsMuxer could transmux those to profile 6 single track dual layer, deprecated but a priori compatible with most STB/TV SoCs. Is it of any interest ?

is that feature missing the reason why my dolby vision m2ts files created from uhd only trigger hdr instead of dolby vision when played by lg c9 usb media player???

and will adding that feature make my dolby vision m2ts files trigger dolby vision???

kind regards

[AVX]

hey guys...new here...



is that feature missing the reason why my dolby vision m2ts files created from uhd only trigger hdr instead of dolby vision when played by lg c9 usb media player???

and will adding that feature make my dolby vision m2ts files trigger dolby vision???

kind regards

I would like to know that too.
In some UHD , it only triggers the HDR not the Dolby Vision.
Idk if its some kind of new protection.
Regards

[a5180007]

In some UHD , it only triggers the HDR not the Dolby Vision.
So the C9 TVs read some DV profile 7 TS and not others ? I thought the tsMuxer TS could be read only by Blu-ray players because of the HDMV descriptors.

[B1gD4ddy]

So the C9 TVs read some DV profile 7 TS and not others ? I thought the tsMuxer TS could be read only by Blu-ray players because of the HDMV descriptors.
i think avx is not talking about c9 usb media player...



my c9 can read and play all dolby vision m2ts files created from uhd by tsmuxer since version 2020-03-23.

older versions created dolby vision m2ts files that forced my c9 into endless loading and trying to read the file.

but all the dolby vision m2ts files tsmuxer creates only trigger hdr and not dolby vision!

so could you please answer my initial question please?

kind regards

[a5180007]

but all the dolby vision m2ts files tsmuxer creates only trigger hdr and not dolby vision!

so could you please answer my initial question please?

@B1gD4ddy So the answer is in my previous answer: I believe the TV cannot trigger DV because of the general HDMV descriptor: HDMV descriptor on top of DV descriptor is not standard. But if we remove the general HDMV descriptor then PGS, ac3+eac3 and ac3+thd won't work anymore. This is the limitation of the TS container.

[B1gD4ddy]

doesn't it help to change the dv profile from 7 to 6 like you suggested for tvs?

for what should that change else be good?

[a5180007]

doesn't it help to change the dv profile from 7 to 6 like you suggested for tvs?

for what should that change else be good?

Most of the non-Bluray DV SoCs should be compatible with profile 4/6 or 5/8. However the change needs to come with a "non-HDMV descriptors" checkbox option.

[B1gD4ddy]

so there is still a possible solution to my problem that could be integrated into tsmuxer with that checkbox and profile change?

Thank you. Going to try now.
:)

Tried M2TS Black Panther and now mediainfo reports: HDR format Dolby Vision version 1.0, dvhe 04.06, BL+EL+RPU /SMPTE ST2086, HDR10 compatible.
Dolby Vision plays perfect in Shield TV 2019 trough Plex and also triggers Dolby Atmos.
Many many thanks @a5180007

btw i read the post i quoted above.

he managed to create a

4/6 (Dolby Vision version 1.0, dvhe 04.06, BL+EL+RPU /SMPTE ST2086, HDR10 compatible) m2ts file

from an uhd with tsmuxer instead of the usual

7/5 (Dolby Vision, Version 1.0, dvhe.07.05, EL+RPU, 8 compatible / SMPTE ST 2086, HDR10 compatible) m2ts files

tsmuxer creates.

how can i replicate that? i wanna test it.

[a5180007]

he managed to create a 4/6 (Dolby Vision version 1.0, dvhe 04.06, BL+EL+RPU /SMPTE ST2086, HDR10 compatible) m2ts file from an uhd with tsmuxer instead of the usual 7/5 (Dolby Vision, Version 1.0, dvhe.07.05, EL+RPU, 8 compatible / SMPTE ST 2086, HDR10 compatible) m2ts files tsmuxer creates.

When I write 4/6 or 5/8 it is profile 4/profile6 or profile5/profile8. Level is related to pixel rate and image width.
how can i replicate that? i wanna test it.

Please read https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602
In brief:
- Demux all tracks with ffmpeg or tsMuxer
- Mix the two profile 7 BL+EL hevc tracks into one profile 4/6 BL+EL single track with yusesope tool
- Remux the profile 4/6 single track in mp4 with Dolby mp4muxer (https://github.com/DolbyLaboratories/dlb_mp4base/tree/master/bin)
- Remux the DV mp4 + audio tracks with mp4box (.mp4) or tsMuxer (.ts) or ffmpeg

Edit: basically the enhancement I've proposed will avoid all the above to directly output the profile 6 .ts with tsMuxer

[koka]

Correct me if I am mistaken:
m2ts files are part of the bluray and therefore there must be HDMV descriptors,
but ts files if there are no PGS or there are DV should be without HDMV descriptors

[a5180007]

Correct me if I am mistaken:
m2ts files are part of the bluray and therefore there must be HDMV descriptors,
but ts files if there are no PGS or there are DV should be without HDMV descriptors

@koka yes I had pushed the commit #203 (https://github.com/justdan96/tsMuxer/pull/203/) to work exactly as you describe. But as PGS, ac3+eac3 and ac3+thd were not working anymore (because there is no equivalent descriptor in non-HDMV world), I was asked to keep the HDMV descriptors in .ts, see issue #208 (https://github.com/justdan96/tsMuxer/issues/208).
I agree it would have been more logical to limit hdmv compatibility to m2ts, as users always have the choice between .ts and .m2ts.
Edit: you can re-open the issue if you also think it should be working this way.

[koka]

see issue #208 (https://github.com/justdan96/tsMuxer/issues/208).

This is exactly (https://github.com/justdan96/tsMuxer/issues/208#issuecomment-594884494) what I suggested

[koka]

Limit hdmv compatibility not with .m2ts, but with .ts, because users always have a choice, but not between .ts and .m2ts, but between including PGS in .ts, then it will have HDMV descriptors or including DV in .ts, then there will be no HDMV descriptors in .ts

[SeeMoreDigital]

Out of interest...

Are the descriptors that are used with the AVCHD (https://en.wikipedia.org/wiki/AVCHD) (camcorder and disc) .mts transport stream any different to the ones used for .ts and .m2ts?

[staina]

@staina In Blu-ray mode (folder or ISO), the HDMV descriptors produced by tsMuxer in the "Program Map Table" packets are all strictly identical to original. DV information is separate in BDMV (bdjo/mpls/clpi) files so no problems.

In non-bluray mode, all stream information is in the descriptors within the ts or m2ts files.

You can me write what has changed at creation output Bluray ISO?

Compared I'm UHD Bluray created in tsMuxeR GUI git-99b4679 and in tsMuxeR GUI git-2ff96ce (latest version) and be here difference in CLPI and M2TS file.

A either write if will correctly playback UHD Bluray ISO created in tsMuxeR GUI git-99b4679?

Thank for answer Staina

[B1gD4ddy]

Edit: basically the enhancement I've proposed will avoid all the above to directly output the profile 6 .ts with tsMuxer

i would love that!
please make that enhancement!
if you need a tester with a c9 im here.

kind regards

[a5180007]

A either write if will correctly playback UHD Bluray ISO created in tsMuxeR GUI git-99b4679?

Thank for answer Staina

Sorry @staina, your query seems lost in translation... Maybe somebody in the community could clarify ?

Limit hdmv compatibility not with .m2ts, but with .ts, because users always have a choice, but not between .ts and .m2ts, but between including PGS in .ts, then it will have HDMV descriptors or including DV in .ts, then there will be no HDMV descriptors in .ts

@koka and what should happen when there are both pgs (or TrueHD) and DV in the input ?

Edit: this is the way I see it working (https://github.com/justdan96/tsMuxer/issues/273).

[imhh11]

There seems to be an issue with SRT subtitles processed in tsmuxer. They show up black. PGS to PGS is fine.

https://extraimage.net/images/2020/04/07/9b460c909de92ba65a55a5e28cc64dab.png



Also, DV TS (dual layer profile 7.06) does not work anymore with the x700 using the latest 2020-04-07--02-11-14.zip

[AVX]

There seems to be an issue with SRT subtitles processed in tsmuxer. They show up black. PGS to PGS is fine.

https://extraimage.net/images/2020/04/07/9b460c909de92ba65a55a5e28cc64dab.png



Also, DV TS (dual layer profile 7.06) does not work anymore with the x700 using the latest 2020-04-07--02-11-14.zip
I have the same problem.
Also anyone knows why added pgs in tsmuxer get dsynced when muxing to bluray folder?

[a5180007]

There seems to be an issue with SRT subtitles processed in tsmuxer. They show up black. PGS to PGS is fine.

@imhh11 is it only with the latest tsMuxer version ? There is no change regarding srt or pgs.

Also, DV TS (dual layer profile 7.06) does not work anymore with the x700 using the latest t2020-04-07--02-11-14.zip

The HDMV descriptor has been removed for the DV track -I would have thought that the DV SoC did not need this descriptor, and that it was creating the pixellisation bug issue . I will push it back.

[imhh11]

@imhh11 is it only with the latest tsMuxer version ? There is no change regarding srt or pgs.
.

I tried the last two versions and one of your test build: same problem.

[B1gD4ddy]

Also, DV TS (dual layer profile 7.06) does not work anymore with the x700 using the latest 2020-04-07--02-11-14.zip

i can confirm that for c9 usb...with version 04-07 we're back to c9 cant even play the dv(m2)ts and loads endlessly.

kind regards

[iSeries]

I tried the last two versions and one of your test build: same problem.

I'm using the second last latest version, and SRT subs worked fine for me with that one (M2TS output - also using x700). Have not tried latest.

[imhh11]

I'm using the second last latest version, and SRT subs worked fine for me with that one (M2TS output - also using x700). Have not tried latest.

are you sure your original file was SRT format because PGS from bluray disc does work properly?

Last two builds (didnt try more) definitely render black subtitles when the source has SRT subs.
2020-03-30--02-11-36.zip & 2020-04-07--02-11-14.zip

[spotter]

I'm wondering if someone here can help me, not quite a tsmuxer issue, but figure people here might know.

I'm doing a project where I'm using libbluray to take a bluray playlist and turn it into a single m2ts (well a bit more complicated, meant for streaming, but that's close enough for a first approximation). What I realize is that in doing this, it loses the language metadata (i.e. the langauge for audio and subtitle tracks) as this data seems to only be in the clip info files so isn't in the "m2ts" stream I'm reading from libbluray. Is there anyway to edit this into a pure m2ts stream? (either editing the stream on the fly or appending a packet of sorts to the start), or is this simply impossible in the m2ts format?

[iSeries]

are you sure your original file was SRT format because PGS from bluray disc does work properly?

Last two builds (didnt try more) definitely render black subtitles when the source has SRT subs.
2020-03-30--02-11-36.zip & 2020-04-07--02-11-14.zip

Yep was SRT

[imhh11]

Yep was SRT

Well, I can reproduce the bug in MPC-BE with the 2 last versions. Not only with DV but with any files.

I only tried the latest version on my x700 though.

sample: https://drive.google.com/file/d/1oTQu6DVcwwtF_oqcMKrBdAyOz-4RexsO/view?usp=sharing

[SeeMoreDigital]

Well, I can reproduce the bug in MPC-BE with the 2 last versions. Not only with DV but with any files.

I only tried the latest version on my x700 though.

sample: https://drive.google.com/file/d/1oTQu6DVcwwtF_oqcMKrBdAyOz-4RexsO/view?usp=sharingNice work with the .TS muxed files...

On my [2016] LG television, the Dolby Vision encoded video and EAC3 audio work perfectly. Sadly my TV does not support PGS subtitles.

On my OPPO, the Dolby Vision encoded video and EAC3 audio work perfectly too. But as others have reported the PGS subtitles are black. And they are huge ;)

[B1gD4ddy]

Nice work with the .TS muxed files...

On my [2016] LG television, the Dolby Vision encoded video and EAC3 audio work perfectly. Sadly my TV does not support PGS subtitles.


do you mean your lgs usb media player?

if yes then...ehm lol...my 2019 lg c9 usb media player loads a sec then says file not supported....

kind regards

[SeeMoreDigital]

do you mean your lgs usb media player?

if yes then...ehm lol...my 2019 lg c9 usb media player loads a sec then says file not supported....
I transferred imhh11's Mandalorian sample onto a USB flash-drive, and used the TV's built-in 'Photo & Video' media player app to play it....

[a5180007]

Nice work with the .TS muxed files...

On my [2016] LG television, the Dolby Vision encoded video and EAC3 audio work perfectly. Sadly my TV does not support PGS subtitles.

On my OPPO, the Dolby Vision encoded video and EAC3 audio work perfectly too. But as others have reported the PGS subtitles are black. And they are huge ;)

@SeeMoreDigital so this is confirmation that DV works on TVs if we remove the HDMV descriptor -but do not work anymore on the Bluray players, which is kind of logical...

I have pushed the commit to reinstate the HDMV descriptor for DV tracks. I still believe that the HDMV descriptors should be present only for m2ts and not for ts. Anyway... I'll work on an option for manual selection of the HDMV descriptors when I have time -after 2.7.0.

As for the srt... no clear if it was already there with 30/03 version, let's see if the reinstatement of the hdmv descriptor fixes the issue.

[B1gD4ddy]

I transferred imhh11's Mandalorian sample onto a USB flash-drive, and used the TV's built-in 'Photo & Video' media player app to play it....

nice...2016 is in some cases more capable/unrestrictive than 2019... fu lg

@SeeMoreDigital so this is confirmation that DV works on TVs if we remove the HDMV descriptor.

ehm nope, not on all, like i said c9 cant even open the file from googledrive.

and like already mentioned every dv (m2)ts created from uhd by tsmuxer only triggers hdr on c9 instead of dv.

no idea what magic seemoredigitals 2016 lg does...

kind regards

[SeeMoreDigital]

@SeeMoreDigital so this is confirmation that DV works on TVs if we remove the HDMV descriptor -but do not work anymore on the Bluray players, which is kind of logical... Actually, imhh11's Mandalorian sample also works on my OPPO via USB flash-drive and when played from my network connected NAS, via UPnP and SMB. But I'm not entirely sure if it makes the player unstable...

"I have spoken"...

[SeeMoreDigital]

ehm nope, not on all, like i said c9 cant even open the file from googledrive.
GogleDrive is pants!!! I suggest you try playing the sample file from a USB flash-drive instead...

[B1gD4ddy]

googledrive is pants!!! I suggest you try playing the sample file from a USB flash-drive instead...

i did of course, downloaded it, put on usb drive, put that in tv and then happened what i already described.

kind regards

[imhh11]

nice...2016 is in some cases more capable/unrestrictive than 2019... fu lg



ehm nope, not on all, like i said c9 cant even open the file from googledrive.

and like already mentioned every dv (m2)ts created from uhd by tsmuxer only triggers hdr on c9 instead of dv.

no idea what magic seemoredigitals 2016 lg does...

kind regards

mmm the sample i posted should work on your C9.. this is not a dual layer profile 7 TS which never worked (in DV)on any TV. The sample is a real profile 05.06 and play fine on my C8

[imhh11]

As for the srt... no clear if it was already there with 30/03 version, let's see if the reinstatement of the hdmv descriptor fixes the issue.

yes the bug is present with 30-03 version.

EDIT: might be my source file after all because I tried with other samples and I can't reproduce it now

[SeeMoreDigital]

mmm the sample i posted should work on your C9.. this is not a dual layer profile 7 TS which never worked (in DV)on any TV. The sample is a real profile 05.06 and play fine on my C8With regard to PGS subtitles... I wonder if genuine PGS subtitles (extracted from a 4K UHD disc) will work better with your Mandalorian sample?!

[B1gD4ddy]

mmm the sample i posted should work on your C9.. this is not a dual layer profile 7 TS which never worked (in DV)on any TV. The sample is a real profile 05.06 and play fine on my C8

i redownloaded and retried. does not work.
c9 is able to show preview thumbnail pics but when i click on the file the c9 loads a sec and then gives me a german error message which translated to english says something like "this file is not recognized. back to list."
firmware is newest from some days ago, 4.71.25.

kind regards

[imhh11]

i redownloaded and retried. does not work.
c9 is able to show preview thumbnail pics but when i click on the file the c9 loads a sec and then gives me a german error message which translated to english says something like "this file is not recognized. back to list."
firmware is newest from some days ago, 4.71.25.

kind regards

Very strange that the C6 and C8 can play it but not the C9.

With regard to PGS subtitles... I wonder if genuine PGS subtitles (extracted from a 4K UHD disc) will work better with your Mandalorian sample?!

Yes pure pgs subtitles should work. I'll try when i get home in a few hours.




EDIT. pgs works just fine when i remux uhd-bd to dual layer TS. But there is no Mandalorian UHD-BD yet, my sample is a downloaded/untouched stream from Disney+. That's why i have to deal with SRT for that profile 05.06 sample.

Complete name : D:\srt bug.ts
Format : MPEG-TS
File size : 119 MiB
Duration : 1 min 1 s
Overall bit rate mode : Variable
Overall bit rate : 16.2 Mb/s
Maximum Overall bit rate : 35.5 Mb/s

Video
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@High
HDR format : Dolby Vision, Version 1.0, dvhe.05.06, BL+RPU
Codec ID : 36
Duration : 1 min 1 s
Bit rate : 14.7 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.074
Stream size : 107 MiB (90%)
Color range : Full

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : E-AC-3 JOC
Format/Info : Enhanced AC-3 with Joint Object Coding
Commercial name : Dolby Digital Plus with Dolby Atmos
Codec ID : 135
Duration : 1 min 1 s
Bit rate mode : Constant
Bit rate : 768 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 5.61 MiB (5%)
Language : English
Service kind : Complete Main
Complexity index : 16
Number of dynamic objects : 15
Bed channel count : 1 channel
Bed channel configuration : LFE

Text
ID : 4768 (0x12A0)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144
Delay relative to video : 1 s 793 ms

[a5180007]

I'm doing a project where I'm using libbluray to take a bluray playlist and turn it into a single m2ts (well a bit more complicated, meant for streaming, but that's close enough for a first approximation). What I realize is that in doing this, it loses the language metadata (i.e. the langauge for audio and subtitle tracks) as this data seems to only be in the clip info files so isn't in the "m2ts" stream I'm reading from libbluray. Is there anyway to edit this into a pure m2ts stream? (either editing the stream on the fly or appending a packet of sorts to the start), or is this simply impossible in the m2ts format?

@spotter you just need to mux the playlist in tsMuxer in non-bluray mode. Although some problems on Linux have been reported, cf. issue #166 (https://github.com/justdan96/tsMuxer/issues/166).

[AVX]

Can someone help me? So i create the blu ray folders after adding some audio and subtitles to a m2ts and everything works fine except the subtitles that have a huuge delay after muxing not before :(

[imhh11]

Ok, the SRT bug seems to be related to my PC(Win10 64x) at work because using the same file and the same tsMuxer here with my PC at home(Win10 64x), no more problem....

how is that possible?

sample with working subtitles (converted from SRT): https://drive.google.com/file/d/1VCxlt-hZIHD5QUzpf2AgjDoX_c5G8QTm/view?usp=sharing

subs, atmos and DV works on x700
C8= atmos + DV but no subs
Shield= Atmos + DV but no subs (plex fault here i think)


sorry for the confusion.

[spotter]

@spotter you just need to mux the playlist in tsMuxer in non-bluray mode. Although some problems on Linux have been reported, cf. issue #166 (https://github.com/justdan96/tsMuxer/issues/166).

the nice thing about libbluray is that it creates a seekable "file handle", What I'm trying to do is store blurays locally and enable them to be streamed on demand to myself via http (including being able to seek into the stream). Don't want to remux and store (time and storage consumng). I'm wondering if its possible to use tsmuxer in library form.

[SeeMoreDigital]

sample with working subtitles (converted from SRT): https://drive.google.com/file/d/1VCxlt-hZIHD5QUzpf2AgjDoX_c5G8QTm/view?usp=sharing

subs, atmos and DV works on x700
C8= atmos + DV but no subs
Shield= Atmos + DV but no subs (plex fault here i think)

I can confirm the same playback results with my OPPO and LG TV... Very well done :)

[mattmarsden]

Could anyone tell me what version I need to remux to dual layer m2ts to work on my Oppo 203? All the versions I've tried just play in HDR10.

[SeeMoreDigital]

Could anyone tell me what version I need to remux to dual layer m2ts to work on my Oppo 203? All the versions I've tried just play in HDR10.As you are an OPPO player owner you can use the muxers 'Blu-ray Folder' output option. And after TSmuxer has finished, you place the 'BDMV' and 'CERTIFICATE' folders within an 'AVCHD' folder (which you have to manually create). Then place the AVCHD folder (including its contents), within another folder named after your movie.

I have several movies with Dolby Vision on my NAS and I can confirm the OPPO plays them perfectly via SMB (including chapter navigation). They also play perfectly via a directly connected USB HDD.

[mattmarsden]

As you are an OPPO player owner you can use the muxers 'Blu-ray Folder' output option. And after TSmuxer has finished, you place the 'BDMV' and 'CERTIFICATE' folders within an 'AVCHD' folder (which you have to manually create). Then place the AVCHD folder (including its contents), within another folder named after your movie.

I have several movies with Dolby Vision on my NAS and I can confirm the OPPO plays them perfectly via SMB (including chapter navigation). They also play perfectly via a directly connected USB HDD.

Thanks for that, I've actually got a modded Oppo that can play iso/blu-ray folder but was wondering if it was possible to play DV directly from a m2ts as that allows resuming on the oppo and iso/blu-ray folder doesn't. Also it would allow me to add them to plex for my other players. The m2ts taken directly from a retail UHD blu-ray folder does play in DV btw.

[SeeMoreDigital]

The m2ts taken directly from a retail UHD blu-ray folder does play in DV btw.Sadly such .m2ts files are full of foreign language audio and subtitle tracks I don't need. And you don't get chapter navigation ;)

[mattmarsden]

Sadly such .m2ts files are full of foreign language audio and subtitle tracks I don't need. And you don't get chapter navigation ;)

Exactly, which is why I was hoping Tsmuxer could create m2ts files that play the same.

[imhh11]

Exactly, which is why I was hoping Tsmuxer could create m2ts files that play the same.

tsMuxer does create Dolby Vision m2ts/ts , you just lose the chapters.

I'm not using the latest versions but this is the version I've been using for a while now. DV, Atmos and subtitles works just fine on the Sony x700 and will certainly work on the oppo as well.

https://drive.google.com/file/d/1ulf9fI7xXfUdt-_s-HYv_q0tGv_m-FuZ/view?usp=sharing

[a5180007]

the nice thing about libbluray is that it creates a seekable "file handle", What I'm trying to do is store blurays locally and enable them to be streamed on demand to myself via http (including being able to seek into the stream). Don't want to remux and store (time and storage consumng). I'm wondering if its possible to use tsmuxer in library form.

@spotter If you want to stream m2ts only then either your streaming service is able to seek the info into the mpls/clpi, or you have to remux to include the language descriptors (in the PMT packets, every 100ms max).

[wackopath]

As you are an OPPO player owner you can use the muxers 'Blu-ray Folder' output option. And after TSmuxer has finished, you place the 'BDMV' and 'CERTIFICATE' folders within an 'AVCHD' folder (which you have to manually create). Then place the AVCHD folder (including its contents), within another folder named after your movie.

I have several movies with Dolby Vision on my NAS and I can confirm the OPPO plays them perfectly via SMB (including chapter navigation). They also play perfectly via a directly connected USB HDD.

...if you select "Force BD-ROM V3 format" in tsmuxer "bluray" tab
when you mux with "Blu-ray Folder" you won't need to make a AVCHD folder for 1080p blu-rays with OPPO, in my case is the UDP203. Now i have tried this with USB attached hdd/usb mem. haven't tried through network yet...

[mattmarsden]

Has there been any progress for X700 corruption after playing a DV m2ts?

[staina]

Sorry @staina, your query seems lost in translation... Maybe somebody in the community could clarify ?


I have asked why are files CLPI and M2TS at output Bluray ISO and Bluray folder different compared to previous version and whether the error be as consequential that the would Bluray ISO created older version tsMuxeR not to need to some machinery work?

[MastaG]

So is it possible to remux dual layer dolby vision (profile 7) into .ts container and play it back on LG tv's now?

[spotter]

@spotter If you want to stream m2ts only then either your streaming service is able to seek the info into the mpls/clpi, or you have to remux to include the language descriptors (in the PMT packets, every 100ms max).

you wouldn't happen to have pointers on how to do that? (example code or what not?).

when you say max ever 100ms, could it conceptually just be once at the beginning of the stream?

What I'm trying to do is enable emby to stream my blurays without requiring me to remux them into mkv or something else (I'd rather keep them as ISOs). While fmpeg can remux into mkv on the fly (have that working to as an http endpoint) that doesn't work as well (at least right now) for seeking (i.e. for another http connections to be made with a range request)

emby can stream http m2ts files just fine (I have that working, drop a strm file in an emby library directory that is basically http://localhost/file=some.iso?playlist=number and it will stream that playlist via libbluray output, bd_read() to http response body essentially).

emby works great as it picks up all the audio and subtitle tracks, but without the metadata as mentioned). If I can figure out how to mix / edit in those pmt packets to set the audio / subtitle language that libbluray has in bd_title_info I'd be all set.

[staina]

Version w64-nightly-2020-03-25--01-12-53 tsMuxeR Gui git-99b4679

Size ISO file: 56 563 728 384 byte
Size M2TS file: 56 561 418 240 byte


Version w64-nightly-2020-04-07--02-11-14 tsMuxeR Gui git-f6ac3b1

Size ISO file: 56 563 728 384 byte
Size M2TS file: 56 561 418 240 byte


Version w64-nightly-2020-04-14--02-13-14 tsMuxeR Gui git-f6ac3b1

Size ISO file: 56 214 224 896 byte
Size M2TS file: 56 211 978 240 byte

Last version w64-nightly-2020-04-16--02-12-23 tsMuxeR Gui git-ac9b47c

Size ISO file: 56 563 728 384 byte
Size M2TS file: 56 561 418 240 byte

Version w64-nightly-2020-04-07--02-11-14 and Last version w64-nightly-2020-04-16--02-12-23 have the same result.
Was any bug in version Version w64-nightly-2020-04-14--02-13-14?

On attachment are CLPI files.

Why are at these version different M2TS and CLPI files?
Why is the same name build at version w64-nightly-2020-04-07--02-11-14 and w64-nightly-2020-04-14--02-13-14.
Can someone write description these changes and which version for creation ISO files UHD Bluray use and why?

Thank for answers Staina

[a5180007]

@staina you can see merges done on 24/03, 06/04 and 15/04 (i.e. the day before the nightly version) on https://github.com/justdan96/tsMuxer/commits/master.

The bintray version w64-nightly-2020-04-14--02-13-14 tsMuxeR Gui git-f6ac3b1 shouldn't exist, no idea how it got there.

[staina]

@staina you can see merges done on 24/03, 06/04 and 15/04 (i.e. the day before the nightly version) on https://github.com/justdan96/tsMuxer/commits/master.

The bintray version w64-nightly-2020-04-14--02-13-14 tsMuxeR Gui git-f6ac3b1 shouldn't exist, no idea how it got there.

Still have not answers to why are you files CLPI and M2TS different and how so can affect their later playback?

Here are downloadable all version:
https://bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly#files

[CapricornX10X]

Something very strange suddenly started in the srt subtitle. That's what he appears to me. And when I play the movie and choose the subtitle.
Just nothing appears. very strange. So far it has not happened to me

[SeeMoreDigital]

@CapricornX10X,

Forum file/image attachments can take a while to be approved. Which git-build version are you using that does not work with srt subtitles?

[imhh11]

Something very strange suddenly started in the srt subtitle. That's what he appears to me. And when I play the movie and choose the subtitle.
Just nothing appears. very strange. So far it has not happened to me

I wonder if you are having the same issue I have with SRT subs with my pc at my work-place. They appear black and if they are positioned in the black bars, you can't see them.

Strangely my other PC here at home doesn't have that issue with basically the same setup.

[CapricornX10X]

@CapricornX10X,

Forum file/image attachments can take a while to be approved. Which git-build version are you using that does not work with srt subtitles?

git-f6ac3b1

[CapricornX10X]

I wonder if you are having the same issue I have with SRT subs with my pc at my work-place. They appear black and if they are positioned in the black bars, you can't see them.

Strangely my other PC here at home doesn't have that issue with basically the same setup.

Yes very strange. It didn't happen to me until yesterday. And I've worked with the software on loads of movies and I've never had a problem.

I downloaded the latest version yesterday and since then the problems started to seem to me. (Or version before last)
I just don't know what software version I used when everything was working properly

I don't know about it like you mentioned. But I choose the subtitle (srt) I want and just nothing appears. strange

[CapricornX10X]

I did a test after what you mentioned to me. And right you are right for some reason the srt subtitles were in black so I did not see them. I have no idea how in the software they appeared in black. I changed to white and everything is fine now.

[a5180007]

Something very strange suddenly started in the srt subtitle. That's what he appears to me. And when I play the movie and choose the subtitle.
Just nothing appears. very strange. So far it has not happened to me

@CapricornX10X please PM me the srt file. I will check whether it is fully UTF-8 compliant.

[CapricornX10X]

@CapricornX10X please PM me the srt file. I will check whether it is fully UTF-8 compliant.

Even in the software according to the picture I sent, this is a problem.
The problem for me is solved, the subtitles appear to me at the moment. tsmuxer made me the blu ray file with a black subtitle. So I didn't see anything (because the subtilte in the black part of the screen below)
Why I still have a problem alert I have no idea. But I checked with more movies and subtitles. And every srt file has this problem.

[CapricornX10X]

By the way we are already discussing the subtitle issue lol.
When I do demux for a Blu-ray movie. And I take away specific subtitles I want.
This time of course in pgs format. And then I take those subtitles and put them in the Blu-ray movie I want and then I do muxsr to blu-ray folder.
Will I have a synchronization problem at times? Between the subtitles and the audio?

Because I did this a while ago and had a real time sync problem

[no-one]

When i take subtitle from demux of version 2020-04-19--02-12-02 to open with bdsub2sup, it gets problem.
Subtitle not show 2 lines from the end.

[a5180007]

@no-one I've demuxed PGS subtitles from various blu-rays with the latest version without problems: I can't reproduce the bug.

[meihuaxiao]

4K video downloaded from the Internet, import tsMuxeR_2.6.15, select Blu-ray folder for output, then split with BD Demuxer Pro 3D UHD v3.2, and import split 00000_1_01.hevc into Scenarist UHD prompt:
Error: Value of Chroma_loc_info_present_flag is not supported in the BD standard.
Unable to import.
How can I solve it? Thank you! !

[a5180007]

4K video downloaded from the Internet, import tsMuxeR_2.6.15, select Blu-ray folder for output, then split with BD Demuxer Pro 3D UHD v3.2, and import split 00000_1_01.hevc into Scenarist UHD prompt:
Error: Value of Chroma_loc_info_present_flag is not supported in the BD standard.
Unable to import.
How can I solve it? Thank you! !
@meihuaxiao to correct the choma_loc no other solution than to re-encode.

[meihuaxiao]

@a5180007 Thanks for guidance

[Wolfe999]

Hi,
First of all, thanx for the great progress you've been doing on this wonderful program.

Just one question: Is there a way to change the default font and size for the subtitles? Because I do it, but the changes revert to the original after I restart the program.

Cheers :)

[vmd12]

do you mean your lgs usb media player?

if yes then...ehm lol...my 2019 lg c9 usb media player loads a sec then says file not supported....

kind regards

Same here. The file does not run on my c9. Maybe some firmware update messes it up.

[staina]

@no-one I've demuxed PGS subtitles from various blu-rays with the latest version without problems: I can't reproduce the bug.

Testing UHD Bluray found:

To version w64-nightly-2020-04-14--02-13-14 is Demux PGS subtitles streams and audio streams OK. Demux from version w64-nightly-2020-04-16--02-12-23 abbreviates files PGS subtitles streams and audio streams about several KB from the end streams, video stream is always OK.

It is possible this fix bug, evidently with occurred in modification between versions w64-nightly-2020-04-14--02-13-14 and w64-nightly-2020-04-16--02-12-23

Thank you staina

[CapricornX10X]

Greetings ,
I have been trying for a long time to get rid of some parts in full Blu Ray movies. But keep the movie and its continuity.
get rid of fbi warning. I tried through bdedit and didn't understand the guide.
Of course I have full-HD and full UHD Blu-ray movies
I'd love to help!

[Dasa21]

I am using the latest version of tsMuxeR 2.6.16. I have such a problem. When I convert Mkv UHD to Bluray Uhd, when I play the BD UHD structure on a BD desktop player, the TV stretches the image without stripes! WHERE PLEASE ERROR?

[SeeMoreDigital]

I am using the latest version of tsMuxeR 2.6.16. I have such a problem. When I convert Mkv UHD to Bluray Uhd, when I play the BD UHD structure on a BD desktop player, the TV stretches the image without stripes! WHERE PLEASE ERROR?This topic is about the new 'Open Source' builds of TSmuxerGUI, so I suggest you download try the newest 'git' version!

At the time of writing, the newest version is dated, 2020-04-30. See here: https://bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly#files/


Cheers

[Dasa21]

Do I have the latest version of tsMuxeR 2.6.16 newer version that I have not seen anywhere? When converting UHD MKV to UHD BD, this version does not preserve the 16: 9 picture format when played by a bluray player on a TV.

[SeeMoreDigital]

Do I have the latest version of tsMuxeR 2.6.16 newer version that I have not seen anywhere? When converting UHD MKV to UHD BD, this version does not preserve the 16: 9 picture format when played by a bluray player on a TV.This topic is about the new 'Open Source' builds of TSmuxerGUI. Which are not the same as the VideoHelp versions!

[darrrkmanxxx]

hey guys, is there a version of tsMuxer, that does dvhe.05.06, BL+RPU in .ts container?

[darrrkmanxxx]

also I get this eroor on every nightly on mac: https://drive.google.com/file/d/1Uwfa56k_TqPjhOhS4SxFbkIWANMfTXCs/view?usp=sharing

do you know how to fix it?

[Bgalakazam]

also I get this eroor on every nightly on mac: https://drive.google.com/file/d/1Uwfa56k_TqPjhOhS4SxFbkIWANMfTXCs/view?usp=sharing

do you know how to fix it?

You need freetype. The easiest is with homebrew.

brew install freetype

There are some extra steps to enable homebrew before you can do this, however. Not sure if links are allowed, but you can search "Catalina homebrew".

[darrrkmanxxx]

You need freetype. The easiest is with homebrew.

brew install freetype

There are some extra steps to enable homebrew before you can do this, however. Not sure if links are allowed, but you can search "Catalina homebrew".

awesome, thank you so much.

[filler56789]

also I get this eroor on every nightly on mac: https://drive.google.com/file/d/1Uwfa56k_TqPjhOhS4SxFbkIWANMfTXCs/view?usp=sharing

Yeah, the lack of static builds of tsMuxeR for the Mac OS suxxx royally.
I know almost-nothing of Macs and so my assumptions can be wrong, but since Mac OS is a type of Unix, it should be trivial to compile the dependencies together with the tsMuxeR executable and then link this latter statically to freetype.
This "recipe" already works on Windows (through MinGW-w64) and should work on Linux as well.

[Bgalakazam]

One other issue you may encounter is with SRT subtitles stating font Ariel is missing. I believe that is resolved by changing the metadata to use a different font. I use PGS so this doesn't affect me.

[Ghitulescu]

Ariel is a mermaid - no wonder the nuxer reports the font as missing. Have you tried Arial instead?

[Emulgator]

no wonder the nuxer reports the font as missing
Arial, Ariel...what gives ? I love nuxers too ;-)

[no-one]

Testing UHD Bluray found:

To version w64-nightly-2020-04-14--02-13-14 is Demux PGS subtitles streams and audio streams OK. Demux from version w64-nightly-2020-04-16--02-12-23 abbreviates files PGS subtitles streams and audio streams about several KB from the end streams, video stream is always OK.

It is possible this fix bug, evidently with occurred in modification between versions w64-nightly-2020-04-14--02-13-14 and w64-nightly-2020-04-16--02-12-23

Thank you staina

Still same problem in lated version (w64-nightly-2020-04-30--02-11-26)

[staina]

Testing UHD Bluray found:

To version w64-nightly-2020-04-14--02-13-14 is Demux PGS subtitles streams and audio streams OK. Demux from version w64-nightly-2020-04-16--02-12-23 abbreviates files PGS subtitles streams and audio streams about several KB from the end streams, video stream is always OK.

It is possible this fix bug, evidently with occurred in modification between versions w64-nightly-2020-04-14--02-13-14 and w64-nightly-2020-04-16--02-12-23

Next testing UHD Bluray found:

Problem needn't be at of all subtitles, but only at some. While testing is need test more UHD movies and make demux of all subtitles make their verification in BDSop2Sub so that the display latest subtitle and here with then will appear error.

Detection:

At demux e.g . subtitles stream 01, 05, 07, 08 is stream 01 OKs, but streams 05, 07, 08 are corrupted. Always at demux is stream with lowest number OK and other are corrupted. The same at audio streams.


Thank you fix bug. staina

[a5180007]

@staina bug shoud be fixed in latest version nightly-2020-05-09--02-16-59, could you please test.

[staina]

@staina bug shoud be fixed in latest version nightly-2020-05-09--02-16-59, could you please test.

All is OK. Big Thanks

[darrrkmanxxx]

Hey guys, when I try to mux BL+RPU, I always get dvhe.08.06, BL+RPU, but what I need is dvhe.05.06, BL+RPU

How can I achieve that?

[SeeMoreDigital]

Hey guys, when I try to mux BL+RPU, I always get dvhe.08.06, BL+RPU, but what I need is dvhe.05.06, BL+RPU

How can I achieve that?Which git build version are you using? And please don't say "the latest one". Quote the actual number!

[darrrkmanxxx]

Which git build version are you using? And please don't say "the latest one". Quote the actual number!
git-7b159f6 mac-nightly-2020-05-09--02-16-59

[a5180007]

Hey guys, when I try to mux BL+RPU, I always get dvhe.08.06, BL+RPU, but what I need is dvhe.05.06, BL+RPU

How can I achieve that?

@darrrkmanxxx can you give a link to a sample of the file which should be dvhe.05.06 ?

[DMagic1]

Is it just a know limitation that tsmuxer can't handle truehd in a mkv file?

[filler56789]

Is it just a know limitation that tsmuxer can't handle truehd in a mkv file?

Yes, it is. The Matroska container doesn't support TrueHD+AC3 and Blu-Ray video doesn't support TrueHD without an AC3 substream.
Transport streams do support pure TrueHD though, so this feature still is in the TO-DO list :-/

[Hellboy.]

How can i read index.bdmv and MovieObject.bdmv? I try with notepad but not work. Thanks.

[chompy]

Hi, I think I've found a bug with Dolby Digital Plus tracks in nightly-2020-05-09--02-16-59... If they are inside a m2ts files they are muxed correctly in a new ts/m2ts file, but if the Dolby Digital Plus track is inside a mkv file, my OPPO BDP-93 doesn't see this audio track, using the same input files with tsMuxerGUI 2.6.12 always give a correct file independent of the original file containing the Dolby Digital Plus audio track.

I've seen that in the correctly muxed files, MediaInfo identifies the Dolby Digital Plus with Coded ID = 132:

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : E-AC-3
Format/Info : Enhanced AC-3
Commercial name : Dolby Digital Plus
Codec ID : 132
Duration : 56 min 54 s
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 260 MiB (14%)
Language : Spanish
Service kind : Complete Main

But in the incorreclty muxed files, the Dolby Digital Plus tracks have Coded ID = 135:

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : E-AC-3
Format/Info : Enhanced AC-3
Commercial name : Dolby Digital Plus
Codec ID : 135
Duration : 56 min 54 s
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 260 MiB (14%)
Language : Spanish
Service kind : Complete Main

Best regards

[a5180007]

How can i read index.bdmv and MovieObject.bdmv? I try with notepad but not work. Thanks
@Hellboy. you can use BDEdit (versions for UHD >0.44).

But in the incorreclty muxed files, the Dolby Digital Plus tracks have Coded ID = 135:

@chompy in the A-52 ATSC standard, stream_type for EAC3 is 0x87 = 135. Is the same problem met on TVs ?

[chompy]

@chompy in the A-52 ATSC standard, stream_type for EAC3 is 0x87 = 135. Is the same problem met on TVs ?

Thanks,

What's the code 132 according to A-52 ATSC standard? The previous v2.6.12 used always this code for EAC3 and in this nightly build is also used when the file from where the EAC3 track is copied is a M2TS.

My TV is an old Panasonic plasma without mediaplayer capabilities, so sorry, I cannot test the files there.

Regards

EDIT:
I've tested in a newer Sony TV I have in the kitchen that I never use, but that it has mediaplayer, and interestingly the EAC3 m2ts muxed with v2.6.12 (132) plays without sound, but the muxed EAC3 m2ts with nightly build plays fine... Maybe the standard has changed since my old OPPO was build, but that's very strange.

[a5180007]

What's the code 132 according to A-52 ATSC standard?
Stream_type 0x84 (132) is AC3 for HDMV -which can be interleaved AC3/EAC3. Pure EAC3 does not exist in HDMV format.

EDIT:
I've tested in a newer Sony TV I have in the kitchen that I never use, but that it has mediaplayer, and interestingly the EAC3 m2ts muxed with v2.6.12 (132) plays without sound, but the muxed EAC3 m2ts with nightly build plays fine... Maybe the standard has changed since my old OPPO was build, but that's very strange.

So what I can do for pure eac3 is stream_type = 0x84 when hdmv_descriptors is checked, and stream_type = 0x87 when unchecked.
Edit: but that would mean that eac3 would not work on TVs in hdmv_descriptors mode. I need others to confirm whether this is the way they want it to work.

[chompy]

Thanks,

I've tested an original m2ts from a bluray, and there the EAC3 is identified as 132. The OPPO plays it fine, but the Sony TV plays it with no sound, so as you said it seems it cannot play interleaved AC3/EAC3 (hdmv_descriptors mode):

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : E-AC-3
Format/Info : Enhanced AC-3
Commercial name : Dolby Digital Plus
Format profile : Blu-ray Disc
Muxing mode : Stream extension
Codec ID : 132
Duration : 9 min 10 s
Bit rate mode : Constant
Bit rate : 768 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 50.4 MiB (5%)
Service kind : Complete Main

[SeeMoreDigital]

Thanks,

I've tested an original m2ts from a bluray, and there the EAC3 is identified as 132. The OPPO plays it fine, but the Sony TV plays it with no sound, so as you said it seems it cannot play interleaved AC3/EAC3 (hdmv_descriptors mode):

Is it the Sony TV or are you sending the DD+ audio from the TV to an AVR via HDMI ARC?

[staina]

I want with ask what with changed from version 2.6.12 at creation 3D Bluray?

3D Bluray created in version 2.6.12 and in latest this version have different M2TS, SSIF, CLPI files.

Which version creates correct 3D Bluray matching original?

Thanks for answer. Standa

[chompy]

Is it the Sony TV or are you sending the DD+ audio from the TV to an AVR via HDMI ARC?

It's the Sony TV playing directly the file using its mediaplayer and using its speakers, I don't have it connected to the AVR.

[SeeMoreDigital]

It's the Sony TV playing directly the file using its mediaplayer and using its speakers, I don't have it connected to the AVR.Out of interest...

What happens if you mux the same streams into the .mkv container. Can your TV detect and play the DD+ audio?

EDIT: I forgot to confirm, that my LG television is able to play .m2ts and .mkv files containing with 6-channel DD+ audio. But it's not able to play .m2ts and .mkv files containing with 8-channel DD+ audio...


Cheers

[Nemesh]

Hello everyone,

For years now I make my own subtitles using Subtitle Edit.
In the past mainly for BD's.
However now I am also creating subtitles for UHD/4K.

When my subtitle is finished, I always export as a .sup file with Subtitle Edit.
Then I add the .sup file to TsMuxer and mux everything.

Everything is fine, except the subtitle hight (from bottom)
No matter what hight (from bottom) I use in Subtitle Edit, TsMuxer always muxes at a fixed hight.
The old version of TsMuxer used the hight (from bottom) I set in Subtitle Edit.

Then I removed the .sup file and added the .srt files.
In the subtitle section from TsMuxer set everything close to my settings from Subtitle Edit.
When TsMuxer is ready the subtitles are higher (from bottom) and that's exactly what I want.

At the moment I am using the Nightly from May 9, 2020.
Is it a bug a stumbled on or must this go to the 'to do-list'?
With much regards,

Nemesh

P.s.
Just to be clear, I mean the: bottom-offset
Also, the subtitle muxer from TsMuxer doesn't recouldnise: {\an8}
This command befire a subtitle placed it top-screen middle.

[Nemesh]

I don't want to edit my first reply.
Have no clue what I did wrong, but now the bottom-offset works.

But the {\an8} command doesn't work in TsMuxer Nighly release May 9 2020.

[chompy]

Out of interest...

What happens if you mux the same streams into the .mkv container. Can your TV detect and play the DD+ audio?

EDIT: I forgot to confirm, that my LG television is able to play .m2ts and .mkv files containing with 6-channel DD+ audio. But it's not able to play .m2ts and .mkv files containing with 8-channel DD+ audio...


Cheers

Yes my Sony is only able to play 5.1 EAC3 and only when it's inside a M2TS, if it's inside a MKV I don't have sound.

With 7.1 EAC it doesn't matter if it's a M2TS or a MKV, I never get sound.

[SeeMoreDigital]

Yes my Sony is only able to play 5.1 EAC3 and only when it's inside a M2TS, if it's inside a MKV I don't have sound.

With 7.1 EAC it doesn't matter if it's a M2TS or a MKV, I never get sound.This would suggest that the audio decoder in your Sony TV is only capable of supporting (5.1) 6-channel E-AC-3 encoded content... Which is currently the maximum number of channels for broadcast and streamed content (with or without Atmos).

[a5180007]

But the {\an8} command doesn't work in TsMuxer Nighly release May 9 2020.

@Nemesh the ASS tags (http://docs.aegisub.org/3.2/ASS_Tags/) are not supported by tsMuxer. You could always open an enhancement feature on Github is somebody is interested to work on this.

[AVX]

Hello, does somebody know if i can generate a mpls that contains calls to multiple m2ts? I bought a BBC 4k bluray and i want to add more audios. There is an option to "play all episodes". This mpls calls the episodes 1 by 1.
I tried to edit it with bdedit but the bluray becomes unusable.
I usually generate the mpls and clpi with tsmuxer because they work flawlessly, but im lost at this point. I can play the episodes individually but i would like to have a 100% functional BD.
https://i.imgur.com/G0dm7Ym.png


As you can see this mpls calls to the episodes individually.

I also tried to make a single m2ts with tsmuxer but it doesnt play correctly either on my oppo.
Has someone succeded in editing a Series BD with tsmuxer?
Thanks!

[a5180007]

Hello, does somebody know if i can generate a mpls that contains calls to multiple m2ts?
@AVX Use tsMuxer to output the m2ts and clpi files, with the same number and PTS offset as the original clpi files.

Use BDEdit to modify / add tracks to the original mpls file.

Unfortunately BDEdit is buggy to add the ATC_delta (aka IsCC5) entry, so you will need to familiarize yourself with the structure of clpi files (https://github.com/lw/BluRay/wiki/ClipInfo) and manually modify the clpi files with an hex editor to add the exact same ATCd entry as in the original clpi files.

[AVX]

@AVX Use tsMuxer to output the m2ts and clpi files, with the same number and PTS offset as the original clpi files.

Use BDEdit to modify / add tracks to the original mpls file.

Unfortunately BDEdit is buggy to add the ATC_delta (aka IsCC5) entry, so you will need to familiarize yourself with the structure of clpi files (https://github.com/lw/BluRay/wiki/ClipInfo) and manually modify the clpi files with an hex editor to add the exact same ATCd entry as in the original clpi files.

Well thank you for the answer.
At least i have something to start testing.
What do you mean by PTS offset?
I am in contact with the dev behind BDedit so ill share this with him.
Thanks mate.

[a5180007]

What do you mean by PTS offset?
I am in contact with the dev behind BDedit so ill share this with him.
PTS = Presentation Time Stamp. The PTS offset is the first PTS in the m2ts packet. In BDEdit, this offset is the "IN Time" in the PLAYLIST tab, which should be the same for each clpi as the "present. st." in the CLIPINF tab. This is what you have to enter in the tsMuxer "Start mux time" under the Blu-ray tab.

Pel has tried to fix the ATCd issue in v0.48 but it still does not work for me. I don't know whether it is fixed in v0.49. Anyway, adding an ATCd entry with an hex editor is quite easy.

[AVX]

PTS = Presentation Time Stamp. The PTS offset is the first PTS in the m2ts packet. In BDEdit, this offset is the "IN Time" in the PLAYLIST tab, which should be the same for each clpi as the "present. st." in the CLIPINF tab. This is what you have to enter in the tsMuxer "Start mux time" under the Blu-ray tab.

Pel has tried to fix the ATCd issue in v0.48 but it still does not work for me. I don't know whether it is fixed in v0.49. Anyway, adding an ATCd entry with an hex editor is quite easy.

Thanks for the answer.
I think he is quite busy but hopefully he will get it fixed in the next update (v0.50)

[B1gD4ddy]

is there a changelog for the brandnew nightly and all the other nightlies?

[varekai]

@justdan96 & a5180007

Thanks for the update! Much appreciated!

[justdan96]

is there a changelog for the brandnew nightly and all the other nightlies?

It's not fully up to date but you can find the main changelog here:
https://github.com/justdan96/tsMuxer/blob/master/CHANGELOG.md

The last nightly from May 9th has been up for a while, there may be a few more nightlies but we might just release the May 9th version as 2.7.0.

[B1gD4ddy]

thank you, and the version from yesterday? and today?

big changes?

[justdan96]

No code changes to tsMuxer at all, just amendments to the scripts in GitHub that produce packages in the Open Build Service (https://build.opensuse.org/package/show/home:justdan96/tsMuxer).

[Emulgator]

Testing tsMuxeR 2020-06-11 (build 7901afa) 64-bit for Blu-ray V2.00 folder muxing

A nice-to-have suggestion before the final build is released:
Pre-loaded default value for Blu-ray V2.00 and V3.00 muxing:
--start-time 524280

A smallish bug:
While exporting a .meta file the file extension .ts is suggested.
Pressing OK without manually going to dropdown "All Files" and removing the superfluous ".ts"
will result in a concatenated and unwanted double file extension .meta.ts
tsMuxeR 2.6.12 does that correctly and suggests file extension .meta

BD-Mux Folderset with AVC 1280x720x50p@28Mbps, duration 48m33s, AC-3 2.0 @192kbps
--start-time no offset, 18 custom chapters in HH:MM:SS.mmm

BDEdit 0.49b:
PLAYLIST finds
IN time 01:10:00.000
OUT time 01:58:33.320

CLIPINF complains: 00000.clpi: lists Packets 56082912.
and pops up window: "The m2ts file contains 56.076.970 packets.
Do you want to correct the packet value of ClipInfo ?"
--
Remuxed BD, this time with typical BD offset --start-time 524250
Checked with BDedit v0.49b: Start time is respected this time.
Number of Packets still diverging.

Investigating...
Manually setting chapters in BDEdit: These are respected by MPC-HC player.
...
BDedit: 11.651s minimum offset it is.
Now Player can skip back to stream start...
BDEdit 11.650s offset:
Player can not skip back to stream start, can only skip back to chapter 2.
On BDedit chapter export this is displayed a 0,1 (0 ticks, the meaning of the second 1 is unknown to me)

Narrowing it down:
tsMuxeR: tick one up: 524250 -> 524251.
This does it. Success.
Preload a minimum of 524251 ticks (or 11,650022222222222222222222222222s)
524280 ticks (or 11,65066666666666666666s) are safe.
On BDedit chapter export this is displayed a 0,1 (0 tick, the meaning of the second 1 is unknown to me)

Auto chaptering every 5min works: Player sees and respects these.
BDedit 0.49b sees these.
PLAYLIST: In BDedit all mark times look offset by 11.650s,
but MPC-HC timeline plays happily at the correct 5:00 positions.

Hmmm, and at the end these 11.650s are missing from BD folder playback in MPC-HC. WTF.
MPC-HC reports total playing time 48:33, but stops after 48:20.

BDedit PLAYLIST sees correct IN time 00:00:11.650
OUT time 00:48:44.970 length 00:48:33.320
Playing the pure 00000.m2ts in MPC-HC: These final 11.650s haven't been muxed into the .m2ts stream,
but were there in the .264 elementary stream before muxing (00:48:33:08 = 145666 frames (0-145665))

This may well be the reason why BDedit 0,49 CLIPINF complains:
00000.clpi lists Packets 56082912
A window pops up: "The m2ts file contains 56.076.970 packets.
Do you want to correct the packet value of ClipInfo ?"

These missing 5942 packets may well be the culprit.
Counterchecking: tsMuxeR 2.6.12 does the same.

tsMuxeR 1.10.6 does it better, lets me have the final 11.650s.
Hardwired first mark time: 00:10:00.000 (10 minutes)
BDedit finds 56032544 packets, won't complain about diverging number of packets.

[a5180007]

A nice-to-have suggestion before the final build is released:
Pre-loaded default value for Blu-ray V2.00 and V3.00 muxing:
--start-time 524280

Depending on the distributors, some Blu-ray PTS start at 2s, some others at 10s, many at 11.650s, others at 1h10s...
What is the community opinion, do we need to change the default 0 ? If so, to what value ?


A smallish bug:
While exporting a .meta file the file extension .ts is suggested.
Pressing OK without manually going to dropdown "All Files" and removing the superfluous ".ts"
will result in a concatenated and unwanted double file extension .meta.ts
tsMuxeR 2.6.12 does that correctly and suggests file extension .meta

Issue opened on Github.


BD-Mux Folderset with AVC 1280x720x50p@28Mbps, duration 48m33s, AC-3 2.0 @192kbps
--start-time no offset, 18 custom chapters in HH:MM:SS.mmm

BDEdit 0.49b:
PLAYLIST finds
IN time 01:10:00.000
OUT time 01:58:33.320

How come that you use a start time = 0, but the mpls file has a start time of 1h10s ? Did you keep the original mpls ?

[outgoing]

Depending on the distributors, some Blu-ray PTS start at 2s, some others at 10s, many at 11.650s, others at 1h10s...
What is the community opinion, do we need to change the default 0 ? If so, to what value ?


Default 0 takes the data as it is original from the mpl, so what kind of need is there to change this behavior, I like it as it is originally from the source.

[Emulgator]

Many thanks for your continued work, a5180007 !
How come that you use a start time = 0, but the mpls file has a start time of 1h10s ? Did you keep the original mpls ?
I muxed from an elementary .avc, so no .mpls was given by me or the stream.
Unintentationally I left the default (0) that the tsmuxerGUI came up with, muxed anyway just to see if the result would be playable.

I continued testing.
Anything below 524250 ticks gives timestamps that look like underflow of a 32-bit register.
This seems to be a limitation of the TS implemetations themselves,
because other muxers (Scenarist) come up with the same start time.
No problem here, but tsMuxeR's v2 muxing end came out premature by the same amount
--------------------------------------------------------
BDedit export of chapter_00000_PTS
shows mark time as <45kHz ticks>,1

mark time = chapter time + --start-time from tsMuxeR (given 11.650s)
Magic Number involved ?

In BDedit inputting an entry mark with mark time
00:00:00.000
delivers a exported chapter time 4294443016,1
which equals
95432,067022222222222222222222222s
Resulting BD is playable from the top, but only once, can not skip back to stream start.

Looks like backwards overflow of a 32-bit counter !
(2^32 = 4294967296)

4294967296 - 4294443016 = 524280 !
There is the magic number.
What power of 2 is next ? 2^19 = 524288.

This offset indicates that somewhere 19 bits might be shifted
for a good reason. Maybe preroll for stuff I don't know at the moment...?

Importing a chapter_00000_PTS with handedited 0 ticks
delivers 11.650s mark time.

Exporting from 11.649s delivers
4294967221,1 ticks
BD can not skip back to stream start.

Exporting from 11.651s:
BD can skip back to stream start.

Test: Rounding from the .ms granularity v into 1/45000s tick granularity
Muxing with --start-time 525250 delivers crap (underflow, see above)
BD can not skip back to stream start.

Muxing with --start-time 524251..294
BD edit sees 11.650s
BDedit exports first chapter as "0,1"
BD can skip back to stream start.

Muxing with --start-time 524295
BD edit sees 11.651s
BDedit exports first chapter as "0,1"
BD can skip back to stream start.
----------------------------------

[Emulgator]

Repeating my tsMuxeR comparisons since I was writing to the same folder and the 3 tsMuxeRs might not have overwritten correctly.
5 muxes of the same content, results came out unchanged:
tsMuxers 2.6.12 and last version seem to lose packets at the end, but 1.10.6 has them muxed playable.

tsMuxeR 1.10.6
--start time is not implemented, GUI has no provision for that
BDedit v0.49b reports first mark time 00:10:00.000 (10min) (so this value seems to be hardwired in tsMuxeR v1), reports no Packets missing.
MPC-HC playback from Bluray-folder and from stream 00000.m2ts: All frames are playable.
tsMuxeR 2.6.12
untouched --start time (GUI reports 00:00:00.000 / 0)
BDedit v0.49b reports first mark time 01:10:00.000 (1hr 10min) (so this value seems to be hardwired in tsMuxeR v2 if 0 is given), reports Packets missing.
MPC-HC playback from Bluray-folder and from stream 00000.m2ts: Both end prematurely ~12s too early.
tsMuxeR 2.6.12
manual --start time (GUI reports 00:00:11.650 / 524280)
BDedit v0.49b reports first mark time 00:00:11.650, reports Packets missing.
MPC-HC playback from Bluray-folder and from stream 00000.m2ts: Both end prematurely ~12s too early.
tsMuxeR 2020-06-11
untouched --start time (GUI reports 00:00:00.000 / 0)
BDedit v0.49b reports first mark time 01:10:00.000 (1hr 10min) (so this value seems to be hardwired in tsMuxeR v2 if 0 is given), reports Packets missing.
MPC-HC playback from Bluray-folder and from stream 00000.m2ts: Both end prematurely ~12s too early.
tsMuxeR 2020-06-11
manual --start time (GUI reports 00:00:11.650 / 524280)
BDedit v0.49b reports first mark time 00:00:11.650, reports Packets missing.
MPC-HC playback from Bluray-folder and from stream 00000.m2ts: Both end prematurely ~12s too early.

mediainfo of the video elementary stream

General
Complete name : J:\4_ES\BD RB\x264 V13 RB 1996.264
Format : AVC
Format/Info : Advanced Video Codec
File size : 9.50 GiB
Overall bit rate mode : Variable
Writing library : x264 core 160 r3000 33f9e14
Encoding settings : cabac=1 / ref=5 / deblock=1:-1:-1 / analyse=0x3:0x133 / me=umh / subme=10 / psy=1 / psy_rd=1.00:0.15 / mixed_ref=1 / me_range=32 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=0,0 / fast_pskip=1 / chroma_qp_offset=-3 / threads=18 / lookahead_threads=1 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=1 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=1 / weightp=0 / keyint=50 / keyint_min=1 / scenecut=40 / intra_refresh=0 / rc_lookahead=50 / rc=2pass / mbtree=1 / bitrate=28000 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=48 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=40000 / vbv_bufsize=30000 / nal_hrd=vbr / filler=0 / ip_ratio=1.20 / aq=1:1.00

Video
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, RefFrames : 4 frames
Bit rate mode : Variable
Bit rate : 28.0 Mb/s
Maximum bit rate : 40.0 Mb/s
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 50.000 FPS
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.608
Writing library : x264 core 160 r3000 33f9e14
Encoding settings : cabac=1 / ref=5 / deblock=1:-1:-1 / analyse=0x3:0x133 / me=umh / subme=10 / psy=1 / psy_rd=1.00:0.15 / mixed_ref=1 / me_range=32 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=0,0 / fast_pskip=1 / chroma_qp_offset=-3 / threads=18 / lookahead_threads=1 / sliced_threads=0 / slices=4 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=1 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=1 / weightp=0 / keyint=50 / keyint_min=1 / scenecut=40 / intra_refresh=0 / rc_lookahead=50 / rc=2pass / mbtree=1 / bitrate=28000 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=48 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=40000 / vbv_bufsize=30000 / nal_hrd=vbr / filler=0 / ip_ratio=1.20 / aq=1:1.00
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

BD RB1996 tsMuxeR 1.10.6.meta
MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray --vbr --custom-chapters=00:00:00.000;00:01:32.080;00:03:17.320;00:05:11.000;00:05:51.720;00:07:49.640;00:10:54.040;00:13:36.440;00:15:27.040;00:16:57.000;00:18:05.360;00:19:04.080;00:23:24.720;00:25:02.960;00:27:23.560;00:30:04.920;00:34:47.400;00:42:05.240 --vbv-len=500
V_MPEG4/ISO/AVC, "J:\4_ES\BD RB\x264 V13 RB 1996.264", fps=50, insertSEI, contSPS
A_AC3, "J:\4_ES\BD RB\V13 RB 1996.ac3", lang=ger

BD RB1996 tsMuxeR 2.6.12 untouched.meta
MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray --vbr --custom-chapters=00:00:00.000;00:01:32.080;00:03:17.320;00:05:11.000;00:05:51.720;00:07:49.640;00:10:54.040;00:13:36.440;00:15:27.040;00:16:57.000;00:18:05.360;00:19:04.080;00:23:24.720;00:25:02.960;00:27:23.560;00:30:04.920;00:34:47.400;00:42:05.240 --vbv-len=500
V_MPEG4/ISO/AVC, "J:\4_ES\BD RB\x264 V13 RB 1996.264", insertSEI, contSPS
A_AC3, "J:\4_ES\BD RB\V13 RB 1996.ac3", lang=ger

BD RB1996 tsMuxeR 2.6.12 524280.meta
MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray --vbr --custom-chapters=00:00:00.000;00:01:32.080;00:03:17.320;00:05:11.000;00:05:51.720;00:07:49.640;00:10:54.040;00:13:36.440;00:15:27.040;00:16:57.000;00:18:05.360;00:19:04.080;00:23:24.720;00:25:02.960;00:27:23.560;00:30:04.920;00:34:47.400;00:42:05.240 --vbv-len=500 --start-time=524280
V_MPEG4/ISO/AVC, "J:\4_ES\BD RB\x264 V13 RB 1996.264", insertSEI, contSPS
A_AC3, "J:\4_ES\BD RB\V13 RB 1996.ac3", lang=ger

BD RB1996 tsMuxeR 2.6.16 untouched.meta
MUXOPT --no-pcr-on-video-pid --new-audio-pes --hdmv-descriptors --blu-ray --vbr --custom-chapters=00:00:00.000;00:01:32.080;00:03:17.320;00:05:11.000;00:05:51.720;00:07:49.640;00:10:54.040;00:13:36.440;00:15:27.040;00:16:57.000;00:18:05.360;00:19:04.080;00:23:24.720;00:25:02.960;00:27:23.560;00:30:04.920;00:34:47.400;00:42:05.240 --vbv-len=500
V_MPEG4/ISO/AVC, "J:\4_ES\BD RB\x264 V13 RB 1996.264", insertSEI, contSPS
A_AC3, "J:\4_ES\BD RB\V13 RB 1996.ac3", lang=ger

BD RB1996 tsMuxeR 2.6.16 524280.meta
MUXOPT --no-pcr-on-video-pid --new-audio-pes --hdmv-descriptors --blu-ray --vbr --custom-chapters=00:00:00.000;00:01:32.080;00:03:17.320;00:05:11.000;00:05:51.720;00:07:49.640;00:10:54.040;00:13:36.440;00:15:27.040;00:16:57.000;00:18:05.360;00:19:04.080;00:23:24.720;00:25:02.960;00:27:23.560;00:30:04.920;00:34:47.400;00:42:05.240 --vbv-len=500 --start-time=524280
V_MPEG4/ISO/AVC, "J:\4_ES\BD RB\x264 V13 RB 1996.264", insertSEI, contSPS
A_AC3, "J:\4_ES\BD RB\V13 RB 1996.ac3", lang=ger

[Emulgator]

And another suggestion, just another nicety for beginners.

2.6.16:The last tsMuxeR version comes up with an empty chapter editor window.
2.6.16 offers 5min auto-chapters, the associated radio button is default.
If user ticks radio button "custom chapters" chapter editor window changes state, and stays empty.
Now if somebody enters the wrong format (frames, or SMPTE), he wont get no lead how to enter correctly.

Using tsMuxeR 1.10.6 one can easily see what chapter format is expected: HH:MM:SS.mmm
1.10.6 offers 5min auto-chapters, the associated radio button is default.
These equally-spaced chapter times are already visible in the still greyed-out chapter editor window.
If user ticks radio button "custom chapters" chapter editor window loses greyed-out and the default equally-spaced chapters become editable.

[a5180007]

If user ticks radio button "custom chapters" chapter editor window changes state, and stays empty.
@Emulgator which OS do you use? On my Windows 10, latest tsMuxer 7b159f6 is working as it should: If user ticks radio button "custom chapters", chapter editor window loses greyed-out and the default equally-spaced HH:MM:SS.mmm chapters become editable.

Edit; same for your "packets missing" issue, I cannot reproduce. Could you please confirm that tsMuxer reports the correct number (i.e. same as reported e.g. by ffmpeg for the original m2ts) of video frames processed, and progress goes up to 100.0% ?

Anybody else has the same issue ?

[Emulgator]

Win7U64 SP1 here, until yesterday I tested only the 64bit version of tsMuxeR 7901afa.
32bit 7901afa still untested, will do that test in the next minutes, see below.

About missing packets: both tsMuxeRs 1.10.6 and 7901afa got fed the same .avc stream,
and BDedit 0.49b finds that discrepancy with new 7901afa and old 2.6.12 from 13.01.2014.
1.10.6 from 11.05.2009 muxes the same stream ok

Right now I haven't yet found 7b159f6 in nightlies...
Once you release 7b159f6 I will test that version too, 32bit and 64bit.

Will continue testing same stream with tsMuxeR 7901afa 32 bit now.

tsMuxeR version git-7901afa. github.com/justdan96/tsMuxer
Decoding H264 stream (track 1): Profile: High@4.1 Resolution:

1280:720p Frame rate: 50
H.264 muxing fps is not set. Get fps from stream. Value: 50
B-pyramid level 1 detected. Shift DTS to 2 frames
H264 bitstream changed: insert pict timing and buffering

period SEI units
Decoding AC3 stream (track 2): Bitrate: 192Kbps Sample Rate:

48KHz Channels: 2
Processed 145666 video frames
Flushing write buffer
Creating Blu-ray stream info and seek index
Creating Blu-ray playlist
Mux successful complete
Muxing time: 6 min 54 sec

All tests with failing muxes show the same:
All tsMuxeR v2 report all .avc frames I had encoded (145666),
progress to 100%, ring and report success.
but muxes seem to miss packets at the end, at least BDEdit tells it so
and Software players stop ~12s prematurely.
(I am not remuxing from a given .m2ts here, I feed a x264 encoded elementary stream)

From the same .avc + .ac3 stream
tsMuxeR 1.10.6 muxes 00000.m2ts with size 10.758.248.448 B
tsMuxeR 2.6.12 32-bit muxes 00000.m2ts with size 10.766.778.368 B
tsMuxeR 7901afa 32-bit muxes 00000.m2ts with size 10.766.778.368 B
tsMuxeR 7901afa 64-bit muxes 00000.m2ts with size 10.766.778.368 B

Will continue that test under WinXP32ProSP3 soonish.

[Emulgator]

a5180007, good guess, there is an OS dependency indeed !

Now on my WinXP32ProSP3 tsMuxeR 2.6.12. muxes ok, the last 12 seconds are playable, BDEdit 0.49b finds no discrepancy.
(But it did not before on my Win7U64SP1.)

Unfortunately tsMuxeR 7901afa 32-bit refuses to start up on WinXP32ProSP3 with an assertion window:
"Der Prozedureinsprungpunkt "Direct3DCreate9Ex" wurde in der DLL "d3d9.dll" nicht gefunden."
"The procedure entry point "Direct3DCreate9Ex" was not found in the DLL "d3d9.dll"".

So I guess that all tsMuxeRs v2 share a small incompatibility with Win7 by birth around 2014,
and additionally an incompatibility with WinXP32 has come up for the new builds since maybe End of 2019.

So I can imagine now why Win10 users may not notice anything.

[staina]

At loaded 3D Bluray with 3D-plane undefined with in "General track options" set 3d offset to "plane 0", but right about to be set "zero".

You can this bug fix? Thank you

[a5180007]

Right now I haven't yet found 7b159f6 in nightlies...
Once you release 7b159f6 I will test that version too, 32bit and 64bit.
@Emulgator 7b159f6 is nightly 2020-05-09, which is same as 2020-06-10 and 2020-06-11 as explained by @justdan96.
I can't help on the bug, I can debug only under Win10.

[Emulgator]

I can't help on the bug, I can debug only under Win10.
Ouch. That would make the newer tsMuxeR builds unusable under WinXP and much worse, even under Win7.
Hopefully a good soul will take up OS compatibilty from here.
To help with that I will go backwards and test all newer 32bit builds to find out which commit might have broken WinXP.

[Emulgator]

If I go from the JFrog repository for me already the first 32bit nightly 2.6.15 from 2019-12-14--14-44-59 seems to break WinXP32 compatibility.
"Der Prozedureinsprungpunkt "Direct3DCreate9Ex" wurde in der DLL "d3d9.dll" nicht gefunden."
"The procedure entry point "Direct3DCreate9Ex" was not found in the DLL "d3d9.dll"".
The (available to me) previous version 2.6.12 starts up properly.
What builds came in between ?

[Emulgator]

Beautiful, with 2020-06-25--02-11-43 Build 0fa0738 chapters list becomes preloaded again on Win7U64 !
Does not yet respect changes in "Insert chapter every <integer> min but still:
Many thanks !

P.S.: No. I had no stream imported, just opened tsMuxer and went to the Blu-ray tab,
so it worked because of no import happening yet.
Once I import a single stream .avc or .ac3, preload chapter values disappear.
So it might be not connected with this build, but should be easier to track now.

P.P.S.: Just tested: That just described behaviour
(GUI losing preloaded chapter values on import of any stream (.avc, .ac3 tested))
was indeed already there in nightly build 2019-12-16, the previous 2019 12-14 GUI does not find its tsMuxeR.exe

[Emulgator]

Strange things here, exporting .meta from GUI (to myself: which?)
seems to lose CR+LF delimiter for the stream command lines, looks concatenated to me (in Windows Notepad, that is)

P.S. Got that now: 2.6.12 uses LF delimiters only ->
Windows Notepad renders concatenated text, notepad++ renders linebreaks

New builds 2.6.16 use CR+LF delimiters ->
Windows Notepad renders linebreaks, notepad++ renders linebreaks, all ok.

Soon I will test CLI...
If I can get my hand on builds in between 2.6.12 and 2.6.15 I would be willing to continue testing these.

[Emulgator]

New 2020-06-25--02-11-43 (64bit Build 0fa0738) CLI with handedited .meta under Win7U64 SP1:
Unchanged. Mux Progress to 100%, success reported, all .avc frames I had encoded are reported (145666).

BD folder Playback ends ~12s prematurely in MPC-HC.
BDedit 0.49b reads 56082912 packets from 00000.clpi,
finds only 56076970 packets, this makes 5942 missing packets.

[a5180007]

Ouch. That would make the newer tsMuxeR builds unusable under WinXP and much worse, even under Win7.
Hopefully a good soul will take up OS compatibilty from here.

@Emulgator the good soul might be @BloodyRipper (aka xavery on Github), he has worked quite a lot on the GUI for XP.

If I can get my hand on builds in between 2.6.12 and 2.6.15 I would be willing to continue testing these.
No open source available for versions prior to 2.6.15.

[filler56789]

Ouch. That would make the newer tsMuxeR builds unusable under WinXP and much worse, even under Win7.

The latest tsMuxer GUI works normally under my 64-bit Windows 7 :confused:
But then I don't let the OS update itself, to begin with...

Regarding XP especifically, many posts ago I suggested that someone :rolleyes: should create a dot-NET GUI for tsMuxer because everybody knows the QT devilopers are totally Linux-centric so to speak ;)

[BloodyRipper]

If I go from the JFrog repository for me already the first 32bit nightly 2.6.15 from 2019-12-14--14-44-59 seems to break WinXP32 compatibility.
"Der Prozedureinsprungpunkt "Direct3DCreate9Ex" wurde in der DLL "d3d9.dll" nicht gefunden."
"The procedure entry point "Direct3DCreate9Ex" was not found in the DLL "d3d9.dll"".
The (available to me) previous version 2.6.12 starts up properly.
What builds came in between ?

The builds (i.e. the regular 32-bit Windows binary and the special Windows XP GUI that's currently only available as an actions artefact) work fine on my Windows XP virtual machine, but I do have DirectX 9.0c installed there (I don't recall installing it explicitly, so it must've been already installed with the rest of the system), and that message is hinting that it might be missing. Please try installing DirectX 9.0c (https://www.microsoft.com/en-us/download/details.aspx?id=34429) and report back.

We don't make use of any DirectX functions directly, but I suppose the dependencies might be injected there indirectly by the compiler and/or the runtime library. The previous (i.e. pre-github) versions were compiled with a different compiler than the one we're currently using, so it is the most obvious suspect.
Regarding XP especifically, many posts ago I suggested that someone :rolleyes: should create a dot-NET GUI for tsMuxer because everybody knows the QT devilopers are totally Linux-centric so to speak ;)Qt is well supported on Windows. If you want to make a new GUI, by all means go ahead - the current GUI source is there to help you, but be aware that it does show its age and there's a lot of stuff that certainly isn't obvious at first glance. Also remember that the GUI is tied to the main binary version by the syntax of the "stream detection mode" output so the GUI can obtain necessary track information. However, seeing how we're trying to maintain backwards compatibility, old versions of the syntax will probably remain supported if it ever changes, potentially with limited functionality.

[filler56789]

The builds (i.e. the regular 32-bit Windows binary and the special Windows XP GUI that's currently only available as an actions artefact) work fine on my Windows XP virtual machine, but I do have DirectX 9.0c installed there (I don't recall installing it explicitly, so it must've been already installed with the rest of the system), and that message is hinting that it might be missing. Please try installing DirectX 9.0c (https://www.microsoft.com/en-us/download/details.aspx?id=34429) and report back.

Note: Direct3DCreate9Ex is supported only in Windows Vista, Windows Server 2008, and Windows 7. Earlier versions of the D3D9.dll library do not include Direct3D9Ex and Direct3DCreate9Ex.

source: https://docs.microsoft.com/en-us/windows/win32/api/d3d9/nf-d3d9-direct3dcreate9ex

[BloodyRipper]

Note: Direct3DCreate9Ex is supported only in Windows Vista, Windows Server 2008, and Windows 7. Earlier versions of the D3D9.dll library do not include Direct3D9Ex and Direct3DCreate9Ex.

source: https://docs.microsoft.com/en-us/windows/win32/api/d3d9/nf-d3d9-direct3dcreate9ex
What does the virtual machine bit have to do with anything? I have also tested these binaries with an actual Windows XP desktop sporting a Pentium 3 (screenshots available earlier in the thread), so I'm quite confident they should work on most, if not all standard-ish XP setups. I just find it easier to launch a VM for a quick test instead of taking an old computer out of the closet.

@Emulgator : Sorry about the confusion - I assumed you meant the commandline binary the whole time, which should work just fine on XP. If you want the use the GUI, you'll have to download a special build for Windows XP available here (https://github.com/justdan96/tsMuxer/actions/runs/146484594) or here (https://a.uguu.se/lWMiCFK1QYuN.7z) if you don't want to create a github account, but the link is only valid for 24 hours.

[filler56789]

What does the virtual machine bit have to do with anything?

Well, if I hadn't emphasized it, probably you would not wake up ;)

[Emulgator]

Thanks, Bloodyripper !
you'll have to download a special build for Windows XP available here or here if you don't want to create a github account, but the link is only valid for 24 hours.
Oh sorry, missed that one, was off for the weekend, can you please reupload the WinXP GUI?
24 hrs server up is quite brief, maybe use wetransfer, this would hold one week.

P.S. Well, I just opened an account on github, got the file..

[Emulgator]

Beautiful ! Under WinXP32ProSP3 BloodyRippers WinXP GUI throws no error on startup.

BD-Mux Folderset with AVC 1280x720x50p@28Mbps, duration 48m33s, AC-3 2.0 @192kbps
--start-time 524280, 18 custom chapters in HH:MM:SS.mmm

-------------------WinXP32ProSP3-------------------
32-bit CLI muxer d2c38c5:
Progressing...Success !
BDedit 0.49b finds no packet discrepancies, MPC-HC stream playback until the end.

32-bit WinXP GUI 2.6.16-dev + last muxer d2c38c5:
Progressing...Success !
BDedit 0.49b finds no packet discrepancies, MPC-HC stream playback until the end.
--------------------Win7U64SP1---------------------------
32-bit CLI muxer d2c38c5:
Progressing...Success !
BDedit 0.49b finds no packet discrepancies, MPC-HC stream playback until the end.

32-bit GUI + muxer d2c38c5:
Progressing...Success !
BDedit 0.49b finds no packet discrepancies, MPC-HC stream playback until the end.

64-bit CLI muxer d2c38c5:
Progressing...Success !
BDedit 0.49b finds no packet discrepancies, MPC-HC stream playback until the end.

64-bit GUI + muxer d2c38c5:
Progressing...Success !
BDedit 0.49b finds no packet discrepancies, MPC-HC stream playback until the end.

And the default .meta file extension is back, nice.

[Emulgator]

Emulgator: Ouch. That would make the newer tsMuxeR builds unusable under WinXP and much worse, even under Win7.
filler56789: The latest tsMuxer GUI works normally under my 64-bit Windows 7
But then I don't let the OS update itself, to begin with...

Sorry for ambiguity: Both 32 and 64bit GUIs seem to work here under Win7U64SP1
and they won't be able to bork the .meta files on passing towards cutting packets I guess.

What I meant to say was: the connected tsMuxeR.exes probably might lose ~12s worth of packets
under Win7U64SP1 from that 1280x720x50p elementary .avc around end.
Will test other framerate/resolutions if necessary.

P.S. At the moment under WinXP32ProSP3 the new 32-bit tsMuxeR.exe CLI works fine with my .avc test stream,
even better: all new d2c38c5 versions 32 bit and 64 bit, CLI and GUI seem to mux to the end under Win7, see above.

[B1gD4ddy]

build from 27.06 has a bug at least for me.
i unpacked a complete iso, removed some audio and subs with tsmuxer and then saved it as iso and tsmuxer put the m2ts in the root of the iso instead in the bdmv\stream folder.
and thus cant be played
older builds work fine.

[Emulgator]

2020-07-27: Unfortunately with a longer .avc stream 1280x720x50p I seem to get missing packets again.
Win7U64SP1

BD-Mux Folderset with AVC 1280x720x50p@28Mbps, duration 1h44m43s, AC-3 2.0 @192kbps
--start-time 524280, 37 custom chapters in HH:MM:SS.mmm

00000.clpi says 120.949.280, BDedit 0.49b finds 120.946.688 packets,
2592 packets missing.
MPC-HC 1.9.6 Playback ends 7 seconds prematurely.
---
Different project, different streams:
BD-Mux Folderset with AVC 1280x720x50p@25Mbps, duration 1h59m46s, AC-3 2.0 @192kbps
--start-time 524280, 9 custom chapters in HH:MM:SS.mmm
BDedit 0.49b finds 123.679.296 packets, no packets missing.
MPC-HC 1.9.6 Playback until end.

For me it means back to 1.10.6 if AVC 1280x720x50p.
1.10.6 muxed all these streams perfectly again.
MPC-HC plays until end, BDedit doesn't complain.

[BloodyRipper]

And the default .meta file extension is back, nice.This was caused by a mishap while introducing multilanguage support.

Beautiful ! Under WinXP32ProSP3 BloodyRippers WinXP GUI throws no error on startup.I will look into providing this GUI by default in 32-bit Windows builds. This way, 32-bit builds will be runnable as a whole all the way down to Windows XP with the oldest processors possible (including pre-SSE ones), while 64-bit builds will use newer Qt versions and possibly leverage compiler optimisations that are possible with newer CPUs. All users should generally use the 64-bit version unless they have a strong reason not to, as it _might_ look better and run faster.

build from 27.06 has a bug at least for me.
i unpacked a complete iso, removed some audio and subs with tsmuxer and then saved it as iso and tsmuxer put the m2ts in the root of the iso instead in the bdmv\stream folder.
and thus cant be played
older builds work fine.
This is fixed in 2020-07-02--02-15-39.

[ryu34]

Hey does the 2019 shield pro support any native playback of the 4k dolby vision remuxes this version of tsmuxer creates?

[yannick92]

Hello,

Here's my problem:
I need to re-encode a MKV / VC-1 movie in H264 to play it on my PS3.
Indeed, this one does not read the VC-1 codec in TS file, and M2TS, I also remind that it does not read MKV.

Well, I'm used to remuxing all of my MKV / H264 to M2TS with TsMuxer, and never any problem reading them on PS3.
So here we are, this MKV / VC-1 therefore needs to be re-encoded in H264, and in my specific case to be encapsulated in M2TS or TS to be fully compatible with the PS3.
You follow me ?

Nothing too complicated you tell me, so here is my approach and why I can't do it ...
To re-encode certain HD movies in H264, I use CloneBD for its simplicity and quality of encoding without getting lost in unnecessary settings ...
But as you probably know, CloneBD does not know how to directly open an MKV, TS, M2TS file ...
It requires opening films in Bluray ISO, Bluray folder or AVCHD folder format exclusively!

So I'm going to need to make an ISO of my MKV file for after being able to open it with CloneBD, so I chose TsMuxer (git-632b6e4) for that.
So I open my MKV with TSMuxer (which is for information an "untouched" Remux with just the languages ​​and subtitles), I chose Bluray-ISO for muxing, and START.

I get my ISO, I launch CloneBD or I can now open my movie in ISO, everything is going well, I choose my encoding parameters, in my case "Full quality H264" for the video and "same as source" for audio, all this in MKV for encapsulation.
And there, when I want to start the encoding, it is the drama, CloneBD crash, the window freezes, and when I click on it it displays the famous "CloneBD do not answer" "want to leave you or wait until the program responds? "...

I tried again, always the same, by redoing an ISO with TsMuxer, same, I even tried with an AVCHD Folder and Bluray Folder structure, same problem ...
Will there be a bug with TsMuxer and Bluray ISO structures?

To be clear, I should point out that if I open another "original" ISO Bluray, without going through TsMuxer, CloneBD works very well when encoding!
I of course also tested with TsMuxer to make an ISO with another MKV file, same observation, CloneBD crash ...

Interesting comparison, via DVDfab, the Bluray ISO files made by TsMuxer do not crash !? (But I don't like DVDfab ...)
Someone would have any idea ?
Come to think of it, I am at a dead end, and question to $ 1,000,000, how can I properly convert my MKV file to Bluray ISO so that I can then encode it with CloneBD?

Here is a sample of my MKV for your possible investigations. https://uptobox.com/a6y3j3svbusf

Thank you very much in advance if you find the source of the problem, see you soon.

Yannick

EDIT: To be sure, I have just tested with TsMuxer 1.10.6, same procedure and it works !!!
CloneBD does not crash any more, the encoding is launched without problem!

There is a problem with the last nighly, right?

Yannick

[a5180007]

There is a problem with the last nighly, right?


Having tried previous versions, this behavior appeared with version of 21 March. I've pushed a reversion (https://github.com/justdan96/tsMuxer/pull/314)on previous patch, this bug should be fixed once the proposed patch has been merged.

Edit: @yannick92 please try latest version on Bintray nightly-2020-07-18--02-16-00.

[Richard1485]

Files with the .dtshd extension are not seen unless the user changes All supported media files to All files. Is it possible for .dtshd to be added to the former so they are visible by default? There's no trouble with these files. It's just the extension.

[staina]

Having tried previous versions, this behavior appeared with version of 21 March. I've pushed a reversion (https://github.com/justdan96/tsMuxer/pull/314)on previous patch, this bug should be fixed once the proposed patch has been merged.

Edit: @yannick92 please try latest version on Bintray nightly-2020-07-18--02-16-00.

1. What effect has this change to creation UHD 4K Bluray ISO and directories?
2. At comparison result from latest version and previous version are there different files M2TS and CLPI has it some influence on playback in multimedia players?
3. What this change one's parameter makes at creation UHD 4k Bluray?

Thank for responses. staina

[yannick92]

Having tried previous versions, this behavior appeared with version of 21 March. I've pushed a reversion (https://github.com/justdan96/tsMuxer/pull/314)on previous patch, this bug should be fixed once the proposed patch has been merged.

Edit: @yannick92 please try latest version on Bintray nightly-2020-07-18--02-16-00.
Ok thx

I just tested with the nightly-2020-07-18--02-16-00, it works very well, after doing my .ISO with TsMuxer, CloneBD does not crash anymore when encoding!

Thank you so much,
see you soon.

Yannick

[BloodyRipper]

Files with the .dtshd extension are not seen unless the user changes All supported media files to All files. Is it possible for .dtshd to be added to the former so they are visible by default? There's no trouble with these files. It's just the extension.This will be included in 2020-07-22 nightly.

[yannick92]

Hello

Small problem, I wanted to split an MKV file for my Fat 32 USB hard drive (max 4 GB per file), I select "Split by Size" every 4,000 GB ok? I run the mux in .TS, and
TsMuxer copies hundreds of randomly cut files to me ??
There is nothing to understand, unusable as it is of course ...

An idea gentlemen?
Especially since it works very well with TsMuxer 1.10.6

Thx a lot.

Yannick

EDIT: Also tested with w64-nightly-2020-07-22--02-14-59
same problem...

[Richard1485]

This will be included in 2020-07-22 nightly.

Thank you for seeing to this. It will make things easier. :)

[BloodyRipper]

Hello

Small problem, I wanted to split an MKV file for my Fat 32 USB hard drive (max 4 GB per file), I select "Split by Size" every 4,000 GB ok? I run the mux in .TS, and
TsMuxer copies hundreds of randomly cut files to me ??
There is nothing to understand, unusable as it is of course ...

An idea gentlemen?
Especially since it works very well with TsMuxer 1.10.6

Thx a lot.

Yannick

EDIT: Also tested with w64-nightly-2020-07-22--02-14-59
same problem...
I can't reproduce this with my "larger" MKV files with splitting set to 4GB or 4GiB or smaller files with splitting set to other thresholds, for example 300MB.
Please post the metafile that you're using. Perhaps this is related to how your particular file is handled.

[yannick92]

I can't reproduce this with my "larger" MKV files with splitting set to 4GB or 4GiB or smaller files with splitting set to other thresholds, for example 300MB.
Please post the metafile that you're using. Perhaps this is related to how your particular file is handled.

Okay
I tested with 2 .MKV files that I have already split with MkvToolnix to reduce the size for my encoding tests with Handbrake, they are between 5 and 8 GB, I will not be able to upload them ...
Could a MediaInfo log help you?

THX

Yannick

Général
Identifiant unique : 135129523374164645483133722259422988883 (0x65A8FFE218B02EBC183F0C6F4A444A53)
Nom complet : C:\Users\Yannick\Videos\Batman Test Handbrake VBR.mkv
Format : Matroska
Version du format : Version 4
Taille du fichier : 6,38 Gio
Durée : 30 min 0s
Débit global moyen : 30,5 Mb/s
Nom du film : THE_DARK_KNIGHT.2008.VFF_VO.BLURAY.REMUX.MKV
Date d'encodage : UTC 2020-07-16 20:04:17
Application utilisée : HandBrake 1.3.3 2020061300
Bibliothèque utilisée : Lavf58.29.100
ErrorDetectionType : Per level 1

Vidéo
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Profil du format : High@L4.1
Paramètres du format : CABAC / 4 Ref Frames
Paramètres du format, CABAC : Oui
Paramètres du format, RefFrames : 4 images
Identifiant du codec : V_MPEG4/ISO/AVC
Durée : 30 min 0s
Débit : 30,0 Mb/s
Largeur : 1 920 pixels
Hauteur : 1 080 pixels
Format à l'écran : 16/9
Type d'images/s : Constant
Images par seconde : 23,976 (24000/1001) Im/s
Espace de couleurs : YUV
Sous-échantillonnage de la chrominance : 4:2:0
Profondeur des couleurs : 8 bits
Type de balayage : Progressif
Bits/(Pixel*Image) : 0.603
Taille du flux : 6,16 Gio (97%)
Bibliothèque utilisée : x264 core 157 r2935 545de2f
Paramètres d'encodage : cabac=1 / ref=4 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=10 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=6 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=8 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=240 / keyint_min=24 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=2pass / mbtree=1 / bitrate=30000 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=62500 / vbv_bufsize=78125 / nal_hrd=none / filler=0 / ip_ratio=1.40 / aq=1:1.00
Default : Oui
Forced : Non
Gamme de couleurs : Limited
Coordonnées de chromaticité : BT.709
Caractéristiques du transfert : BT.709
Coefficients de la matrice : BT.709

Audio
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Nom commercial : Dolby Digital
Identifiant du codec : A_AC3
Durée : 30 min 0s
Type de débit : Constant
Débit : 448 kb/s
Canaux : 6 canaux
Channel layout : L R C LFE Ls Rs
Echantillonnage : 48,0 kHz
Images par seconde : 31,250 Im/s (1536 SPF)
Mode de compression : Avec perte
Taille du flux : 96,2 Mio (1%)
Titre : Surround
Langue : Français
Service kind : Complete Main
Default : Oui
Forced : Non

[von Suppé]

For a thread at VH I did some quick tests with importing a m2ts file only into tsMuxer and exporting as BD folder structure.
These tests were to find out if the results could be imported into MakeMKV without errors.

My findings say that if I use tsMuxer version 2.6.12, MakeKMV accepts the resulting BD perfectly.

Using the nightly portable (2020-07-22 64 bit), after import into MakeMKV, it returns with an error ("Failed to decode audio/video data for title #0 - invalid mux or internal error")

Eventhough the output performs well for my pc and mediaplayers and it seems to be okay further, is this something that must be looked into?

[outgoing]

Maybe a possible bug (tsMuxerGUI.exe CRC-32: f060620b It seems to me that this is the last or penultimate release). When I make a mux and apply a negative delay to the audio from the tsmuxer itself, the result is that the In time changes from the origianl and it doesn't play when you recreate the full bluray again. However, if I make the mux without applying the negative delay, the bluray (remain with the same In time from original) can be reassembled and played.

[yannick92]

Okay
I tested with 2 .MKV files that I have already split with MkvToolnix to reduce the size for my encoding tests with Handbrake, they are between 5 and 8 GB, I will not be able to upload them ...
Could a MediaInfo log help you?

THX

Yannick

Général
Identifiant unique : 135129523374164645483133722259422988883 (0x65A8FFE218B02EBC183F0C6F4A444A53)
Nom complet : C:\Users\Yannick\Videos\Batman Test Handbrake VBR.mkv
Format : Matroska
Version du format : Version 4
Taille du fichier : 6,38 Gio
Durée : 30 min 0s
Débit global moyen : 30,5 Mb/s
Nom du film : THE_DARK_KNIGHT.2008.VFF_VO.BLURAY.REMUX.MKV
Date d'encodage : UTC 2020-07-16 20:04:17
Application utilisée : HandBrake 1.3.3 2020061300
Bibliothèque utilisée : Lavf58.29.100
ErrorDetectionType : Per level 1

Vidéo
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Profil du format : High@L4.1
Paramètres du format : CABAC / 4 Ref Frames
Paramètres du format, CABAC : Oui
Paramètres du format, RefFrames : 4 images
Identifiant du codec : V_MPEG4/ISO/AVC
Durée : 30 min 0s
Débit : 30,0 Mb/s
Largeur : 1 920 pixels
Hauteur : 1 080 pixels
Format à l'écran : 16/9
Type d'images/s : Constant
Images par seconde : 23,976 (24000/1001) Im/s
Espace de couleurs : YUV
Sous-échantillonnage de la chrominance : 4:2:0
Profondeur des couleurs : 8 bits
Type de balayage : Progressif
Bits/(Pixel*Image) : 0.603
Taille du flux : 6,16 Gio (97%)
Bibliothèque utilisée : x264 core 157 r2935 545de2f
Paramètres d'encodage : cabac=1 / ref=4 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=10 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=6 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=8 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=240 / keyint_min=24 / scenecut=40 / intra_refresh=0 / rc_lookahead=60 / rc=2pass / mbtree=1 / bitrate=30000 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=62500 / vbv_bufsize=78125 / nal_hrd=none / filler=0 / ip_ratio=1.40 / aq=1:1.00
Default : Oui
Forced : Non
Gamme de couleurs : Limited
Coordonnées de chromaticité : BT.709
Caractéristiques du transfert : BT.709
Coefficients de la matrice : BT.709

Audio
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Nom commercial : Dolby Digital
Identifiant du codec : A_AC3
Durée : 30 min 0s
Type de débit : Constant
Débit : 448 kb/s
Canaux : 6 canaux
Channel layout : L R C LFE Ls Rs
Echantillonnage : 48,0 kHz
Images par seconde : 31,250 Im/s (1536 SPF)
Mode de compression : Avec perte
Taille du flux : 96,2 Mio (1%)
Titre : Surround
Langue : Français
Service kind : Complete Main
Default : Oui
Forced : Non


It's odd that you can't reproduce this bug, it is systematic on all the MKV that I tested?
Attached is a capture of the split files that I get ...

17467

[tebasuna51]

@yannick92

I can confirm the problem, I checked the split with 2 mkv's and tsMuxeR split the file by keyframes (the same number of fragments than keyframes) ignoring the size.

The metafile:

MUXOPT --no-pcr-on-video-pid --new-audio-pes --hdmv-descriptors --vbr --split-size=3,000GB --vbv-len=500
V_MPEG4/ISO/AVC, "D:\Temp\test.mkv", insertSEI, contSPS, track=1, lang=eng
...

I don't know if the "3,000GB" can be a problem. I put "3" without decimals in the capture and is the same.

EDIT:
That is the problem, with the .meta file edited to "3GB" or "3.000GB" works fine

[BloodyRipper]

@tebasuna51 @yannick92

Thanks a lot. Another locale issue, since tsMuxer is hardcoded to use a decimal dot when parsing this particular argument. Since my locale uses a dot as well, I obviously could not reproduce it. This should be fixed in 2020-08-18 nightly.

[tebasuna51]

Thanks, problem solved.

[Emulgator]

A small wish to the developers:
I would welcome the usual changelog per build where one can see what has changed.
The release notes add up what has been achieved for Version 2.6.16, but do not mention the various builds.
Right now from 2019 12 14 until today I have 146 builds sitting in my tsMuxeR folder, so bugtracking becomes a bit hard.

[maxibon]

A subtitle bug or a wish to the developers

When I change the color of a subtitle in a UHD Bluray only if the format is srt works fine. Could if possible working as well if codec is pgs?

Let me show some images what's happening

https://t45.pixhost.to/thumbs/142/160272394_anotacion-2020-08-30-075959.png (https://pixhost.to/show/142/160272394_anotacion-2020-08-30-075959.png)

https://t45.pixhost.to/thumbs/142/160272395_anotacion-2020-08-30-080150.png (https://pixhost.to/show/142/160272395_anotacion-2020-08-30-080150.png)

Result ok with srt

https://t45.pixhost.to/thumbs/142/160272396_anotacion-2020-08-30-080337.png (https://pixhost.to/show/142/160272396_anotacion-2020-08-30-080337.png)

Same color if pgs

https://t45.pixhost.to/thumbs/142/160272399_anotacion-2020-08-30-080444.png (https://pixhost.to/show/142/160272399_anotacion-2020-08-30-080444.png)

Regards

[r0lZ]

PGS subtitles are in graphic format. The colors are in the image. And there can be any number of colors in a single subtitle. The only way to change the colors is to convert the subtitles to XML/PNG (with BDSup2Sub for example), edit the PNG images with a graphic programs, and convert them back to BD SUP.
In the other hand, a SRT is a simple text, converted to graphics at playback time. Therefore the color is not dependent of the subtitle stream, and you can change it easily.

[maxibon]

Could yo tell me which graphic programs should I use in order to edit PNG images?

Thanks

[ocean]

Hi everyone, I don't know if the topic has already been raised, but BDinfo after the mux with tsMuxeR, reads the Bitrate of the Blu-Ray, but not those of the Blu-Ray UHD, the problem is in the m2ts container, here are 2 examples:

Blu-ray

https://i.ibb.co/qDHm8LB/Immagine.png (https://ibb.co/qDHm8LB)


Blu-Ray UHD

https://i.ibb.co/M5MKd3C/Immagine-copy.png (https://ibb.co/M5MKd3C)

[MrVideo]

Could yo tell me which graphic programs should I use in order to edit PNG images?
PhotoShop ($$$$)
Gimp (Free)

[MrVideo]

I just noticed that the GUI About tab doesn't list the version number. I understand that all of the nightly builds are the same version, so the nightly build date should be listed as well.

[outgoing]

Hi everyone, I don't know if the topic has already been raised, but BDinfo after the mux with tsMuxeR, reads the Bitrate of the Blu-Ray, but not those of the Blu-Ray UHD, the problem is in the m2ts container, here are 2 examples:


This bug reminds me of a similar one in another program. The metadata is broken to be able to list the bitrate properly. If it is confirmed it is an error that should be fixed.

Glad to see you here again. :D

[mariner]

Greetings to all for creating this wonderful tool.

Two questions:

1. Is DD+ 5.1 sound track supported when creating BDMV folder? It appears some have reported getting error 135 message when doing so.

2. Can this be used to create BDMV consisting of multiple HEVC titles? Or any suggestion for a suitable tool?

Many thanks and best regards,

[MrVideo]

I can crash the Sep 6th nightly build (Win7-64) extremely easily. Just do a remove of any of the tracks and you can easily cause it to crash. Changing the order of the track removal can make it not crash, but after a successful M2TS muxing, doing a remove of the imported files resulted in a crash when removing that last of the two files.

Going back to the June 1st build results in it working, without crashing.

[ocean]

Hi outgoing thank you, nice to see you again, the problem described above, I found an analogy in the encoder used, ATEME Titan File 3.9.0 (4.9.0.0), the titles that use this encoder generate the problem.

[a5180007]

BDinfo after the mux with tsMuxeR, reads the Bitrate of the Blu-Ray, but not those of the Blu-Ray UHD, the problem is in the m2ts container

Should be fixed in the Bintray nightly-2020-09-13--02-21-33.

[outgoing]

Nice, great work!!

[iSeries]

Not sure if this is a bug or not but using the latest nightly, remuxing full disc backup of Midsommar Director's Cut to m2ts, tsMuxer is adding a -13 second audio delay relative to video (shown in MediaInfo). No delay is indicated in the original playlist/m2ts. I have no idea how to stop tsMuxer from adding this delay.

[imhh11]

Hi, I'm having this issue with the latest build (2020-09-13--02-21-33 )

https://ibb.co/9yPxzQn

[a5180007]

Hi, I'm having this issue with the latest build (2020-09-13--02-21-33 )

https://ibb.co/9yPxzQn
@imhh11 sorry, my mistake... The next Bintray nightly should fix this.

[imhh11]

thank you @a5180007

[varekai]

@a5180007 and justdan96
Thanks for the continuing tsMuxer updates, much appreciated!

[BloodyRipper]

I can crash the Sep 6th nightly build (Win7-64) extremely easily. Just do a remove of any of the tracks and you can easily cause it to crash. Changing the order of the track removal can make it not crash, but after a successful M2TS muxing, doing a remove of the imported files resulted in a crash when removing that last of the two files.

Going back to the June 1st build results in it working, without crashing.
Should be fixed starting with 2020-09-17--02-22-29 (https://bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly/2020-09-17--02-22-29#files), please report if this keeps happening.

[Peter_A]

I found an issue with an audio delay being introduced, according to MediaInfo, and the audio/video sync is off during playback, when using version 2020-09-18--02-23-09.

Using the same source and version 2020-06-25--02-11-43 (with the same settings), there is no delay introduced, and video/audio sync appears to be correct.

I'm not sure what's causing this, or in which version this started (since I jumped from 6/25 to 9/28). Any idea what the issue may be?

Using version 2020-09-18--02-23-09
Audio #1
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : DTS XLL
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Muxing mode : Stream extension
Codec ID : 134
Duration : 1 h 42 min
Bit rate mode : Variable
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossless
Delay relative to video : -1 s 668 ms
Language : English
Source : 00000.m2ts / 00000.m2ts

Audio #2
ID : 4353 (0x1101)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 1 h 42 min
Bit rate mode : Constant
Bit rate : 224 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : -1 s 668 ms
Stream size : 165 MiB
Language : English
Service kind : Complete Main
bsid : 6
Dialog Normalization : -27
Dialog Normalization : -27 dB
compr : 1.94
compr : 1.94 dB
dynrng : 1.26
dynrng : 1.26 dB
dsurmod : 1
dsurmod : Not Dolby Surround encoded
acmod : 2
lfeon : 0
dialnorm_Average : -27
dialnorm_Average : -27 dB
dialnorm_Minimum : -27
dialnorm_Minimum : -27 dB
dialnorm_Maximum : -27
dialnorm_Maximum : -27 dB
dialnorm_Count : 1100
compr_Average : 2.20
compr_Average : 2.20 dB
compr_Minimum : -1.80
compr_Minimum : -1.80 dB
compr_Maximum : 5.74
compr_Maximum : 5.74 dB
compr_Count : 828
dynrng_Average : 1.79
dynrng_Average : 1.79 dB
dynrng_Minimum : -1.97
dynrng_Minimum : -1.97 dB
dynrng_Maximum : 5.88
dynrng_Maximum : 5.88 dB
dynrng_Count : 1058
format_identifier : AC-3
Source : 00000.m2ts / 00000.m2ts

Using version 2020-06-25--02-11-43
Audio #1
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : DTS XLL
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Muxing mode : Stream extension
Codec ID : 134
Duration : 1 h 42 min
Bit rate mode : Variable
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossless
Language : English
Source : 00000.m2ts / 00000.m2ts

Audio #2
ID : 4353 (0x1101)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 1 h 42 min
Bit rate mode : Constant
Bit rate : 224 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 165 MiB
Language : English
Service kind : Complete Main
bsid : 6
Dialog Normalization : -27
Dialog Normalization : -27 dB
compr : 1.94
compr : 1.94 dB
dynrng : 1.26
dynrng : 1.26 dB
dsurmod : 1
dsurmod : Not Dolby Surround encoded
acmod : 2
lfeon : 0
dialnorm_Average : -27
dialnorm_Average : -27 dB
dialnorm_Minimum : -27
dialnorm_Minimum : -27 dB
dialnorm_Maximum : -27
dialnorm_Maximum : -27 dB
dialnorm_Count : 1090
compr_Average : 2.23
compr_Average : 2.23 dB
compr_Minimum : -1.80
compr_Minimum : -1.80 dB
compr_Maximum : 5.74
compr_Maximum : 5.74 dB
compr_Count : 818
dynrng_Average : 1.80
dynrng_Average : 1.80 dB
dynrng_Minimum : -1.97
dynrng_Minimum : -1.97 dB
dynrng_Maximum : 5.88
dynrng_Maximum : 5.88 dB
dynrng_Count : 1048
format_identifier : AC-3
Source : 00000.m2ts / 00000.m2ts

[FilipeAmadeuO]

Audio delay bug seems to be acorrected in today binary:
https://github.com/justdan96/tsMuxer/commit/6fb457b961734fbdf20d95fc65623563480bc176

[Peter_A]

Audio delay bug seems to be acorrected in today binary:
https://github.com/justdan96/tsMuxer/commit/6fb457b961734fbdf20d95fc65623563480bc176

Thanks. I'll test the new version out. I did check for an update yesterday and did not see one, but I did not check today before posting (which I should have done).

Have the releases been pretty stable lately, in general?

[imhh11]

@a5180007

For the dual layer profile 7.06 TS files, it says: Dolby Vision, Version 1.0, dvhe.07.06, EL+RPU, 8 compatible / SMPTE ST 2086, HDR10 compatible
for the dual layer profile 7.06 MP4 files, it says Dolby Vision, Version 1.0, dvhe.07.06, EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible

what is ''8 compatible'' ? this is a long shot but could it be the reason of the bug with the dual layer DV TS/M2TS files on the Sony x700? I think it worth a try.

thank you !

[cogira]

@a5180007

For the dual layer profile 7.06 TS files, it says: Dolby Vision, Version 1.0, dvhe.07.06, EL+RPU, 8 compatible / SMPTE ST 2086, HDR10 compatible
for the dual layer profile 7.06 MP4 files, it says Dolby Vision, Version 1.0, dvhe.07.06, EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible

what is ''8 compatible'' ? this is a long shot but could it be the reason of the bug with the dual layer DV TS/M2TS files on the Sony x700? I think it worth a try.

thank you !

+1
I have the same problem since long time ago.

[a5180007]

what is ''8 compatible'' ?
@imhh11 you might have something. The Dolby spec 1.2 for the Dovi descriptor is:

https://i.imgur.com/shJ7WXg.png

However:
Mediainfo Code for decoding the descriptor (https://github.com/MediaArea/MediaInfoLib/blob/702d6b20c7bdaccf2dc2b7c5d6ceca673d5c608a/Source/MediaInfo/Multiple/File_Mpeg_Descriptors.cpp#L3457)

Ffmpeg Code for decoding the descriptor (https://github.com/FFmpeg/FFmpeg/blob/e71d73b09652f4fc96e512a7d6d4c2ab41860f27/libavformat/mpegts.c#L2170)

Neither ffmpeg nor mediainfo read the dependency_pid, they read directly the compatibility_id !!! Hence the 8 (first nibble of PID 0x1011).

So as version 1 seems to be incorrect, I will change the descriptor to version 2 major, and put the reading of the compatibility_id just after reading the BL flag.

[yannick92]

Hello,

What future for the new "IETF BCP 47 language tags" and its implementation in TsMuxer?
thx

https://gitlab.com/mbunkus/mkvtoolnix/-/wikis/Languages-in-Matroska-and-MKVToolNix

[imhh11]

So as version 1 seems to be incorrect, I will change the descriptor to version 2 major, and put the reading of the compatibility_id just after reading the BL flag.

great thank you !


EDIT:

I get a black screen with the latest version and DV isn't triggered.
Mediainfo now say DV Version 2.0 but is Dolby Vision Version 1.0 bluray compatible possible ?

[MrVideo]

Should be fixed starting with 2020-09-17--02-22-29 (https://bintray.com/justdan96/tsMuxer/tsMuxerGUI-Nightly/2020-09-17--02-22-29#files), please report if this keeps happening.
OK, Will do. Thanks.

[a5180007]

I get a black screen with the latest version and DV isn't triggered.
Mediainfo now say DV Version 2.0 but is Dolby Vision Version 1.0 bluray compatible possible ?

@imhh11, so your player would not be compatible with DV 2.0 ? Could you please try https://github.com/jcdr428/tsMuxer/suites/1234807529/artifacts/18624616, to see whether DV 1.0 still works with the swap compatibility_id / dependency_pid.

Edit: Mediainfo now shows 'Blu-ray compatible' instead of '8 compatible'.

[imhh11]

thanks this version looks promising. I'll be home in a couple of hours to try it...

Maybe @cogira will try before me.

[cogira]

@imhh11, so your player would not be compatible with DV 2.0 ? Could you please try https://github.com/jcdr428/tsMuxer/suites/1234807529/artifacts/18624616, to see whether DV 1.0 still works with the swap compatibility_id / dependency_pid.

Edit: Mediainfo now shows 'Blu-ray compatible' instead of '8 compatible'.

The linkk is not valid

[a5180007]

The linkk is not valid

The link is valid, you simply need to register on Github. Alternative OneDrive link. (https://1drv.ms/u/s!AqRZp848Q4jUgbRk_yF6IAPsuZcdww?e=1Rzzej)

[cogira]

I download it from alternative link. will test and report.
Thank you

[cogira]

I made ts and m2ts versions.
Both have the same behaviour:
Black screen
the file does not start to play and the counter stays at zero.
The x700 player hangs and do not respond anymore to the commands. Had to pull out the power chord and then reconnect again to restablish the correct player operation.

[filler56789]

The link is valid, you simply need to register on Github.

Which nowadays is not a good idea, considering that GitHub was bought my µ$oft and µ$oft ruined GitHub,
I mean,

https://github.community/t/new-security-feature-device-verification/10216/5

and

https://github.community/t/disable-remove-email-device-verification-prompt-on-login-not-the-2fa/2333/2

[imhh11]

I made ts and m2ts versions.
Both have the same behaviour:
Black screen
the file does not start to play and the counter stays at zero.
The x700 player hangs and do not respond anymore to the commands. Had to pull out the power chord and then reconnect again to restablish the correct player operation.

same result. Damn, I really thought that version would fix the x700 bug. Back to w64-nightly-2020-09-19--02-23-22 I guess.

thank's anyway @a5180007

[a5180007]

same result. Damn, I really thought that version would fix the x700 bug. Back to w64-nightly-2020-09-19--02-23-22 I guess.

@cogira @imhh11 please try this alternative (https://1drv.ms/u/s!AqRZp848Q4jUgbRlz31ddXi1M9-VCQ?e=Ki7iJQ).
I've put the reserved nibble at the end. If it does not work and nobody can advise on the right DOVI descriptor syntax, I am out of ideas...


bl_present_flag 1
dv_bl_signal_compatibility_id 4
If (!bl_present_flag) {
dependency_pid 13
reserved 3
}
reserved 4

[cogira]

Tested as before. Unfortunately nothing has changed. Exactly the same problems.
Thank you for your efforts @a5180007

[imhh11]

yep, I confirm. Same behavior but the file is Dolby vision V2 ... is the same change but with DV V1 possible ?

[a5180007]

yep, I confirm. Same behavior but the file is Dolby vision V2 ... is the same change but with DV V1 possible ?

@imhh11 @cogira same but with V1 (https://1drv.ms/u/s!AqRZp848Q4jUgbRmAfndIPLFatLFHA?e=bEg0NJ).

[cogira]

Tested and same results. Thank you again.

[yannick92]

Hi,

In the git-e7133f9 version, I noticed in the remux a change in the management of SEIs compared to 2.6.12.

Could there be an impact on the correct functioning of the files obtained with this new method?
Viewing problem?
Compatibility on video players? etc ...

In my case, I mainly use a PS3 to watch my remux movies.
Thank you in advance for your clarifications

Yannick


On the 2.6.12

17495


Actually, this is normal ?

17496

[a5180007]

Tested and same results. Thank you again.
Ok. So I will revert to previous v1 Dovi descriptor as described in the Dobly spec 1.2. Until somebody can confirm the structure of the v2 Dovi descriptor or give a working profile 7 sample, Mediainfo will keep on showing "8 compatible"... :mad:

[imhh11]

this sample is probably useless because it's a single layer BL+EL+RPU but this TS file play properly and does not have any bug on the x700.
https://drive.google.com/file/d/1bU026TmdlcJiH6mraPy8FBinpBVZIxhd/view?usp=sharing

same scene in dual layer TS with the bug:
https://drive.google.com/file/d/1Cy6QFAZu8HBnl59ohFHElQosS2bVhAAm/view?usp=sharing

same scene in dual layer mp4 without the bug:
https://drive.google.com/file/d/1sMvvwnBix0ZBQistaddqrgdtoz8qVlG9/view?usp=sharing

[a5180007]

In the git-e7133f9 version, I noticed in the remux a change in the management of SEIs compared to 2.6.12.

Could there be an impact on the correct functioning of the files obtained with this new method?
Viewing problem?
Compatibility on video players? etc ...


Bonjour Yannick, 2.6.12 was buggy: it did not detect the situation where two different pps can have the same id, resulting in corrupted H264 muxed stream. With 2.6.15, when this situation is detected, tsMuxer stops adding the timing SEI to the H264 stream. Therefore the resulting stream is still missing the timing SEI (as was the original stream), but at least it is not corrupted.

So this is still work in progress, as ultimately tsMuxer should correct and add the timing SEI when two different pps or sps with the same id are detected.

[a5180007]

same scene in dual layer TS with the bug:
https://drive.google.com/file/d/1Cy6QFAZu8HBnl59ohFHElQosS2bVhAAm/view?usp=sharing


Thanks @imhh11, but it does not help. Dovi descriptor is:

descriptor_tag: 0xb0
descriptor_length: 7
dv_version_major: 1
dv_version_minor: 0
dv_profile: 7
dv_level: 6
rpu_present_flag: 1
el_present_flag: 1
bl_present_flag: 0
dependency_pid: 0x1011
reserved: 0b111
dv_bl_signal_compatibility_id: 6
reserved: 0b1111

Buggy despite being strictly as per Dolby document.
What I need is a non-buggy profile 7.

Could you please test this version (https://1drv.ms/u/s!AqRZp848Q4jUgbRnhVUh1BMq_uC91g?e=LSHdV6) . I've simply removed the dependency_pid part, instead of moving it to the end.

[yannick92]

Bonjour Yannick, 2.6.12 was buggy: it did not detect the situation where two different pps can have the same id, resulting in corrupted H264 muxed stream. With 2.6.15, when this situation is detected, tsMuxer stops adding the timing SEI to the H264 stream. Therefore the resulting stream is still missing the timing SEI (as was the original stream), but at least it is not corrupted.

So this is still work in progress, as ultimately tsMuxer should correct and add the timing SEI when two different pps or sps with the same id are detected.

Ok, thanks for the explanations, it's a little clearer for me ...

Nevertheless, I am asking myself several legitimate questions about the use of new versions of TsMuxer as a plugin in another software that I have been using constantly for a long time now ...: "PS3Muxer Copyright (C) 2011 Anton Burdinuk"

Can I allow myself to do a quick parenthesis on its operation with the TsMuxer plugin (currently 1.10.6) as well as my questions?

Concretely, I mainly use a PS3 to play my video files, but as you probably know, this one has a lot of compatibility restrictions (fat 32, ts and m2ts only, ac-3 only, Level H264 4.1 max. .)

So I use the excellent PS3Muxer for converting MKV to the PS3.
Very practical and of high quality, in its operation it uses different plugins.
It is an "All in One", so it goes all at once: demuxer (MKV Extract), re-encode the DTS audio in AC-3 ( ffmpeg), remux in m2ts (TsMuxer) and splitter in Fat 32.
However, there has not been an update since 2011, but it still works great!

So I come to my questions: it uses version 1.10.6 of TsMuxer, is it also bugged on SEI like version 2.6.12?
I also noticed that there is no longer the line "H264 bitstream changed: insert nal unit delimiters" in the last versions of TsMuxer, is this normal and what are the consequences?

For all practical purposes, here is a functioning log of PS3Muxer.

Thanks to the whole team

Yannick

17497

[imhh11]

Could you please test this version (https://1drv.ms/u/s!AqRZp848Q4jUgbRnhVUh1BMq_uC91g?e=LSHdV6) . I've simply removed the dependency_pid part, instead of moving it to the end.

same black screen issue :(

[a5180007]

same black screen issue :(

Ok, I give up :)
The latest nightly should be back as before, with the Mediainfo "8 compatible" and the x700 pixellisation issue when the player is stopped.

[imhh11]

all good, it's not a big issue. :)
I watched 50&+ TS DV movies and they all work like a charm while with the mp4 container, some won't play or will freeze. thank's again for your work!



EDIT:

I dont know if this could help but when you play/stop this LG file, it fixes the bug where normally, you had to reboot the player to fix it. I tried many other videos(netflix/amazon/bluray/sdr file/hdr file) and none was able to do that.
So since the LG file also have an EL(but is single layer), it looks like x700 get stuck in a faulty mode when you play a dual layer TS but then playing back the lg file can somehow reset it.
lg demo
https://drive.google.com/file/d/1ZRwhD-PeD6Wptwcxtc8KYMwP1R32vcxg/view?usp=sharing

I hope you understand what I'm saying, my english is not so good. Credit goes to @cogira for finding this workaround



EDIT2: also, i just noticed that when you remux that file using the latest nightly, the HEVC stream disappear from mediainfo.

[a5180007]

EDIT2: also, i just noticed that when you remux that file using the latest nightly, the HEVC stream disappear from mediainfo.

After analysis, this behavior is the same since 2.6.12. Another thing to look at...

[mczuzlak]

Hello folks. I'm using tsmuxer explicitly for remuxing my retail uhd-bd backups with dark grey subtitles ( subtitle edit export as blu-ray sup) I've created my self as I'm sensitive to the retails way too bright ones.
Most of the time I can play them just fine on my oppo-203 as iso or bd folder.
I've a slight problem now with The Fifth Element GBR release that came out just recently with dolby vision. ( I can provide mediainfo export or something if needed )
I do everything as usual import the playlist of the main title add my sup file and hit muxing. The resulting output freezes at a certain frame near the beginning. It occurs right after the part where you can see the studiocanal logo.
It's strange as even though it's the main title I see even on the retails bd backup that after this scene my AVR shows a spilt second change in the codec as it would start a new title. Thats the part where tsmuxer seems to have a problem.

I hope I could describe it well. Is this maybe a known bug with other releases as well ? Any older nightlies I should try ?

Thanks

EDIT : Remuxing the tsmuxer output ( the one that freezes ) with CloneBD resolves the problem. No more freeze after that.
I wish tsmuxer could do the same.

[Emulgator]

That would look like changing parameters mid-stream.
Well possible for broadcast, never thought that would be Blu-ray legal. A new kind of copy protection ?
IIRC something regarding mid-stream audio codec or channel count changes had been reported from satellite broadcasts...
Modern chipsets may obey that. If that can be handled by vanilla tsMuxeR as remux ? Doubt that.
Maybe you will have to demux before and append these streams in tsMuxeR.

I would suggest to try DGDemux (now with preview), you will comfortably see which playlist it is.
Lets see if it handles such demux already...

[MrVideo]

Well possible for broadcast, never thought that would be Blu-ray legal. A new kind of copy protection?
AFAIK, U.S. OTA broadcasters are not allowed to change from AC3-5.1 to AC3-2.0, and vice versa.
IIRC something regarding mid-stream audio codec or channel count changes had been reported from satellite broadcasts...
There are several C-Band services that change from AC3-5.1 to AC3-2.0 and back. Even the main Ku-Band PBS network feed switches back and forth.

[MrVideo]

Here is a minor bug that has been there for ages....

In the track list, if you select a track and move it up, or down, you'll notice that its position in the metafile list does not change. It will only change if you select a different track. The metafile list should change as soon as you move, up or down, a selected track. Many moons ago I did a mux and noticed afterward that the order I wanted was not the order in the output. It was then I discovered that moving a track doesn't actually move the track. It would be nice if moving a track actually moved the track in the metafile list.

[a5180007]

The resulting output freezes at a certain frame near the beginning. It occurs right after the part where you can see the studiocanal logo.

EDIT : Remuxing the tsmuxer output ( the one that freezes ) with CloneBD resolves the problem. No more freeze after that.
I wish tsmuxer could do the same.

@mczuzlak can you please post Mediainfo for the studiocanal intro and for the main movie.

[SeeMoreDigital]

...I've a slight problem now with The Fifth Element GBR release that came out just recently with dolby vision. ( I can provide mediainfo export or something if needed )
I do everything as usual import the playlist of the main title add my sup file and hit muxing. The resulting output freezes at a certain frame near the beginning. It occurs right after the part where you can see the studiocanal logo. @mczuzlak can you please post Mediainfo for the studiocanal intro and for the main movie.How odd...

I re-muxed the StudioCanal version of The Fifth Element using git-c139668 and it plays perfectly using my OPPO UDP-203... Here's the MediaInfo file report of the newly created '00000.m2ts' stream: -

General
ID : 1 (0x1)
Complete name : \\SYNOLOGY_NAS\My HD Movies\UHD Movies\The Fifth Element [1997] 206mins (78.4GB)\AVCHD\BDMV\STREAM\00000.m2ts
Format : BDAV
Format/Info : Blu-ray Video
File size : 78.4 GiB
Duration : 2 h 6 min
Overall bit rate mode : Variable
Overall bit rate : 88.9 Mb/s
Maximum Overall bit rate : 35.5 Mb/s

Video #1
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 2 h 6 min
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2

Video #2
ID : 4117 (0x1015)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 2 h 6 min
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Writing library : x265 3.2+20-a4e060a44839:[Windows][GCC 6.3.0][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=5 / numa-pools=16,16 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=1920x1080 / interlace=0 / total-frames=3854 / level-idc=51 / high-tier=1 / uhd-bd=1 / ref=3 / no-allow-non-conformance / repeat-headers / annexb / aud / hrd / info / hash=0 / no-temporal-layers / no-open-gop / min-keyint=1 / keyint=24 / gop-lookahead=0 / bframes=3 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=24 / lookahead-slices=6 / scenecut=40 / hist-scenecut=0 / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=3 / selective-sao=4 / early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=cbr / bitrate=500 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / vbv-maxrate=500 / vbv-bufsize=550 / vbv-init=0.9 / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=9 / transfer=16 / colormatrix=9 / chromaloc=1 / chromaloc-top=2 / chromaloc-bottom=2 / display-window=0 / master-display=G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) / cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / hist-threshold=0.01 / no-opt-cu-delta-qp / no-aq-motion / hdr / hdr-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00 / no-scenecut-aware-qp
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2

Audio #1
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : AC-3 MLP FBA 16-ch
Format/Info : Audio Coding 3 + Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Muxing mode : Stream extension
Codec ID : 131
Duration : 2 h 6 min
Bit rate mode : Variable
Bit rate : 640 kb/s
Maximum bit rate : 6 342 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 578 MiB (1%)
Service kind : Complete Main
Number of dynamic objects : 11
Bed channel count : 1 channel
Bed channel configuration : LFE

Audio #2
ID : 4353 (0x1101)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 2 h 6 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 578 MiB (1%)
Service kind : Complete Main

Text
ID : 4768 (0x12A0)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144

[BloodyRipper]

Here is a minor bug that has been there for ages....

In the track list, if you select a track and move it up, or down, you'll notice that its position in the metafile list does not change. It will only change if you select a different track. The metafile list should change as soon as you move, up or down, a selected track. Many moons ago I did a mux and noticed afterward that the order I wanted was not the order in the output. It was then I discovered that moving a track doesn't actually move the track. It would be nice if moving a track actually moved the track in the metafile list.
Should be fixed starting with the 2020-10-07 build.

[MrVideo]

Should be fixed starting with the 2020-10-07 build.
Thanks.

[MrVideo]

Yep, that fixed it. But, I have now run into a new issue. I have a video that has a new style subtitle format. VLC and MPC-BE both display the text. But, tsmuxer declares that stream to be no good. Here is the mediainfo info:
ID : 3
Format : ASS
Codec ID : S_TEXT/ASS
Codec ID/Info : Advanced Sub Station Alpha
Duration : 50 min 3 s
Compression mode : Lossless
Writing library : Lavc58.78.102 ssa
Language : English
Default : No
Forced : No

[Emulgator]

You can not mux .ass into any .ts anyway, it is not supported.
If you want text-based, .srt is supported:
"S_TEXT/UTF8 SRT subtitle format. Encoding MUST be UTF-8/UTF-16/UTF-32"
You may use SubtitleEdit to convert into .srt before muxing.

tsMuxeR's additional parameters for PG and SRT tracks:

video-width The width of the video in pixels.
video-height The height of the video in pixels.
fps Video fps. It is recommended to define this parameter for more exact timing.
3d-plane Parameter defines number of the '3D offset track' which is placed inside MVC track.
Each particular subtitle can have individual 3D offset. This information will be stored inside 3D offset track.

Additional parameters for SRT tracks:

font-name Font name to render.
font-color Font color. Color can be defined in hexadecimal or decimal format.
If this value is 24 bit long (for instance 0xFF00FF) it will be interpreted as RGB components.
If this value is 32 bit long (for instance 0x80FF00FF) it will be interpreted as ARGB components.
font-size Font size to be rendered in pixels.
font-italic Italic text.
font-bold Bold text.
font-underline Underlined text.
font-strikeout Strikethrough text.
bottom-offset Distance from the lower edge while displaying text.
font-border Outline width in pixels.
fadein-time Time in ms for smooth subtitle appearance.
fadeout-time Time in ms for smooth subtitle disappearance.
line-spacing Interval between lines. Default value 1.0.

tsMuxeR supports additional tags inside SRT track. The syntax and parameters coincide with HTML: <b>, <i>, <u>, <strike>, <font>.
Default relative font size (used in these tags) in dpi is 3.

For example:
<b><font size=5 color="deepskyblue" name="Arial"><u>Test</u><font size= 4 color="#806040">colored</font>text</font></b>

[MrVideo]

You can not mux .ass into any .ts anyway, it is not supported.
That may be, but I never got that far since the ASS stream was rejected. It was part of a MKV file. When I have subtitle text to mux, I do so to M2TS files. I had no choice as to what the subtitle stream was.

Why doesn't tsmuxer support ASS subtitles? All it has to do is remux it.

[filler56789]

.........
Why doesn't tsmuxer support ASS subtitles? All it has to do is remux it.

Actually tsMuxeR converts the .SRT files to sequences of pictures...
theoretically, it could do the same to .SSA and .ASS files, but then someone would have to write a proper patch to the source-code :-/

[tebasuna51]

Why doesn't tsmuxer support ASS subtitles? All it has to do is remux it.

Because ASS is not supported in .ts or .m2ts containers.

tsMuxeR is not created to convert streams formats.
Only SRT subtitles are converted to PGS format to mux in ts/m2ts

You can't claim than tsMuxeR convert any kind of subtitles (there are many) to the PGS format required by ts/m2ts.

Also there are many video and audio codecs suported in mkv than can't be remuxed to ts/m2ts. And tsMuxeR can't recode them.

[SeeMoreDigital]

Yep... Currently there's only support for SRT 'text based' subtitles: -

https://i.ibb.co/w6YRZcf/Capture.png

[Ghitulescu]

Why doesn't tsmuxer support ASS subtitles? All it has to do is remux it.

tsMuxer is as its name says only a muxer - it takes "bricks" and builds a thing. As you can't simply use other things than bricks to make a wall, so tsMuxer can't use just anything to make a TS or M2TS files. If it's in the BD or TS specs, it will work.

The SRT to PGS is a bonus. You just discovered why employers are so reticent in giving bonuses to employees - they rapidly get the idea wrongly, as they are entitled to.

Most people around here prefer a solid tool (that is less preferably 0 bugs) with few functions, rather than a functions-rich tools equally full of errors.

[MrVideo]

Thanks for all the responses. Obviously I knew that ASS wasn't supported, because I found that out while trying to mux a file that had it.

Now I know why it will never be supported. I have no clue as to why ASS was used in the first place. I never heard of it before this.

[qyot27]

ASS is hardly a new format (https://en.wikipedia.org/wiki/SubStation_Alpha). It's been around for 18 years. Either open it up in Aegisub and export to SRT or use FFmpeg to do it.

[MrVideo]

Like I said, new to me. First time I've ever seen it used. It might have been in other MKV files, but since I didn't run those thru tsmuxer, I wouldn't have known. I have looked at a lot of MKV files with mediainfo, and never saw it that way either. Just my luck to not have seen it before.

Thanks for the program tip.

[r0lZ]

ASS (and SSA, its predecessor) is a text based subtitle format much versatile and powerful than SRT. You can obtain almost everything you want. So, unfortunately, if you need to convert it to SRT, you will probably lose the formatting, colors, fonts, position, size, orientation ext... It's why I would prefer to convert it directly to PGS, to keep it as close to the original as possible. I don't know if a program able to do that exists. SubtitleEdit can load SSA, but afaik it converts it internally to SRT immediately. It can also export to PGS, but probably only the subtitles already converted to SRT. Aegisub can only export to SRT, and certainly not to PGS, so IMO, it is better to try SubtitleEdit first. Or post in the Subtitles forum here at D9. Someone will probably be able to help you much than me.

Of course, if your subtitle stream is simply a succession of white lines always near the bottom of the screen, like a SRT stream, then converting it to SRT will not be a problem.

[LowDead]

EasySUP by deank..

It's old but works quite well and you find it here... (https://forum.doom9.org/showthread.php?t=149160)

//LD

[tebasuna51]

I can't make EasySup read .ass files, only .srt.

SubtitleEdit can export the .ass files to Blu-ray .sup

Support colours, position, etc.

Of course you must have installed the fonts used in the system.
The fonts used can be extracted from the .mkv and can be installed (only temporaly if you want) with FontViewer (http://www.ampsoft.net/utilities/FontViewer.php)

[filler56789]

I can't make EasySup read .ass files, only .srt.

I have never used .ASS files, only the goode and olde .SSA, and here both easySUP and avs2bdnxml load them correctly...

[LowDead]

I have used .ASS many times with easySUP. Make sure you have java and AviSynth installed properly.

//LD

[LowDead]

I also stumbled across this that looks promising. I have never tested it though.

sub2bd (https://forum.fanres.com/thread-2075.html)

//LD

[tebasuna51]

I have used .ASS many times with easySUP. Make sure you have java and AviSynth installed properly.
All is OK, work with .srt

The same with sub2bd, work with a .srt but not with my test .ass

Check it yourself:

[LowDead]

All is OK, work with .srt

The same with sub2bd, work with a .srt but not with my test .ass

Check it yourself:

Seems to be something wrong with that file. It can't be opened in Aegisub either. It opens in Subtitle Edit though.

//LD

[r0lZ]

SubtitleEdit can export the .ass files to Blu-ray .sup
Good to know ! Thanks. But I know that SubtitleEdit has at least some limitations when it loads the ASS streams. For example, with BD3D2MK3D, I have created a tool to convert SRT to ASS 3D. Of course, each subtitle is duplicated and the two instances are resized and displayed at a different location on screen. SubtitleEdit can read that 3D ASS files, but it refuse to show the two subtitles of the 3D view at the same time, and therefore it highlights the second one as illegal. I suppose it has also other limitations, as programs able to display all ASS streams without problems are very rare. The complexity of that format is enormous. For example, a subtitle can be animated to follow a character on screen ! Only a few players can display that correctly.

[tebasuna51]

@LowDead
Don't work with any sample from https://hhsprings.bitbucket.io/docs/programming/examples/ffmpeg/subtitle/ass.html

@r0lZ
You are right ASS is very complex. At least we can hope improvements because SubtitleEdit (https://github.com/SubtitleEdit/subtitleedit/releases) is updated at present, Aegisub is from 2014 and EasySup from 2010.

[qyot27]

https://github.com/wangqr/Aegisub/releases

[von Suppé]

It's why I would prefer to convert it directly to PGS, to keep it as close to the original as possible. I don't know if a program able to do that exists. SubtitleEdit can load SSA, but afaik it converts it internally to SRT immediately. It can also export to PGS, but probably only the subtitles already converted to SRT...
I'm quite surprised to hear that. I am importing ass subtitles into SE and export as BD-SUP for years without problems.
Maybe it's in your workflow?

[r0lZ]

I'm quite surprised to hear that. I am importing ass subtitles into SE and export as BD-SUP for years without problems.
Maybe it's in your workflow?
I did not know that this was possible. But anyway. currently. SubtitleEdit doesn't support everything possible with the ASS format. It's probably why I have assumed that it can only keep the strings, timings, colors and style (bold, italic, underline), in other words, everything supported by SRT. As far as I know, it doesn't support at least some of the other features, such as the font, scaling, animation, etc..., and especially multiple subtitles displayed at the same time (and for that last point, I am absolutely sure). See my reply here (https://forum.doom9.org/showthread.php?p=1926064#post1926064).

[Emulgator]

https://github.com/wangqr/Aegisub/releases

Thanks, qyot27, for the pointer !

[von Suppé]

As far as I know, it doesn't support at least some of the other features, such as the font, scaling, animation, etc..., and especially multiple subtitles displayed at the same time...
See my reply here (https://forum.doom9.org/showthread.php?p=1926064#post1926064).
Ah okay. I never worked with animation, and - as you know - not with the type of 3D subtitles that you are constructing in your tool. I'm sure there's a lot more to Aegisub and ass subs than I usually require.
I can confirm however that during export SE does honour the font's sort, size, colours & offset).

[Littleman]

Hey there, I've just purchased a Sony XH90 (X900H) TV and the Dolby Vision learning curve is...steep, to put it mildly. After a week of research, I now understand that I can only play single layer DV files & that profiles 5 & 8 work fine on my TV (tested with 4K60fps samples that look stunning).

What I'm now trying to do is to turn a DV dual layer movie into a SL DV one (profile 5/8). I have the 2 hevc files (movie + dv "video" track + ac3 audio) and the necessary tools (nightly tsmuxer + mp4muxer) but I'm not even sure this is even possible after searching this huge post & makemkv forum... no one mentions doing that / there's no guide pointing in the right direction.
So...simple question: is this hopeless or am I missing something? Cheers! And thanks for developing great tools like that.

[SeeMoreDigital]

Hey there, I've just purchased a Sony XH90 (X900H) TV and the Dolby Vision learning curve is...steep, to put it mildly. After a week of research, I now understand that I can only play single layer DV files & that profiles 5 & 8 work fine on my TV (tested with 4K60fps samples that look stunning).Have you tried playing dual-layered Dolby Vision files muxed within the .mp4 container (along with either AAC or AC3 audio). Such files play okay on my 2016 LG ;)

For more info, see here: https://forum.doom9.org/showthread.php?p=1868184#post1868184

[Littleman]

Have you tried playing dual-layered Dolby Vision files muxed within the .mp4 container (along with either AAC or AC3 audio). Such files play okay on my 2016 LG ;)

For more info, see here: https://forum.doom9.org/showthread.php?p=1868184#post1868184
yes they don't play on Sony Tvs, only LGs. Still looking into this (DvdFab apparently generates decent single layer files from uhd discs but... it's quite expensive).

[SeeMoreDigital]

yes they don't play on Sony Tvs, only LGs. Still looking into this (DvdFab apparently generates decent single layer files from uhd discs but... it's quite expensive).Okay, try the following: -

* Use MakeMKV v1.15.3 to back-up your 'dual-layer' 4K UHD Dolby Vision disc's into 'single-layer'.mkv muxes.

* Use one of the newer 'open-source' TSmuxer GUI builds to re-mux your 'single-layer' .mkv mux into 'single-layer' .ts contained muxes.

I can confirm that such .ts muxes also play perfectly on my humble 2016 LG television in Dolby Vision.


Cheers

[imhh11]

MakeMKV DV remux are still dual-layer files. The layers are just merged in one track (BL+EL+RPU).
If you want a single-layer file (BL+RPU) you can use @yusesope tool MUX_AND_CONVERT_TO_PROFILE_81.bat: https://mega.nz/file/mdU00TZR#bCiuGx6-7QaM2IeaIjNwdkmRWVA4hLti5rjLOOKESeE

https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602&start=2970#p96282

[Littleman]

MakeMKV DV remux are still dual-layer files. The layers are just merged in one track (BL+EL+RPU).
If you want a single-layer file (BL+RPU) you can use @yusesope tool MUX_AND_CONVERT_TO_PROFILE_81.bat: https://mega.nz/file/mdU00TZR#bCiuGx6-7QaM2IeaIjNwdkmRWVA4hLti5rjLOOKESeE

https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602&start=2970#p96282

"Great success", to quote Borat. This is exactly what I was looking for. First experimentation looks promising: I've produced a .ts file that triggers dolby vision in Plex on the tv (but plain HDR in Sony's own media player, I'll look into it).
Thanks for pointing me in the right direction!

Edit: I believe my ts file plays regular hdr10. I've remuxed using mp4muxer and I have a much better visual quality in dv, triggered in all players of the tv. The ts file reports a dv profile of 8.07, the mp4 one is 8.06.
I'm very happy with the mp4 mux ����

[SeeMoreDigital]

MakeMKV DV remux are still dual-layer files. The layers are just merged in one track (BL+EL+RPU).
Support for Dolby Vision playback across devices is so bonkers!

Personally, I would have thought that my old 2016 LG television would be miles behind what's currently supported. But it plays most variants of Dolby Vision (up-to 30fps).

[SeeMoreDigital]

MakeMKV DV remux are still dual-layer files. The layers are just merged in one track (BL+EL+RPU).
If you want a single-layer file (BL+RPU) you can use @yusesope tool MUX_AND_CONVERT_TO_PROFILE_81.bat: Using the 'Black Panther' movie as a source, I've just used that software to create an Dolby Vision BL+RPU .hevc back-up. And after muxing the elementary .hevc stream into the .ts container, I can confirm that my OPPO-UDP-203 plays the file perfectly. But my 2016 LG televisions media player app gets caught in a loop...

[imhh11]

yeah @yusesope is a very smart person. All the files created by his tool play flawlessly on my Sony x700 without the famous dual-track dual-layer TS bug.

-ST FEL or MEL (BL+EL+RPU)
-ST FEL to MEL (BL+EL+RPU)
-DT FEL or MEL to single-layer (BL+RPU)

[MrVideo]

I don't if the following is a problem, or not. I took a MKV file and made into a Blu-ray ISO file and then burned it. When I played it back, it didn't start at the beginning of the movie. It started at the first chapter mark, which wasn't at time zero. Why? No matter how many chapter marks there are, even if it is zero, shouldn't playback always start at time 0? I made sure there was a chapter mark for time 0 and not knowing if it was an issue, or not, I checked BD-ROM V3. That worked.

[SeeMoreDigital]

...I took a MKV file and made into a Blu-ray ISO file and then burned it. When I played it back, it didn't start at the beginning of the movie. It started at the first chapter mark, which wasn't at time zero. Why?
How are you playing the disc?

[a5180007]

I don't if the following is a problem, or not. I took a MKV file and made into a Blu-ray ISO file and then burned it. When I played it back, it didn't start at the beginning of the movie.

@MrVideo I can have a look at this bug if you provide me in PM a link to the mkv.

[MrVideo]

How are you playing the disc?
On my Sony BD X800M2 player.

[MrVideo]

@MrVideo I can have a look at this bug if you provide me in PM a link to the mkv.
It is 24GB. Looking at it now won't do much good, since it is now working.

It used to be that VideoReDo added a chapter marker at time 0 to every MKV file it assembled. But, with VideoReDoPro6, it doesn't seem to. No idea when that started. So, when playback didn't start at time zero, I looked at the MKV file in VRDPro6 and when there wasn't a chapter mark at time 0, I added one and created a new file. When I ran that thru tsmuxer, and I set the BD-ROM V3 option (no idea what that is supposed to imply), I saw that there was a chapter mark listed for time 0 in tsmuxer. Playback of that ISO file started at time 0. Interesting thing is that when I read that MKV file back into VRDPro6, there is no chapter mark shown at time 0.

If it is a BD spec that there be a chapter mark at time 0, then tsmuxer should look for one and automatically add it to the chapter list. That said, tsmuxer has an option for no chapter marks. So, where is the BD player supposed to start playing the disc?

If the MKV file is supposed to have a chapter mark at time 0 in order for correct BD playback, I'll have to submit a bug to the VRD team to get it fixed.

[r0lZ]

... when there wasn't a chapter mark at time 0, I added one and created a new file.
I just want to let you know that you can easily read the chapters from the MKV within the mkvtoolnix GUI, add the missing chapter, and save the new chapter list to the original MKV, without having to remux it entirely.

[a5180007]

If the MKV file is supposed to have a chapter mark at time 0 in order for correct BD playback, I'll have to submit a bug to the VRD team to get it fixed.

Blu-ray specs:

"Chapter is a time based playing interval in a Movie Title. A Chapter is determined by a pair of consecutive Entry-marks in a PlayList which corresponds to a Movie Title. If there is no Entrymark at the end of a PlayList, an interval between a last Entrymark and end point of a PlayList composes the last Chapter of the Movie Title."

"Entry-mark shall be put at the beginning of a PlayList – i.e. put an Entrymark at the “IN_time” of the first PlayItem of the PlayList."

[MrVideo]

I just want to let you know that you can easily read the chapters from the MKV within the mkvtoolnix GUI, add the missing chapter, and save the new chapter list to the original MKV, without having to remux it entirely.
Thanks.

[MrVideo]

Win7 - 64bit
Major failure with Nov 5 nightly build. The failure started before this build.

The issue: txmuxer.exe crashes when attempting to read in an HEVC stream file: 720p - 59.94fps - 4:2:2
Problem Event Name: APPCRASH
Application Name: tsmuxer.exe
Application Version: 0.0.0.0
Application Timestamp: 5fa352c4
Fault Module Name: msvcrt.dll
Fault Module Version: 7.0.7601.17744
Fault Module Timestamp: 4eeb033f
Exception Code: c0000005
Exception Offset: 0000000000001444
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: f4f4
Additional Information 2: f4f431a9497e574fdd3de91ca2750e84
Additional Information 3: 94db
Additional Information 4: 94db2c26458f17ebd8741f5458769f7a

Update: HEVC @4:2:0 is just fine.

[a5180007]

The issue: txmuxer.exe crashes when attempting to read in an HEVC stream file: 720p - 59.94fps - 4:2:2

@MrVideo please PM me a link for the 4:2:2 HEVC stream file (a 20-50 MB file should be enough to debug).

[SeeMoreDigital]

The issue: txmuxer.exe crashes when attempting to read in an HEVC stream file: 720p - 59.94fps - 4:2:2
Out of interest... How come you're using 4:2:2 HEVC encoded video streams?

[MrVideo]

Out of interest... How come you're using 4:2:2 HEVC encoded video streams?
The ABC network feed is HEVC @4:2:2.

IMHO, that is stupid, since the ultimate result is MPEG-2 @4:2:0, highly bitstarved.

[antioch]

Hello! I've got a file I'd like to demux the first audio track from but I can't seem to figure out how to do this from the command line. The docs are confusing to me, and I apologize for not understanding, but how can I accomplish this from the cli quick and easily?

Thank you!

[Emulgator]

Throw your desired muxed file at tsMuxeR GUI.
Choose Demux. Choose Output folder.
If you see unneeded video/audio/subtitle tracks: untick these.
Or leave all in and decide later.
Save meta file. Start demuxing.
If you dislike the GUI: Feed the just saved .meta file to the CLI.
Just a quick BD 3D test for you (throwing a .mpls at tsMuxeR GUI)
MUXOPT --no-pcr-on-video-pid --new-audio-pes --hdmv-descriptors --demux --vbr --vbv-len=500 --start-time=524280
V_MPEG4/ISO/MVC, "J:\6_DISC\BD_MEN_IN_BLACK_3_3D\BDMV\PLAYLIST\00800.mpls", insertSEI, contSPS, track=4114
V_MPEG4/ISO/AVC, "J:\6_DISC\BD_MEN_IN_BLACK_3_3D\BDMV\PLAYLIST\00800.mpls", insertSEI, contSPS, track=4113
A_DTS, "J:\6_DISC\BD_MEN_IN_BLACK_3_3D\BDMV\PLAYLIST\00800.mpls", track=4352, lang=eng
A_DTS, "J:\6_DISC\BD_MEN_IN_BLACK_3_3D\BDMV\PLAYLIST\00800.mpls", track=4353, lang=deu
A_AC3, "J:\6_DISC\BD_MEN_IN_BLACK_3_3D\BDMV\PLAYLIST\00800.mpls", track=4354, lang=tur
S_HDMV/PGS, "J:\6_DISC\BD_MEN_IN_BLACK_3_3D\BDMV\PLAYLIST\00800.mpls", fps=23.976, track=4608, lang=eng
S_HDMV/PGS, "J:\6_DISC\BD_MEN_IN_BLACK_3_3D\BDMV\PLAYLIST\00800.mpls", fps=23.976, track=4609, lang=deu
S_HDMV/PGS, "J:\6_DISC\BD_MEN_IN_BLACK_3_3D\BDMV\PLAYLIST\00800.mpls", fps=23.976, track=4610, lang=tur


Your command line Demuxmyfile.bat:
(path to\)tsMuxeR.exe <(path to\)meta file> <(path to\)output file or folder>

BTW, whatever a desired track might be I use to decide after demuxing all assets.

BD Audio demuxing is not as trivial as it seems if your desired "first" track is one of the prime beef kind.
tsMuxeR might not give you what you expect.
Expect audio gaps, overlaps, clicks...It is mainly for muxing.
tsMuxeR version git-32db2aa. github.com/justdan96/tsMuxer
Decoding H264 stream (track 1): H.264/MVC Views: 2 Profile: High@4.1 Resolution: 1920:1080p Frame rate: 23.976
MVC muxing fps is not set. Get fps from stream. Value: 23.976
Decoding H264 stream (track 2): Profile: High@4.1 Resolution: 1920:1080p Frame rate: 23.976
H.264 muxing fps is not set. Get fps from stream. Value: 23.976
Decoding DTS-HD stream (track 3): Bitrate: 1536Kbps core + MLP data.Sample Rate: 48KHz Channels: 5.1 (DTS Master Audio)
Decoding DTS-HD stream (track 4): Bitrate: 1536Kbps core + MLP data.Sample Rate: 48KHz Channels: 5.1 (DTS Master Audio)
Decoding AC3 stream (track 5): Bitrate: 640Kbps Sample Rate: 48KHz Channels: 5.1
Decoding PGS stream (track 7): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 8): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 6): Resolution: 1920:1080 Frame rate: 23.976
DTS-HD stream (track 3): overlapped frame detected at position 00:43:05,173. Remove frame.
DTS-HD stream (track 4): overlapped frame detected at position 00:43:05,173. Remove frame.
AC3 stream (track 5): overlapped frame detected at position 00:43:05,184. Remove frame.
DTS-HD stream (track 3): overlapped frame detected at position 00:54:32,778. Remove frame.
DTS-HD stream (track 4): overlapped frame detected at position 00:54:32,778. Remove frame.
AC3 stream (track 5): overlapped frame detected at position 00:54:32,800. Remove frame.
DTS-HD stream (track 3): overlapped frame detected at position 01:45:37,674. Remove frame.
DTS-HD stream (track 4): overlapped frame detected at position 01:45:37,674. Remove frame.
AC3 stream (track 5): overlapped frame detected at position 01:45:37,695. Remove frame.
AC3 stream (track 5): overlapped frame detected at position 01:45:48,032. Remove frame.
Processed 152233 video frames
Processed 152233 video frames
Flushing write buffer
Demux complete.
Demuxing time: 12 min 48 sec


I would suggest using DGDemux for that.
If you want to read that up at rationalqm.us:
A considerable amount of work was needed to get that right.

[antioch]

Throw your desired muxed file at tsMuxeR GUI.

I would suggest using DGDemux for that.

Thanks for the reply. As mentioned, I don't want to use a GUI, rather I want a scriptable tool I can use on the command line.

I looked at DGDemux and it only accepts mpls playlist files but I'm dealing with TS files that have 1 video stream, and 1 or 2 audio streams.

Indeed, I'm not familiar with the complexities of how audio is stored in TS container, but I was hoping there would be some CLI tool I can use analogous to this AviSynth function which would demux the first audio track.
LWLibavAudioSource("myVideo.ts", stream_index=-1, av_sync=true)
I'd like to trim the raw audio stream without a recode (using something like beSplit), but it seems to be that the above function decodes the audio which is why I was looking at some other tool to demux with. DGIndex seems to be a 1-click solution but I haven't found a command line interface for it. :(

[Emulgator]

DGDemuxGUI.exe is the GUI,
DGDemux.exe is the CLI.
If you bring .m2ts or .MTS without .mpls, you may consider eac3to.
CLI or GUI, you decide.

[antioch]

Sadly, eac3to doesn't give the same accurate results as tsMuxer or DGindex does.

Back to the topic, however. Is there some way to get an error log for tsMuxer? I've got a ts file that tsMuxer CLI and GUI fail to parse stream info for when first loading, and the error message is blank on the GUI (see attached png) or non-existent on the CLI.

PS D:\> .\tsMuxeR.exe "D:\Videos\myVideo.ts"
tsMuxeR version git-999c472. github.com/justdan96/tsMuxer
HEVC muxing fps is not set. Get fps from stream. Value: -0.537057
<exits>

The file works when run through DGindex and eac3to, however.

[Bgalakazam]

Hi, anybody got this to work with macOS Big Sur? tsmuxergui that is, app "opens" but no windows come up.

[von Suppé]

Wrong thread, please remove. My apologies.

[mczuzlak]

Are there any plans to support the Dolby Vision compatible mkv remuxes created by MakeMKV 1.5.3 ?
I wanted to use one as a source to mux it into a bluray iso but tsmuxer failed to load the mkv.
It would be nice to create backups with MakeMKV but still be able to convert back to UHD bluray structure while preserving the Dolby Vision metadata.

[SeeMoreDigital]

Are there any plans to support the Dolby Vision compatible mkv remuxes created by MakeMKV 1.5.3 ?Hmmm...

MakeMKV v1.5.3 now converts 2-layer Dolby Vision sources into 1-layer .mkv muxes (primarily for playback with nVidia Shield owners). And previous versions of MakeMKV discarded the secondary Dolby Vision FEL/MEL stream altogether.

If the MakeMKV developers created a build with an .mkv muxer that preserved both Dolby Vision layers (like Mosu's MKVToolNix can), it would then be possible for the open source builds of TSmuxer to easily create 4K UHD Blu-ray compliant muxes. (Dolby TrueHD audio streams without AC3 core excepted).

[imhh11]

Are there any plans to support the Dolby Vision compatible mkv remuxes created by MakeMKV 1.5.3 ?
I wanted to use one as a source to mux it into a bluray iso but tsmuxer failed to load the mkv.
It would be nice to create backups with MakeMKV but still be able to convert back to UHD bluray structure while preserving the Dolby Vision metadata.

I would love that as well but i doubt it can be done without demuxing first

Hmmm...

MakeMKV v1.5.3 now converts 2-layer Dolby Vision sources into 1-layer .mkv muxes (primarily for playback with nVidia Shield owners). And previous versions of MakeMKV discarded the secondary Dolby Vision FEL/MEL stream altogether.

If the MakeMKV developers created a build with an .mkv muxer that preserved both Dolby Vision layers (like Mosu's MKVToolNix can), it would then be possible for the open source builds of TSmuxer to easily create 4K UHD Blu-ray compliant muxes. (Dolby TrueHD audio streams without AC3 core excepted).


MakeMKV does not convert dual-layer to single-layer. it does preserve both DV layers
It creates a single track with two layers (BL+EL+RPU) which can be extracted (with yusesope tool (https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602&start=2970#p96282)) and then can be rebuilt with tsmuxer.

HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatible

[SeeMoreDigital]

I would love that as well but i doubt it can be done without demuxing first

MakeMKV does not convert dual-layer to single-layer. it does preserve both DV layers
It creates a single track with two layers (BL+EL+RPU) which can be extracted (with yusesope tool (https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602&start=2970#p96282)) and then can be rebuilt with tsmuxer.

HDR format : Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2086, HDR10 compatibleOkay yes, for the sake of clarity, MakeMKV merges the two separate (video) tracks found on Dolby Vision encoded 4K UHD Blu-ray discs, into a single video stream.

Now that we have software that can merge these tracks. It would be handy to have software that could separate them too!

[imhh11]

Now that we have software that can merge these tracks. It would be handy to have software that could separate them too!

we have one, I just gave you a link in my last post :)

https://i.extraimage.info/pix/2020/12/02/7b9a6ee254610b4df6ae970469695c75.png

[BloodyRipper]

Due to a rather embarrassing error, only the Mac build was created in today's (2020-12-05) nightlies.
Things should be back to normal in tomorrow's build, which will include a GUI translation to Chinese.

[von Suppé]

I would like to ask again:
For quite some time now, latest tsMuxer's 3D-BD (re-)mux to ISO or BD-folderstructure is not accepted by MakeMKV when importing, returning several errors.
Strange thing is, 3D muxing results from the older tsMuxer version 2.6.15 pass without problems.
Should this be looked into or am I maybe unaware of certain settings?

[cogira]

I would like to ask again:
For quite some time now, latest tsMuxer's 3D-BD (re-)mux to ISO or BD-folderstructure is not accepted by MakeMKV when importing, returning several errors.
Strange thing is, 3D muxing results from the older tsMuxer version 2.6.15 pass without problems.
Should this be looked into or am I maybe unaware of certain settings?

I have the same problem

[Emulgator]

A .meta file would help.

[von Suppé]

A .meta file would help.
Would you care to explain what a .meta file is? Do you mean the error log of MakeMKV perhaps?

Edit: Doh... got it. This is the meta from tsMuxer GUI git-bfeee07, remuxing a (mounted) movie-only ISO to movie-only ISO:


MUXOPT --no-pcr-on-video-pid --new-audio-pes --hdmv-descriptors --blu-ray --label="3D remux" --vbr --custom-chapters=00:00:00.000;00:03:55.401;00:06:51.994;00:11:47.706;00:14:29.451;00:18:37.653;00:22:15.834;00:26:51.151;00:30:31.287;00:36:41.364;00:40:48.320;00:44:49.936;00:48:47.797;00:51:16.447;00:54:22.217;00:57:32.657;01:00:31.168;01:04:41.543;01:06:49.045;01:11:01.881;01:16:53.692;01:21:18.037;01:24:30.354;01:28:08.533;01:30:54.157;01:34:14.564;01:37:20.542;01:39:20.203;01:42:40.319;01:46:50.069;01:49:02.661;01:52:18.314;01:57:29.876;02:00:23.841;02:05:41.323;02:07:31.268;02:13:38.466;02:16:21.881;02:19:39.995;02:23:19.799;02:30:12.334 --vbv-len=500 --start-time=524280
V_MPEG4/ISO/MVC, "M:\BDMV\PLAYLIST\00000.mpls", insertSEI, track=4114
V_MPEG4/ISO/AVC, "M:\BDMV\PLAYLIST\00000.mpls", insertSEI, track=4113
A_DTS, "M:\BDMV\PLAYLIST\00000.mpls", track=4352, lang=eng
S_HDMV/PGS, "M:\BDMV\PLAYLIST\00000.mpls", fps=23.976, 3d-plane=0, track=4608, lang=eng
S_HDMV/PGS, "M:\BDMV\PLAYLIST\00000.mpls", fps=23.976, 3d-plane=1, track=4609, lang=nld

[Emulgator]

Yes, I meant the .meta generated from tsMuxeR GUI.
track=4114 looks ok for a 3D .mvc dependent view.
V_MPEG4/ISO/MVC, "M:\BDMV\PLAYLIST\00000.mpls", insertSEI, track=4114
V_MPEG4/ISO/AVC, "M:\BDMV\PLAYLIST\00000.mpls", insertSEI, track=4113
I would swap lines, but that is me.
contSPS might be missing
Try
V_MPEG4/ISO/AVC, "M:\BDMV\PLAYLIST\00000.mpls", insertSEI, track=4113, contSPS
V_MPEG4/ISO/MVC, "M:\BDMV\PLAYLIST\00000.mpls", insertSEI, track=4114, contSPS

Forgot if this was needed for demuxing only:
subTrack Used for combined AVC/MVC tracks only.
TsMuxeR always demultiplexes such tracks into separate AVC and MVC streams.
subtrack=1 defines the AVC part, subtrack=2 defines the MVC part.

[von Suppé]

I would swap lines, but that is me.
Since day 1 I've been 3D muxing with the MVC stream as first in the list. I've read it to be the right way, ages ago in the old tsMuxer thread.
Of course I tried with H264 as first and it did not make a difference for the MakeMKV acceptance.

contSPS might be missing
This switch is activated by checking the "Continually insert SPS/PPS" box, right? I tried, but switching this off or on also did not make a difference.
Again, ages ago I read that this box should not be checked when muxing 3D.

-

Never really having thought about this .meta file, your post made me think it maybe was a good idea to compare them from both version 2.6.15 and the latest nightly.
I spotted a difference. With both loading the same ISO, here are the first lines of their meta:


Version 2.6.15

MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray --vbr --custom-chapters=00:00:00.000 --vbv-len=500

===

Latest nightly:

MUXOPT --no-pcr-on-video-pid --new-audio-pes --hdmv-descriptors --blu-ray --vbr --custom-chapters=00:00:00.000 --vbv-len=500

==

The latest nightly adds "--hdmv-descriptors". I don't know if this can make the difference?

I would love to try muxing without it, but I don't know how to delete that switch using the GUI.
I did notice, when I set the output to "TS muxing" or "M2TS muxing", at the General tab the option "Generate HDMV compatible TS" becomes available. Checking the box on/off results in "--new-audio-pes --hdmv-descriptors" being set or deleted. But for BD ISO or folderstructure it is greyed out.

Is there a way to view/export the whole command-line, working from the GUI?

[Emulgator]

Yes, you may use the GUI to create the meta.
Open that .meta in Editor and make your manual changes
Make a .bat, point to the .meta, start the .bat.
The CLI will start using that .meta.

CLI Examples:
All modes A (Track Detection) or B (Demuxing) or C (Muxing) need only a single line .bat file
+++++++ A: Track detection mode +++++++++++++++++++++++++++++++

(path to\)tsMuxeR.exe <(path to\)input file>
pause

If tsMuxeR is run with only that input file argument
tsMuxeR will assume track detection mode, parse given input file and display found information which can be used to build meta file.

Example

"C:\_PROG\tsMuxeR\tsMuxeR.exe" "T:\BD Ratatouille\RATATOUILLE_DEU\BDMV\STREAM\00002.m2ts"
pause

If you want to inspect more than one stream at once, just add another line into that batch file

"C:\_PROG\tsMuxeR\tsMuxeR.exe" "J:\4_ES\BD RB\x264 V13 RB 1996.264"
"C:\_PROG\tsMuxeR\tsMuxeR.exe" "J:\4_ES\BD RB\V13 RB 1996.ac3"
pause

Again: In track detection mode no .meta file is needed or generated
+++++++ B and C Demuxing/Muxing mode +++++++++++++++++++++++

Open Editor, make a batch file (plain text file with file extension .bat)
(path to\)tsMuxeR.exe <(path to\)meta file> <(path to\)output file or folder>

Arguments are separated by 1 space.
The <> are meant as delimiters for the full path.
(Full path delimited by "" is only needed for those arguments (.bat file, input files, output files) that reside in different folders than tsMuxeR.exe.)

If tsMuxeR is run with an additional path to a .meta file,
tsMuxeR parses that given .meta file and expects to start a demuxing or muxing process.
If output folder doesn't exist, tsMuxeR will generate one at given location.

I did notice, when I set the output to "TS muxing" or "M2TS muxing", at the General tab the option "Generate HDMV compatible TS" becomes available. Checking the box on/off results in "--new-audio-pes --hdmv-descriptors" being set or deleted. But for BD ISO or folderstructure it is greyed out.

"Generate HDMV compatible TS" is mandatory for Blu-ray, so it seems useful that it can not be checked off while opting for Blu-ray muxing.
The greyed-out tickbox shows the tick fixed to active, and this is what I would expect.

Ok, will have to make a 3D test mux soonish to see what MakeMKV finds.

[von Suppé]

Thanks for your help, Emulgator.
Hope your examples will steer me to be able and try different things with cli. Will report back.
Cheers

[Emulgator]

MIB3_3D ripped via Any (full .ssif):
MIB3_3D ripped via Make (.ssif.smap):
00800.mpls thrown on tsMuxeR GUI 2020-12-08 for Demux-Remux:
After 0,1% (some 35MB) tsMuxeR comes up with Error -1 "F".
Found BD folder structure, inside like ~35MB 0000.m2ts Main view + 3x Audio +3x Subs playable, ~8MB 00001.m2ts dependent view. mvc alone.
2.6.12 does that too, but can at least write the Error -1 "Fehlerhafter Parameter".
Individual streams demuxed following 00800.mpls by DGDemux46: The same.
No .ssif. If I specify .ssif in GUI trying to type extension while .m2ts radiobutton, radiobutton falls back to .mts.

Now having BD_Rebuilder 0.61.18 running a Main Movie on BD-R 25GB FRIM Re-encode.
Lets see what the BD_RB .meta says.

[von Suppé]

As a quick response to MIB3_3D, wasn't this one of those "problematic" discs in terms of demuxing?
To rule certain things out, maybe better to try with another title?

[EDIT] Well, finaly managed to get this working pfffff. Took half a bottle of single malt & almost an ambulance...
First off, hopelessly having lost track, can you please confirm what encodings must be used for creating the .bat and .meta file? UTF-8 or ANSI? And when I already opened a file in notepad, how can I tell what encoding is being used?

removing the "--hdmv-descriptors" from the .meta file did not make the difference I was hoping for.

[Emulgator]

Hrm. I had started this morning.
BD_RB finished ok.
Found the BD_RB .meta, had muxed all subs into 3dplane 1.
Should have been into 1,2,3 (says DGDemux)

MakeMKV finds faults, that confirms your findings.
MakeMKV v1.15.3 win(x64-release) gestartet
Debug-Aufzeichnung eingeschaltet. Aufzeichnung wird gespeichert als C:\Users\l/MakeMKV_log.txt
Lade aktuelle SDF in C:\Users\l/.MakeMKV ...
Öffne Dateien auf Festplatte in J:/8_DISC_REMUX/BD_MIB3_3D_Any_BD-RB/MEN_IN_BLACK_3
AACS-Verzeichnis nicht vorhanden. Es wird angenommen, dass die Disk unverschlüsselt ist
Die Quell-Datei '00000.clpi' ist defekt oder ungültig bei Offset #1100. Es wird versucht, dies zu umgehen
Die Quell-Datei '00000.clpi' ist defekt oder ungültig bei Offset #1101. Es wird versucht, dies zu umgehen
Die Quell-Datei '00000.clpi' ist defekt oder ungültig bei Offset #1102. Es wird versucht, dies zu umgehen
Titel #00001.mpls wurde übersprungen
Titel #00000.m2ts wurde übersprungen
Das Öffnen der Disk schlug fehl.

BDEdit 0,49: 1100,1101,1102 are the 3 audio streams.
No fault message.
MPC-HC plays the mux with audio and subs, 2D tested
3D untested for now, need to burn to BD-RE25 and use the chain Oppo 205 -> LG OLED55E6V

[von Suppé]

Here is what MakeMKV says about importing a mounted iso from latest tsMuxer:

MakeMKV v1.15.3 win(x64-release) gestartet
Debug-Aufzeichnung eingeschaltet. Aufzeichnung wird gespeichert als C:\Users\***/MakeMKV_log.txt
Direkter Zugriffsmodus wird verwendet
AACS-Verzeichnis nicht vorhanden. Es wird angenommen, dass die Disk unverschlüsselt ist
DEBUG: Code 0 at <)@bC=_v7LB*WJKP:121262302
DEBUG: Code 0 at j_2*gIk0SDRBlYdA[&(.:29397771
DEBUG: Code 0 at )|-Dt0UfP<I#NHOVBsLn:121262348
DEBUG: Code 0 at )|-Dt0UfP<I#NHOVBsLn:121262210
DEBUG: Code 0 at )|-Dt0UfP<I#NHOVBsLn:121261773
DEBUG: Code 0 at sB1Ak-Qr63XhpI9v@LaQ:213136769
DEBUG: Code 0 at [`wp1Bv4=]`if>k%a-:121262049
DEBUG: Code 0 at [`wp1Bv4=]`if>k%a-:121262256
Dekodierung der Audio- und Videodaten von Titel #0 ist fehlgeschlagen. Ungültiger Mux oder interner Fehler. Der Titel wurde übersprungen.
DEBUG: Code 0 at GHaY;DP.*KMTFuAQ:213131387
DEBUG: Code 0 at G]}%-0xK4D#J5U5:29401934
DEBUG: Code 0 at *0,;c\PL0:J=9lq%:213116437
Titel #00000.mpls wurde übersprungen
DEBUG: Code 0 at j_2*gIk0SDRBlYdA[&(.:29397771
DEBUG: Code 0 at )|-Dt0UfP<I#NHOVBsLn:121262348
DEBUG: Code 0 at )|-Dt0UfP<I#NHOVBsLn:121262210
DEBUG: Code 0 at )|-Dt0UfP<I#NHOVBsLn:121261773
DEBUG: Code 0 at sB1Ak-Qr63XhpI9v@LaQ:213136769
DEBUG: Code 0 at [`wp1Bv4=]`if>k%a-:121262049
DEBUG: Code 0 at [`wp1Bv4=]`if>k%a-:121262256
Dekodierung der Audio- und Videodaten von Titel #0 ist fehlgeschlagen. Ungültiger Mux oder interner Fehler. Der Titel wurde übersprungen.
DEBUG: Code 0 at GHaY;DP.*KMTFuAQ:213131387
DEBUG: Code 0 at G]}%-0xK4D#J5U5:29401934
DEBUG: Code 0 at *0,;c\PL0:J=9lq%:213116437
Titel #00000.m2ts wurde übersprungen
Das Öffnen der Disk schlug fehl

Mind, that the iso's seem ok and play on pc and via NFS on my mediaplayers.
I don't use the iso's for burning. But I do use them sometimes to create a 3D-MKV.

[mikahawkins1]

Private or not its good work. I will give you that.

[von Suppé]

I'm not sure I understand your post. If you mean the language in the code box, my apologies. I did this so it may be easier to read for Emulgator, who obviously uses german.

In english:

MakeMKV v1.15.3 win(x64-release) started
Debug logging enabled, log will be saved as C:\Users\***/MakeMKV_log.txt
Using direct disc access mode
AACS directory not present, assuming unencrypted disc
DEBUG: Code 0 at <)@bC=_v7LB*WJKP:121262302
DEBUG: Code 0 at j_2*gIk0SDRBlYdA[&(.:29397771
DEBUG: Code 0 at )|-Dt0UfP<I#NHOVBsLn:121262348
DEBUG: Code 0 at )|-Dt0UfP<I#NHOVBsLn:121262210
DEBUG: Code 0 at )|-Dt0UfP<I#NHOVBsLn:121261773
DEBUG: Code 0 at sB1Ak-Qr63XhpI9v@LaQ:213136769
DEBUG: Code 0 at [`wp1Bv4=]`if>k%a-:121262049
DEBUG: Code 0 at [`wp1Bv4=]`if>k%a-:121262256
Failed to decode audio/video data for title #0 - invalid mux or internal error, title skipped.
DEBUG: Code 0 at GHaY;DP.*KMTFuAQ:213131387
DEBUG: Code 0 at G]}%-0xK4D#J5U5:29401934
DEBUG: Code 0 at *0,;c\PL0:J=9lq%:213116437
Title #00000.mpls was skipped
DEBUG: Code 0 at j_2*gIk0SDRBlYdA[&(.:29397771
DEBUG: Code 0 at )|-Dt0UfP<I#NHOVBsLn:121262348
DEBUG: Code 0 at )|-Dt0UfP<I#NHOVBsLn:121262210
DEBUG: Code 0 at )|-Dt0UfP<I#NHOVBsLn:121261773
DEBUG: Code 0 at sB1Ak-Qr63XhpI9v@LaQ:213136769
DEBUG: Code 0 at [`wp1Bv4=]`if>k%a-:121262049
DEBUG: Code 0 at [`wp1Bv4=]`if>k%a-:121262256
Failed to decode audio/video data for title #0 - invalid mux or internal error, title skipped.
DEBUG: Code 0 at GHaY;DP.*KMTFuAQ:213131387
DEBUG: Code 0 at G]}%-0xK4D#J5U5:29401934
DEBUG: Code 0 at *0,;c\PL0:J=9lq%:213116437
Title #00000.m2ts was skipped
Failed to open disc

[Emulgator]

3D Folder Mux using BD_RB's built-in tsMuxer4k (w32-nightly-2020-09-25--02-25-44, 32db2aa) tested successfully, burned to BD-RE25.
tsMuxer hasn't muxed .ssif, just all streams .avc. + mvc + 3x Audio + 3x Subs into 00000.m2ts
Playback Chain BD-RE25 -> Oppo 205 -> LG OLED55E6V plays it as 3D, no complaints.
Well, that is Oppo which might play even non-standard mux.
For nitpicking standalones I will have to throw that at a Panasonic BDT-110 at the weekend.
And I haven't tested muxing into .iso.

[EDIT]
...First off, hopelessly having lost track, can you please confirm what encodings must be used for creating the .bat and .meta file? UTF-8 or ANSI? And when I already opened a file in notepad, how can I tell what encoding is being used?

I use notepad++, this shows character encoding and allows to move between different character encodings.

tsMuxeR can be run in one of three modes.
A: Track detection mode or B: Muxing mode or C: Demuxing mode.

Only Track detection mode (see below) needs no .meta file.
To control any demuxing/muxing on runtime you have to generate a .meta file, either by hand or using the tsMuxeR GUI
This is a plain text file in ANSI coding (from 2.6.16 Unicode is possible too) and MUST have extension .meta.

tsMuxeR GUI 1.10.6 will generate .meta files with LF linebreaks,
tsMuxeR GUI 2.6.12 will generate .meta files with LF+CR linebreaks,
To be safe while generating .meta manually I suggest to use LF+CR.

The tsMuxeR GUI generates .meta file before muxing.
The tsMuxeR GUI is only there to write such .meta file, unfortunately it can not read any .meta file.
(You may use that feature to test-run as follows:
Use the GUI, save the .meta file from the GUI, let it test-mux, re-edit that .meta file, then run the CLI on that .meta)
.bat encoding: I suggest ANSI, haven't tested Unicode.

[von Suppé]

Ok, sticking to ANSI seems to work all the time. Thanks for the Notepad++ suggestion.

[EDIT] Just minutes ago I learned there was a new MakeMKV version out. This one also returns errors on 3D ISO import. But, apparently MakeMKV now has found a way to "get around" the errors and I was taken to the next screen to make a 3D mkv.
Of course I will test this further, but it's an improvement nevertheless from the MakeMKV guys.

For those who are interested here's the log. I could only put it partially as it was too long.



The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset 2626056192, attempting to work around
DEBUG: Code 266257 at h*CYV;I&#^aU54?q0v+l:29395563
The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset 2626136064, attempting to work around
DEBUG: Code 266257 at h*CYV;I&#^aU54?q0v+l:29395563
The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset 2626222080, attempting to work around
DEBUG: Code 266257 at h*CYV;I&#^aU54?q0v+l:29395563
The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset 2626430976, attempting to work around
DEBUG: Code 266257 at h*CYV;I&#^aU54?q0v+l:29395563
The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset 2626516992, attempting to work around
DEBUG: Code 266257 at h*CYV;I&#^aU54?q0v+l:29395563
The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset 2626596864, attempting to work around
DEBUG: Code 266257 at h*CYV;I&#^aU54?q0v+l:29395563
The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset 2626682880, attempting to work around
DEBUG: Code 266257 at h*CYV;I&#^aU54?q0v+l:29395563
The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset 2626842624, attempting to work around
DEBUG: Code 266257 at h*CYV;I&#^aU54?q0v+l:29395563
The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset 2626928640, attempting to work around
DEBUG: Code 266257 at h*CYV;I&#^aU54?q0v+l:29395563
The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset 2627088384, attempting to work around
DEBUG: Code 266257 at h*CYV;I&#^aU54?q0v+l:29395563
The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset 2627254272, attempting to work around
DEBUG: Code 266257 at h*CYV;I&#^aU54?q0v+l:29395563
The source file '/BDMV/STREAM/00000.m2ts' is corrupt or invalid at offset 2627334144, attempting to work around
DEBUG: Code 266257 at... etc etc this goes on and on and on.....
last two lines are:
File 00000.mpls was added as title #0
Operation successfully completed

[glc650]

I've noticed on my Oppo UDP-203 that BDMV folders that are remuxed to ts or m2ts with tsmuxer playback fine initially but the very next movie (any file type, HDR or SDR, even the same ts/m2ts file that was just played) results in a pink/green/purple screen (the DV banner still flashes & audio is fine, just the video is a problem). Only way to fix this (besides rebooting the Oppo) is to play a movie from a BDMV folder (full rip or even one that tsmuxer has rexmuxed) which will result in the same scrambled screen but the very next movie will play correctly (until a ts/m2ts file generated by tsmuxer is played again).

[Emulgator]

Could be unrelated to tsmuxeR, I had the same sometimes:
After successful play of any pressed BD-ROM on returning to Player menu HDMI is negotiated new.
If user-set player preferences dictate negotiating maxed-out HDMI connection AND no content negotiates its own preferences
AND HDMI cable is not prime (mine wasn't until 3 months ago)
4k60p connection might fail,
but no fallback from Oppo players in such case (player won't notice anyway), instead garbled picture on screen
Setting player's user preference to 4k24p helped in such case, until I went for a prime HDMI cable.

[SeeMoreDigital]

@glc650,

After creating your 'Blu-ray Folder' muxes, are you remembering to place the 'BDMV and CERTIFICATE' folders within an (manually created) AVCHD folder prior to playback?

[glc650]

@glc650,

After creating your 'Blu-ray Folder' muxes, are you remembering to place the 'BDMV and CERTIFICATE' folders within an (manually created) AVCHD folder prior to playback?Yes I have to in order to even get the oppo to play them.

[glc650]

Could be unrelated to tsmuxeR, I had the same sometimes:
After successful play of any pressed BD-ROM on returning to Player menu HDMI is negotiated new.
If user-set player preferences dictate negotiating maxed-out HDMI connection AND no content negotiates its own preferences
AND HDMI cable is not prime (mine wasn't until 3 months ago)
4k60p connection might fail,
but no fallback from Oppo players in such case (player won't notice anyway), instead garbled picture on screen
Setting player's user preference to 4k24p helped in such case, until I went for a prime HDMI cable.If it was unrelated to tsmuxer I would think this would happen with other content but it only happens when the file is a ts/m2ts and was created by tsmuxer. None of my MKVs or BDMV folders do this.

[SeeMoreDigital]

Yes I have to in order to even get the oppo to play them.In that case...

I'm unable to replicate your issue with my OPPO UDP-203. And all my HDMI leads are Premium Certified ;)

[glc650]

In that case...

I'm unable to replicate your issue with my OPPO UDP-203. And all my HDMI leads are Premium Certified ;)I'm using the default txmuxer settings. Did you change any of them when remuxing from BDMV to m2ts?

[Emulgator]

You may still show your playback preferences from Oppo setup menu to rule out any HDMI switching to 4k60.

[glc650]

You may still show your playback preferences from Oppo setup menu to rule out any HDMI switching to 4k60.Output Resolution = Source Direct; Color Space and Depth = auto (but I also tried 4:2:0 and 4:2:2 and all 3 depths)

I'm using all Monoprice 8K Ultra High Speed 48Gbps cables @ 6 ft

[Emulgator]

That should work then for the HDMI side of things.

[SeeMoreDigital]

I'm using the default txmuxer settings. Did you change any of them when remuxing from BDMV to m2ts?Just so you know...

The most recent (Dolby Vision) 4K UHD disc I backed-up was last week using MakeMKV in backup mode and TSmuxer GUI git-999c472 in Blu-ray folder mode.

My OPPO's video output settings are as follows: -

HDR Settings: -
HDR: Auto
Target Luminance: 300 nits
HDR to SDR Mode: Mode 1
Dolby Vision Processing: TV-led
Output Resolution: Source Direct
Custom Resolution: UHD Auto
Color Space: Auto
Color Depth: Auto


Cheers

[imhh11]

I've noticed on my Oppo UDP-203 that BDMV folders that are remuxed to ts or m2ts with tsmuxer playback fine initially but the very next movie (any file type, HDR or SDR, even the same ts/m2ts file that was just played) results in a pink/green/purple screen (the DV banner still flashes & audio is fine, just the video is a problem). Only way to fix this (besides rebooting the Oppo) is to play a movie from a BDMV folder (full rip or even one that tsmuxer has rexmuxed) which will result in the same scrambled screen but the very next movie will play correctly (until a ts/m2ts file generated by tsmuxer is played again).

Sounds exactly like the same issue I'm having with the Sony x700 when I play ts/m2ts Dolby vision file created by tsMuxer.

This issue only caused by DV content right ? HDR10 and SDR file are ok? definitely a tsMuxer related problem. Unfortunately, @a5180007 tried a lot of things to fix the issue but nothing worked. :(

[glc650]

Sounds exactly like the same issue I'm having with the Sony x700 when I play ts/m2ts Dolby vision file created by tsMuxer.

This issue only caused by DV content right ? HDR10 and SDR file are ok? definitely a tsMuxer related problem. Unfortunately, @a5180007 tried a lot of things to fix the issue but nothing worked. :(I only use the oppo for DV so I haven't tested that but its possible.

[bairradino]

Hi.

I tried to get a Blu-ray iso from my UHD-HLG mp4 video file but when starting muxing I get "tsMuxer finished with error code -1073741819" error.
What am I doing wrong? Here the characteristics of my video file:

General
Complete name : E:\Blu-Ray\Casamento_UHD.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (isom/mp42)
File size : 16.2 GiB
Duration : 38 min 22 s
Overall bit rate mode : Variable
Overall bit rate : 60.4 Mb/s
Encoded date : UTC 2020-12-22 23:06:54
Tagged date : UTC 2020-12-22 23:06:54

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main@L5@High
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 38 min 22 s
Bit rate : 60.2 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Bits/(Pixel*Frame) : 0.290
Stream size : 16.1 GiB (100%)
Language : English
Encoded date : UTC 2020-12-22 23:07:04
Tagged date : UTC 2020-12-22 23:07:04
Codec configuration box : hvcC

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 38 min 22 s
Bit rate mode : Variable
Bit rate : 192 kb/s
Maximum bit rate : 521 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 52.0 MiB (0%)
Language : English
Encoded date : UTC 2020-12-22 23:07:04
Tagged date : UTC 2020-12-22 23:07:04

[Emulgator]

Might be unrelated, but for UHD Blu-ray 3840x2160x25fps only 10bit HEVC is legal.
And AAC LC also is no blu-ray-legal audio stream.

[KingLir]

Hi all, I hope someone here can help me with an issue I encounter.

When I input tsMuxer an mp4 file with DV Profile 5 like the following:
Dolby Vision, Version 1.0, dvhe.05.06, BL+EL+RPU / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible

The .ts file muxed changed to Profile 7:
Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible

Shouldn't at least be an option in tsMuxer to keep the original profile 5 ? As I assume it's not best to make this the default behavior.

[imhh11]

Hi all, I hope someone here can help me with an issue I encounter.

When I input tsMuxer an mp4 file with DV Profile 5 like the following:
Dolby Vision, Version 1.0, dvhe.05.06, BL+EL+RPU / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible

The .ts file muxed changed to Profile 7:
Dolby Vision, Version 1.0, dvhe.07.06, BL+EL+RPU, Blu-ray compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile B compatible

Shouldn't at least be an option in tsMuxer to keep the original profile 5 ? As I assume it's not best to make this the default behavior.

your original mp4 is in the wrong DV profile. Profile 5 is for single layer DV (for streaming services)and not for UHD-BD rip.
P7 is the correct profile for a file containing an HDR10 BL with an EL+RPU.

If what you want is a single layer file BL+RPU only, then the correct profile you are looking for is p8. you can find tools to convert your dual layer file here:
https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602&start=2970#p96282

[KingLir]

your original mp4 is in the wrong DV profile. Profile 5 is for single layer DV (for streaming services)and not for UHD-BD rip.
P7 is the correct profile for a file containing an HDR10 BL with an EL+RPU.

If what you want is a single layer file BL+RPU only, then the correct profile you are looking for is p8. you can find tools to convert your dual layer file here:
https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602&start=2970#p96282

Let me examine.

I got this mp4 file since I am trying to convert UHD-BD to DV Profile 5 (for playback on Apple TV 4K which only supports Profile 5).
And indeed the new single layer profile 5 mp4 file works with DV on Apple TV 4K and I can't detect issues with the video.
But now I am trying to mux in TrueHD Atmos track, which I reached tsMuxer for.

Can you point me on how to achieve this ?

[imhh11]

There's an edited version of tsMuxer out there that will keep your file in profile 5 but keep in mind that its not in the DV specs and it may not produce an accurate image because your TV & AppleTV are expecting a different colorspace for that type of DV.
you can ask if someone still has that edited version on the makemkv link I posted in my previous reply.

On the AppleTV, all you will get out of TrueHD is LPCM right? no bitstreaming.
if you can't find the edited tsMuxer version., you can demux the atmos track to lpcm and remux in a profile 5 MP4. this should work as well.
https://mrmc.tv/forum/viewtopic.php?f=15&t=4171&sid=66e9881b0a0b18a334658ac1c2f33776&start=310

[a5180007]

Hi.

I tried to get a Blu-ray iso from my UHD-HLG mp4 video file but when starting muxing I get "tsMuxer finished with error code -1073741819" error.
What am I doing wrong?

@bairradino please confirm that the issue has been fixed with latest bintray nightly.
Happy new year to you all.