BD Rebuilder Beta - Bug Reports Only

[deadfrog]

I just downloaded NVEncC 5.09 64 bit. I have a Ryzen 3900 with 128gb ram and a RTX2060. If someone could give me the command line they would like tested I can run it against Avengers endgame and see what kind of frames/sec I get.

[Mike-uk]

I just downloaded NVEncC 5.09 64 bit. I have a Ryzen 3900 with 128gb ram and a RTX2060. If someone could give me the command line they would like tested I can run it against Avengers endgame and see what kind of frames/sec I get.

--avhw --vpp-pad 0,276,0,278 -i F:\Movies\uhd2019\BDMV\STREAM\00014.m2ts --codec hevc --preset quality --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) --qp-min 0 --vbrhq 0 --vbr-quality 25 --sar 1:1 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 --slices 4 -o "D:\test\VID_00000.hevc

[cartman0208]

I had to do some small corrections to make it work (with powershell):
"C:\path\to\nvenc\nvencc64.exe" --avhw --vpp-pad 0,276,0,278 -i "X:\path\to\input.file" --codec hevc --preset quality --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --qp-min 0 --vbrhq 0 --vbr-quality 25 --sar 1:1 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 --slices 4 -o "X:\path\to\output.file"

Also I coudn't make out any difference in encoding speed between 32bit and 64bit version.

[jdobbs]

Also I coudn't make out any difference in encoding speed between 32bit and 64bit version.I also see no difference in speed between 32 bit and 64 bit. That makes sense, since the actual encoding is being done by hardware anyway.

The one thing I did notice is that (like x264 and x265) you can't use the 64 bit version with a standard (not "+" version) of AVISYNTH. So in BD-Rebuilder I will only be including the 32 bit version of NCEncc in the TOOLS folder.

I have NVENCC working reliably within BD Rebuilder. I'm now working on the function of sizing predictions for constant quality mode (CQM). Since prediction (X264/x265 CRF) never really worked well with HEVC sources in the past, I'm also fixing that in the prediction algorithm. There are a few other minor support functions that will have to be adjusted as well.

All-in-all I'm pretty pleased with what I'm seeing (especially for UHD sources). The only real disadvantage of NVENC is the lack of a true 2-pass mode. But I don't think that's ever likely with a HW encoder.
"C:\path\to\nvenc\nvencc64.exe" --avhw --vpp-pad 0,276,0,278 -i "X:\path\to\input.file" --codec hevc --preset quality --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --qp-min 0 --vbrhq 0 --vbr-quality 25 --sar 1:1 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 --slices 4 -o "X:\path\to\output.file"By the way, the only reason "--vpp-pad 0,276,0,278" was a part of that command line is because the file I was using was imported from an MKV and the black padding had been removed in the original MKV file. So, during import, BD-RB sensed the sizing irregularity and inserted the necessary padding to make it UHD-BD compliant. Some of the other portions of the command line (e.g. --master-display) can also be specific to a source (UHD-BD keeps track of it, and BD-RB pulls the information to make sure the reencode matches). With recent changes to NVENCC you would also want to add the "--repeat-headers" parameter to it if the output is targeted at a UHD-BD disc.

[Mike-uk]

The only real disadvantage of NVENC is the lack of a true 2-pass mode. But I don't think that's ever likely with a HW encoder.


can you not do a CPU true first pass ??
ou can do 2-pass in a few popular encoding programs, but the .stats file that is created is blank. The only way I've found to actually get a true 2-Pass is to run the first pass on the CPU, save the stats file and then use that during a second pass using NVENC which is a cumbersome process. Every other way I've encountered is no different than a 1-pass encode.

[jdobbs]

can you not do a CPU true first pass ??
ou can do 2-pass in a few popular encoding programs, but the .stats file that is created is blank. The only way I've found to actually get a true 2-Pass is to run the first pass on the CPU, save the stats file and then use that during a second pass using NVENC which is a cumbersome process. Every other way I've encountered is no different than a 1-pass encode.How can you get NVENC to read a stats file? I must have missed that parameter.

But, even if it could, running the first pass on the CPU kinda' defeats the purpose (speed) of NVENCC.

Right now all NVENCC can do is a 2-pass within a short range of frames... which isn't really a 2 pass. Honestly, though, I'm pretty satisfied with the output quality of 1 pass anyhow, and the CQM output looks really good.

[cartman0208]

How do you make sure, you hit the requested target size?
I imagine thats pretty hard with CQM ...

[Sharc]

How do you make sure, you hit the requested target size?
I imagine thats pretty hard with CQM ...
Possibly using the same (or similar) prediction algorithm which has been available since long for CPU based x264 CRF encodes?

[jdobbs]

Possibly using the same (or similar) prediction algorithm which has been available since long for CPU based x264 CRF encodes?Yeah. I built a prediction algorithm for BD Rebuilder so it could do targeted sizing using CRF in X264/X265. So for NVENC, I just had to do a large group of sample encodes in order to build its prediction tables.

I've done several tests and it seems to be working well enough. I also modified the way in which HEVC sources are sampled -- AVISYNTH's SelectRangeEvery() was getting terrible picture glitches with hevc, and I couldn't use if for UHD-BD anyway, because it didn't support HDR.

[cartman0208]

Yeah. I built a prediction algorithm for BD Rebuilder so it could do targeted sizing using CRF in X264/X265. So for NVENC, I just had to do a large group of sample encodes in order to build its prediction tables.


You mean like: take a sample of 24 frames from every minute of the movie ? :)

Oh, and what I just noticed ... is BD-RB cabable of HDR10+ ?
(sorry if that topic came up already)
because MediaInfo shows me on very few movies
HDR format : SMPTE ST 2094 App 4, Version 1, HDR10+ Profile A compatible
and after the BD-RB conversion:
HDR format : SMPTE ST 2086, HDR10 compatible

Or did I miss a secret switch? :eek:

[jdobbs]

You mean like: take a sample of 24 frames from every minute of the movie ? :)

Oh, and what I just noticed ... is BD-RB cabable of HDR10+ ?
(sorry if that topic came up already)
because MediaInfo shows me on very few movies

and after the BD-RB conversion:


Or did I miss a secret switch? :eek:The AVISYNTH sampling is configurable. See HIDDENOPTS.TXT: SAMPLE_GROUP=n n = Number of frames in each sample group for CRF estimation
SAMPLE_SIZE=n n = Number of frames in each sample for CRF estimation (size/group = sample percentage)The default values change depending upon on source framerates. But typically they are a 1% sample (e.g. 24fps uses a 48 frame sample [SAMPLE_SIZE] for every 4800 frames [SAMPLE_GROUP]).

On an HEVC source (in the upcoming version) a sample M2TS is created which consists of a 1% sample across multiple locations within the source.

BD-RB supports HDR10 and Dolby Vision. I don't think I've looked at HDR10+ yet (it's been a while), but frankly I am skeptical of all of these "extensions" to HDR10 as I think they are getting ridiculous and may in the same category as "HD Audio" (which is nothing beyond a marketing gimmick that has been proven scientifically as nonsense). Of course that comment will likely result in responses from people with "magic ears" who will say how they can tell the difference (even though what they actually hear is increased baseline volume that the marketeers have implemented in HD audio to try and make it appear as if there is an actual difference). Double blind tests show that (other than the additional channels available available in HD formats) Dolby Digital 5.1 at 640Kbs is indistinguishable from an lossless original audio source. Okay, time to step down off my soapbox.

I suppose I will have to look at HDR10+ just to keep the wolves at bay. But my guess is it will soon be replaced by HDR10++ or HDR10+ super-duper-excellent or some such thing. Marketeers have no boundaries (or ethics).

[cartman0208]

thanks for the description.

From my limited knowlege ... HDR10+, almost like DolbyVision, adds dynamic metadata to adjust brightness scene-by-scene, while HDR10 only uses static metadata

[Sharc]

NVEncC v5.10 is out. Supporting multipass ... (didn't try yet)

[jdobbs]

NVEncC v5.10 is out. Supporting multipass ... (didn't try yet)What???

And I was close to posting a test version of BD-RB...

I think I'll test multipass first...

[jdobbs]

I set it to --multipass 2pass-full and it shows it as set while it is running... but the speed seems identical and it appears to only do one pass. I think this may be a mode I read about previously (somewhere), where it does two passes on a limited subset of frames (the lookahead, maybe?). It wouldn't be considered as really two pass.

True two-pass encoding requires a look at the entire stream so bits can be allocated with the entire set of frames under consideration.

With that said, I'll do some testing and see if --multipass results in any noticable improvements.

[Edit] Curiouser and curiouser... you can even set --multipass 2pass-full when using CQM mode. How does that work?
And it appears that two-pass is ON no matter what settings you use. The encode shows 2pass-full mode even when I set --multipass none or --multipass 2pass-quater [SIC] It even says it is on if you leave the --multipass option off completely.

v5.10 is running a little slower than v5.09 and the output size with the same setting is a little larger with v5.10 (with the same CQM value)... so something has changed. I'm just not sure what. Maybe it's because 2 pass is stuck on no matter the setting? No idea.

So....

:confused:

[Sharc]

it requires nvidia driver 445.87 or later (SDK API 10.0).
Can't test it as I am away from home ....

Edit:
Perhaps this explains it
https://github.com/rigaya/NVEnc/issues/248

Edit2:
NVIDIA's multipass description / definition:
https://docs.nvidia.com/video-technologies/video-codec-sdk/nvenc-video-encoder-api-prog-guide/index.html#multi-pass-frame-phencoding

[jdobbs]

it requires nvidia driver 445.87 or later (SDK API 10.0).
Can't test it as I am away from home ....

Edit:
Perhaps this explains it
https://github.com/rigaya/NVEnc/issues/248I'm currently using nvidia driver 451.48... so that's not it.

[Sharc]

NVIDIA's multipass explanation from their doc:
https://docs.nvidia.com/video-technologies/video-codec-sdk/nvenc-video-encoder-api-prog-guide/index.html#multi-pass-frame-phencoding

Multi pass frame encoding
When determining the QP to use for encoding a frame, it is beneficial if NVENC knows the overall complexity of the frame to distribute the available bit budget in the most optimal manner. In some situations, multi-pass encoding may also help catch larger motion between frames. For this purpose, NVENC supports the following types of multi-pass frame encoding modes:

1-pass per frame encoding (NV_ENC_MULTI_PASS_DISABLED)
2-passes per frame, with first pass in quarter resolution and second pass in full resolution (NV_ENC_TWO_PASS_QUARTER_RESOLUTION)
2-passes per frame, with both passes in full resolution (NV_ENC_TWO_PASS_FULL_RESOLUION).
In 1-pass rate control modes, NVENC estimates the required QP for the macroblock and immediately encodes the macroblock. In 2-pass rate control modes, NVENC estimates the complexity of the frame to be encoded and determines bit distribution across the frame in the first pass. In the second pass, NVENC encodes macroblocks in the frame using the distribution determined in the first pass. As a result, with 2-pass rate control modes, NVENC can distribute the bits more optimally within the frame and can reach closer to the target bitrate, especially for CBR encoding. Note, however, that everything else being the same, performance of 2-pass rate control mode is lower than that of 1-pass rate control mode. The client application should choose an appropriate multi-pass rate control mode after evaluating various modes, as each of the modes has its own advantages and disadvantages. NV_ENC_TWO_PASS_FULL_RESOLUION generates better statistics for the second pass, whereas NV_ENC_TWO_PASS_QUARTER_RESOLUTION results in larger motion vectors being caught and fed as hints to second pass.

[jdobbs]

Thanks for that. That make sense. So it isn't really 2 pass encoding in the traditional sense at all -- it's just 2 passes on a single frame during that frame's encoding.

It looks to me like the new version of NVENCC keeps it in 2-pass-full no matter what setting you specify. I'm sure that's a bug... but probably not a bad one, since 2pass-full is likely the best option in most cases anyhow.

[Edit] I submitted a bug report on GITHUB related to the mode always staying 2pass-full. (or, at least, always reporting 2pass-full)

Interestingly, the encode seems to actually be faster on a UHD source on v5.10 vs. v5.09 -- even with 2pass-full always selected. I'm not sure that that might mean.

[jdobbs]

thanks for the description.

From my limited knowlege ... HDR10+, almost like DolbyVision, adds dynamic metadata to adjust brightness scene-by-scene, while HDR10 only uses static metadataJust an interesting aside on this subject. NVENCC has an option built in in which the additional information associated with HDR10+ can be copied from the original file automatically during encoding.

[cartman0208]

Just an interesting aside on this subject. NVENCC has an option built in in which the additional information associated with HDR10+ can be copied from the original file automatically during encoding.

Yep, found that, too ;)
Actually a lot of parameters can just be copied ... like colormatrix, master-display and so on, even the audio...
https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md

Doesn't that make your job a lot easier?

[jdobbs]

Yep, found that, too ;)
Actually a lot of parameters can just be copied ... like colormatrix, master-display and so on, even the audio...
https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md

Doesn't that make your job a lot easier?Yes, for NVEncC -- but I'll also have to make it work for X265 encoding. That means I'll probably have to create a JSON file from the extracted HEVC file, so it can be referenced from the command line -- which will add about 6-10 minutes to each job.

As for the other settings that can be copied... they are readily available in a BD structure and BD-RB already has the code to extract it and use it. My attention-to-detail tendencies also make me want to have control over things like that rather than "trust" other software.

Just a note on that. In my testing, I'm finding (as you might expect) that X265 is significantly more efficient than the NVIDIA hardware encoder. For example, if you encode some sources with a CQM of 25 using the hardware encoder you will get a file that is twice as large as one created by X265 with a CRF of 25. Of course you also have to factor in that the hardware encode is about 20-40x faster...

[Sharc]

Just a note on that. In my testing, I'm finding (as you might expect) that X265 is significantly more efficient than the NVIDIA hardware encoder. For example, if you encode some sources with a CQM of 25 using the hardware encoder you will get a file that is twice as large as one created by X265 with a CRF of 25. Of course you also have to factor in that the hardware encode is about 20-40x faster...
Would you say that the quality (in terms of metrics or by visual comparison) is about the same for the CQM=25 (HW, h.265) and and CRF=25 (SW, x265) encodes?

[jdobbs]

Would you say that the quality (in terms of metrics or by visual comparison) is about the same for the CQM=25 (HW, h.265) and and CRF=25 (SW, x265) encodes? I'm not sure. I don't like doing subjective comparisons, so I'll have to use AVISYNTH and do some SSIM testing.

More on the "--multipass" thing: It turns out that setting --vbrhq mode automatically sets the encoder to do 2 pass-full. So I'm not sure that there is actually any additional capability associated with that parameter other than it may provide a bit of granularity (with the ability to set 2pass-quarter).

[Mike-uk]

I'm not sure. I don't like doing subjective comparisons, so I'll have to use AVISYNTH and do some SSIM testing.

More on the "--multipass" thing: It turns out that setting --vbrhq mode automatically sets the encoder to do 2 pass-full. So I'm not sure that there is actually any additional capability associated with that parameter other than it may provide a bit of granularity (with the ability to set 2pass-quarter).

well yess compressing around 80 gig to 25 will have its tradeoff in quality, i think for h264 max quality, is like x264 medium not sure with 265

[Mike-uk]

hmm i wonder if the AMD Ryzen Threadripper 3970X Processor (32 Core / 64 Threads , 128 MB Cache, 4.5 GHz Boost) would bring x265 times down ? its only 1.8k for the chip :P

[laserfan]

The discussion of quality settings makes me smile. My first BD backup/conversion, in Oct 2008 before BD-RB was born iirc, was Live Free or Die Hard which as you all know is action-packed. Yet when compressed to less than 4GB DVD-size it looked flippin' awesome the couple times I played it. I will have to break it out sometime and see how it holds-up 12 years later!

:)

[jdobbs]

I've created a test release (v0.61.06) of BD Rebuilder for anyone who would like to experiment and report any issues they see with the new support for NVIDIA/NVENC support.

Please note that in order to use the new capability you must run BD-RB on a system that has an NVIDIA card installed that supports NVENC. You can find out more about which cards can be used at this link (https://developer.nvidia.com/video-encode-decode-gpu-support-matrix). BD-RB does a check when you attempt to select the NVENC encoder (under the SETTINGS menu).

There were a considerable number of changes to this release, so this version should be considered "for testing purposes only", so I'm not updating the first post of this thread -- please try it and let me know your experiences and report any bugs you find.

BD-RB v0.61.06 (https://jammernhilftnichts.de/jdobbs/BD-RBV06106.zip)

Thanks.

[Mark_Venture]

I've created a test release (v0.61.06) of BD Rebuilder for anyone who would like to experiment and report any issues they see with the new support for NVIDIA/NVENC support.

Please note that in order to use the new capability you must run BD-RB on a system that has an NVIDIA card installed that supports NVENC. You can find out more about which cards can be used at this link (https://developer.nvidia.com/video-encode-decode-gpu-support-matrix). BD-RB does a check when you attempt to select the NVENC encoder (under the SETTINGS menu).

There were a considerable number of changes to this release, so this version should be considered "for testing purposes only", so I'm not updating the first post of this thread -- please try it and let me know your experiences and report any bugs you find.

BD-RB v0.61.06 (https://jammernhilftnichts.de/jdobbs/BD-RBV06106.zip)

Thanks.Can I just say, I hate Norton... gives issues on the NVEncC.exe included with BD-RB (says RISK:WS.Reputation.1). didn't have issues with one I downloaded separately.

(had to restore and exclude this)

[cartman0208]

First encode looks pretty awesome, but I wanted to compare more closely, so I tried AviSynth interleave (first time for me) on the m2ts files

Immediately I noticed random artifacts on the reencoded file.

a=DirectShowSource("U:\FullDisc\OLYMPUS_HAS_FALLEN\BDMV\STREAM\00021.m2ts").Subtitle("O", align=2, size=30, text_color=$ffffff)
b=DirectShowSource("U:\BD-Output\OLYMPUS_HAS_FALLEN\BDMV\STREAM\00021.m2ts").Subtitle("NV", align=2, size=30, text_color=$ffffff)
return interleave(a, b)

Playing the resulting file alone is without artifacts...
Any Hints from the AviSynth pro's?

[Mark_Venture]

First encode of ALT-Movie Only (MKV Container, HEVC, NO_Resize, Intact Audio) of Avengers Endgame was quick. ABout 1hr 21 min.
[07/17/20] BD Rebuilder v0.61.06
[12:35:56] Source: AVENGERS_ENDGAME-4K_00004
- Input BD size: 59.49 GB
- Approximate total content: [03:01:11.527]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, HEVC, NO_RESIZE, Intact Audio
- Quality: High Quality (Default)
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[12:35:59] PHASE ONE, Encoding
- [12:35:59] Processing: VID_00055 (1 of 1)
- [12:35:59] Extracting A/V streams [VID_00055]
- [12:56:49] Reencoding video [VID_00055]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 260,656 frames
- [12:56:49] Reencoding: VID_00055, Pass 1 of 1
- [13:45:26] Video Encode complete
- [13:45:26] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4353 (eng): Keeping original audio
[13:45:26]PHASE ONE complete
[13:45:26]PHASE TWO - Rebuild Started
- [13:45:26] Building ALTERNATE OUTPUT Structure
[13:56:22] - Encode and Rebuild complete
[13:56:22] JOB: AVENGERS_ENDGAME-4K finished.



using the following ini...
[Options]
VERSION=0.61.0.6
ENCODER=1
MODE=3
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
DECODER=3
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=0
OUTPUT_SBS=1
NEROAAC=0
SUPTITLE=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=23500
PRIORITY_CLASS=0
TARGET_SIZE=23500
MOVIEONLY_TYPE=40
ALTCRF=19
ALT_TARGET=8096
ALTMETHOD=0
ALTAUTOCROP=0
QUICK_EXTRAS=1
AUDIO_DRC=0
PGSTOSRT=0
ALT_CRF_TARGET=1024
FRIM_SW_DECODE=0
FRIM_SW_ENCODE=0
NVENC_CAPABLE=1

[Paths]
SupTitlePath=C:\Program Files (x86)\AviSynth\plugins\SupTitle.dll
SOURCE_PATH=H:\BLURAY\AVENGERS_ENDGAME-4K\
WORKING_PATH=F:\BLURAY-WORKING\
DGIndexNV=D:\BD_Rebuilder\dgdecnv\DGIndexNV.exe
DGDecNV=D:\BD_Rebuilder\dgdecnv\DGDecodeNV.dll
General
Unique ID : 220642287505551334163210721554557699978 (0xA5FE28AA6D37327D898374BC265A078A)
Complete name : F:\BluRay-Working\AVENGERS_ENDGAME-4K.mkv
Format : Matroska
Format version : Version 2
File size : 27.7 GiB
Duration : 3 h 1 min
Overall bit rate mode : Variable
Overall bit rate : 21.9 Mb/s
Encoded date : UTC 2020-07-17 17:45:32
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@L5@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 3 h 1 min
Bit rate : 16.1 Mb/s
Width : 3 840 pixels
Height : 2 160 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 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.081
Stream size : 20.3 GiB (73%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2

Audio #1
ID : 2
Format : MLP FBA 16-ch
Format/Info : Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Codec ID : A_TRUEHD
Duration : 3 h 1 min
Bit rate mode : Variable
Bit rate : 4 777 kb/s
Maximum bit rate : 8 430 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 1 200.000 FPS (40 SPF)
Compression mode : Lossless
Delay relative to video : 1 ms
Stream size : 6.05 GiB (22%)
Language : English
Default : Yes
Forced : No
Number of dynamic objects : 13
Bed channel count : 1 channel
Bed channel configuration : LFE

Audio #2
ID : 3
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 3 h 1 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 829 MiB (3%)
Service kind : Complete Main
Default : No
Forced : No

Audio #3
ID : 4
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 3 h 1 min
Bit rate mode : Constant
Bit rate : 320 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 415 MiB (1%)
Language : English
Service kind : Complete Main
Default : No
Forced : No

Text
ID : 5
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 0 min
Bit rate : 11.5 kb/s
Count of elements : 5266
Stream size : 14.9 MiB (0%)
Language : English
Default : No
Forced : No

Menu
00:00:00.000 : en:00:00:00.000
00:08:06.068 : en:00:08:06.068
00:20:01.867 : en:00:20:01.867
00:26:15.448 : en:00:26:15.448
00:36:57.340 : en:00:36:57.340
00:43:20.764 : en:00:43:20.764
00:48:44.338 : en:00:48:44.338
00:57:36.911 : en:00:57:36.911
01:07:12.778 : en:01:07:12.778
01:16:02.683 : en:01:16:02.683
01:26:25.597 : en:01:26:25.597
01:32:20.284 : en:01:32:20.284
01:38:55.971 : en:01:38:55.971
01:48:12.527 : en:01:48:12.527
01:57:27.081 : en:01:57:27.081
02:05:00.409 : en:02:05:00.409
02:15:06.598 : en:02:15:06.598
02:25:50.616 : en:02:25:50.616
02:34:38.102 : en:02:34:38.102
02:43:04.065 : en:02:43:04.065
02:49:05.510 : en:02:49:05.510
03:01:11.277 : en:03:01:11.277

Original M2TS on disc 59.4 GB, resulting file from BD-RB is 27.6GB, so a nice reduction in size.

Playback on my 1080p monitor looked good. Will check on my 4K TV as soon as I get a chance to step away from my desk.

I also just started a Full Backup to BD-25.. Will post results in a little bit.


NOTE: my graphics card is an EVGA GTX 1660ti XC Ultra Gaming 06G-P4-1267-KR (full PC spec's HERE (https://forum.doom9.org/showpost.php?p=1918386&postcount=45) )

[Sharc]

First encode looks pretty awesome, but I wanted to compare more closely, so I tried AviSynth interleave (first time for me) on the m2ts files

Immediately I noticed random artifacts on the reencoded file.

a=DirectShowSource("U:\FullDisc\OLYMPUS_HAS_FALLEN\BDMV\STREAM\00021.m2ts").Subtitle("O", align=2, size=30, text_color=$ffffff)
b=DirectShowSource("U:\BD-Output\OLYMPUS_HAS_FALLEN\BDMV\STREAM\00021.m2ts").Subtitle("NV", align=2, size=30, text_color=$ffffff)
return interleave(a, b)

Playing the resulting file alone is without artifacts...
Any Hints from the AviSynth pro's?
Don't use DirectShowSource. Make .dgi index files of the 2 files (original and encoded) instead.

[cartman0208]

Don't use DirectShowSource. Make .dgi index files of the 2 files (original and encoded) instead.

.dgi sounds like DGDecNV ... Oh well, seems I have to invest that money ..:p

[Sharc]

BD-RB does a check when you attempt to select the NVENC encoder (under the SETTINGS menu).

Encoding a HD BD 1920x1080 source with NVEnc is done with h264 (AVC) only. I can't select h265 (HEVC). Is this because my 1050ti does not support B-frames for HEVC?
Not that it matters, it's just a question.

[cartman0208]

Encoding a HD BD 1920x1080 source with NVEnc is done with h264 (AVC) only. I can't select h265 (HEVC). Is this because my 1050ti does not support B-frames for HEVC?
Not that it matters, it's just a question.

HEVC is for UHD-BD only ... wouldn't be compliant with (Full-HD) BD
I think BD-RB has always been like that (also with x264/x265) to be compliant with disc standards.

Seems to work for Alternate Encoding though :cool:

[jdobbs]

Encoding a HD BD 1920x1080 source with NVEnc is done with h264 (AVC) only. I can't select h265 (HEVC). Is this because my 1050ti does not support B-frames for HEVC?
Not that it matters, it's just a question.It follows the same rules as X265/X264. The only way to force a 1920x1080 source to HEVC would be with ALTERNATE output.

I am working on that ability -- to create a 1080p HEVC (UHD format) disc -- but I disabled that code for this release because I haven't tested it very well.HEVC is for UHD-BD only ... wouldn't be compliant with (Full-HD) BD
I think BD-RB has always been like that (also with x264/x265) to be compliant with disc standards.

Seems to work for Alternate Encoding though :cool:The UHD standard also allows 1080p using HEVC. So that part should be available soon. See the table below from the Part 3 Whitepaper.

But, just as an aside... I have tried other formats (720p and 480p) using HEVC and UHD (V3) disc output and they also play on my Sony player -- so I might put a hidden option that allows HEVC there as well. It would be a great non-standard-but-working capability for creating series discs, since HEVC looks a lot better at lower bitrates. I'm usually hesitant to step out of the standard -- but I'd bet that most UHD players will accept it since the format/type tables have settings for it.

[cartman0208]

I am working on that ability -- to create a 1080p HEVC (UHD format) disc -- but I disabled that code for this release because I haven't tested it very well.

Can you implement that as Alternate Output setting for HEVC with AC3, too?
Would be a nice addition, because my SamsungTV can't play DTS and some older SmartTV models had trouble playing AAC ...

AC3 just plays everywhere :)

[jdobbs]

Can you implement that as Alternate Output setting for HEVC with AC3, too?
Would be a nice addition, because my SamsungTV can't play DTS and some older SmartTV models had trouble playing AAC ...

AC3 just plays everywhere :)You can easily create a preset that uses AC3 by editing the ALTERNATE.TXT file in the Misc folder. The comment area at the beginning of the file explains the settings. Here's an example you could try:

[00041]
caption=MKV Container, HEVC, NO_RESIZE, Auto-AC3
vEncoder=1
vBitrate=1500
vKeyint=Auto
aBitrate=*
aType=0
vFormat=7
cType=1

I used [00041] because the default ALTERNATE.TXT file has 40 entries in it. Just adjust if yours has more or fewer. You could also replace one of the existing presets if you'd like that better.

Honestly I thought I'd put one in there. I'm surprised that I didn't.

[cartman0208]

You can easily create a preset that uses AC3 by editing the ALTERNATE.TXT file in the Misc folder.

Wow, I've never noticed that file ... :thanks:

[jdobbs]

Encoding a HD BD 1920x1080 source with NVEnc is done with h264 (AVC) only. I can't select h265 (HEVC). Is this because my 1050ti does not support B-frames for HEVC?
Not that it matters, it's just a question.It follows the same rules as X265/X264. The only way to force a 1920x1080 source to HEVC would be with ALTERNATE output.

I am working on that ability -- to create a 1080p HEVC (UHD format) disc -- but I disabled that code for this release because I haven't tested it very well.The UHD standard also allows 1080p using HEVC. So that part should be available soon.If you'd like to experiment with the capability to output 1080p to disc using HEVC into a UHD format, try adding:

UHD_V3_MODE=1

...to your INI file. I haven't tested it much, but I'm pretty sure it would only work in movie-only mode right now. Don't forget to reset it to 0 after playing with it -- as it will try to make normal BD backups into UHD format.

[Edit] Nope... sorry. I just ran a test on a 1080p source and, while it played, BD-RB failed to add the "--repeat-headers" parameter in the encode and FF/REW/CHAP isn't working (for 1080p output). I fixed it for the next release.

[prologic]

Tested BD-RB v0.61.06
With Movie LE_MANS_66 UHD 60gig to BD50 using geforce gtx 1070 card.
Worked a treat .Took about 1 hour to do .Very pleased with the result , on my oppo 203 Player , with all the menus and such .
Here is the log:
[07-18-20] BD Rebuilder v0.61.06
[12:27:33] Source: LE_MANS_66
- Input BD size: 60.18 GB
- Approximate total content: [02:43:59.496]
- Target BD size: 46.26 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Very Good (Very Fast), ABR
- X264 Tweak(s) enabled
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=1 DTS=1 HD=1 Kbs=640
[12:27:33] PHASE ONE, Encoding
- [12:27:33] Processing: VID_00006 (1 of 1)
- [12:27:33] Extracting A/V streams [VID_00006]
- Extracting video streams [VID_00006]
- Extracting audio/subtitle streams [VID_00006]
- [12:33:35] Reencoding video [VID_00006]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23.976fps, 219,511 frames
- Bitrate: 31,380 Kbs
- [12:33:35] Reencoding: VID_00006, Pass 1 of 1
- [13:21:57] Video Encode complete
- [13:21:57] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [13:21:57] Multiplexing M2TS
[13:26:07]PHASE ONE complete
[13:26:07]PHASE TWO - Rebuild Started
- [13:26:07] Rebuilding BD file Structure
[13:26:17] - Encode and Rebuild complete
[13:26:17] JOB: LE_MANS_66 finished.

[cartman0208]

I'm having trouble converting UHD BDs in CQM Mode ... each one I tried so far fails on CQM prediction
[07.18.20] BD Rebuilder v0.61.06
[21:57:28] Source: COLD_PURSUIT
- Input BD size: 78,62 GB
- Approximate total content: [02:04:46.291]
- Target BD size: 47,85 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), CQM
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[21:57:33] PHASE ONE, Encoding
- [21:57:33] Processing: VID_00000 (1 of 14)
- [21:57:33] Extracting A/V streams [VID_00000]
- [21:57:38] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 1.046 frames
- [21:57:38] Performing CQM Prediction...
- Analyzing 17,35 [21:57:42] - Failed video encode, aborted


VBR runs fine

Which one would you suggest for quality?

[jdobbs]

I'm having trouble converting UHD BDs in CQM Mode ... each one I tried so far failes on CQM prediction


VBR runs fine

Which one would you suggest for quality? I think it may be too early to call for quality -- but I suspect it might be CQM. I wouldn't make a wager on that though until a lot more testing is done.

Can you -- right after the encode fails:

1. Copy the content of LASTCMD.TXT (in the BD-RB folder) and post it here.

2. Cut and paste the command line from that file into a DOS prompt window and try to run it, and see what error it gets.

Hmm... I wonder if the routine is inserting a "," instead of a "." when specifying the CQM value on the command line because of European notation for the decimal place?

Thanks.

[jdobbs]

Tested BD-RB v0.61.06
With Movie LE_MANS_66 UHD 60gig to BD50 using geforce gtx 1070 card.
Worked a treat .Took about 1 hour to do .Very pleased with the result , on my oppo 203 Player , with all the menus and such.Thanks for testing and posting the result. Appreciated.

One thing I see... since X264 isn't being used, I guess the message saying "tweaks enabled" isn't applicable and shouldn't be logged.

[cartman0208]

"U:\BD_Rebuilder\tools\nvenc\nvencc.exe" --avhw -i "U:\BD-OUTPUT\WORKFILES\00008.AVS.SMPL.m2ts" --codec hevc --preset quality --profile main10 --output-depth 10 --repeat-headers --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) --qp-min 0 --vbr 0 --vbr-quality 1 --aq-temporal --keyfile "U:\BD-OUTPUT\WORKFILES\VID_00008.CHP" --sar 1:1 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 -o "U:\BD-OUTPUT\WORKFILES\TEMP.265"


and the result from command line:


--------------------------------------------------------------------------------
U:\BD-OUTPUT\WORKFILES\TEMP.265
--------------------------------------------------------------------------------
avcuvid: size of input file "U:\BD-OUTPUT\WORKFILES\00008.AVS.SMPL.m2ts" is 0
failed to initialize file reader(s).
Failed to open input file.

[jdobbs]

and the result from command line:Ok... I see. It looks like the input file is too short for BD-RB to create a sample. I guess I never thought about that possibility when I added the new sampling method for HEVC.

There's only 1 frame in that file? I'm surprise it is even in the list to be encoded... you must have set the minimum encode length to 0, maybe?

Would you mind posting the contents of your BDREBUILDER.INI file?

[cartman0208]

Ok... I see. It looks like the input file is too short for BD-RB to create a sample. I guess I never thought about that possibility when I added the new sampling method for HEVC.

There's only 1 frame in that file? I'm surprise it is even in the list to be encoded... you must have set the minimum encode length to 0, maybe?

Would you mind posting the contents of your BDREBUILDER.INI file?

The input file should have 160k frames

[22:37:53] PHASE ONE, Encoding
- [22:37:53] Processing: VID_00008 (5 of 14)
- [22:38:24] Reencoding video [VID_00008]
- Source Video: HEVC, 3840x2160
- Rate/Length: 24,000fps, 160.215 frames
- [22:38:24] Performing CQM Prediction...
- Analyzing 1,00 [22:38:28] - Failed video encode, aborted[/QUOTE]

[QUOTE][Options]
AC3_192=0
AC3_640=1
AC3_REENCODE=0
ALTAUTOCROP=1
ALTCRF=20
ALTMETHOD=0
ALT_CRF_TARGET=1024
ALT_TARGET=1024
ASSUME_DVD_PAL=0
AUDIO_DRC=0
AUDIO_TO_KEEP=deu;eng;ger;
AUDIO_TRACK_LIMIT=1
AUTO_BURN=2
AUTO_QUALITY=0
AVCHD=1
BD25_SIZE=24500
BD50_SIZE=49000
BDMV_CERT_ONLY=0
COMPLETION_BEEP=0
CONVERT_WIDE=0
CUSTOM_TARGET_SIZE=23500
DECODER=0
DEINTERLACE=0
DTS_REENCODE=0
ENCODER=1
ENCODE_QUALITY=3
FRIMSOURCE=0
IGNORE_3D=0
IVTC_PULLDOWN=0
KEEP_HD_AUDIO=0
MODE=0
MOVIEONLY_TYPE=4
NEROAAC=0
NVENC_CAPABLE=1
ONEPASS_ENCODING=2
OPEN_GOP=0
OUTPUT_SBS=0
PGSTOSRT=0
REMOVE_OUTPUT=0
REMOVE_WORKFILES=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
SD_CONVERT=0
SD_TO_1080=0
SUBS_TO_KEEP=all
SUBTITLE_TRACK_LIMIT=1
SUPTITLE=0
TARGET_SIZE=49000
USE_FILTERS=0
VERSION=0.61.0.6
MENU_BACKGROUND=U:\BD_Rebuilder\misc\menuback.jpg
MENU_AUDIO=U:\BD_Rebuilder\tools\blankclip\blank.ac3
IMPORT_THRESHOLD=1
QUICK_PLAY_THRESHOLD=1
MENU_AUTO_BACKGROUND=1
MENU_AUTO_DVDAUDIO=1
MENU_PLAY_SEQUENTIAL=0
MENU_START_WITH_MENU=1
IMPORT_LIMIT_LANG=0
IMPORT_KEEP_PLAYALL=0
IMPORT_PREPARE_MKV=0
[Paths]
SOURCE_PATH=U:\FULLDISC\COLD_PURSUIT\
WORKING_PATH=U:\BD-OUTPUT\
DGIndexNV=U:\Tools\dgdecnv2053\x32 Binaries\DGIndexNV.exe
DGDecNV=U:\Tools\dgdecnv2053\x32 Binaries\DGDecodeNV.dll

[jdobbs]

The input file should have 160k framesNot in the log that you posted:

[21:57:33] PHASE ONE, Encoding
- [21:57:33] Processing: VID_00000 (1 of 14)
- [21:57:33] Extracting A/V streams [VID_00000]
- [21:57:38] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160

The 160 frames is for an entirely different M2TS (VID_00008). (5 of 14)

- [22:37:53] Processing: VID_00008 (5 of 14)
- [22:38:24] Reencoding video [VID_00008]
- Source Video: HEVC, 3840x2160


Looking back at it now, though, it looks like even that one had over 1000 frames (I got confused by the use of "." rather than ",")

[cartman0208]

Sorry, that was the same movie, I just wanted some progress while waiting ;)
I did the 1st vid ... when that failed, I posted that and switched to VBR
When you asked for that command line, I was on the 5th vid of that movie, switched back to CQM, and posted the log...
Sorry again for the confusion :rolleyes:

Should I switch regional settings on my OS?

[cartman0208]

Hmm... I wonder if the routine is inserting a "," instead of a "." when specifying the CQM value on the command line because of European notation for the decimal place?


Good hint ... and guess what?

Should I switch regional settings on my OS?

That worked!
I set decimal separator to "." and digit grouping to "," (like here (https://www.officetooltips.com/office_2016/tips/how_to_change_decimal_symbol_and_digit_grouping_symbol_in_windows_10.html) ) and now the encode runs fine in CQM mode...

But I'd rather have my settings back to normal :scared: