BD Rebuilder Beta - Bug Reports Only

[LowDead]

@Ch3vr0n: WOW Congrats for that!

Anyway here's an update on that file from "The Natural" that gives TSmuxer4k a mild to, at times, severe headaches..

General
ID : 1 (0x1)
Complete name : B:\WORK\NATURAL__THE
Format : Blu-ray Clip info / Blu-ray Clip info
File size : 1.14 KiB
Duration : 2 min 8 s
Overall bit rate mode : Variable
Overall bit rate : 22.5 Mb/s
Maximum Overall bit rate : 35.5 Mb/s
OverallBitRate_Precision_Min : 22462713
OverallBitRate_Precision_Max : 22462888

Video
ID : 4113 (0x1011)
Menu ID : 1 (0x1)
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : 36
Duration : 2 min 8 s
Bit rate : 21.4 Mb/s
Width : 3 840 pixels
Height : 2 160 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.043
Stream size : 328 MiB
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
Source : 00337.m2ts / 00337.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 : 2 min 8 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 : 2.95 MiB
Language : English
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 : 1153
compr_Average : 0.67
compr_Average : 0.67 dB
compr_Minimum : -4.08
compr_Minimum : -4.08 dB
compr_Maximum : 5.74
compr_Maximum : 5.74 dB
compr_Count : 1072
dynrng_Average : 0.66
dynrng_Average : 0.66 dB
dynrng_Minimum : -4.08
dynrng_Minimum : -4.08 dB
dynrng_Maximum : 5.88
dynrng_Maximum : 5.88 dB
dynrng_Count : 1133
format_identifier : AC-3
Source : 00337.m2ts / 00337.m2ts

//LD

[cartman0208]

Got my hands on a disc that also consists of 24p and 60p videos.
Couldn't find any issues with x265 or nvenc:

[09.25.20] BD Rebuilder v0.61.16
[22:18:02] Source: GEMINI_MAN
- Input BD size: 86,10 GB
- Approximate total content: [02:17:58.350]
- Target BD size: 47,36 GB
- Windows Version: 6.2 [9200]
- Quality: Good (Fastest, BD-25+), CRF
- Decoding/Frame serving: FFMPEG
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[22:18:03] PHASE ONE, Encoding
- [22:18:03] Processing: VID_00000 (1 of 3)
- [22:18:03] Extracting A/V streams [VID_00000]
- [22:18:10] Reencoding video [VID_00000]
- Source Video: HEVC, 3840x2160
- Rate/Length: 23,976fps, 528 frames
- [22:18:10] Reencoding: VID_00000, Pass 1 of 1
- [22:18:34] Video Encode complete
- [22:18:34] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:18:34] Multiplexing M2TS
- [22:18:38] Processing: VID_00579 (2 of 3)
- [22:18:38] Extracting A/V streams [VID_00579]
- [22:19:07] Reencoding video [VID_00579]
- Source Video: HEVC, 3840x2160
- Rate/Length: 59,940fps, 10.940 frames
- [22:19:07] Reencoding: VID_00579, Pass 1 of 1
- [22:26:01] Video Encode complete
- [22:26:01] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:26:01] Multiplexing M2TS
- [22:26:07] Processing: VID_00003 (3 of 3)
- [22:26:07] Extracting A/V streams [VID_00003]
- [22:48:58] Reencoding video [VID_00003]
- Source Video: HEVC, 3840x2160
- Rate/Length: 59,940fps, 420.962 frames
- [22:48:59] Performing CRF Prediction...
- Analyzing 12,00 11,05 [11,05]
- [22:55:23] Encoding using constant rate factor.
- [03:34:42] Video Encode complete
- [03:34:42] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- Track 4354 (deu): Keeping original audio
- [03:34:42] Multiplexing M2TS
[03:47:33]PHASE ONE complete
[03:47:33]PHASE TWO - Rebuild Started
- [03:47:33] Rebuilding BD file Structure
[03:47:54] - Encode and Rebuild complete
[03:47:54] Writing BD structure to ISO file
- ImgBurn completed successfully
[03:56:11] JOB: GEMINI_MAN finished.

IMO 60fps in a movie looks phenomenal ... no idea why all the movies stick with 24fps ... whatever this soap opera effect is, that people complain about, I have no issues with that :cool:

[jdobbs]

Got my hands on a disc that also consists of 24p and 60p videos.
Couldn't find any issues with x265 or nvenc:



IMO 60fps in a movie looks phenomenal ... no idea why all the movies stick with 24fps ... whatever this soap opera effect is, that people complain about, I have no issues with that :cool:Probably because most movies are mastered on film at 24fps.

[MrVideo]

Probably because most movies are mastered on film at 24fps.
Not anymore. A majority of movies are shot on video, using cameras specifically designed for movies. Some directors still like shooting on film, but the film is digitally transferred and edited.

One such company making digital cameras is Red (red.com). The other is Arri (www.arri.com/en/camera-systems/cameras).

Shooting at 60fps would result in the movie not getting shown in many theaters, as they are not equipped with the very expensive projectors to do so. Even 48fps movies are limited.

[Ch3vr0n]

Does this 61.16 release include the updated frim or did you not have more time to tinker with it?

[jdobbs]

Does this 61.16 release include the updated frim or did you not have more time to tinker with it?Sorry. I haven't played with it at all yet.

[jdobbs]

Not anymore. A majority of movies are shot on video, using cameras specifically designed for movies. Some directors still like shooting on film, but the film is digitally transferred and edited.

One such company making digital cameras is Red (red.com). The other is Arri (www.arri.com/en/camera-systems/cameras).

Shooting at 60fps would result in the movie not getting shown in many theaters, as they are not equipped with the very expensive projectors to do so. Even 48fps movies are limited.Yeah, I was aware that most have gone digital now. But I'm also referring to the other million+ or so releases that happened before that.

[Ch3vr0n]

no worries. Was just a question. In the mean time i've been tinkering with nvenc, sad to say i can't reproduce your problem. Maybe its because your GPU is actually of a newer generation than mine. That'll change though when my 3090 hopefully arrives in a couple weeks ^^

[jdobbs]

I got a strange error today:

MapSMtoCores undefined SMversion 7.5!

It happens when I try to encode a movie with X264. It's related to CUVID on my NVIDIA card. If I turn CUVID off it works. Oddly, it worked fine yesterday and I don't see anything that has changed (no updates etc.).

Is anyone familiar with this? Is there a fix?

[Edit] Well... it seems to have gone away with the installation of an updated version of LAV Filters. I may have to update the first post of the thread with a newer version for download. I'll need to do some testing first. Unfortunately that may delay release of the new version. Still wondering what changed overnight, though.

[Ch3vr0n]

You mean X264 as frameserver instead of DGDecNV? I can run a test with my 1080 if you want.

[gonca]

You mean X264 as frameserver instead of DGDecNV? I can run a test with my 1080 if you want.

I believe he means that he was using LAV with hardware acceleration (CUVID) for frame serving

jdobbs
Could it be one of those once in a blue moon glitches?

[jdobbs]

I believe he means that he was using LAV with hardware acceleration (CUVID) for frame serving

jdobbs
Could it be one of those once in a blue moon glitches?No. I can repeat it easily with the version of LAV Filters in the first post. It seems to only happen, though, when reencoding a 2160p source using X264. In my case I was creating ALTERNATE output using a preset that creates an MKV. I'm going to try it with a different 2160p source and see if happens then also.

[Edit] I tried it with another 2160p source and it ran fine. I think the issue is related to that specific source. It was an odd UHD file without HDR that I'd downloaded for a specific bug fix test. I think it is fine the way it is.

[jdobbs]

I think this version is ready for release, but since using the new version of TSMUXER to do all muxing actions can affect a lot of things, I'd like to post it as a test version so some of you experienced users can run it through the ringer before I officially release it.

You can download it from this link: BD-RB v0.61.17 (https://jammernhilftnichts.de/jdobbs/BD-RBV06117.zip)

Please provide feedback as to whether or not you find any anomalies. Thanks.

Changes for this release:- Corrected an issue in which attempts to
perform a size-correcting second pass on
an AVC source could result in an error
"PredictAndEncode() 00011 2994".
- Made adjustments to correct for bad time
codes in .SUP files that could result in
certain oddly formatted multi-part sources
(shows itself as subtitles that extend
well beyond the lenght of the movie)
- Added changes that will prevent occurance
of some "Bitstream exception" errors.
- Implemented default use of v2.6.16 of
TSMUXER for all TSMUXER functions. In
order to disable and return to v2.6.12
use hidden option "ENABLE_NEW_TSMUXER=0".
- Added a routine that catches previously
undetected errors in AAC encoding and then
attempts reencoding via a new method.
- Corrected a setting used with HEVC that
could assert HDR when it is not present in
the original source.
- Updated TSMUXER4K to the 2020-09-25 build.
- Other minor corrections and cosmetic fixes.

[Ch3vr0n]

a few quick questions @jdobbs

* is this switch SPECIAL_3D_MUX=1 still needed for in-mux 3D or even at all? (maybe make it a setting instead of hidden option?)
* i'm trying to create movie-only output type but i can't figure it out. I'd like "MKV, Full-SBS (3D), but recoded audio (aac or ac3, but surround intact or recoded to 5.1, codec don't care)". Ideally for an estimated filesize of around 4-8gb. Is this doable?

[Emulgator]

Might still be lurking around: The tsMuxeR 2.6.16 beta versions I tested (from December 2019 until July 2020) were not able to mux 1280x720x50p without packet loss. I kept tsMuxeR 1.10.6 in my toolbox for such reason, muxed ok.
Right now I have no such project, If I find time I will start trying newer tsMuxeR versions on such files.

P.S. Found my test project. Looks good for now.
No packet loss anymore with tsMuxeR git-32db2aa x64 2020-09-25--02-25-44.

P.P.S. And a concatenated ~5h 1280x720x50p project was muxed fine too.
BDEdit 0.49b finds no more packet loss.

[jdobbs]

Might still be lurking around: The tsMuxeR 2.6.16 beta versions I tested (from December 2019 until July 2020) were not able to mux 1280x720x50p without packet loss. I kept tsMuxeR 1.10.6 in my toolbox for such reason, muxed ok.
Right now I have no such project, If I find time I will start trying newer tsMuxeR versions on such files.

P.S. Found my test project. Looks good for now.
No packet loss anymore with tsMuxeR git-32db2aa x64 2020-09-25--02-25-44.

P.P.S. And a concatenated ~5h 1280x720x50p project was muxed fine too.
BDEdit 0.49b finds no more packet loss.Good to know. Thanks.

[jdobbs]

a few quick questions @jdobbs

* is this switch SPECIAL_3D_MUX=1 still needed for in-mux 3D or even at all? (maybe make it a setting instead of hidden option?)
* i'm trying to create movie-only output type but i can't figure it out. I'd like "MKV, Full-SBS (3D), but recoded audio (aac or ac3, but surround intact or recoded to 5.1, codec don't care)". Ideally for an estimated filesize of around 4-8gb. Is this doable?All SPECIAL_3D_MUX does is not add the InsertSEI and contSPS parameters to the video line of the META file. It was reported to help with pixelation... but I can't confirm that it does. But it should have no affect on MKV output.

It's been a while since I've done 3D, but In order to output SBS, you should just add:

OUTPUT_SBS=1

to your BDREBUILDER.INI file. Alternatively you can set it by selecting "Output SBS/OU Movie-Only Output" from the SETTINGS dialog (it sets/resets OUTPUT_SBS). On my system I also have to add:

FRIM_SW_DECODE=1

You should then be able to pick any of the "No Resize" options for output. For example you might choose "MKV Container, NO_RESIZE, AutoGOP, Auto-AC3". In order to set to a certain output size you can select "VBR Target Size..." when you are selecting the ALTERNATE output. You could also choose "One Pass CRF Target Size...".

[Edit] You'll have to use either X264 or X265. I just tried one using NVENCC and it choked on the input. Not sure why, but I'm guessing it either doesn't like the sizing or it has an issue with the AVS. I'll look at it for the next release.

[meadrocks]

mediainfo looks correct on Watchmen Dir Cut, will watch it tonight. Doing Howls Moving Castle next.

[Ch3vr0n]

i thought that switch was needed for was needed for in-mux 3D, or is that another one? I can find alternate. I have enabled the SBS switch. The 2 profiles that semi match what i want i believe are "MP4/MKV Full-SBS (3D)" but they both use intact audio. I don't mind it being downscaled to 5.1 ac3/aac. There's no profile for that.

[jdobbs]

i thought that switch was needed for was needed for in-mux 3D, or is that another one? I can find alternate. I have enabled the SBS switch. The 2 profiles that semi match what i want i believe are "MP4/MKV Full-SBS (3D)" but they both use intact audio. I don't mind it being downscaled to 5.1 ac3/aac. There's no profile for that.Please re-read my response. You don't need to choose a profile that says "Full-SBS" in it. You just need to select one that says "No Resize".

[Ch3vr0n]

I did, but forgive me for asking, but isn't that the opposite of what i asked? i'm trying to create movie-only output type but i can't figure it out. I'd like "MKV, Full-SBS (3D).... I may very well not be understanding things entirely. I've done plenty full disc 3D backups, 3D MKV's to me are a new ballgame.

What's the difference then between full-SBS (3D) and "no resize". Reason why i'm asking is because my home theatre projection system only has 3D options for OU and SBS (Nebula Cosmos). i have no idea what the outcome would be if i pick "no resize"

[cartman0208]

I did only UHD Full Backups with the new version so far but I noticed two things:
Whenever the size-correcting second pass is applied to the main movie, the disk is slightly (5-10%) oversized
Disks with only one pass on the main movie hit the destination size pretty good.

Also after clearing the batch queue, I get a Runtime Error '35601' when clicking on the Batch tab or trying to add the current project to batch.
That persists even when restarting BDRB.

[jdobbs]

I did, but forgive me for asking, but isn't that the opposite of what i asked? . I may very well not be understanding things entirely. I've done plenty full disc 3D backups, 3D MKV's to me are a new ballgame.

What's the difference then between full-SBS (3D) and "no resize". Reason why i'm asking is because my home theatre projection system only has 3D options for OU and SBS (Nebula Cosmos). i have no idea what the outcome would be if i pick "no resize"If you select "No Resize" and you set the switch I mentioned on a 3D source -- you will get full SBS output. You can also get OU if you want by using the TYPE_OF_3D hidden options (see HIDDENOPTS.TXT). You can even switch the views (left/right), for the rare occasion where a player is different, with the SWAP_3D hidden option.

[jdobbs]

I did only UHD Full Backups with the new version so far but I noticed two things:
Whenever the size-correcting second pass is applied to the main movie, the disk is slightly (5-10%) oversized
Disks with only one pass on the main movie hit the destination size pretty good.

Also after clearing the batch queue, I get a Runtime Error '35601' when clicking on the Batch tab or trying to add the current project to batch.
That persists even when restarting BDRB.1. I'll look at the sizing issue.

1. The 35601 error is a weird one. Try deleting the file BDBATCH.INI and see if the problem goes away.

[LowDead]

have tested the new version on the problematic disc...

Good news: No more error on that 60fps 4k mux.

Bad news: New error that I can't continue from.

- [01:17:22] Processing: VID_00341 (15 of 43)
- [01:17:22] Extracting A/V streams [VID_00341]
- Extracting video streams [VID_00341]
- Processed 5823 video frames
- Error in attempt to extract video.
- Processed 5823 video frames
- Processed 5823 video frames
[01:17:41] - Failed to retrieve audio, aborted

//LD

[Sharc]

...........
[Edit] You'll have to use either X264 or X265. I just tried one using NVENCC and it choked on the input. Not sure why, but I'm guessing it either doesn't like the sizing or it has an issue with the AVS. I'll look at it for the next release.
There seems to be a problem with the script. Opening the script in MPC-HC gives the error for line 3 of the script:
"Cannot initialize Intel media SDK session"
#Created by BD Rebuilder - v0.61.17
LoadPlugin("P:\Program Files Video\BD_Rebuilder\tools\frimsource.dll")
SBS=FRIMSource(codec="mvc",filename="F:\BDMV\STREAM\00800.m2ts",filename_dep="F:\BDMV\STREAM\01065.m2ts",layout="sbs",ts=true,platform="sw",cache=24,num_frames=166915)
VIEW1=Crop(SBS,1920,0,1920,1080)
VIEW2=Crop(SBS,0,0,1920,1080)
StackHorizontal(VIEW2,VIEW1)
ConvertToYV12().AssumeFPS(24000,1001)
So it seems not to be related to the NVEncC encoder?
The source is a 1920x1080 3D MVC Blu-ray.

Edit:
All right, I had to put the 'BD_Rebuilder\Tools' folder into the PATH.
Now I am getting the script error:
Crop: you cannot use crop to enlarge or 'shift' a clip

Edit2:
I think that the 3 lines
VIEW1=Crop(SBS,1920,0,1920,1080)
VIEW2=Crop(SBS,0,0,1920,1080)
StackHorizontal(VIEW2,VIEW1)
can be deleted from the script when the parameter 'layout="sbs"' is set, so it seems to work with something like
#Created by BD Rebuilder - v0.61.17
LoadPlugin("P:\Program Files Video\BD_Rebuilder\tools\frimsource.dll")
SBS=FRIMSource(codec="mvc",filename="F:\BDMV\STREAM\00800.m2ts",filename_dep="F:\BDMV\STREAM\01065.m2ts",layout="sbs",ts=true,platform="sw",cache=24,num_frames=166915)
return SBS.converttoYV12().AssumeFPS(24000,1001)

Edit 3: ... and this also works with NVEncC as the encoder :)

Edit4: Pulling my hair...
After been through the steps above, I now found that the original script seems to work fine now. So the solution was probably to include the Tools folder (or the libmfxsw32.dll) in the PATH. Oh well .....
Anyway, happy that it works now with NVEncC as well :cool:

[cartman0208]

1. I'll look at the sizing issue.

1. The 35601 error is a weird one. Try deleting the file BDBATCH.INI and see if the problem goes away.

Forgot to mention, I only used NVENC

Deleted BDBATCH.INI, BDITEM.INI and BDREBUILDER.INI to be sure. Works again and I couldn't reproduce the issue.
I will test some more.

[Ch3vr0n]

Tried and failed with 61.16. One thing i noticed is that the decoding/frameserving sais "FRIMSource", however the decoding process itself is done by DGDecNV, as there's a part about "completing DGIndexing". Picked the option "VBR Target Site (MB) with a value of 8600"


[09/30/20] BD Rebuilder v0.61.16
[17:35:14] Source: TOMB_RAIDER_00098
- Input BD size: 42,66 GB
- Approximate total content: [01:57:50.438]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, Full-SBS (3D), Intact Audio
- Quality: High Quality (Default)
- Output folder: H:\Blu-ray\Encodes\BDRB\
- 3D conversion mode enabled
- Decoding/Frame serving: FRIMSource
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[17:35:16] PHASE ONE, Encoding
- [17:35:16] Processing: VID_00252 (1 of 1)
- [17:35:16] Extracting A/V streams [VID_00252]
[09/30/20] Checking System Settings
- BD-Rebuilder v0.61.16
- Windows Version: 6.2 [9200]
- Working Path Free Space: 467,30GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[09/30/20] Systems Settings Check complete
- [17:45:02] Reencoding video [VID_00252]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 169.521 frames
- Converting output to Side-By-Side 3D Format
- Bitrate: 7.184 Kbs
- [17:45:02] Reencoding: VID_00252, Pass 1 of 2
[17:45:03] - Failed video encode, aborted
----------------------
[09/30/20] BD Rebuilder v0.61.16
[17:48:50] Source: TOMB_RAIDER_00098
- Input BD size: 42,66 GB
- Approximate total content: [01:57:50.438]
- Windows Version: 6.2 [9200]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, NO_RESIZE, AutoGOP, Auto-AC3
- Quality: High Quality (Default)
- Output folder: H:\Blu-ray\Encodes\BDRB\
- 3D conversion mode enabled
- Decoding/Frame serving: FRIMSource
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[17:48:51] PHASE ONE, Encoding
- [17:48:51] Processing: VID_00252 (1 of 1)
- [17:48:51] Extracting A/V streams [VID_00252]
- [17:58:26] Reencoding video [VID_00252]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 169.521 frames
- Converting output to Side-By-Side 3D Format
- Bitrate: 9.236 Kbs
- [17:58:26] Reencoding: VID_00252, Pass 1 of 2
[17:58:27] - Failed video encode, aborted



[Options]
VERSION=0.61.0.16
ENCODER=1
MODE=3
ENCODE_QUALITY=0
ONEPASS_ENCODING=0
AUTO_QUALITY=1
TARGET_SIZE=23500
AUTO_BURN=0
AUDIO_TO_KEEP=dut;eng;nld;und;
SUBS_TO_KEEP=dut;eng;nld;und;
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=3
AVCHD=0
REMOVE_WORKFILES=1
REMOVE_OUTPUT=1
USE_FILTERS=0
BDMV_CERT_ONLY=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
COMPLETION_BEEP=1
OUTPUT_SBS=1
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=4100
#FRIM_SW_DECODE=0
FRIM_SW_ENCODE=1
#SPECIAL_3D_MUX=1

#General Settings
ENABLE_TEST=1
ENABLE_BLANKING=1
BEEP_SOUNDFILE=C:\Program Files (x86)\ImgBurn\Sounds\Success.wav
OUTPUT_FOLDER=H:\Blu-ray\Encodes\BDRB
MINIMIZE_TO_TRAY=1
MOVIEONLY_TYPE=32
ALTCRF=23
ALT_TARGET=8600
ALT_CRF_TARGET=2048
ALTMETHOD=2
ALTAUTOCROP=0
FRIMSOURCE=0
NVENC_CAPABLE=1

[Paths]
SOURCE_PATH=L:\
DGIndexNV=C:\Program Files (x86)\BD_Rebuilder\Tools\dgdecnv\x32 Binaries\DGIndexNV.exe
DGDecNV=C:\Program Files (x86)\BD_Rebuilder\Tools\dgdecnv\x32 Binaries\DGDecodeNV.dll
WORKING_PATH=H:\Temp\

Will try 61.17 next. just noticed the new version.

** edit ** still failed with 61.17 but worked when i switched encoder from NVEnc encoders to "x264 / x265". Don't know if i overlooked you saying that part, if you didn't, maybe it's an idea to auto use that as a fallback?

[Sharc]

Try 1-pass (constant quality mode, CQM) encoding.
NVEnc does not support classic 2-pass encoding.

[Ch3vr0n]

Yes it does, and i didn't specify any pass. BDRB did. I'm using automatic quality settings.

[Sharc]

It doesn't. See NVEnc documentation. Its '2-pass' applies to single frames rather than for the entire video. This is different from the classic global 2-pass which uses the stats file from pass 1.

In the Alternate Movie-Only output, select 'Constant Quality Mode (CQM)' and put your quality value there, e.g. 22.
Works perfectly here.

[jdobbs]

I've updated the first post of this thread with a link to the latest release of BD Rebuilder (v0.61.17). Changes for this release:- Corrected an issue in which attempts to
perform a size-correcting second pass on
an AVC source could result in an error
"PredictAndEncode() 00011 2994".
- Made adjustments to correct for bad time
codes in .SUP files that could result in
certain oddly formatted multi-part sources
(shows itself as subtitles that extend
well beyond the lenght of the movie)
- Added changes that will prevent occurance
of some "Bitstream exception" errors.
- Implemented default use of v2.6.16 of
TSMUXER for all TSMUXER functions. In
order to disable and return to v2.6.12
use hidden option "ENABLE_NEW_TSMUXER=0".
- Added a routine that catches previously
undetected errors in AAC encoding and then
attempts reencoding via a new method.
- Corrected a setting used with HEVC that
could assert HDR when it is not present in
the original source.
- Updated TSMUXER4K to the 2020-09-25 build.
- Other minor corrections and cosmetic fixes.
There have been no changes made since the test release of this version.

[ggtop]

Hi jdobbs,

can you please check if setting "MULTIPROCESS" is deprecated in the last version?
I have it set to "MULTIPROCESS=2" in my INI and used to see "- Decoding/Frame serving: DGDecNV [2-way]" in the log, but using 0.61.17 I see only "- Decoding/Frame serving: DGDecNV" and one x264 process running. No big deal as it wasn't the speed gain on my system anyway, but I wanted to mention as I remember you changed something for cartman increasing max thread limit (http://forum.doom9.org/showthread.php?p=1919764#post1919764).

Thank you,
ggtop

[LowDead]

have tested the new version on the problematic disc...

Good news: No more error on that 60fps 4k mux.

Bad news: New error that I can't continue from.



//LD

Seems I did this test from the already processed/encoded test output instead of the original folder. I'm running from original folder right now and there's no problem at all (yet...) ;)

It didn't work.. I almost got through the whole disc but managed to get the same error as before:

- [12:59:31] Multiplexing M2TS
- [13:00:51] Processing: VID_00359 (33 of 43)
- [13:00:51] Extracting A/V streams [VID_00359]
- Extracting video streams [VID_00359]
- 93.8% complete
- Error in attempt to extract video.
- 93.8% complete
- 93.8% complete
[13:15:43] - Failed to retrieve audio, aborted

//LD

[jdobbs]

Seems I did this test from the already processed/encoded test output instead of the original folder. I'm running from original folder right now and there's no problem at all (yet...) ;)

It didn't work.. I almost got through the whole disc but managed to get the same error as before:

- [12:59:31] Multiplexing M2TS
- [13:00:51] Processing: VID_00359 (33 of 43)
- [13:00:51] Extracting A/V streams [VID_00359]
- Extracting video streams [VID_00359]
- 93.8% complete
- Error in attempt to extract video.
- 93.8% complete
- 93.8% complete
[13:15:43] - Failed to retrieve audio, aborted

//LDIt's going to be hard to debug from just that. Are you positive you have plenty of disc space. I got an error almost identical to that a couple days ago -- and then realized my disc had gotten full.

[LowDead]

It's going to be hard to debug from just that. Are you positive you have plenty of disc space. I got an error almost identical to that a couple days ago -- and then realized my disc had gotten full.

hehe.. You nailed it. How could I miss that.. I should sleep at night, not sit by the computer when my eyes barely can see straight.. ghaa. coffee. must. have. :D

Sorry for that. Everything is working as it should now. No more errors. Please move along, nothing to see here :thanks:

//LD

[jdobbs]

hehe.. You nailed it. How could I miss that.. I should sleep at night, not sit by the computer when my eyes barely can see straight.. ghaa. coffee. must. have. :D

Sorry for that. Everything is working as it should now. No more errors. Please move along, nothing to see here :thanks:

//LDGood to hear.

[LowDead]

With successful tests of Full UHD x265 encodes resulting in extremely super sweet quality i'm eager to begin testing backup using the NVEnc encoder.
And I was wondering a bit about the encoder settings. Am I right to think that CQM is the constant quality option and the VBR is the same as the old-school version of VBR?
I was somewhat thrown off by Sharc's posts #30037 and #30039. I will not do any alternative output, only full UHDs.

//LD

[Sharc]

With successful tests of Full UHD x265 encodes resulting in extremely super sweet quality i'm eager to begin testing backup using the NVEnc encoder.
And I was wondering a bit about the encoder settings. Am I right to think that CQM is the constant quality option and the VBR is the same as the old-school version of VBR?
I was somewhat thrown off by Sharc's posts #30037 and #30039. I will not do any alternative output, only full UHDs.

//LD
NVEnc supports both quality based (CQM) and bitrate (target file size) based 'VBR' encoding, and so does BD-RB.
My posts just recalled the fact that - under the hood - '2-pass' has a different meaning for NVEnc than for x264/x265. This has been discussed further up in the thread. You shouldn't have to worry much about this. You can try BD-RB's options and settings. What isn't available is greyed out in the menus or hidden (unless there is a bug ....).
So for full backups using NVEnc you will find under 'Settings->Encoder Settings' the options 'One Pass (CQM) Encoding' (quality based) and 'One Pass (VBR) Encoding' (bitrate based acc. target size). In the case of NVEnc you have to select one of these. You can't disable both to invoke the classic 2-pass encoding as you could for x264/x265. It will however internally trigger '2-passes' as per NVIDIA's per frame definition.
Sorry to have caused some confusion.

Added:
See the discussion around here:
https://forum.doom9.org/showthread.php?p=1918354#post1918354

[LowDead]

NVEnc supports both quality based (CQM) and bitrate (target file size) based 'VBR' encoding, and so does BD-RB.
My posts just recalled the fact that - under the hood - '2-pass' has a different meaning for NVEnc than for x264/x265. This has been discussed further up in the thread. You shouldn't have to worry much about this. You can try BD-RB's options and settings. What isn't available is greyed out in the menus or hidden (unless there is a bug ....).
So for full backups using NVEnc you will find under 'Settings->Encoder Settings' the options 'One Pass (CQM) Encoding' (quality based) and 'One Pass (VBR) Encoding' (bitrate based acc. target size). In the case of NVEnc you have to select one of these. You can't disable both to invoke the classic 2-pass encoding as you could for x264/x265. It will however internally trigger '2-passes' as per NVIDIA's per frame definition.
Sorry to have caused some confusion.

Added:
See the discussion around here:
https://forum.doom9.org/showthread.php?p=1918354#post1918354

Great, Thanks for the clarification!

//LD

[FilipeAmadeuO]

@jdobbs
Is there any chance to use a mounted ISO or ISO (without protection) as the source for BDRebuilder ?

[prologic]

@jdobbs
Is there any chance to use a mounted ISO or ISO (without protection) as the source for BDRebuilder ?

I mount iso files regulary , for use in BDRebuilder.

[AmigaFuture]

Hi jdobbs,

can you please check if setting "MULTIPROCESS" is deprecated in the last version?
I have it set to "MULTIPROCESS=2" in my INI and used to see "- Decoding/Frame serving: DGDecNV [2-way]" in the log, but using 0.61.17 I see only "- Decoding/Frame serving: DGDecNV" and one x264 process running.

I just noticed the number isn't there also. Looking at Task Manager, I see 1 process also. I wondered what happened.

Update: I noticed the "bug" from a while back seems to be gone. Perhaps with newer tsMuxer. 2 movies that I had a problem with video corruption so far, are clean with making MKV's from previous BD-RB processing.

[jdobbs]

@jdobbs
Is there any chance to use a mounted ISO or ISO (without protection) as the source for BDRebuilder ?As prologic said, it shouldn't be an issue... but it is usually faster to rip it to hard drive first and then use the ripped image (either mounted as an ISO or as a folder).

[jdobbs]

Hi jdobbs,

can you please check if setting "MULTIPROCESS" is deprecated in the last version?
I have it set to "MULTIPROCESS=2" in my INI and used to see "- Decoding/Frame serving: DGDecNV [2-way]" in the log, but using 0.61.17 I see only "- Decoding/Frame serving: DGDecNV" and one x264 process running. No big deal as it wasn't the speed gain on my system anyway, but I wanted to mention as I remember you changed something for cartman increasing max thread limit (http://forum.doom9.org/showthread.php?p=1919764#post1919764).

Thank you,
ggtopI've disabled MULTIPROCESS when the new TSMUXER version is enabled. Honestly, though, since X264/X265 became multithreaded (a long time ago) it doesn't really serve much of a function anymore.

BTW. The recent change I made in response to cartman's post increases the number of THREADS you can specify -- that really isn't related to MULTIPROCESS (which actually launches multiple instances of the encoder -- each of which could be multithreaded) function.

While MULTIPROCESS isn't actually deprecated yet -- you should probably expect it to be sometime soon.

[ggtop]

Thank you for the clarification.
Thought it might be worth to ask as it wasn't stated in the changes.
Glad to hear it wasn't accidentially and as I said no problem for me speed-wise. I was just used to have that setting.

Have a nice weekend,
ggtop

[AmigaFuture]

I don't get it. Going back to .13 I notice a big speed difference with MULTIPROCESS=6 or less...with this Ryzen. With MP disabled, it's a bit slower with current .17. I'm using an a GTX so the new nVIDIA doesn't really show an increase for me (Sad face..hehe). Even if I bring the threads up. Perhaps I'm missing something?? I also have THEADS set to AUTO and I tried higher or lower. Speed wasn't near what it was before. I did go Ryzen so I could get some faster speeds previous to my 10+ year old system. It shouldn't be because I'm still using Windows 7.. I couple post some pictures showing differences, if you like? I might be very dense about how this is supposed to be better to rely on THREADS and not MULTIPROCESS. Hmm..

[jdobbs]

I don't get it. Going back to .13 I notice a big speed difference with MULTIPROCESS=6 or less...with this Ryzen. With MP disabled, it's a bit slower with current .17. I'm using an a GTX so the new nVIDIA doesn't really show an increase for me (Sad face..hehe). Even if I bring the threads up. Perhaps I'm missing something?? I also have THEADS set to AUTO and I tried higher or lower. Speed wasn't near what it was before. I did go Ryzen so I could get some faster speeds previous to my 10+ year old system. It shouldn't be because I'm still using Windows 7.. I couple post some pictures showing differences, if you like? I might be very dense about how this is supposed to be better to rely on THREADS and not MULTIPROCESS. Hmm..It isn't "better" to rely on THREADS. As I said, the two aren't really related. One is applied against available threads supported by the processor and the other simply runs multiple instances of encoder against sections of the source to be encoded.

I will say that I am surprised that your Ryzen is running faster with MULTIPROCESS. I'm also using an AMD processor -- and I get 100% of my processor applied to the encode with or without it.

The purpose of MULTIPROCESS was to try and get a higher percentage of available CPU capability applied to encoding. When you are encoding -- could you please run task manager and see if you are running at a higher percentage of CPU with MULTIPROCESS?

If so, I can always reenable it. I only disabled it to avoid having to adjust the new code I wrote in support of the latest TSMUXER for it. As I said, I'm actually surprised it is accomplishing anything these days.

[AmigaFuture]

Sure thing, Boss. :) I took the 2nd picture of MP because I wanted the average to happen to give better results. I was surprised also about the Ryzen. Not sure why..

[jdobbs]

@AmigaFuture

Interesting. I'll reenable it for the next release. I'll have to go through and make some changes -- and then do some testing.