BD Rebuilder Beta - Bug Reports Only

[jdobbs]

OK, after 2 days of testing, gradually removing paramters from the stax-string and then adding the parameters from the BDRB string (which I should have done the other way around, because I found it on the second-to-last parameter :mad:) the cause for the flickering is found ...
If the --pic-struct is removed from the command line string, the file plays fine.

But I also noticed, some scenes are WAY to dark on my TV.
A file with intact video (vFormat=8 in the alternate.txt) on the other hand is bright in the same scenes.
I'll do some more testing to find the cause for that...Thanks! Your help is very much appreciated -- I had no way of testing it myself.

[Edit] I went back through requirements of the BD standard information that I have to see when the pic-structure is needed, and I think removing that parameter will be ok.

[jdobbs]

Bug on HEVC/V3 BluRays and x264/LAVF frameserving:

[08.12.20] BD Rebuilder v0.61.10
[20:38:07] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:38:09] PHASE ONE, Encoding
- [20:38:09] Processing: VID_00001 (2 of 4)
- [20:38:09] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00001.meta
- Can't open file: Q:\4K\WORKFILES\VID_00001.AVS.hevc
[20:38:13] - Failed to build structure, aborted
----------------------
[08.12.20] BD Rebuilder v0.61.10
[20:39:11] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:39:12] PHASE ONE, Encoding
- [20:39:12] Processing: VID_00001 (2 of 4)
- [20:39:12] Multiplexing M2TS
- [20:39:17] Processing: VID_00002 (3 of 4)
- [20:39:17] Extracting A/V streams [VID_00002]
- [20:39:21] Reencoding video [VID_00002]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 557 frames
- Bitrate: 1.424 Kbs
- [20:39:21] Reencoding: VID_00002, Pass 1 of 2
- [20:40:12] Reencoding: VID_00002, Pass 2 of 2
- [20:40:49] Video Encode complete
- [20:40:49] PredictAndEncode() 00053 2809
[20:40:56] - Aborted by user request
----------------------
[08.12.20] BD Rebuilder v0.61.10
[20:40:59] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:41:01] PHASE ONE, Encoding
- [20:41:01] Processing: VID_00002 (3 of 4)
- [20:41:01] Processing audio tracks
- [20:41:01] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00002.meta
- Can't open file: Q:\4K\WORKFILES\VID_00002.AVS.hevc
[20:41:05] - Failed to build structure, aborted
----------------------
[08.12.20] BD Rebuilder v0.61.10
[20:41:22] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:41:23] PHASE ONE, Encoding
- [20:41:23] Processing: VID_00002 (3 of 4)
- [20:41:23] Multiplexing M2TS
- [20:41:27] Processing: VID_00003 (4 of 4)
- [20:41:27] Extracting A/V streams [VID_00003]
- [20:41:31] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 279 frames
- Bitrate: 2.160 Kbs
- [20:41:31] Reencoding: VID_00003, Pass 1 of 2
- [20:42:27] Reencoding: VID_00003, Pass 2 of 2
- [20:43:18] Video Encode complete
- [20:43:18] PredictAndEncode() 00053 2809
[20:43:21] - Aborted by user request
----------------------
[08.12.20] BD Rebuilder v0.61.10
[20:43:30] Source: SONNTAG_IN_NEW_YORK_1963_1080P
- Input BD size: 29,48 GB
- Approximate total content: [01:48:22.412]
- Target BD size: 4,41 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- HEVC/V3 mode for BD disc enabled
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
- Resuming from previously started job.
[20:43:31] PHASE ONE, Encoding
- [20:43:31] Processing: VID_00003 (4 of 4)
- [20:43:31] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [20:43:32] Multiplexing M2TS
[20:43:35]PHASE ONE complete
[20:43:35]PHASE TWO - Rebuild Started
- [20:43:35] Rebuilding BD file Structure
[20:43:36] - Encode and Rebuild complete
[20:43:36] Writing BD structure to ISO file
- ImgBurn completed successfully
- SONNTAG_IN_NEW_YORK_1963_1080P folder removed.
- WORKFILES folder removed.
[20:43:47] JOB: SONNTAG_IN_NEW_YORK_1963_1080P finished.

The name of the encoded file is false. When I rename the file manually, BDRB works correct.

With directshow no problems.I don't think UHD_V3_MODE is ready for full backups yet. It's definitely only experimental -- and it should probably only be used experimentally for MOVIE-ONLY backups.

With that said -- I'll do some testing to see why the filename issue is popping up.

[gonca]

OK, after 2 days of testing, gradually removing paramters from the stax-string and then adding the parameters from the BDRB string (which I should have done the other way around, because I found it on the second-to-last parameter :mad:) the cause for the flickering is found ...
If the --pic-struct is removed from the command line string, the file plays fine.

But I also noticed, some scenes are WAY to dark on my TV.
A file with intact video (vFormat=8 in the alternate.txt) on the other hand is bright in the same scenes.
I'll do some more testing to find the cause for that...

Well done

[cartman0208]

Thanks! Your help is very much appreciated -- I had no way of testing it myself.

[Edit] I went back through requirements of the BD standard information that I have to see when the pic-structure is needed, and I think removing that parameter will be ok.

I'll try to get my hands on a HDR10+ capable player, to see if the flicker is there when played from disk...
If not, then it might be enough if the parameter is removed in alternate output only.

What does this parameter do anyway? I read something about shutter timings :confused:

[gonca]

--pic-struct <integer>

Set the picture structure and emits it in the picture timing SEI message. Values in the range 0..12. See D.3.3 of the HEVC spec. for a detailed explanation. Required for HLG (Hybrid Log Gamma) signalling. Not signalled by default.
Not required for HDR10+

[jdobbs]

Not required for HDR10+I went through the spec -- and there are three conditions where it has to be used... none of which really apply to HEVC/UHD.

[gonca]

I was referring to x265 (HEVC)

[cartman0208]

After some more testing I'm pretty sure, that's an encoder thing ...

My TV is showing the HDR10+ logo when playing the intact file, which is bright, also the file encoded with x265 and metadata.

Same brightness on an encoded file, either x265 and nvenc (surprisingly), without HDR10+ metadata, TV then shows a HDR-Logo

A file encoded with nvencc plus metadata also shows the HDR10+ logo, but dark scenes are much too dark, barely visible... where in the same scene on the other files everything was distinguishable...

I tried playing with maxcll values, but that doesn't help either ... plus - I don't want to mess up the original settings

I even tried to set my TV to max backlight and brightness, still too dark

Any ideas what else I could try?

[jdobbs]

After some more testing I'm pretty sure, that's an encoder thing ...

My TV is showing the HDR10+ logo when playing the intact file, which is bright, also the file encoded with x265 and metadata.

Same brightness on an encoded file, either x265 and nvenc (surprisingly), without HDR10+ metadata, TV then shows a HDR-Logo

A file encoded with nvencc plus metadata also shows the HDR10+ logo, but dark scenes are much too dark, barely visible... where in the same scene on the other files everything was distinguishable...

I tried playing with maxcll values, but that doesn't help either ... plus - I don't want to mess up the original settings

I even tried to set my TV to max backlight and brightness, still too dark

Any ideas what else I could try?Does it look the same if you use the "copy" feature in the command line (with NVENCC) instead of the JSON reference?

I wish I could help, but I have no equipment that has the ability to playback HDR10+.

[cartman0208]

Does it look the same if you use the "copy" feature in the command line (with NVENCC) instead of the JSON reference?

I wish I could help, but I have no equipment that has the ability to playback HDR10+.


Yep, "copy" or using the JSON file gives the same negative result...

The file is extracted with
ffmpeg -i "input.m2ts" -c:v copy -vbsf hevc_mp4toannexb -f hevc - | hdr10plus_parser.exe -o metadata.json -

Correct?

Problem might be, that rigaya does not have the equipment either. I think I'll post an issue on his github page.

I suggest to disable the feature by default and only enable it optional... until the root cause is found.

[jdobbs]

Yep, "copy" or using the JSON file gives the same negative result...

The file is extracted with
ffmpeg -i "input.m2ts" -c:v copy -vbsf hevc_mp4toannexb -f hevc - | hdr10plus_parser.exe -o metadata.json -

Correct?

Problem might be, that rigaya does not have the equipment either. I think I'll post an issue on his github page.

I suggest to disable the feature by default and only enable it optional... until the root cause is found.Yes. The JSON file is extracted with that command line -- it actually comes from the hdr10plus_parser.exe documentation (https://github.com/quietvoid/hdr10plus_parser).

Yeah. I'll do that.

The NVENCC documentation does say the "copy" option is "experimental". Interestingly it doesn't say that about --dhdr10-info with the JSON file.

You mentioned that x265 looks ok without the metadata. Have you tried an X265 encode using the JSON file?

[cartman0208]

Yes. The JSON file is extracted with that command line -- it actually comes from the hdr10plus_parser.exe documentation (https://github.com/quietvoid/hdr10plus_parser).

Yeah. I'll do that.

The NVENCC documentation does say the "copy" option is "experimental". Interestingly it doesn't say that about --dhdr10-info with the JSON file.

You mentioned that x265 looks ok without the metadata. Have you tried an X265 encode using the JSON file?

Yes, that works well with BDRB:
"V:\BD_Rebuilder\tools\ffmpeg.exe" -probesize 100MB -i "V:\FULLDISC\BOHEMIAN_RHAPSODY\BDMV\STREAM\00685.m2ts" -an -pix_fmt yuv420p10le -f yuv4mpegpipe -strict -1 - | "V:\BD_Rebuilder\tools\x265-64.exe" - --preset ultrafast --profile main10 --uhd-bd --repeat-headers --vbv-bufsize 45000 --vbv-maxrate 48000 --hdr --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50)" --dhdr10-info "V:\OUTPUT\WORKFILES\VID_00685.JSON" --fps 23.976 --slow-firstpass --qpfile "V:\OUTPUT\WORKFILES\VID_00685.CHP" --keyint 24 --crf 30 --y4m --stats "V:\OUTPUT\WORKFILES\VID_00685.AVS.hevc.stats" --output "V:\OUTPUT\WORKFILES\VID_00685.AVS.hevc"


That one is unaltered from LASTCMD, brightness is right and also comes without flicker.

[jdobbs]

Yes, that works well with BDRB:


That one is unaltered from LASTCMD, brightness is right and also comes without flicker.Ahh so that makes it clear that the issue is within NVENCC.

Thanks.

I'll do a couple encodes with each encoder and then look at the SEI extension data in the HEVC files to see what differences I can find.

I think if I can get past that one, I'm ready for a new release (a real one rather than test version).

[MrVideo]

This is a capability question. As you know, I've created BDs with 1080p H.264 videos, with menus. Can 1080p HEVC videos be used in the same way to create UHD formatted BDs with menus? The video is not to be upscale recoded to 4K, but left as 1080p.

[jdobbs]

This is a capability question. As you know, I've created BDs with 1080p H.264 videos, with menus. Can 1080p HEVC videos be used in the same way to create UHD formatted BDs with menus? The video is not to be upscale recoded to 4K, but left as 1080p.I'm working on that. Right now my plan is for the menus themselves to stay H.264/1080p, but the videos accessed via the menu would be HEVC at 1080p.

I will include a hidden switch that would allow 720p and SD to be encoded to HEVC as well. That wouldn't be inline with the BD specification -- but I think most if not all UHD players will handle it (mine does). It would make it nice for creating disc backups of things like SD series. It could give the better quality of HEVC at low bitrates when you put a large number of episodes on a single disc.

[MrVideo]

I'm working on that.
I look forward to it. Thanks.

[jdobbs]

I look forward to it. Thanks.Well... a new glitch thrown into the mix. The way I'd tested this previously was by muxing with the old version of TSMUXER and then correcting the stream from within BD-RB. Slow as molasses.

I had assumed that the new UHD capable version of TSMUXER would mux a 1080p source correctly -- easy peasy.

Well, I've done two attempts so far today (both using NVENCC) and TSMUXER has failed to mux them. No error message, no warning, no failure indicator. It just stops.

Honestly this whole thing is getting tiresome. I've had to write code for so many "exceptions" in the helper apps that BD-RB has more code dedicated to bypassing mistakes or implementing workarounds than it has actually doing its job.

I'm trying an encode using X265 now to see if it fares any better.

[MrVideo]

Well, I've done two attempts so far today (both using NVENCC) and TSMUXER has failed to mux them. No error message, no warning, no failure indicator. It just stops.
I don't have the right card to take advantage of NVENCC. I'm waiting for the newest series to be released, for better I/P/B frame support.
I'm trying an encode using X265 now to see if it fares any better.
I'm hoping that the HEVC in the MKV files will pass muster and be usable without recoding. But, my luck normally means... nope.

[jdobbs]

I don't have the right card to take advantage of NVENCC. I'm waiting for the newest series to be released, for better I/P/B frame support.

I'm hoping that the HEVC in the MKV files will pass muster and be usable without recoding. But, my luck normally means... nope.Yeah. It's rare that an MKV doesn't have a huge (240 frame or so) GOP.

[jdobbs]

I don't have the right card to take advantage of NVENCC. I'm waiting for the newest series to be released, for better I/P/B frame support.

I'm hoping that the HEVC in the MKV files will pass muster and be usable without recoding. But, my luck normally means... nope.Ok. I found out that X265 was working fine on the 1080p source. So I did some checking with my HEVC browser. It turns out that the issue was caused by the removal of the "--pic-struct" command line parameter in response to a bug report by cartman0208 related to HDR10+. Without that parameter the new UHD TSMUXER got totally confused and bailed on a 1080p source.

I went back in and made changes so the parameter was removed only for HDR10+ sources. But given the other reported issues with NVENCC and HDR10+, I may have to just remove HDR10+ support completely for NVENCC until it is fixed anyway.

[cartman0208]

I opened an issue at the NVENCC Github page regarding dark scenes.
Should I address the --pic-struct issue also? Could be related...

[jdobbs]

I opened an issue at the NVENCC Github page regarding dark scenes.
Should I address the --pic-struct issue also? Could be related...You might want to mention it. There seems to be a connection -- and it might help put a finger on the problem.

[cartman0208]

You might want to mention it. There seems to be a connection -- and it might help put a finger on the problem.

Did that ... I also added some captures I did with my mobile phone to see the differences

[jdobbs]

Did that ... I also added some captures I did with my mobile phone to see the differencesIn browsing the HEVC streams from X265 and NVENCC -- there is one thing that stands out:

1. In the X265 encoded HEVC file there are two SEI prefixes added:

One SEI that contains the content light level
One SEI that contains the display mastering information

2. In the NVENCC there is only one SEI prefix that contains:

Content light level, followed by display mastering information.

3. In the original (from the authored disc) there are also two SEI prefixes present:

One SEI that contains the content light level
One SEI that contains the display mastering information

4. It also appears that both X265 and the original add the two SEIs to every IDR frame (even if they don't change) -- while NVENCC doesn't (I assume it only changes it at what it thinks are scene changes... but I'm not sure).


Since both the original and X265 streams seem to be working... I suspect that the problem is centered around the attempt to combine both types of information into a single SEI.

I'm nowhere near an expert on how these SEIs should be implemented -- but this information might be helpful to add to your bug report.

[cartman0208]

I'm nowhere near an expert on how these SEIs should be implemented -- but this information might be helpful to add to your bug report.

Well, since I'm even farther away ... feel free to add it :)

[MrVideo]

Yeah. It's rare that an MKV doesn't have a huge (240 frame or so) GOP.
That isn't the fault of MKV, but with the person who set the encoding options.

For one show, a quick glance showed 250 frames from one IDR to the next. Another show wasn't as bad, but still normally more than 50.

To be UHD disc compliant, what should the maximum be?

[jdobbs]

That isn't the fault of MKV, but with the person who set the encoding options.

For one show, a quick glance showed 250 frames from one IDR to the next. Another show wasn't as bad, but still normally more than 50.

To be UHD disc compliant, what should the maximum be?From the UHD Part 3, v3.1 Whitepaper:

[cartman0208]

jdobbs: do you have plans to change the "browse for folder" interfaces (behind the "Browse" buttons in the main interface) so they look like the one for "import file" ?

I'd love to sort the folders by age when browsing :)

[jdobbs]

jdobbs: do you have plans to change the "browse for folder" interfaces (behind the "Browse" buttons in the main interface) so they look like the one for "import file" ?

I'd love to sort the folders by age when browsing :)No plans right now. Browsing for a file and browsing for a folder involve two different system calls in Windows. But I'll look at it and see if it's possible.

[jdobbs]

I opened an issue at the NVENCC Github page regarding dark scenes.
Should I address the --pic-struct issue also? Could be related...I was hoping this might be a quick fix, especially after I noted the differences... but it doesn't look like it is getting any attention at all.

I could probably write code to make this fix myself, but I'd hesitated since the last time I did that a fix was made a couple days later. Another reason for hesitating is that it will add time (since I'd have to scan and rewrite the entire HEVC file after the encode is done).

[cartman0208]

I was hoping this might be a quick fix, especially after I noted the differences... but it doesn't look like it is getting any attention at all.

I could probably write code to make this fix myself, but I'd hesitated since the last time I did that a fix was made a couple days later. Another reason for hesitating is that it will add time (since I'd have to scan and rewrite the entire HEVC file after the encode is done).

I would wait ... several days with no contribution or blog activity ... maybe rigaya is on vacation ?

[jdobbs]

I have updated the first post of this thread with a link to the latest version (v0.61.12) of BD Rebuilder. Cumulative changes for this release (since the last public release):- This list includes changes made since the
last public release (v0.61.05).
- Added support for NVIDIA NVENC encoding.
- Corrected an error that could cause BD-RB
to exit in failure when attempting a size-
correcting second pass in CRF mode while
doing a UHD backup.
- Added code that will update the HDR flags
in the MPLS file for sources in which HDR
was not established until after reencoding
on full backups.
- Fixed an error in which MPEG2 sources may
not make video adjustments detected during
import when reencoding. This could result
in stretched or compressed images.
- Created a workaround for a problem with
converting PAL to NTSC flags during import
which could confuse TSMUXER's recognition
of video resolution.
- Added code to adapt to UHD sources that are
not sized to either 3840(h) or 2160(v).
- Corrected an issue in which video sources
that are an odd size during import might
use the wrong resizing when HEVC encoding
is enabled.
- Fixed a bug in which large audio offsets
detected during import were not being
interpreted correctly.
- Fixed a bug that could cause undersizing
when an AC3 stream is kept intact because
the original is smaller than the selected
reencoder bitrate. This typically only
happens on DVD imports.
- Fixed an error that could result in wrong
aspect ratio on imported sources that are
being resized.
- Corrected an issue in which some command
line settings were not being set when a
non-UHD source is output as V3.
- Added a routine to ensure formatting of
CRF values consistent.
- Updated CQM prediction routines.
- Fixed an issue that can cause the CQM/CRF
sample file to have a zero length when
used in other-than-US regions.
- Modified NVENCC options to eliminate vbrhq
from the command line, as it is targeted
to be deprecated. Replaced by "vbr" and
manually enabling "--multipass 2pass-full"
(the newer equivalent of vbrhq).
- Rewrote the "Bitstream Exception" TSMUXER
error workaround routine so it now uses
a more efficient method -- and better
adjusts audio sync. It also now adjusts
for Dolby Vision exception errors.
- Fixed an issue in which BT709 sources were
not being encoded with proper settings.
- Increased the accepted value of the THREADS
hidden option from 16 to 128. Note: While
128 is accepted for x264 -- realistically
you should never set it that high.
- Added support for HDR10+ in X265 encoding
and experimental (needs testing) support
for NVENCC. A JSON file is created con-
currently with video extraction. HDR10+
streams are now identified in the streams
list by a "+" next to "HEVC". Note that "*"
indicates Dolby Vision. "*+"=both. To enable
experimental support in NVENCC, as the
hidden value NVENC_ENABLE_10PLUS=1 to your
BDREBUILDER.INI file.
- Corrected an error that would result in
only 48 frames being encoded during CRF
prediction when using X265.
- Changed the ALTERNATE settings so creating
a preset that outputs HEVC to MP4 is now
allowed.
- Fixed an issue that could result in an
error "ExtractAudioSubs() 00058 1605".
- Fixed a problem that could cause multipart
sources to fail during rebuild when
outputting to ALTERNATE choices.
- Implemented a method by which a different
background image could be used for multpage
menus. Menu pages 2-x can be changed by
adding additional file(s) into the same
folder as the initial background image.
Example: If the background image is called
"BACKGROUND.JPG". You can us another
image for page 2 by creating an image called
"BACKGROUND_2.JPG" (page 3=BACKGROUND_3.JPG)
etc.
- Updated the included version of MP4BOX to
support HEVC.
- Updated the included versions of X265 to a
newer (v3.2.1) release.
- Other minor corrections and cosmetic fixes.

[meadrocks]

Ran Howls Moving Castle w/ the new version, same problem. I'll try with a mp4 container.


$ mediainfo HOWLS_MOVING_CASTLE.mkv
General
Unique ID : 221294904985475506127951980034512522439 (0xA67BD931150DAFE18584E1C6A43E0CC7)
Complete name : HOWLS_MOVING_CASTLE.mkv
Format : Matroska
Format version : Version 2
File size : 2.44 GiB
Duration : 3 h 53 min
Overall bit rate : 1 495 kb/s
Encoded date : UTC 2020-08-21 06:17:34
Writing application : mkvmerge v9.7.1 ('Pandemonium') 32bit
Writing library : libebml v1.3.4 + libmatroska v1.4.5

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 h 59 min
Bit rate : 2 611 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.053
Stream size : 2.18 GiB (89%)
Writing library : x265 3.2.1+3-b4b2ecac21f6:[Windows][GCC 9.2.0][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=3 / numa-pools=8 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 /
input-res=1920x1080 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud /
no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=240 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 /
rc-lookahead=20 / lookahead-slices=6 / scenecut=40 / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 /
tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra /
strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / no-hme / weightp / no-weightb /
no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=3 / selective-sao=4 / early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless /
b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=23.7 / qcomp=0.60 /
qpstep=4 / stats-write=0 / stats-read=0 / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 /
no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=2 / transfer=2 / colormatrix=2 / chromaloc=0 /
display-window=0 / cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps /
no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-hdr / no-hdr-opt / no-dhdr10-opt /
no-idr-recovery-sei / analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao /
ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt /
no-field / qp-adaptation-range=1.00
Default : Yes
Forced : No

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : A_AAC-2
Duration : 1 h 59 min
Bit rate : 277 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 237 MiB (9%)
Language : English
Default : Yes
Forced : No

Text #1
ID : 3
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 3 h 49 min
Bit rate : 10.8 kb/s
Count of elements : 2845
Stream size : 17.7 MiB (1%)
Language : English
Default : No
Forced : No

Text #2
ID : 4
Format : PGS
Muxing mode : zlib
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 3 h 53 min
Bit rate : 7 807 b/s
Count of elements : 2062
Stream size : 13.0 MiB (1%)
Language : English
Default : No
Forced : No

Menu
00:00:00.000 : en:00:00:00.000
00:01:09.069 : en:00:01:09.069
00:05:03.302 : en:00:05:03.302
00:12:27.037 : en:00:12:27.037
00:18:27.397 : en:00:18:27.397
00:23:21.691 : en:00:23:21.691
00:28:56.025 : en:00:28:56.025
00:33:18.287 : en:00:33:18.287
00:40:14.703 : en:00:40:14.703
00:45:35.023 : en:00:45:35.023
00:49:20.248 : en:00:49:20.248
00:55:30.618 : en:00:55:30.618
00:58:36.804 : en:00:58:36.804
01:04:58.185 : en:01:04:58.185
01:10:58.545 : en:01:10:58.545
01:15:28.815 : en:01:15:28.815
01:20:30.116 : en:01:20:30.116
01:25:26.412 : en:01:25:26.412
01:32:35.841 : en:01:32:35.841
01:38:39.204 : en:01:38:39.204
01:44:26.551 : en:01:44:26.551
01:48:27.792 : en:01:48:27.792
01:52:24.028 : en:01:52:24.028
01:54:43.209 : en:01:54:43.209
01:59:27.201 : en:01:59:27.201

[MrVideo]

I have updated the first post of this thread with a link to the latest version (v0.61.12) of BD Rebuilder. Cumulative changes for this release (since the last public release):
- Implemented a method by which a different
background image could be used for multpage
menus. Menu pages 2-x can be changed by
adding additional file(s) into the same
folder as the initial background image.
Example: If the background image is called
"BACKGROUND.JPG". You can us another
image for page 2 by creating an image called
"BACKGROUND_2.JPG" (page 3=BACKGROUND_3.JPG)
etc.
Somehow I missed that new feature. I like it and will be using it. Thanks.

[jdobbs]

@meadrocks

I notice that the source is 1920x1080. Was it imported into BD-RB, or was it from a BD disc?

[meadrocks]

@meadrocks

I notice that the source is 1920x1080. Was it imported into BD-RB, or was it from a BD disc?

The source is a BD disk.

When making a mp4 I get an "ERROR in attempt to mux (MP4BOX)"

Trying Watchmen DC disk now.

[jdobbs]

The source is a BD disk.

When making a mp4 I get an "ERROR in attempt to mux (MP4BOX)"

Trying Watchmen DC disk now.Are you sure you are using the new version -- including the helper files that are included with the new version?

I didn't make any changes to affect the subtitles -- but I did multiple tests with MP4BOX without error.

By "Watchmen DC" are you referring to the Directors Cut (DC)?

[jdobbs]

Updated the first post of this thread with a new version (v0.61.13) of BD Rebuilder. Changes for this release:

This is nothing more than a recompile of v0.61.12. Apparently some antivirus software was (incorrectly) flagging BD-RB.EXE. Changing the version number seems to have "fixed" it. Just another antivirus false positive. Go figure.

I've also updated the v0.61.12 zip file so it downloads v0.61.13. The last thing I need is people driving me crazy with reports of false positives from antivirus mistakes.

[meadrocks]

Are you sure you are using the new version -- including the helper files that are included with the new version?

I didn't make any changes to affect the subtitles -- but I did multiple tests with MP4BOX without error.

By "Watchmen DC" are you referring to the Directors Cut (DC)?

Yes Watchmen Dir Cut. its 186 minutes long. Both of these BD disks (Howls Moving Castle & Watchmen Dir Cut) are multi part.

[meadrocks]

Yes Watchmen Dir Cut. its 186 minutes long. Both of these BD disks (Howls Moving Castle & Watchmen Dir Cut) are multi part.

Heres the Input file.


[Status]
LABEL=WATCHMEN
VERSION=v0.61.12
SOURCE_SIZE=35145842688
SOURCE_VIDEO_SIZE=35145842688
TARGET_SIZE=4686086144
REDUCTION=.133332587458487
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=all
BACKUP_MODE=1
MOVIEONLY_TYPE=41
USE_LAVF=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
UHD_V3_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=25
REBUILD_COMPLETE=0
[00500]
AUDIO=100
PGS=100010
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=268696
NSIZE=0
FLINK=-1
MLINK=0
[00501]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=15032236
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00502]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=57589438
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00503]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=78818887
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00504]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=378957342
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00505]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=69512008
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00506]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=574395251
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00507]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=65900995
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00508]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=134614287
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00509]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=45525147
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00510]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=94264817
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00511]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=65805968
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00512]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=597088602
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00513]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=56924251
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00514]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=802112735
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00515]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=93446440
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00516]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=473949605
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00517]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=69221194
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00518]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=334745366
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00519]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=69143370
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00520]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=87712073
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00521]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=64320767
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00522]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=366298316
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00523]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=90352339
AUDIO=100
NSIZE=0
FLINK=-1
MLINK=0
[00524]
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=86016
AUDIO=100
NSIZE=0
FLINK=0
MLINK=0



Heres the output file.


----------------------
[08/21/20] BD Rebuilder v0.61.12
[08:05:09] Source: WATCHMEN_00100
- Input BD size: 32.73 GB
- Approximate total content: [03:06:28.385]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MP4 Container, HEVC 1920x1080, Auto-AAC
- Quality: High Quality (Default)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[08:05:09] PHASE ONE, Encoding
- [08:05:09] Processing: VID_00500 (1 of 25)
- [08:05:09] Extracting A/V streams [VID_00500]
[08:05:40]PHASE ONE aborted by user request
----------------------
[08/21/20] BD Rebuilder v0.61.12
[08:06:43] Source: WATCHMEN_00100
- Input BD size: 32.73 GB
- Approximate total content: [03:06:28.385]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MP4 Container, HEVC 1920x1080, Auto-AAC
- Quality: High Quality (Default)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[08:06:46] PHASE ONE, Encoding
- [08:06:46] Processing: VID_00500 (1 of 25)
- [08:06:46] Extracting A/V streams [VID_00500]
- [08:11:41] Reencoding video [VID_00500]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 96 frames
- [08:11:41] Reencoding: VID_00500, Pass 1 of 1
- Analyzing 43.95 24.40 1.00 [1.00]
- [08:11:51] Video Encode complete
- [08:11:51] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AAC...

snip

- [14:51:53] Processing: VID_00524 (25 of 25)
- [14:51:53] Extracting A/V streams [VID_00524]
- [14:51:57] Reencoding video [VID_00524]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 29 frames
- [14:51:57] Reencoding: VID_00524, Pass 1 of 1
- Analyzing 42.60 25.00 14.60 1.00 [1.00]
- [14:52:05] Video Encode complete
[14:52:05]PHASE ONE complete
[14:52:05]PHASE TWO - Rebuild Started
- [14:52:05] Building ALTERNATE OUTPUT Structure
- ERROR in attempt to mux (MP4BOX)
[14:54:35] - Failed to REBUILD

[Ch3vr0n]

Just a quick question. I don't see a mentioning of updated FRIM. Is it still the "old" one or the new one that supposedly fixes pixellation issues on 3D for software players?

[jdobbs]

Just a quick question. I don't see a mentioning of updated FRIM. Is it still the "old" one or the new one that supposedly fixes pixellation issues on 3D for software players?Sorry, but I haven't updated it yet. I haven't had time to test it. By testing I mean making sure that it still works the same and doesn't cause other issues. I can't test the pixellation issue since it doesn't happen to me.

[Ch3vr0n]

Yeah no worries, I'll see it updated when it gets updated. Was just a question

Sent from my Pixel 3 XL using Tapatalk

[jdobbs]

Weird. Yesterday someone indicated that their antivirus software was give a hit on BD-RB. This wasn't the first time I'd gotten a false negative in a new release. I ran a scan with AVG (the AV software I use) and it also showed it. So I recompiled and what I assume was a false negative went away. I packed the new compile into a ZIP file and posted it for download. I even downloaded it and ran the test again. No problem.

Now today that user told me he got it again, and sure enough, AVG showed it too -- and it also found something else in the FRIMSource.dll. Huh? There'd been a virus database update earlier. I scanned my entire system -- nothing found. But I've blocked the downloads until I do some more in-depth checking.

A long time ago I put special code in BD-RB that performs a checksum at startup and it exits with a warning if the EXE has been modified. It also is protected via EXE compression (from reverse engineering) so it would be very hard for malware to "attach" itself to it. So I have to assume another false negative, FRIMSource.dll hasn't changed in years. But it is getting annoying.

The two hits were with AVG and AVAST -- can someone scan the new version of BD-RB with another A/V checker and see if it gets an all-clear?

[musiclover]

All files in the BD_Rebuilder v0.61.13 folder are getting the all-clear from Malwarebytes

[MajorEvent]

All clear with Malwarebytes and Windows Defender both .zip and extracted with BD-RBV06112

[jdobbs]

Thanks. Yeah, the odds are high that it's another false positive. It's happened before. Sometimes A/V software can be just as bad as the things they are designed to protect you against.

Anyone else?

[prologic]

can not download from the main site, re-direction .. not working here .

[raul124]

first page redirected me to this
https://jammernhilftnichts.de/jdobbs/BD-RBV06113.zip

[jdobbs]

Sorry, I blocked it until it could be tested by a few different packages. Try this link (https://jammernhilftnichts.de/jdobbs/BD-RBV06113-keep.zip).

Thanks,