BD Rebuilder Beta - Bug Reports Only

[jdobbs]

Ouuuu ! Alien intervention ! This is exactly what my problematic VC-1 title is about ! (4th kind).
So now we found the bug LOL !

Seriously, can you provide, as i asked before, the registry paths i should be looking into (and what values they should be after BD-RB intervention ?) so at least i can start debugging something ?

:thanks:A warning to all -- if you are not careful you can screw yourself permanently by messing with the registry -- and you're on your own when that happens. I take no responsibility for any actions you take in editing the registry.

@PhilippeB
For your problem it appears that there are some keys that should be set but are not.


In this registry area:
HKLM\Software\Microsoft\Directshow\Preferred

These keys:

{31435657-0000-0010-8000-00AA00389B71}
{31435641-0000-0010-8000-00AA00389B71}
{e06d8026-db46-11cf-b4d1-00805f6cbbea}

should all be set to

{04FE9017-F873-410E-871E-AB91661A4EF7}

That tells the system that the preferred DirectShow CODEC for VC-1, AVC, and MPEG-2 should be FFDSHOW.

BD-RB looks at these keys when it loads on a Windows 7 system, and tells you when they are incorrect. It then gives you a prompt and attempts to set them correctly. It then looks at them, and if they weren't changed it knows it didn't have privilege to do so, and gives you another "you need to run me as administrator" message.

When it successfully changes them, it also creates a batch file in the BD-RB folder that lets you change them back to their original state.

Note that on Windows 7 64 bit systems the registry path (in REGEDIT) may be:

HKLM\SOFTWARE\Wow6432Node\Microsoft\DirectShow\Preferred

[shon3i]

Why not just use Win7DSFilterTweaker (http://www.codecguide.com/Win7DSFilterTweaker.zip) and set to ffdshow, because is recommended over manual tweaking registry.

[jdobbs]

Why not just use Win7DSFilterTweaker (http://www.codecguide.com/Win7DSFilterTweaker.zip) and set to ffdshow, because is recommended over manual tweaking registry. Because BD Rebuilder does it for you anyway. You don't need anything else like an additional tweaker. I'm just posting this because I was asked for the information, and PhilippeB doesn't seem to believe me when I tell him...

[laserfan]

@PhilippeB
For your problem it appears that there are some keys that should be set but are not.

In this registry area:
HKLM\Software\Microsoft\Directshow\Preferred

These keys:

{31435657-0000-0010-8000-00AA00389B71}
{31435641-0000-0010-8000-00AA00389B71}
{e06d8026-db46-11cf-b4d1-00805f6cbbea}

should all be set to

{04FE9017-F873-410E-871E-AB91661A4EF7}

That tells the system that the preferred DirectShow CODEC for VC-1, AVC, and MPEG-2 should be FFDSHOW.

BD-RB looks at these keys when it loads on a Windows 7 system, and tells you when they are incorrect. It then gives you a prompt and attempts to set them correctly. It then looks at them, and if they weren't changed it knows it didn't have privilege to do so, and gives you another "you need to run me as administrator" message.

When it successfully changes them, it also creates a batch file in the BD-RB folder that lets you change them back to their original state.

Note that on Windows 7 64 bit systems the registry path (in REGEDIT) may be:

HKLM\SOFTWARE\Wow6432Node\Microsoft\DirectShow\Preferred@jdobbs as PhilippeB has said his is a W7 64-bit machine, the entries at issue for him are in the Wow6432Node, not the first mentioned in your post.

I just checked my own 64-bit system and the Wow6432Node entries are all {04FE9017-F873-410E-871E-AB91661A4EF7} but the HKLM\Software\Microsoft\Directshow\Preferred are different. And when I run 0.32.08 (beta) there is no mention or complaint about my system at all.

[jdobbs]

@jdobbs as PhilippeB has said his is a W7 64-bit machine, the entries at issue for him are in the Wow6432Node, not the first mentioned in your post.

I just checked my own 64-bit system and the Wow6432Node entries are all {04FE9017-F873-410E-871E-AB91661A4EF7} but the HKLM\Software\Microsoft\Directshow\Preferred are different. And when I run 0.32.08 (beta) there is no mention or complaint about my system at all.Look at the last three lines of my post...Note that on Windows 7 64 bit systems the registry path (in REGEDIT) may be:

HKLM\SOFTWARE\Wow6432Node\Microsoft\DirectShow\Preferred

[PhilippeB]

Why not just use Win7DSFilterTweaker (http://www.codecguide.com/Win7DSFilterTweaker.zip) and set to ffdshow, because is recommended over manual tweaking registry.

Shon, this is something i tried yesturday night. Surprisingly, it succeeds (at least in part) where BD-RB Fails...

I tried Win7DSFilterTweaker_1.9 and had put everything in there to ffdshow (under 32 bits tree). I Then started BD-RB and for the 1st time, it didn't complain about anything. So for BD-RB at that point everything was fine. EXCEPT, it will still fail at the CODEC but without complaining about VC-1 and MPEG not being attributed to FFDSHOW.

Proof of what i am saying is here:

-----------------------
[14:27:40] BD Rebuilder v0.32.08 (beta)
- Source: THE_MUMMY
- Input BD size: 29,42 GB
- Approximate total content: [02:04:53.235]
- Target BD size: 23,93 GB
- Windows Version: 6.1 [7600]
- MOVIE-ONLY mode enabled
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[14:27:41] PHASE ONE, Encoding
- [14:27:41] Reencoding: VID_00000 (1 of 1)
- [14:27:41] Collecting video information
- Source Video: VC-1, 1920x1080
- Rate/Length: 23,976fps, 179*658 frames
- Bitrate: 19*550 Kbs
- [14:27:41] Reencoding: VID_00000, Pass 1 of 2
- Encode failed. Retrying. <- No more VC-1 not configured for FFDSHOW
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- FFDSHOW Revision: (3133)
[14:27:43] - Failed video encode, aborted

--------------------------------------------------


Ok, well, it's a start, that lead me to think JDoobs is looking under the 32-bit keys tree rather than the 64. But my machine is 64 bits. Back to Win7DSFilterTweaker_1.9, under the 64-bit tree, for all codecs, the only option available is MICRO$OFT.

Humm.. Does that mean i need to install some set of 64 bits codecs ? Does BD-RB needs 64-bit codecs if my machine is 64 bits ? Or can it uses 32-bit (then how do i tell it to go for 32-bits instead of theses 64-bit that are microsoft only ? Should i install a 64-bit FFDSHOW (Does that exists ?) Then again, i heard JDoobs saying that AVISYNTH doesn't like 64-bit codecs..

Gee - everything was so simple under RC-1 (64 bits still) should never had gone legit with RTM =P

I Will try to do a VDO at some point and post it to Youtube to show it to everybody. I seem to have fallen into a void somewhere. But my objective is to clarify this so next versions can address this problem in any situation (32, 64 or whatever the problem is).

:thanks:

[jdobbs]

Shon, this is something i tried yesturday night. Surprisingly, it succeeds (at least in part) where BD-RB Fails...

I tried Win7DSFilterTweaker_1.9 and had put everything in there to ffdshow (under 32 bits tree). I Then started BD-RB and for the 1st time, it didn't complain about anything. So for BD-RB at that point everything was fine. EXCEPT, it will still fail at the CODEC but without complaining about VC-1 and MPEG not being attributed to FFDSHOW.

Proof of what i am saying is here:

-----------------------
[14:27:40] BD Rebuilder v0.32.08 (beta)
- Source: THE_MUMMY
- Input BD size: 29,42 GB
- Approximate total content: [02:04:53.235]
- Target BD size: 23,93 GB
- Windows Version: 6.1 [7600]
- MOVIE-ONLY mode enabled
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[14:27:41] PHASE ONE, Encoding
- [14:27:41] Reencoding: VID_00000 (1 of 1)
- [14:27:41] Collecting video information
- Source Video: VC-1, 1920x1080
- Rate/Length: 23,976fps, 179*658 frames
- Bitrate: 19*550 Kbs
- [14:27:41] Reencoding: VID_00000, Pass 1 of 2
- Encode failed. Retrying. <- No more VC-1 not configured for FFDSHOW
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- FFDSHOW Revision: (3133)
[14:27:43] - Failed video encode, aborted

--------------------------------------------------


Ok, well, it's a start, that lead me to think JDoobs is looking under the 32-bit keys tree rather than the 64. But my machine is 64 bits. Back to Win7DSFilterTweaker_1.9, under the 64-bit tree, for all codecs, the only option available is MICRO$OFT.

Humm.. Does that mean i need to install some set of 64 bits codecs ? Does BD-RB needs 64-bit codecs if my machine is 64 bits ? Or can it uses 32-bit (then how do i tell it to go for 32-bits instead of theses 64-bit that are microsoft only ? Should i install a 64-bit FFDSHOW (Does that exists ?) Then again, i heard JDoobs saying that AVISYNTH doesn't like 64-bit codecs..

Gee - everything was so simple under RC-1 (64 bits still) should never had gone legit with RTM =P

I Will try to do a VDO at some point and post it to Youtube to show it to everybody. I seem to have fallen into a void somewhere. But my objective is to clarify this so next versions can address this problem in any situation (32, 64 or whatever the problem is).

:thanks: You know, a little logic would lead you to believe that what you are saying is BS... have you noticed at all that it is working for everybody else on the planet who has a Win7 64 bit setup except for you...

If you starting installing 64 bit codecs I can guarantee you will have additional failures.

You obviously know more than I do. But do me a favor, if you post videos about how to do this -- please caviat it with "the developer of BD-RB doesn't agree with this". Because all it's going to do is cause me more headaches.

Hope you find your problem. I give up.

And by the way... my name isn't JDoobs, it's jdobbs. I would appreciate it if you at least got THAT right.

[PhilippeB]

For your problem it appears that there are some keys that should be set but are not.


In this registry area:
HKLM\Software\Microsoft\Directshow\Preferred

These keys:

{31435657-0000-0010-8000-00AA00389B71}
{31435641-0000-0010-8000-00AA00389B71}
{e06d8026-db46-11cf-b4d1-00805f6cbbea}

should all be set to

{04FE9017-F873-410E-871E-AB91661A4EF7}

That tells the system that the preferred DirectShow CODEC for VC-1, AVC, and MPEG-2 should be FFDSHOW.

Note that on Windows 7 64 bit systems the registry path (in REGEDIT) may be:

HKLM\SOFTWARE\Wow6432Node\Microsoft\DirectShow\Preferred


Thank you very much. I will look at this verry slowly tonight.
It is okay for the warning, anybody should know it is a risky business playing directly in the registry and don't worry - i won't sue anybody if i screw up ;)
BTW i program under WinCE and have to create / modify / flush keys all the time so this is not a so different world for me.

This is the last step i will attempt. If this doesn't work, i plan to whipeout my entire system and re-install it. This takes me about 2 days so maybe it worths it.

Thanxs for the support. will come back soon with the results.

PhilippeB

PS: The alien intervention was a joke - the movie REALLY is about Aliens abductions - if anybody is into that, it is worth listening to :)

[jdobbs]

Thank you very much. I will look at this verry slowly tonight.
It is okay for the warning, anybody should know it is a risky business playing directly in the registry and don't worry - i won't sue anybody if i screw up ;)
BTW i program under WinCE and have to create / modify / flush keys all the time so this is not a so different world for me.

This is the last step i will attempt. If this doesn't work, i plan to whipeout my entire system and re-install it. This takes me about 2 days so maybe it worths it.

Thanxs for the support. will come back soon with the results.

PhilippeB

PS: The alien intervention was a joke - the movie REALLY is about Aliens abductions - if anybody is into that, it is worth listening to :) If you set these keys through system functions or via a BATCH file, they will be set in the Wow6432Node area where they are supposed to be through virtualization... but if you're doing it via REGEDIT... you have to know about virtualization and do it by hand. So be careful that you aren't setting/resetting the wrong area.

[PhilippeB]

If you set these keys through system functions or via a BATCH file, they will be set in the Wow6432Node area where they are supposed to be through virtualization... but if you're doing it via REGEDIT... you have to know about virtualization and do it by hand. So be careful that you aren't setting/resetting the wrong area.

Oki - I went throught regedit because i don't know any other way throught GUI.

Unfortunatly, everything seems to be ok. See the 3 snapshots of the 3 keys in the order you stated them (not the order they appear in regedit) in attachment.

:(

[jdobbs]

Oki - I went throught regedit because i don't know any other way throught GUI.

Unfortunatly, everything seems to be ok. See the 3 snapshots of the 3 keys in the order you stated them (not the order they appear in regedit) in attachment.

:(Are you positive you are using AVISYNTH 2.57 (not 2.58), and the versions of HAALI & FFDSHOW shown in the first post???

I can't tell from the image -- are those values in the "Wow6432Node" area or the other one?

You may also want to try right-clicking on the streams and attempting to play them back. If the CODEC is set right you should be able to view them when MPC gets executed.

I worry a little that you'd been editing the REGISTRY before -- not sure what impact that could have on this whole thing.

[kshock]

I have a Sony BVD-E300 and use BD-RB as described in the top post of the bug thread, I have done STAR TREK and 2012 to Optical Quantum BD-25 and TDK DVD+R DL as BD/9 both run great. I did movie only english only sub strict AVCHD. About 20 hrs to do each. The only changes I have made is to check all in the Blu Ray audio. Love the Program and thanks for you hard work JDobbs!!

[jdobbs]

I have a Sony BVD-E300 and use BD-RB as described in the top post of the bug thread, I have done STAR TREK and 2012 to Optical Quantum BD-25 and TDK DVD+R DL as BD/9 both run great. I did movie only english only sub strict AVCHD. About 20 hrs to do each. The only changes I have made is to check all in the Blu Ray audio. Love the Program and thanks for you hard work JDobbs!! :cool: As I've said before, if you follow the instructions it will work. It's only when people "get creative" that there is ever an issue. I appreciate your kind words.
:thanks:

[PhilippeB]

:cool: As I've said before, if you follow the instructions it will work. It's only when people "get creative" that there is ever an issue. I appreciate your kind words.
:thanks:

I always follow instructions and yes, i learned to read at school. Appreciate your concerns but condescendence will not fix my bug. Maybe let me feel a little bit more guilty of asking for help but definitly not fixing my problem.

Meanwhile, if you understood my problem was fixed it is not - even with the keys correctly setted as posted, it is still not working... I posted a log just above that shows that and i am re-posting it here:


-----------------------
[16:36:10] BD Rebuilder v0.32.08 (beta)
- Source: THE_MUMMY
- Input BD size: 29,42 GB
- Approximate total content: [02:04:53.235]
- Target BD size: 23,93 GB
- Windows Version: 6.1 [7600]
- MOVIE-ONLY mode enabled
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[16:36:12] PHASE ONE, Encoding
- [16:36:12] Reencoding: VID_00000 (1 of 1)
- [16:36:12] Collecting video information
- Source Video: VC-1, 1920x1080
- Rate/Length: 23,976fps, 179*658 frames
- Bitrate: 19*550 Kbs
- [16:36:12] Reencoding: VID_00000, Pass 1 of 2
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting. <- Observe that there is no complain anymore about VC-1 or MPEG2 not being correctly setted up for FFDSHOW
- FFDSHOW Revision: (3133)
[16:36:13] - Failed video encode, aborted

---------------------------------------------

BD-RB is probably doing its job but the codec seems to be innaccessible. Why can it BD-RB access AVC or H264, but not VC1 ? Answering that question would probably fix the problem.
I'll probably have to re-install Windows 7 (again) ... Expecting things won't stop working at the first new program install.

Maybe one solution would be to include the VC-1 codec somewhere in next BD-RB package (under 'Tools' folder like the other utilities) and if it doesn't infringe any copywright so it doesn't have to rely on so flakey / obscure registry things.

My point: One cannot stop using his machine fearing that the next program he installs will comprmise what is already working. A computer generally runs more than one program everyone will agree.

[jdobbs]

@PhilippeB

I recommend that if you want it to work, you start from scratch and completely reinstall Win7. I have no way of knowing what has or has not been modified on your system. There are thousands of others using it on Win7/64 -- including me -- and it simply works as-is. There's obviously something different on your system -- but there's just no way I can put my finger on what it is long distance.

As for including the VC-1 CODEC in the package... that's an extremely tall order, and considering the total of two BD-RB donations I've received in the last month (combined to add up to $27) -- and the fact that I've spend four times that much buying discs in the same period so that I can repeat reported issues -- it isn't likely that I'm going to go any route that adds additional programming time/expense. Frankly it's all I can do in my mind to justify continuing the project at all.

[Jagaer]

I had the same issue as PhilippeB

Manually using the Last Command in a Console, the x264 1st pass encode was just "quitting" almost immediately.

I downloaded another x264 compile with the options BDRB uses from another site and it works fine.

I am not certain if it is because I am running BDRB in VMWare XP, or because my CPU is old (A64 3000+) so certain compiler optimizations are unavailable, like SSE4.

The debug info given by BDRB has always been enough to troubleshoot what is causing the problem. It has never been BDRB itself, but some of the helper programs distributed with it.

[Rob_G]

@PhilippeB

I recommend that if you want it to work, you start from scratch and completely reinstall Win7. I have no way of knowing what has or has not been modified on your system. There are thousands of others using it on Win7/64 -- including me -- and it simply works as-is. There's obviously something different on your system -- but there's just no way I can put my finger on what it is long distance.

As for including the VC-1 CODEC in the package... that's an extremely tall order, and considering the total of two BD-RB donations I've received in the last month (combined to add up to $27) -- and the fact that I've spend four times that much buying discs in the same period so that I can repeat reported issues -- it isn't likely that I'm going to go any route that adds additional programming time/expense. Frankly it's all I can do in my mind to justify continuing the project at all.

Fresh install of XP and I've had the same problems a few others are mentioning. Pass 1 of 'Good Luck Chuck' completes, pass 2 fails. I have tried everything from installing wm11, disabling vc-1 etc and have had no success.

I never had problems with previous versions of bdrebuilder. It may not be a fault of bd rebuilder itself, but one of the other applications it uses.

Rob

[Rob_G]

I had the same issue as PhilippeB

Manually using the Last Command in a Console, the x264 1st pass encode was just "quitting" almost immediately.

I downloaded another x264 compile with the options BDRB uses from another site and it works fine.

I am not certain if it is because I am running BDRB in VMWare XP, or because my CPU is old (A64 3000+) so certain compiler optimizations are unavailable, like SSE4.

The debug info given by BDRB has always been enough to troubleshoot what is causing the problem. It has never been BDRB itself, but some of the helper programs distributed with it.

Interesting. I am running XP in virtualbox myself. I was able to encode lost boys no problem and make it through the first pass of good luck chuck, but it can't start pass 2.

Rob

[jdobbs]

Fresh install of XP and I've had the same problems a few others are mentioning. Pass 1 of 'Good Luck Chuck' completes, pass 2 fails. I have tried everything from installing wm11, disabling vc-1 etc and have had no success.

I never had problems with previous versions of bdrebuilder. It may not be a fault of bd rebuilder itself, but one of the other applications it uses.

Rob Look at the times in the log. It's probably not actually completing Pass 1... it's just not having an error returned.

What version of BD-RB are you using? If it isn't the latest, download v0.32.08 and try again. What you are describing was a known issue on an earlier version that was fixed.

[Rob_G]

I ran the bdrebuilder last command manually from a command prompt and it seems x264 is aborting with an error:

avs [info]: 1920x1080p 1:1 @ 24000/1001 fps (cfr)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2 SSE3 Cache64
x264 [error]: ratecontrol_init: can't open stats file
x264 [error]: x264_encoder_open failed


Could this be a sign that the first pass did not complete correctly? The file is there, but I suppose it may be damaged/truncuated.

Rob

[rendez2k]

I've got the same issue under Win 7 64bit also. BR-Rebuilder gives me no warning or messages about changing settings. Have tried as admin and re-installing codecs and avi synth.

[00:02:32] PHASE ONE, Encoding
- [00:02:32] Extracting A/V streams [VID_00181]
- [00:02:35] Reencoding: VID_00181 (1 of 46)
- [00:02:35] Collecting video information
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 3,485 frames
- [00:02:36] Reencoding: VID_00181, Pass 1 of 1
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- FFDSHOW Revision: (3322)
[00:02:42] - Failed video encode, aborted

[jdobbs]

I ran the bdrebuilder last command manually from a command prompt and it seems x264 is aborting with an error:

avs [info]: 1920x1080p 1:1 @ 24000/1001 fps (cfr)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2 SSE3 Cache64
x264 [error]: ratecontrol_init: can't open stats file
x264 [error]: x264_encoder_open failed


The file is there however.

Rob Read my post above yours. It never really finished pass 1... so there wouldn't be a stats file for pass 2.

[jdobbs]

I've got the same issue under Win 7 64bit also. BR-Rebuilder gives me no warning or messages about changing settings. Have tried as admin and re-installing codecs and avi synth.

[00:02:32] PHASE ONE, Encoding
- [00:02:32] Extracting A/V streams [VID_00181]
- [00:02:35] Reencoding: VID_00181 (1 of 46)
- [00:02:35] Collecting video information
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 3,485 frames
- [00:02:36] Reencoding: VID_00181, Pass 1 of 1
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- FFDSHOW Revision: (3322)
[00:02:42] - Failed video encode, abortedRead the instructions in the first post. Download the versions as it says to do, then try again. You obviously didn't read/comply because your FFDSHOW version is wrong.

Sorry if I sound rude, but this is about the 9000th time I've posted this exact same answer. It fixed 8998 of the previous issues.

[Atak_Snajpera]

FFDSHOW Revision: (3322)
What is wrong in this version? Forcing old revision is not a good idea.

[Rob_G]

Read my post above yours. It never really finished pass 1... so there wouldn't be a stats file for pass 2.

I downloaded bdrebuilder again and cleaned out the temp folder. Pass1 is running right now. I gave the XP virtualbox 2 processors and the ETA to finish this first pass is about 3 hours.



Rob

[jdobbs]

What is wrong in this version? Forcing old revision is not a good idea.Using versions that don't work are an even worse idea. The concept of upgrading simply for the sake of upgrading is silly.

About half the versions released since then have issues of one sort or another that make them stop working with BD-RB. I don't know why -- I just know that going back to that version fixes it. I tell people to stick with one that works or else its just a crapshoot. I'm testing 3326 now, and when I feel comfortable there are no issues I'll recommend it.

[sidneysides]

I am having a little trouble with the fluidity of some scenes. T

I reencoded a Jamiroquai live concert. The original was extremely smooth when panning around the stage. When I watched the reencoded version it was slightly and jerky and blurry during the same panning scenes. The picture itself was fine with regards to sharpness - pretty much the same as the original - it was just during movement. It was a little similar to the old days with CCE when you encoded with the wrong field first, although not anywhere near as bad - I'm just trying to describe it a bit better.

I noticed the same thing happening when I reencoded Monsters Inc, although this time it was during the scrolling on the menu.

I thought that reencoding would not affect the picture in this way, only perhaps slight blockiness or grain.

I tried the Jamiroquai concert full disc and movie only and got the same result - slight motion blur

[rendez2k]

Read the instructions in the first post. Download the versions as it says to do, then try again. You obviously didn't read/comply because your FFDSHOW version is wrong.

Sorry if I sound rude, but this is about the 9000th time I've posted this exact same answer. It fixed 8998 of the previous issues.

No problem and thanks for the reply. I've tried installing the recommended versions and no change though. I am actually beginning to wonder if its the source files although if others are having the same issue?

[lican]

Mr. JOBBY I tried this version fd 3326 everything seems ok perfect video and audio encoding 15:12:29] BD Rebuilder v0.32.08 (beta)
- Source: UNDERWORLD_EXT.CUT_[FULL_BLU-RAY_AVC_1080P_LPCM_5.1]
- Input BD size: 36,25 GB
- Approximate total content: [02:13:37.009]
- Target BD size: 22,90 GB
- Windows Version: 6.1 [7600]
- MOVIE-ONLY mode enabled
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[15:12:29] PHASE ONE, Encoding
- [15:12:29] Extracting A/V streams [VID_00011]
- [15:19:13] Reencoding: VID_00011 (1 of 1)
- [15:19:13] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 192.216 frames
- Bitrate: 17.021 Kbs
- [15:19:13] Reencoding: VID_00011, Pass 1 of 2
- [17:04:20] Reencoding: VID_00011, Pass 2 of 2
- [23:35:06] Video Encode complete
- [23:35:06] Reencoding audio tracks (if req'd)
- [23:35:06] Multiplexing M2TS
[23:43:50]PHASE ONE complete
[23:43:50]PHASE TWO - Rebuild Started
- [23:43:50] Rebuilding BD file Structure
[23:57:31] - Encode and Rebuild complete
[23:57:31] BURNING BD structure to disc
- ImgBurn completed successfully
- WORKFILES folder removed.
[01:19:48]JOB: UNDERWORLD_EXT.CUT_[FULL_BLU-RAY_AVC_1080P_LPCM_5.1] finished.

[Rob_G]

Pass 1 completes, pass 2 fails to start still.

[22:35:44] BD Rebuilder v0.32.08 (beta)
- Source: GOOD_LUCK_CHUCK
- Input BD size: 27.53 GB
- Approximate total content: [01:41:18.113]
- Target BD size: 7.72 GB
- Windows Version: 5.1 [2600]
- MOVIE-ONLY mode enabled
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[22:35:47] PHASE ONE, Encoding
- [22:35:47] Extracting A/V streams [VID_00000]
- [22:49:31] Reencoding: VID_00000 (1 of 1)
- [22:49:31] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 145,729 frames
- Bitrate: 9,315 Kbs
- [22:49:32] Reencoding: VID_00000, Pass 1 of 2
- [02:19:49] Reencoding: VID_00000, Pass 2 of 2
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- FFDSHOW Revision: (3133)
[02:19:56] - Failed video encode, aborted

[ViolentA79]

Ok, so I dual boot Windows 7 64 bit and Win Vista 32 bit.

I backed up New Moon using anydvd and tried to rebuild it. It keeps rebooting my machine so i don't have the log.

I switched to Vista and it almost finished... BUT then it prompts me if I wanted overwrite my files where i have the rip.

If i Click NO, it aborts. If I click YES, it aborts and also deletes everything in my file. Now i have to re-rip it.

-----------------------
[14:03:49] BD Rebuilder v0.32.08 (beta)
- Source: NEW_MOONRIP
- Input BD size: 42.20 GB
- Approximate total content: [03:37:25.382]
- Target BD size: 22.90 GB
- Windows Version: 6.0 [6001]
- One Pass ABR Mode enabled
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[14:03:51] PHASE ONE, Encoding
- [14:03:51] Extracting A/V streams [VID_00552]
- [14:03:51] Reencoding: VID_00552 (1 of 16)
- [14:03:51] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 144 frames
- [14:03:51] Reencoding: VID_00552, Pass 1 of 1
- [14:04:01] Video Encode complete
- [14:04:01] Reencoding audio tracks (if req'd)
- [14:04:01] Multiplexing M2TS
- [14:04:02] Extracting A/V streams [VID_00555]
- [14:04:04] Reencoding: VID_00555 (2 of 16)
- [14:04:04] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 2,786 frames
- [14:04:04] Reencoding: VID_00555, Pass 1 of 1
- [14:04:22] Video Encode complete
- [14:04:22] Reencoding audio tracks (if req'd)
- [14:04:22] Multiplexing M2TS
- [14:04:23] Extracting A/V streams [VID_00553]
- [14:04:29] Reencoding: VID_00553 (3 of 16)
- [14:04:29] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 6,834 frames
- [14:04:29] Reencoding: VID_00553, Pass 1 of 1
- [14:05:09] Video Encode complete
- [14:05:09] Reencoding audio tracks (if req'd)
- [14:05:09] Multiplexing M2TS
- [14:05:10] Extracting A/V streams [VID_00556]
- [14:05:20] Reencoding: VID_00556 (4 of 16)
- [14:05:20] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 6,654 frames
- [14:05:20] Reencoding: VID_00556, Pass 1 of 1
- [14:06:03] Video Encode complete
- [14:06:03] Reencoding audio tracks (if req'd)
- [14:06:03] Multiplexing M2TS
- [14:06:05] Extracting A/V streams [VID_00554]
- [14:06:14] Reencoding: VID_00554 (5 of 16)
- [14:06:14] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 6,804 frames
- [14:06:14] Reencoding: VID_00554, Pass 1 of 1
- [14:06:54] Video Encode complete
- [14:06:54] Reencoding audio tracks (if req'd)
- [14:06:54] Multiplexing M2TS
- [14:06:56] Extracting A/V streams [VID_00042]
- [14:07:05] Reencoding: VID_00042 (6 of 16)
- [14:07:05] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 1,370 frames
- [14:07:05] Reencoding: VID_00042, Pass 1 of 1
- [14:07:37] Video Encode complete
- [14:07:37] Reencoding audio tracks (if req'd)
- [14:07:37] Multiplexing M2TS
- [14:07:39] Extracting A/V streams [VID_00559]
- [14:07:56] Reencoding: VID_00559 (7 of 16)
- [14:07:56] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 3,504 frames
- [14:07:56] Reencoding: VID_00559, Pass 1 of 1
- [14:09:12] Video Encode complete
- [14:09:12] Reencoding audio tracks (if req'd)
- [14:09:12] Multiplexing M2TS
- [14:09:15] Extracting A/V streams [VID_00558]
- [14:09:35] Reencoding: VID_00558 (8 of 16)
- [14:09:35] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 3,648 frames
- [14:09:35] Reencoding: VID_00558, Pass 1 of 1
- [14:10:57] Video Encode complete
- [14:10:57] Reencoding audio tracks (if req'd)
- [14:10:57] Multiplexing M2TS
- [14:11:01] Extracting A/V streams [VID_00557]
- [14:11:20] Reencoding: VID_00557 (9 of 16)
- [14:11:20] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 3,648 frames
- [14:11:20] Reencoding: VID_00557, Pass 1 of 1
- [14:12:42] Video Encode complete
- [14:12:42] Reencoding audio tracks (if req'd)
- [14:12:42] Multiplexing M2TS
- [14:12:46] Extracting A/V streams [VID_00547]
- [14:13:06] Reencoding: VID_00547 (10 of 16)
- [14:13:06] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 5,904 frames
- [14:13:06] Reencoding: VID_00547, Pass 1 of 1
- [14:15:23] Video Encode complete
- [14:15:23] Reencoding audio tracks (if req'd)
- [14:15:23] Multiplexing M2TS
- [14:15:27] Extracting A/V streams [VID_00546]
- [14:15:48] Reencoding: VID_00546 (11 of 16)
- [14:15:48] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 6,480 frames
- [14:15:49] Reencoding: VID_00546, Pass 1 of 1
- [14:18:19] Video Encode complete
- [14:18:19] Reencoding audio tracks (if req'd)
- [14:18:19] Multiplexing M2TS
- [14:18:24] Extracting A/V streams [VID_00548]
- [14:19:02] Reencoding: VID_00548 (12 of 16)
- [14:19:02] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 11,256 frames
- [14:19:02] Reencoding: VID_00548, Pass 1 of 1
- [14:23:12] Video Encode complete
- [14:23:12] Reencoding audio tracks (if req'd)
- [14:23:12] Multiplexing M2TS
- [14:23:22] Extracting A/V streams [VID_00551]
- [14:24:00] Reencoding: VID_00551 (13 of 16)
- [14:24:00] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 11,952 frames
- [14:24:00] Reencoding: VID_00551, Pass 1 of 1
- [14:28:37] Video Encode complete
- [14:28:37] Reencoding audio tracks (if req'd)
- [14:28:37] Multiplexing M2TS
- [14:28:49] Extracting A/V streams [VID_00550]
- [14:29:35] Reencoding: VID_00550 (14 of 16)
- [14:29:35] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 15,072 frames
- [14:29:35] Reencoding: VID_00550, Pass 1 of 1
- [14:35:47] Video Encode complete
- [14:35:47] Reencoding audio tracks (if req'd)
- [14:35:47] Multiplexing M2TS
- [14:36:17] Extracting A/V streams [VID_00549]
- [14:38:43] Reencoding: VID_00549 (15 of 16)
- [14:38:43] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 43,392 frames
- [14:38:43] Reencoding: VID_00549, Pass 1 of 1
- [14:56:14] Video Encode complete
- [14:56:14] Reencoding audio tracks (if req'd)
- [14:56:14] Multiplexing M2TS
- [14:58:06] Extracting A/V streams [VID_00001]
- [15:18:30] Reencoding: VID_00001 (16 of 16)
- [15:18:30] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 187,944 frames
- Bitrate: 12,319 Kbs
- [15:18:30] Reencoding: VID_00001, Pass 1 of 1
- [17:26:40] Video Encode complete
- [17:26:40] Reencoding audio tracks (if req'd)
- [17:26:40] Multiplexing M2TS
[17:35:48]PHASE ONE complete
[17:35:48]PHASE TWO - Rebuild Started
- [17:35:48] Rebuilding BD file Structure
- [17:44:09] RebuildBDFiles() 00006 2203
[17:44:15] - Aborted at user request
-----------------------
[17:44:17] BD Rebuilder v0.32.08 (beta)
- Source: NEW_MOONRIP
- Input BD size: 42.20 GB
- Approximate total content: [03:37:25.382]
- Target BD size: 22.90 GB
- Windows Version: 6.0 [6001]
- One Pass ABR Mode enabled
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[17:44:19] PHASE ONE, Encoding
[17:44:19]PHASE ONE complete
[17:44:19]PHASE TWO - Rebuild Started
- [17:44:19] Rebuilding BD file Structure
- [17:44:21] RebuildBDFiles() 00006 2203
[17:44:22] - Aborted at user request
-----------------------
[17:44:39] BD Rebuilder v0.32.08 (beta)
- Source: NEW_MOONRIP
- Input BD size: 42.20 GB
- Approximate total content: [03:37:25.382]
- Target BD size: 22.90 GB
- Windows Version: 6.0 [6001]
- One Pass ABR Mode enabled
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[17:44:41] PHASE ONE, Encoding
[17:44:41]PHASE ONE complete
[17:44:42]PHASE TWO - Rebuild Started
- [17:44:42] Rebuilding BD file Structure
- [17:44:44] RebuildBDFiles() 00006 2203
[17:44:46] - Aborted at user request

[jdobbs]

Ok, so I dual boot Windows 7 64 bit and Win Vista 32 bit.

I backed up New Moon using anydvd and tried to rebuild it. It keeps rebooting my machine so i don't have the log.

I switched to Vista and it almost finished... BUT then it prompts me if I wanted overwrite my files where i have the rip.

If i Click NO, it aborts. If I click YES, it aborts and also deletes everything in my file. Now i have to re-rip it.Sounds a lot like a bad rip...

[RocKKer]

ViolentA79....sometimes bad memory will cause a spontaneous reboot. Encoding is known to expose hardware issues.

Use memtest86+ to test.

[ViolentA79]

Thanks guys. Jdobbs, I just re-ripped with anydvd. I'm backing up again and will post my results later on. rockker, I'll def. give the memtest a try as well.

JDobbs, should i be changing any settings in anydvd. I just install and keep everything as is.

[Warbucks81]

Ok, so I dual boot Windows 7 64 bit and Win Vista 32 bit.

I backed up New Moon using anydvd and tried to rebuild it. It keeps rebooting my machine so i don't have the log.

I switched to Vista and it almost finished... BUT then it prompts me if I wanted overwrite my files where i have the rip.

If i Click NO, it aborts. If I click YES, it aborts and also deletes everything in my file. Now i have to re-rip it.



Make sure you are using the latest version of anydvd as it was recently updated specifically for the R1 release of new moon.

[setarip_old]

@Warbucks81

Hi!

I believe what you are referring to is regarding a DVD and not the BluRay version...

[ViolentA79]

No, Warbucks81 is absolutely right. The minute i put in New Moon, anydvd told me to get the latest update and would not read the disc otherwise.

[Rob_G]

Pass 1 completes, pass 2 fails to start still.

[22:35:44] BD Rebuilder v0.32.08 (beta)
- Source: GOOD_LUCK_CHUCK
- Input BD size: 27.53 GB
- Approximate total content: [01:41:18.113]
- Target BD size: 7.72 GB
- Windows Version: 5.1 [2600]
- MOVIE-ONLY mode enabled
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[22:35:47] PHASE ONE, Encoding
- [22:35:47] Extracting A/V streams [VID_00000]
- [22:49:31] Reencoding: VID_00000 (1 of 1)
- [22:49:31] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 145,729 frames
- Bitrate: 9,315 Kbs
- [22:49:32] Reencoding: VID_00000, Pass 1 of 2
- [02:19:49] Reencoding: VID_00000, Pass 2 of 2
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
- FFDSHOW Revision: (3133)
[02:19:56] - Failed video encode, aborted

I'm rebuilding Pink Panther 2 ar the moment. No problems starting pass 2. I guess BD Rebuilder just doesn't like my Good Luck Chuck...

Rob

[setarip_old]

@ViolentA79

First you said: I backed up New Moon using anydvd and tried to rebuild it. It keeps rebooting my machine so i don't have the log.

I switched to Vista and it almost finished... BUT then it prompts me if I wanted overwrite my files where i have the rip.

Now you say: The minute i put in New Moon, anydvd told me to get the latest update and would not read the disc otherwise.These appear to be direct contradictions.

Would you please be good enough to clarify this for me (so I know what to expect should I purchase "New Moon")?

Thanks.

[ViolentA79]

OK... to clarify. When i first put New Moon into my drive it told me to update anydvd. I updated it and had no problem ripping it.

Once ripped i tried to use BD Rebuilder to do a BD-25

When i did it in Windows 7 64 bit my computer kept rebooting.

Next i tried vista 32 bit and it got to 100% then prompted me to overwrite my files and never finished.

I'm waiting for my next go-around to finish and i will post the log when completed.

[ViolentA79]

Seems that this time we had success...

-----------------------
[20:26:34] BD Rebuilder v0.32.08 (beta)
- Source: NEW_MOON
- Input BD size: 42.20 GB
- Approximate total content: [03:37:25.382]
- Target BD size: 22.90 GB
- Windows Version: 6.0 [6001]
- One Pass ABR Mode enabled
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[20:26:37] PHASE ONE, Encoding
- [20:26:37] Extracting A/V streams [VID_00552]
- [20:26:37] Reencoding: VID_00552 (1 of 16)
- [20:26:37] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 144 frames
- [20:26:37] Reencoding: VID_00552, Pass 1 of 1
- [20:26:41] Video Encode complete
- [20:26:41] Reencoding audio tracks (if req'd)
- [20:26:41] Multiplexing M2TS
- [20:26:41] Extracting A/V streams [VID_00555]
- [20:26:45] Reencoding: VID_00555 (2 of 16)
- [20:26:45] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 2,786 frames
- [20:26:45] Reencoding: VID_00555, Pass 1 of 1
- [20:27:03] Video Encode complete
- [20:27:03] Reencoding audio tracks (if req'd)
- [20:27:03] Multiplexing M2TS
- [20:27:04] Extracting A/V streams [VID_00553]
- [20:27:11] Reencoding: VID_00553 (3 of 16)
- [20:27:11] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 6,834 frames
- [20:27:11] Reencoding: VID_00553, Pass 1 of 1
- [20:27:52] Video Encode complete
- [20:27:52] Reencoding audio tracks (if req'd)
- [20:27:52] Multiplexing M2TS
- [20:27:54] Extracting A/V streams [VID_00556]
- [20:28:03] Reencoding: VID_00556 (4 of 16)
- [20:28:03] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 6,654 frames
- [20:28:03] Reencoding: VID_00556, Pass 1 of 1
- [20:28:48] Video Encode complete
- [20:28:48] Reencoding audio tracks (if req'd)
- [20:28:48] Multiplexing M2TS
- [20:28:51] Extracting A/V streams [VID_00554]
- [20:28:59] Reencoding: VID_00554 (5 of 16)
- [20:28:59] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 6,804 frames
- [20:28:59] Reencoding: VID_00554, Pass 1 of 1
- [20:29:44] Video Encode complete
- [20:29:44] Reencoding audio tracks (if req'd)
- [20:29:44] Multiplexing M2TS
- [20:29:45] Extracting A/V streams [VID_00042]
- [20:29:54] Reencoding: VID_00042 (6 of 16)
- [20:29:54] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 1,370 frames
- [20:29:54] Reencoding: VID_00042, Pass 1 of 1
- [20:30:28] Video Encode complete
- [20:30:28] Reencoding audio tracks (if req'd)
- [20:30:28] Multiplexing M2TS
- [20:30:31] Extracting A/V streams [VID_00559]
- [20:30:48] Reencoding: VID_00559 (7 of 16)
- [20:30:48] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 3,504 frames
- [20:30:48] Reencoding: VID_00559, Pass 1 of 1
- [20:32:09] Video Encode complete
- [20:32:09] Reencoding audio tracks (if req'd)
- [20:32:09] Multiplexing M2TS
- [20:32:15] Extracting A/V streams [VID_00558]
- [20:32:33] Reencoding: VID_00558 (8 of 16)
- [20:32:33] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 3,648 frames
- [20:32:33] Reencoding: VID_00558, Pass 1 of 1
- [20:33:57] Video Encode complete
- [20:33:57] Reencoding audio tracks (if req'd)
- [20:33:57] Multiplexing M2TS
- [20:34:07] Extracting A/V streams [VID_00557]
- [20:34:26] Reencoding: VID_00557 (9 of 16)
- [20:34:26] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 3,648 frames
- [20:34:26] Reencoding: VID_00557, Pass 1 of 1
- [20:35:50] Video Encode complete
- [20:35:50] Reencoding audio tracks (if req'd)
- [20:35:50] Multiplexing M2TS
- [20:35:57] Extracting A/V streams [VID_00547]
- [20:36:20] Reencoding: VID_00547 (10 of 16)
- [20:36:20] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 5,904 frames
- [20:36:20] Reencoding: VID_00547, Pass 1 of 1
- [20:38:41] Video Encode complete
- [20:38:41] Reencoding audio tracks (if req'd)
- [20:38:41] Multiplexing M2TS
- [20:38:52] Extracting A/V streams [VID_00546]
- [20:39:17] Reencoding: VID_00546 (11 of 16)
- [20:39:17] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 6,480 frames
- [20:39:17] Reencoding: VID_00546, Pass 1 of 1
- [20:41:50] Video Encode complete
- [20:41:50] Reencoding audio tracks (if req'd)
- [20:41:50] Multiplexing M2TS
- [20:42:03] Extracting A/V streams [VID_00548]
- [20:42:43] Reencoding: VID_00548 (12 of 16)
- [20:42:43] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 11,256 frames
- [20:42:43] Reencoding: VID_00548, Pass 1 of 1
- [20:46:59] Video Encode complete
- [20:46:59] Reencoding audio tracks (if req'd)
- [20:46:59] Multiplexing M2TS
- [20:47:20] Extracting A/V streams [VID_00551]
- [20:48:02] Reencoding: VID_00551 (13 of 16)
- [20:48:02] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 11,952 frames
- [20:48:03] Reencoding: VID_00551, Pass 1 of 1
- [20:52:36] Video Encode complete
- [20:52:36] Reencoding audio tracks (if req'd)
- [20:52:36] Multiplexing M2TS
- [20:52:57] Extracting A/V streams [VID_00550]
- [20:53:51] Reencoding: VID_00550 (14 of 16)
- [20:53:51] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 15,072 frames
- [20:53:51] Reencoding: VID_00550, Pass 1 of 1
- [20:59:57] Video Encode complete
- [20:59:57] Reencoding audio tracks (if req'd)
- [20:59:57] Multiplexing M2TS
- [21:00:27] Extracting A/V streams [VID_00549]
- [21:03:10] Reencoding: VID_00549 (15 of 16)
- [21:03:10] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 43,392 frames
- [21:03:11] Reencoding: VID_00549, Pass 1 of 1
- [21:21:08] Video Encode complete
- [21:21:08] Reencoding audio tracks (if req'd)
- [21:21:08] Multiplexing M2TS
- [21:22:59] Extracting A/V streams [VID_00001]
- [21:43:10] Reencoding: VID_00001 (16 of 16)
- [21:43:10] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 187,944 frames
- Bitrate: 12,319 Kbs
- [21:43:10] Reencoding: VID_00001, Pass 1 of 1
- [23:55:16] Video Encode complete
- [23:55:16] Reencoding audio tracks (if req'd)
- [23:55:16] Multiplexing M2TS
[00:04:05]PHASE ONE complete
[00:04:05]PHASE TWO - Rebuild Started
- [00:04:05] Rebuilding BD file Structure
[00:04:12] - Encode and Rebuild complete
[00:04:12] BURNING BD structure to disc
- ImgBurn completed successfully
[00:52:31]JOB: NEW_MOON finished.

[Nerz]

Are the any system requirements for re-encoding? not necessarily for the time it takes to complete, but for success? I noticed someone stated they had a amd 64 3000+ processor. Which is what I'm trying on. I'm just wondering if this could be the problem, before I do a complete restore which might change remove any settings that might be causing any failures with my system

[nurbs]

No minimum requirements. You could encode on a pentium II if you didn't mind waiting a couple of weeks for the encode to finish. IIRC the CPU needs MMX for x264 to work, but nothing more apart form that.

[Dark Shikari]

No minimum requirements. You could encode on a pentium II if you didn't mind waiting a couple of weeks for the encode to finish. IIRC the CPU needs MMX for x264 to work, but nothing more apart form that.Pentium 3 or later (for Intel) or Athlon XP or later (for AMD), actually. We upped the default requirement to SSE a while back and nobody seems to have noticed, so I doubt anyone is still using older chips ;)

[Jagaer]

Pentium 3 or later (for Intel) or Athlon XP or later (for AMD), actually. We upped the default requirement to SSE a while back and nobody seems to have noticed, so I doubt anyone is still using older chips ;)

Not certain if you mean the x264 distributed with BDRB or source hardware requirements, but I may have noticed...http://forum.doom9.org/showthread.php?p=1384631#post1384631

[Capsbackup]

I have now experienced, on three different full movie backups to BD9, on both software players and my Sony S360, that after the movie completes and returns to the main menu, the menu backround/picture is only a black screen while the selectable buttons are visible. Everything works properly, and when the disc is first inserted and starts, the proper main menu is displayed. Only after the conclusion of the movie and the return to the main menu is this black screen with only the button selections present. :confused:

[jdobbs]

I have now experienced, on three different full movie backups to BD9, on both software players and my Sony S360, that after the movie completes and returns to the main menu, the menu backround/picture is only a black screen while the selectable buttons are visible. Everything works properly, and when the disc is first inserted and starts, the proper main menu is displayed. Only after the conclusion of the movie and the return to the main menu is this black screen with only the button selections present. :confused: I'll look at it. Can you give me an example disc and settings? Also -- is it a java supported disc (are the JAR files)?

[jdobbs]

Not certain if you mean the x264 distributed with BDRB or source hardware requirements, but I may have noticed...http://forum.doom9.org/showthread.php?p=1384631#post1384631I think in the link you referenced the command is "quiting almost immediately" because the command line is trying to do a second pass -- and there is no .stats file. You'd have to go back and reattempt the first pass in order to find out what was really the issue. One recommendation in that circumstance would be to change "--pass 2" to "--pass 1" on the command line and see what happens. Historically BD-RB reported X264 issues have almost always been linked back to CODEC problems rather than X264 itself.

Dark Shikari's comments would always apply to the version included with BD-RB... I think that if you went back to one of the processors that aren't supported you'd probably still be waiting for your first blu-ray backup to complete.

[deank]

Pentium 3 or later (for Intel) or Athlon XP or later (for AMD), actually. We upped the default requirement to SSE a while back and nobody seems to have noticed, so I doubt anyone is still using older chips ;)

I noticed that, because I was using a really old Celeron machine with 128MB RAM for tests and at one point x264 refused to work with ASM-something message. I asked one of the guys who put 20 patched builds per day to compile one without the new-requirement... He never answered back. Then the power-box of that old PC blew-up :)... Fate.

Dean

[brogan]

I always follow instructions and yes, i learned to read at school. Appreciate your concerns but condescendence will not fix my bug. Maybe let me feel a little bit more guilty of asking for help but definitly not fixing my problem.

Meanwhile, if you understood my problem was fixed it is not - even with the keys correctly setted as posted, it is still not working... I posted a log just above that shows that and i am re-posting it here:


-----------------------
[16:36:10] BD Rebuilder v0.32.08 (beta)
- Source: THE_MUMMY
- Input BD size: 29,42 GB
- Approximate total content: [02:04:53.235]
- Target BD size: 23,93 GB
- Windows Version: 6.1 [7600]
- MOVIE-ONLY mode enabled
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[16:36:12] PHASE ONE, Encoding
- [16:36:12] Reencoding: VID_00000 (1 of 1)
- [16:36:12] Collecting video information
- Source Video: VC-1, 1920x1080
- Rate/Length: 23,976fps, 179*658 frames
- Bitrate: 19*550 Kbs
- [16:36:12] Reencoding: VID_00000, Pass 1 of 2
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting. <- Observe that there is no complain anymore about VC-1 or MPEG2 not being correctly setted up for FFDSHOW
- FFDSHOW Revision: (3133)
[16:36:13] - Failed video encode, aborted

---------------------------------------------

BD-RB is probably doing its job but the codec seems to be innaccessible. Why can it BD-RB access AVC or H264, but not VC1 ? Answering that question would probably fix the problem.
I'll probably have to re-install Windows 7 (again) ... Expecting things won't stop working at the first new program install.

Maybe one solution would be to include the VC-1 codec somewhere in next BD-RB package (under 'Tools' folder like the other utilities) and if it doesn't infringe any copywright so it doesn't have to rely on so flakey / obscure registry things.

My point: One cannot stop using his machine fearing that the next program he installs will comprmise what is already working. A computer generally runs more than one program everyone will agree.

Hey Philippe,

Did you ever get this sorted? I'm having the exact same problem right after a clean install of Windows 7 Ultimate x64...