BD Rebuilder Beta - Bug Reports Only

[jdobbs]

Yes, same source per my example above (The Matrix 1080p blu-ray). That's the whole point of this, to convert non-UHD BD discs to UHD-BD (HEVC) format per jdobbs quote above. And yes, I'm getting 150+ fps on the Highest Quality (slowest) setting with NVENC and a Ryzen 2700X. If I set it to Automatic it soars to over 250+ fps, amazing!

Still only one pass, so the jury is still out on the picture quality differences compared to x265 two pass and L5.1 vs NVENC one pass and L4.1. Maybe someone can try both and chime in. Thanks for all your replies...Makes you wonder why you didn't start encoding with NVENCC earlier doesn't it? At least that's the case for me.

Try encoding using CQM -- that way you know you are getting quality roughly equal to X265 (at least in my tests).

[jdobbs]

@spotswood

I just did a 1080p HEVC encode using the default setting (High Quality) and my GTX-1660 is getting ~340 frames per second. At the Highest setting I'm getting a little over 160 frames per second.

[spotswood]

Makes you wonder why you didn't start encoding with NVENCC earlier doesn't it? At least that's the case for me.

Try encoding using CQM -- that way you know you are getting quality roughly equal to X265 (at least in my tests).Yeah, no s**t! Just tried it...

----------------------
[03/14/21] BD Rebuilder v0.61.21
[13:28:09] Source: THE_FIFTH_ELEMENT_00001
- Input BD size: 35.37 GB
- Approximate total content: [02:05:53.546]
- Target BD size: 25.00 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), CQM
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[13:28:09] PHASE ONE, Encoding
- [13:28:09] Processing: VID_00001 (1 of 1)
- [13:28:09] Extracting A/V streams [VID_00001]
- [13:31:58] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 181,104 frames
- [13:31:58] Performing CQM Prediction...
- Analyzing 6.00
[13:32:00] - Failed video encode, aborted

Uh oh, here we go again. But I went back and found your post about using FIXED_CRF=n. When using your starting point of 28 it worked, although the resulting job finished a little undersized. After a couple attempts (thanks to NVENC) I settled on 19, which gave me a finished size of 25GB, right on target.

@spotswood

I just did a 1080p HEVC encode using the default setting (High Quality) and my GTX-1660 is getting ~340 frames per second. At the Highest setting I'm getting a little over 160 frames per second.Yeah, I'm sure your 1660 is a little faster than my 1060. Thought about upgrading but the prices are still a little too high for me. Think I'll stick with this poor man's UHD for the time being... ;^)

[spotswood]

Try encoding using CQM -- that way you know you are getting quality roughly equal to X265 (at least in my tests).So here's a couple screenshots from The Fifth Element using that famous close-up of Leeloo at 30:38. The first one is with x265 HEVC High Quality Two-Pass (the one that took 12+ hours). The second is using NVENC HEVC Highest Quality CQM Fixed_Crf=19 (that only took 30min). I'll be damned if they don't look exactly the same! I'm sold, guess I'll be using NVENC from now on... :D

[spotswood]

I personally would use aBitrate=640 and aType=0 for AC3 640kb, since some audio streams can be quite big...
On the other hand I'm not that audiophile like some others :DYeah, that's what I usually use for BD9 w/5.1 tracks. If a title uses a 7.1 ATMOS or DTS:X track, I'll keep it. I haven't noticed a difference in video at BD25. At BD9, well then yeah I use the AC3 or DTS core tracks.

Since the compression of audio with AC3 5.1 @640kbs has been proven to be invisible to the human ear in laboratory double-blind tests... I call that a rational decision.Exactly! I've been using your advise since way back. My ears can't tell the difference... :D

[cartman0208]

...
Yeah, I'm sure your 1660 is a little faster than my 1060. ...

Not only that ... the 1660 was the cheapest solution supporting B-Frames on HEVC (when I bought it over a year ago), giving you even more Quality per megabyte ;)

[varekai]

Who is the manufacturer, name, specs., of your GTX1660 6GB?
Found lots of different names and specs...
ASUS, Gigabyte, MSI, Gainward, Palit, PNY, EVGA, Zotac...
Thanks for any info.
Best regards,
varekai

[jdobbs]

Who is the manufacturer, name, specs., of your GTX1660 6GB?
Found lots of different names and specs...
ASUS, Gigabyte, MSI, Gainward, Palit, PNY, EVGA, Zotac...
Thanks for any info.
Best regards,
varekaiThe one I bought was an MSI VENTUS XS w/6GB -- but that's just because it happened to be the cheapest one they had on-the-shelf at Microcenter (or the only one, I don't remember). I didn't do any comparison shopping. This one can be overclocked -- but I run it at standard speed.

I've been told that GTX-1660s have gotten popular and are getting harder to find (and more expensive) -- but I haven't really done any research. I bought mine for $238.

[spotswood]

The one I bought was an MSI VENTUS XS w/6GB -- but that's just because it happened to be the cheapest one they had on-the-shelf.

I've been told that GTX-1660s have gotten popular and are getting harder to find (and more expensive) -- but I haven't really done any research. I bought mine for $238.When I was looking to upgrade my GTX-1050 the prices for the GTX-1660's were around what you paid. I had one in my cart at Amazon, but waited too long and by the time I was ready they were north of $600+ :eek:! I ended up with a Zotac GTX-1060 6GB Factory Refurb I found on eBay for $225. Sold my GTX-1050 to offset the cost a little, figured it was the best I could do. Don't think prices will be coming down to what you paid anytime soon...

BTW... what email do I use for a donation? My stimulus check hit my account today... ;^)

[jdobbs]

BTW... what email do I use for a donation? My stimulus check hit my account today... ;^)dvd-rb@jdobbs.net

Thanks for thinking about me.

[spotswood]

dvd-rb@jdobbs.net

Thanks for thinking about me.Done, on it's way! Thanks for all your hard work! Keep it going!

[varekai]

@jdobbs
@spotswood
Thanks for info, I also noticed the GTX1660 prices are high.

[Mark_Venture]

Not only that ... the 1660 was the cheapest solution supporting B-Frames on HEVC (when I bought it over a year ago), giving you even more Quality per megabyte ;)I've read the Turing NVENC encoder gives improvements in quality, in addition to B Frame support. Is that correct? Or is it just the B-frames that is making the difference?

I do know that the GTX1660, GTX1660ti, RTX20x0/30x0, and GTX1650Super use the Turing NVENC chip. But the original GTX1650 still uses the Volta (basically Pascal) encoder so it lacks B-frames and performs like the GTX10x0 line.

I've never really done a side by side comparison as I've never had a GTX10X0 card, but I can say I have notice a marked improvement in video quality when using NVENC with my GTX1660ti vs my GTX970.

[jdobbs]

Done, on it's way! Thanks for all your hard work! Keep it going!Really appreciated. Thanks!

[LowDead]

I'm getting an error in the META file. BDRB thinks the video is a .264 file and puts ****.264 for muxing in the META file. The original file is .hevc and BDRB also correctly saves that file as .hevc but puts wrong extension in the META file.
This has only happened to me in the latest version of BDRB and I haven't yet run it with an older version. Will try also another title to see if it is repeatable.

Also want to point out that I do know I have the wrong avisynth installed. The reason for that is to get compability with other software. Of course it could be this that makes it error out but because I have never gotten this error before it might not be related and
before I test to install the right version of avisynth I will try earlier version of BDRB and also check for another title to try.

LOG:

[03-14-21] BD Rebuilder v0.61.21
[19:44:25] Source: Cinema Paradiso (Theatrical) 4K UHD
- Input BD size: 90,40 GB
- Approximate total content: [03:35:16.728]
- Target BD size: 47,07 GB
- Windows Version: 6.2 [9200]
- Quality: High Quality (Default), Two Pass
- UHD-BD source detected.
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[19:44:27] PHASE ONE, Encoding
- [19:44:27] Processing: VID_00000 (1 of 7)
- [19:44:27] Extracting A/V streams [VID_00000]
- [19:44:33] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 471 frames
- Bitrate: 1 038 Kbs
- [19:44:33] Reencoding: VID_00000, Pass 1 of 2
- [19:44:36] Reencoding: VID_00000, Pass 2 of 2
- [19:44:38] Video Encode complete
- [19:44:38] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [19:44:38] Multiplexing M2TS
- [19:44:42] Processing: VID_00001 (2 of 7)
- [19:44:42] Extracting A/V streams [VID_00001]
- [20:22:05] Reencoding video [VID_00001]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 176 826 frames
- Bitrate: 43 840 Kbs
- [20:22:05] Reencoding: VID_00001, Pass 1 of 2
- [20:41:29] Reencoding: VID_00001, Pass 2 of 2
- [17:54:41] Video Encode complete
- [17:54:41] Processing audio tracks
- Track 4352 (ita): Keeping original audio
- Track 4353 (ita): Keeping original audio
- Track 4354 (eng): Keeping original audio
- [17:54:41] Multiplexing M2TS
- [18:08:22] Processing: VID_00005 (3 of 7)
- [18:08:22] Extracting A/V streams [VID_00005]
- [18:08:41] Reencoding video [VID_00005]
- Source Video: HEVC, 1920x1080
- Rate/Length: 59,940fps, 98 692 frames
- Bitrate: 1 858 Kbs
- [18:08:41] Reencoding: VID_00005, Pass 1 of 2
- [18:55:10] Reencoding: VID_00005, Pass 2 of 2
- [19:34:59] Video Encode complete
- [19:34:59] Processing audio tracks
- Track 4352 (ita): Keeping original audio
- [19:34:59] Multiplexing M2TS
EXIT CODE: -2
- Error in attempt to multiplex: MUX_00005.meta
- Can't open file: D:\WORK\WORKFILES\VID_00005.AVS.264
[19:35:03] - Failed to build structure, aborted[03-19-21] Checking System Settings
- BD-Rebuilder v0.61.21
- Windows Version: 6.2 [9200]
- Working Path Free Space: 113,03GB
- AVISYNTH Version: 3.6.1.0, not recommended version
- LAVFILTERS: Ok
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[03-19-21] Systems Settings Check complete


Original file:

General
ID : 0 (0x0)
Complete name : A:\UHDBD\Cinema Paradiso (Theatrical) 4K UHD\BDMV\CLIPINF\00005.clpi
Format : Blu-ray Clip info
File size : 9.52 KiB
Duration : 27 min 26 s
Overall bit rate mode : Variable
Overall bit rate : 4 521 kb/s
Maximum Overall bit rate : 109 Mb/s
OverallBitRate_Precision_Min : 4521253
OverallBitRate_Precision_Max : 4521256

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
Codec ID : 36
Duration : 27 min 26 s
Bit rate : 4 139 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.033
Stream size : 812 MiB
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
format_identifier : HDMV
Source : 00005.m2ts

Audio
ID : 4352 (0x1100)
Menu ID : 1 (0x1)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 129
Duration : 27 min 26 s
Bit rate mode : Constant
Bit rate : 192 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 : 37.7 MiB
Language : Italian
Service kind : Complete Main
bsid : 8
Dialog Normalization : -31
Dialog Normalization : -31 dB
compr : -0.28
compr : -0.28 dB
dsurmod : 1
dsurmod : Not Dolby Surround encoded
acmod : 2
lfeon : 0
dialnorm_Average : -31
dialnorm_Average : -31 dB
dialnorm_Minimum : -31
dialnorm_Minimum : -31 dB
dialnorm_Maximum : -31
dialnorm_Maximum : -31 dB
dialnorm_Count : 2389
compr_Average : -2.42
compr_Average : -2.42 dB
compr_Minimum : -13.84
compr_Minimum : -13.84 dB
compr_Maximum : 6.02
compr_Maximum : 6.02 dB
compr_Count : 2380
dynrng_Average : -2.38
dynrng_Average : -2.38 dB
dynrng_Minimum : -13.68
dynrng_Minimum : -13.68 dB
dynrng_Maximum : 5.88
dynrng_Maximum : 5.88 dB
dynrng_Count : 2386
format_identifier : AC-3
Source : 00005.m2ts

Text
ID : 4608 (0x1200)
Menu ID : 1 (0x1)
Format : PGS
Codec ID : 144
Duration : 26 min 46 s
Delay relative to video : 5 s 72 ms
Language : English
Source : 00005.m2ts



Last command:

"C:\Vidsoft\BD_Rebuilder\tools\ffmpeg.exe" -probesize 100MB -i "A:\UHDBD\Cinema Paradiso (Theatrical) 4K UHD\BDMV\STREAM\00005.m2ts" -an -pix_fmt yuv420p10le -f yuv4mpegpipe -strict -1 - | "C:\Vidsoft\BD_Rebuilder\tools\x265-64.exe" - --preset medium --profile main10 --uhd-bd --repeat-headers --vbv-bufsize 45000 --vbv-maxrate 48000 --colorprim bt709 --transfer bt709 --colormatrix bt709 --fps 59.97 --sar 1:1 --qpfile "D:\WORK\WORKFILES\VID_00005.CHP" --keyint 60 --bitrate 1858 --y4m --stats "D:\WORK\WORKFILES\VID_00005.AVS.hevc.stats" --pass 2 --output "D:\WORK\WORKFILES\VID_00005.AVS.hevc"


//LD

[cartman0208]

I've read the Turing NVENC encoder gives improvements in quality, in addition to B Frame support. Is that correct? Or is it just the B-frames that is making the difference?

I do know that the GTX1660, GTX1660ti, RTX20x0/30x0, and GTX1650Super use the Turing NVENC chip. But the original GTX1650 still uses the Volta (basically Pascal) encoder so it lacks B-frames and performs like the GTX10x0 line.

I've never really done a side by side comparison as I've never had a GTX10X0 card, but I can say I have notice a marked improvement in video quality when using NVENC with my GTX1660ti vs my GTX970.

Taken from Wikipedia (https://en.wikipedia.org/wiki/Video_compression_picture_types)

Three types of pictures (or frames) are used in video compression: I, P, and B frames.

An I‑frame (Intra-coded picture) is a complete image, like a JPG or BMP image file.

A P‑frame (Predicted picture) holds only the changes in the image from the previous frame. For example, in a scene where a car moves across a stationary background, only the car's movements need to be encoded. The encoder does not need to store the unchanging background pixels in the P‑frame, thus saving space. P‑frames are also known as delta‑frames.

A B‑frame (Bidirectional predicted picture) saves even more space by using differences between the current frame and both the preceding and following frames to specify its content.

P and B frames are also called Inter frames. The order in which the I, P and B frames are arranged is called the Group of pictures.


So HEVC created with pre-Turing only consists of P- and I-Frames. Since B-Frames are even smaller, the same quality setting should result in smaller video-filesize
Or the other way around you can increase the quality level to reach the same filesize

[spotswood]

Really appreciated. Thanks!No worries! Really appreciate your hard work!


----------------------
[03/14/21] BD Rebuilder v0.61.21
[13:28:09] Source: THE_FIFTH_ELEMENT_00001
- Input BD size: 35.37 GB
- Approximate total content: [02:05:53.546]
- Target BD size: 25.00 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), CQM
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[13:28:09] PHASE ONE, Encoding
- [13:28:09] Processing: VID_00001 (1 of 1)
- [13:28:09] Extracting A/V streams [VID_00001]
- [13:31:58] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 181,104 frames
- [13:31:58] Performing CQM Prediction...
- Analyzing 6.00
[13:32:00] - Failed video encode, aborted
Can you look into why all my 1080p titles I'm trying to reencode to HEVC fail at the CQM prediction? I can use FIXED_CRF=n, but it's a trial and error to get the sizing I want. The standard 2160p UHD titles I've tried perform the CQM prediction as expected.

As for the levels -- BD-RB leaves it to the encoder (both have defaults set at auto). But I'm surprised they are different, since the settings for encoding are virtually identical. The level is usually influenced by the maximum bitrate selected by BD-RB. But it is the same for both encoders. I'll take a look at it and see why they are different. Any ideas on the difference in the levels (L4.1 vs L5.1) between the two encoders? Does it affect quality? Can/should L5.1 be forced in NVENC? x265 seems to use L5.1 on everything.


A couple things I noticed with Convert BD to UHD... I tried with Movie and Menus selected, and in the log it shows "Converting to UHD-BD (HEVC)". But when selecting "Movie Only" mode the same log notation is not shown. I do have "Convert BD to UHD-BD (HEVC)" selected. The resulting job is in fact HEVC, it's just not shown in the log as in M&M mode.Probably just a typo but thought I'd mention it. That's it for now! Thanks again!

[MrVideo]

Any ideas on the difference in the levels (L4.1 vs L5.1) between the two encoders? Does it affect quality? Can/should L5.1 be forced in NVENC? x265 seems to use L5.1 on everything.!
The levels really have nothing to do with the actual encoding. It doesn't provide any settings. It indicates the capabilities of the encoded video. It is up to the user to set the encoding parameters so that they match the spec for that particular level.

See: https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding_tiers_and_levels

[jdobbs]

The levels really have nothing to do with the actual encoding. It doesn't provide any settings. It indicates the capabilities of the encoded video. It is up to the user to set the encoding parameters so that they match the spec for that particular level.

See: https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding_tiers_and_levelsExactly. It really just a tag the accompanies the video. I'd still like to understand, though, why X265 and NVENCC tag different levels when the settings (max bitrate, etc) are the same.

[jdobbs]

Can you look into why all my 1080p titles I'm trying to reencode to HEVC fail at the CQM prediction? I can use FIXED_CRF=n, but it's a trial and error to get the sizing I want. The standard 2160p UHD titles I've tried perform the CQM prediction as expected. I'm at a loss. I use the prediction setting all the time (almost every day), and I've never had a problem.

Something you could try:

1. Set BD-RB up to run with the prediction.
2. Let it start and then fail.
3. Go to the BD Rebuilder folder and look for a file called LASTCMD.TXT
4. Open the file (with NOTEPAD) and cut the command line that is represented there.
5. Open a CMD window, and paste the command.
6. Run it and see what error you get.

Then mark/cut-and-paste the information from the CMD window to this thread so I can see the error.

[jdobbs]

@LowDead

Can you post the META file that causes the issue you reported? Just to be clear, the encode went correctly and created a .hevc file -- but when it tried to rebuild the META referenced a .264 file, right?

I suspect it has something to do with this:

- Rate/Length: 59,940fps, 98 692 frames

[LowDead]

@LowDead

Can you post the META file that causes the issue you reported? Just to be clear, the encode went correctly and created a .hevc file -- but when it tried to rebuild the META referenced a .264 file, right?

I suspect it has something to do with this:

- Rate/Length: 59,940fps, 98 692 frames

You are correct. I accidentally deleted the workfolder so I had to redo. To save time I switched encoder and did a faster encode for extras. And it was repeatable. This time it errored out on a different one, MUX_00007.meta.

Here comes the content of it:

MUXOPT --no-pcr-on-video-pid --new-audio-pes --hdmv-descriptors --blu-ray --vbr --auto-chapters=5 --vbv-len=500 --start-time=27000000
V_MPEG4/ISO/AVC, "B:\WORK\FULLDISC\WORKFILES\VID_00007.AVS.264", fps=59.94, insertSEI, contSPS
A_AC3, "B:\WORK\FULLDISC\WORKFILES\00007.track_4352.AC3", lang=ita
S_HDMV/PGS, "B:\WORK\FULLDISC\WORKFILES\00007.track_4608.sup",lang=eng


//LD

[spotswood]

The levels really have nothing to do with the actual encoding. It doesn't provide any settings. It indicates the capabilities of the encoded video. It is up to the user to set the encoding parameters so that they match the spec for that particular level.

See: https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding_tiers_and_levels

Exactly. It really just a tag that accompanies the video. I'd still like to understand, though, why X265 and NVENCC tag different levels when the settings (max bitrate, etc) are the same.So I did The Fifth Element 1080p/HEVC again with both decoders since I had deleted jobs/logs and wanted to post the results below to possibly help you in determining what the differences are.

x265: I bolded the encoder settings in the MediaInfo below showing the level and tier settings that I assume tell the encoder what level/tier to use.
----------------------
[03/22/21] BD Rebuilder v0.61.21
[11:21:03] Source: THE_FIFTH_ELEMENT_00001
- Input BD size: 35.37 GB
- Approximate total content: [02:05:53.546]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Auto Quality: Very Good (Very Fast), ABR
- Decoding/Frame serving: DGDecNV [4-way]
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[11:21:06] PHASE ONE, Encoding
- [11:21:06] Processing: VID_00001 (1 of 1)
- [11:21:06] Extracting A/V streams [VID_00001]
- [11:24:53] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 181,104 frames
- Bitrate: 15,315 Kbs
- [11:24:53] Reencoding: VID_00001, Pass 1 of 1
- [15:57:33] Video Encode complete
- [15:57:33] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[15:57:33]PHASE ONE complete
[15:57:33]PHASE TWO - Rebuild Started
- [15:57:33] Rebuilding BD file Structure
[15:58:09] - Encode and Rebuild complete
- WORKFILES folder removed.
[15:58:10] JOB: THE_FIFTH_ELEMENT finished.
----------------------
MediaInfo:

General
Complete name : C:\Users\eM-SSD\Videos\HEVC\THE_FIFTH_ELEMENT\\BDMV\PLAYLIST\00000.mpls
Format : Blu-ray Playlist
File size : 456 Bytes
Duration : 2 h 5 min
Overall bit rate mode : Variable
Overall bit rate : 0 b/s

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

NVENCC: The NVENC encoder doesn't show as much info, let alone what settings are used. I'm assuming again that NVENC sets the level/tier automatically depending on the file being encoded, and x265 requires specific settings? I know you said that both are set to default settings so I'll leave that to you to figure out.

----------------------
[03/22/21] BD Rebuilder v0.61.21
[16:54:48] Source: THE_FIFTH_ELEMENT_00001
- Input BD size: 35.37 GB
- Approximate total content: [02:05:53.546]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Auto Quality: Very Good (Very Fast), ABR
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[16:54:49] PHASE ONE, Encoding
- [16:54:49] Processing: VID_00001 (1 of 1)
- [16:54:49] Extracting A/V streams [VID_00001]
- [16:58:09] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 181,104 frames
- Bitrate: 15,315 Kbs
- [16:58:09] Reencoding: VID_00001, Pass 1 of 1
- [17:12:05] Video Encode complete
- [17:12:05] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[17:12:05]PHASE ONE complete
[17:12:05]PHASE TWO - Rebuild Started
- [17:12:05] Rebuilding BD file Structure
[17:12:42] - Encode and Rebuild complete
- WORKFILES folder removed.
[17:12:43] JOB: THE_FIFTH_ELEMENT finished.
----------------------
MediaInfo:

General
Complete name : C:\Users\eM-SSD\Videos\HEVC\THE_FIFTH_ELEMENT\\BDMV\PLAYLIST\00000.mpls
Format : Blu-ray Playlist
File size : 456 Bytes
Duration : 2 h 5 min
Overall bit rate mode : Variable
Overall bit rate : 0 b/s

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4.1@High
Codec ID : 36
Duration : 2 h 5 min
Bit rate : 22.1 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.445
Stream size : 19.4 GiB
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
format_identifier : HDMV
Source : 00000.m2ts / 00000.m2ts

So there you go. Hope this helps you determine what the differences are, and whether it makes any difference quality wise. I would like to continue using NVENC just in the speed difference alone, so if it can be set like x265 even better. Or if I shouldn't worry about it then that's ok too. Thanks again for your help.

[spotswood]

I'm at a loss. I use the prediction setting all the time (almost every day), and I've never had a problem.

Something you could try:

1. Set BD-RB up to run with the prediction.
2. Let it start and then fail.
3. Go to the BD Rebuilder folder and look for a file called LASTCMD.TXT
4. Open the file (with NOTEPAD) and cut the command line that is represented there.
5. Open a CMD window, and paste the command.
6. Run it and see what error you get.

Then mark/cut-and-paste the information from the CMD window to this thread so I can see the error.Here ya go...

C:\Windows\system32>"C:\Users\eM-SSD\Downloads\BD-RBV06121\BD_Rebuilder\tools\nvenc\nvencc.exe" --avs -i "C:\USERS\EM-SSD\VIDEOS\HEVC\WORKFILES\TEMP.AVS" --codec hevc --preset performance --profile main10 --output-depth 10 --repeat-headers --colorprim bt709 --transfer bt709 --colormatrix bt709 --qp-min 0 --multipass 2pass-full --vbr 0 --vbr-quality 17.55 --aq --aq-temporal --sar 1:1 --aud --pic-struct --vbv-bufsize 45000 --max-bitrate 48000 --gop-len 24 -o "C:\USERS\EM-SSD\VIDEOS\HEVC\WORKFILES\TEMP.265"
--------------------------------------------------------------------------------
C:\USERS\EM-SSD\VIDEOS\HEVC\WORKFILES\TEMP.265
--------------------------------------------------------------------------------
avs: invalid clip.
avs: DGSource: Cannot open index file!
avs: (C:\USERS\EM-SSD\VIDEOS\HEVC\WORKFILES\TEMP.AVS, line 3)
failed to initialize file reader(s).
Failed to open input file.

[jdobbs]

@spotswood

Hmm... DGSource as the input... I'll check that out.

Can you post the contents of TEMP.AVS?

[spotswood]

@spotswood

Hmm... DGSource as the input... I'll check that out.

Can you post the contents of TEMP.AVS?I figured it out. I recently upgraded my dgdecnv2053 to the newer v2053.0.0.228. When I opened the TEMP.AVS I noticed it's reference to the new version folder (I had renamed it), but forgot to copy the license file over from the old version. DUH! Don't know why VBR mode worked and CQM didn't, but it's all good now. Soory about that Chief!

[cartman0208]

Are there any advantages of DGDecNV compared to DirectshowSource regarding speed/quality?

I also have a licence for DGDecNV, but I usually use Directshow as it seems more compatible...

[maxWsax]

1. Installed latest version and everything as instructed including all recommended components in proper order (Win 10)
2. Registered mscomctl.ocx successfully (as Admin)
3. Made sure mscomctl.ocx is in both \system32 and \sysWOW64 and registered properly.
4. When running BDRB.exe as Admin getting error message that mscomctl.ocx or one if it's dependencies is not properly installed or is missing, despite being successfully registered.
5. Installed VisualBasic6 as per some comment, but no luck.
6. If running BDRB as non-admin, the program tries to config LAV which had been properly installed and already configured during installation and BDRB cannot due it saying I have to run it as Admin (see above). Basically running in circles.
7. Running out of options. Any thoughts?

[LowDead]

1. Installed latest version and everything as instructed including all recommended components in proper order (Win 10)
2. Registered mscomctl.ocx successfully (as Admin)
3. Made sure mscomctl.ocx is in both \system32 and \sysWOW64 and registered properly.
4. When running BDRB.exe as Admin getting error message that mscomctl.ocx or one if it's dependencies is not properly installed or is missing, despite being successfully registered.
5. Installed VisualBasic6 as per some comment, but no luck.
6. If running BDRB as non-admin, the program tries to config LAV which had been properly installed and already configured during installation and BDRB cannot due it saying I have to run it as Admin (see above). Basically running in circles.
7. Running out of options. Any thoughts?

You don't have Bitdefender AV, do you? I have it and it can sometimes interfere with programs saving to "secure" folder and forces you to whitelist them programs.. Maybe other AVs have this "feature" also?

Probably another issue for you though.. Just putting the idea out there ^_^

//LD
//LD

[maxWsax]

I wish it was that easy. I disabled security programs with no effect on this issue. Hopefully, someone can reproduce it and resolve :(

[Lathe]

Hi Lathe, I read your post and was apprehensive when I took my newly burned BD25 that was processed using v0.61.21 and put it in my OPPO BDP-93. It plays perfectly, I wonder if the disk you did was from a Blu-ray or were you rebuilding something from a 4K?

Sorry to answer this so much later (I REALLY need to keep up here...)

The source was from Blu-ray, but I have the older BDP-83; perhaps there were some firmware updates on yours that are not on mine.

[Lathe]

Yes. I appreciate the thought.
Any chance you may have had "Convert BD to UHD-BD (HEVC) Format" selected? That would have created a disc that would do exactly what you describe.

No... I don't even see that in the drop down menu (as pictured by another fellow above) For some reason the encode that BDRB had completed when burned would not play on my OPPO, but when I took the re-encoded files and used an older version of TSMuxer and then burned that it played just fine. That was the only difference. But, no biggie... Next time I need to re-encode a film I'll try the resulting encode from BDRB. If it does the same thing, I'll just make sure to take the raw re-encoded files and use the older version of TSMuxer to mux it before I burn it.

BTW, sorry for the delay, but $100 is on the way! I hope that helps make up for the off-chance, miniscule, and extremely rare, probably negligible occurrence if it actually exists, when I might possibly annoy someone (and no comments from the Peanut Gallery please. JD's opinion is the only one that counts and I just made a donation :D)

[Jackie Treehorn]

What is the required information to post when you are having an issue? I assume it is the output of the "inspect" function and "log"?

Thanks!

[musiclover]

What is the required information to post when you are having an issue? I assume it is the output of the "inspect" function and "log"?

Thanks!

You assume right. Also your ini file could be of interest. And a clear description of the problem.

[gamete]

@jdobbs

Here my error

https://forum.doom9.org/showpost.php?p=1937502&postcount=30428

[Jackie Treehorn]

[03/25/21] BD Rebuilder v0.61.21
[11:37:58] Source: LOGICAL_VOLUME_ID_00000
- Input BD size: 10.62 GB
- Approximate total content: [01:49:39.239]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MP4 Container, NO_RESIZE, AutoGOP, Auto-AAC
- Quality: High Quality (Default)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[11:38:00] PHASE ONE, Encoding
- [11:38:00] Processing: VID_00000 (1 of 1)
- [11:38:00] Reencoding video [VID_00000]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 157,744 frames
- [11:38:01] Reencoding: VID_00000, Pass 1 of 1
- Encode failed. Aborting.
- BD-Rebuilder v0.61.21
- Windows Version: 6.2 [9200]
- Working Path Free Space: 32.66GB
- AVISYNTH Version: 2.6.0.6, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- AnyDVD settings check: Ok.
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[12:30:06] - Failed video encode, aborted

[03/25/21] Checking System Settings
- BD-Rebuilder v0.61.21
- Windows Version: 6.2 [9200]
- Working Path Free Space: 32.66GB
- AVISYNTH Version: 2.6.0.6, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- AnyDVD settings check: Ok.
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[03/25/21] Systems Settings Check complete

Been using BD Rebuilder for about 6 years now w/o issue. Had to jump to a new machine with Windows 10 on it and Ive been having issues such as that posted above. I am sure it's user error... like I said it worked flawlessly on Windows 7 to the point where I haven't changed the settings in years. A new machine made me do just that and what we have above is the byproduct. Thanks for any help!

[Jackie Treehorn]

Ooops... INI file below

[Options]
VERSION=0.61.0.21
ENCODER=0
MODE=3
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=1
MOVIEONLY_TYPE=21
ALTCRF=23
ALT_TARGET=1024
ALT_CRF_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
PRIORITY_CLASS=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=all
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
AUDIO_DRC=0
DECODER=0
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=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23500
[Paths]
SOURCE_PATH=D:\
WORKING_PATH=C:\USERS\JWALTMAN21\DOCUMENTS\WORKING\

[jdobbs]

No... I don't even see that in the drop down menu (as pictured by another fellow above) For some reason the encode that BDRB had completed when burned would not play on my OPPO, but when I took the re-encoded files and used an older version of TSMuxer and then burned that it played just fine. That was the only difference. But, no biggie... Next time I need to re-encode a film I'll try the resulting encode from BDRB. If it does the same thing, I'll just make sure to take the raw re-encoded files and use the older version of TSMuxer to mux it before I burn it.

BTW, sorry for the delay, but $100 is on the way! I hope that helps make up for the off-chance, miniscule, and extremely rare, probably negligible occurrence if it actually exists, when I might possibly annoy someone (and no comments from the Peanut Gallery please. JD's opinion is the only one that counts and I just made a donation :D)Wow. Thanks!

[spotswood]

I've been told that GTX-1660s have gotten popular and are getting harder to find (and more expensive) -- but I haven't really done any research. I bought mine for $238.For those interested, I just found a screaming deal for a Brand New GTX-1660 Super 6GB on eBay for $169! Hurry they're going fast! https://www.ebay.com/itm/ASUS-GeForce-GTX1660-SUPER-6GB-GDDR6-DUAL-GTX1660S-6G-EVO-Video-Card-New/254918051014?hash=item3b5a4cc4c6:g:nt0AAOSw0iNgXqSf

NEVERMIND... The item was pulled. My order got cancelled. CRAP! The seller must have figured out his asking price was WAY too low. Can they do that?

UPDATE... I called eBay and was told since my order was confirmed and my card was charged before the item was removed, the seller is required to ship the item. I can file a claim if he doesn't. So we'll see what happens, fingers crossed...

[Mike-uk]

BTW, sorry for the delay, but $100 is on the way! I hope that helps make up for the off-chance, miniscule, and extremely rare, probably negligible occurrence if it actually exists, when I might possibly annoy someone (and no comments from the Peanut Gallery please. JD's opinion is the only one that counts and I just made a donation :D)

Top man , nice to see people supporting this awesome piece of software, its certainly been useful to me so will also be donating soon

[Jackie Treehorn]

Ooops... INI file below

[Options]
VERSION=0.61.0.21
ENCODER=0
MODE=3
ENCODE_QUALITY=2
ONEPASS_ENCODING=0
AUTO_QUALITY=1
MOVIEONLY_TYPE=21
ALTCRF=23
ALT_TARGET=1024
ALT_CRF_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
PRIORITY_CLASS=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=all
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
AUDIO_DRC=0
DECODER=0
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=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23500
[Paths]
SOURCE_PATH=D:\
WORKING_PATH=C:\USERS\JWALTMAN21\DOCUMENTS\WORKING\

Can anyone lend a hand?

[Mike-uk]

Can anyone lend a hand?

try internal lav frame server ??

[gamete]

Good morning. I have a doubt. if when I make a backup in bd25 the estimated time is 50 hours with 2 passes, how much will the estimated time be if I make a backup in bd50 of the same film with the same settings? 25 hours?

[Jackie Treehorn]

try internal lav frame server ??

Thank you sir; however I am not sure how to do that... is that a setting in ffdshow?

[jdobbs]

@Jackie Treehorn

After the job has failed, check the file LASTCMD.TXT in the BD Rebuilder folder. It has the command line that failed contained within it. Please post that command line here so I can see if there is something obvious wrong. Also, open a CMD window and cut/paste the command into it and see what error is occurring. Then please paste that here as well.

[jdobbs]

I'm getting an error in the META file. BDRB thinks the video is a .264 file and puts ****.264 for muxing in the META file. The original file is .hevc and BDRB also correctly saves that file as .hevc but puts wrong extension in the META file.
This has only happened to me in the latest version of BDRB and I haven't yet run it with an older version. Will try also another title to see if it is repeatable.

Also want to point out that I do know I have the wrong avisynth installed. The reason for that is to get compability with other software. Of course it could be this that makes it error out but because I have never gotten this error before it might not be related and
before I test to install the right version of avisynth I will try earlier version of BDRB and also check for another title to try.

LOG:


//LDI've fixed this error for the next release. BD-RB wasn't properly creating the META when the source was 1080p and HEVC.

As a temporary fix, you can set UHD_V3_MODE=1 in your INI file while doing that disc -- but don't forget to reset it when done (it has the same effect as selecting "Convert BD to UHD-BD (HEVC) Format" from the output menu).

[Jackie Treehorn]

@Jackie Treehorn

After the job has failed, check the file LASTCMD.TXT in the BD Rebuilder folder. It has the command line that failed contained within it. Please post that command line here so I can see if there is something obvious wrong. Also, open a CMD window and cut/paste the command into it and see what error is occurring. Then please paste that here as well.

"C:\Users\jwaltman21\Documents\BD_Rebuilder\tools\x264.exe" "C:\USERS\JWALTMAN21\DOCUMENTS\WORKING\WORKFILES\VID_00000.AVS" --preset medium --bluray-compat --b-pyramid none --weightp 1 --slow-firstpass --qpmin=0 --crf 23 --level 4.0 --qpfile "C:\USERS\JWALTMAN21\DOCUMENTS\WORKING\WORKFILES\VID_00000.CHP" --aud --nal-hrd vbr --pic-struct --vbv-bufsize 15000 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 15000 --threads auto --thread-input --stats "C:\USERS\JWALTMAN21\DOCUMENTS\WORKING\WORKFILES\VID_00000.AVS.264.stats" --output "C:\USERS\JWALTMAN21\DOCUMENTS\WORKING\WORKFILES\VID_00000.AVS.264"

[Jackie Treehorn]

Microsoft Windows [Version 10.0.19042.867]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users\jwaltman21>"C:\Users\jwaltman21\Documents\BD_Rebuilder\tools\x264.exe" "C:\USERS\JWALTMAN21\DOCUMENTS\WORKING\WORKFILES\VID_00000.AVS" --preset medium --bluray-compat --b-pyramid none --weightp 1 --slow-firstpass --qpmin=0 --crf 23 --level 4.0 --qpfile "C:\USERS\JWALTMAN21\DOCUMENTS\WORKING\WORKFILES\VID_00000.CHP" --aud --nal-hrd vbr --pic-struct --vbv-bufsize 15000 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 15000 --threads auto --thread-input --stats "C:\USERS\JWALTMAN21\DOCUMENTS\WORKING\WORKFILES\VID_00000.AVS.264.stats" --output "C:\USERS\JWALTMAN21\DOCUMENTS\WORKING\WORKFILES\VID_00000.AVS.264"
avs [info]: 1920x1080p 0:0 @ 24000/1001 fps (cfr)
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
x264 [info]: profile High, level 4.0, 4:2:0, 8-bit
[2.3%] 3689/157744 frames, 36.58 fps, 1080.46 kb/s, eta 1:10:10

[LowDead]

I've fixed this error for the next release. BD-RB wasn't properly creating the META when the source was 1080p and HEVC.

As a temporary fix, you can set UHD_V3_MODE=1 in your INI file while doing that disc -- but don't forget to reset it when done (it has the same effect as selecting "Convert BD to UHD-BD (HEVC) Format" from the output menu).

Great work. Thanks!

//LD

[spotswood]

Hey again... trying different options with the new UHD_CONVERT_ENABLE=1 mode and think I found a bug maybe? After running a job in CQM, I switched to One Pass (VBR) Encoding (pic attached), then when starting the job the log shows the file being encoded in ABR mode instead of VBR mode (see Quality: line in pic). Is this correct? I ran several jobs last night and swore the log showed VBR mode (logs deleted unfortunately). I've tried going back and forth between CQM and VBR using different encoder/output options and it still says ABR mode when selecting VBR mode :confused:. Thanks for any help...