BD Rebuilder Beta - Bug Reports Only

[kanerulz69]

If its not stable -- explain how?

meaning that the progress bar jus gets stuck on version 2201 & 2202 so i went back to 09, i had to open up 2209 and resume where it froze and got stuck

[MikeyBK]

meaning that the progress bar jus gets stuck on version 2201 & 2202 so i went back to 09, i had to open up 2209 and resume where it froze and got stuck

But if you thoroughly read the thread about that issue, you'd have found out that it is only a cosmetic issue and that the encoding 'does' complete successfully if you let it run. X264 is still encoding even thought the progress bar doesn't reflect that.

[kanerulz69]

But if you thoroughly read the thread about that issue, you'd have found out that it is only a cosmetic issue and that the encoding 'does' complete successfully if you let it run. X264 is still encoding even thought the progress bar doesn't reflect that.

i even clicked on the working folder (right click properties) just to see after like 10min if the progress was still doing anything and the file size was still the same it didnt even change any

[MikeyBK]

i even clicked on the working folder (right click properties) just to see after like 10min if the progress was still doing anything and the file size was still the same it didnt even change any

A better way to verify that x264 is still actually encoding would be to use something like RealTemp or CoreTemp and it'll show that your cores are all spiking.

We've all verified that even though it appears stuck on the GUI, the encoding does continue in the background.

Or even better yet, as JDobbs himself suggested, enter the parameter 'SHOW_ENCODER=1' into the INI file, and it will show x264 encoding.

[kanerulz69]

A better way to verify that x264 is still actually encoding would be to use something like RealTemp or CoreTemp and it'll show that your cores are all spiking.

We've all verified that even though it appears stuck on the GUI, the encoding does continue in the background.

Or even better yet, as JDobbs himself suggested, enter the parameter 'SHOW_ENCODER=1' into the INI file, and it will show x264 encoding.

thats fine and all but since .09 works the best for me and i enjoy seeing the progress bar as its going so i know when its going 2 be finished i'll stick to that til a different layout of the program with pause / resume etc is created, still i love the program and will continue to try all the versions that come out just in case

[MikeyBK]

thats fine and all but since .09 works the best for me and i enjoy seeing the progress bar as its going so i know when its going 2 be finished i'll stick to that til a different layout of the program with pause / resume etc is created, still i love the program and will continue to try all the versions that come out just in case

No worries Bro, it's your prerogative....
however... it doesn't really help JD as much as if you'd use the latest Beta just in case you might come across some other 'bug' that might be specific to your PC configuration.
He's basically pretty much asked that all users use the latest Beta, unless there is a complete instability.... which there really isn't in v0.22.02.

[Furiousflea]

Thought I'd report back my findings with using the hidden keep interlaced option set to "1".

Have found no problems at all with this on 5-6 discs. Plays without issue at all on my Sony BDP-S550. For me I consider it the "default" to use.

[user822]

having some problems with "Batman Begins"

Resize to 720p does not work

EDIT: It works with oder Movies and i fixed it by editing the .avs file manually(afer killing x264 with the 1080p settings it said "encode failed, retry" and then it started again using the edited avs file)

[jdobbs]

i even clicked on the working folder (right click properties) just to see after like 10min if the progress was still doing anything and the file size was still the same it didnt even change any That's not a good check. It won't change until the file is closed.

[jdobbs]

A better way to verify that x264 is still actually encoding would be to use something like RealTemp or CoreTemp and it'll show that your cores are all spiking.

We've all verified that even though it appears stuck on the GUI, the encoding does continue in the background.

Or even better yet, as JDobbs himself suggested, enter the parameter 'SHOW_ENCODER=1' into the INI file, and it will show x264 encoding.

I think I have the issue fixed anyway (I can't be sure since it never happens to me) -- I'll post a new version later today.

[jdobbs]

having some problems with "Batman Begins"

Resize to 720p does not work

EDIT: It works with oder Movies and i fixed it by editing the .avs file manually Doesn't work how? It doesn't playback, fails, hits an error, or just doesn't resize?

[user822]

Doesn't work how? It doesn't playback, fails, hits an error, or just doesn't resize?

it keeps 1080p(main movie) perhaps because it "thinks" it is a menu or something

i edited my original post how i fixed it:

EDIT: It works with oder Movies and i fixed it by editing the .avs file manually(afer killing x264 with the 1080p settings it said "encode failed, retry" and then it started again using the edited avs file). I added LanczosResize(1280,720) myself(hope it does not make any problems later)

[leChameleon]

I wanted to see if anyone else is experiencing increased run times and memory consumption in 0.22.02 ?

Most rebuilds use to take around 10 hours, sometimes 12 hours on a Intel i7 Core 940, 12GB RAM, 6TB HDD running Windows 7 64-bit.

I'm running DEFIANCE 2008, Region A now and it's consumed 9.47GB of RAM @ 40.87% overall progress.

[23:41:20] BD Rebuilder v0.22.02 (beta)
- Source: DEFIANCE
- Input BD size: 43.95 GB
- Approximate total content: [03:10:09.064]
- Target BD size: 22.46 GB

http://img189.imageshack.us/img189/6720/perfb.jpghttp://img189.imageshack.us/img189/5967/pros.jpg

I suspect it's not BD-RB but rather a different version of x264 that may be causing it.

[leChameleon]

Removed...

[user822]

my blu ray with the changed avs did not work

maybe not because of resize but because of other problems(powerdvd also didnt play it)

anyway i ordnered the blu ray on amazon *gg*

[Furiousflea]

I wanted to see if anyone else is experiencing increased run times and memory consumption in 0.22.02 ?

Most rebuilds use to take around 10 hours, sometimes 12 hours on a Intel i7 Core 940, 12GB RAM, 6TB HDD running Windows 7 64-bit.

I'm running DEFIANCE 2008, Region A now and it's consumed 9.47GB of RAM @ 40.87% overall progress.

[23:41:20] BD Rebuilder v0.22.02 (beta)
- Source: DEFIANCE
- Input BD size: 43.95 GB
- Approximate total content: [03:10:09.064]
- Target BD size: 22.46 GB

http://img189.imageshack.us/img189/6720/perfb.jpghttp://img189.imageshack.us/img189/5967/pros.jpg

I suspect it's not BD-RB but rather a different version of x264 that may be causing it.

You sure it's bdrb\x264. Can see your uptime is a good few days. Try a restart, maybe you've got some spyware\dodgy webpage thats loaded something and is eating all the memory. Worth a check anyways.

[setarip_old]

@user822

Hi!anyway i ordnered the blu ray on amazonWhat will you gain by purchasing a second BluRay disc of "Batman Begins"? You'll still be confronted with trying to downconvert from 1080p to 720p...

[leChameleon]

You sure it's bdrb\x264. Can see your uptime is a good few days. Try a restart, maybe you've got some spyware\dodgy webpage thats loaded something and is eating all the memory. Worth a check anyways. Up time has nothing to do with it. I've checked this behavior over the past week, and have seen similar behavior.

What it appears to me is that x264 keeps incrementing memory and is not releasing it. Currently the same job is now over 10GB of RAM and 1,420KB of memory with a CPU time of almost 6 hours. If you look at the swap, why would it ever get so high?

Second the only thing that is running on this machine is BD-RB and me accessing this web page only, other than the default page GOOGLE.com when it invokes.

I've been monitoring memory usage over the past week and there are no other apps consuming memory and the disk space in other areas remains constant accept for the swap space and where BD-RB is working.

At the time x264 is finished reencoding one section the memory space is never released. Once another job is launched it continues to increment. Once x264 exits and starts another job the RAM should be released and the page file flushed.

[GaPony]

No such problems with my PC...

[jdobbs]

Mine is working correctly also.

[SurroundBoy]

Can anyone here source out my issue? Trying to re-encode to BD-5, I use 720p and it fails while extracting audio. If I turn off the 720p and just have it do 1080p, it continues fine. Whats the problem here with switching 720p on and off?

[drmih]

I thought I was imagining it but mine is also much slower. I started an encode but after an hour realised I had a setting wrong and broke it, change the setting and then restarted (without ever leaving bd-rb). The latest version of bd-rb has been fine so think it must have been doing the above. As soon as the encode finishes I will reboot and am sure that will sort it out.

[bassnut]

no issues with my system either. I'm Running ...

AMD Phenom Quad 940 with 4 Gig Kingston HyperX ram

Running like a charm at about 50% memory ussage and the processors at 75 - 80 % first pass and lit for the second pass. 4 - 5 hours BD9 and about 8-10 for BD25

[Groucho2004]

I believe the default priority for x264 has changed in the last build to idle.

So, whatever you have running besides x264 (virus scanner, etc) will take processor cycles away especially if the priority is higher than idle.

This might explain the slower encodes reported by some people.

[jdobbs]

I believe the default priority for x264 has changed in the last build to idle.

So, whatever you have running besides x264 (virus scanner, etc) will take processor cycles away especially if the priority is higher than idle.

This might explain the slower encodes reported by some people.Definitely. With older versions NORMAL priority was the default, but the INI that way included in the ZIP file had IDLE set. I stopped shipping an INI in the package, so the default started coming through. In the last release I changed the DEFAULT to IDLE. IDLE will run just as fast as NORMAL when the system is not being used, but when you start running other programs they will have a higher priority and could slow down BD-RB.

[user822]

@user822

Hi!What will you gain by purchasing a second BluRay disc of "Batman Begins"? You'll still be confronted with trying to downconvert from 1080p to 720p...

the first one was a iso file and i dont have a bd burner

[woodman]

Hi, just backed up Chronicles Of Riddick to BD25 (full backup) and the film jerks about every second, apart from that it plays fine, sound ok. Anyone got any idea whats wrong. Thanks

[setarip_old]

@user822the first one was a iso file and i dont have a bd burner

This thread is for reporting BD-RB bugs that arise from a process starting with a commercial disc as the initial source.

It's grossly unfair to waste the time of the author "jdobbs", by asking him to resolve problems that you're having with "other than original" source material (and, if that's the case, it's also a violation of the rules of the Doom9 Forums)...

[Wolfe999]

As of v0.22.02 the "problem" of the 50% freezing still continues. Yeah, I click abort and then backup and resumes, but anyway I think it still is a bug. Never happened/happens with v0.21.01. It seems it began with 0.22. My PC is the same, as I only do encodes in it and haven installed anything new since then. As you say, hope you have it fixed with the new version.

regards and thanx again :)

[datman]

I have been seeing a few pixelation defects in every backup that I have watched using 22.01 & 22.02, may have been doing with every version. I haven’t been looking for it. They are very short and toward the end of the film only a few frames and the audio is unaffected.

My setup is Movie only, to a BD-25 target the slowest speed, keeping the HD audio

It’s a very small defect and may only happen when saving to a BD-25 target. I can live with it for backups.

Has anyone else seen this?

Thanks for the heads up That might be it. I removed 2 programs MakeMKV and smartshopper. I have not changed anything and this computer is never (rarely) on the internet but perhaps that was it.

I played 22.02 encodes films that were movie only to a BD-9 and full movie to a BD-25 and had no pixelation, as far as I saw.

[GaPony]

You definitely don't need the highest quality (slowest) setting for copying to a BD25 disc... its really alot of overkill. In fact, the good quality (fast) setting gives excellant results for BD25 copies. I usually use the high quality setting, but its more from pathological reasoning than any real quality improvement.

[YolkiePolkie]

I'm also getting the freezing at 50% with v0.22.02. It worked for the first disc I encoded no problems, but for the next 2 it has frozen. Have rebooted between encodes. Any advice appreciated.

[MikeyBK]

I'm also getting the freezing at 50% with v0.22.02. It worked for the first disc I encoded no problems, but for the next 2 it has frozen. Have rebooted between encodes. Any advice appreciated.

Read back a few pages and you'll see that it is merely a cosmetic bug, and not the encoding failing...
The project will complete successfully even though it appears stuck in the GUI.

Has been talked about ever since v0.22.01 & v0.22.02 was released... so no need to reboot or abort... let it just finish and 'it will' :)

[deank]

Is it possible that some recent Windows (XP/Vista) update caused this problem with '50%' erroneous display? Just a thought.

[YolkiePolkie]

Read back a few pages and you'll see that it is merely a cosmetic bug, and not the encoding failing...
The project will complete successfully even though it appears stuck in the GUI.

Has been talked about ever since v0.22.01 & v0.22.02 was released... so no need to reboot or abort... let it just finish and 'it will' :)


Thanks very much for the info. Have been off the scene for around 2 months and so have not been able to keep up to date. Keep it Mencap.

[Mr. Movies]

Is it possible that some recent Windows (XP/Vista) update caused this problem with '50%' erroneous display? Just a thought.

I don't think it is an update as I've not updated my machine but it does it now that I've upgraded from 20.08 to the current version, something else is going on.

I've had pretty good luck with BD-RB especially since I VC-1 fixed my setup but now I'm having audio sync issues for the first disc of the 3 disc set of Firefly. The funny thing is all short (normal) episodes sync fine it is only the first episode that gets out of sync. It plays fine for the first 8 minutes and then the lip sync is off by almost 4 seconds. All following episodes are fine. I've tried x264 and FFMPEG but the problem remains the same.

The first M2TS is the openning episode and is 16.9GB uncompressed, but comes out to 8.33GB compressed for "00001.m2ts". The original file plays fine of course. There might be some dead space between the opening of the audio track and when the episode would come back from commercial. When encoding videos manually I've had problems with that so I wonder if that could be the cause here?

BDREBUILDER.INI
Last Settings with no re-encode audio & using x264
[Options]
MODE=0
QUICK_EXTRAS=0
PRIORITY_CLASS=0
RESIZE=0
ENCODER=0
ENCODE_QUALITY=3
TARGET_SIZE=23450
AUDIO_TO_KEEP=all
SUBS_TO_KEEP=all
TRELLIS=1
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
KEEP_HD_AUDIO=1
AVCHD=1
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=22450
VERBOSE_STATUS=1
[Paths]
SOURCE_PATH=E:\MOVIES\BD\FIREFLYUS_D1\
WORKING_PATH=E:\MOVIES\TEMP\

Normal settings using FFMPEG
[Options]
MODE=0
QUICK_EXTRAS=0
PRIORITY_CLASS=0
RESIZE=0
ENCODER=1
ENCODE_QUALITY=3
TARGET_SIZE=23450
AUDIO_TO_KEEP=all
SUBS_TO_KEEP=all
TRELLIS=1
COLOR_BOOST=0
RESIZE_1080=0
DTS_REENCODE=1
AC3_REENCODE=1
AC3_640=0
KEEP_HD_AUDIO=1
AVCHD=1
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=22450
VERBOSE_STATUS=1
[Paths]
SOURCE_PATH=E:\MOVIES\BD\FIREFLYUS_D1\
WORKING_PATH=E:\MOVIES\TEMP\


I do have TMT 2.6.119 installed and have the VC-1 reg hack to fix not being able to transocde some of my other movies.

One other question - Why is FFMPEG greyed out so that the only way I can select it is by changing the Encode=1 in the INI file?

[Wolfe999]

Read back a few pages and you'll see that it is merely a cosmetic bug, and not the encoding failing...
The project will complete successfully even though it appears stuck in the GUI.

Has been talked about ever since v0.22.01 & v0.22.02 was released... so no need to reboot or abort... let it just finish and 'it will' :)

I'm not sure about what you say, MikeyBK, because last night I left a movie during the night, and when I woke it was stuck in the 50%. I decided to wait and not touch anything, so I went out and came back 4 hours later, and it was at the same point... had to abort and click again backup for it to begin the second pass. Let me tell you that in my new PC the "movie only" I do always lasts around 4/5 hours, not more, so it didn't complete by itself, though it was maxing my CPU at 100%. Regretfully, I'll have to go back again to 0.21.01.

Just edited a typo :)

[DMagic1]

Sorry if this was brought up before, Is there a way to have BDRebuilder only encode extras and leave main titile video untouched except the stipping of audio?

[Furiousflea]

Sorry if this was brought up before, Is there a way to have BDRebuilder only encode extras and leave main titile video untouched except the stipping of audio?

not yet, surely in future releases though.

[GaPony]

I'm not sure about what you say, MikeyBK, because last night I left a movie during the night, and when I woke it was stuck in the 50%. I decided to wait and not touch anything, so I went out and came back 4 hours later, and it was at the same point... had to abort and click again backup for it to begin the second pass. Let me tell you that in my new PC the "movie only" I do always lasts around 4/5 hours, not more, so it didn't complete by itself, though it was maxing my CPU at 100%. Regretfully, I'll have to go back again to 0.21.01.

Just edited a typo :)

Maybe that one movie froze up for some unrelated reason, but everything I've done that got stuck on 50% has completed normally. Mikeyb is right on this issue. (Did I really just say that? :))

[MikeyBK]

I'm not sure about what you say, MikeyBK, because last night I left a movie during the night, and when I woke it was stuck in the 50%. I decided to wait and not touch anything, so I went out and came back 4 hours later, and it was at the same point... had to abort and click again backup for it to begin the second pass. Let me tell you that in my new PC the "movie only" I do always lasts around 4/5 hours, not more, so it didn't complete by itself, though it was maxing my CPU at 100%. Regretfully, I'll have to go back again to 0.21.01.

Just edited a typo :)

Well the fact that your CPU is spiking to max, tells you that it is encoding.

Every single one I've done has completed, and successfully.... so not sure what you're doing differently or wrongly.

I'm thinking that v0.21.01 is about to expire.... not sure, but I think JD still times out each Beta so users don't report bugs from older betas.

(oh BTW, I also agree with GaPony..... and I also can't believe I'm agreeing with him on this LOL)

[Mr. Movies]

Well the fact that your CPU is spiking to max, tells you that it is encoding.

Every single one I've done has completed, and successfully.... so not sure what you're doing differently or wrongly.

I'm thinking that v0.21.01 is about to expire.... not sure, but I think JD still times out each Beta so users don't report bugs from older betas.

(oh BTW, I also agree with GaPony..... and I also can't believe I'm agreeing with him on this LOL)

With this new version and trying to re-run my Firefly my machine just froze up at the 100% mark of the 1st pass of the first stream, the largest one on this disc of a 4 episode disc. My 4 cores were close to 100% usage, but were not fluctuating as they would normally if the encoding was still happening, and my keyboard / mouse stopped responding which I haven't had problems with until this last RB update.

My mem clocking was off so that is why mine froze up this time I've been running my pC hard for the last 3 days and it's hot so ignor this post.

[Wolfe999]

Well the fact that your CPU is spiking to max, tells you that it is encoding.

Every single one I've done has completed, and successfully.... so not sure what you're doing differently or wrongly.

I'm thinking that v0.21.01 is about to expire.... not sure, but I think JD still times out each Beta so users don't report bugs from older betas.

(oh BTW, I also agree with GaPony..... and I also can't believe I'm agreeing with him on this LOL)

Mine have not completed. The fact that my CPU is spiking to the max tells me that 264 is using it, not that it's encoding because the movie didn't finish 12 hours later, and after I aborted and clicked backup again, it required 2/3 hours more to finish.

I'm doing nothing differently nor wrongly, because each time I've gone back to 0.21.01, I repeated the same steps (movie only, 2 languages, 2 subs, that's all, and depending of the length of the movie, BD-5 or BD-9) and the encoding finished during those 4/5 hours total.

It's a pity that 0.21.01 would expire, because I only can talk about my experience, and that of v0.22.02 for me it's no cosmetic bug, because if I'm not present my computer runs and runs and runs without finishing the encode

In that machine I'm not connected to the net, so it's not a problem of some update.

[GaPony]

I found that on a couple of movies that appear to freeze at the 50% mark, if I abort and then restart the progress bar starts working. This hasn't been true in all instances, however.

I think you might be experiencing the same symptom (progress bar freezing) for an entirely different problem. Which makes it very difficult for you to pinpoint. Hopefully the next update will shed some light on your issue. It should be out at anytime now...

[setarip_old]

@Mr. Movies

Hi!When encoding videos manually I've had problems with that so I wonder if that could be the cause here?Please explain what you mean by "encoding videos manually"...

[liquidskin76]

@jdobbs

Just curious... what's the minimum custom target size that can be used before HD audio isn't kept (with the option to keep HD audio enabled)?

Keep up the amazing work!

[tekmobile]

@jdobbs

Just curious... what's the minimum custom target size that can be used before HD audio isn't kept (with the option to keep HD audio enabled)?

Keep up the amazing work!

Anything greater that BD9

[MILLZY]

The links to the files are highlighted in the text in the first post. If you have TMT2 installed, download the update patch and the filter tweak, otherwise if you have powerdvd use that although as stated it does resize to 740x480.

Seeing the questions you've asked I really would go for the bd-25 route and use the minimum file size as it's a simple and perfect solution.

Were do i add the "MIN_M2TS= ****
Sorry for being a noob!

[liquidskin76]

Anything greater that BD9

Cheers tekmobile.

I've just tested this with a custom size of 12500 and it's retained the HD audio.

[Wolfe999]

I found that on a couple of movies that appear to freeze at the 50% mark, if I abort and then restart the progress bar starts working. This hasn't been true in all instances, however.

I think you might be experiencing the same symptom (progress bar freezing) for an entirely different problem. Which makes it very difficult for you to pinpoint. Hopefully the next update will shed some light on your issue. It should be out at anytime now...

First of all, I do not want to give the impression that I want to be polemic. It's not my nature and never was.

Yesterday I left encoding (reverting to v0.21.01) during the night a movie of 90 mins. When I woke up I saw in the log that all the process took 3 hours, 40 mins.

It's not the bar that freezes, It's the ENCODING. Whenever it happened, it never finished during all night. Can't say what that different problem might be, because as I already said, I use that computer only for encoding, it's not connected to the net and I do not install programs not necessary for the BD encoding. And whenever I go back to v0.21.01, the problem vanishes. So that make me believe that it's not on my side (but believe me that I wouldn't mind at all that you'd said to me, "look, wolfe, your problem is here, and here, and here, change this from your side and everything will be fine. I' do it, of course), besides that many others have experienced it.

And it's not a couple of movies, it's happened on almost all (because I can't remember having a finished encoding with 0.22.02) the movies I did with the 0.22 versions.

So, from my part, this issue is finished. I'll be reading the post and when this "problem" is solved for me, don't doubt that I'll post my experience. (Meanwhile, I'll be praying that v0.21 doesn't expire)

Best regards
Wolfe :)

EDIT typo in version