tsMuxeR 2.17.0

Dolby Vision discs now survive a round trip through Matroska, TrueHD keeps its lossless stream, and HEVC output matches what pressed Blu-rays carry.

Changes

• A dual layer Dolby Vision disc is now carried in one Matroska track. Such a disc puts the picture on two video streams, a base layer plus a quarter-resolution enhancement layer holding the Dolby Vision data, and Matroska needs both in a single track. Until now a disc source produced two tracks and no player engaged Dolby Vision.
• And back out again. A merged track splits into its two layers to author a disc, through the existing subTrack=. A disc taken to Matroska and back comes out byte for byte identical over a full feature, so nothing is given up by storing a film this way.
• Matroska no longer reduces a TrueHD track to its AC-3 core. The result was a 448 kbps track labelled AC-3, with no warning and a successful mux, while the same source muxed to m2ts was intact. The lossless stream is carried now, with the core kept beside it as its own AC-3 track, which is the layout a disc remux normally has. merge-ac3-track= braids the two back together when a disc is authored from that file, and drop-ac3-core leaves it out.
• A DTS:X track using the IMAX variant of the marker is now named. It describes the audio encoding and nothing else: it does not say the title is an IMAX Enhanced presentation.
• The level of an HEVC stream can be changed without re-encoding, through the same level= track option the H.264 path has always had. The level is a single byte in a header, so a 4K track no longer has to be re-encoded to alter one number.
• Access unit delimiters are written for HEVC when a source has none, which the H.264 path has done for years. They are optional in HEVC itself, but every pressed disc carries exactly one per picture.
• The HDR mastering display and content light level are repeated at every random access point when authoring a Blu-ray. Material that states them once, at the head of the stream, left a player with no HDR10 metadata at all after a seek; Dolby Vision hides the problem, because its own metadata travels with every picture. The values written are the stream's own.
• The layer-break guard beside the normal Blu-ray output was placed at the wrong sector. That list had no capacities behind it and the break was never passed to the muxer, so every disc fell back to half a 50 GB disc. Both parts of the interface share one disc table now, and the group shows where the guard will land before the mux runs.
• The pre-filled Free Sectors for BD-R XL was the defect-managed capacity, which put the calculated break a full GiB from the real one, far outside any guard band. Entries now carry the full capacity and show their own sector count so it can be matched against the burner at a glance. Reported by @DreckSoft.
• A 100 GB disc can be used across its first two layers only. There is no 66 GB BD-R and many players cope with two layers better than three, so the one break it needs lands on the disc's real first layer boundary and the third layer is left unwritten. It is still BD-R XL media, so the player-compatibility warning still appears. Requested by @DreckSoft.
• "Also fill before the break" now works on an ordinary mux and not only on --bdmv-to-iso, for media that are weak just before the layer transition as well as after it.

Downloads

File	Platform
tsMuxeR-2.17.0-windows-x64.zip	Windows 64-bit, Windows 7 SP1 and newer
tsMuxeR-2.17.0-windows-x86.zip	Windows 32-bit, Windows 7 SP1 and newer
tsMuxeR-2.17.0-macos-arm64.zip	macOS, Apple Silicon
tsMuxeR-2.17.0-macos-x86_64.zip	macOS, Intel
tsMuxeR-2.17.0-linux-x64.zip	Linux x86_64 (the GUI needs Qt 6 installed on the system)

Each Windows zip is a self-contained folder: unzip and run tsMuxerGUI.exe or tsMuxeR.exe.