BD Rebuilder Beta - Bug Reports Only

[sneaker_ger]

bye bye RTX 2070 super :( , the 3 week wait for my RTX 3080 will be sad :(, but hopefully they have made more improvements to nvenc
Nvidia has said encoding hardware is the same as turing. Only decoding is improved (added AV1 decoding).

Q: Will there be any improvements to the RTX encoder in the Ampere series cards, similar to what we saw for the Turing Release? I did see info on the Broadcast software, but I'm thinking more along the lines of improvements in overall image quality at same bitrate.

For RTX 30 Series, we decided to focus improvements on the video decode side of things and added AV1 decode support. On the encode side, RTX 30 Series has the same great encoder as our RTX 20 Series GPU. We have also recently updated our NVIDIA Encoder SDK. In the coming months, livestream applications will be updating to this new version of the SDK, unlocking new performance options for streamers.
https://www.nvidia.com/en-us/geforce/news/rtx-30-series-community-qa/
https://www.reddit.com/r/nvidia/comments/iko4u7/geforce_rtx_30series_community_qa_submit_your/g3mixss?utm_source=share&utm_medium=web2x&context=3

[jdobbs]

Would that mean that, if above fix works, I could be lazy and just set output size larger than UHD50 in BDRB and re-run it and it will automagically fix itself? :)

//LDYes. That would likely work -- if you mean running BD-RB against the output of your last run.

The subtitles were working when BD-RB used the previous version of TSMUXER (4k) with the PID set starting at 0x1200. In the meantime a change was made that sets them for HDR to an address starting at 0x12A0. Since I missed that note in the change log -- the CLPI and M2TS created by the new version of TSMUXER (on full backups) has a different PID than the MPLS (which is updated by BD-RB to account for languages that may not have been kept). The problem doesn't exist in movie-only backups.

I've fixed it and will kick out a new version in the next couple of days.

[LowDead]

Yes. That would likely work -- if you mean running BD-RB against the output of your last run.

The subtitles were working when BD-RB used the previous version of TSMUXER (4k) with the PID set starting at 0x1200. In the meantime a change was made that sets them for HDR to an address starting at 0x12A0. Since I missed that note in the change log -- the CLPI and M2TS created by the new version of TSMUXER (on full backups) has a different PID than the MPLS (which is updated by BD-RB to account for languages that may not have been kept). The problem doesn't exist in movie-only backups.

I've fixed it and will kick out a new version in the next couple of days.

That was exactly what I meant :)

Great, thanks!

//LD

[MrVideo]

Looks like I'll have to wait until the RTX-3090 is released to find out if the driver for the RTX-30xx series still supports win7-64.

[Mike-uk]

Hi

trying to convert a 2160p mkv to a 25 gig bluray but it keeps failing :( where am i going wrong ??

[14:30:30] Importing MKV: test
- Collecting audio/video streams from source...
- Converting audio, Track #2, EAC3 to AC3...
- Building pseudo-BD source structure...
- Source issue found, attempting correction...
- Building pseudo-BD source structure...
[14:32:15]ERROR: Failed to build BD structure. Aborted.

thanks
mike

[MrVideo]

trying to convert a 2160p mkv to a 25 gig bluray but it keeps failing
H.264 or H.265 source? Looking Blu-ray standard or UHD standard?

JDobbs is working on h.265 to UHD.

A note to JDobbs: When doing the h.265/UHD version, do not convert EAC3 to AC3. While my 4k BD player refuses to play EAC3 files, it will play EAC3 when on a UHD disc. I did a test using TSmuxer to create a BD ISO and that disc played just fine. The Sony player even said that it was a UHD disc, which surprised me. I didn't expect TSmuxer to create a UHD disc.

[Mike-uk]

H.264 or H.265 source? Looking Blu-ray standard or UHD standard?

JDobbs is working on h.265 to UHD.

A note to JDobbs: When doing the h.265/UHD version, do not convert EAC3 to AC3. While my 4k BD player refuses to play EAC3 files, it will play EAC3 when on a UHD disc. I did a test using TSmuxer to create a BD ISO and that disc played just fine. The Sony player even said that it was a UHD disc, which surprised me. I didn't expect TSmuxer to create a UHD disc.

yes its a h265 source and im wanting it to a 25 gig bluray standard

[jdobbs]

- Source issue found, attempting correction...Odds are this is the issue... bad source.

[MrVideo]

yes its a h265 source and im wanting it to a 25 gig bluray standard
Any chance you can find an H.264 MKV source?

[Mike-uk]

Any chance you can find an H.264 MKV source?

yes had to resort to a 264 at half the file size :(, but i guess after re encoding a 265 to 264 ill end up with similar quality anyway

[alex74.744]

have a nice day. sorry for my english i use a translator. noticed such a problem. after deleting unnecessary audio tracks and playing in DUNE HD, the sound on the main movie does not work. When playing a movie with a menu (full menu), there is sound in the menu, additional materials, but there is no sound in the movie itself. When played without a menu (lite), there is sound in the movie. And so on any reassembled film. If you rebuild the movie with the multiAVCHD program, the sound works in the main movie, and in the menu, and in additional materials.

[BuddTX]

Looks like I'll have to wait until the RTX-3090 is released to find out if the driver for the RTX-30xx series still supports win7-64.

I made the jump to W10 this month, upgraded my 10+YO Dell T3500 to W10. It was a rough few days, but I am loving it now!

I made a backup boot HD with my W7, and I had to use it a few times. I have a 2.5/3.5 HD "cassette" that I installed into my PC, so I can mount hard drives without having to open up my computer. I also installed a usb 3.1 card, and a SATA3 controller

I have not even applied any "De-Bloat" "De-Crapifier" etc., W10 Privacy settings yet. I will make a backup image b4 I start applying those "tools".

So, just saying that as a fellow "W7 forever" person, go ahead and make the jump! look up on youtube and google how to most probably be able to still use your W7 activation code to work with W10.

I have a nVidia 1050ti installed, as much as I would like to play with a new GPU, unless the turing NVidia cards get real cheap, (or I win a lottery!), I will be keeping the 1050ti for a while. I know my GPU does not support "HEVC B Frame". So unless a 1660 or better nVidia card gets real cheap (come on Black Friday!), I will be keeping my 1050ti.

Also, if I read the last few pages here correctly, there are no more "new" encoding features on the new nVidia cards, just much faster processing, and other playback and decoding improvements.

One of the many reasons why I like BD-Rebuilder so much, is that I can apply all the "insane" "over kill" super slow video encoding settings in x265 to my MKV files!

Oh, I have to say, check out "Open Shell", it will turn your W10 into the W7 look and feel you love! "Open shell" used to be called "Classic Shell", and the original developer stopped developing "Classic Shell", so a new person took over development of the same program. https://open-shell.github.io/Open-Shell-Menu/

[MrVideo]

No Win10 for me. If need be, I'll get the latest nVidia turning card that still works with Win7-64.

[cartman0208]

Back from holidays I just did the first encode with BDRB 0.61.13 and I swapped the nvenc files with the newest ones (version 5.15 ... which apparently was released just some hours ago) and now HDR10+ works and looks awesome on alternate encodes. :)

I used the hidden switch mentioned in the last release notes.
Will do some more sources to confirm the results.

[jdobbs]

Back from holidays I just did the first encode with BDRB 0.61.13 and I swapped the nvenc files with the newest ones (version 5.15 ... which apparently was released just some hours ago) and now HDR10+ works and looks awesome on alternate encodes. :)

I used the hidden switch mentioned in the last release notes.
Will do some more sources to confirm the results.Great! I noticed the changes had been added to the latest NVENCC release. I'm adding it to BD-RB for the next release.

[jdobbs]

I posted and then removed v0.61.15 -- there's something that I forgot to test and I suspect it may have an issue.

If you downloaded it -- please don't upgrade/use it until I know it is working properly.

[cartman0208]

This might have been reported already?

If BDRB is set to NVENC, the encode stops on some sources with error, when the size-correcting second pass should be performed:

...
- [20:00:21] Processing: VID_00004 (5 of 21)
- [20:00:21] Extracting A/V streams [VID_00004]
- [20:00:26] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 2.520 frames
- [20:00:26] Performing CQM Prediction...
- Analyzing 14,50 19,15 20,10 [20,12]
- [20:00:36] Encoding using constant quality mode.
- Performing size-correcting second pass...
- [20:00:55] PredictAndEncode() 00011 2994

When I then switch the encoder to x264/x265, I can resume and continue

[Michi]

All my UHDs encoding with NVENCC are in 2176p. I use a GTX1660.

I thought this bug was fixed with turion, but it isn't fixed.

[jdobbs]

I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.61.16). Changes for this release:- Handling of HDR10+ in NVENCC has now been
enabled by default, the hidden option
NVENC_ENABLE_10PLUS is no longer needed or
supported.
- Corrected an issue in which SD imports may
not be reencoded with the correct aspect
ratio under some (rare) circumstances.
- Fixed an issue associated with incorrect
subtitle PID values on UHD/HDR sources.
- Added parameter to MKV creation that makes
odd subtitle characters less likely.
- Updated the version of NVENCC included with
BD-RB to v5.15 -- enabling corrected HDR10+
support.
- Other minor corrections and cosmetic fixes.

[LowDead]

All my UHDs encoding with NVENCC are in 2176p. I use a GTX1660.

I thought this bug was fixed with turion, but it isn't fixed.

That is a hardware limitation. It has nothing to do with BD-RB. Anyway you have nothing to worry about as the decoder on your player corrects this and output it as intended per the specs.

This is my understandings, anyone feel free to correct me if i'm wrong.

//LD

[jdobbs]

That is a hardware limitation. It has nothing to do with BD-RB. Anyway you have nothing to worry about as the decoder on your player corrects this and output it as intended per the specs.

This is my understandings, anyone feel free to correct me if i'm wrong.

//LDThat is also my understanding. From what I've read, the way it is used is in sync with industry standards, and if any player has an issue with it -- it is the player that has a "bug", not the encode.

[MrVideo]

It is the same thing with 1080 video. In case you didn't know, 1080 is encoded at 1088, as it too needs to be a multiple of 16. In the early days of OTA HD, my local NBC affiliate had their encoder screwed up such that the 1088 was actually displayed as 1088. The VideoReDo software had to add a "feature" where this was detected and fixed so that I could edit 1080 material with this screwed up 1088 material.

[mikeonecl]

any setup for processing a 3d movie with nvenc enabled?
i mean 3d encoding with nvenc

[Ch3vr0n]

no. 3D requires FRIM and even with nvenc, when bdrb detects 3D afaik it will override the decoder/encoder and default to FRIM

[BuddTX]

I have an install question, and I apologize in advance if it has been answered before, or if the answer is obvious, but obviously it is confusing to me:stupid::

The instructions say:
=================================
2. While not required it is recommended you perform either one of the following (2A, preferred, or 2B):

2A. Download and install the LAV Directshow Filters. Use only the version linked here -- as other versions may result in out-of-sync audio. While not required for BD-RB to work, LAVFilters will improve functionality and are free. They are required for some functionality associated with HEVC import and processing.

2B. Download and install FFDSHOW and the Haali Matroska Splitter. While they are not required for BD-RB to work, they will improve functionality and are free. After the install, run "Video Decoder Configuration" for FFDSHOW from the "START/Programs" menu, and make sure MPEG2 decoding is enabled. Do the same using "Audio Decoder Configuration" to ensure "Uncompressed" is set to "All Supported".

2C. If you decide to install both 2A and 2B, make sure HAALI/FFDSHOW (2B) is installed first, followed by LAVFilters (2A). This will prevent issues with HEVC splitting.
=================================

So the first line says "2A, preferred". OK that makes sense, I always want to do what the author recommends, right!

But then in 2B it says:
=======
While they are not required for BD-RB to work, they will improve functionality and are free.
=======

So, does this mean I SHOULD ALSO install 2B?

After all, who would not want "improved functionality". I am assuming that BD Rebuilder will work better if both 2A and 2B are installed, based on this statement, but the first statement says that 2A is preferred.

Thanks in advance!

[LowDead]

Just wanted to say that subtitles works now for me with full backup UHD with HDR and I could feed the old encode to "fix" it without doing a new encode.

Thanks ALOT for the fix!! :D

//LD

[jdobbs]

I have an install question, and I apologize in advance if it has been answered before, or if the answer is obvious, but obviously it is confusing to me:stupid::

The instructions say:
=================================
2. While not required it is recommended you perform either one of the following (2A, preferred, or 2B):

2A. Download and install the LAV Directshow Filters. Use only the version linked here -- as other versions may result in out-of-sync audio. While not required for BD-RB to work, LAVFilters will improve functionality and are free. They are required for some functionality associated with HEVC import and processing.

2B. Download and install FFDSHOW and the Haali Matroska Splitter. While they are not required for BD-RB to work, they will improve functionality and are free. After the install, run "Video Decoder Configuration" for FFDSHOW from the "START/Programs" menu, and make sure MPEG2 decoding is enabled. Do the same using "Audio Decoder Configuration" to ensure "Uncompressed" is set to "All Supported".

2C. If you decide to install both 2A and 2B, make sure HAALI/FFDSHOW (2B) is installed first, followed by LAVFilters (2A). This will prevent issues with HEVC splitting.
=================================

So the first line says "2A, preferred". OK that makes sense, I always want to do what the author recommends, right!

But then in 2B it says:
=======
While they are not required for BD-RB to work, they will improve functionality and are free.
=======

So, does this mean I SHOULD ALSO install 2B?

After all, who would not want "improved functionality". I am assuming that BD Rebuilder will work better if both 2A and 2B are installed, based on this statement, but the first statement says that 2A is preferred.

Thanks in advance!No. Sorry, that's badly worded. It means that BD-RB will run without either of them (LAV or FFDSHOW) -- but installing one or the other will improve functionality. Using 2A is preferable.

[jdobbs]

Just wanted to say that subtitles works now for me with full backup UHD with HDR and I could feed the old encode to "fix" it without doing a new encode.

Thanks ALOT for the fix!! :D

//LDGlad to be of help. :)

[BuddTX]

No. Sorry, that's badly worded. It means that BD-RB will run without either of them (LAV or FFDSHOW) -- but installing one or the other will improve functionality. Using 2A is preferable.

As always, Thank you JDobbs!

[LowDead]

I got this error with UHD The Natural. Did it before with previous version of BD-RB without fail, but as I got a bit of an undersize + the sub bug I decided to redo it comletely with the new version.

----------------------
[09-17-20] BD Rebuilder v0.61.16
[02:28:54] Source: NATURAL__THE_
- Input BD size: 84,78 GB
- Approximate total content: [03:25:27.987]
- Target BD size: 49,02 GB
- Windows Version: 6.2 [9200]
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[02:28:54] PHASE ONE, Encoding
- [02:28:54] Processing: VID_00001 (1 of 43)
- [02:28:54] Extracting A/V streams [VID_00001]
- [02:28:57] Reencoding video [VID_00001]
- [02:28:57] Keeping original video (no reencode)
- [02:28:57] Processing audio tracks
- [02:28:57] Multiplexing M2TS
- [02:29:01] Processing: VID_00080 (2 of 43)
- [02:29:01] Extracting A/V streams [VID_00080]
- [02:29:05] Reencoding video [VID_00080]
- [02:29:05] Keeping original video (no reencode)
- [02:29:05] Processing audio tracks
- [02:29:05] Multiplexing M2TS
- [02:29:08] Processing: VID_00081 (3 of 43)
- [02:29:08] Extracting A/V streams [VID_00081]
- [02:29:12] Reencoding video [VID_00081]
- [02:29:12] Keeping original video (no reencode)
- [02:29:12] Processing audio tracks
- [02:29:12] Multiplexing M2TS
- [02:29:15] Processing: VID_00082 (4 of 43)
- [02:29:15] Extracting A/V streams [VID_00082]
- [02:29:19] Reencoding video [VID_00082]
- [02:29:19] Keeping original video (no reencode)
- [02:29:19] Processing audio tracks
- [02:29:19] Multiplexing M2TS
- [02:29:22] Processing: VID_00100 (5 of 43)
- [02:29:22] Extracting A/V streams [VID_00100]
- [02:29:28] Reencoding video [VID_00100]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 346 frames
- Bitrate: 11 918 Kbs
- [02:29:28] Reencoding: VID_00100, Pass 1 of 2
- [02:31:59] Reencoding: VID_00100, Pass 2 of 2
- [02:34:58] Video Encode complete
- [02:34:58] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:34:58] Multiplexing M2TS
- [02:35:02] Processing: VID_00102 (6 of 43)
- [02:35:02] Extracting A/V streams [VID_00102]
- [02:35:06] Reencoding video [VID_00102]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 5 200 frames
- Bitrate: 500 Kbs
- [02:35:06] Reencoding: VID_00102, Pass 1 of 2
- [02:46:37] Reencoding: VID_00102, Pass 2 of 2
- [02:54:01] Video Encode complete
- [02:54:01] Processing audio tracks
- [02:54:01] Multiplexing M2TS
- [02:54:05] Processing: VID_00104 (7 of 43)
- [02:54:05] Extracting A/V streams [VID_00104]
- [02:54:10] Reencoding video [VID_00104]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 1 frames
- Bitrate: 48 000 Kbs
- [02:54:10] Reencoding: VID_00104, Pass 1 of 2
- [02:54:11] Reencoding: VID_00104, Pass 2 of 2
- [02:54:13] Video Encode complete
- [02:54:13] Processing audio tracks
- [02:54:13] Multiplexing M2TS
- [02:54:17] Processing: VID_00116 (8 of 43)
- [02:54:17] Extracting A/V streams [VID_00116]
- [02:54:21] Reencoding video [VID_00116]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 271 frames
- Bitrate: 4 292 Kbs
- [02:54:21] Reencoding: VID_00116, Pass 1 of 2
- [02:55:35] Reencoding: VID_00116, Pass 2 of 2
- [02:56:53] Video Encode complete
- [02:56:53] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:56:53] Multiplexing M2TS
- [02:56:57] Processing: VID_00208 (9 of 43)
- [02:56:57] Extracting A/V streams [VID_00208]
- [02:57:01] Reencoding video [VID_00208]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 262 frames
- Bitrate: 3 863 Kbs
- [02:57:01] Reencoding: VID_00208, Pass 1 of 2
- [02:58:02] Reencoding: VID_00208, Pass 2 of 2
- [02:59:00] Video Encode complete
- [02:59:00] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:59:00] Multiplexing M2TS
- [02:59:04] Processing: VID_00336 (10 of 43)
- [02:59:04] Extracting A/V streams [VID_00336]
- [02:59:08] Reencoding video [VID_00336]
- [02:59:08] Keeping original video (no reencode)
- [02:59:08] Processing audio tracks
- [02:59:08] Multiplexing M2TS
- [02:59:11] Processing: VID_00337 (11 of 43)
- [02:59:11] Extracting A/V streams [VID_00337]
- [02:59:46] Reencoding video [VID_00337]
- Source Video: HEVC, 3840x2160
- Rate/Length: 59,940fps, 7 728 frames
- Bitrate: 22 256 Kbs
- [02:59:46] Reencoding: VID_00337, Pass 1 of 2
- [04:20:04] Reencoding: VID_00337, Pass 2 of 2
- [05:38:56] Video Encode complete
- [05:38:56] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [05:38:56] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00337.meta
- HEVC manual defined fps doesn't equal to stream fps. Change HEVC fps from 59.97 to 59.9401
[05:39:02] - Failed to build structure, aborted

[Status]
LABEL=NATURAL__THE_
VERSION=v0.61.16
SOURCE_SIZE=91036714291
SOURCE_VIDEO_SIZE=90696757248
TARGET_SIZE=52638515200
REDUCTION=.576630959517059
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=all
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=all
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=-1
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
UHD_V3_MODE=0
QUICK=0
ENCODE_STEP=4
COMPLETED=10
[00001]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=325939
USE_ORIGINAL=1
NSTART=27000000
NEND=28351349
NSIZE=589824
FLINK=0
MLINK=0
[00080]
AUDIO=
PGS=1
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=109827
USE_ORIGINAL=1
NSTART=27000000
NEND=27450449
NSIZE=196608
FLINK=0
MLINK=0
[00081]
AUDIO=
PGS=1
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=109827
USE_ORIGINAL=1
NSTART=27000000
NEND=27450449
NSIZE=196608
FLINK=0
MLINK=0
[00082]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=109827
USE_ORIGINAL=1
NSTART=27000000
NEND=27450449
NSIZE=196608
FLINK=0
MLINK=0
[00100]
AUDIO=1
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=24643860
RATE=11918
NSTART=27000000
NEND=27649398
NSIZE=24084480
FLINK=0
MLINK=0
[00102]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4439154
RATE=500
NSTART=27000000
NEND=36759749
NSIZE=8294400
FLINK=0
MLINK=0
[00104]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=276340
RATE=48000
NSTART=27000000
NEND=27001876
NSIZE=430080
FLINK=0
MLINK=0
[00116]
AUDIO=1
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=6940386
RATE=4292
NSTART=27000000
NEND=27508632
NSIZE=6782976
FLINK=0
MLINK=0
[00208]
AUDIO=1
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=6079480
RATE=3863
NSTART=27000000
NEND=27491740
NSIZE=6070272
FLINK=0
MLINK=0
[00336]
AUDIO=
PGS=1
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=109827
USE_ORIGINAL=1
NSTART=27000000
NEND=27450449
NSIZE=196608
FLINK=0
MLINK=0
[00337]
AUDIO=1
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=390557002
RATE=22256

"C:\vidsoft\BD_Rebuilder\tools\ffmpeg.exe" -probesize 100MB -i "A:\UHDBD\THE NATURAL\BDMV\STREAM\00337.m2ts" -an -pix_fmt yuv420p10le -f yuv4mpegpipe -strict -1 - | "C:\vidsoft\BD_Rebuilder\tools\x265-64.exe" - --preset slow --profile main10 --uhd-bd --repeat-headers --vbv-bufsize 45000 --vbv-maxrate 48000 --hdr --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)" --fps 59.97 --sar 1:1 --qpfile "B:\WORK\WORKFILES\VID_00337.CHP" --keyint 60 --bitrate 22256 --y4m --stats "B:\WORK\WORKFILES\VID_00337.AVS.hevc.stats" --pass 2 --output "B:\WORK\WORKFILES\VID_00337.AVS.hevc"

[09-17-20] Checking System Settings
- BD-Rebuilder v0.61.16
- Windows Version: 6.2 [9200]
- Working Path Free Space: 604,51GB
- AVISYNTH Version: 2.6.0.5, Ok
- LAVFILTERS: Ok
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[09-17-20] Systems Settings Check complete

//LD

[Ch3vr0n]

@Jdobbs if you're interested, the Nvidia 3000 series whitepaper is now available. https://www.nvidia.com/en-us/geforce/news/rtx-30-series-ampere-architecture-whitepaper-download/

Sent from my Pixel 3 XL using Tapatalk

[gonca]

NVEnc hasn't changed, NVDec has been improved

[varekai]

@jdobbs
Thanks for the update! Much appreciated!

[jdobbs]

This might have been reported already?

If BDRB is set to NVENC, the encode stops on some sources with error, when the size-correcting second pass should be performed:

...
- [20:00:21] Processing: VID_00004 (5 of 21)
- [20:00:21] Extracting A/V streams [VID_00004]
- [20:00:26] Reencoding video [VID_00004]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 2.520 frames
- [20:00:26] Performing CQM Prediction...
- Analyzing 14,50 19,15 20,10 [20,12]
- [20:00:36] Encoding using constant quality mode.
- Performing size-correcting second pass...
- [20:00:55] PredictAndEncode() 00011 2994

When I then switch the encoder to x264/x265, I can resume and continueI fixed this one. Thanks for your help. It was a silly mistake on my part (the code was looking for a wrong filename when collecting the file size -- resulting in a divide-by-zero error). I'm looking at one other bug I'd like to fix, and then I'll release a new version.

[LowDead]

- [05:38:56] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00337.meta
- HEVC manual defined fps doesn't equal to stream fps. Change HEVC fps from 59.97 to 59.9401
[05:39:02] - Failed to build structure, aborted

Update to my issue:

Made a new encode switching to NVEnc encoder instead and then it did get past that muxing error point. Will test another new x265 encode to see if it was something temporary.

//LD

UPDATE: I did another encode with x265 and managed to reproduce the error. So maybe a bug in x265? Can I download a newer version of x265 from somewhere to test if the bug is fixed?

UPDATE 2: Noticed that the error wasn't exactly the same as before..

- [23:46:01] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00337.meta
- Muxing time: 3 sec
[23:46:10] - Failed to build structure, aborted

After restarting and letting it continue with the backup the muxing went on fine and the disc continued with the encode.

[jdobbs]

Update to my issue:

Made a new encode switching to NVEnc encoder instead and then it did get past that muxing error point. Will test another new x265 encode to see if it was something temporary.

//LD

UPDATE: I did another encode with x265 and managed to reproduce the error. So maybe a bug in x265? Can I download a newer version of x265 from somewhere to test if the bug is fixed?

UPDATE 2: Noticed that the error wasn't exactly the same as before..



After restarting and letting it continue with the backup the muxing went on fine and the disc continued with the encode.It's more likely an error in TSMUXER. Try using TSMUXER4K.EXE for the mux and you may find it works. There were multiple bugs fixed with the new release of TSMUXER (v2.6.16). Unfortunately there are also some changes that can create issues... and I'm working on BD-RB to adjust for those changes. In the end I'm hoping to use the newer version as a complete replacement (it is currently only used for UHD muxing).

[LowDead]

It's more likely an error in TSMUXER. Try using TSMUXER4K.EXE for the mux and you may find it works. There were multiple bugs fixed with the new release of TSMUXER (v2.6.16). Unfortunately there are also some changes that can create issues... and I'm working on BD-RB to adjust for those changes. In the end I'm hoping to use the newer version as a complete replacement (it is currently only used for UHD muxing).

Well then, thats the one that is used as it is a UHD disc...

//LD

[jdobbs]

Well then, thats the one that is used as it is a UHD disc...

//LDUghhh...

[LowDead]

ughhh...

?

//ld

[cartman0208]

Time for your own muxer implementation? ;)

[jdobbs]

?

//ldI was just commenting that it means it is likely a bug that I will have to hunt down and destroy.

[LowDead]

I was just commenting that it means it is likely a bug that I will have to hunt down and destroy.

Ahh, I see. Will post some info on the file that behaves strange as soon as the encode is finished that I'm on now. It's still The Natural.. The movie is divided into Theatrical and Extended versions with seamless branching. It's a pain with all the small segments as it takes like 5-6 days to complete (2-pass very good x265). ohhh I like that sweet sweet quality ;)

//LD

[jdobbs]

I've noticed an anomaly with NVENCC and I wonder if anyone else is experiencing the same thing.

When encoding a 1920x1080 source I typically get about 320 or so frames per second. But I notice that sometimes it encodes at 150 fps. When it does that, if I stop the encode and restart it -- it goes right back up to 320 fps and stays there for the remainder of the encode. I haven't done any extensive testing -- but it seems that I see it when there is more than one encode -- and one is starting right after the other (like in a multipart encode).

Not sure how or why it does that. Anyone else have any insight?

[ggtop]

Hi jdobbs,

I feel a little bit guilty that a lot of people ask for help and you in return get no response...
Actually I'm running a NVEncC encode the very first time now. I only have a Feforce GT730 running under Win10 using MS drivers, but as far as I'm informed it should work with x264.
It's only running with 100 FPS so I'm not even sure if faster than CPU.
When I look into e.g. taskmanager I see 1 process called "NVEncC.exe". Don't know how it is designed but if the host is running something like a service it could be that an orphaned or not correctly quitted task gets re-activated when a new one is started. Do you see more than one process? Or NVEnc is running multi-threaded which it doesn't on my ancient card?

BTW Will compare speed later.

Edit: Speed in nearly equal on my system:
Source: Avengers Endgame, Full backup to BD-25
NVEnC: 102 FPS, full GPU load on encoding/decoding, CPU: 20%
SW: 96 FPS, full CPU load, 75% GPU load while decoding using DGDecNV

While the SW encode is still running I'm very pleased with the visual result.

ggtop

[jdobbs]

Hi jdobbs,

I feel a little bit guilty that a lot of people ask for help and you in return get no response...
Actually I'm running a NVEncC encode the very first time now. I only have a Feforce GT730 running under Win10 using MS drivers, but as far as I'm informed it should work with x264.
It's only running with 100 FPS so I'm not even sure if faster than CPU.
When I look into e.g. taskmanager I see 1 process called "NVEncC.exe". Don't know how it is designed but if the host is running something like a service it could be that an orphaned or not correctly quitted task gets re-activated when a new one is started. Do you see more than one process? Or NVEnc is running multi-threaded which it doesn't on my ancient card?

BTW Will compare speed later.

Edit: Speed in nearly equal on my system:
Source: Avengers Endgame, Full backup to BD-25
NVEnC: 102 FPS, full GPU load on encoding/decoding, CPU: 20%
SW: 96 FPS, full CPU load, 75% GPU load while decoding using DGDecNV

While the SW encode is still running I'm very pleased with the visual result.

ggtopThanks.

[gonca]

As I understand you get slow downs when running consecutive encodes
Ran a simple test with consecutive encodes (x64>x64>x86>x86)
Input was the same for all encodes (vpy script using DGIndexNV)
computer was in use at this time on another encode

Results
\nvencc64.exe" --codec avc --cqp 22 --output T:\\00246.264 --y4m --input
fps 309.29
fps 300.48

\nvencc.exe" --codec avc --cqp 22 --output "T:\\00246 (2).264" --y4m --input
fps 284.18
fps 284.34

[LowDead]

Got a reply from Bitdefender regarding the whole ransomware farce.

"Thank you for your patience.

First of all, please accept my apologies for the severely delayed response. It was by no means intended, just that we are currently receiving a higher number of requests than usual and it takes longer for us to reply. We are working around the clock in order to improve our response time and I am sure that in the future you will notice a significant improvement.

The file was analyzed and it is currently not detected from our end. However, if the .exe file is taking actions in specific locations similar to what real ransomware would do, you will have to add a local exception.

Open Bitdefender, click on the Protection tab and then go to Ransomware Remediation, click on the Add an Exception button, and add the file in question.

If the situation persists, please send us a screenshot with the detection."

..So it shouldn't be detected anymore in bitdefender and IF it still does, one has to manually add BD-RB to exceptions.

//LD

[Ch3vr0n]

I got a GTX 1080 (placed my order in for a 3090 on wednesday lol), i'll see if can reproduce this fps issue

**edit** Pretty consistent so far on my end

Source: Pacific Rim Uprising
Decoder: NVDec (GPU load 45-55%)
Encoder: NVEnc (GPU load 30-35%, Memory use: 320-330MB)
Max FPS: 230-235 with peak of around 250-260 at the 80% complete mark for the main title. Smaller clips cap out at around 350-360 (maybe my 3090 will increase that count :D)
CPU load: 10-13%
Start to fish: around 20min

[LowDead]

I got a GTX 1080 (placed my order in for a 3090 on wednesday lol), i'll see if can reproduce this fps issue

**edit** Pretty consistent so far on my end

Source: Pacific Rim Uprising
Decoder: NVDec (GPU load 45-55%)
Encoder: NVEnc (GPU load 30-35%, Memory use: 320-330MB)
Max FPS: 230-235 with peak of around 250-260 at the 80% complete mark for the main title. Smaller clips cap out at around 350-360 (maybe my 3090 will increase that count :D)
CPU load: 10-13%
Start to fish: around 20min

Please do come with an comparison with the 3090 when it arrives :)

//LD

[Ch3vr0n]

you bet. That'll probably be a while though. In case ya wanna know which one. Picked the ROG STRIX RTX3090 024G Gaming (aka the highest overclocked model ^^). Dollar to Euro, snapped a CUSTOM card up for UNDER nvidia MSRP for a founders edition. Lol € 1390, 110€ cheaper than founders edition.