tsMuxer is a transport stream muxer for remuxing/muxing elementary streams, EVO/VOB/MPG, MKV/MKA, MP4/MOV, TS, M2TS to TS to M2TS. Supported video codecs H.264/AVC, H.265/HEVC, VC-1, MPEG2. Supported audio codecs AAC, AC3 / E-AC3(DD+), DTS/ DTS-HD.
Hi,
I found a bug in "Nightly build from 2022-01-10-02-10-24" (ab2e101) [windows version]. After muxing streams from direct mkv file or from separates files demuxed by ffmpeg (to hevc and ac3 file) there is problem with Dolby Vision profile. I've tested it with TS Muxer and M2TS muxer, both files after muxing with this version, reports wrong Dolby Vision profile.
Last version that I'm sure that works and generate correct profile is "Nightly build from 2022-01-04-02-09-52 (e0279f3).
I tested it on 3 different source files (2x mkv and mp4). All have different content (different movies), all have DoVi profile 5.
I have tested Dolby vision profile report using MediaInfo. Also my LG OLED TV (B9) cannot open such file with wrong DoVi profile.
Look at "HDR format".
Wrong report in m2ts file (generated using: ab2e101):
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.04.0B, EL+RPU, SDR compatible
Codec ID : 36
Duration : 2 h 35 min
Bit rate : 24.5 Mb/s
Width : 3 840 pixels
Height : 1 608 pixels
Display aspect ratio : 2.40:1
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.165
Stream size : 26.7 GiB (92%)
Correct report in m2ts file (generated using: e0279f3), file works without problem in my TV:
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 : 2 h 35 min
Bit rate : 24.5 Mb/s
Width : 3 840 pixels
Height : 1 608 pixels
Display aspect ratio : 2.40:1
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.165
Stream size : 26.7 GiB (92%)
Media info from MKV source file:
Video
ID : 1
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 : V_MPEGH/ISO/HEVC
Duration : 2 h 35 min
Bit rate : 24.3 Mb/s
Width : 3 840 pixels
Height : 1 608 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.164
Stream size : 26.5 GiB (97%)
Default : Yes
Forced : No
jcdr428
commented
2 years ago
Hi, I found a bug in "Nightly build from 2022-01-10-02-10-24" (ab2e101) [windows version]. After muxing streams from direct mkv file or from separates files demuxed by ffmpeg (to hevc and ac3 file) there is problem with Dolby Vision profile. I've tested it with TS Muxer and M2TS muxer, both files after muxing with this version, reports wrong Dolby Vision profile. Last version that I'm sure that works and generate correct profile is "Nightly build from 2022-01-04-02-09-52 (e0279f3).
I tested it on 3 different source files (2x mkv and mp4). All have different content (different movies), all have DoVi profile 5.
I have tested Dolby vision profile report using MediaInfo. Also my LG OLED TV (B9) cannot open such file with wrong DoVi profile. Look at "HDR format".
Wrong report in m2ts file (generated using: ab2e101):
Correct report in m2ts file (generated using: e0279f3), file works without problem in my TV:
Media info from MKV source file: