Quote:
Originally Posted by jdobbs
Your post isn't making any sense. You're telling me that somehow the codecs are affecting the extract when in fact the two are completely unrelated. Then you tell me that you get an error when you try to run REG_MSCOMCTL... and I can't see why you are even running it since you only need to if you get an error saying "MSCOMCTL isn't installed". The error is probably telling you it won't register it because it's already registered. Last you tell me that installing the Shark007 codecs somehow miraculously makes the audio extract go faster... even though the extract is done by TSMUXER and never references the codecs in any manner whatsoever (and hardly uses any CPU).
In other words... huh????
I think you are confused. Something else is going on with your computer.
|
What dont you understand?
With Shark007 the a/v extract goes very fast if it starts at all. Most of the time it will just popup an x264 error. The exact error I have to retrieve when I get home. Why did I tell you this? I don't know, because I thought the more information I give the better someone could help me. I have absolutely no idea why Shark007 would allow BD Rebuilder to extract the a/v quicker but it does for me. I can't use it though because of the x264 error I receive.
When I uninstall Shark007 and just install the recommended software at the beginning of this page the a/v extract goes extremely slow, taking probably 2 hours to extract and only using 1-15% of my CPU the whole time. I didn't know if this is supposed to be a CPU intensive process or what software it uses, I just know that it seems to take unreasonably long based on what others are saying on here.
Once it is done extracting the a/v it begins to encode or decode (whichever it is) but spits back a very basic error, again I have to retreive this info when I get home. It basically just says something like the error is ffdshow (3133). If I install a different version of ffdshow it gives the exact same error but changes the version number of course.
You say that it just uses tsmuxer, is this built in or is it your own version? I ask because using the stand alone tsmuxer it is very fast for me, often taking about 30min. Using Ripbot it demuxes files in about the same amount of time.
I can't say for certain there isn't a problem with my system but the only issue I appear to be having is with BD Rebuilder or one of the required pieces of software it uses.
Why did I run the REG_MSCOMCTL? Because searching through this page one user suggested to another that it be done and since I was uninstalling everything and starting from scratch I thought I should too.
Quote:
Originally Posted by Capsbackup
@mochevolete;
Try this:
uninstall your ffdshow, haali and avisynth. Reboot. Download the supported ones at the first page of this bug report thread. Install them.
Then unzip a fresh new BD-RB, right click on "REG_MSCOMCTL.BAT" and select run it as administrator."
Then, if that does not work, right click on BD_Rebuilder.EXE and select "Run as Administrator" .
You should be ready to go.
|