BD Rebuilder Beta - Bug Reports Only

[jdobbs]

Thanks jdobbs. I downloaded the file, but what am I supposed to do with it? I thought about replacing a built-in version that, perhaps, you include with BD-Rebuilder, but the closest file I found was NVEncC.exe, so they are not the same.

I’m sorry I’m not a video expert as you guys; I’m just a “n00b” that wanted to convert that Glitch in the Matrix movie. It was the first time I wanted to do a conversion, the first time I’ve found your tool and the first time I was looking forward to be able to burn a Blu-Ray back. What a luck… first time and it doesn’t work because some flagging / non-compliant attributes that sound like gibberish to me... :scared:

Thanks again for your help.That software is meant only for folks who have an NVIDIA video card that supports encoding. It isn't included as a part of BD Rebuilder (yet). This version was updated to specifically address issues reported by Mark_Venture in this post (https://forum.doom9.org/showthread.php?p=1962477#post1962477).

If you have one of the appropriate video cards, you just put NVENCCRE.EXE into the BD-RB folder. During execution it accesses some of the programs in the TOOLS folder.

[Timmy256]

That software is meant only for folks who have an NVIDIA video card that supports encoding. It isn't included as a part of BD Rebuilder (yet). This version was updated to specifically address issues reported by Mark_Venture in this post (https://forum.doom9.org/showthread.php?p=1962477#post1962477).

If you have one of the appropriate video cards, you just put NVENCCRE.EXE into the BD-RB folder. During execution it accesses some of the programs in the TOOLS folder.

Oh, sorry, I though you were talking about my issue.

Did you get a chance to take a look at my report and MrVideo’s diagnosis (https://forum.doom9.org/showthread.php?p=1962728#post1962728) of what the problem is?

Thanks again.

[Mark_Venture]

I've fixed several issues in NVENCCRE associated with reencoding audio. You can download the updated version at this link (https://jammernhilftnichts.de/jdobbs/NVENCCRE.zip).

I've re-tried those two movies using this version and it works! Thank you!!

I know see --audio-copy 1 --audio-copy 2 --audio-copy 3 for each audio stream, matching what is in the source, in the lastcmd.txt file.

I appreciate the quick fix!!

[MrVideo]

It is my understanding that if a font is not found, BDRB will fall back to a default font. I did a project where the font was not found and the menu screen had no text. The menu still worked, even though I couldn't see anything.

[MrVideo]

Currently the menu in 1080p. Any thought to changing the menu to 2160p?

The reason is projector switching (might affect TVs/monitors as well). When going from 1080p, which the projector upconverts, to 2160p, it has to change modes to handle the native resolution. That results in a black display until the mode change completes.

Not a must, but a nice-to-have.

[jdobbs]

Currently the menu in 1080p. Any thought to changing the menu to 2160p?

The reason is projector switching (might affect TVs/monitors as well). When going from 1080p, which the projector upconverts, to 2160p, it has to change modes to handle the native resolution. That results in a black display until the mode change completes.

Not a must, but a nice-to-have.Not sure how much work that would be as I haven't looked at it. I'm mainly worried about adjustments for screen placement etc -- but I'll check it out and see.

[Timmy256]

Hi jdobbs,

Do you have any comments on what (if) I can try anything to try to make me previous reported conversion working successfully?

Thanks?

[jdobbs]

Hi jdobbs,

Do you have any comments on what (if) I can try anything to try to make me previous reported conversion working successfully?

Thanks?Sorry, but no. BD-RB relies on the MPLS and CLPI to be correct. So when it sees 59.94 as the framerate, it assumes that to be correct. My guess is that either NVENCC (if you are using it) or AVISYNTH (if you are using x264) are misinterpreting the framerate during reencode due to the frame doubling.

BTW. You asked why, when you change one stream, others change. That means they are linked and playback as a part of a single playlist. So if one changes (for example removing an audio stream) they all have to change. The * next to the stream in the streams list indicates it is a component of a multipart playlist.

This issue probably requires that I get my hands on the original to do any serious testing.

[Timmy256]

Sorry, but no. BD-RB relies on the MPLS and CLPI to be correct. So when it sees 59.94 as the framerate, it assumes that to be correct. My guess is that either NVENCC (if you are using it) or AVISYNTH (if you are using x264) are misinterpreting the framerate during reencode due to the frame doubling.

BTW. You asked why, when you change one stream, others change. That means they are linked and playback as a part of a single playlist. So if one changes (for example removing an audio stream) they all have to change. The * next to the stream in the streams list indicates it is a component of a multipart playlist.

This issue probably requires that I get my hands on the original to do any serious testing.

Thanks for your reply jdobbs.

If you want, I can upload the offending file (extra - 00010.m2ts) and share it with you through a link. It’s around 2 GB.

Would that be OK for you to be able to troubleshoot what’s going on? As I said before it puzzles me that Media Player Classic plays it wrong, VLC plays it correctly and other conversion tools, like DVDFab, are able to convert it correctly.

Thanks.

[Link removed]

[jdobbs]

Thanks for your reply jdobbs.

If you want, I can upload the offending file (extra - 00010.m2ts) and share it with you through a link. It’s around 2 GB.

Would that be OK for you to be able to troubleshoot what’s going on? As I said before it puzzles me that Media Player Classic plays it wrong, VLC plays it correctly and other conversion tools, like DVDFab, are able to convert it correctly.

Thanks.

[Link deleted]I believe the link you posted may be copyrighted material, so I've deleted the reference. Please review Rule 6. I'm taking into consideration that you are new to the forum, so I am not issuing a strike. But please review the rules so this forum isn't made in any way liable or questionable.

[MrVideo]

NVENCCRE

I set the bitrates to 5000, 10000 and 15000, selecting 10000. When my first file was done, it was really large. So I checked it with MediaInfo and it had a bitrate of 40.8 Mb/s. I'm curious as to why the big difference between the selected bitrate and the final result.

UPDATE: Now I'm really confused. I changed the list to 2500, 5000 & 10000 and selected 5000. The program even indicates that it will be using VBR 5000 and yet the result is still 40.8 Mb/s.

Any thoughts?

[jdobbs]

NVENCCRE

I set the bitrates to 5000, 10000 and 15000, selecting 10000. When my first file was done, it was really large. So I checked it with MediaInfo and it had a bitrate of 40.8 Mb/s. I'm curious as to why the big difference between the selected bitrate and the final result.

UPDATE: Now I'm really confused. I changed the list to 2500, 5000 & 10000 and selected 5000. The program even indicates that it will be using VBR 5000 and yet the result is still 40.8 Mb/s.

Any thoughts?Interesting. Apparently no one else uses bitrate. There was a bug in which a wrong value was used on the command line. I can't believe I missed it.

[jdobbs]

I fixed the bug in NVENCCRE that ignored the specified bitrate. You can download the new version at this link (https://jammernhilftnichts.de/jdobbs/NVENCCRE.zip).

[Timmy256]

I believe the link you posted may be copyrighted material, so I've deleted the reference. Please review Rule 6. I'm taking into consideration that you are new to the forum, so I am not issuing a strike. But please review the rules so this forum isn't made in any way liable or questionable.

Oh, sorry jdobbs. Since it was mentioned before that the YouTube sample I’ve created wasn’t useful and that the original was needed, I took the liberty to do so.

Is there any way I can provide you with that material safely, for testing purposes, so you might have a better understanding on why BD-Rebuilder is returning a wrong conversion for it and how it could be fixed?

Thanks

[MrVideo]

Interesting. Apparently no one else uses bitrate. There was a bug in which a wrong value was used on the command line. I can't believe I missed it.
Leave it to me to find it. I do prefer using bitrate values for encoding.

[MrVideo]

When importing a directory that contains multiple BD folders, BDRB creates a titles.inf file that is really great for when you rerun the job. Except that it tends to get it wrong.

Long story short, I had a title.inf file that had a blank space. because I unchecked a title. I had then added a new BD folder. I manually edited the titles.inf file and added the new file name, in the correct alphabetical position and corrected all of the lines in the file. When I started BDRB and read in the directory, It changed the title of #8 to what #7 is so that it was like this in the dialog box: 08. title [length]. The original list has the generated BDRB numbers removed, as well as the length values. It also added a title #13, even though there are only 12 titles. #13 is a duplicate of the #12 title, with the BDRB number and length added.

I then started and aborted the job so that I coould check the titles.inf file. Yep, the wrong entries are now in the file. I corrected the file, restarted BDRB and again it screwed up the list.

To try and get this right, I closed BDRB and deleted the titles.inf file. I started again and again the dialog was wrong. Title #7 was the way I want it, i.e., no BDRB number and no length. But, it duplicated title #7's title and added the BDRB goodies and gave it entry #8. Yep again the list now contains 13 titles when there really is only 12.

Just what is BDRB doing? Is there a secret stash that BDRB is using regarding the imported titles.

[jdobbs]

When importing a directory that contains multiple BD folders, BDRB creates a titles.inf file that is really great for when you rerun the job. Except that it tends to get it wrong.

Long story short, I had a title.inf file that had a blank space. because I unchecked a title. I had then added a new BD folder. I manually edited the titles.inf file and added the new file name, in the correct alphabetical position and corrected all of the lines in the file. When I started BDRB and read in the directory, It changed the title of #8 to what #7 is so that it was like this in the dialog box: 08. title [length]. The original list has the generated BDRB numbers removed, as well as the length values. It also added a title #13, even though there are only 12 titles. #13 is a duplicate of the #12 title, with the BDRB number and length added.

I then started and aborted the job so that I coould check the titles.inf file. Yep, the wrong entries are now in the file. I corrected the file, restarted BDRB and again it screwed up the list.

To try and get this right, I closed BDRB and deleted the titles.inf file. I started again and again the dialog was wrong. Title #7 was the way I want it, i.e., no BDRB number and no length. But, it duplicated title #7's title and added the BDRB goodies and gave it entry #8. Yep again the list now contains 13 titles when there really is only 12.

Just what is BDRB doing? Is there a secret stash that BDRB is using regarding the imported titles.The TITLES.INF file was never intended to be edited by the user. It is just a way for BD-RB to keep that information between runs. That file also contains information as to changes in position and inclusion/removal information (that are made from the dialog in BD-RB).

I've never seen it "get it wrong". If it is... it is likely because you've edited it without understanding it.

[MrVideo]

The TITLES.INF file was never intended to be edited by the user. It is just a way for BD-RB to keep that information between runs. That file also contains information as to changes in position and inclusion/removal information (that are made from the dialog in BD-RB).

I've never seen it "get it wrong". If it is... it is likely because you've edited it without understanding it.
Continuing this via PM.

[Lowpro]

The TITLES.INF file was never intended to be edited by the user. It is just a way for BD-RB to keep that information between runs. That file also contains information as to changes in position and inclusion/removal information (that are made from the dialog in BD-RB).

I've never seen it "get it wrong". If it is... it is likely because you've edited it without understanding it.I concur. I've never seen it "get it wrong" either. Well, unless the problem exists between the keyboard and chair anyway. I've seen that a few times. :p

[MrVideo]

I concur. I've never seen it "get it wrong" either. Well, unless the problem exists between the keyboard and chair anyway. I've seen that a few times. :p
Normally BDRB gets it right. But I've run into a situation where it doesn't. Data sent to jdobbs that showed what happened.

[MrVideo]

I've never seen it "get it wrong" either.
Well, here is proof.
A directory contains five directories, Titles-01 thru Titles-05. Starting BDRB and importing the directory results in BDRB-01 (http://vidiot.com/images/BDRB-01.jpg).
The titles.inf is:

[Titles]
Title=BDRB
Threshold=0
00001=01. Title-01 [00:48:31]
00002=02. Title-02 [01:00:02]
00003=03. Title-03 [01:01:58]
00004=04. Title-04 [00:54:01]
00005=05. Title-05 [00:55:30]
[Position]
00001=1
00002=2
00003=3
00004=4
00005=5
[Selected]
00001=-1
00002=-1
00003=-1
00004=-1
00005=-1
Looks good.
Now I add another directory, Title-06, and restart BDRB and import again. And the oops result is BDRB-02 (http://vidiot.com/images/BDRB-02.jpg). The original directory name of Titles-06 is the mistake name in the list.
[Titles]
Title=BDRB
Threshold=0
00001=01. Title-01 [00:48:31]
00002=02. Title-02 [01:00:02]
00003=03. Title-03 [01:01:58]
00004=04. Title-04 [00:54:01]
00005=05. Title-05 [00:55:30]
00006=I Am Mortal
00007=07. Title-06 [01:23:13]
[Position]
00001=1
00002=2
00003=3
00004=4
00005=5
00006=6
00007=7
[Selected]
00001=-1
00002=-1
00003=-1
00004=-1
00005=-1
00006=-1
00007=-1
As can be seen, I'm not making this up. BDRB does not like that title.

[Mike-uk]

Mrvideo use a image host as images uploaded to here require admin approval and as you can see it might take a while for it to be aproved but an image host we can see your images instantly :)

[Emulgator]

Just report such post as "Please approve attachments" to give moderators notice and it will be done.
I just did that for #31170.
Why ? External hosts die, or cancel their services and thread content will be lost.

[MrVideo]

In this case it is my own server. That said, when I die, my server will go away.

[MrVideo]

Working on a UHD resizing from 36GB and BDRB is not getting it. There are two large files (one HDR and one SDR). The first run thru had each of the files about 11GB each (they are equal in size). The overall job was 2.4GB too large for the BD25. So, I set the TARGET_SIZE to 21000, but the encoded file size was still 11GB.

So, I looked at the output settings and Custom was checked, but the value shown was 23500, when I wanted 21000.

What do I need to do to get BDRB to use the 21000 target size?

[Emulgator]

If you checked "Custom Target Size", Configuration Editor
CUSTOM_TARGET_SIZE=21000
should work.

[MrVideo]

If you checked "Custom Target Size", Configuration Editor
CUSTOM_TARGET_SIZE=21000
should work.
Thanks for the pointer. I didn't know that option existed. When editing the configuration file, I ran into TARGET_SIZE first and changed it. The CUSTOM_TARGET_SIZE is later in the file.

[Timmy256]

Hi jdobbs,

Sorry to insist with my report for the past few months, but are you interested in working on that issue at all? If not, that’s OK, but would you please let me know, so I can go on purchase DVDFab and stop posting and investing time troubleshooting BD-Rebuilder?

Thanks.

[ggtop]

... and stop posting and investing time troubleshooting BD-Rebuilder?

Hi Timmy256,

there is simply nothing to troubleshoot as you have proven you use BDRB on a pre processed and obviously illegal source. Buy the original! You will see BDRB will work as expected then :-)

ggtop

[ggtop]

Hi jdobbs,

I encountered something unusual using Alternate Output (mp4).
The audio settings in the profile I use is set to AC-3@640. The source bitrate is AC-3@448 and BDRB upconverts to 640. "Normally" it lowers the bitrate to the source bitrate as a maximum what I would expect. This only happens on multi-part sources e.g. Fast & Furious 9.

Have a nice weekend,
ggtop

[Timmy256]

Hi everyone,

Sorry to have bothered you with my posts, it wasn’t my intention. I’m no video engineer as you guys; just an “end user” who found out jdobbs’ tool and used it only one time and didn’t work as expected; hence my posting here trying to find out whats going on.

As I said, I’m not a video engineer (I’m a software engineer, though); I don’t understand (nor do I have a personal or professional interest) in all the video advanced terms, technicalities and codecs understanding. I just wanted to shrink one Blu-Ray to be able to back it up in a smaller disc as a “n00b”.

From my experience here, you have years of knowdledge and learnings, but that didn't translate (nor the community didn't seem) to be very open or friendly to newcomers or people interested in just using the tool and get on with their life. But that’s OK, you are free to foster whatever community you like! :)

Thanks again for the original tool and, hopefully, some expert; community-approved user will stumble into the same issue some time in the future years and benefit the whole community while troubleshooting.

[ggtop]

Hi jdobbs,

out of interest. Would it be possible for you to make parameter "threshold" for Avisynth function "Autocrop ()" available through hidden opts? I sometimes encounter too much cropping with default value. Changing AVS and re-running Last command isn't very handy...

http://avisynth.nl/index.php/AutoCrop

Thank you,
ggtop

[MrVideo]

Is there a hidden option whereby the numbers and length text that is added by BDRB can be disabled? What I want displayed in the menu is only the folder name.

Thanks

[gonca]

It would also be great if we could have an option for longer movie names

[MrVideo]

It would also be great if we could have an option for longer movie names
I second that. But, this would apply to importing of single files as well. Many a time TV show episode titles won't fit in the allocated space. When the menu only contains one column, there is lots of space for lengthy titles.

[thecrowler]

Hi all,
is it possible to manually update NVEnc in the "BDRB\Tools" folder to the latest release on Github (rigaya/NVEnc)?
Regards.

[MrVideo]

You can do so, but keep in mind that jdobbs tests any and all new releases to make sure that it doesn't break anything. Therefore, if you do, you can't complain when something goes wrong and it is related to the encoder.

For example, I've installed the 1/24/22 version of tsmuxer, as I need its ability to work with DD+ audio. TsMuxer has changed a bunch of naming schemes, which jdobbs has discovered. That means he can't use the new tsMuxer until he has sorted out all of the changes. I've run across one of the naming schemes and I have to deal with it manually when I use BDRB for a certain operation.

In other words, do so at your own risk.

[MrVideo]

I've learned some more about the use of titles.inf. Say you have a directory with 10 titles. Not all of them will fit on a BD. So you uncheck the ones that you'll watch later. In the meantime, there are some more titles that you will want to add. After watching some of the titles on the BD, you go back to the directory and removed the viewed titles. You then add the new titles and restart BDRB and import that directory. The list of titles is totally fubar.

There are only two ways to fix it. 1) you remove the titles.inf and start over 2) you manually edit the titles.inf file. With #1 you have to remove the numbers and length text, again (hence the above request). With the #2 option, you won't have the issue with the number and length text.

But, you still have to do something, because BDRB loses its marbles when a titles.inf file is used again and the content of the directory has changed.

[gonca]

I've learned some more about the use of titles.inf. Say you have a directory with 10 titles. Not all of them will fit on a BD. So you uncheck the ones that you'll watch later. In the meantime, there are some more titles that you will want to add. After watching some of the titles on the BD, you go back to the directory and removed the viewed titles. You then add the new titles and restart BDRB and import that directory. The list of titles is totally fubar.

There are only two ways to fix it. 1) you remove the titles.inf and start over 2) you manually edit the titles.inf file. With #1 you have to remove the numbers and length text, again (hence the above request). With the #2 option, you won't have the issue with the number and length text.

But, you still have to do something, because BDRB loses its marbles when a titles.inf file is used again and the content of the directory has changed.
Try editing the inf file in BD_RB directly, it works.
I do it quite often.

[MrVideo]

Try editing the inf file in BD_RB directly, it works.
I do it quite often.
And how is one supposed to do that when the list of titles shown within BDRB is totally incorrect? For example, I removed from the directory the titles I had watched. When BDRB displayed the list, two of the titles that I removed are still there. Two of the titles that are in the directory are not in the list.

Only when I manually edit the titles.inf file is the list now correct.

There's more:

I then added a new title and ended up with:
Title-1
Title-2
Title-3
04. Title-3 [0:44:00]
The title that I added, alphabetically it is equal to "Title-0."

Based upon my experience, BDRB was not designed to re-import a directory with changes. The content needs to be the same, or you have to manually edit the titles.inf file.

Update: I just edited the titles.inf file to add the new title. I placed it in the 4th position and when I restarted BDRB, I ended up with the same title list as shown above. When I edited the titles.inf file to place the new title alphabetically in the correct position and restarted BDRB, the new title showed up, but had "01. " in front of the title and the "[length]" at the end of the title, even though the title.inf file has no such text in it.

That tells me that BDRB has a hidden file of some sort so that it knows that the newly added title was not there before. That would explain the issue I had with a title that kept returning, as noted in previous posts.

[gonca]

You have the original output (created structure from import)
Load this into BD_RB
Edit the menu
Save and continue

EXAMPLE
DISC>disc 1, disc 2, etc [folder structure]
import
Edit menu etc
output>NEW DISC

Next time
NEW DISC
Add DISC > (BD/NEW DISC + DISC) structure
import
Edit menu etc
output>NEW DISC 2

Do not touch the inf file directly
Just uncheck the movies you don't want and add the ones you do

[MrVideo]

Please re-red what I posted. I think you have totally missed what I'm doing. What you are suggesting would be great if the directory had ALL of the titles I would be dealing with. Because the content of the directory would not be changing.

The issue is when the content of the directory changes. After viewing some of the content on the disc. I remove that content from the directory. At that point the titles.inf file no longer matches what is in the directory. When I remove content, most of the time I add new content to the directory. That makes the directory more out-of-step with the titles.inf file. BDRB can't seem to deal with directory content changes.

[gonca]

Please re-red what I posted. I think you have totally missed what I'm doing. What you are suggesting would be great if the directory had ALL of the titles I would be dealing with. Because the content of the directory would not be changing.

The issue is when the content of the directory changes. After viewing some of the content on the disc. I remove that content from the directory. At that point the titles.inf file no longer matches what is in the directory. When I remove content, most of the time I add new content to the directory. That makes the directory more out-of-step with the titles.inf file. BDRB can't seem to deal with directory content changes.
Re-read post
It has been edited

[MrVideo]

As pointed out in my post, that doesn't work. It might if you start with a single disc and then add a single disc, for a total of two. When working with multiple titles, it tends to fail, as pointed out in post 31189.

[gonca]

I start with multiple discs and a create a disc structure with menu
Later on I add a new disc to that collection, or replace a disc with an upgraded version of one of the movies, or both.
IT WORKS, I do it on a regular basis
But you just don't want to get it, fine, there is no issue with the menu creation so good luck!

[MrVideo]

IT WORKS, I do it on a regular basis
As I've pointed out, with plenty of examples, for me it does not work.

[cartman0208]

Hi all,
is it possible to manually update NVEnc in the "BDRB\Tools" folder to the latest release on Github (rigaya/NVEnc)?
Regards.

Possible but not recommended.
As pointed out in the very first post BDRB works best with the shipped or linked versions.

[MrVideo]

I've run into an issue with backing up a UHD disc. This has happened before, so it didn't come as a surprise. That said, this is more informational than anything else.

I'm on my third try to try and get it to fit on a BD25. The original M2TS file is about 60GB. 8.1GB of which is the TrueHD and AC3 audio streams. Using the default settings, the re-encoded video was about 30GB. Certainly missed the mark. Then tried 21000 as a custom setting. Still missed. I then tried 19000. Still larger than the target by about 3GB. I'm now trying 18000.

But what I've noticed in the config file is that when a job is started, the target size is equal to the previous setting. For a custom size of 19000, the target was 21000. For the current custom setting of 18000, the target is 19000. I have no idea why the current target setting is set to the previous custom setting.

UPDATE: I have to yet another attempt. It would probably have been easier if I could have selected a bitrate instead of a target size. The original file is a 29.7 Mbps. I figure that using 15 Mbps would have fit. The last run BDRB set the bitrate to 16 Mbps. Frankly, I'm not sure that 15 Mbps will cut it. I noticed that the target rate stayed at 19000, even though I've now set 17000. Nope, cancelled the 17000, as the bitrate is a fraction about 15 Mbps, which I don't think it is going to make it. So, I'm trying 16000, yielding a bitrate just over 14 Mbps. If this doesn't do it, I'm heading to bed, as I've already spent over 4 hours on this single project.

UPDATE #2: It took a target size of 15000. That is about 64% of the default 23500. That is a big math error.

[cartman0208]

Strange ... the target size in my inf file matches the set target exactly ...
Are you doing Full disk backup? Movie Only?
I also had the targed size missed on rare occasions, but that was only about one or two GB ...

[MrVideo]

Strange
Are you doing Full disk backup?
Yep, strange and yep. It does indeed normally hit without issues.