View Full Version : Error 0006 starting REBUILD.
apfraats
8th January 2005, 12:45
Has my computer done a 20 hour encoding fase, without problems, now
I got the error 0006: DVD-RB has found an inconsistency in the source data between the prepare and rebuild phase, aborting.
Anyone ?
(Slowly but surely, DVDSHRINK is comming back into my mind !)
jdobbs
8th January 2005, 12:49
Use it. Enjoy the blocks, pixelation, and other artifacts.
Do you really think wise-ass remarks about changing to another encoder is going to somehow get a better response on a freeware program?
Give me a break.
apfraats
8th January 2005, 13:20
I WAS using DVDSHRINK and searh for a better option.
In place of this irrelevant response better answer the question about
the error 0006 I got.
Have a lot more on these responses.
thx anyway
Toine
jdobbs
8th January 2005, 13:53
Error 0006 is an indicator that the framecount for a section during REBUILD doesn't match that found in PREPARE. The data is corrupt. The most common (almost exclusive) source of the error is an accidentally aborted encode (hitting the "Cancel" button while CCE is encoding.
In other words: you probably caused it.
You could either redo the encode, or if you understand CCE a little you can identify the corrupt file, copy the .ECL data from REBUILDER.ECL into ITEM.ECL (replacing what is there), and encode that .ECL as a project in CCE (just the offending section). After you are done, REBUILD (in three click mode).
A better tact in the future toward getting an answer might be to keep your questions and remarks relevent -- and lose the "jerk" attitude.
apfraats
9th January 2005, 15:54
ok, I never will mention DVDSHRINK again.
It was my dissatisfaction with the movie I compiled that forced me to search for an alternative and so I found it with DVDREBUILDER.
By the way I didn't interrupt the proces, as far I know.
But the strange thing is, that I switched back to Quenc 54 instead of 59A and got no errors anymore, but disabled all quality options this time !
I'm now burning my first RW with my difficult movie !!
Thx for answering, just a starter on DVDRB and I'm glad for the alternative for DVDSHRINK.
But let first see the results !
Toine
jdobbs
9th January 2005, 16:26
I just read a tread that I think mentioned frame loss with QuEnc 0.59 -- but I can't remember where..
Mention DVD Shrink all you want. It is a very good product written by a very smart guy... I use it for lots of functions -- just not reencoding DVDs. I am very quality conscious -- if I didn't care about quality I'd use VHS to make backups.
jdobbs
9th January 2005, 17:10
Somewhere I'd mentioned .58 as the last stable version -- actually what I'd intended to say was .57... I've done a lot of testing with that version and it works well.
goat67
14th January 2005, 13:10
I also had this error.
0006: DVD-RB has found an inconsistency in the source data between the prepare and rebuild phase, aborting.
I am using DVD Rebuilder .69 and the error was recieved with QuEnc version .59a
I left all settings on default in DVD Rebuilder since I figure the programmer knows what a good default is.... :D
I tried multiple movies and recieved this error consistently at the start of the rebuild phase.
So I went to QuEnc version .54 and I got my first complete pass with DVD Rebuilder. :)
By saying I went to the .54 version a just renamed the .59 version and placed the .54 version in the same dir so I can go back and forth between these without a problem.
I am posting this to let people know and also I am open for suggests on what I could be doing wrong.
I have tried to find a history of version info for QuEnc but have not had any luck. So I do not know if version .54 is good or if there is a better version to use. I could only find the .59a or the .54 version nothing in between.
Is there a place that the previous versions of QuEnc exist?
PS
DVD Rebuilder is a cool program I like the flexibility it allows and the quality of the Output is awesome
jdobbs
14th January 2005, 13:45
As I mentioned above, stick with 0.57 until the bugs are worked out of .59 -- unless of course you are purposely attempting to identify problems for the QuEnc version.
But... if you are trying to look for DVD-RB bugs, please use 0.57 (actually as I recall .54 was a good one too, but I'm not positive)-- as with the newer version it becomes difficult to decide where the source of the problem might truly be (DVD-RB is also in testing) or QuEnc.
goat67
14th January 2005, 13:59
Thanks for the quick response.
I would use the 57 version if I could find it. :(
If you would want any help or info on the problem with the 59a version of QuEnc and DVD RB please let me know what I can do to help you. As I said I can run either very easily.
On this subject would it help if I created a test image consisting of 30 seconds of each chapter I also use DVDReMakePro and It will do this I then could run the two thru QuEnc and DVDRB and see what happens?
What do you think?
Trahald
14th January 2005, 14:55
I think jdobbs is saying if you intend to use quenc 59a then it would only be for helping the quenc project. if 59a is producing a stream that is inconsistant with the source then there is nothing in rb to fix :/ .. as far as .57 .. im sure Nic (if hes listening) can provide a link to it.
Rockas
14th January 2005, 15:02
QuEnc 0.57 is available to download on www.dvdrebuilder.com
keep it UP
goat67
14th January 2005, 15:19
Thanks Rockas
I am doing some tests, I am right now doing a test for a baseline using .54 version of QuEnc and DVD Rebuilder .69 (Beta)
I used dvdremakepro to get 60 seconds from all chapters of the Matrix
I will run this same source using QuEnc .54 then .57 and finally .59a
I will post the rebuilder.log file and output / working folder information for tests. Anything else you would like we to save for each test?
M7S
19th January 2005, 16:25
I got error #6 when I used quenc 0.59 so I downgraded to 0.57 and did the whole transcoding again. I still got the same error. What now? I'm using avisynth 2.54 and dgdecode.dll. Have I forgot some information? The movie is Terminator 3 if that makes any difference at all.
Regards,
M7S
jdobbs
20th January 2005, 01:51
I just did 4 full encodes of "Rundown" as a test overnight.
CCE v2.50: Success
QuEnc v0.54: Success
QuEnc v0.57: Success
QuEnc v0.59: Error 006 and an ungraceful exit
I'll run it again and do some analysis of the QuEnc output to see if I can put my finger on the problem.
nathanaa
10th February 2005, 14:28
After about 16 hours of attempting to process disc one of Yes, Minister I got this 0006 error. Apparently the QuEnc version DVD-RB Installer loaded is 1.0.0.1 - should I try to go back to a previous version of QuEnc? I have DVD-RB v.70 and AVISynth 2.5.5.0.
Mmm, might be relevant - when I tried using ReJig (v0.3.0.0) to process this disc first, DVD-RB worked, but when I went to burn the backup Nero gave me a message about the DVD source files were out of standard and might not work/play properly (I can't remember the exact wording, sorry). That's why I tried QuEnc....and ended up here now.
Any input greatly appreciated, thanks - I hope I'm providing enough info for you folks!
EDIT: Just realized some more info might be helpful - I used DVDDecrypter v3.5.2.0 to rip the entire disc, in File mode, to an external HDD. I have DVD-RB working on the internal drive but getting the source material from the external HDD and outputting to the HDD.
M7S
10th February 2005, 15:28
I got things working after I choosed "nomux" in quenc 0.57 before encoding. Quenc 0.59beta2 works aswell when I'm using noaudio.
nathanaa
10th February 2005, 20:39
I have QuEnc v1.0.0.1 - what would choosing this "nomux" option do for me, would you say?
Or should I try an earlier version of QuEnc?
pg55555
10th February 2005, 21:00
nathanaa
There is not QuEnc v1.0.0.1.
RB returns wrong version numbers in the Help\Disply Versions when it does not know how to get the version numbers of certain software.
To know what version of QuEnc are you using, just run QuEnc.exe (double click from Windows Explorer)and look (is in the top of the QuEnc windows)
nathanaa
10th February 2005, 21:07
I *thought* that sounded pretty damn odd, having only ever seen versions in the ~.5x range. Pray tell why would it read out the way it does? Just can't find the right number or something, eh?
I have v.56 [ALPHA]. So, what does that mean as regards all this, do you think?
jdobbs
10th February 2005, 21:25
Originally posted by pg55555
nathanaa
RB returns wrong version numbers in the Help\Disply Versions when it does not know how to get the version numbers of certain software. Ehh??? RB reports what the application reports. If it says 1.0.0.1 -- that means that is what the application reports to the operating system.
nathanaa
10th February 2005, 22:11
Originally posted by jdobbs
Ehh??? RB reports what the application reports. If it says 1.0.0.1 -- that means that is what the application reports to the operating system.
Ok, my bad for misstating what I meant - so why does the application report some goofy number then? I suppose it's not really relevant (and I know you have no control over how or why it would do such a thing), I'm just curious, as I do *want* to understand as best I can how/why these programs do these things.
I'll never be a wunderkind at video editing/programming stuff like you guys, but it would be great to not sound like a complete moron all the time! <grin>
Back to what I asked earlier though - would changing to a different version of QuEnc (v.57 maybe?) be a good idea? Or should I be getting decent performance with what I have? This 0006 error is, for me, still not resolved yet. At least, I don't think it is.....I haven't tried running the process again yet (plan to do so later tonight).
Any tips/ideas appreciated, thanks all.
jdobbs
10th February 2005, 22:48
You may want to go into the D2VAVS directory and make sure no .M2V files are missing or are way too short.
pg55555
11th February 2005, 00:02
Ehh??? RB reports what the application reports. If it says 1.0.0.1 -- that means that is what the application reports to the operating system.
jdobbs
I was not implying it was RB fault to be reporting a wrong QuEnc version, just that the version number nathanaa was reporting was wrong.
In a previous thread, when something similar about the QuEnc version arised, you indicated that RB could not report the version number because QuEnc was not including version numbers.I just run QuEnc and found a version number at the top of the window.
Now, if QuEnc informs the version to the operating system I have not idea. Or if the number it reports to the place where RB looks for version numbers is that 1.0.0.1, I have not idea eihter. But that 1.0.0.1 is not the version number of the QuEnc we are talking about I'm sure.
I'm at work now, but I have just pointed RB setup to a copy of QuEnc 0.59 (ALPHA) I have in this machine, and the Help/Display Versions shows: QuEnc Version: v1.0.0.1
nathanaa
I would say that cahnging to v0.57 or 0.54 would not hurt.
nathanaa
11th February 2005, 00:08
Originally posted by jdobbs
You may want to go into the D2VAVS directory and make sure no .M2V files are missing or are way too short.
Ummm.....for this clueless dude, how would I know if there were missing .M2V files? Are there supposed to be a fixed number of them? Or how would I be able to tell if they were way too short? Is there an approximate size they should be that I should look for? Ack, I can always do a forum search too and see if there is more info on these points.
I always use the 1-Click option, so I've never looked at these thigns before.
I think I shall try QuEnc v.54, I still have that from before I used the DVD-RB Installer. Or I can look for the v.57 if that doesn't work.
Or, if there are any other points of advice, I'd be glad to hear them.
jdobbs
11th February 2005, 00:08
@pg55555
Understand. The text at the top of the window isn't really the "Version Number" it's just a caption. Try right clicking on the file in Explorer and select "Properties" -- you'll see that the Operating System also sees it as "1.0.0.1" also -- I do know that DragonGodz added it and it was correctly reported in v0.54 -- and I mentioned it to Nic and he indicated he would add the version number in future versions. The "1.0.0.1" is probably the value that the C compiler puts in by default.
I can't really talk, though. I forget to update mine all the time. If you look at DVD-RB version 0.74 with Explorer it will say 0.73.
nathanaa
20th February 2005, 07:57
I've now gotten this Error 0006 with QuEnc v54, v56, and v59b2. I just replaced 59b2 with v57, and am hoping it will finally work. I've tried several different titles, so it is not just one bad source file.
What does the "nomux" option change? If I turn it off (like the previous poster) what will that result in? I have no idea if I should try it or not. But, at ~10 hours per try, I'm getting very frustrated that I cannot get this to work. I have now spent a total accumulation of DAYS trying to get this combination (RB+QuEnc) to function, with NO success AT ALL.
I would greatly appreciate some advice from anyone on what either I am doing wrong, or what is wrong with my set up, or what the program is having fits with, or anything else it might possibly be.
jdobbs
20th February 2005, 11:44
1. Use QuEnc v0.54. It seems to avoid all problems.
2. Make sure you use no DGDECODE version above 1.1.0 -- they won't work correctly.
3. If you use QuEnc v0.54 the muxing code was not implemented in that version.
Are you getting any other problems -- like freezing during encodes or find yourself needing to restart? You wouldn't be using a computer that is overclocked by any chance?
Plutox
20th February 2005, 13:24
Originally posted by jdobbs
Make sure you use no DGDECODE version above 1.1.0 -- they won't work correctly.
As a matter of interest, what is going wrong with DGDECODE post 1.1.0 that is causing the red letter warnings?
jdobbs
20th February 2005, 13:52
I don't believe it is anything that affects DVD-RB, as I've done numerous DVDs using it. I assume the newer versions are adding lots of bells and whistles that aren't needed by DVD-RB.
Of course there is always the old reliable MPEG2DEC3DG.DLL. It has been solid as a rock for almost a year and a half.
I think I may start including the most recent fully tested .DLL in the rebuilder zip file. I'll have to check and see what the GNU rules will allow me to do.
dragongodz
20th February 2005, 14:15
1. Use QuEnc v0.54. It seems to avoid all problems.
and if using a Pentium 4 cpu then download and use the memaligned avcodec.
guess its a good thing i havent bothered to delete these yet. :)
I think I may start including the most recent fully tested .DLL in the rebuilder zip file. I'll have to check and see what the GNU rules will allow me to do.
without looking, you have to provide atleast a link to the source code so people can download that aswell if they wish.
jdobbs
20th February 2005, 14:24
I'm pretty sure v0.57 is good as well, but I know v0.54 is -- I'm doing some more testing. The newer versions seem to be undersizing the output quite a bit.
nathanaa
20th February 2005, 20:31
Originally posted by jdobbs
1. Use QuEnc v0.54. It seems to avoid all problems.
2. Make sure you use no DGDECODE version above 1.1.0 -- they won't work correctly.
3. If you use QuEnc v0.54 the muxing code was not implemented in that version.
Are you getting any other problems -- like freezing during encodes or find yourself needing to restart? You wouldn't be using a computer that is overclocked by any chance?
A1. I have it, and tried it, and it did not work. I have now tried 54, 56, 57, and 59, no success with any of them.
A2. In the AVISYNTH folder I have MPED2Dec3dg.dll 1.0.1.0.
Occasionally various versions of QuEnc seem to freeze up during encoding, and I have been forced to restart severaltimes. I unfotunately cannot remember which version did what. No problem with freezeup or restart with 54 or 57 though, as I tried those yesterday/last night.
And no, my system is not overclocked.
Here are the logs (I just found where they were) and the contents of that D2VAV2 file. Perhaps they can help someone figure out what is going awry. Or any other advice on how my system might be set up wrong, please shout it out folks. Thanks for any help.
REBUILDER.LOG file contents
Transcoding...
-----------------
[02:55:56] Phase I, PREPARATION started.
- "Steal Space from Extras" mode is enabled.
- VTS_01: 3,939,433 sectors.
-- Scanning and writing .D2V file
-- Processed 266,241 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 52.3%
- Overall Bitrate : 2,924Kbs
- Space for Video : 3,963,276KB
- Movie improvement from extra reduction = .0%
- HIGH/LOW/AVERAGE Cell Bitrates: 3,618/393/2,924 Kbs
[03:11:21] Phase I, PREPARATION completed in 16 minutes.
[03:11:21] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Creating M2V for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Creating M2V for VTS_01 segment 7
- Creating M2V for VTS_01 segment 8
- Creating M2V for VTS_01 segment 9
- Creating M2V for VTS_01 segment 10
- Creating M2V for VTS_01 segment 11
- Creating M2V for VTS_01 segment 12
- Creating M2V for VTS_01 segment 13
- Creating M2V for VTS_01 segment 14
- Creating M2V for VTS_01 segment 15
- Creating M2V for VTS_01 segment 16
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_01 segment 18
- Creating M2V for VTS_01 segment 19
- Creating M2V for VTS_01 segment 20
- Creating M2V for VTS_01 segment 21
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
- Creating M2V for VTS_01 segment 26
- Creating M2V for VTS_01 segment 27
- Creating M2V for VTS_01 segment 28
- Creating M2V for VTS_01 segment 29
- Creating M2V for VTS_01 segment 30
- Creating M2V for VTS_01 segment 31
- Creating M2V for VTS_01 segment 32
- Creating M2V for VTS_01 segment 33
- Creating M2V for VTS_01 segment 34
- Creating M2V for VTS_01 segment 35
- Creating M2V for VTS_01 segment 36
- Creating M2V for VTS_01 segment 37
- Creating M2V for VTS_01 segment 38
- Creating M2V for VTS_01 segment 39
- Creating M2V for VTS_01 segment 40
- Creating M2V for VTS_01 segment 41
- Creating M2V for VTS_01 segment 42
[06:22:24] Phase II ENCODING completed in 191 minutes.
[06:22:24] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Rebuilding segment 0 VOBID: 1 CELLID: 1
D2VAVS file contents
Directory of C:\Temp DVDRB Dir B - Working\D2VAVS
REBUILDER.ECL 47,973 2/20/2005
REBUILDER.INF 8,712 2/20/2005
V01.D2V 948,284 2/20/2005
V01000000001001.AVS 283 2/20/2005
V01000000001001.FLG 7,246 2/20/2005
V01000000001001.m2v 88,899,584 2/20/2005
V01000100001002.AVS 287 2/20/2005
V01000100001002.FLG 7,341 2/20/2005
V01000100001002.m2v 72,005,632 2/20/2005
V01000200001003.AVS 288 2/20/2005
V01000200001003.FLG 6,036 2/20/2005
V01000200001003.m2v 61,306,880 2/20/2005
V01000300001004.AVS 288 2/20/2005
V01000300001004.FLG 7,398 2/20/2005
V01000300001004.m2v 80,601,088 2/20/2005
V01000400001005.AVS 288 2/20/2005
V01000400001005.FLG 7,896 2/20/2005
V01000400001005.m2v 101,105,664 2/20/2005
V01000500001006.AVS 288 2/20/2005
V01000500001006.FLG 7,041 2/20/2005
V01000500001006.m2v 119,543,808 2/20/2005
V01000600001007.AVS 288 2/20/2005
V01000600001007.FLG 4,812 2/20/2005
V01000600001007.m2v 86,167,552 2/20/2005
V01000700001008.AVS 288 2/20/2005
V01000700001008.FLG 4,791 2/20/2005
V01000700001008.m2v 52,684,800 2/20/2005
V01000800001009.AVS 288 2/20/2005
V01000800001009.FLG 11,260 2/20/2005
V01000800001009.m2v 209,346,560 2/20/2005
V01000900001010.AVS 288 2/20/2005
V01000900001010.FLG 6,600 2/20/2005
V01000900001010.m2v 129,105,920 2/20/2005
V01001000001011.AVS 288 2/20/2005
V01001000001011.FLG 6,864 2/20/2005
V01001000001011.m2v 123,836,416 2/20/2005
V01001100001012.AVS 288 2/20/2005
V01001100001012.FLG 5,925 2/20/2005
V01001100001012.m2v 118,532,096 2/20/2005
V01001200001013.AVS 288 2/20/2005
V01001200001013.FLG 8,371 2/20/2005
V01001200001013.m2v 170,164,224 2/20/2005
V01001300001014.AVS 289 2/20/2005
V01001300001014.FLG 10,186 2/20/2005
V01001300001014.m2v 181,815,296 2/20/2005
V01001400001015.AVS 290 2/20/2005
V01001400001015.FLG 6,637 2/20/2005
V01001400001015.m2v 116,107,264 2/20/2005
V01001500001016.AVS 290 2/20/2005
V01001500001016.FLG 5,304 2/20/2005
V01001500001016.m2v 87,586,816 2/20/2005
V01001600001017.AVS 290 2/20/2005
V01001600001017.FLG 6,407 2/20/2005
V01001600001017.m2v 80,142,336 2/20/2005
V01001700001018.AVS 290 2/20/2005
V01001700001018.FLG 7,026 2/20/2005
V01001700001018.m2v 133,578,752 2/20/2005
V01001800001019.AVS 290 2/20/2005
V01001800001019.FLG 2,637 2/20/2005
V01001800001019.m2v 36,605,952 2/20/2005
V01001900002001.AVS 290 2/20/2005
V01001900002001.FLG 6,109 2/20/2005
V01001900002001.m2v 71,659,520 2/20/2005
V01002000002002.AVS 290 2/20/2005
V01002000002002.FLG 2,760 2/20/2005
V01002000002002.m2v 47,644,672 2/20/2005
V01002100002003.AVS 290 2/20/2005
V01002100002003.FLG 4,067 2/20/2005
V01002100002003.m2v 54,839,296 2/20/2005
V01002200002004.AVS 290 2/20/2005
V01002200002004.FLG 7,301 2/20/2005
V01002200002004.m2v 103,575,552 2/20/2005
V01002300002005.AVS 290 2/20/2005
V01002300002005.FLG 2,495 2/20/2005
V01002300002005.m2v 39,723,008 2/20/2005
V01002400002006.AVS 290 2/20/2005
V01002400002006.FLG 9,444 2/20/2005
V01002400002006.m2v 161,316,864 2/20/2005
V01002500002007.AVS 290 2/20/2005
V01002500002007.FLG 6,120 2/20/2005
V01002500002007.m2v 84,035,584 2/20/2005
V01002600002008.AVS 290 2/20/2005
V01002600002008.FLG 4,324 2/20/2005
V01002600002008.m2v 62,443,520 2/20/2005
V01002700002009.AVS 290 2/20/2005
V01002700002009.FLG 6,270 2/20/2005
V01002700002009.m2v 88,342,528 2/20/2005
V01002800002010.AVS 290 2/20/2005
V01002800002010.FLG 11,309 2/20/2005
V01002800002010.m2v 156,790,784 2/20/2005
V01002900002011.AVS 290 2/20/2005
V01002900002011.FLG 9,354 2/20/2005
V01002900002011.m2v 118,190,080 2/20/2005
V01003000002012.AVS 290 2/20/2005
V01003000002012.FLG 4,382 2/20/2005
V01003000002012.m2v 79,396,864 2/20/2005
V01003100002013.AVS 290 2/20/2005
V01003100002013.FLG 2,076 2/20/2005
V01003100002013.m2v 22,200,320 2/20/2005
V01003200002014.AVS 290 2/20/2005
V01003200002014.FLG 3,792 2/20/2005
V01003200002014.m2v 67,803,136 2/20/2005
V01003300002015.AVS 290 2/20/2005
V01003300002015.FLG 4,452 2/20/2005
V01003300002015.m2v 86,843,392 2/20/2005
V01003400002016.AVS 290 2/20/2005
V01003400002016.FLG 6,053 2/20/2005
V01003400002016.m2v 101,588,992 2/20/2005
V01003500002017.AVS 290 2/20/2005
V01003500002017.FLG 6,636 2/20/2005
V01003500002017.m2v 88,666,112 2/20/2005
V01003600002018.AVS 290 2/20/2005
V01003600002018.FLG 9,038 2/20/2005
V01003600002018.m2v 97,081,344 2/20/2005
V01003700002019.AVS 290 2/20/2005
V01003700002019.FLG 3,484 2/20/2005
V01003700002019.m2v 60,821,504 2/20/2005
V01003800002020.AVS 290 2/20/2005
V01003800002020.FLG 7,035 2/20/2005
V01003800002020.m2v 135,493,632 2/20/2005
V01003900002021.AVS 290 2/20/2005
V01003900002021.FLG 4,548 2/20/2005
V01003900002021.m2v 64,573,440 2/20/2005
V01004000002022.AVS 290 2/20/2005
V01004000002022.FLG 10,026 2/20/2005
V01004000002022.m2v 185,389,056 2/20/2005
V01004100002023.AVS 290 2/20/2005
V01004100002023.FLG 5,387 2/20/2005
V01004100002023.m2v 60,235,776 2/20/2005
V01004200003001.AVS 290 2/20/2005
V01004200003001.FLG 1 2/20/2005
V01004200003001.m2v 8,192 2/20/2005
132 file(s) found
Total file size 4,089,083,455 bytes
dragongodz
21st February 2005, 00:41
Occasionally various versions of QuEnc seem to freeze up during encoding, and I have been forced to restart severaltimes.
that could happen with 0.54 on a Pentium 4 unless you use the memaligned avcodec by the way. which is why i mentioned it aboev. :)
The newer versions seem to be undersizing the output quite a bit.
yes i have a few theories on why this may be happening but i really need to test them. just have to find some time to set up compiling the latest version etc. :D
nathanaa
21st February 2005, 01:49
Originally posted by dragongodz
that could happen with 0.54 on a Pentium 4 unless you use the memaligned avcodec by the way. which is why i mentioned it aboev. :)
I don't have a Pentium 4. I also really have no idea what a memaligned avcodec is though, but I guess that point is moot. Any other ideas on what might be going on? Thanks for the input.
nathanaa
21st February 2005, 20:17
Based on the log contents and the file type & size info I included above, does anyone have any input on anything that might be causing my Error 0006 problem? I cannot get DVD-RB to work with any version of QuEnc. Every single version gets to the same point and then errors out and crashes the program.
Can ANYONE think of anything I could try?
borgraf
21st February 2005, 21:28
Originally posted by nathanaa
Can ANYONE think of anything I could try? I can think of a bunch of things you can try. But unfortunately none of them have a high chance of success. Either way, trying various things might help narrow down the problem..
Try changing your decoder to the recommended one, DGDecode.dll, found here:
http://forum.doom9.org/attachment.php?s=&postid=613629
put it in your avisynth/plugins folder and setup RB to use it instead of your MPEG2Dec3dg.dll
You can also try a run with the CCE SP trial version (I haven't run this one myself but it should work), download here: http://www.cinemacraft.com/eng/trial.html#sp and set RB to mode CCE and to option CCE SP Trial. You might also have to check the setting "Run Encoder(s) Minimized". The encoded dvd will have watermarks, but atleast you will know if it works then the problem might be with QuEnc, if it gives the same error the problem might not be with QuEnc but something else.
Another unlikely thing to try it to not use the external HDD at all, only the internal.
hope it helps, or gets the ball rolling..
good luck!
lamster
21st February 2005, 22:30
Originally posted by nathanaa
so why does the application report some goofy number then? I suppose it's not really relevant (and I know you have no control over how or why it would do such a thing), I'm just curious, as I do *want* to understand as best I can how/why these programs do these things.
If you download the QuEnc source, and examine QuEnc.rc, you'll note that it contains:
VS_VERSION_INFO VERSIONINFO
FILEVERSION 1,0,0,1
PRODUCTVERSION 1,0,0,1
nathanaa
22nd February 2005, 00:16
Originally posted by lamster
If you download the QuEnc source, and examine QuEnc.rc, you'll note that it contains:
VS_VERSION_INFO VERSIONINFO
FILEVERSION 1,0,0,1
PRODUCTVERSION 1,0,0,1
So, in other words it reports that because that is what QuEnc lists the information as. Why didn't you just say so? :)
Not only would I not know where to DL the QuEnc source (or any source, for that matter), but I certainly would not know how to examine said source. Far beyond my current capabilities. Thanks for the info though, informative!
I'm going to replace that .dll and see if that can help. I hadn't thought to try that CCE trial method to make sure that it wasn't anything else (just QuEnc), so I'll perhaps have to give that a whirl too.
nathanaa
22nd February 2005, 21:19
I replaced the .dll file with the recommended version, and I also tried running everything from the internal HDD - still no luck with QuEnc. I keep getting the same 0006 error in the same spot.
I then downloaded the CCE 2.50 trial, and set that up. I'm no 100% sure I have everything set up properly. In the RB set up I pointed the CCE 2.50 where the CCE 2.5 .exe was installed, and I ran EclPro (from the RB Installer) at the CCE 2.50 .exe file too.
When I ran RB it errored out with error's 76 and 53 (I think those were the numbers).
I don't really want to spend a lot of time trying to get the CCE trial working when I really want QuEnc to work.
Can ANYONE help? God, this is so frustrating, I've been trying to get this to work for WEEKS now.
dragongodz
22nd February 2005, 22:24
nathanaa -
how many movies fail at the rebuild stage ?
what specific movie/s fail ?
nyt
22nd February 2005, 23:33
Hi,
I have a movie with an uncorrectable error, causing 10 bad frames (in one spot). I am using CCE 2.7, RB 0.77, dgdecode 1.10.
I trim()'d the bad frames in the .avs:
trim(start,badframe-1) ++ trim(firstnewgoodframe, end)
then reencoded the corresponding m2v, reduced the Frames value accordingly in the rebuilder.inf, but I still get error 6. What did I miss?
thanks!
pg55555
22nd February 2005, 23:48
nathanaa
For CCE 2.5 you need a program called EclCCE, not EclPro which is for Procoder.
You must copy EclCCE.exe to a directory (it can be the same as ccesp.exe) and run it. When you run it it will ask you for the location of the ccesp.exe file. Point to it. In RB setup you must point to the path of the EclCCE.exe file, NO to the ccesp.exe. Run RB+CCE with just 2 passes (you are testing) If after doing this you still have problems, please post you rebuilder.ini file
Regarding QuEnc "10 hours" encoding, try disabling all the High Quality settings (ie Trellis): You are in debugging mode, not trying to get the best copy
In a previous post you mentioned you were successful with RB+Rejig but when trying to burn with Nero you got a Error message. I would recomend next time it happens somethinng similar, use DVDShrink Full Backup with "No Compression" to produce an ISO file, and then burn this ISO file with DVDDecrypter (I'm not very fond of Nero for burning DVD Video)
nathanaa
23rd February 2005, 00:13
I'll answer this in two separate posts to keep from getting confusing.
Originally posted by pg55555
nathanaa
Regarding QuEnc "10 hours" encoding, try disabling all the High Quality settings (ie Trellis): You are in debugging mode, not trying to get the best copy
In a previous post you mentioned you were successful with RB+Rejig but when trying to burn with Nero you got a Error message. I would recomend next time it happens somethinng similar, use DVDShrink Full Backup with "No Compression" to produce an ISO file, and then burn this ISO file with DVDDecrypter (I'm not very fond of Nero for burning DVD Video)
When I have run QuEnc, I *have* disabled all the high quality settings, and it was taking about 10 hours. When I switched it to 1 hour mode (for debugging) it is about 5-6 hours I think (been running it at night, so not sure, as when I get up and I have the error 0006 message, it crashes after clicking OK).
The oddity with ReJig I was talking about, was that after having processed with ReJig, I tried to burn with Nero. I got a warning that the video would be "out of standard" or something like that (so I cancelled the burn). When I redid the same discs with DVDShrink, I got no such error message (so now at least I have a lower-quality backup of Yes, Minister).
I have not noticed this problem with any of my other discs, just Yes, Minister. It was the same with all 4 of the discs in the series though, and I re-ripped them several times (in File mode). I'll give the ISO mode a try next time that particular problem arises.
On to the next post!
nathanaa
23rd February 2005, 00:16
Originally posted by pg55555
nathanaa
For CCE 2.5 you need a program called EclCCE, not EclPro which is for Procoder.
You must copy EclCCE.exe to a directory (it can be the same as ccesp.exe) and run it. When you run it it will ask you for the location of the ccesp.exe file. Point to it. In RB setup you must point to the path of the EclCCE.exe file, NO to the ccesp.exe. Run RB+CCE with just 2 passes (you are testing) If after doing this you still have problems, please post you rebuilder.ini file
I suppose I'll give that a try, as it is the only way to make sure it is actually QuEnc that is the problem. I'll look up and download EclCCE and follow your directions, and if I still have no luck I'll post that rebuilder.ini file (I did post the QuEnc one previously, if you want to see what that had to say, maybe there is something there???). Thanks for the input/assistance!
And on to the next post!
nathanaa
23rd February 2005, 00:25
Originally posted by dragongodz
nathanaa -
how many movies fail at the rebuild stage ?
what specific movie/s fail ?
ALL of them fail at the rebuild stage. I have tried many different discs - off the top of my head I have tried:
- all four Yes, Minister discs
- Dune (SciFi channel version) D1
- two of the five Band of Brothers discs
- assorted discs from Frasier S2, Alias S3, and other shows
I have a lot of TV shows (episode discs), those are what I mainly am backing up, as I used DVDShrink before I found out about DVDRebuilder for most of movies; once I get RB to work for me with QuEnc, I plan on redoing my movies (time and money permitting - what the heck am I going to do with all those "old" backup discs???).
I buy the TV shows cheaper at the used DVD store (amazing the stuff you find there, *days* after it's been released), but they are in excellent shape (only once did I get a damaged disc), so I don't believe it is the source files.
Any thoughts?
dragongodz
23rd February 2005, 00:28
I would recomend next time it happens somethinng similar, use DVDShrink Full Backup with "No Compression" to produce an ISO file, and then burn this ISO file with DVDDecrypter (I'm not very fond of Nero for burning DVD Video)
i agree. you can also use imgtool classic for making an iso of coures but dvdshrink should also be fine. :)
if you are game heres another thing you can try and see if it makes any difference. run yes minister through dvdshrink first with everything set to no compression and nothing removed(audio/subs). then try running that through DVD-RB.
EDIT:
ALL of them fail at the rebuild stage.
which is the strange thing since others have not had any trouble. so it has to be something specific to your pc or dvds(such a mix suggests its not the dvds).
EDIT2:
can you tell me what you have in your Avisynth plugins folder aswell ? i reccomend NOT to have dgdecode.dll etc there but somewhere else and then set the path to that in DVD-RB.
nathanaa
23rd February 2005, 01:20
Originally posted by dragongodz
EDIT:
which is the strange thing since others have not had any trouble. so it has to be something specific to your pc or dvds(such a mix suggests its not the dvds).
EDIT2:
can you tell me what you have in your Avisynth plugins folder aswell ? i reccomend NOT to have dgdecode.dll etc there but somewhere else and then set the path to that in DVD-RB.
Yes, I am thinking it has to be something specific to my computer, I don't think it a fault of RB directly.
Contents of my AVISynth 2.5 folder:
DOCS folder
-english folder
-avisynth.css file
-style2.css file
-style.css file
Examples folder
- <assorted files>
plugins folder
- colors_rgb.avsi file
- DirectShowSource.dll file
- MPEG2Dec3dg.dll file
- NEWDGDecode.dll file (my addition on previous posters advice)
- OLDDGDecode.dll file (whatever the Installer installed)
- TCPDeliver.dll file
gpl.txt file
Uninstall.exe file
So if I should not have the DGDecode file(s) in the AVISynth folder, should I remove both of the two DGDecode files AND the MPEG2Dec3dg.dll file? Or remove just those and leave the other?
dragongodz
23rd February 2005, 01:41
So if I should not have the DGDecode file(s) in the AVISynth folder, should I remove both of the two DGDecode files AND the MPEG2Dec3dg.dll file? Or remove just those and leave the other?
remove them all. you do not want any of them autoloading.
make a folder somewhere else and put just 1 of the dll in it. set DVD-RB up for that.
nathanaa
23rd February 2005, 02:22
Originally posted by pg55555
nathanaa
For CCE 2.5 you need a program called EclCCE, not EclPro which is for Procoder.
You must copy EclCCE.exe to a directory (it can be the same as ccesp.exe) and run it. When you run it it will ask you for the location of the ccesp.exe file. Point to it. In RB setup you must point to the path of the EclCCE.exe file, NO to the ccesp.exe. Run RB+CCE with just 2 passes (you are testing) If after doing this you still have problems, please post you rebuilder.ini file
OK, I downloaded EclCCE.exe (1.81 I believe). I searched my computer, but there is no ccesp.exe file. I don't know if it is supposed to be in the CCE 2.50 trial? Where else would it have come from?
Also, once one of you folks clues me in as to where I am supposed to get this file (program?) from, where should it be installed - in the DVD Rebuilder folder, by itself, in the AVISynth folder, ???
Thanks for any & all help folks.
nathanaa
23rd February 2005, 02:24
Originally posted by dragongodz
remove them all. you do not want any of them autoloading.
make a folder somewhere else and put just 1 of the dll in it. set DVD-RB up for that.
OK, I'll give that a try and see if I can get QuEnc to work then. I'll try the NEW one first, then the OLD one, then the MPEG2 one, hopefully one of those 3 in the proper place will do the trick. I'll post results when I have them, THANKS!!! (All the help is GREATLY appreciated!!)
pg55555
23rd February 2005, 13:55
OK, I downloaded EclCCE.exe (1.81 I believe). I searched my computer, but there is no ccesp.exe file. I don't know if it is supposed to be in the CCE 2.50 trial? Where else would it have come from?
ccesp.exe should be the executable of CCE 2.50 and yes, it should be in the CCE 2.50 Trial folder (Maybe it has another name in 2.50 trial, I am using my memory here).
Rockas
23rd February 2005, 20:07
OK, I downloaded EclCCE.exe (1.81 I believe). I searched my computer, but there is no ccesp.exe file. I don't know if it is supposed to be in the CCE 2.50 trial? Where else would it have come from?
Why don't you use my installer? It contains EclCCE and will install it if your version of CCE needs it (you just need to pay attention to the version you choose) and it will set the pathes on Rebuilder correctly.
nathanaa
23rd February 2005, 21:47
Originally posted by Rockas
Why don't you use my installer? It contains EclCCE and will install it if your version of CCE needs it (you just need to pay attention to the version you choose) and it will set the pathes on Rebuilder correctly.
I *did* use your Installer. I *didn't* understand how to properly set it up though, which is where these particular CCE-related (really "set up" related) problems came from. I'm not really interested in using CCE though, I want QuEnc to work, CCE would just be to discern if all my problems are actually QuEnc related or if it is something else.
nathanaa
23rd February 2005, 21:55
Originally posted by dragongodz
remove them all. you do not want any of them autoloading.
make a folder somewhere else and put just 1 of the dll in it. set DVD-RB up for that.
Ok, I have now tried this, and still no success. I tried all three of the possible .dll files and each got to the same point and Error 0006 crashed the program.
I also tried something else; I have been using DVDDecrypter to rip my DVDs in File mode. I tried using DVDShrink in ISO mode, mounted it with Daemon Tools, and used the above recommended version of DGDecode (located in a separate folder than Avisynth plugin's). It still failed.
I've kept the rebuilder.ini logs for each separate attempt, I'll post the most recent one (with the DVDShrink ISO attempt), but if you want to see the other 3 I can post any or all of them, or email/PM them to anyone who wants them. I could also provide the contents of the D2VAS file (the file/folder names and sizes) if it would be of any help, although a previous one is provided in a previous post (if anyone wants to check that, on page 2 of this thread I believe).
Any further help, GREATLY appreciated.
Transcoding...
-----------------
[08:38:11] Phase I, PREPARATION started.
- "Steal Space from Extras" mode is enabled.
- VTS_01: 3,939,433 sectors.
-- Scanning and writing .D2V file
-- Processed 266,241 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 52.3%
- Overall Bitrate : 2,924Kbs
- Space for Video : 3,963,276KB
- Movie improvement from extra reduction = .0%
- HIGH/LOW/AVERAGE Cell Bitrates: 3,618/393/2,924 Kbs
[08:46:26] Phase I, PREPARATION completed in 8 minutes.
[08:46:26] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Creating M2V for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Creating M2V for VTS_01 segment 7
- Creating M2V for VTS_01 segment 8
- Creating M2V for VTS_01 segment 9
- Creating M2V for VTS_01 segment 10
- Creating M2V for VTS_01 segment 11
- Creating M2V for VTS_01 segment 12
- Creating M2V for VTS_01 segment 13
- Creating M2V for VTS_01 segment 14
- Creating M2V for VTS_01 segment 15
- Creating M2V for VTS_01 segment 16
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_01 segment 18
- Creating M2V for VTS_01 segment 19
- Creating M2V for VTS_01 segment 20
- Creating M2V for VTS_01 segment 21
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
- Creating M2V for VTS_01 segment 26
- Creating M2V for VTS_01 segment 27
- Creating M2V for VTS_01 segment 28
- Creating M2V for VTS_01 segment 29
- Creating M2V for VTS_01 segment 30
- Creating M2V for VTS_01 segment 31
- Creating M2V for VTS_01 segment 32
- Creating M2V for VTS_01 segment 33
- Creating M2V for VTS_01 segment 34
- Creating M2V for VTS_01 segment 35
- Creating M2V for VTS_01 segment 36
- Creating M2V for VTS_01 segment 37
- Creating M2V for VTS_01 segment 38
- Creating M2V for VTS_01 segment 39
- Creating M2V for VTS_01 segment 40
- Creating M2V for VTS_01 segment 41
- Creating M2V for VTS_01 segment 42
[11:50:55] Phase II ENCODING completed in 184 minutes.
[11:50:55] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Rebuilding segment 0 VOBID: 1 CELLID: 1
nathanaa
24th February 2005, 09:36
Well, after following the instructions for getting CCE to work, I ran Dune D1 through CCE SP 2.50 and it worked perfectly. I am amazed, to be frank, at the quality of the image. This was about a full 50% shrink (8.1 gigs to 4.15 gigs). Yes, I said 4.15 - the result was undersized. Any idea why it would have done that?
I may have to seriously consider paying the $50+ to get the basic CCE, becuase man oh man is that a sharp and clear image.
Still, anyone have any further input on my QuEnc problems?
borgraf
24th February 2005, 16:43
I'm glad you finally got it to work. Don't hesitate to buy CCE Basic, it's the best encoder. You will get a more recent and improved version than the one you used; and that could be better at, among other things, meeting the targetsize. You can also tweak the targetsize manually, see sticky threads, but no complaints if you tweak too much and oversize :)
Now since you've changed some files around, and had a successful run with CCE and your Dune disc, i'd give QuEnc another go with the same source to see if you still get the error.
nathanaa
24th February 2005, 19:45
Allright, I'll give QuEnc one more try. If it doesn't work this time, I think I'll just go ahead and purchase CCE Basic. I realized that with the accumulated WEEKS I have spent trying to get QuEnc to work, the time I have spent on that effort was certainly worth far more than $60.
Actually, to hell with it, I'll just buy the CCE Basic. If I get bored maybe I'll try QuEnc again, lol. Hmm, I should make a donation too while I'm at it, if I can buy CCE I can certainly drop a few bucks in jdobbs's lap for his efforts.
Hopefully I shall not have to return to this thread!!! Wish me luck, and thanks for all the help folks.
vBulletin® v3.8.4, Copyright ©2000-2010, Jelsoft Enterprises Ltd.