BD Rebuilder Beta - Bug Reports Only

[Lathe]

Originally Posted by gonca

As long as you know it

During import TsMuxer is doing the demux/remux.
It can handle 10 bit video.
For encoding, avisynth is used, and the version you are on can not.
That is why import was good and processing failed.

Edit
I am not laughing my head off, I have come to expect it of you!

Ah, I see... Thanks for the explanation. I was curious why BDRB was rejecting it, that's good to know.

I'm glad your expectations have been met...

BTW, how's the Moose Stew...?

[MrVideo]

Originally Posted by Lathe

I would like just to use a simply CMD line, but there are certain settings I think in order to get the frame rate right or something that I'm not sure of. And, I don't know if my GPU will work with that, I'm not familiar with that whole side of the GPU used for encoding.

It can be run via a command line, but because of the numerous options, best to run it from the GUI. There's lots of previous discussion about the newer GPUENCC program. Dig back thru the thread.

[MrVideo]

Originally Posted by MrVideo

UPDATE: It just dawned on me what the issue probably is. BDs don't handle HEVC video. I set UHD_CONVERT_ENABLE to 1, but it didn't make a difference. How do I get BDRB to author a UHD disc with 1080p HEVC content? BTW, I don't want to use the standalone program to upconvert to 2160p because the program doesn't use the chapter locations to create I-frames at those locations. AIUI, you want I-frames at chapter marks.

I went back to the original HEVC videos and recoded them to AVC (via GPUENCC). Because I had to edit them at the commercial breaks to remove some of the black and to create I-frames at those locations, I didn't have to start from scratch as I was able to use the VideoReDo project files to do the editing again, but on AVC files this time. The BD was created just fine.

While I was able to get around the issue this time, I still want to be able to create a UHD with 1080p HEVC videos, in order to avoid a recoding. Each recoding introduces minor artifacts, etc. The less recoding, the better.

[varekai]

Originally Posted by MrVideo

(via GPUENCC).

Where can i find this GUI - GPUENCC program? I can't find it with google.

[musiclover]

Originally Posted by varekai

Where can i find this GUI - GPUENCC program? I can't find it with google.

In the BD_Rebuilder directory

[Lathe]

Originally Posted by musiclover

In the BD_Rebuilder directory

Soooooo, you can just run it by itself somehow...?

[gonca]

Originally Posted by Lathe

Soooooo, you can just run it by itself somehow...?

Yes, it has a gui just for you.

[Lathe]

Originally Posted by gonca

Yes, it has a gui just for you.

Lovely... I have NO bloody idea what it does (except doesn't it have something to do with using your GPU to do the encoding? I don't know if I have the right kind. Raedon I think) but, I'll check it out.

If that is the case, I wonder what the benefit is rather then just using the CPU as usual? I've been pretty happy with the speed of the encodes now that I have a faster CPU and more memory, so I don't get why there is some whole other way to do it...?

[gonca]

It has to be a Nvidia gpu, radeon would be amd.

[Lathe]

Originally Posted by gonca

It has to be a Nvidia gpu, radeon would be amd.

Yep, thought so...

[MrVideo]

Originally Posted by gonca

It has to be a Nvidia gpu, radeon would be amd.

Or the Intel.

[MrVideo]

Originally Posted by Lathe

If that is the case, I wonder what the benefit is rather then just using the CPU as usual?

It is many times faster than using software (CPU) encoding.

[Lathe]

Originally Posted by MrVideo

It is many times faster than using software (CPU) encoding.

Kinda figured that too... So, does it use the exact same parameters and yield the exact same quality as you would get using x264 settings and the CPU? Would the only different factor then just be the time of encoding?

[varekai]

Originally Posted by musiclover

In the BD_Rebuilder directory

Thanks!

[varekai]

Originally Posted by Lathe

Kinda figured that too... So, does it use the exact same parameters and yield the exact same quality as you would get using x264 settings and the CPU? Would the only different factor then just be the time of encoding?

From Google... maybe accurate?

In terms of bitrate efficiency, which encoding is better, software or hardware encoding?
For the best bitrate efficiency (quality per bitrate), software encoding tends to be superior due to its flexibility and ability to use advanced encoding techniques.
14 okt. 2024

Is it better to encode with GPU or CPU?
You almost always want to do GPU encoding for recordings if you have access to it because it minimizes CPU overhead.
However, CPU encoding technically produces more efficient compression (better quality at a given bitrate or lower bitrate at given quality).
19 dec. 2023

Is software or GPU rendering better?
The main attraction to software rendering is capability.
While hardware in GPU rendering is generally limited to its present capabilities, software rendering is developed with fully customizable programming, can perform any algorithm, and can scale across many CPU cores across several servers.

[MrVideo]

Originally Posted by Lathe

So, does it use the exact same parameters and yield the exact same quality as you would get using x264 settings and the CPU?

Different parameters. As indicated by varekai's posting, overall, software gives you more control. But takes a lot longer. Depending on the job, I'll do some x264 encoding, but it takes a lot longer. I'm not even set up to do x265 software encoding.

[Lathe]

Originally Posted by varekai

From Google... maybe accurate?

In terms of bitrate efficiency, which encoding is better, software or hardware encoding?
For the best bitrate efficiency (quality per bitrate), software encoding tends to be superior due to its flexibility and ability to use advanced encoding techniques.
14 okt. 2024

Is it better to encode with GPU or CPU?
You almost always want to do GPU encoding for recordings if you have access to it because it minimizes CPU overhead.
However, CPU encoding technically produces more efficient compression (better quality at a given bitrate or lower bitrate at given quality).
19 dec. 2023

Is software or GPU rendering better?
The main attraction to software rendering is capability.
While hardware in GPU rendering is generally limited to its present capabilities, software rendering is developed with fully customizable programming, can perform any algorithm, and can scale across many CPU cores across several servers.

Thanks mate!

[iambryanknowles]

When encoding x264 720p 60fps, BDRB defaults to keyint=30, and with extended_gop goes up to keyint=60. Should't it be 60 and 120?

[jdobbs]

Originally Posted by varekai

From Google... maybe accurate?

In terms of bitrate efficiency, which encoding is better, software or hardware encoding?
For the best bitrate efficiency (quality per bitrate), software encoding tends to be superior due to its flexibility and ability to use advanced encoding techniques.
14 okt. 2024

Is it better to encode with GPU or CPU?
You almost always want to do GPU encoding for recordings if you have access to it because it minimizes CPU overhead.
However, CPU encoding technically produces more efficient compression (better quality at a given bitrate or lower bitrate at given quality).
19 dec. 2023

Is software or GPU rendering better?
The main attraction to software rendering is capability.
While hardware in GPU rendering is generally limited to its present capabilities, software rendering is developed with fully customizable programming, can perform any algorithm, and can scale across many CPU cores across several servers.

If I can give my humble opinion... yes, CPU encoding technically produces more efficient compression. That's mainly due to its ability to do multi-pass encoding. But even then the difference is minimal -- a few percentage points in output size savings at a comparable quality level.

I personally use the GPU to do all my encoding and use constant quality mode (CRF [x264/5], QVBR [Nvidia], or ICQ [Intel]). That way I know exactly what quality level I will get. The only down side to it is that the size isn't easy to predict as it depends on the quality you choose and the complexity of the source. But in BD-RB that is taken care of by the program with sampling and size prediction.

And, as mentioned earlier by MrVideo -- GPU encoding is many, many times faster than using the CPU.

[varekai]

Originally Posted by jdobbs

If I can give my humble opinion...

That's interesting! Thanks for the info! Can I ask what NVIDIA GPU you use?
I have this Geforce RTX 4060 8GB and never tried encoding with it, next project I will try it with your settings.