View Full Version : Are there any issues with BD-Rebuilder and i7s
jellyhead1
19th January 2011, 02:00
This is the problem I'm having. I had a Core 2 Duo E6600 CPU which I upgraded to a Q6600. I did change any software at all. Everything worked the same as with the dual core CPU except for cutting about 3 hrs from the encoding time. I Then upgraded my motehrboard, CPU and RAM to an Asus Sabertooth X58 with an i7 950 and 12GB DDR3 (3x4GB) PC12800 1600MHz Patriot RAM. I only removed/uninstall hardware from device manager before upgrading. I started up with the new hardware and installed all the drivers. This was all done within 1 months time so I know there has been no changes to the software on my system. Everything is working fine except now I've been getting random encoding errors and the reencode fails. I've tried 4 movies and 2 have failed. One was Terminator Salvation DC, the other was Universal Soldier. Before I continue trying to track down what is causing the errors, I wanted to make sure there was no issue with BD Rebuilder and the i7 CPUs or the intel x58 chipset. When it has worked, the encoding ti for BD50 to BD25 is about 1.5 hrs. with the E6600 it was 5-6 hrs.
Another thing I noticed is that the ffmpeg encoder has always been greyed out even before I bagan having problems, is this normal?
Capsbackup
19th January 2011, 02:07
No problem with my i7 920.
Are you overclocked?
Do you have adequate cooling?
jellyhead1
19th January 2011, 02:40
I was overclocked with an upgraded cooler. The first this I did was go back to stock settings but I still got the error. I didn't have the recommended versions of ffdshow or Matroska Splitter installed but I never did and it worked fine on about 20 movies. I have since installed the recommended versions but it didn't help and tried to set the options as instructed. I am a little unsure about some of the options such as, VC-1 has 2 options when enabling it, libavcodec and wmv9, I chose wmv9. Also there is a start menu folder for ffdshow and ffdshow x64. I opened both and enabled to options but there was only 1 option in the x64 version. before upgrading and having these problems, I had the current version of windows 7 codec pack installed and never had any encoding problems with BD Rebuilder.
jdobbs
19th January 2011, 03:24
Make sure you are using the recommended versions of the helper apps. I can tell you from experience that a wrong version of HAALI will very definitely cause random encoding errors.
jdobbs
19th January 2011, 03:27
I was overclocked with an upgraded cooler. The first this I did was go back to stock settings but I still got the error. I didn't have the recommended versions of ffdshow or Matroska Splitter installed but I never did and it worked fine on about 20 movies. I have since installed the recommended versions but it didn't help and tried to set the options as instructed. I am a little unsure about some of the options such as, VC-1 has 2 options when enabling it, libavcodec and wmv9, I chose wmv9. Also there is a start menu folder for ffdshow and ffdshow x64. I opened both and enabled to options but there was only 1 option in the x64 version. before upgrading and having these problems, I had the current version of windows 7 codec pack installed and never had any encoding problems with BD Rebuilder. How can you say you are using the recommended versions in one sentence, and then say you are using the 64 bit versions in another?
Your problem is that you don't (or won't) follow directions. Uninstall your software (ALL OF IT) and install only from the links in the first post of the bug thread -- and it will work. Don't install both 64 bit and 32 bit versions. You're installing 64 bit apps that conflict with other apps.
jellyhead1
20th January 2011, 01:39
It seems the problem was that the video was VC-1. I thought I had already used BD Rebuilder on some movies that were VC-1 but maybe not. I did read the instructions in this thread
http://forum.doom9.org/showthread.php?t=143716
but there is no mention of enabling VC-1 decoding. after reading the readme file included with the download I saw that I needed to enabled this. I also removed ffdshow completely and installed only the recommended version. I tried Terminator Salvation DC again an it was able to complete without errors. I found however that the resulting BD25 played about 20 minutes before the video froze and the sound continued playing. I checked the m2ts file and it is undersized at 11.8 gbs.
jdobbs
20th January 2011, 01:55
It seems the problem was that the video was VC-1. I thought I had already used BD Rebuilder on some movies that were VC-1 but maybe not. I did read the instructions in this thread
http://forum.doom9.org/showthread.php?t=143716
but there is no mention of enabling VC-1 decoding. after reading the readme file included with the download I saw that I needed to enabled this. I also removed ffdshow completely and installed only the recommended version. I tried Terminator Salvation DC again an it was able to complete without errors. I found however that the resulting BD25 played about 20 minutes before the video froze and the sound continued playing. I checked the m2ts file and it is undersized at 11.8 gbs. Really? What about this line from that very same link:
8. Recommended for Windows XP only: Download and install WMV11 from Microsoft, and set VC-1 decoding to "disabled" in FFDSHOW (allowing the WMV11 codec to be used). This seems to be the codec with the fewest problem on VC-1. For Vista or Windows 7 -- select "wmv9"
If you want it to work -- follow the directions. All of them. I'd be willing to bet that you either have another package that is interfering (CODEC packs perhaps) or you're using the wrong version of one of the software packages.
jellyhead1
20th January 2011, 02:53
I initially didn't change the VC-1 option because 8. starts with for XP only. After reading another topic regarding this I read again more carefully.
I'm not trying to argue with you or complain about BD Rebuilder at all, I think it's a great app. I started this topic because I wanted to make sure it wasn't hardware related before I started changing software configuration. It was just odd that I never had any errors before installing the new hardware. Apparently none of the movies I've done so far were VC-1.
As far as other codec packs causing the problem, I had thought of that so I tried the same movie on another PC with a fresh setup of Windows 7 x64 running my old Core 2 Q6600. I only installed the recommended apps/versions and no other editing apps or codecs at all. I tried movie only and full disc The result were the exact same so It must have to do with the video itself.
Thanks for your help
jellyhead1
21st January 2011, 03:53
Ok, I found the problem with the freezing video. I've actually had this happen before and it's caused by a distortion (not really sure of the technical term for it) in the original video which looks like it pixelizes for a second. For some reason this causes BD Rebuilder to stop the video at this point but the audio continues. The original video plays through the distorted section but not the re-encoded video. Guess that's what I get for not obtaining the BRs by legitimate means.
jdobbs
21st January 2011, 04:06
Ok, I found the problem with the freezing video. I've actually had this happen before and it's caused by a distortion (not really sure of the technical term for it) in the original video which looks like it pixelizes for a second. For some reason this causes BD Rebuilder to stop the video at this point but the audio continues. The original video plays through the distorted section but not the re-encoded video. Guess that's what I get for not obtaining the BRs by legitimate means. Please review Rule 6...
Actually I'm surprised it didn't crash trying to decode/encode it.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.