BD Rebuilder Beta - Bug Reports Only

[rendez2k]

Sorry, I think I may have asked this before but can't remember the outcome. I load a BR, blank some audio and video. Is there anyway to tell if my blanking has enabled the remaining content to fit on a BD-25 without compression?

[cinephage]

Silly question but I changed my system to windows7 64 bits and re-installed bd-rebuilder from scratch. After at least 3 years of perfect use.
I can't start it getting this message: "MSCOMCTL.OCX or one of its dependecies not correctly registered a file is missing or invalid"

[xterminater]

jdobbs, I know this question have probably popped up before but I couldn't seem to find an answer. Is there a way we can "make" BD-RB allocate space better, like try to fit as much as the bd-disc can hold? I noticed that whenever I back up a BD-50 to BD-25, it's always around 21-22gb, instead of the maximum 25, which I know isn't really 25gb, but at least closer than that. Is there a hidden setting that I must enter? Also I do not allow hd audio, just dts core for audio.

[Capsbackup]

jdobbs, I know this question have probably popped up before but I couldn't seem to find an answer. Is there a way we can "make" BD-RB allocate space better, like try to fit as much as the bd-disc can hold? I noticed that whenever I back up a BD-50 to BD-25, it's always around 21-22gb, instead of the maximum 25, which I know isn't really 25gb, but at least closer than that. Is there a hidden setting that I must enter? Also I do not allow hd audio, just dts core for audio.

If you select 2 pass encoding, this is the most accurate method. Every disc will be different though, taking into account action scenes, darker movies, many audio tracks, etc... so it is "safer" to stay below the maximum BD-R capacity of about 23.5GB (25,000,000,000 bytes) .
You can try different "CUSTOM_TARGET_SIZE=xxxxxx" settings to try and reach your desired output. :cool:
The visual gain will probably be miniscule at best, but you can fill up that disc to the max if it makes you "feel" better! :o

[RobertM]

Is there a way we can "make" BD-RB allocate space better

The problem is that the actual size after re-encoding cannot be known until the re-encode is complete. Any attempt to calculate the final size before-hand is just an estimate, so you have to leave a little extra headroom or lots of rebuilds would end up being too large to fit on a BD-25. My BD-25 rebuilds end up filling 96% to 97% of the disc, using the default BD-25 target size. I feel that this is close enough to not worry about it.

But you can modify this yourself. Just don't use the standard BD-25 target size; use a custom size instead. I believe that the standard size is 23.5 GB, so you could try 24 GB and see what happens. In my case, I have not seen anything over 97%, so if I used a custom size of 24GB then I might expect a final result around 97% x 24/23.5, or 99.06%. Hmm.... maybe I'll actually give this a try and see what happens.

The only real downside of doing this is that you increase the chances of getting the occasional rebuild that is too big, and you'll have to repeat the rebuild with a smaller target size. Not a big problem, as long as you remember why the oversize is happening.

Caps beat me to the response

[jdobbs]

Silly question but I changed my system to windows7 64 bits and re-installed bd-rebuilder from scratch. After at least 3 years of perfect use.
I can't start it getting this message: "MSCOMCTL.OCX or one of its dependecies not correctly registered a file is missing or invalid"Right click on REG_MSCOMCTL.BAT in the BD-RB folder and say "Run as Administrator".

[omegaman7]

By using 2 - 5% more of a BD disc, you will not see a difference in video quality. And you risk errors on the outer edge of the disc. Plus they take longer to burn. There's no factor which would make me elect to use the full 23.2Gb of Disc space. That's asking for trouble. I prefer go with 22.0 - 22.5Gb. However if I remove audio tracks, and no encoding is required, and I end up around 22.7 - 23.0Gb, that is acceptable. My LG drive seems to have trouble closing LTH discs around the outer edge. Jdobbs hit the estimation algorithm right on the money! :D

[AmigaFuture]

@omegaman7 Some of us ~do~ see a difference with video quality. Typing that "you will not see a difference in video quality" is subjective to personal vision and experience. Some people have to be "shown" the difference. I'm able to walk into a Walmart or some other store and ~KNOW~ the difference between Video or HDMI output. Many "customers" have no idea of what I'm talking about, but there are those that ~get it~ to some degree and express real ~appreciation~. Only relating to visual and not actual media data as you are. ~Smile~ Hehe!

[omegaman7]

Well... to each his own. :p

[Cela]

@jdobbs,
feedback about impact of the new versions, AnyDVD HD 7.0.3.0 and BD-RBV04009:
The new combination still produces the erroneous, false negative 'SourceCheck() 00006 2501', 'Selected source is not BD format' error messages and still prohibits BD-RBV04009 normal processing of my two problem disks.

Regards

[jdobbs]

@omegaman7 Some of us ~do~ see a difference with video quality. Typing that "you will not see a difference in video quality" is subjective to personal vision and experience. Some people have to be "shown" the difference. I'm able to walk into a Walmart or some other store and ~KNOW~ the difference between Video or HDMI output. Many "customers" have no idea of what I'm talking about, but there are those that ~get it~ to some degree and express real ~appreciation~. Only relating to visual and not actual media data as you are. ~Smile~ Hehe! I have a really, really hard time believing that anyone could identify a difference of 2% on a BD-25. I'm not saying its impossible -- but if I were a betting man I'd be willing to bet the farm that it couldn't be identified in a double-blind test...

[jdobbs]

@jdobbs,
feedback about impact of the new versions, AnyDVD HD 7.0.3.0 and BD-RBV04009:
The new combination still produces the erroneous, false negative 'SourceCheck() 00006 2501', 'Selected source is not BD format' error messages and still prohibits BD-RBV04009 normal processing of my two problem disks.

Regards The confusing thing is that I'm not getting any other reports (beyond one or two folks). That routine gets executed on every single disc processed.

[Yordan5]

I have a really, really hard time believing that anyone could identify a difference of 2% on a BD-25. I'm not saying its impossible -- but if I were a betting man I'd be willing to bet the farm that it couldn't be identified in a double-blind test...

Same here. Using BD-RB I shrank the StarWars trilogy (episodes 4, 5 and 6). Each episode was around 35Gb and with BD-RB I shrank them to 13Gb each. No matter how hard I tried to find any degradation in quality I was not able to. I did that on a PC with a 32" Sony monitor and on a 42" Panasonic LED TV. If someone claims they are able to tell the difference due to an extra 2% storage on a 25Gb disk, that is pure fantasy.

[omegaman7]

Perhaps they have eagle eyes?

I may have an idea why some people think they see a difference. I noticed with compressed sources, Hardware enabled playback(E.g. GPU used for playback) can cause an oversimplified colorspace playback. Which can cause a certain level of artifacting in white and dark scenery. When the CPU is used instead, the video is being played exactly as the frame is intended.

[wakko709]

[04/21/12] BD Rebuilder v0.40.09 (beta)
[16:23:53] Source: ZOMBIELAND
- Input BD size: 36.26 GB
- Approximate total content: [03:05:29.975]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7600]
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[16:23:56] PHASE ONE, Encoding
- [16:23:56] Processing: VID_00011 (1 of 41)
- [16:23:56] Extracting A/V streams [VID_00011]
- [16:33:57] Reencoding video [VID_00011]
- [16:33:57] Reencoding secondary video [TRK_02]
- Encode failed. Aborting.
- BD-Rebuilder v0.40.09 (beta)
- Windows Version: 6.1 [7600]
- AVISYNTH Version: 2.5.7.0, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 3882, Ok
- WIN7 preferred AVC CODEC: Not Set correctly
- WIN7 preferred VC-1 CODEC: Not Set correctly
- WIN7 preferred MPEG2 CODEC: Not Set correctly
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- AnyDVD settings check: Ok.
- X264: Ok
what the hell is win7 codec?

[RobertM]

If someone claims they are able to tell the difference due to an extra 2% storage on a 25Gb disk, that is pure fantasy.

You are probably right. But are you also willing to state, equally forcefully, that the 2% larger file is, in fact, no better. If so, then you would be wrong. The difference may be subtle, even imperceptible to lots of people, but it does contain more information, and it is -- technically -- better, whether you, or anyone else, can see it or not. You may feel that this is an "angels on the head of a pin" type of argument, but why should people leave empty space on a BD disc when it could be put to some use. And basing your argument on a 42" display is only valid if you are sitting within 5 feet or so.

[setarip_old]

@Yordan5

Hi! I shrank the StarWars trilogy (episodes 4, 5 and 6). Each episode was around 35Gb and with BD-RB I shrank them to 13Gb each. No matter how hard I tried to find any degradation in quality I was not able to.

I'd suggest that your choice of Blu-ray disc for testing, one with loads of CGI - and shot with digital cameras, is a major contributing factor for the remarkably good high compression results.

When "King Kong" first became available on HD-DVD, the members here (myself included) were equally impressed with the quality of highly compressed versions of it.

See if you get the same remarkably good results when compressing a more "standard", live action only shot on film Blu-ray...

[Yordan5]

You're both (RobertM, setarip_old) technically correct. The argument was that in practical use those 2% extra data on a 25Gb disk would make absolutely no difference to your viewing experience when compressing a movie, on top of the fact that you'd be asking for trouble writing so close to the outer edge of the disk. I only gave the example of the StarWars trilogy to make the point that if I cannot see a difference when there's been more than 40% compression what's the point of running the risk of a coaster for an academic gain. We all know that BD-RB produces results that a nothing short of spectacular and it would take a lot more than 2% (that's half a Gig on 25Gb disk) for most people to actually see a visual difference. Technically we know that there would be a difference but we wouldn't be able to see it. I'd much rather just enjoy the movie instead of trying to ruin the experience looking for miniscule artifacts the whole time.

[lone-warrior]

"Three Colors: Blue" BD from Netflix. Movie only convert to DVD5. Video OK but no audible audio. Log follows:
----------------------
[04/21/12] BD Rebuilder v0.40.09 (beta)
[09:51:35] Source: THREE_COLORS_BLUE
- Input BD size: 26.78 GB
- Approximate total content: [01:38:20.936]
- Target BD size: 4.36 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Auto Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[09:51:35] PHASE ONE, Encoding
- [09:51:35] Processing: VID_00274 (1 of 1)
- [09:51:35] Extracting A/V streams [VID_00274]
- [10:09:56] Reencoding video [VID_00274]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 141,481 frames
- Bitrate: 5,639 Kbs
- [10:09:56] Reencoding: VID_00274, Pass 1 of 2
- [10:56:22] Reencoding: VID_00274, Pass 2 of 2
- [12:25:13] Video Encode complete
- [12:25:14] Processing audio tracks
- Track 4352 (fra): Reencoding audio to AC3...
[12:26:15]PHASE ONE complete
[12:26:15]PHASE TWO - Rebuild Started
- [12:26:15] Rebuilding AVCHD file Structure
[14:28:28] - Encode and Rebuild complete
[14:28:28] JOB: THREE_COLORS_BLUE finished.
Note: On the the last two lines it was waiting a couple of hours for my reply to override the output folder!
-----------------------------
Workfiles:http://webpages.charter.net/carlospg/Blue-Workfiles.jpg
00274.track_4352.dts has audio OK. However, no audible audio on AUD_00274_4352.mkv, AUD_00274_4352.AC3
-----------------------------
AUD_00274_4352.AVS:
#Created by BD Rebuilder - v0.40.09 (beta)
LoadPlugin("M:\BD_Rebuilder-0.40.09\BD_Rebuilder\tools\nicaudio.dll")
audio=DirectShowSource("M:\1-BDR-BLUE\WORKFILES\AUD_00274_4352.mkv").Amplify(1)
ConvertAudioTo16bit(ResampleAudio(audio, 48000))
-----------------------------
Also, despite selecting 448Kbps audio, output shows 192Kbps
Thanks in advance

[DMagic1]

Sorry I'm a little behind on the progress of BDRebulder. Before I post any bugs I like to know if it is now able to process 3D titles that I'm stripping some extras and audio but not reencoding?


Thanks

[drmih]

Sorry I'm a little behind on the progress of BDRebulder. Before I post any bugs I like to know if it is now able to process 3D titles that I'm stripping some extras and audio but not reencoding?


Thanks

No, as soon as you adjust the streams you'd need to be able to cross reference the 3D data.

[Sky7777]

That is a disc read/write access error... it's possible something (like a path) might be corrupt in the INI file. Try renaming BDREBUILDER.INI to another name temporarily and see if the error goes away.

An error does not go away:(

[AmigaFuture]

I have a really, really hard time believing that anyone could identify a difference of 2% on a BD-25. I'm not saying its impossible -- but if I were a betting man I'd be willing to bet the farm that it couldn't be identified in a double-blind test...

Some blind people hear nuances in sounds and feel vibrations that (most) people who trust their eyes and logical (mosty)...don't hear/feel. Some of these people will teach those of us whom do use our eyes well, but desire to expand that sense, too. I can see the difference between BD-25 and originals, but it's definitely a practiced/focusing thing. I'm also into "audiophile". Transcoding makes it ~much~ easier to see/hear the differences. Rerendering does not. :D

Anyway...I was trying to have some fun with the message but you 2 may not have read it that way.

[Cela]

The confusing thing is that I'm not getting any other reports (beyond one or two folks). That routine gets executed on every single disc processed.Too bad! Then I'll never know the true reasons why my BD was rejected by BDRB and classified as 'non-BD', i.e. which of the numerous checks in that routine (executed on every single disc processed) it did not pass. :confused:

Thanks!

[RobertM]

I've made this request before. It isn't really a "bug", in that we know precisely why this behaviour is happening, but it sure feels like a bug when it happens.

This morning I woke to find that an overnight rebuild had rebuilt the wrong playlist. Before starting a rebuild I always check the "output options" screen to make sure I had selected the right target size. Sometimes I forget that if I make a change between BD-25 and BD-9 that my previous playlist selection (and any specific selections I have made on the "stream" tab) will be thrown out and replaced with a default playlist selection. The "rescanning" message was displayed, of course, but it happens every time we make a change, so it is not a good indicator that something has actually changed.

I can't see why it would be particularly difficult to remember the playlist selection for the rescan. If it cannot be, for whatever reason, then a message dialogue should draw attention to the fact that the playlist has changed. It feels REALLY odd to have the app override a manual selection without some kind of warning. Like I said, when this problem happens -- and it has happened to me many times -- it feels like a bug.

[varekai]

Most likely not a bug in BD-RB but something makes x264 crash.
"H.264 (MPEG-4 AVC) encoder has stopped working..." and BD-RB stops with message "- Failed video encode, aborted".
I've been able to reproduce this on several different encodes.
Maybe the later release version of x264 in build BD-RB v0.40.09 could be the cause?

With build BD-RB v0.40.08 and that earlier version of x264 all encodes works fine.
Did some testings with LinX 0.64 and let it run on high priority for hours without getting any errors.
Monitored power with CPUID HWMonitor and my Corsair 1200W seems to work OK.
CPU temperature on 100% load is 55-60C so no heat issue.
Also uninstalled ffdshow, Hali Matroska Splitter, Avisynth and cleaned registry and then reinstalled.

What could be the cause of x264 crashing? It's probably on my end since there's no reports from other users.

Regards

[busch42]

varekai, I too have the same problem. I had a problem similar to this about 4 weeks ago, So I wiped my hard drive and reinstalled windows 7 64bit then everything worked great, This is the first time I did a Bluray (Contraband) in a few weeks now I'm having your problem after installing Bdrebuilder version 04009. I haven't installed any new programs so I'm not sure what could be causing this. Here's my report If anyone could please help ,
H.264 (MPEG-4 AVC) encoder has stopped
working
A problem caused the program to stop working correctly.

[04/27/12] BD Rebuilder v0.40.09 (beta)
[09:46:06] Source: CONTRABAND
- Input BD size: 32.09 GB
- Approximate total content: [01:49:38.446]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[09:46:06] PHASE ONE, Encoding
- [09:46:06] Processing: VID_00023 (1 of 1)
- [09:46:06] Extracting A/V streams [VID_00023]
- [10:14:32] Reencoding video [VID_00023]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 157,725 frames
- Bitrate: 26,116 Kbs
- [10:14:32] Reencoding: VID_00023, Pass 1 of 1
- Encode failed. Aborting.
- BD-Rebuilder v0.40.09 (beta)
- Windows Version: 6.1 [7601]
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 3882, Ok
- WIN7 preferred AVC CODEC: Ok
- WIN7 preferred VC-1 CODEC: Ok
- WIN7 preferred MPEG2 CODEC: Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "ffmpeg-mt": Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
[10:43:46] - Failed video encode, aborted

[omegaman7]

Most likely not a bug in BD-RB but something makes x264 crash.
"H.264 (MPEG-4 AVC) encoder has stopped working..." and BD-RB stops with message "- Failed video encode, aborted".
I've been able to reproduce this on several different encodes.
Maybe the later release version of x264 in build BD-RB v0.40.09 could be the cause?



What are some titles you've had trouble with? Please give multiple examples.

[busch42]

omegaman7, The movie I'm trying is Contraband, I did rip it to hard drive with anydvd.

[omegaman7]

I'm afraid I won't have that one for a while. Money is tight :(

I do however have multiple new releases waiting for me.

[busch42]

I tried several programs to shrink the movie Contraband to a BD25 and nothing works, So I'm begining to think it isn't BDrebuilder but maybe a bad rip to hard drive, Has anybody had any luck with this movie?

[setarip_old]

@busch42

Hi! I tried several programs to shrink the movie Contraband to a BD25 and nothing worksIf I remember correctly, if you want to do a "Movie-only" of this disc, you have to first remove what appears to be a secondary video from 00023.m2ts

Have you tried doing a "FULL DISC" copy using the same rip?

[varekai]

What are some titles you've had trouble with? Please give multiple examples.

The problems I'm having with x264 is not related to any particular titles.
Tested with older titles as well as newer.

Regards

[omegaman7]

Well I've ran at least 5 titles without trouble on the newest version. Again, a title (or multiple) would help us pinpoint the problem. E.g. if you run "Tower Heist" and have a problem, then I should run it, and see if I have the same problem.

Obviously Jdobbs felt the new version was ready ;)

[varekai]

@omegaman7

I don't have "Tower Heist" and I'm not planning on getting it.
Made BD-RB v0.40.09 encodes of new title "The Girl with the Dragon Tattoo"
and the old title "Saving Private Ryan" and x264 crashed on both titles.
BD-RB v0.40.08 encodes of the same titles works flawlessly.
Encode settings are identical in both BD-RB versions.
I can't figure out why x264 crashes?

Regards

[Capsbackup]

@omegaman7

I don't have "Tower Heist" and I'm not planning on getting it.
Made BD-RB v0.40.09 encodes of new title "The Girl with the Dragon Tattoo"
and the old title "Saving Private Ryan" and x264 crashed on both titles.
BD-RB v0.40.08 encodes of the same titles works flawlessly.
Encode settings are identical in both BD-RB versions.
I can't figure out why x264 crashes?

Regards

Try switching x264 from BD-RB v0.40.08 and put that one in BD-RB v0.40.09 to see if the newest x264 is causing the problem. ;)

[jdobbs]

Well I've ran at least 5 titles without trouble on the newest version. Again, a title (or multiple) would help us pinpoint the problem. E.g. if you run "Tower Heist" and have a problem, then I should run it, and see if I have the same problem.

Obviously Jdobbs felt the new version was ready ;) I've done about 40 backups using the new version... no issues.

There was a new version of X264 included in the release of BD-RB v0.40.09, so there's always a chance that could be an issue. Since then there is another new version of X264 (http://www.x264.nl/) (revision 2197) out, in case someone thinks they are crashing due to the last release. I just started testing it today. Just remember to only use the 8-bit depth versions. You also have to remember to rename the 64 bit version to x264-64.EXE for BD-RB to see it.

[varekai]

Try switching x264 from BD-RB v0.40.08 and put that one in BD-RB v0.40.09 to see if the newest x264 is causing the problem. ;)

I did think of that but never actually tested because BD-RB System Inspection gives " -X264: Wrong version found"

Regards

[varekai]

I've done about 40 backups using the new version... no issues.

There is a new version of X264 (http://www.x264.nl/) out, in case someone thinks they are crashing due to the last release. Just remember to only use the 8-bit depth versions. You also have to remember to rename the 64 bit version to x264-64.EXE for BD-RB to see it.

:D Thanks, I'll try that new version at once!
So I'll ignore BD-RB System Inspection and give it a go!
Good to see you, been real quiet here lately...

Regards

[jdobbs]

:D Thanks, I'll try that new version at once!
So I'll ignore BD-RB System Inspection and give it a go!
Good to see you, been real quiet here lately...

Regards

Yeah, other work (the kind that actually pays my bills) has been pulling me in several directions lately. I'm on the road a lot and don't have much free time. Hopefully it will quiet down by summer.

[jdobbs]

I did think of that but never actually tested because BD-RB System Inspection gives " -X264: Wrong version found"

Regards Yeah, just ignore it.

[varekai]

Yeah, the real job (the one that actually pays my bills) has been pulling me in several directions lately. I'm on the road a lot and don't have much free time. It should quite down a bit by summer.

I know what you mean, done a lot of touring myself working as a stage crew, eat-work-sleep-travel-eat-work-sleep...
I'm retired now, and summer is just around the corner, thank goodness! :D

Will make a donation to your much appreciated BD-RB project!

Regards

[jdobbs]

eat-work-sleep-travel-eat-work-sleepThat pretty much sums it up. I'm sitting here right now, half-asleep, thinking about that 4:00am wakeup tomorrow.

[wolverine3n8]

Yeah, other work (the kind that actually pays my bills) has been pulling me in several directions lately. I'm on the road a lot and don't have much free time. Hopefully it will quiet down by summer.

It's none of my business but what do you do in real life? Feel free to ignore this btw.

[omegaman7]

Given his expertise (Jealous), I'm sure it's some kind of computer consultant work. Networking, or what not. One day!

[busch42]

setarip_old, No I haven't tried to do a full movie backup, But i read on another site's forum where someone said they did just the main movie with BDrebuilder and had no problems.

[busch42]

jdobbs, I'm going to try the new version of x264, Do I just copy and paste the new one over the old one? If so I noticed in the Bdrebuilder program that the x264 application has no .exe after it.

[omegaman7]

Either it's been renamed, or windows doesn't allow you to see the file extensions. You can change that ;)

[jdobbs]

@busch42

You must have "Hide extensions to known file types" enabled in Windows Explorer's folder options. BD-RB uses the .EXE extension.

[busch42]

Thanks jdobbs, I tried the new version of x264 and this time I got to 17.40%, that's futher then before, I'm doing the bluray movie of Contraband, I don't think it's BDrebuilder's fault because if it was it wouldn't work from the beginning at least you would think that, At least the program starts then just comes up x264 has stopped working.