BD Rebuilder Beta - Bug Reports Only

[Lathe]

Originally Posted by MrVideo

I was looking for a box in which to enter the text. I wasn't expecting a checkbox having to be ticked first. Silly me for thinking that. Oh well.

Thanks.

Sure thing mate. The reason I knew about it is that I've actually used it before, so that's why... Not being an AVS expert, I don't know if there are any limits to the script you can use, but for the basic stuff I do (tweak, etc.) it seems to work okay.

[MrVideo]

Well, that didn't work. The frame rate is still an incorrect 59.94fps. I'm sorry, but this needs to be fixed. Relying on MediaInfo, which is getting a false positive, is causing BDRB to do things it isn't supposed to. There needs to be an override option to force no VFR.

[jdobbs]

Originally Posted by MrVideo

Well, that didn't work. The frame rate is still an incorrect 59.94fps. I'm sorry, but this needs to be fixed. Relying on MediaInfo, which is getting a false positive, is causing BDRB to do things it isn't supposed to. There needs to be an override option to force no VFR.

Try setting "IMPORT_VFR_SCAN=1" If set, BD-RB will collect all the timecodes and check for VFR itself. I'll have to check whether it will override MEDIAINFO.

Interestingly, I rarely have ever seen a false positive on VFR.

[TatanScorp]

When I import a MKV file into BDrebuilder it reads "Importing MKV"
then "Collecting audio/video streams from source" After building a pseodo Bd structure Bd rebuilder shows only a vid and subtitle track but no audio. It's a Atmos tract but at least it should show 7.1 tract. How do I get the audio?

Thanks

[MrVideo]

Originally Posted by jdobbs

Try setting "IMPORT_VFR_SCAN=1" If set, BD-RB will collect all the timecodes and check for VFR itself. I'll have to check whether it will override MEDIAINFO.

It still does VFR to CFR, doubling the frame rate.

Interestingly, I rarely have ever seen a false positive on VFR.

I have a 100MB test file that I can upload for you to use as a test.

[jdobbs]

Originally Posted by MrVideo

It still does VFR to CFR, doubling the frame rate.

I have a 100MB test file that I can upload for you to use as a test.

I'd appreciate it if I can get the file.

[jdobbs]

Originally Posted by TatanScorp

When I import a MKV file into BDrebuilder it reads "Importing MKV"
then "Collecting audio/video streams from source" After building a pseodo Bd structure Bd rebuilder shows only a vid and subtitle track but no audio. It's a Atmos tract but at least it should show 7.1 tract. How do I get the audio?

Thanks

I don't think I've ever tried importing an Atmos track. But... I believe it isn't a legal audio track for blu-ray unless it is inside a Dolby TrueHD wrapper. I can tell you this -- in the version of the BD standard that I have (a few years old) there isn't a single reference to the term "Atmos". My guess is that TSMUXER rejects it -- but, as I said, I've never actually tried.

[MrVideo]

Originally Posted by jdobbs

But... I believe it isn't a legal audio track for blu-ray unless it is inside a Dolby TrueHD wrapper.

Or Dolby Digital Plus.

[jdobbs]

Originally Posted by MrVideo

The test file is here.
Once you have it, I will delete it. If need be, I can get you one that works.

Got it.

[TatanScorp]

Originally Posted by jdobbs

I don't think I've ever tried importing an Atmos track. But... I believe it isn't a legal audio track for blu-ray unless it is inside a Dolby TrueHD wrapper. I can tell you this -- in the version of the BD standard that I have (a few years old) there isn't a single reference to the term "Atmos". My guess is that TSMUXER rejects it -- but, as I said, I've never actually tried.

I don't get it. I'm getting the Atmos tract off of a Blu-ray disk, and yes TSmuxer doesn't recognize the track. Isn't the Atmos just meta data plus the Dolby True HD 7.1? The two Blu-rays I have with Atmos are John Wick and John Wick 2.

[jdobbs]

Originally Posted by TatanScorp

I don't get it. I'm getting the Atmos tract off of a Blu-ray disk, and yes TSmuxer doesn't recognize the track. Isn't the Atmos just meta data plus the Dolby True HD 7.1? The two Blu-rays I have with Atmos are John Wick and John Wick 2.

Kinda', yes, but... there's an independent track contained in it. The problem is that on a Blu-Ray disc it is packaged together with a normal Dolby track (as one stream) so it is treated as an extension to it. When an MKV is created they are separated. Unless they are recombined it is not a legal track. That makes sense since Atmos isn't officially a part of the standard. The same concept applies to other audio types as well. Support for Atmos is optional but not required -- so there has to be a fallback audio stream for players that don't support it.

The bottom line is that the audio track you are trying to mux isn't a legal Blu-Ray audio track -- so, as would be expected, it is rejected.

[MrVideo]

Originally Posted by jdobbs

When an MKV is created they are separated. Unless they are recombined it is not a legal track.

I was curious about this, so I went looking for info and found a site that has a boatload of Dolby trailers, several of which have ATMOS.

I used mkvmerge to look at the content of one of them and there was just one video stream and one audio stream (TrueHD Atmos).

It looks like the author of tsmuxer is going to have to update his program to accept TrueHD-Atmos audio streams. Until then BDRB is going to end up without the audio stream because tsmuxer doesn't like it.

[MrVideo]

Originally Posted by jdobbs

Got it.

OK, deleted. Let me know if you want a sample where BDRB doesn't think it is VFR.

[jdobbs]

Originally Posted by MrVideo

I was curious about this, so I went looking for info and found a site that has a boatload of Dolby trailers, several of which have ATMOS.

I used mkvmerge to look at the content of one of them and there was just one video stream and one audio stream (TrueHD Atmos).

It looks like the author of tsmuxer is going to have to update his program to accept TrueHD-Atmos audio streams. Until then BDRB is going to end up without the audio stream because tsmuxer doesn't like it.

If it is TrueHD-Atmos it will likely accept it. My guess would be the ones that fail would be Atmos only...

[jdobbs]

Originally Posted by MrVideo

OK, deleted. Let me know if you want a sample where BDRB doesn't think it is VFR.

The timecodes indicate VFR since there isn't consistent separation. Here is a short partial look at some display timecodes (in ms):

352
418
452
485
518
552
585
619
635
652
669
685
685
702
702
719
719
735
735
752
752
769
769
785
785
802
819
835
852
869
886
902
919
936
952
969
986
1002
1019
1036
1052
1069
1086
1102
1119
1136
1152
1169
1186
1202
1219
1236
1253
1269
1286
1303
1319
1336
1353
1369
1386
1403
1419
1436
1453
1469
1486
1503
1519
1536
1553
1570
1586
1603
1620
1636
1653
1670
1686
1703
1720
1736
1753
1770
1786
1803
1820
1836
1853
1870
1887
1903
1920
1937
1953
1970
1987
2003
2020

Just guessing, it looks like some of the frames have two fields with the same display timecode and others (most) have two fields that are temporally separated. I don't think that's normal. With that said, it also looks like BD-RB is mixing up the field timecodes with frame timecodes, causing the framerate speedup.

[Edit] I just checked a couple other interlaced sources. They only include timecodes for frames (not fields) -- so I guess that's why the issue with framerate doubling hasn't occurred before. When BD-RB scans and determines VFR, it has to then use the minimum separation of timecodes to determine the actual underlying frame rate.

Also, I'm pretty sure the non-temporally separated display timecodes on the fields is also why MEDIAINFO is also reporting the rate as "Variable". I'm going to have to write code for special cases when each field includes a timecode to prevent framerate doubling. But that won't necessarily prevent what we saw here with the determination of VFR caused by consecutive identical timecodes... I'll have to give that some more thought.

[Lathe]

Originally Posted by TatanScorp

I don't get it. I'm getting the Atmos tract off of a Blu-ray disk, and yes TSmuxer doesn't recognize the track. Isn't the Atmos just meta data plus the Dolby True HD 7.1? The two Blu-rays I have with Atmos are John Wick and John Wick 2.

So far TSMuxer has never accepted an MKV file where the the original TrueHD track has been muxed in with it. As JD said, AFAIK, EVERY time you convert or mux a TrueHD track to MKV it always rips out the AC3 core. It is an easy fix though. All you have to do is use EAC3to or with the GUI like I do, UsEac3to, drop in the MKV file, choose the True track, and select as your output THD+AC3. That way, EAC3to puts the AC3 core back into the file (thus now making it 'legal') and the resulting THD+AC3 file WILL now be accepted by TSMuxer. As far as the Atmos stuff, that I'm not sure about...

[MrVideo]

Originally Posted by Lathe

So far TSMuxer has never accepted an MKV file where the the original TrueHD track has been muxed in with it.

But, the tsmuxer author should release a new version where TrueHD audio is accepted, as it is legal Blu-ray audio.

But that is a topic for the tsmuxer thread.

[MrVideo]

Originally Posted by jdobbs

Just guessing, it looks like some of the frames have two fields with the same display timecode and others (most) have two fields that are temporally separated.

Who knows what the hell CBS is doing with their H.264/4:2:2 encoders.

As a test, I captured 100MB of the same transponder stream using the professional Tandberg IRD. That is this file. It has good in the filename, but for some reason BDRB doesn't like it either.

So, I went back and ran one of the previous files I captured with the same IRD, on the same computer, and that file was still liked by BDRB. That file is 230MB and it is here.

I'm curious what you find out about those two files and why one is working. They might give you more clues as to why BDRB is doing what it is doing.

As a test, you might want to force no VFR testing to see how x264 handles those video streams. If x264 deals with them just fine and converts them to H.264/4:2:0 interlaced, without any issues, it might be easier to code in a no-VFR option instead of trying to code around the weird timestamps.

[jdobbs]

Originally Posted by MrVideo

But, the tsmuxer author should release a new version where TrueHD audio is accepted, as it is legal Blu-ray audio.

But that is a topic for the tsmuxer thread.

No. It is not. Support for TrueHD is optional in a player. That's why the core is required to be muxed with TrueHD.

[MrVideo]

I did some more digging and discovered that when a MKV file is created and a TrueHD audio stream is added to the output, the AC3 core is stripped out. Sounds kinda stupid to me. Now to find out why that is done.

UPDATE: Found out why: https://github.com/mbunkus/mkvtoolni...rueHD-and-AC-3