Log in

View Full Version : tsMuxer Open Source


Pages : 1 2 3 [4] 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

justdan96
16th December 2019, 16:27
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
16th December 2019, 19:56
0x16 = HDR10+ : Alita BD is authored incorrectly.


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

justdan96
17th December 2019, 08:29
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
17th December 2019, 10:26
.............

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
17th December 2019, 16:21
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
17th December 2019, 22:28
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
18th December 2019, 12:11
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
19th December 2019, 08:20
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
19th December 2019, 10:07
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
19th December 2019, 15:49
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
19th December 2019, 19:41
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
21st December 2019, 15:41
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
29th December 2019, 18:24
@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
30th December 2019, 03:45
Great work, can't wait for a Gui version. Thank you very much for all your time.

SeeMoreDigital
30th December 2019, 11:33
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
30th December 2019, 14:26
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
30th December 2019, 16:18
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
30th December 2019, 18:41
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
31st December 2019, 11:11
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
31st December 2019, 14:13
@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
31st December 2019, 16:42
I don't suppose you have logs from the player we could try to analyse?

SeeMoreDigital
31st December 2019, 16:59
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
31st December 2019, 22:57
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
1st January 2020, 02:50
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
1st January 2020, 12:52
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
1st January 2020, 13:07
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
1st January 2020, 16:43
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
1st January 2020, 17:06
@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
1st January 2020, 17:10
Hello...

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

You need to register...

a5180007
1st January 2020, 18:15
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
1st January 2020, 18:29
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
1st January 2020, 22:31
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
2nd January 2020, 10:25
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
2nd January 2020, 13:58
Yes a5180007, tested on oppo, now Dolby Vision is detected and the movie starts normally.
Same here

SeeMoreDigital
2nd January 2020, 19:06
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
2nd January 2020, 23:56
@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
3rd January 2020, 02:08
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
3rd January 2020, 03:06
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
3rd January 2020, 10:17
@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
3rd January 2020, 19:52
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
3rd January 2020, 21:54
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
3rd January 2020, 21:55
@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
3rd January 2020, 22:49
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
3rd January 2020, 23:07
Yep.
When the output is ISO the chapters are there

a5180007
4th January 2020, 09:03
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
4th January 2020, 11:01
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
4th January 2020, 11:31
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
4th January 2020, 11:47
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
4th January 2020, 11:52
@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
4th January 2020, 12:10
@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 ?