tsMuxer Open Source

[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.