BD Rebuilder Beta - Bug Reports Only

[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	21764853

Example: 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]

Originally Posted by 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.

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]

Originally Posted by 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.

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-e...ort-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]

Originally Posted by 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	21764853

Example: 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]

Originally Posted by 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.

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]

Originally Posted by cartman0208

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

You 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. That's some pretty fast encoding, eh?

[Lathe]

Originally Posted by jdobbs

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

That's why we're here JD, for moral support and to make up the difference...

[jdobbs]

Originally Posted by Lathe

That's why we're here JD, for moral support and to make up the difference...

And I'd be lost without you.

[Rich86]

Originally Posted by jdobbs

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:


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]

Originally Posted by jdobbs

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]

Originally Posted by SquallMX

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]

Originally Posted by MrVideo

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

Yes, its a Windows 11 version number.