BD Rebuilder Beta - Bug Reports Only

[dietachi]

@dietachi

I'll work on it. As you know, I don't have a VCEEnc GPU for testing. Of the options available to replace "--vpp-deinterlace", which do you think generates the best looking output?

I'm inclined to go with "-vpp-decomb" since the others appear to throw away one field and regenerate it from the kept field. But I have seen instances where that actually looks better...


I will try to run some tests, but I can only do so after this Thursday.

When I had a look at the output videos after the encodes.
For this video "--vpp-decomb" was good.

I noticed in the past that "--vpp-afs" can cause some problems depending on the source file.

[jdobbs]

I will try to run some tests, but I can only do so after this Thursday.

When I had a look at the output videos after the encodes.
For this video "--vpp-decomb" was good.

I noticed in the past that "--vpp-afs" can cause some problems depending on the source file.I'll just go ahead and replace it with "--vpp-decomb". If it appears to have issues later, we can always address it again.

[jdobbs]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.62.12). Changes for this release:- Corrected an issue in which encoding can
fail while using the VCEENCC (AMD) GPU
encoder if encoding 720x480 interlaced
sources and deinterlacing is enabled.
- Fixed an error in which VC-1 sources were
failing to encode while using the VCEENCC
(AMD) GPU encoder.
- Other minor corrections and cosmetic fixes.

[jdobbs]

I will try to run some tests, but I can only do so after this Thursday.

When I had a look at the output videos after the encodes.
For this video "--vpp-decomb" was good.

I noticed in the past that "--vpp-afs" can cause some problems depending on the source file.I just thought I'd share something I just discovered. If you are encoding a source that is VC-1 using QSVEnc (Intel GPU), the speed of the encode is slower than what you might typically see because of the change to to "--avsw".

I found that forcing the encoder to use AVISYNTH and "--avs" as a source is actually faster -- almost twice as fast on my system.

There is a hidden setting NVENC_FORCE_AVS=1 that can be used. While it appears (by the name) to be applied only to NVEnc, it just so happens that it is applied across all three GPU encoders. So if you have a heavily VC-1 source, and are in a hurry, you might save yourself some encoding time by adding it to BDREBUILDER.INI's "[Options]" area just before the encode.

I'm not sure if the speed increase is also the case when using VCEEnc, as I'm not able to test it. It would be interesting to find out.

Of course you'd also have to remember to remove or disable that hidden setting when you are doing non-VC-1 sources -- as "--avhw" is likely significantly faster than using AVS mode.

[dietachi]

I just thought I'd share something I just discovered. If you are encoding a source that is VC-1 using QSVEnc (Intel GPU), the speed of the encode is slower than what you might typically see because of the change to to "--avsw".

I found that forcing the encoder to use AVISYNTH and "--avs" as a source is actually faster -- almost twice as fast on my system.

There is a hidden setting NVENC_FORCE_AVS=1 that can be used. While it appears (by the name) to be applied only to NVEnc, it just so happens that it is applied across all three GPU encoders. So if you have a heavily VC-1 source, and are in a hurry, you might save yourself some encoding time by adding it to BDREBUILDER.INI's "[Options]" area just before the encode.

I'm not sure if the speed increase is also the case when using VCEEnc, as I'm not able to test it. It would be interesting to find out.

Of course you'd also have to remember to remove or disable that hidden setting when you are doing non-VC-1 sources -- as "--avhw" is likely significantly faster than using AVS mode.


Thank you for the information.
I will test this with VCEEnc and QSVEnc where both GPUs are in the same machine.
The disc I have to test is all mixed codec and interlaced and progressive for extras etc, while the main title is AVC.
Once done I'll report back.

[Intel Iris the Great]

I just thought I'd share something I just discovered. If you are encoding a source that is VC-1 using QSVEnc (Intel GPU), the speed of the encode is slower than what you might typically see because of the change to to "--avsw".

I found that forcing the encoder to use AVISYNTH and "--avs" as a source is actually faster -- almost twice as fast on my system.

There is a hidden setting NVENC_FORCE_AVS=1 that can be used. While it appears (by the name) to be applied only to NVEnc, it just so happens that it is applied across all three GPU encoders. So if you have a heavily VC-1 source, and are in a hurry, you might save yourself some encoding time by adding it to BDREBUILDER.INI's "[Options]" area just before the encode.

I'm not sure if the speed increase is also the case when using VCEEnc, as I'm not able to test it. It would be interesting to find out.

Of course you'd also have to remember to remove or disable that hidden setting when you are doing non-VC-1 sources -- as "--avhw" is likely significantly faster than using AVS mode.

Yeah I noticed too that the VC-1 encode was much slower than an MPEG-4 encode using QSVEnc. Well it's already done now, but for now I won't be using VC-1 anytime soon. Thanks for the clarification though.

As for speed on my system, the QSVEnc GPU encoder runs over 3x faster than DirectShow CPU encoder for MPEG-4 encodes, so that's quite a significant increase !!

[dietachi]

I just thought I'd share something I just discovered. If you are encoding a source that is VC-1 using QSVEnc (Intel GPU), the speed of the encode is slower than what you might typically see because of the change to to "--avsw".

I found that forcing the encoder to use AVISYNTH and "--avs" as a source is actually faster -- almost twice as fast on my system.

There is a hidden setting NVENC_FORCE_AVS=1 that can be used. While it appears (by the name) to be applied only to NVEnc, it just so happens that it is applied across all three GPU encoders. So if you have a heavily VC-1 source, and are in a hurry, you might save yourself some encoding time by adding it to BDREBUILDER.INI's "[Options]" area just before the encode.

I'm not sure if the speed increase is also the case when using VCEEnc, as I'm not able to test it. It would be interesting to find out.

Of course you'd also have to remember to remove or disable that hidden setting when you are doing non-VC-1 sources -- as "--avhw" is likely significantly faster than using AVS mode.

AVS vs. AVSW Encoding Performance Comparison

This comparison evaluates the encoding performance difference between using the --avs option and the --avsw option with two different GPU setups, using specific quality and preset settings for each encoder.

QSVEnc Settings: --quality fastest
VCEEnc Settings: --preset fast

Test Setup 1: QSVEnc with Intel Arc A770 Graphics
CPU: AMD Ryzen 9 5950X 16-Core Processor [4.99GHz] (16C/32T)
GPU Info: Intel Arc A770 Graphics (512EU) 300-2400MHz (32.0.101.5768)

Video Source: VC-1 - 1920x1080

With --avs: Encoded 15,456 frames at 435.87 fps, 5616.79 kbps, 431.64 MB.

With --avsw: Encoded 15,456 frames at 145.93 fps, 5616.78 kbps, 431.64 MB.

Result: The --avs option was approximately 3 times faster than --avsw .

Test Setup 2: VCEEnc with AMD Radeon RX 7600
CPU: AMD Ryzen 9 5950X 16-Core Processor [4.99GHz] (16C/32T)
GPU: AMD Radeon RX 7600 [32.0.11029.1008]

Video Source: VC-1 - 1920x1080

With --avs: Encoded 15,456 frames at 304.35 fps, 9550.10 kbps, 733.90 MB.

With --avsw: Encoded 15,456 frames at 121.79 fps, 9550.10 kbps, 733.90 MB.

Result: The --avs option was approximately 2.5 times faster than --avsw.

In summary, for VC-1 1920x1080 video decoding, the --avs option is notably faster than --avsw, achieving up to 3 times the speed depending on the system configuration.

[dietachi]

I have updated the first post of this thread with a link to the latest version of BD-RB (v0.62.12). Changes for this release:- Corrected an issue in which encoding can
fail while using the VCEENCC (AMD) GPU
encoder if encoding 720x480 interlaced
sources and deinterlacing is enabled.
- Fixed an error in which VC-1 sources were
failing to encode while using the VCEENCC
(AMD) GPU encoder.
- Other minor corrections and cosmetic fixes.

I have tested both fixes and can confirm that they are working fine.

[dietachi]

AVHW vs. AVS Encoding Performance Comparison

This comparison evaluates the encoding performance of --avhw versus --avs for an AVC 1920x1080 video source across two different GPU configurations.

Test Setup 1: VCEEnc with AMD Radeon RX 7600
CPU: AMD Ryzen 9 5950X 16-Core Processor [4.92GHz] (16C/32T)
GPU: AMD Radeon RX 7600 [32.0.11029.1008]

With --avhw: Encoded 16,001 frames at 285.68 fps, 19526.57 kbps, 1553.48 MB.

With --avs: Encoded 16,001 frames at 190.26 fps, 19526.57 kbps, 1553.48 MB.

Result: The --avhw option was around 1.5 times faster than --avs on the AMD Radeon RX 7600.

Test Setup 2: QSVEnc with Intel Arc A770 Graphics
CPU: AMD Ryzen 9 5950X 16-Core Processor [4.92GHz] (16C/32T)
GPU: Intel Arc A770 Graphics (512EU) 300-2400MHz (32.0.101.5768)

With --avhw: Encoded 16,001 frames at 479.16 fps, 19960.55 kbps, 1588.01 MB.

With --avs: Encoded 16,001 frames at 304.42 fps, 19966.33 kbps, 1588.47 MB.

Result: The --avhw option was around 1.6 times faster than --avs on the Intel Arc A770 Graphics.

[jdobbs]

@dietachi

Thanks for the testing and feedback. It's good to know that my experience wasn't an anomaly.

I think I may go in and change the default encoding to "--avs" for QSVEnc and VCEEnc when VC-1 is the source. That way the user won't have to add and remove "NVENC_FORCE_AVS=1" from their BDREBUILDER.INI file to get the faster speeds.

[jdobbs]

For anyone who may be interested, I've done some testing to compare what can give similar results across three of the HEVC encoders available through BD-RB (X265, QSVEncc, and NVEncc). Using a source that combines parts (using the BD-RB prediction sampling algorithm) of several different types of movies, I ran each encoder using its version of constant quality encoding. This way, if you have been using one encoder and want to try another -- you can see what value results in equivalent quality (per SSIM results), and what you might expect in terms of sizing.

Just as an additional note -- each of the GPU encoders is many, many times faster...X265 SSIM SIZE NVIDIA SSIM FILESIZE SIZE % INTEL SSIM FILESIZE SIZE %
CRF
NV_HEVC_11 0.99469 2735438211 QSV_HEVC_11 0.99492 2370988385
NV_HEVC_12 0.99448 2552227295
NV_HEVC_13 0.99401 2328739840 QSV_HEVC_12 0.99420 2151610991
11 0.99335 1949610802 NV_HEVC_14 0.99338 2122928050 108.88 QSV_HEVC_13 0.99337 1919639622 98.46
12 0.99262 1750487380 NV_HEVC_15 0.99244 1900798214 108.59 QSV_HEVC_14 0.99236 1686108802 89.79
13 0.99179 1566882823 NV_HEVC_16 0.99132 1688757477 107.78 QSV_HEVC_15 0.99134 1486820316 94.89
14 0.99082 1396060525
15 0.98977 1237639586 NV_HEVC_17 0.99009 1492524278 120.59 QSV_HEVC_16 0.99005 1289467174 104.19
16 0.98858 1087869492 NV_HEVC_18 0.98871 1310176603 120.44 QSV_HEVC_17 0.98864 1116438300 102.63
17 0.98712 939036774 NV_HEVC_19 0.98728 1148904500 122.35 QSV_HEVC_18 0.98702 960051106 102.24
18 0.98546 801110032 NV_HEVC_20 0.98584 1009198253 125.97 QSV_HEVC_19 0.98533 821968709 102.60
NV_HEVC_21 0.98436 885250807
19 0.98365 677460693 NV_HEVC_22 0.98282 772522049 114.03 QSV_HEVC_20 0.98337 690590341 101.94
20 0.98166 566939264 NV_HEVC_23 0.98117 666817944 117.62 QSV_HEVC_21 0.98144 583298263 102.89
21 0.97953 469052281 NV_HEVC_24 0.97950 573435830 122.25 QSV_HEVC_22 0.97931 481562861 102.67
22 0.97733 384487124 NV_HEVC_25 0.97791 493929976 128.46 QSV_HEVC_23 0.97716 394645310 102.64
NV_HEVC_26 0.97634 423749808 QSV_HEVC_24 0.97651 370217079
QSV_HEVC_25 0.97589 349571314
23 0.97510 312082984 NV_HEVC_27 0.97472 360136885 115.40 QSV_HEVC_26 0.97526 331796120 106.32
24 0.97293 251675944 NV_HEVC_28 0.97322 307347661 122.12 QSV_HEVC_27 0.97312 269137749 106.94
NV_HEVC_29 0.97173 261407806
25 0.97086 201981938 QSV_HEVC_28 0.97105 218090181 107.98
NV_HEVC_30 0.97027 222447802
26 0.96889 161696455 NV_HEVC_31 0.96877 187941863 116.23 QSV_HEVC_29 0.96899 174132836 107.69
27 0.96709 130308016 NV_HEVC_32 0.96730 158906997 121.95 QSV_HEVC_30 0.96703 141389351 108.50
28 0.96542 106218339 NV_HEVC_33 0.96580 134505532 126.63
QSV_HEVC_31 0.96489 112962058
29 0.96384 88090623 NV_HEVC_34 0.96434 114609022 130.10
30 0.96225 74482214 NV_HEVC_35 0.96279 97577670 131.01 QSV_HEVC_32 0.96299 92046174 123.58
31 0.96061 63853702 NV_HEVC_36 0.96118 83653349 131.01 QSV_HEVC_33 0.96143 79951128 125.21
32 0.95889 55398574 NV_HEVC_37 0.95954 72067442 130.09 QSV_HEVC_34 0.95938 67142107 121.20
33 0.95706 48562088 NV_HEVC_38 0.95776 62530064 128.76 QSV_HEVC_35 0.95721 57324572 118.04
34 0.95510 42844610 NV_HEVC_39 0.95583 54649663 127.55 QSV_HEVC_36 0.95506 49657159 115.90
35 0.95297 38016642 NV_HEVC_40 0.95368 47941203 126.11 QSV_HEVC_37 0.95286 43762369 115.11
36 0.95068 33822068 QSV_HEVC_38 0.95107 41276063 122.04
37 0.94826 30198276 QSV_HEVC_39 0.94866 36743861 121.68
38 0.94571 27011194 QSV_HEVC_40 0.94613 33191208 122.88
39 0.94304 24209378
40 0.94019 21764853Example: Let's say you had been using X265 with a CRF of 23 and like the results. By the table you could use QSVEncc using a ICQ value of 26 -- and get similar quality with about a 6% increase in output file size. If you chose to use NVEncc you could select 27 and get the same results with a 15% increase.

[Rich86]

Greetings to everyone!
I generally use ripping and conversion software very little these days.
I am still a physical media guy, and like to have a BD backup copy to go with my 4K/UHD disc when I make purchases these days.
Of course the providers (in their infinite wisdom) often skip providing a BD of the movie when providing the 4K/UHD disc.
In these cases, I rip the 4K/UHD disc to my hard drive and then create a BD copy of the movie to burn onto BDR media.
However, BDRB has been my goto software for many years, but lately I can no longer depend on it if I want to take advantage of my video card NVENC capabilities. It seems to always fail.
If I use different software, it seems to work fine. If anyone else runs into this and has an idea if I am doing something wrong, pls fill me in.
I remain forever grateful for jdobbs software endeavors and support.

[dietachi]

Greetings to everyone!
I generally use ripping and conversion software very little these days.
I am still a physical media guy, and like to have a BD backup copy to go with my 4K/UHD disc when I make purchases these days.
Of course the providers (in their infinite wisdom) often skip providing a BD of the movie when providing the 4K/UHD disc.
In these cases, I rip the 4K/UHD disc to my hard drive and then create a BD copy of the movie to burn onto BDR media.
However, BDRB has been my goto software for many years, but lately I can no longer depend on it if I want to take advantage of my video card NVENC capabilities. It seems to always fail.
If I use different software, it seems to work fine. If anyone else runs into this and has an idea if I am doing something wrong, pls fill me in.
I remain forever grateful for jdobbs software endeavors and support.



Hello,
could you please provide the following details?

Which GPU are you currently using?
Which driver version is installed for your GPU?
Which version of BD Rebuilder are you using?

Additionally, when BD Rebuilder fails at encoding, could you try opening the lastcmd.txt file located in the BD Rebuilder folder?

Please open a command line in Windows, execute that command, and let us know if it fails by sharing the error message you receive.

This information will help to better understand the issue and assist you further.

[Rich86]

Thanks. Requested info follows:
1, Nvidia GEForce GTX760
2. driver = 475.06
3. BDRB 62.12
4. GPU #0 (NVIDIA GeForce GTX 760) does not support H.265/HEVC encoding.
Unknown erro occurred during checking GPU.

I'm not sure I understand this error. If I run this using DVDFab specifying NVENC it seems to work fine?
--------------------------------------------
Update: I did some further checking and apparently DVDFab uses NVENC for H.264 video but switches to software encoding for H.265.
I guess I'll have to update my video card if I want to use NVENC for H.265 encoding.
Many thanks for your comments and guidance helping me to understand what was going on and why.

[dietachi]

Thanks. Requested info follows:
1, Nvidia GEForce GTX760
2. driver = 475.06
3. BDRB 62.12
4. GPU #0 (NVIDIA GeForce GTX 760) does not support H.265/HEVC encoding.
Unknown erro occurred during checking GPU.

I'm not sure I understand this error. If I run this using DVDFab specifying NVENC it seems to work fine?
--------------------------------------------
Update: I did some further checking and apparently DVDFab uses NVENC for H.264 video but switches to software encoding for H.265.
I guess I'll have to update my video card if I want to use NVENC for H.265 encoding.
Many thanks for your comments and guidance helping me to understand what was going on and why.


The problem is that, as far as I know, the NVIDIA GeForce GTX 760 can't encode HEVC, only AVC.

If you re-encode BD to BD, that should be no issue, as the GPU can encode H.264/AVC.

If you open a UHD with BD Rebuilder, it will shrink the disc to a UHD, which is HEVC/H.265.

Unfortunately, I don't know if an option exists to enable the UHD to BD format conversion.

You need a newer GPU if you want to encode UHD to UHD.

Here is the Video Encode and Decode GPU Support Matrix for NVIDIA GPUs.
https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new

------

Update:
If you want to check the capabilities of the GPU (GTX 760), you can copy the first part from the LASTCMD.TXT and paste to the Windows command line, and add --check-features

You should get a result similar to:


"D:\BdRebuilder\tools\nvenc\nvencc.exe" --check-features
NVEncC (x86) 5.41 (r2064) by rigaya, Oct 14 2021 13:59:26 (VC 1929/Win)
[NVENC API v11.1, CUDA 11.1]
reader: raw, y4m, avi, avs, vpy, avsw, avhw [H.264/AVC, H.265/HEVC, MPEG2, VP8, VP9, VC-1, MPEG1, MPEG4, AV1]

Environment Info
OS : Windows 11 x64 (22631) [UTF-8]
CPU: 12th Gen Intel Core i9-12900K [4.91GHz] (16C/24T)
RAM: Used 12831 MB, Total 65289 MB

#0: NVIDIA GeForce RTX 3080 (8704 cores, 1725 MHz)[2147483.64]
NVEnc features
Codec: H.264/AVC
Encoder Engines 1
Max Bframes 4
B Ref Mode 3 (each + only middle)
RC Modes 63
Field Encoding 0 (no)
MonoChrome no
FMO no
Quater-Pel MV yes
B Direct Mode yes
CABAC yes
Adaptive Transform yes
Max Temporal Layers 4
Hierarchial P Frames yes
Hierarchial B Frames yes
Max Level 62 (6.2)
Min Level 10 (1)
4:4:4 yes
Min Width 145
Max Width 4096
Min Height 49
Max Height 4096
Multiple Refs yes
Max LTR Frames 8
Dynamic Resolution Change yes
Dynamic Bitrate Change yes
Forced constant QP yes
Dynamic RC Mode Change no
Subframe Readback yes
Constrained Encoding yes
Intra Refresh yes
Custom VBV Bufsize yes
Dynamic Slice Mode yes
Ref Pic Invalidiation yes
PreProcess no
Async Encoding yes
Max MBs 65536
Lossless yes
SAO no
Me Only Mode 1 (I,P frames)
Lookahead yes
AQ (temporal) yes
Weighted Prediction yes
10bit depth no

Codec: H.265/HEVC
Encoder Engines 1
Max Bframes 5
B Ref Mode 3 (each + only middle)
RC Modes 63
Field Encoding 0 (no)
MonoChrome no
Quater-Pel MV yes
B Direct Mode no
Max Temporal Layers 0
Hierarchial P Frames no
Hierarchial B Frames no
Max Level 186 (6.2)
Min Level 30 (1)
4:4:4 yes
Min Width 129
Max Width 8192
Min Height 33
Max Height 8192
Multiple Refs yes
Max LTR Frames 7
Dynamic Resolution Change yes
Dynamic Bitrate Change yes
Forced constant QP yes
Dynamic RC Mode Change no
Subframe Readback yes
Constrained Encoding yes
Intra Refresh yes
Custom VBV Bufsize yes
Dynamic Slice Mode yes
Ref Pic Invalidiation yes
PreProcess no
Async Encoding yes
Max MBs 262144
Lossless yes
SAO yes
Me Only Mode 1 (I,P frames)
Lookahead yes
AQ (temporal) yes
Weighted Prediction yes
10bit depth yes


NVDec features
H.264/AVC: nv12, yv12
H.265/HEVC: nv12, yv12, yv12(10bit), yv12(12bit), yuv444, yuv444(10bit), yuv444(12bit)
MPEG1: nv12, yv12
MPEG2: nv12, yv12
MPEG4: nv12, yv12
VP8: nv12, yv12
VP9: nv12, yv12, yv12(10bit), yv12(12bit)
VC-1: nv12, yv12
AV1: nv12, yv12, yv12(10bit)

[Rich86]

It appears that DVDFab uses a combination of tools in its UHD to BD process.
It appears to be using software to decode the 4K/UHD video & the video card resources to encode that video for BD.
It seems to work ok.

[cartman0208]

For anyone who may be interested, I've done some testing to compare what can give similar results across three of the HEVC encoders available through BD-RB (X265, QSVEncc, and NVEncc). Using a source that combines parts (using the BD-RB prediction sampling algorithm) of several different types of movies, I ran each encoder using its version of constant quality encoding. This way, if you have been using one encoder and want to try another -- you can see what value results in equivalent quality (per SSIM results), and what you might expect in terms of sizing.

Just as an additional note -- each of the GPU encoders is many, many times faster...X265 SSIM SIZE NVIDIA SSIM FILESIZE SIZE % INTEL SSIM FILESIZE SIZE %
CRF
NV_HEVC_11 0.99469 2735438211 QSV_HEVC_11 0.99492 2370988385
NV_HEVC_12 0.99448 2552227295
NV_HEVC_13 0.99401 2328739840 QSV_HEVC_12 0.99420 2151610991
11 0.99335 1949610802 NV_HEVC_14 0.99338 2122928050 108.88 QSV_HEVC_13 0.99337 1919639622 98.46
12 0.99262 1750487380 NV_HEVC_15 0.99244 1900798214 108.59 QSV_HEVC_14 0.99236 1686108802 89.79
13 0.99179 1566882823 NV_HEVC_16 0.99132 1688757477 107.78 QSV_HEVC_15 0.99134 1486820316 94.89
14 0.99082 1396060525
15 0.98977 1237639586 NV_HEVC_17 0.99009 1492524278 120.59 QSV_HEVC_16 0.99005 1289467174 104.19
16 0.98858 1087869492 NV_HEVC_18 0.98871 1310176603 120.44 QSV_HEVC_17 0.98864 1116438300 102.63
17 0.98712 939036774 NV_HEVC_19 0.98728 1148904500 122.35 QSV_HEVC_18 0.98702 960051106 102.24
18 0.98546 801110032 NV_HEVC_20 0.98584 1009198253 125.97 QSV_HEVC_19 0.98533 821968709 102.60
NV_HEVC_21 0.98436 885250807
19 0.98365 677460693 NV_HEVC_22 0.98282 772522049 114.03 QSV_HEVC_20 0.98337 690590341 101.94
20 0.98166 566939264 NV_HEVC_23 0.98117 666817944 117.62 QSV_HEVC_21 0.98144 583298263 102.89
21 0.97953 469052281 NV_HEVC_24 0.97950 573435830 122.25 QSV_HEVC_22 0.97931 481562861 102.67
22 0.97733 384487124 NV_HEVC_25 0.97791 493929976 128.46 QSV_HEVC_23 0.97716 394645310 102.64
NV_HEVC_26 0.97634 423749808 QSV_HEVC_24 0.97651 370217079
QSV_HEVC_25 0.97589 349571314
23 0.97510 312082984 NV_HEVC_27 0.97472 360136885 115.40 QSV_HEVC_26 0.97526 331796120 106.32
24 0.97293 251675944 NV_HEVC_28 0.97322 307347661 122.12 QSV_HEVC_27 0.97312 269137749 106.94
NV_HEVC_29 0.97173 261407806
25 0.97086 201981938 QSV_HEVC_28 0.97105 218090181 107.98
NV_HEVC_30 0.97027 222447802
26 0.96889 161696455 NV_HEVC_31 0.96877 187941863 116.23 QSV_HEVC_29 0.96899 174132836 107.69
27 0.96709 130308016 NV_HEVC_32 0.96730 158906997 121.95 QSV_HEVC_30 0.96703 141389351 108.50
28 0.96542 106218339 NV_HEVC_33 0.96580 134505532 126.63
QSV_HEVC_31 0.96489 112962058
29 0.96384 88090623 NV_HEVC_34 0.96434 114609022 130.10
30 0.96225 74482214 NV_HEVC_35 0.96279 97577670 131.01 QSV_HEVC_32 0.96299 92046174 123.58
31 0.96061 63853702 NV_HEVC_36 0.96118 83653349 131.01 QSV_HEVC_33 0.96143 79951128 125.21
32 0.95889 55398574 NV_HEVC_37 0.95954 72067442 130.09 QSV_HEVC_34 0.95938 67142107 121.20
33 0.95706 48562088 NV_HEVC_38 0.95776 62530064 128.76 QSV_HEVC_35 0.95721 57324572 118.04
34 0.95510 42844610 NV_HEVC_39 0.95583 54649663 127.55 QSV_HEVC_36 0.95506 49657159 115.90
35 0.95297 38016642 NV_HEVC_40 0.95368 47941203 126.11 QSV_HEVC_37 0.95286 43762369 115.11
36 0.95068 33822068 QSV_HEVC_38 0.95107 41276063 122.04
37 0.94826 30198276 QSV_HEVC_39 0.94866 36743861 121.68
38 0.94571 27011194 QSV_HEVC_40 0.94613 33191208 122.88
39 0.94304 24209378
40 0.94019 21764853Example: Let's say you had been using X265 with a CRF of 23 and like the results. By the table you could use QSVEncc using a ICQ value of 26 -- and get similar quality with about a 6% increase in output file size. If you chose to use NVEncc you could select 27 and get the same results with a 15% increase.

That's very cool, thanks ... I would be very much interested in the associated encoding times ;)
I'd venture Intel and Nvidia won't differ much

[jdobbs]

It appears that DVDFab uses a combination of tools in its UHD to BD process.
It appears to be using software to decode the 4K/UHD video & the video card resources to encode that video for BD.
It seems to work ok.I'll look at how hard it would be to recognize early cards and automatically use software encoding.

In the meantime, though, try adding the line below to the "[Options]" area of BDREBUILDER.INI and force software decoding, just to see if that solves the issue.

NVENC_FORCE_AVS=1

[jdobbs]

That's very cool, thanks ... I would be very much interested in the associated encoding times ;)
I'd venture Intel and Nvidia won't differ muchYou know, if I was a little smarter I would have recorded that when I was doing this!

[Edit] Hmmm... I still have the resulting files with timecodes on them... I may just be able to put something together. I'll tell you this with assurance, though: Both Intel and Nvidia are many, many, many times faster than X265 (at least on my i7 system while using FFMPEG to frameserve to it).

[Another Edit] Never mind. I looked at some of the files, and (weirdly) they make no sense. Some of them show as "last modified" an hour before they were created. :confused: That's some pretty fast encoding, eh?

[Lathe]

You know, if I were a little smarter...

That's why we're here JD, for moral support and to make up the difference... https://lh3.googleusercontent.com/pw/AP1GczNuSHXicvIvdYEl-wb99oyNaE1gavkEGTT7HSnVqz5pGPEXLyXQvQ8LiOllw7D6hYjqX6y71aZ09-magBjY5mcW2zU5pSdDprOC1jGadqQHhzSQ_RRGV4lBT_9ydGbj80uWSk895V-CwIUn5x2BXCXrtg=w15-h15-s-no-gm?authuser=0

[jdobbs]

That's why we're here JD, for moral support and to make up the difference... https://lh3.googleusercontent.com/pw/AP1GczNuSHXicvIvdYEl-wb99oyNaE1gavkEGTT7HSnVqz5pGPEXLyXQvQ8LiOllw7D6hYjqX6y71aZ09-magBjY5mcW2zU5pSdDprOC1jGadqQHhzSQ_RRGV4lBT_9ydGbj80uWSk895V-CwIUn5x2BXCXrtg=w15-h15-s-no-gm?authuser=0And I'd be lost without you.

[Rich86]

I'll look at how hard it would be to recognize early cards and automatically use software encoding.

In the meantime, though, try adding the line below to the "[Options]" area of BDREBUILDER.INI and force software decoding, just to see if that solves the issue.

NVENC_FORCE_AVS=1

I made the change you suggested. It did not fail, but it looks like it is going to run forever?

[jdobbs]

Wow. That is really slow. I don't think it is AVISYNTH, as it runs pretty fast most of the time. Ugghh... You're probably better off with X265.

[gonca]

@Rich86
If possible could you check CPU and GPU usage (during the encode) from task manager and post the info.

[SquallMX]

BDRebuilder is completely broken on Windows 24H2.

I tried several disks, on several modes only to get weird error messages, I even created a simple BD structure with TSMuxerGUI, same result:

[09/03/24] BD Rebuilder v0.62.12
[10:17:13] Source: SAMPLE
- Input BD size: 0.04 GB
- Approximate total content: [00:00:12.680]
- Target BD size: 22.46 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- X264 Tweak(s) enabled
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- [10:17:13] DoEncoding() 00011 1502
[10:17:14] - Failed to complete.


Sometimes detects a BD with completely wrong values:
https://i.imgur.com/7R2cIGg.png

Sometimes instead a error message appears {THE SELECTED SOURCE IS NOT BD FORMAT }

It was working fine on 23H2.

[jdobbs]

Can anybody else confirm issues with Windows 24H2? I'm still on 23H2. I haven't even gotten an update notification for 24H2.

[SquallMX]

Can anybody else confirm issues with Windows 24H2? I'm still on 23H2. I haven't even gotten an update notification for 24H2.

It's only available for Business at the moment. I going to install it on another PC and test it for the same issues. Maybe is just a botched install, too bad if that is the case, the Business edition is free from bloatware and ads.

[MrVideo]

What the hell is 24H2? What is it. i.e., the version of Win 11?

[jdobbs]

It's only available for Business at the moment. I going to install it on another PC and test it for the same issues. Maybe is just a botched install, too bad if that is the case, the Business edition is free from bloatware and ads.Unfortunately that's what is sounds like -- either that or just a badly tested release. Any other software showing issues?

[jdobbs]

What the hell is 24H2? What is it. i.e., the version of Win 11?Yes, its a Windows 11 version number.

[SquallMX]

Unfortunately that's what is sounds like -- either that or just a badly tested release. Any other software showing issues?

Finally I found the cause of this misbehavior!

It was the option "Beta: Use Unicode UTF-8 for worldwide language support", disabling this checkbox fixed the issue after a restart.

According to my google-fu "If you check this option, Windows will use codepage 65001 (Unicode UTF-8) instead of the local codepage. The downside is that ANSI-Only programs (most older programs) will show garbage instead of accented characters." Looks like BD-Rebuilder is one of those older programs.

[jdobbs]

Finally I found the cause of this misbehavior!

It was the option "Beta: Use Unicode UTF-8 for worldwide language support", disabling this checkbox fixed the issue after a restart.

According to my google-fu "If you check this option, Windows will use codepage 65001 (Unicode UTF-8) instead of the local codepage. The downside is that ANSI-Only programs (most older programs) will show garbage instead of accented characters." Looks like BD-Rebuilder is one of those older programs.Hmmm... I seem to remember getting a report of that error many, many years ago.

[stonesfan129]

jdobbs, is there any way you can add the AMD VCE encoder into this program? I see that Intel QSV was added, and I think NVENC has always been available. I specifically would like to compress some 4K content to BD50/BD25. Thank you.

[jdobbs]

jdobbs, is there any way you can add the AMD VCE encoder into this program? I see that Intel QSV was added, and I think NVENC has always been available. I specifically would like to compress some 4K content to BD50/BD25. Thank you.It was added for testing in v0.62.10 (see CHANGES.TXT). You can enable it (for testing) by adding the following line to the "[Options]" area of BDREBUILDER.INI (in the same folder as BDRB.EXE):

VCE_TEST=1

[Lathe]

What the hell is 24H2? What is it. i.e., the version of Win 11?

... Annnnnnd, that's why after a very scary, almost compulsory huge screen filled prompt basically TELLING me I have to upgrade to W11, I desperately searched for what to do. For me personally, I have turned off Windows update completely in the system settings (they're not going to update W10 anyway) That was the only way I could prevent a very FORCEFUL update to W11.

[Lathe]

Hmmm... I seem to remember getting a report of that error many, many years ago.

It was McFly coming back to warn you that this would happen...

[stonesfan129]

It was added for testing in v0.62.10 (see CHANGES.TXT). You can enable it (for testing) by adding the following line to the "[Options]" area of BDREBUILDER.INI (in the same folder as BDRB.EXE):

VCE_TEST=1

Thank you. This will be great for doing some test 4KBD encodes to BD50 and BD25.

[jdobbs]

It was McFly coming back to warn you that this would happen...:scared: Could it be?

[Hooman]

Hi, when (re-)muxing with BD-RB, the playlists’ IN_Time always defaults to 00:00:00:00. If the original IN_Time is different, we’ll see an unintended portion at the start of the clips. Can you please fix this issue?

[jdobbs]

Can you post the log for that encode?

[Hooman]

Can you post the log for that encode?
It’s not an issue with the encodes. Whenever the clip (the streams) contains a part at its start that is to be skipped according to its corresponding playlist file, BD-RB doesn't retain the (PlayItem's) IN_Time at its original value and changes it to 00:00:00:00. This could be due to the commands BD-RB sends to tsMuxer (Or the "Rebuilding BD file Structure"). The attached image shows the original structure as imported into Scenarist by a BD-Reauthor script. The black frame that reads ‘Cinerama Everywhere, RT 8:20…’ is a shot of the short part at the start of the clip that is not intended to be played back.

If I rebuild the same title (even with the FORCE_NOENCODE=1 flag?) and then import the rebuilt version into Scenarist for re-authoring, the aforementioned IN_Time is not the same as in the original MPLS. When that playlist/clip is called from the disc menu, those few frames at the start of the clip play back because the IN_Time has changed. Maybe something like BDTools can correct it in MPLS files.

PS
For this particular clip, the “IN_time” of the PlayItem and the “mark_time_stamp” of the first “PlayListMark” in the original playlist MPLS (converted by BDTools to readable JSON) is 27167041. However, in the BD-Rebuilt version, it has changed to 27000000.
{
"MPLS": {
"version_number": "0200",
"reserved_header": [
0
],
"AppInfoPlayList": {
"reserved01": 0,
"PlayList_playback_type": 1,
"UO_mask_table": {
"menu_call_mask": 0,
"title_search_mask": 0,
"chapter_search_mask": 0,
"time_search_mask": 0,
"skip_to_next_point_mask": 0,
"skip_back_to_previous_point_mask": 0,
"play_FirstPlay_mask": 0,
"stop_mask": 0,
"pause_on_mask": 0,
"pause_off_mask": 0,
"still_off_mask": 0,
"forward_play_mask": 0,
"backward_play_mask": 0,
"resume_mask": 0,
"move_up_selected_button_mask": 0,
"move_down_selected_button_mask": 0,
"move_left_selected_button_mask": 0,
"move_right_selected_button_mask": 0,
"select_button_mask": 0,
"activate_button_mask": 0,
"select_button_and_activate_mask": 0,
"primary_audio_stream_number_change_mask": 0,
"reserved01": 0,
"angle_number_change_mask": 0,
"popup_on_mask": 0,
"popup_off_mask": 0,
"PG_textST_enable_disable_mask": 0,
"PG_textST_stream_number_change_mask": 0,
"secondary_video_enable_disable_mask": 0,
"secondary_video_stream_number_change_mask": 0,
"secondary_audio_enable_disable_mask": 0,
"secondary_audio_stream_number_change_mask": 0,
"reserved02": 0,
"PiP_PG_textST_stream_number_change_mask": 0,
"reserved03": 0
},
"reserved02": 0,
"PlayList_random_access_flag": 0,
"audio_mix_app_flag": 1,
"lossless_may_bypass_mixer_flag": 0,
"MVC_Base_view_R_flag": 0
},
"PlayList": {
"reserved01": 0,
"PlayItem": [
{
"Clip_Information_file_name": "00018",
"Clip_codec_identifier": "M2TS",
"ref_to_STC_id": 0,
"reserved01": 0,
"is_multi_angle": 0,
"connection_condition": 1,
"IN_time": 27167041,
"OUT_time": 49802154,
"UO_mask_table": {
"menu_call_mask": 0,
"title_search_mask": 0,
"chapter_search_mask": 0,
"time_search_mask": 0,
"skip_to_next_point_mask": 0,
"skip_back_to_previous_point_mask": 0,
"play_FirstPlay_mask": 0,
"stop_mask": 0,
"pause_on_mask": 0,
"pause_off_mask": 0,
"still_off_mask": 0,
"forward_play_mask": 0,
"backward_play_mask": 0,
"resume_mask": 0,
"move_up_selected_button_mask": 0,
"move_down_selected_button_mask": 0,
"move_left_selected_button_mask": 0,
"move_right_selected_button_mask": 0,
"select_button_mask": 0,
"activate_button_mask": 0,
"select_button_and_activate_mask": 0,
"primary_audio_stream_number_change_mask": 0,
"reserved01": 0,
"angle_number_change_mask": 0,
"popup_on_mask": 0,
"popup_off_mask": 0,
"PG_textST_enable_disable_mask": 0,
"PG_textST_stream_number_change_mask": 0,
"secondary_video_enable_disable_mask": 0,
"secondary_video_stream_number_change_mask": 0,
"secondary_audio_enable_disable_mask": 0,
"secondary_audio_stream_number_change_mask": 0,
"reserved02": 0,
"PiP_PG_textST_stream_number_change_mask": 0,
"reserved03": 0
},
"PlayItem_random_access_flag": 0,
"reserved02": 0,
"still_mode": 0,
"still_time": 0,
"STN_table": {
"reserved01": 0,
"number_of_PiP_PG_textST_stream_entries_plus": 0,
"stream": [
{
"type": 1,
"pid": 4113,
"stream_coding_type": "H.264",
"video_format": "1080p",
"frame_rate": "23.976",
"reserved01": 0
},
{
"type": 1,
"pid": 4352,
"stream_coding_type": "AC-3",
"audio_presentation_type": "Stereo",
"sampling_frequency": "48 kHz",
"language_code": "fra"
},
{
"type": 2,
"subpath_id": 0,
"subclip_id": 0,
"pid": 5120,
"stream_coding_type": "IGS",
"language_code": "eng",
"reserved01": 0
}
]
}
}
],
"SubPath": [
{
"reserved01": 0,
"SubPath_type": 3,
"reserved02": 0,
"is_repeat_SubPath": 0,
"reserved03": 0,
"SubPlayItem": [
{
"Clip_Information_file_name": "00016",
"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": 27001876,
"sync_PlayItem_id": 0,
"sync_start_PTS_of_PlayItem": 0
}
]
}
]
},
"PlayListMark": [
{
"reserved01": 0,
"mark_type": 1,
"ref_to_PlayItem_id": 0,
"mark_time_stamp": 27167041,
"entry_ES_PID": 65535,
"duration": 0
},
{
"reserved01": 0,
"mark_type": 1,
"ref_to_PlayItem_id": 0,
"mark_time_stamp": 49800277,
"entry_ES_PID": 65535,
"duration": 0
}
]
}
}
I believe this issue can only be resolved by a reverse conversion of the JSON file back into an MPLS playlist after BD-RB’s work.

[jdobbs]

There is other useful information in the log... for example, was it a full backup or a movie-only? But I guess you decided it wasn't needed and provided something I didn't ask for instead.

[Hooman]

Sorry, didn't realize the log was needed.
It was a full backup.
Here is the log:
[09/06/24]BD Rebuilder v0.61.28
[08:59:11] Source: JOB_TITLE
- Input BD size: 43.72 GB
- Approximate total content: [04:58:08.562]
- Target BD size: 24.30 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[08:59:14] PHASE ONE, Encoding
- [08:59:14] Processing: VID_00003 (2 of 9)
- [08:59:14] Extracting A/V streams [VID_00003]
- [09:04:03] Reencoding video [VID_00003]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 83,529 frames
- Bitrate: 11,188 Kbs
- [09:04:03] Reencoding: VID_00003, Pass 1 of 2
- [09:39:03] Reencoding: VID_00003, Pass 2 of 2
- [11:18:34] Video Encode complete
- [11:18:34] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
- Track 4354 (eng): Keeping original audio
- [11:18:34] Multiplexing M2TS
- [11:22:17] Processing: VID_00004 (3 of 9)
- [11:22:17] Extracting A/V streams [VID_00004]
- [11:22:57] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 18,152 frames
- Bitrate: 9,249 Kbs
- [11:22:57] Reencoding: VID_00004, Pass 1 of 2
- [11:30:10] Reencoding: VID_00004, Pass 2 of 2
- [11:48:50] Video Encode complete
- [11:48:50] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:48:50] Multiplexing M2TS
- [11:49:04] Processing: VID_00007 (4 of 9)
- [11:49:04] Extracting A/V streams [VID_00007]
- [11:49:20] Reencoding video [VID_00007]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 22,315 frames
- Bitrate: 2,527 Kbs
- [11:49:20] Reencoding: VID_00007, Pass 1 of 2
- [11:55:16] Reencoding: VID_00007, Pass 2 of 2
- [12:03:24] Video Encode complete
- [12:03:24] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [12:03:24] Multiplexing M2TS
- [12:03:31] Processing: VID_00011 (5 of 9)
- [12:03:31] Extracting A/V streams [VID_00011]
- [12:03:50] Reencoding video [VID_00011]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 25,111 frames
- Bitrate: 4,040 Kbs
- [12:03:50] Reencoding: VID_00011, Pass 1 of 2
- [12:14:52] Reencoding: VID_00011, Pass 2 of 2
- [12:39:37] Video Encode complete
- [12:39:37] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [12:39:37] Multiplexing M2TS
- [12:39:48] Processing: VID_00012 (6 of 9)
- [12:39:48] Extracting A/V streams [VID_00012]
- [12:40:00] Reencoding video [VID_00012]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 8,578 frames
- Bitrate: 3,527 Kbs
- [12:40:00] Reencoding: VID_00012, Pass 1 of 2
- [12:42:43] Reencoding: VID_00012, Pass 2 of 2
- [12:49:50] Video Encode complete
- [12:49:50] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [12:49:50] Multiplexing M2TS
- [12:49:56] Processing: VID_00013 (7 of 9)
- [12:49:56] Extracting A/V streams [VID_00013]
- [12:50:20] Reencoding video [VID_00013]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 8,660 frames
- Bitrate: 12,251 Kbs
- [12:50:20] Reencoding: VID_00013, Pass 1 of 2
- [12:54:11] Reencoding: VID_00013, Pass 2 of 2
- [13:05:50] Video Encode complete
- [13:05:50] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [13:05:50] Multiplexing M2TS
- [13:06:03] Processing: VID_00018 (8 of 9)
- [13:06:03] Extracting A/V streams [VID_00018]
- [13:06:19] Reencoding video [VID_00018]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 12,060 frames
- Bitrate: 5,119 Kbs
- [13:06:19] Reencoding: VID_00018, Pass 1 of 2
- [13:11:19] Reencoding: VID_00018, Pass 2 of 2
- [13:22:34] Video Encode complete
- [13:22:34] Processing audio tracks
- Track 4352 (fra): Keeping original audio
- [13:22:34] Multiplexing M2TS
- [13:22:42] Processing: VID_00019 (9 of 9)
- [13:22:42] Extracting A/V streams [VID_00019]
- [13:24:16] Reencoding video [VID_00019]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 104,046 frames
- Bitrate: 7,172 Kbs
- [13:24:16] Reencoding: VID_00019, Pass 1 of 2
- [14:06:15] Reencoding: VID_00019, Pass 2 of 2
- [15:58:16] Video Encode complete
- [15:58:16] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [15:58:16] Multiplexing M2TS
[15:59:29]PHASE ONE complete
[15:59:29]PHASE TWO - Rebuild Started
- [15:59:29] Rebuilding BD file Structure
[16:00:04] - Encode and Rebuild complete
[16:00:04] JOB: JOB_TITLE finished.

and the inf:
[Status]
LABEL=JOB_TITLE
VERSION=v0.61.28
SOURCE_SIZE=46943731324
SOURCE_VIDEO_SIZE=44934285312
TARGET_SIZE=26088570880
REDUCTION=.535874214996572
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=all
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=all
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=-1
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
UHD_V3_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=9
REBUILD_COMPLETE=1
[00002]
AUDIO=111
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=9246285730
RATE=11507
SPLITS=1
NSTART=27000000
NEND=204107555
NSIZE=8848588800
FLINK=0
MLINK=0
[00003]
AUDIO=111
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=8327054407
RATE=11188
SPLITS=1
NSTART=27000000
NEND=183773491
NSIZE=7944744960
FLINK=0
MLINK=0
[00004]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=969496565
RATE=9249
SPLITS=1
NSTART=27000000
NEND=61069035
NSIZE=948553728
FLINK=0
MLINK=0
[00007]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=350516679
RATE=2527
SPLITS=1
NSTART=27000000
NEND=68882465
NSIZE=343523328
FLINK=0
MLINK=0
[00011]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=486022446
RATE=4040
SPLITS=1
NSTART=27000000
NEND=64704166
NSIZE=474673152
FLINK=0
MLINK=0
[00012]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=182880271
RATE=3527
SPLITS=1
NSTART=27000000
NEND=43099833
NSIZE=179073024
FLINK=0
MLINK=0
[00013]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=676139437
RATE=12251
SPLITS=1
NSTART=27000000
NEND=43253737
NSIZE=662796288
FLINK=0
MLINK=0
[00018]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=364861714
RATE=5119
SPLITS=1
NSTART=27000000
NEND=49635113
NSIZE=358785024
FLINK=0
MLINK=0
[00019]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=3475867620
RATE=7172
SPLITS=1
NSTART=27000000
NEND=183225069
NSIZE=3390314496
FLINK=0
MLINK=0

[Lathe]

Well, I probably missed this being covered before, and if so, my humble apologies...

Can you use BDRB to convert from a UHD/HDR source to a playable SDR 1080 Blu-ray? Is there any adjustment for changing the color filter to BT709 or any other parameters that allow this?

Or, sort of conversely (not really) can you also simply convert any UHD source using x264 to make a playable Blu-ray? It seems that whenever I try to convert HEVC to x264 it always throws an error. Any secret settings in the configurations? I've tried using both alternate movie only format and archive format (AVC/AC3) neither seem to work for this.

Thanks!

[jdobbs]

Well, I probably missed this being covered before, and if so, my humble apologies...

Can you use BDRB to convert from a UHD/HDR source to a playable SDR 1080 Blu-ray? Is there any adjustment for changing the color filter to BT709 or any other parameters that allow this?

Or, sort of conversely (not really) can you also simply convert any UHD source using x264 to make a playable Blu-ray? It seems that whenever I try to convert HEVC to x264 it always throws an error. Any secret settings in the configurations? I've tried using both alternate movie only format and archive format (AVC/AC3) neither seem to work for this.

Thanks!Right now there isn't an easy way to go from UHD to HD. There will probably never be a way to do a full backup -- that's because of differences in v2 and v3 file formats/types.

I'm looking at the possibility of adding a movie-only and/or quick-menu type backup.

Right now you'd have to create an alternate backup in 1080p and then import it.

[Lathe]

Right now there isn't an easy way to go from UHD to HD. There will probably never be a way to do a full backup -- that's because of differences in v2 and v3 file formats/types.

I'm looking at the possibility of adding a movie-only and/or quick-menu type backup.

Right now you'd have to create an alternate backup in 1080p and then import it.

Okidoke, thanks JD! So, I CAN import either the full UHD blu-ray (m2ts) or 2160 HEVC file and use alternate movie only backup? Would I then be selecting HEVC (it's original format) or can I choose x264? I'm a little fuzzy about the exact steps to use after importing the file...

And, I'm assuming there is no ability to use a BT709 filter to convert it to SDR either, right?

[gonca]

And, I'm assuming there is no ability to use a BT709 filter to convert it to SDR either, right?

You might be able to input a tonemapping filter with the avisynth tweaks setting

[jdobbs]

Okidoke, thanks JD! So, I CAN import either the full UHD blu-ray (m2ts) or 2160 HEVC file and use alternate movie only backup? Would I then be selecting HEVC (it's original format) or can I choose x264? I'm a little fuzzy about the exact steps to use after importing the file...

And, I'm assuming there is no ability to use a BT709 filter to convert it to SDR either, right?You can choose X264 for the output to alternate (or any other H264 encoder for that matter). Then when you import, you won't have to encode again (unless you decide to do a near-identical [low CRF] encode during the alternate phase) -- that way after importing you can reencode again.

If you decide to do only on encode (alternate), add ALTERNATE_BLURAY=1 to your REBUILDER.INI. That way the alternate encode will be forced to meet Blu-Ray requirements (making it possible to import without reencoding a second time).

[Lathe]

You might be able to input a tonemapping filter with the avisynth tweaks setting

Ah yes, I was thinking about that...

[Lathe]

You can choose X264 for the output to alternate (or any other H264 encoder for that matter). Then when you import, you won't have to encode again (unless you decide to do a near-identical [low CRF] encode during the alternate phase) -- that way after importing you can reencode again.

If you decide to do only on encode (alternate), add ALTERNATE_BLURAY=1 to your REBUILDER.INI. That way the alternate encode will be forced to meet Blu-Ray requirements (making it possible to import without reencoding a second time).

Ah, good, thank you Sir!