BD Rebuilder Beta - Bug Reports Only

[Sharc]

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...
VBR (variable bitrate) and ABR (average bitrate) and CQM (or CRF) are different things. There is no contradiction.
VBR (variable bitrate) is a means to improve compression efficiency maintaining a certain perceptual quality by dynamically allocating less bitrate to less critical (simple) scenes and more bitrate to complex scenes where the losses of the lossy compression would become noticeable to the viewer. Hence VBR is improving compression efficiency by not wasting bits for less complex scenes where the viewer subjectively does not notice the losses.
VBR is used for CQM (constant quality) encodes as well as for ABR (average bitrate) encodes. With ABR the encoder controls the bitrate (which is still variable VBR bitrate though) such as to obtain a desired average bitrate (means a target file size eventually), whereas CQM (or CRF) targets a certain perceptual quality rather than a bitrate or a certain file size. The bitrate is for both cases variable, i.e. always VBR.
Constant bitrate (CBR) is used for special purposes only these days.
Just google for VBR, CBR, ABR, CRF, VFR etc., or collect some explanations from here: https://slhck.info/video/2017/03/01/rate-control.html or from here https://en.wikipedia.org/wiki/Variable_bitrate

[hautem]

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

If you don't mind me asking, what was the Blu-ray source of the burned copy that wouldn't play in your BDP-83? I'm having a similar problem that I initially tried addressing at RedFox here:

https://forum.redfox.bz/threads/solved-screenpass-problem-with-knives-out-blue-ray.78237/page-4#post-534479

but I'm not so sure that's the problem. Another poster in that thread had a similar problem with that title (Knives Out) and the burned copy not playing in a stand alone Blu-ray player. Also reported that with "Judy" (another recent Lionsgate release) on Blu-ray.

https://forum.redfox.bz/threads/solved-screenpass-problem-with-knives-out-blue-ray.78237/page-3#post-513955

I'm just wondering if this might be a specific title or a larger Lionsgate issue (or maybe I just have an entire spindle of blank discs that have gone bad).

If you feel so inclined...thanks.

[jdobbs]

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...I'll take a look at it.

[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...

VBR (variable bitrate) is a means to improve compression efficiency maintaining a certain perceptual quality by dynamically allocating less bitrate to less critical (simple) scenes and more bitrate to complex scenes where the losses of the lossy compression would become noticeable to the viewer. Hence VBR is improving compression efficiency by not wasting bits for less complex scenes where the viewer subjectively does not notice the losses.Which is why I prefer VBR over CQM as it is supposed to provide better quality. I'm just confused as to why BDRB is choosing ABR when VBR is selected. Thanks for your reply.

I'll take a look at it.Thank you sir. I'll patiently await your findings.

[jdobbs]

Which is why I prefer VBR over CQM as it is supposed to provide better quality. I'm just confused as to why BDRB is choosing ABR when VBR is selected. Thanks for your reply.

Thank you sir. I'll patiently await your findings.

ABR=Average Bitrate
CQM=Constant Quality Mode

Actually ABR and CQM are both VBR (Variable Bitrate). ABR uses VBR but tries to keep the overall bitrate at a certain level to control the output size. ABR is also sometimes called "one pass" VBR, as it (usually) uses a sliding window to allocate bits while keeping the average at the specified bitrate. CQM uses VBR but tries to keep a specified quality at a certain level without regard to output size. The X264/X265 equivalent to CQM is called CRF (constant rate factor).

There's also a third common type of VBR called "two pass" or "multipass". In two pass a non-encoding pass is performed first to analyze the complexity of all frames in the source. Then, the available bits can be allocated across the entire video to give the best quality at a given bitrate. Two-pass is available in X264 and X265, but not in NVENC (although there is a confusing reference to two pass in the docs that doesn't actually qualify as true "two pass").

The alternative to VBR would be CBR (Constant Bitrate). VBR is generally superior to CBR because bits can be allocated as needed to different parts of the video, while CBR uses the same bitrate over the entire video usually resulting in too many bits being allocated to some parts and too few to others. But some methods of distributing video over digital pathways require CBR. Because of it's encoding purpose, BD-RB always uses VBR in its encodes.

In my experience CQM provides better quality than ABR -- but it's output size varies based upon the complexity of the content. To combat that, BD-RB does a prediction using samples of the source. It works pretty well most of the time -- but it can occasionally under/over size.

Now... with that said. My understanding of your problem was that you select one of the choices but the checkmark on the dropdown menu wasn't matching what you chose... is that correct, or did I misunderstand?


@Sharc -- sorry that I repeated much of what you were explaining... I think I probably added to the confusion by adding a "(VBR)" behind the ABR selection in the dropdown menu but not doing so to the CQM selection.

[spotswood]

VBR is generally superior to CBR because bits can be allocated as needed to different parts of the video, while CBR uses the same bitrate over the entire video usually resulting in too many bits being allocated to some parts and too few to others. Because of it's encoding purpose, BD-RB always uses VBR in its encodes.Which is why I was confused as to why I was seeing ABR mode...
Now... with that said. My understanding of your problem was that you select one of the choices but the checkmark on the dropdown menu wasn't matching what you chose... is that correct, or did I misunderstand?No, when I select VBR Mode in the dropdown after previously using CQM, when I restart the job the log shows ABR being used rather than VBR (see pic in previous post). But here's something weird... when restarting the same job after changing settings, BDRB asks if I want to delete the previous files which I select yes. But with the folder open in which the files are located (.log and .inf), the files are not deleted, unless it happens so fast that I don't see it. My guess is that the files are not deleted and BDRB uses the info from the previous CQM job? I don't know.

After trying different settings and still getting ABR mode when selecting VBR, I physically deleted the previous .log and .inf files so BDRB has to create new ones. When I start the "new" job, voila VBR mode. Weird huh? I knew I wasn't seeing things last night! So now I make sure to physically delete the previous .log and .inf files before starting a new job and BDRB uses VBR mode.

UPDATE:
Well I might have spoke too soon. I just started another job using the same settings as the one before that used VBR mode and BDRB is back to ABR mode. So confusing and frustrating. What I tried this time was using Automatic Quality and BDRB chose Very Fast/VBR. I aborted and went back to Highest Quality and VBR mode was kept. So I don't know at this point. I guess I'll go back and forth between settings until I get VBR for what I'm running. Sorry for all the confusion. Maybe you can come up with why it won't just use VBR when selected. Thanks for all your help...

[cartman0208]

...
Now... with that said. My understanding of your problem was that you select one of the choices but the checkmark on the dropdown menu wasn't matching what you chose... is that correct, or did I misunderstand?
...

I'm pretty sure, that's what is causing the confusion here.
If the x264 / x264 encoder is selected, CRF and ABR appear in the menu.
If set to NVENC, you can see CQM and VBR.
Easiest solution would be to substitute the V with an A in the NVENC menu :D

To repeat what starc and JD already said ...
BDRB can do 2 MODES: Average Bitrate (ABR) and Constant Quality (CRF/CQM)
Variable Bitrate (VBR) is used in both modes ...

Please correct me, if that is wrong.

[Sharc]

.... So confusing and frustrating. What I tried this time was using Automatic Quality and BDRB chose Very Fast/VBR. I aborted and went back to Highest Quality and VBR mode was kept. So I don't know at this point. I guess I'll go back and forth between settings until I get VBR for what I'm running. Sorry for all the confusion. Maybe you can come up with why it won't just use VBR when selected. Thanks for all your help...
Whichever encoding mode you select (CQM or ABR, 1-pass or 2-pass), the encoding will always be done with VBR (variable bitrate). The menu or log may or may not tell this explicitly for every setting.
CQM or ABR (1-pass or 2-pass) are just different methods for how to steer the bitrate -- which is however always variable (=VBR). Otherwise you wouldn't get a decent quality for blu-ray backups on a DVD 9.
I think this is causing your confusion, no?

Hint: When publishing your settings you should do this in text form rather than append it as an attachment (.png) which needs to be approved by a moderator before anyone can see it.

Edit:
I just read cartman's comment:
I'm pretty sure, that's what is causing the confusion here.
If the x264 / x264 encoder is selected, CRF and ABR appear in the menu.
If set to NVENC, you can see CQM and VBR.
Easiest solution would be to substitute the V with an A in the NVENC menu
Good point.

[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.

@ jdobbs

Any chance to take a look what I posted in response to your inquiry?

Many thanks for your assistance on this! Sending some AMZN cards for the development and support.

Cheers

[jdobbs]

@spotswood

And... as I explained in my post and others are explaining -- ABR is VBR.

As cartman0208 said, I think what is causing the confusion is that I used different terms in the dropdown menu if you select X264/X265 than if you select NVENCC.

In X264/X265 the two modes you can select are:

- One Pass (CRF) Encoding
- One Pass (ABR) Encoding

If either is selected, you are doing one-pass encoding. If neither are selected you are doing two-pass encoding.

In NVENCC the two modes you can select are:

- One Pass (CQM) Encoding
- One Pass (VBR) Encoding

One of the two is always selected because there is no two-pass mode in NVENCC.

My guess is that you are switching between X264/X265 mode and NVENCC and that is causing the confusion when you see the "ABR" change to "VBR". But, since ABR is VBR -- it really isn't a conflict. I'll change the name on the second option of one or the other of the selections so they match to avoid confusion.

[jdobbs]

@ jdobbs

Any chance to take a look what I posted in response to your inquiry?

Many thanks for your assistance on this! Sending some AMZN cards for the development and support.

CheersFrom your last post (https://forum.doom9.org/showthread.php?p=1939294#post1939294) it looks like the encode is actually working when you run it from the command line. That's the confusing part.

[gamete]

@jdobbs

Can you help me with this error

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

[Jackie Treehorn]

From your last post (https://forum.doom9.org/showthread.php?p=1939294#post1939294) it looks like the encode is actually working when you run it from the command line. That's the confusing part.

Below there seems to be some errors in command line paste from the last command in the BD folder; it does seem to complete that portion of the encode tho....

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

C:\Windows\system32>"C:\Users\James\Documents\BD_Rebuilder\tools\x264L-64.exe" "C:\USERS\JAMES\DOCUMENTS\27027846_LADY_IN_THE_WATER\BDMV\STREAM\00000.m2ts" --preset medium --bluray-compat --demuxer lavf --force-cfr --b-pyramid none --weightp 1 --slow-firstpass --qpmin=0 --crf 23 --level 4.0 --qpfile "C:\USERS\JAMES\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\JAMES\DOCUMENTS\WORKING\WORKFILES\00000.m2ts.264.stats" --output "C:\USERS\JAMES\DOCUMENTS\WORKING\WORKFILES\00000.m2ts.264"
[mpegts @ 00000000001c7080] Failed to open codec in av_find_stream_info
[mpegts @ 00000000001c7080] start time for stream 4 is not set in estimate_timings_from_pts
[mpegts @ 00000000001c7080] start time for stream 5 is not set in estimate_timings_from_pts
[mpegts @ 00000000001c7080] start time for stream 6 is not set in estimate_timings_from_pts
[mpegts @ 00000000001c7080] start time for stream 7 is not set in estimate_timings_from_pts
[mpegts @ 00000000001c7080] Could not find codec parameters for stream 1 (Audio: ac3 (AC-3 / 0x332D4341), 0 channels): unspecified sample rate
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mpegts @ 00000000001c7080] Could not find codec parameters for stream 2 (Audio: ac3 (AC-3 / 0x332D4341), 0 channels): unspecified sample rate
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mpegts @ 00000000001c7080] Could not find codec parameters for stream 3 (Audio: ac3 (AC-3 / 0x332D4341), 0 channels): unspecified sample rate
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mpegts @ 00000000001c7080] Could not find codec parameters for stream 4 (Subtitle: hdmv_pgs_subtitle ([144][0][0][0] / 0x0090)): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mpegts @ 00000000001c7080] Could not find codec parameters for stream 5 (Subtitle: hdmv_pgs_subtitle ([144][0][0][0] / 0x0090)): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mpegts @ 00000000001c7080] Could not find codec parameters for stream 6 (Subtitle: hdmv_pgs_subtitle ([144][0][0][0] / 0x0090)): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
[mpegts @ 00000000001c7080] Could not find codec parameters for stream 7 (Subtitle: hdmv_pgs_subtitle ([144][0][0][0] / 0x0090)): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
lavf [info]: 1920x1080p 1:1 @ 24000/1001 fps (cfr)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 AVX2 LZCNT BMI2
x264 [info]: profile High, level 4.0
x264 [info]: frame I:7940 Avg QP:20.27 size: 46872
x264 [info]: frame P:62583 Avg QP:21.49 size: 17541
x264 [info]: frame B:87221 Avg QP:23.20 size: 6073
x264 [info]: consecutive B-frames: 22.4% 4.1% 23.0% 50.5%
x264 [info]: mb I I16..4: 23.9% 72.1% 4.0%
x264 [info]: mb P I16..4: 3.7% 7.6% 0.1% P16..4: 40.4% 5.8% 5.5% 0.0% 0.0% skip:36.9%
x264 [info]: mb B I16..4: 0.3% 0.4% 0.0% B16..8: 30.7% 1.0% 0.1% direct: 1.3% skip:66.2% L0:36.5% L1:62.4% BI: 1.1%
x264 [info]: 8x8 transform intra:69.0% inter:93.1%
x264 [info]: coded y,uvDC,uvAC intra: 39.3% 52.0% 9.3% inter: 10.3% 16.5% 0.1%
x264 [info]: i16 v,h,dc,p: 41% 19% 8% 32%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 30% 17% 31% 3% 4% 4% 4% 4% 3%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 37% 18% 12% 5% 8% 7% 6% 5% 3%
x264 [info]: i8c dc,h,v,p: 58% 19% 21% 3%
x264 [info]: Weighted P-Frames: Y:2.8% UV:0.9%
x264 [info]: ref P L0: 68.9% 18.9% 12.2%
x264 [info]: kb/s:2431.46

encoded 157744 frames, 38.89 fps, 2431.46 kb/s

C:\Windows\system32>

[Jackie Treehorn]

It appears this is the error I keep getting....

[14:46:57]PHASE ONE complete
[14:46:57]PHASE TWO - Rebuild Started
- [14:46:57] Building ALTERNATE OUTPUT Structure
- ERROR in attempt to mux (MP4BOX)
[14:46:58] - Failed to REBUILD

[spotswood]

Whichever encoding mode you select (CQM or ABR, 1-pass or 2-pass), the encoding will always be done with VBR (variable bitrate). The menu or log may or may not tell this explicitly for every setting. CQM or ABR (1-pass or 2-pass) are just different methods for how to steer the bitrate -- which is however always variable (=VBR). I think this is causing your confusion, no?
My confusion comes from the fact that BDRB keeps switching modes (or nomenclature) when running the exact same job with the exact same source/settings. See below:

This one I did last night that BDRB shows using VBR...

----------------------
[03/29/21] BD Rebuilder v0.61.21
[13:44:21] Source: GLADIATOR_D1_00010
- Input BD size: 37.47 GB
- Approximate total content: [02:50:58.873]
- Target BD size: 8.00 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: High Quality (Default), VBR
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[13:44:21] PHASE ONE, Encoding
- [13:44:21] Processing: VID_00102 (1 of 27)
- [13:44:22] Extracting A/V streams [VID_00102]

This one I did this morning using the exact same source/settings that BDRB shows using ABR... :confused:

----------------------
[03/30/21] BD Rebuilder v0.61.21
[09:26:40] Source: GLADIATOR_D1_00010
- Input BD size: 37.47 GB
- Approximate total content: [02:50:58.873]
- Target BD size: 8.00 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: High Quality (Default), ABR
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[09:26:40] PHASE ONE, Encoding
- [09:26:40] Processing: VID_00102 (1 of 27)
- [09:26:40] Extracting A/V streams [VID_00102]
EXIT CODE: 259
[09:26:57]PHASE ONE aborted by user requestWhy is BDRB changing modes (or nomenclature) when using the exact same decoder/source/settings? That's the "the crux of the biscuit."

My guess is that you are switching between X264/X265 mode and NVENCC and that is causing the confusion when you see the "ABR" change to "VBR". But, since ABR is VBR -- it really isn't a conflict. I'll change the name on the second option of one or the other of the selections so they match to avoid confusion.But I'm not using X264/X265. I'm using NVENC and seeing VBR change to ABR and visa-versa when running the exact same job with the exact same decoder/source/settings, as my examples above show. If you want to change the lettering to avoid confusion that's fine, but I think there's something else going on internally that's causing this, but I don't know. If it's all VBR as everyone is suggesting, replace the A with a V. Sorry to stir up a hornets nest. As always jdobbs, thanks for all your hard work. I'll accept any solution you come up with...

[cartman0208]

My confusion comes from the fact that BDRB keeps switching modes (or nomenclature) when running the exact same job with the exact same source/settings. See below:
...

Ok, now I think I understand.
...and I'm able to reproduce it...

Start BDRB, set VBR -> VBR is in the log
Abort encode, exit BDRB
Start BDRB, just push the "Backup" button -> ABR is in the log

Hope that helps, JD ;)

[spotswood]

My confusion comes from the fact that BDRB keeps switching modes (or nomenclature) when running the exact same job with the exact same source/settings...

Ok, now I think I understand.
...and I'm able to reproduce it...

Start BDRB, set VBR -> VBR is in the log
Abort encode, exit BDRB
Start BDRB, just push the "Backup" button -> ABR is in the log

Hope that helps, JD ;)YES, EXACTLY! I'm not going crazy!!! Although I'm not always exiting BDRB in between encodes. Also hope that helps... ;^)

[jdobbs]

Ok, now I think I understand.
...and I'm able to reproduce it...

Start BDRB, set VBR -> VBR is in the log
Abort encode, exit BDRB
Start BDRB, just push the "Backup" button -> ABR is in the log

Hope that helps, JD ;)Yeah. I see it. The text that it uses when starting is different than the text used when first selecting.

I'll make it consistent for the next release. But, it's just a cosmetic fix -- the processing works the same either way.

[spotswood]

Yeah. I see it. The text that it uses when starting is different than the text used when first selecting.

I'll make it consistent for the next release. But, it's just a cosmetic fix -- the processing works the same either way.Great! Bug Vanquished! V is for Victory! VBR Rules! Sorry for any convusion (pun intended). :D

[cartman0208]

...
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 2
x265 [info]: Keyframe min / max / scenecut / bias: 1 / 24 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 15 / 4 / 0
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 2 / on / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : ABR-20153 kbps / 0.60
x265 [info]: VBV/HRD buffer / max-rate / init : 45000 / 48000 / 0.900
x265 [info]: tools: rd=2 psy-rd=2.00 early-skip rskip signhide tmvp fast-intra
x265 [info]: tools: strong-intra-smoothing lslices=8 deblock sao stats-write
x265 [error]: malloc of size 20951040 failedime=00:00:00.79 bitrate=4772805.4kbits/s speed=0.723x
x265 [error]: memory allocation failure, aborting encode
x265 [info]: consecutive B-frames: 100.0% 0.0% 0.0% 0.0% 0.0%

encoded 0 frames
aborted at input frame 23, output frame 0
av_interleaved_write_frame(): Broken pipe
Error writing trailer of pipe:: Broken pipetime=00:00:01.16 bitrate=4602347.3kbits/s speed=0.667x
frame= 28 fps= 10 q=-0.0 Lsize= 656100kB time=00:00:01.16 bitrate=4602347.3kbits/s speed=0.421x
video:14kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 4544317.000000%
Conversion failed!
...


That seems not right, might be something wrong with the source?

[gamete]

I dont know
Now i get backup
First with dvdfab without compression
After with bdrebuilder in bd25

First time i have problem with a backup

[Lathe]

@Lathe

If you don't mind me asking, what was the Blu-ray source of the burned copy that wouldn't play in your BDP-83? I'm having a similar problem that I initially tried addressing at RedFox here:

https://forum.redfox.bz/threads/solved-screenpass-problem-with-knives-out-blue-ray.78237/page-4#post-534479

but I'm not so sure that's the problem. Another poster in that thread had a similar problem with that title (Knives Out) and the burned copy not playing in a stand alone Blu-ray player. Also reported that with "Judy" (another recent Lionsgate release) on Blu-ray.

https://forum.redfox.bz/threads/solved-screenpass-problem-with-knives-out-blue-ray.78237/page-3#post-513955

I'm just wondering if this might be a specific title or a larger Lionsgate issue (or maybe I just have an entire spindle of blank discs that have gone bad).

If you feel so inclined...thanks.

It's been a little while ago (my fault) so I'm not sure, but I believe it was the recent Blu-ray release of 'BREAKDOWN' from Imprint in Australia, but ripped region free of course. Again, in my case it SEEMS that the only difference between a Blu-ray disc burned after being re-encoded by BDRB playing and not playing was using an older version of TSMuxer instead of whatever newer version is included with BDRB. As soon as I took the raw re-encoded files from the 'Workfiles' folder and remuxed them with the older version of TSMuxer, the resulting Blu-ray played perfectly.

[Lathe]

Great! Bug Vanquished! V is for Victory! VBR Rules! Sorry for any convusion (pun intended). :D

https://lh3.googleusercontent.com/pw/ACtC-3c2olx_T2Z4d60deJD2Bl9c6EXVBZZgbiLSyMEgyEeMTAb0e6UelBHdUtnS8KnCl6OSwB9o48jBTG6y-81vn2KODEAy_CucUGLZaPHQDF1_4oynIDNX1XQ01e96_9dmkw-UmgXyo3DgsGuoAjR9NJn0Tw=w500-h208-no?authuser=0

[hautem]

It's been a little while ago (my fault) so I'm not sure, but I believe it was the recent Blu-ray release of 'BREAKDOWN' from Imprint in Australia, but ripped region free of course. Again, in my case it SEEMS that the only difference between a Blu-ray disc burned after being re-encoded by BDRB playing and not playing was using an older version of TSMuxer instead of whatever newer version is included with BDRB. As soon as I took the raw re-encoded files from the 'Workfiles' folder and remuxed them with the older version of TSMuxer, the resulting Blu-ray played perfectly.

@Lathe

Thanks much for the reply/info. I was just curious if it was another Lionsgate release.

[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?

[spotswood]

Great! Bug Vanquished! V is for Victory! VBR Rules! Sorry for any convusion (pun intended). :D

https://lh3.googleusercontent.com/pw/ACtC-3c2olx_T2Z4d60deJD2Bl9c6EXVBZZgbiLSyMEgyEeMTAb0e6UelBHdUtnS8KnCl6OSwB9o48jBTG6y-81vn2KODEAy_CucUGLZaPHQDF1_4oynIDNX1XQ01e96_9dmkw-UmgXyo3DgsGuoAjR9NJn0Tw=w500-h208-no?authuser=0?????

[Lathe]

?????

Your PUN! :rolleyes:

[Lathe]

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

Well, I just got this stimulus dumped in my lap and I don't really have a lot of expenses, so I thought it would be a good time to send something JD's way.

I kinda wanted to help out gonca too. I feel kind of sorry for him way up there in the Great North, isolated deep in the snowy forest in that ramshackle cabin of his. But, I KNOW that he would just spend it on Moose Pheromones. Sometimes tough love is best... (not to be confused with Moose love)

[cartman0208]

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?

I'd guess, about the same time ... the whole video needs to be reencoded, just with a higher bitrate.

Why don't you just try it?

[kpic]

So I'm not sure if this is a 'bug', a known limitation or I have an internal setting wrong? Using latest BDRB 0.61.21 and I am sending through a UHD title that has an additional audio track muxed in (I am doing testing to add in audio\subtitle tracks to existing UHD title & have thread over in the "Blu-ray Authoring' section)

Anyway this title has 2 audio tracks; DTS 4.0, DTS 2.0 I have muxed in an additional track & clipinfo that is DTS-HD 7.1 (BDRB reads it ok upon import) - so it reads it all correctly when importing. I set everything as export to BD-50 & Full Backup and the version that has been output now has converted my DTS-HD 7.1 track to a DTS 5.1 track (So it now shows DTS 4.0, 2.0 & 5.1 where before BDRB it showed DTS 4.0, 2.0 & DTS-HD MA 7.1)

Is this a limitation of BDRB, or did it do something on purpose to convert the DTS-HD 7.1 track to DTS 5.1?

[jdobbs]

So I'm not sure if this is a 'bug', a known limitation or I have an internal setting wrong? Using latest BDRB 0.61.21 and I am sending through a UHD title that has an additional audio track muxed in (I am doing testing to add in audio\subtitle tracks to existing UHD title & have thread over in the "Blu-ray Authoring' section)

Anyway this title has 2 audio tracks; DTS 4.0, DTS 2.0 I have muxed in an additional track & clipinfo that is DTS-HD 7.1 (BDRB reads it ok upon import) - so it reads it all correctly when importing. I set everything as export to BD-50 & Full Backup and the version that has been output now has converted my DTS-HD 7.1 track to a DTS 5.1 track (So it now shows DTS 4.0, 2.0 & 5.1 where before BDRB it showed DTS 4.0, 2.0 & DTS-HD MA 7.1)

Is this a limitation of BDRB, or did it do something on purpose to convert the DTS-HD 7.1 track to DTS 5.1?BD-RB can change a 7.1 track to a 5.1 track is if it is being reencoded (standard AC3 doesn't support 7.1). Since your description says it is still DTS in the output -- I don't see how that could be the case. It might also happen if the core audio is being kept and the core is 5.1.

If I understand correctly, you have created a file (MKV, MP4, M2TS?) in which you have muxed in a DTS 7.1 track and then imported it into BD-RB. You then reencoded from the newly created pseudo-disc structure.

1. Do you have "Do not convert DTS to AC3" checked in the SETUP dialog? That will prevent it from being reencoded to AC3.

2. You should also make sure you click "Keep HD Audio for BD25/Alternate intact" -- and set your output size is set to a minimum of BD-25 (as it appears you have). That's because HD audio is generally too big for smaller output sizes. Typically 7.1 sources are HD (as yours is). By default it is unchecked and BD-RB keeps the core audio.

I'm guessing the option in #2 isn't checked and that is the source of your issue.

[kpic]

Jdobbs; thanks for the reply, I did in fact have the 'Keep HD Audio' unchecked in the setup, so it was converting the DTS-HD tracks to DTS just like you thought.

Basically in that other thread another user and I are trying to come up with a streamlined or system\guide to insert audio & subtitle tracks into a UHD title keeping everything else (structure) intact.

Simplified; if TSmuxerGUI is used to create the M2TS you would like (with added sub track\audio etc.) along with a clipinf file then replace the M2TS in the current UHD title with your revised one (of course it doesn't work correctly at this point).

At that point if you take that revised UHD title and send it through your lovely program it will 'fix' the title into a playable UHD title, I then use BDedit for further needed tweaking.

Now for me I have a finished & working 45gb or so UHD title capable of burning to BD-DL and that is fine for me however others may want to keep the UHD size intact and use an ISO for playback - my test UHD title is 57gb in size - so for them; is BDRB able to run through the entire process to 'rebuild & fix' the title but not actually compress?

[jdobbs]

Jdobbs; thanks for the reply, I did in fact have the 'Keep HD Audio' unchecked in the setup, so it was converting the DTS-HD tracks to DTS just like you thought.

Basically in that other thread another user and I are trying to come up with a streamlined or system\guide to insert audio & subtitle tracks into a UHD title keeping everything else (structure) intact.

Simplified; if TSmuxerGUI is used to create the M2TS you would like (with added sub track\audio etc.) along with a clipinf file then replace the M2TS in the current UHD title with your revised one (of course it doesn't work correctly at this point).

At that point if you take that revised UHD title and send it through your lovely program it will 'fix' the title into a playable UHD title, I then use BDedit for further needed tweaking.

Now for me I have a finished & working 45gb or so UHD title capable of burning to BD-DL and that is fine for me however others may want to keep the UHD size intact and use an ISO for playback - my test UHD title is 57gb in size - so for them; is BDRB able to run through the entire process to 'rebuild & fix' the title but not actually compress?Yes. You can either set FORCE_NOENCODE=1 in the INI file, or create a custom output size and make it larger than the input. If there is no need to recompress, the BD-RB will keep it intact.

Just a warning, though. The maximum encode bitrate for a BD-66 or BD-100 is higher than a BD-50. I haven't personally had an issue with it... but it's possible there could be playback issues if the bitrate goes higher than acceptable for BD-50, assuming the source came from a BD-66 or BD-100.

[gamete]

I'd guess, about the same time ... the whole video needs to be reencoded, just with a higher bitrate.

Why don't you just try it?

I was hoping that with less compression it would take less time

[sieve]

I've redone this bd a couple of times and am having the same problem. The video playback of the burned bd has a notably slow fps, as if I'm watching a slow motion playback.

I am running v61.21. I have even tried uninstalling and reinstalling bdrb and all associated programs hoping that would help. It didn't.

Any help is appreciated. Data is below. Thanks!

Here is the log from the last encode:

----------------------
[04/07/21] BD Rebuilder v0.61.21
[22:08:59] Source: ROCKY_HORROR_WW_00800
- Input BD size: 26.60 GB
- Approximate total content: [01:38:40.914]
- Target BD size: 21.97 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[22:08:59] PHASE ONE, Encoding
- [22:08:59] Processing: VID_00260 (1 of 3)
- [22:08:59] Extracting A/V streams [VID_00260]
- [22:09:30] Reencoding video [VID_00260]
- [22:09:30] Keeping original video (no reencode)
- [22:09:30] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:09:30] Processing: VID_00261 (2 of 3)
- [22:09:30] Extracting A/V streams [VID_00261]
- [22:10:03] Reencoding video [VID_00261]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 106,957 frames
- Bitrate: 23,325 Kbs
- [22:10:03] Reencoding: VID_00261, Pass 1 of 2
- [23:19:14] Reencoding: VID_00261, Pass 2 of 2
- [03:23:05] Video Encode complete
- [03:23:05] Processing: VID_00263 (3 of 3)
- [03:23:05] Extracting A/V streams [VID_00263]
- [03:23:11] Reencoding video [VID_00263]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 5,935 frames
- Bitrate: 23,016 Kbs
- [03:23:11] Reencoding: VID_00263, Pass 1 of 2
- [03:25:29] Reencoding: VID_00263, Pass 2 of 2
- [03:40:50] Video Encode complete
[03:40:50]PHASE ONE complete
[03:40:50]PHASE TWO - Rebuild Started
- [03:40:50] Rebuilding BD file Structure
[03:41:40] - Encode and Rebuild complete
[03:41:40] Writing BD structure to ISO file
- ImgBurn completed successfully
- ROCKY_HORROR_WW folder removed.
- WORKFILES folder removed.
[03:42:52] JOB: ROCKY_HORROR_WW finished.


and here is the INF file:

[Status]
LABEL=ROCKY_HORROR_WW
VERSION=v0.61.21
SOURCE_SIZE=28559505408
SOURCE_VIDEO_SIZE=28559505408
TARGET_SIZE=23592960000
REDUCTION=.826098339692928
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=
BACKUP_MODE=1
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
UHD_V3_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=3
REBUILD_COMPLETE=1
[00260]
AUDIO=1000000
PGS=00000000000000000000
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4858045732
USE_ORIGINAL=1
NSIZE=0
FLINK=-1
MLINK=0
[00261]
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=17762342798
RATE=23325
SPLITS=1
AUDIO=1000000
NSIZE=0
FLINK=-1
MLINK=0
[00263]
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=972571470
RATE=23016
SPLITS=1
AUDIO=1000000
NSIZE=0
FLINK=0
MLINK=0

[RetsimLegin]

I'm very new to this and am not sure whether this is a BDRB bug or something else. So I'm doing this as a separate thread. Happy for it to merge into the BDRB bug thread if it transpires that's what I'm seeing. Any help on this will be appreciated:

I have embarked on a project to save storage space by pulling content off a DVD set and putting it onto BD-R DLs. Typically it will be around 7 or 8 DVDs into one BD-R DL. The source DVD is film based (a 1960s TV series) NTSC.

Method used is extract DVD titles using MakeMKV. Build a BD structure and menu using MultiAVCHD. Create disc folders without transcoding. So at this point we have a working BD layout with entirely SD MPEG content that has NOT been re-encoded; just remuxed as necessary. Files are not split; each m2ts stream represents one original title.

The completed output is larger than 50GB so it needs re-encoding to fit a BD-R DL, so I'd use BDRB to re-encode the whole thing down to a smaller size. Doing it in this order means that the whole re-encode (which is the only time-consuming part of it) can be done in a single sweep unattended. Note: I do not rescale the SD content; I leave it at its original definition - NTSC 720x480 - because upscaling will be done in the player in due course anyway and using more pixels would therefore only occupy unnecessary disc space or compromise on compression quality or both.

Up to press I have done several of these successfully on a fairly well-specced machine (i7) with no dedicated graphics chip using the x264 encoder. It encodes at around 80-100 fps and a full disc takes perhaps 6 hours. I just recently got a new machine which has a NVidia GTX1650Ti graphics chip and decided to try the same process, but using the NVENC encoder.

And here is the problem. It got about 75% into the encoding step of the first title (running at ~1500 fps - >15x faster than the i7/x264) and then quit with the message "NVENCC prematurely terminated". Eventually, I did the project on the same new machine using the x264 encoder and that has worked just fine, but 15x more slowly (again ~90 fps).

Since, I have tried the following, all with the same outcome:
- imported that first title alone into BDRB (m2ts from the BD mastered "stream" folder; about 90 minutes duration) and tried to back it up
- imported the raw source .mkv of that title; ditto
- imported a different title (~45 mins) from the same project; ditto
- imported a fresh title (~45 mins) from an entirely different disc set; ditto
- imported a title (~45 mins) using another extraction tool (not MakeMKV) to .mpg; ditto
- tried all encoding options CQM, VBR and "auto" on at least one of the above; ditto.
- tried three of the decoding/frame serve options; ditto

So - simply - any clues?

For reference, here is the BDRB log from a second attempt of the entire project:
----------------------
[04/04/21] BD Rebuilder v0.61.21
[09:00:36] Source: AVCHD_34
- Input BD size: 54.14 GB
- Approximate total content: [21:49:07.947]
- Target BD size: 41.99 GB
- Windows Version: 6.2 [9200]
- Auto Quality: High Quality (Default), VBR
- Decoding/Frame serving: NVENCC
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[09:00:41] PHASE ONE, Encoding
- [09:00:41] Processing: VID_00000 (1 of 35)
- [09:00:41] Extracting A/V streams [VID_00000]
- [09:01:33] Reencoding video [VID_00000]
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 155,453 frames
- Bitrate: 4,333 Kbs
- [09:01:33] Reencoding: VID_00000, Pass 1 of 1
- Error: NVENCC prematurely terminated.
- Encoded: 124372, expected: 155453
[09:03:19] - Failed video encode, aborted
[04/04/21] Checking System Settings
- BD-Rebuilder v0.61.21
- Windows Version: 6.2 [9200]
- Working Path Free Space: 565.31GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- X264: Ok
- X265: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[04/04/21] Systems Settings Check complete

=========================================

PC hardware:
GeForce GTX 1650 Ti (Driver v 461.92) + 4GB GDDR5 VRAM
Intel Iris XE integrated graphics
11th Gen Intel Core i7-1165G7 @ 2.80GHz
64GB RAM
Windows 10 20H2
1TB Samsung 980PRO SSD

=========================================

MEDIA INFO for one of the test source files
General
Unique ID : 190443608565044140394060944873527511407 (0x8F461AD7238A3D69E420A18934E5096F)
Complete name : D:\GFU for NVENCC test make.mkv
Format : Matroska
Format version : Version 2
File size : 1.82 GiB
Duration : 50 min 7 s
Overall bit rate mode : Variable
Overall bit rate : 5 201 kb/s
Encoded date : UTC 2021-04-06 12:15:19
Writing application : MakeMKV v1.16.1 win(x64-release)
Writing library : libmakemkv v1.16.1 (1.3.10/1.5.2) win(x64-release)

Video
ID : 1
ID in the original source medium : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings : CustomMatrix / BVOP
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : M=3, N=12
Codec ID : V_MPEG2
Codec ID/Info : MPEG 1 or 2 Video
Duration : 50 min 7 s
Bit rate mode : Variable
Bit rate : 5 004 kb/s
Maximum bit rate : 9 000 kb/s
Width : 720 pixels
Height : 480 pixels
Display aspect ratio : 4:3
Frame rate mode : Variable
Frame rate : 23.976 FPS
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Scan order : 2:3 Pulldown
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.604
Time code of first frame : 01:14:55:12
Time code source : Group of pictures header
GOP, Open/Closed : Closed
Stream size : 1.75 GiB (96%)
Language : English
Default : No
Forced : No
Color primaries : BT.601 NTSC
Transfer characteristics : BT.601
Matrix coefficients : BT.601
Original source medium : DVD-Video

Audio
ID : 2
ID in the original source medium : 189 (0xBD)128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 50 min 7 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 : 68.8 MiB (4%)
Title : Stereo
Language : English
Service kind : Complete Main
Default : Yes
Forced : No
Original source medium : DVD-Video

Menu
00:00:00.000 : en:Chapter 01
00:06:39.399 : en:Chapter 02
00:07:18.938 : en:Chapter 03
00:19:02.141 : en:Chapter 04
00:25:35.534 : en:Chapter 05
00:35:52.150 : en:Chapter 06
00:49:12.449 : en:Chapter 07
00:49:23.961 : en:Chapter 08

===============================================


Other tests also using a single imported file:
- checking deinterlace caused the encode to fail immediately
- checking IVTC caused the encode to fail immediately
- Convert SD to HD (720p) with no other options checked doubled the frame rate to 59.94. The progress bar showed progress up to 200% and DID complete.

[jdobbs]

After it fails, go to the BD-RB folder and open LASTCMD.TXT. Then open a DOS windows and cut/paste the command from LASTCMD.TXT to the DOS window. Let it attempt the encode, and post the command along wth any error messages here so we can take a look at what is happening.


Just as an aside, why use MultiAVCHD when you can import the MKV files directly with BD-RB?

[jdobbs]

I've redone this bd a couple of times and am having the same problem. The video playback of the burned bd has a notably slow fps, as if I'm watching a slow motion playback.

I am running v61.21. I have even tried uninstalling and reinstalling bdrb and all associated programs hoping that would help. It didn't.

Any help is appreciated. Data is below. Thanks!The only thing I see that is strange is that you are doing a MOVIE-ONLY encode -- but one of the parts is not encoding while the other two are. I don't see an obvious connection to your problem -- but when they are all part of the same movie either all streams or none should be encoded, not a mixture. I'll have to follow the code and see how that could have happened.

[sieve]

Interesting. I hadn't noticed that detail.

I typically do movie-only and with no problems. And I've never had an issue like this one (slow FPS) before. (I have occasionally run into out-of-sync audio, but I think that is a result of the LAV getting corrupted or replaced by another program install. Uninstalling everything and reinstalling with fresh new files fixes that.)

I just looked at the 3 included source files. 260 is the first 20 min or so of the movie. 261 is the middle 75 minutes. 263 is the last 4.

If I play each of these 3 files individually on VLC media player, the video and audio look fine, so the ripped source files are good.

For some reason, the encode/compress function seems to be dramatically slowing the FPS in the final .iso

[jdobbs]

Interesting. I hadn't noticed that detail.

I typically do movie-only and with no problems. And I've never had an issue like this one (slow FPS) before. (I have occasionally run into out-of-sync audio, but I think that is a result of the LAV getting corrupted or replaced by another program install. Uninstalling everything and reinstalling with fresh new files fixes that.)

I just looked at the 3 included source files. 260 is the first 20 min or so of the movie. 261 is the middle 75 minutes. 263 is the last 4.

If I play each of these 3 files individually on VLC media player, the video and audio look fine, so the ripped source files are good.

For some reason, the encode/compress function seems to be dramatically slowing the FPS in the final .isoImmediately after the encode, look at the command line in LASTCMD.TXT. See if a strange frame rate is somehow being used (--fps xx.xx in the command line).

[sieve]

I don't have that file. Maybe because I have settings set to "remove workfiles after rebuild"?
eta it's not in my trash folder either.

[cartman0208]

I don't have that file. Maybe because I have settings set to "remove workfiles after rebuild"?
eta it's not in my trash folder either.

It's located in the BDRB installation folder

[sieve]

I looked there also. Searched the entire HD. I didn't find it.
Here is a screenshot of the install folder...

[thecrowler]

Hi all,
sorry for the newbie question I'm gonna ask.
I would like to remux an UHD M2TS adding a new audio track (PCM) to the existing one.
Could please, anyone, tell me what version of TSMuxer to use (including GUI)?

[LowDead]

Hi all,
sorry for the newbie question I'm gonna ask.
I would like to remux an UHD M2TS adding a new audio track (PCM) to the existing one.
Could please, anyone, tell me what version of TSMuxer to use (including GUI)?

Get over to the TSmuxer thread and get the latest one... It will work for your needs.

//LD

[gonca]

It's located in the BDRB installation folder
Should actually be WORKING folder, if I am correct

[jdobbs]

Should actually be WORKING folder, if I am correctNo. It's the installation folder. But one of the reasons I put this in the instructions...

3. Unzip the BD-RB.zip file. Put it in a directory of its own. I'd recommend putting it somewhere other than "C:\Program Files" until it has been tested more (because of the virtualization that began with Vista).

...is because Windows sometimes virtualizes and puts it elsewhere... I've located it before -- but that was a long time ago and I've forgotten where. Windows tries to keep the program files folders protected.

[sieve]

Fair enough. I haven't had problems in the past with it in Program Files, but I'll give it a shot. I unzipped the files to a different directory (C:bd rebuilder). I started a project and lascmd.txt appeared in the folder.

Thanks, jdobbs!

I'll report back after the encode finishes.

[cartman0208]

I'm trying to troubleshoot the playback of some of my video files, so I'm playing around with the settings and discovered something...

The entry in my alternate.txt states:
[00012]
caption=MP4, IntactVideo, NO_RESIZE, IntactAudio
aType=2
cType=5
vFormat=8


So from my understanding the imported video file should only be demuxed and muxed again, right?
BDRB seems to ignore the aType=2 and remuxes audio-streams to AC3/640kbit
I tried files that already had AC3/640kbit and foles with EAC3/192kbit/5.1 ... all were converted.

Another thing I noticed.
Some files have timed text as subtitles, those are gone after conversion.
Text #1
ID : 3
Format : Timed Text
Muxing mode : sbtl
Codec ID : tx3g
Duration : 47 min 9 s
Bit rate mode : Variable
Bit rate : 70 b/s
Stream size : 24.0 KiB (0%)
Title : English [CC] / English [CC]
Language : English
Forced : No
Encoded date : UTC 2021-04-12 07:26:04
Tagged date : UTC 2021-04-12 07:26:04

I'm pretty sure that is because it's in no way BluRay compatible, but it would be nice to have :rolleyes:

Here's my .INI
[Options]
VERSION=0.61.0.21
ENCODER=1
MODE=3
ENCODE_QUALITY=3
ONEPASS_ENCODING=1
AUTO_QUALITY=0
TARGET_SIZE=47366
NVENC_CAPABLE=1
AUDIO_TO_KEEP=deu;eng;ger;
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=1
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=1
PGSTOSRT=1
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=50000
AUTO_BURN=2
MOVIEONLY_TYPE=12
ALTCRF=18
ALT_TARGET=1024
ALT_CRF_TARGET=1024
ALTMETHOD=0
ALTAUTOCROP=0
[Paths]
SOURCE_PATH=U:\BD-OUTPUT\IMPORTS\
WORKING_PATH=U:\BD-OUTPUT\
SupTitlePath=U:\BD_Rebuilder\Tools\SupTitle\x86\SupTitle.dll

[jdobbs]

Fair enough. I haven't had problems in the past with it in Program Files, but I'll give it a shot. I unzipped the files to a different directory (C:bd rebuilder). I started a project and lascmd.txt appeared in the folder.

Thanks, jdobbs!

I'll report back after the encode finishes.It'll work in the "Program Files" folder. But it in the debugging that you run into issues.