Software » MKV to MP4/BD » tsMuxeR 2.18.4 / 2.7.0 Original / 2.7.2

tsMuxeR 2.18.4
A 3D disc can now be wrapped into an ISO without writing its video twice.

New: --3d-single-copy
A 3D Blu-ray stores its video ONCE and gives it three names. The base view and the dependent view are cut into chunks and written alternately, and that single run of sectors is what the .ssif names. The same sectors are addressed again as two .m2ts, one naming only the base chunks and one only the dependent chunks, so a 2D player opens the base .m2ts and never sees the rest.

Copying all three by name writes the video twice. 2.18.3 started reporting that; this writes it once instead, so all three names resolve to the same sectors again, as on the source disc.

tsMuxeR --bdmv-to-iso --3d-single-copy <BDMV_folder> out.iso
Both facts it needs are stated on the disc, so nothing is guessed: the clip info file lists where the chunks divide, and the playlist names which two clips pair up. A group whose five files are not all present, or whose two views are not cut into the same number of chunks, is left alone and copied as found.

Off by default. Without it the image is byte for byte what it was before.

Measured on a six-group 3D structure, with 1, 2, 2, 4, 4 and 4 chunk pairs:

without 366,084,096 bytes, every chunk of video present TWICE
with 188,088,320 bytes, every chunk present ONCE, dependent view first
All 18 files read back byte for byte identical to the source, checked twice with two independent readers: 7-Zip, and the operating system's own UDF driver, which is what a player uses.

Then on a full-size 3D structure, 852 files and 40.8 GiB, its main title interleaved in 1,774 chunk pairs:

image 43,796,791,296 bytes, against 43,800,002,560 for the source it was built from
a plain copy would have written 87.2 GB
files 852 of 852 byte for byte identical, 0 different, 0 missing, 0 added
The source stores its video once, and the rebuilt image lands 3.21 MB from the same size, which is the difference in UDF overhead and nothing else. 0 added says the source's own BACKUP came through untouched rather than being regenerated.

The 3D authoring path was verified, not changed
tsMuxeR has authored 3D discs from streams for years, and createInterleavedFile is shared between that path and the new one, so it was run rather than assumed. Muxing the two views of a 3D source to a Blu-ray ISO gives a base view and a dependent view whose sizes sum to the .ssif exactly, inside an image too small to hold the video twice, with the dependent chunk first. Building a disc that way and then copying it with --3d-single-copy returns every file byte for byte.

Note that only a Blu-ray ISO can hold this. Two files sharing one run of sectors is a property of the UDF image; a folder on an ordinary filesystem cannot express it.

Fixed: an interleaved 3D file could be built wrong instead of refused
createInterleavedFile guarded its two preconditions with assertions, which a release build removes. Both mean the interleave cannot be described: unequal piece counts leave chunks with no partner, and a part-sector piece cannot be addressed by a non-final allocation descriptor. Building it anyway produces a file of exactly the right length with its two halves out of step, which no size check catches and no reader reports. Both conditions now say what is wrong and refuse.

The 3D authoring path calls the same function and ignored its result, which was reasonable while the only outcome was an assertion a release build deletes. It acts on a refusal now: carrying on past one would end the build with "Mux successful complete" while leaving a zero-length .ssif in the image, which is a 3D disc that cannot play, reported as a success.

The BDMV folder to ISO tab has a checkbox for it
The option was reachable only from the command line, and that tab is where someone wrapping a 3D disc actually is. One checkbox next to the other build options, off like the option itself, with a tooltip explaining the three names. Translated into all eight interface languages.

Fixed: leaving out the output path printed one character
--bdmv-to-iso was only routed to its own handler when at least four arguments came with it, so a call that forgot the output path fell through to the ordinary muxing path, which tried to open --bdmv-to-iso as a meta file and printed a single character of the resulting exception. The mode is routed on its own name now, and all three of --bdmv-to-iso, one argument and three arguments print what the mode expects.

Fixed: the layer-break guard could move a UDF structure and corrupt files
This is not a 3D fault. It was found while testing the 3D authoring path, but it reproduces on an ordinary copy with --3d-single-copy off and no 3D content involved.

Who it reaches. It needs a disc of roughly 7,000 files or more, with --layer-break-guard or --inner-only in use. For scale, a full feature disc measured here holds 852 files, about a ninth of that, so an ordinary disc was never at risk. If you built an image far larger than that with an earlier version, a BD-J disc for instance, the result is worth checking. The damage is silent: the build reports success and the files look normal.

The UDF unique-id mapping file lives at a fixed address just past the metadata partition, and it is written at the very end of the build by seeking BACK to it. FileEntryInfo::write consults the layer-break guard on every write, so a guard zone that reached back that far padded the mapping file FORWARD, out of its own home and into the data area.

The guard exists to move file data off the sectors around a layer transition. A volume structure has nowhere else it may live, so moving one does not protect it, it destroys the image. The guard is now suppressed while such a structure is written.

The metadata region grows with the file count, so the two eventually meet. Measured on a 12,005 file tree with --inner-only on a BD50, which is a supported combination and not a contrived one:

before the mapping file's home is sector 12,928, the guard's before-zone begins at 8,704,
so the structure was written at sector 24,429,792 and four navigation files
(index.bdmv, MovieObject.bdmv and both .clpi) came back wrong
after 12,005 of 12,005 files byte for byte identical
Also visible on a small tree with a hand-set early break, where it silently replaced the first sector of the first file with a descriptor: eight break positions from 700 to 2000 sectors are now byte-exact where four of them were not.

Fixed: a layer-break guard could land inside a 3D chunk
3D only, and only with a guard in use. The guard pad is laid down wherever the copy write that reaches the zone happens to begin, and a chunk larger than the 16 MB copy buffer takes several writes, so the pad could fall inside a chunk. The interrupted view then gained a piece its partner did not have and the group could not be rebuilt at all. Reproduced on real chunk tables, which have 125 chunks over 16 MB in the main title alone:

Can't interleave BDMV/STREAM/SSIF/00019.ssif: 5 pieces against 4
The pad is now placed at the boundary between one pair of chunks and the next, where both views are between pieces and stay in step. Verified with the pad falling both before a group and inside one, byte exact in each case.

Supported incoming formats:

* TS;
* M2TS;
* Blu-ray;
* Demux option.

Supported videocodecs:

* H.264
* Microsoft VC-1;
* MPEG-2.

Supported audiocodecs:

* AAC;
* AC3 / E-AC3(DD+);
* Dolby True HD (for streams with AC3 core only);
* DTS/ DTS-HD;
* LPCM.

Supported subtitle types:

* M2TS Presentation graphic stream.
* SRT text subtitles

Supported containers and formats:

* Elementary stream;
* Transport stream TS and M2TS;
* Program stream EVO/VOB/MPG;
* Matroska MKV/MKA;
* MP4/MOV

Main features:

* Automatic or manual fps adjustment while mixing;
* Level changing as well as SEI, SPS/PPS elements and NAL unit delimiter cycle insertion while mixing H.264;
* Audio tracks and subtitles time shifting;
* Ability to extract DTS core from DTS-HD;
* Ability to extract AC3 core from True-HD;
* Ability to join files;
* Ability to adjust fps for subtitles;
* Ability to convert LPCM streams into WAVE and vice versa;
* Track language information injection into blu-ray structure and TS header;
* Ability to cut source files;
* Ability to split output file;
* Ability to detect audio delay for TS/M2TS/MPG/VOB/EVO sources;
* Ability to remove pulldown info from stream;
* Ability to open Blu-ray playlist (MPLS) files;
* Ability to convert SRT subtitles to PGS;
* Tags for SRT subtitles support - tags for changing font, color, size, etc.; tag's syntax is similar to HTML;
* United cross-platform GUI - Windows, Linux, MacOS.