BD Rebuilder Beta - Bug Reports Only

[84lion]

Any idea why this is happening? This also happens with other seamless branching titles (e.g. - The Martian Extended Edition).

[08/03/19] BD Rebuilder v0.60.18
[18:59:38] Source: GLADIATOR_2000_00391
- Input BD size: 76.55 GB
- Approximate total content: [02:50:56.829]
- Target BD size: 46.26 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Very Good (Very Fast), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[18:59:41] PHASE ONE, Encoding
- [18:59:41] Processing: VID_00498 (1 of 22)
- [18:59:41] Extracting A/V streams [VID_00498]
- Error in attempt to extract audio/subs.
- Can't parse play list file "X:\GLADIATOR4KBR\GLADIATOR_2000\BDMV\\PLAYLIST\00391.mpls"
[18:59:45] - Failed to retrieve audio, aborted

[jdobbs]

I don't remember for sure if it is the old (not connected) Sony player, or the Samsungs that I have, but the player refused the BD authored DVD disc because it wasn't on BD media. So, creating a BD5/9 doesn't mean that your BD player will play it.Yeah. Most accept it, but not all. I think pretty much all will accept it in strict AVCHD format. But, as you mentioned, there's not a lot of incentive to do BD-5/9 these days with a 50 pack of high-end (Verbatim) BD-R blanks costing less than $40.

[jdobbs]

The problem with debugging these UHD reports is that even if I know the disc name, I have no way of getting my hands on them so I can try to repeat/fix the problem.

[jdobbs]

Any idea why this is happening? This also happens with other seamless branching titles (e.g. - The Martian Extended Edition).

[08/03/19] BD Rebuilder v0.60.18
[18:59:38] Source: GLADIATOR_2000_00391
- Input BD size: 76.55 GB
- Approximate total content: [02:50:56.829]
- Target BD size: 46.26 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Very Good (Very Fast), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[18:59:41] PHASE ONE, Encoding
- [18:59:41] Processing: VID_00498 (1 of 22)
- [18:59:41] Extracting A/V streams [VID_00498]
- Error in attempt to extract audio/subs.
- Can't parse play list file "X:\GLADIATOR4KBR\GLADIATOR_2000\BDMV\\PLAYLIST\00391.mpls"
[18:59:45] - Failed to retrieve audio, abortedThat error is coming from TSMUXER when it is trying to demux using the MPLS. I don't think I've see that before.

[CV91913]

That error is coming from TSMUXER when it is trying to demux using the MPLS. I don't think I've see that before.

Is the directory tree BDMV\\PLAYLIST a valid path?

[Acerjen]

Jdobbs,

Do you have any UHD discs? Which ones? Just curious.

[MrVideo]

But, as you mentioned, there's not a lot of incentive to do BD-5/9 these days with a 50 pack of high-end (Verbatim) BD-R blanks costing less than $40.
https://www.ebay.com/itm/100-OQ-6x-25GB-Blu-ray-BD-R-Glossy-White-Inkjet-HUB-Printable-OQBDR06GWIP-H-50/251168706948?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649

I print on the discs. Inkjet printing doesn't come close to professional printing, but it is better than nothing.

[jdobbs]

Is the directory tree BDMV\\PLAYLIST a valid path?Good catch. I didn't notice that.

[jdobbs]

Jdobbs,

Do you have any UHD discs? Which ones? Just curious.Yes, of course, just for testing. But very few. They all work with BD-RB... I also have 4K MKVs that I have created for testing of imports.

[84lion]

Is the directory tree BDMV\\PLAYLIST a valid path?

Yeah, that looks like the problem. I don't know why the program is evidently inserting the extra forward slash. I'm not doing it, at least knowingly. Is there any way to specify the directory tree in BD-Rebuilder?

Also had this problem this morning - everything purring along beautifully and then...so close to completion...

[08/03/19] BD Rebuilder v0.60.18
[20:07:25] Source: HULK_UHD_UPK1_00801
- Input BD size: 80.29 GB
- Approximate total content: [02:18:06.444]
- Target BD size: 46.26 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Better (Faster), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[20:07:32] PHASE ONE, Encoding
- [20:07:32] Processing: VID_00026 (1 of 1)
- [20:07:32] Extracting A/V streams [VID_00026]
- [20:13:58] Reencoding video [VID_00026]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 198,676 frames
- Bitrate: 35,000 Kbs
- [20:13:58] Reencoding: VID_00026, Pass 1 of 1
- [08:35:56] Video Encode complete
- [08:35:56] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4357 (eng): Keeping original audio
[08:38:16]PHASE ONE complete
[08:38:16]PHASE TWO - Rebuild Started
- [08:38:16] Rebuilding BD file Structure
- Failed in attempt to multiplex: MUX_MOVIE_ONLY.meta
- Bitstream exception Unknown exception. It does not have to be! Please contact application support team for more information.
[08:38:31] - Failed to REBUILD

And Jdobbs - :thanks: for all the great work you do. I appreciate it!

[jdobbs]

Is the directory tree BDMV\\PLAYLIST a valid path?Interestingly, I just looked at the code and it always puts that extra backslash in -- and has been for almost 10 years (since v0.18.1). TSMUXER just accepts it fine and it works fine. Now that is really weird.

[jdobbs]

Yeah, that looks like the problem. I don't know why the program is evidently inserting the extra forward slash. I'm not doing it, at least knowingly. Is there any way to specify the directory tree in BD-Rebuilder?

Also had this problem this morning - everything purring along beautifully and then...so close to completion...

[08/03/19] BD Rebuilder v0.60.18
[20:07:25] Source: HULK_UHD_UPK1_00801
- Input BD size: 80.29 GB
- Approximate total content: [02:18:06.444]
- Target BD size: 46.26 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Better (Faster), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[20:07:32] PHASE ONE, Encoding
- [20:07:32] Processing: VID_00026 (1 of 1)
- [20:07:32] Extracting A/V streams [VID_00026]
- [20:13:58] Reencoding video [VID_00026]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 198,676 frames
- Bitrate: 35,000 Kbs
- [20:13:58] Reencoding: VID_00026, Pass 1 of 1
- [08:35:56] Video Encode complete
- [08:35:56] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4357 (eng): Keeping original audio
[08:38:16]PHASE ONE complete
[08:38:16]PHASE TWO - Rebuild Started
- [08:38:16] Rebuilding BD file Structure
- Failed in attempt to multiplex: MUX_MOVIE_ONLY.meta
- Bitstream exception Unknown exception. It does not have to be! Please contact application support team for more information.
[08:38:31] - Failed to REBUILD

And Jdobbs - :thanks: for all the great work you do. I appreciate it!That's also an error from TSMUXER. You're using the version of TSMUXER that is included with BD-RB, right? I've seen that error before -- if I remember correctly it is related to a bad source file, but it's been a long time.

Can you post the .META file for this job and also for one of the seamless branching titles that failed?

[84lion]

Sorry for my stupidity...where is the .META file located? If it's in the WORKFILES folder...unfortunately, I deleted that since I needed the space.

I'll try re-ripping Hulk. The file I was using was a rip to an outboard hard drive that I copied over to the hard drive on my computer. It's possible that in the copying process that the file got corrupted.

Finally, I'll check to make sure I have the TSMUXER version you specify in the initial post of this thread. If it hasn't changed since 60.04 then it should be the same.

[zamengo]

The problem with debugging these UHD reports is that even if I know the disc name, I have no way of getting my hands on them so I can try to repeat/fix the problem.

If you need, I can upload Avengers Endgame UHD disc to google drive.

[ripem2011]

Hi jdobbs i got the same error doing AQUAMAN i played the movie even though it didnt finish it and in properties it show the DV when i played it Video: HEVC 3840x2160 23.976fps [V: hevc main 10 L5.1, yuv420p10le, 3840x2160] Video: HEVC 1920x1080 23.976fps [V: hevc main 10 L5.1, yuv420p10le, 1920x1080] so i dont know if that means its keeping the DV too

[MrVideo]

I don't know why the program is evidently inserting the extra forward slash.
It is a backslash. As noted, tsmuxer inserts those and the OS is accepting them.

BTW, there is many a time where I see an ad that has a website listed and the announcer says "backslash" instead of "forward slash." :eek:

[jdobbs]

Hi jdobbs i got the same error doing AQUAMAN i played the movie even though it didnt finish it and in properties it show the DV when i played it Video: HEVC 3840x2160 23.976fps [V: hevc main 10 L5.1, yuv420p10le, 3840x2160] Video: HEVC 1920x1080 23.976fps [V: hevc main 10 L5.1, yuv420p10le, 1920x1080] so i dont know if that means its keeping the DV tooNot sure I get what you are saying? Where does the "DV" come in?

[Ch3vr0n]

Dolby vision

Sent from my Pixel 3 XL using Tapatalk

[jdobbs]

Dolby vision

Sent from my Pixel 3 XL using TapatalkAhhh, I see. It confused me because of the actual format called DV (Digital Video) that is common on some video recorders.

@ripem2011

Dolby Vision isn't supported yet. I have a few details on it, but not all that is needed. I probably won't work on it until I have standard UHD processing bug free.

[Ch3vr0n]

And the chance you're going to get them is close to non-existent. It's a proprietary format with 0 documentation available. The currently only known program to fully support it is elaborate bytes' clonebd, and it required them to rewrite half the program and add support bit by bit.

You could contact them, maybe they'll be kind enough to tell you what they know.

Sent from my Pixel 3 XL using Tapatalk

[cartman0208]

I seem to have the same issue I posted back here (https://forum.doom9.org/showthread.php?p=1877744#post1877744) with version 0.60.04
Not Aquaman this time, but I will try that as well.
----------------------
[08.04.19] BD Rebuilder v0.60.18
[21:59:38] Source: VENOM_2018
- Input BD size: 54,98 GB
- Approximate total content: [02:09:45.108]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Very Good (Very Fast), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[21:59:41] PHASE ONE, Encoding
- [21:59:41] Processing: VID_00001 (1 of 1)
- [21:59:41] Reencoding video [VID_00001]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 161.640 frames
- Bitrate: 31.245 Kbs
- [21:59:41] Reencoding: VID_00001, Pass 1 of 1
- [13:20:09] Video Encode complete
- [13:20:09] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4355 (deu): Keeping original audio
- [13:20:09] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00001.meta
- Can't open file: V:\BDFILES50\WORKFILES\VID_00001_2.AVS.264
[13:20:13] - Failed to build structure, aborted
----------------------

and after renaming VID_00001_2.AVS to VID_00001_2.AVS.264 and resuming the rebuild is fine (VID_00001_2.AVS is recreated? in the process, at least it has the same content)

----------------------
[08.05.19] BD Rebuilder v0.60.18
[16:21:25] Source: VENOM_2018
- Input BD size: 54,98 GB
- Approximate total content: [02:09:45.108]
- Target BD size: 46,26 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Very Good (Very Fast), ABR
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[16:21:27] PHASE ONE, Encoding
- [16:21:27] Processing: VID_00001 (1 of 1)
- [16:21:27] Multiplexing M2TS
[16:45:55]PHASE ONE complete
[16:45:55]PHASE TWO - Rebuild Started
- [16:45:55] Rebuilding BD file Structure
[16:46:14] - Encode and Rebuild complete
[16:46:14] JOB: VENOM_2018 finished.


If nobody else does have issues with UHDs, I think my system is messed up somehow :confused:

[jdobbs]

@cartman0208

- Error in attempt to multiplex: MUX_00001.meta
- Can't open file: V:\BDFILES50\WORKFILES\VID_00001_2.AVS.264That error can occur when you are attempting backup of a Dolby Vision source. Dolby Vision isn't supported yet. The .264 file it can't open represents the Dolby data that is muxed separately (as track 4117) in the source. What I guess I should do, at least until Dolby Vision is supported, is pop up a "no can do" message when it is encountered.

[jdobbs]

To those who are getting the "UHD_Correct_M2TS() 00009 8102" error. I have found/fixed at least one cause of it (thanks for the help, zamengo). I'd created an array to hole CPI table data that is collected during the remux of the M2TS (offsets for fast forward, etc). It wasn't large enough for some sources. I'm testing the fix right now and will post as soon as I'm sure it is all good.

[cartman0208]

Is it possible to strip the Dolby Vision data?
Like backup a 3D source as 2D?

[jdobbs]

Is it possible to strip the Dolby Vision data?
Like backup a 3D source as 2D?I could probably convert it to standard HDR10, but I'm not sure yet how to extract the data from that secondary stream. It might just be easier to support it, I don't know yet. The only reason I haven't done it already is that I'm missing some information as to how it is supported (that and the fact that I haven't looked at it in several months). I'll have to go back and review it before deciding what I'm going to do.

[cartman0208]

No sweat, I could do with the "no can do" message until then :)

[SeeMoreDigital]

I could probably convert it to standard HDR10, but I'm not sure yet how to extract the data from that secondary stream. If 'for the purposes of testing', all you need to do is extract the secondary Dolby Vision data stream, the little 'dv-mp4-maker.exe' maker app can do that...

[jdobbs]

If 'for the purposes of testing', all you need to do is extract the secondary Dolby Vision data stream, the little 'dv-mp4-maker.exe' maker app can do that...TSMUXER can extract it easy enough. But I need to be able to interpret it. I don't know how (yet).

Is the source code for 'dv-mp4-maker.exe' around anywhere? That might reveal something that could be used for HDR10 conversion, or maybe even for rebuilding it.

[gonca]

I could probably convert it to standard HDR10, but I'm not sure yet how to extract the data from that secondary stream. It might just be easier to support it, I don't know yet. The only reason I haven't done it already is that I'm missing some information as to how it is supported (that and the fact that I haven't looked at it in several months). I'll have to go back and review it before deciding what I'm going to do.

Do you mean converting Dolby Vision to HDR10?:confused:

[jdobbs]

Do you mean converting Dolby Vision to HDR10?:confused:Yes. But, as I said, it depends on how hard it will be to support Dolby Vision directly.

[jdobbs]

Is it possible to strip the Dolby Vision data?
Like backup a 3D source as 2D?Apparently, from what I gather, a Blu-Ray stream with Dolby Vision stream also includes HDR10. So I should be able to support it as an HDR10 stream until I find out how to provide support for Dolby Vision.

Has anyone seen contradicting information?

[laserfan]

Not sure but jdobbs this thread might be useful to you in some way?

https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602&sid=f74fc972c355c40f0c94ad9c2def00a1

[SeeMoreDigital]

Apparently, from what I gather, a Blu-Ray stream with Dolby Vision stream also includes HDR10....Indeed it does.

I've carried out quite a few Dolby Vision detection tests using my LG television and OPPO UDP-203 playback devices and with most current muxing tools when you mux a HEVC stream with Dolby Vision into the .m2ts or .mkv container, the aforementioned hardware playback devices only detect/trigger the HDR10 layer.

[jdobbs]

I've updated the first post of this thread with a link to the most recent release of BD Rebuilder. Changes for this release:- Corrected "UHD_Correct_M2TS() 00009 8102"
error that could be experienced on some
high framecount BDs.
- Fixed "Can't open file:" error that can
occur when attempting backup of sources
with Dolby Vision.
- Added code to help support Dolby Vision, it
is very experimental and needs much more
testing.
- Other minor corrections and cosmetic fixes.

[FilipeAmadeuO]

I've updated the first post of this thread with a link to the most recent release of BD Rebuilder. Changes for this release:- Corrected "UHD_Correct_M2TS() 00009 8102"
error that could be experienced on some
high framecount BDs.
- Fixed "Can't open file:" error that can
occur when attempting backup of sources
with Dolby Vision.
- Added code to help support Dolby Vision, it
is very experimental and needs much more
testing.
- Other minor corrections and cosmetic fixes.
Tested 0.60.19 and the error "Corrected "UHD_Correct_M2TS() 00009 8102" still appears on SOLO STAR WARS UHD. Any sugestion ?

[jdobbs]

Tested 0.60.19 and the error "Corrected "UHD_Correct_M2TS() 00009 8102" still appears on SOLO STAR WARS UHD. Any sugestion ?When you reported it (https://forum.doom9.org/showthread.php?p=1880987#post1880987) a couple of days ago you said the error was "UHD_Correct_M2TS() 00006 8102". Are you sure it isn't error 00006?

[gonca]

Yes. But, as I said, it depends on how hard it will be to support Dolby Vision directly.
Dolby Vision and HDR10 co-exist in the same stream.
If you omit the DV layer you still have HDR10.
Typical movie disc layout of m2ts

4K video layer, movie and HDR metadata
2K video layer, DV metadata
Sound
Subs
Etc

[ripem2011]

Ahhh, I see. It confused me because of the actual format called DV (Digital Video) that is common on some video recorders.

@ripem2011

Dolby Vision isn't supported yet. I have a few details on it, but not all that is needed. I probably won't work on it until I have standard UHD processing bug free.

yes thats what i am saying it kept the Dolby Vision file it shows both

[ripem2011]

yes thats what i am saying it kept the Dolby Vision file it shows both

you are right it show Dolby Vision i just tried it and it plays the HDR and not Dolby Vision my bad

[FilipeAmadeuO]

When you reported it (https://forum.doom9.org/showthread.php?p=1880987#post1880987) a couple of days ago you said the error was "UHD_Correct_M2TS() 00006 8102". Are you sure it isn't error 00006?

You are correct. The error reported was:
08/06/19 [18:56:02] UHD_Correct_M2TS() 00006 8102

[spotter]

I'm wondeirng if it ever be possible to add hdr10+ metadata based on dolby vision to a stream, this would be somewhat of a game changer for those with hdr10+ TVs. My guess is that it be significantly harder to go in the opposite direction (hdr10+ to dolby vision), but who knows.

[jdobbs]

I'm wondeirng if it ever be possible to add hdr10+ metadata based on dolby vision to a stream, this would be somewhat of a game changer for those with hdr10+ TVs. My guess is that it be significantly harder to go in the opposite direction (hdr10+ to dolby vision), but who knows.If I'm seeing it correctly, the HDR10 metadata is already there, stored in the same way as if it weren't Dolby Vision. I'm not sure how it changes with HDR10+. I don't have an HDR10+ source to dump/study.

Things are changing too fast... it's getting really hard to keep up.

[FilipeAmadeuO]

If I'm seeing it correctly, the HDR10 metadata is already there, stored in the same way as if it weren't Dolby Vision. I'm not sure how it changes with HDR10+. I don't have an HDR10+ source to dump/study.

Things are changing too fast... it's getting really hard to keep up.
Dolby Vision and HDR10+ are aditional 1080p layers
HDR10 metadata is integrated in the main HEVC

[spotter]

Dolby Vision and HDR10+ are aditional 1080p layers
HDR10 metadata is integrated in the main HEVC

what Filipe said.

a UHD BluRay with HDR will have HDR in the main HEVC stream, but HDR10+ and dolby vision are additions on top of that to enable more dynamic HDR. The problem is it really depends on your TVs support. Most TVs that support dynamic HDR, only support Dolby Vision, while a few (notably all Samsung's) only support HDR10+. Basically a format war all over again.

It be nice if a mechanism was figured out to reauthor blurays to support both (especially if one can do it wiithout modifying the core HEVC stream), but have no clue if its possible.

[SeeMoreDigital]

I have some Dolby Vision (.ts and .mp4 contained) samples where the Dolby Vision meta-data is embedded within the HEVC video stream. And I also have some Dolby Vision samples where the Dolby Vision meta-data is placed within the .m2ts or .mp4 container as a separate stream.

So far all the Dolby Vision encoded discs I have have their Dolby Vision meta-data placed within the .m2ts container as separate stream.

By contrast, I have a couple of HDR10+ encoded discs and their HDR10+ meta-data is embedded within the HEVC video stream.

If people have some samples they would like testing I'm able to do this...

EDIT: Over on the Blu-ray.com forum there's this List of UHDs that contain Dolby Vision (https://forum.blu-ray.com/showthread.php?t=276448) topic, which now contains information about whether the disc has been encoded using MEL (10-bit minimal enhancement layer) or FEL (12-bit full enhancement layer).



Cheers

[SeeMoreDigital]

Most TVs that support dynamic HDR, only support Dolby Vision, while a few (notably all Samsung's) only support HDR10+. Basically a format war all over again.
Actually..... The newer ranges of Panasonic televisions and UHD players support both Dolby Vision and HDR10+

[spotter]

Actually..... The newer ranges of Panasonic televisions and UHD players support both Dolby Vision and HDR10+

yes, but not available to US consumers :) I believe many players support both, but its the TV that really matters. The # of TVs that support both is very small (relative to the size of the market).

Sony was able to add Dolby Vision to their TVs, they have no intent to support HDR10+, but I sort of hope they add it if it gets significant market share

[jdobbs]

I have updated the first post of this thread with a link to the most recent release of BD Rebuilder (v0.60.20). Changes for this version:- Added code to work around the TSMUXER
error: "Can't parse play list file" which
appears to be associated with certain UHD
MPLS files.
- Fixed an error in UHD audio extraction in
which a "Failed to retrieve audio..."
by TSMUXER message might appear.
- Added steps to audio/video extraction
routines to try several demuxing methods
before declaring failure. Prompted by
TSMUXER issues associated with UHD.
- Fixed an issue that could prevent BD-RB
from keeping originals when size permits
while IVTC_1080P is set -- even when the
source was not 29.97fps.
- Added a check in automatic audio track
selection that prevents a mono or stereo
stream from taking priorty over a multi-
channel source just because it is a higher
priority encoding technology.
- Made numerous changes in order to support
Dolby Vision sources. It needs considerable
testing and feedback, but has progressed
significantly.
- Other minor corrections and cosmetic fixes.I would appreciate feedback on the Dolby Vision support. I don't have a player or monitor that supports Dolby Vision -- so your comments are the only way I know if it works properly.

[SeeMoreDigital]

yes, but not available to US consumers :) It is indeed sad that Panasonic products are not readily available for you guys over in the US of A (you don't say where you're from by-the-way).

But good news for the two hundred or-so other countries in the world ;)

[jdobbs]

I have updated the first post of this thread with a link to the most recent release of BD Rebuilder (v0.60.21). Changes for this release:- Fixed an error that would prevent muxing of
Dolby Vision sources that are multipart and
in which the video is being left intact.
This might also affect non-Dolby Vision
sources that have secondary video streams.
- Fixed an issue that would cause oversizing
when reencoding Dolby Vision sources. The
sizing algorithm was not accounting for the
fixed size of the Dolby Vision track.
- Other minor corrections and cosmetic fixes.