PDA

View Full Version : Error 006: Framecount differences.....


camelx
28th March 2006, 00:54
The error I'm getting is:

Error 006: DVD-RB has found framecount differences between the PREPARE and REBUILD phases. Aborting.

Background:
Using 1.09.2 Pro
Movie - The Cave
Used newest Fabdecriptor to rip it 2.9.7.3
Pointed Dvdrebuilder to that rip dir
and it goes a good while prior to me getting the error.

NOte:
DVDShrink was aborting during it's process too, until I used the new version of Fabdecriptor, then it worked just fine!!

jdobbs
28th March 2006, 02:59
That is an indicator of a bad rip. It's possible that there is a true error on the disc (for example a scratch) that DVD Fab has misinterpreted as copy protection. You may want to try ripping it again.

Also -- have you done any preprocessing at all? Make sure you let DVD-RB work with the original rip.

camelx
28th March 2006, 06:13
I got another copy of the movie and had the same results, so it happened twice. Also the same rip dir, worked just fine with DVDShrink, and I played and watched about half of the movie and fast forwarded through the rest of it on the PC itself from the ripped dir.

The other copy I got was a friends, I thought the same about the original being bad. I have had that problem before with bad originals.

Not saying it still is not a possiblity, however wanted to include more details for you. I know "The Cave" has issues, that's why DVDFABdecriptor had to update too.

I guess the best thing now is to see if anyone else ripped (with what?), and did a DVDRebuilder with "The Cave".

Also I'll add, I tried both full DVD, all original, and movie only attempts with DVDRebuilder. Each bombed out.

THanks in advance, I still love DVDRebuilder!

jdobbs
28th March 2006, 13:10
I did the NTSC, R1 version.

l8nights
28th March 2006, 17:02
the use of fixvts should alleviate the error, mine worked fine w/ psl2 wizard, and if I'm remembering right the cave was one I experimented w/ fabdecrypter also and it worked fine so I wonder what the difference is like jdobbs I'm also in R1

camelx
28th March 2006, 18:15
I'm NTSC also and R1.

Pardon my ignorance, but where and how do I use the fixdts you mentioned?

And the same for the psl2 wizard?

Thanks again.

l8nights
30th March 2006, 06:00
fixvts 1.24 (http://www.videohelp.com/~FixVTS/)
psl2 plugin (http://www.digital-digest.com/~blutach/PgcEdit_install.exe)

Thang_Bom
1st April 2006, 04:41
I got the same error... I did use DVDFAB v2.9.7.5 Beta 2.. I did run thru VOBBlanker (to blank out) and DVDSHrink (no Encode) and Back to VOBBLanker again.

If I let DVDshrink to re-encode (transcode), DVDshrink work fine.

I would think right now, it maybe RB-PRO v1.09.

jdobbs
1st April 2006, 05:04
I don't.

Run it without the preprocessing and see if it happens. My guess is it won't.

No one ever gets that error except with a bad rip or preprocessing.

Thang_Bom
1st April 2006, 07:19
I assume you mean PREPARE, ENCODE, Rebuild. That is what I did it first run, After a long CCEing and it failed on rebuild process.

Then I let DVDShrink to process that DVDFAB and try 1-step Click. It failed again. I change to 2 pass CCEing and 1-pass.

I will try to run BIG-3 tonight.

jdobbs
1st April 2006, 12:14
What disc are you doing? Is it "The Cave" also?

The DVD Fab I used to do that movie was v2.9.6.8. I'll run that it through again using the latest (v2.9.7.3) DVD Fab and see what happens.

BTW -- reporting that you ran it through Shrink doesn't mean anything. Shrink doesn't check the stream for integrity because it doesn't have to reencode it.

Thang_Bom
1st April 2006, 14:16
This is the new Vietnamese music video... I am processing DVD 2 of that set.

There is a discussion of it in Digital forum here.

http://forum.digital-digest.com/showthread.php?t=63955&page=8

I hope it is ok to post the link.

l8nights
1st April 2006, 17:01
I don't get the relevance of the link it's a different title &, different method of ripping than you are saying to use??!??

did you try the method in your link?
I don't know why the second, post shrink, vobblanker pass?

I think if you ran your files through vobblanker, rebuilder should eat them up, no?

jakeduck
1st April 2006, 17:41
[QUOTE=camelx]

I guess the best thing now is to see if anyone else ripped (with what?), and did a DVDRebuilder with "The Cave".

" The Cave" AnyDVD>DVDDecrypter>DVDRB. No problem.

Thang_Bom
1st April 2006, 17:48
It is the new protection scheme, I did run DVD1 thru DVDFab and I did get RB ok. But not on the second disk. For this second disk, as I mention earlier and on the post. I did use DVDFab v2.9.7.5 beta 2at the request of the author. So now I am trying to CCE it. I got the error code '6'.

Yes I know there are some fake cell that need to be cleaned but I thought by running thru DVDshrink and Vobblanker, it would clean it up. Maybe it did not clean them good enough that RB detect error.

One more question, if I ran thru RB without re-encoding, would it clean it? and then I can re-encode?

I don't get the relevance of the link it's a different title &, different method of ripping than you are saying to use??!??

did you try the method in your link?
I don't know why the second, post shrink, vobblanker pass?

I think if you ran your files through vobblanker, rebuilder should eat them up, no?

l8nights
1st April 2006, 18:24
the "new protection scheme" can be applied in different places in different way's on different movies/zones

so one may not represent the same scheme on another title

after rip use the vobblanker if you have it or fixvts (link above) and see if your error will disapate in rebuilder as well as shrink.

Thang_Bom
1st April 2006, 19:08
Here are all the steps I did after running DVDFAB v2.9.7.5 Beta 2

- Vobblanker
- DVDshrink on top of Vobblanker
- Vobblanker again.
- fixvts

DVDshrink to transcode works...


the "new protection scheme" can be applied in different places in different way's on different movies/zones

so one may not represent the same scheme on another title

after rip use the vobblanker if you have it or fixvts (link above) and see if your error will disapate in rebuilder as well as shrink.

jdobbs
1st April 2006, 22:37
Or you could:

1. Rip with AnyDVD.
2. Reencode with DVD Rebuilder.

That's how I did that disc.

I'll have the results of testing it with DVD Fab today.

Thang_Bom
2nd April 2006, 01:09
I try with the latest version... The DVD 1 can read ok.. But DVD 2 does not work.. Still getting error reading with disk 2.

jdobbs
2nd April 2006, 03:22
Well, I don't know what you guys are doing -- but it has to be more than I'm seeing in this post. I just finished running "The Cave, R1, NTSC" for the third time today (I did it with three different encoders). It worked perfectly every time.

Here's the complete process I used.

1. I read it with DVD Fab Decrypter v2.9.7.3 into a directory.
2. I ran DVD Rebuilder v1.09.2 in One Click mode.

It worked with CCE, HC Encoder, and ProCoder.

@camelx

Could you post your REBUILDER.LOG?

Thang_Bom
2nd April 2006, 03:26
My movie is not the Cave - A new protection scheme that need to get v2.9.7.5 to rip it. There is fake VTS_02, if you dont use v2.9.7.5 Beta 2, it will take forever to rip the disk.

Thang_Bom
2nd April 2006, 03:46
Here is the link for the log file

http://s33.yousendit.com/d.aspx?id=1X4G0HEX1GNYC2KJTO0FBM5XT1

blutach
2nd April 2006, 09:08
The "new protection" on the Vietnamese music DVD is simply a more advanced version of ARccOS, where the bad sectors are not only in VTS_0X_1.VOB

Those disks can be ripped by the PgcEdit (http://www.videohelp.com/~r0lZ/pgcedit/index.html) plugin in advanced mode (after ignoring unreferenced titlesets).

I'd bet any errors you are getting in DVD Rebuilder (http://dvd-rb.dvd2go.org/) would be related to a bad rip.

Regards

JohnG
5th April 2006, 21:49
I'm having a problem with "Narnia..". I'm receiving the 0006 error whenever I try to blank any portion of the movie. I ripped to .iso with DVD Decrypter, mounted it with Daemon as the DVD-RB source and blanked it using the built in Preview/Edit function. I tried to back-up without processing and it works. By the way, the portions that I am trying to blank are merely previews and should have nothing to do with tainting the structure.

jakeduck
5th April 2006, 23:12
Just did "Narnia" DVDD to HDD>DVDRB "movie and menus" Img to burn no problem.

JohnG
5th April 2006, 23:53
Just did "Narnia" DVDD to HDD>DVDRB "movie and menus" Img to burn no problem.

Right, my point is that the processing function in RB is creating a problem on the rebuild phase of the back-up. I already managed a regular back-up.

jdobbs
6th April 2006, 00:05
Send me your REBUILDER.INI file at dvd-rb@dvd-rb.com so I can make sure I repeat your actions exactly.

JohnG
6th April 2006, 19:35
Just a follow-up:
I since have re-ripped using DVDFab, run it through FixVTS and then process with VOB Blanker. It's running through RB now (using Rejig just to quickly test) and it's 60% through the rebuild with no problems....looking good. Jdobbs, would you still like me to replicate the procedure that failed before? It's no problem if you still want to see that log file.

jdobbs
6th April 2006, 20:22
I'd definitely like to track down the cause.

JohnG
6th April 2006, 20:31
Okay. I'm currently finishing it up (encoding with CCE), so I will redo the old procedure and send along the file when I'm done.

jdobbs
6th April 2006, 23:19
Thanks.

JohnG
7th April 2006, 17:24
jdobbs, the files have been sent to your e-mail.
From what I understand, this is a ripguard disk which might explain the problems. As I mentioned, I already managed a very nice back-up after re-ripping with DVDFab->FixVTS->blanked with VOBblanker->RB. The only time I experienced any issues was with the DVDD ripped .iso version. But even with this rip, I still managed a FULL back-up (untouched source), but any processing to the extraneous VTSs with RB's preview/edit function caused a Rebuild failure. I also tried oversizing the disk and marking those cells to remain as "raw frames" (no encoding) in the hopes to post process...the rebuild still failed.

lamster
9th April 2006, 18:31
I just ran across the second DVD where I got this error. (Ran it through FixVTS, and am retrying...)

Is there any way that you can detect the problem up-front, as opposed to my not finding out until phase 3?

Also, do you think that the error message should be written to the rebuilder.log? It seems to me that this would be helpful, so people can quote it accurately when posting.

jdobbs
9th April 2006, 18:46
I might be able to if I could find that it's usually the same thing causing it. But right now, since it's an indicator of a corrupt input stream -- that might be anything. Honestly most of the time I think its the result of bad editing... and I'm not sure I'd ever be able to get around that. For example, if someone breaks a stream on a GOP that is open -- there might be a reference to a frame that doesn't exist any more... and you'd get this error. To fix it I'd be asked to create a missing frame out of nothing.

This is the reason I keep saying I can't respond to problems reported that involve preprocessing... it's just too much to ask to have DVD-RB bring a "butchered" stream back to life. Most of the time people will say "but it seems ok in my player" -- and its a true statement -- but that's because a player will just keep going and ignore the garbage. An authoring package can't do that.

I'm not whining... but I just want people to understand what the real problem is.

If DVD-RB is the only processing (e.g. the segment editor, as was mentioned in at least one case) then I can find a cause and fix it.

lamster
9th April 2006, 19:43
Well, in this case I just decrypted with DVD Decrypter and tried to make a backup using Rebuilder. In the previous case, I first did that, and after that failed, I tried re-ripping with DVDFab Decrypter, and got the same results. I did no pre-processing in either case.

DVD Decrypter did say:
W 23:50:07 Possible Structure Protection Found!
W 23:50:07 2 areas have been marked as 'suspect'.
W 23:50:07 Dummy sectors will be inserted where necessary.
- do you count that as preprocessing?

I understand what you're saying; I'm just wondering if you can detect up-front discrepancies caused by copy protection that will cause problems in the rebuild phase.

jdobbs
9th April 2006, 23:20
Unfortunately every time I've gotten one of these reports so far, and then have gone out and purchased the DVD hoping to repeat it -- it has worked correctly. I have never found it necessary to use Fixvts on any DVD yet -- and although I test encode anywhere from 2 to 4 DVDs every night, I have never gotten a #0006 error.

If someone could point me to an NTSC disc and a ripping process (even if it involves preprocessing) that will definitely cause this error I'd love to find it. Even if the fault isn't DVD-RB it would be nice to see an example so I can find out what gremlin is crawling around in the MPEG stream.

mikaru
10th April 2006, 21:49
I am having this exact problem with Narnia ntsc retail. dvddecrypter warns about the dummy sectors but i end up with complete iso file. dvdrb fails with error #006 at the rebuild stage. i have tried it with preprocessing and with the original iso file and it errors everytime. this might be one for you to try. i rip with dvddecrypter 3.5.4.0, mount the image with Daemon tools 3.47 and run dvd rebuilder pro 1.09.2. hope this helps.

Mike

lamster
10th April 2006, 22:16
Ditto with Narnia (NTSC, region 1, 2-disk deluxe edition).

DVDdecrypter 3.5.4.0, ripped as files, no preprocessing, QuEnc 0.6.1.0, "Half D1/Half space for extras", DTS and French audio tracks being removed. Ended with error 6.

Ran FixVTS and retried. The rebuilder.log from the first attempt had "-- Embedded null records found", whereas the log from the second attempt does not. However, the second attempt also ended with error 6. The last thing in the rebuilder.log is "- Processing VTS_01" ... "Rebuilding seg 2 VOBID 2 CELLID 1"

SpazzHH
10th April 2006, 23:42
Since those are RipGuard discs, I would retry with DVDFab Decrypter and do no preprocessing. That formula worked for me. If I tried to run VobBlanker afterwards, the encodes errored out, but as long as I sent them straight to RB they worked fine.

jdobbs
11th April 2006, 00:43
Ditto with Narnia (NTSC, region 1, 2-disk deluxe edition).

DVDdecrypter 3.5.4.0, ripped as files, no preprocessing, QuEnc 0.6.1.0, "Half D1/Half space for extras", DTS and French audio tracks being removed. Ended with error 6.

Ran FixVTS and retried. The rebuilder.log from the first attempt had "-- Embedded null records found", whereas the log from the second attempt does not. However, the second attempt also ended with error 6. The last thing in the rebuilder.log is "- Processing VTS_01" ... "Rebuilding seg 2 VOBID 2 CELLID 1"I've done that disc with AnyDVD/DVD Decrypter without any errors. But I'll run it through anyway without AnyDVD -- I'd like to find out what is actually causing the error.

You may want to try removing VTS_MIN_SIZE from your INI if you have one. I seem to remember that one of the small VTSs on that disc was filled with garbage. Without VTS_MIN_SIZE it would simply be copied. I'm working from memory, though.

jdobbs
13th April 2006, 01:41
Just an update on this one.... I don't know how you ripped "Narnia" with DVD Decrypter alone... I tried it and it fails within a minute or so of the start with a read error...

JohnG
16th April 2006, 06:23
Just an update on this one.... I don't know how you ripped "Narnia" with DVD Decrypter alone... I tried it and it fails within a minute or so of the start with a read error...
Could it be that the settings are somehow different? It appears that at least 3 of us have ripped this successfully to .iso with DVDD alone.

jdobbs
16th April 2006, 12:10
My guess is that you have "ignore errors" set. That might work on some discs -- but can result in problems on others. I have ripped and tested "Narnia" with the latest versions of both DVD Fab and AnyDVD and it works correctly.

JFerguson
24th April 2006, 20:51
I just got this error with Memoirs Of A Geisha R1 Disc 1. Ripped with AnyDVD v5.9.4.1 (which I now see is dated).

I'll rerip with an updated version...

jdobbs
25th April 2006, 04:13
I did that one... I used AnyDVD. I've been working for the past week on various ways to circumvent the causes of #0006. It's mainly caused by garbage in the source... version 1.09.3 should make it much less likely.

Voodoochild
27th April 2006, 08:28
But Have lot's of Experience with DVD rips.
I used to work and steel do with DVD shrink, How ever I discovered DVD RB, and for heavy compressions.. yes it's the best.
I have some tips that may help some people with error 0006.
1. no matter how you ripped the DVD, Use FixVts at the end, it remove all the garbage, and DVD- RB can rebuild.
I tried to rebuild backup of my Seinfeld DVD and I got error0006, after FixEdit problem solved.
2. You don't have to rip SonyArcos DVD's with PcgEdit Plugin,
you can rip it with software like anydvd or DVd region + css
but be sure to run it with FIxVts after.
3. FixVts should be the last step .. after using VobBlanker , menushrink etc...
Then dvdrb can rebuild No Problem.

No for 1 question, I'm using the 0.97 free edition, is there any way to upgrade the DGdecode.DLL.
when I used Latest version Encode time was 4 time Faster with VTS setting deen()...
BUT I couldn't see the video since DGindex version was different then the DGDecode.dll version.
Is there way to upgrade the DGindex as well...??
Many Thanks in advance.

Rockas
27th April 2006, 10:22
At this point you can't use other dgdecode.dll than the one included on the package...

Voodoochild
27th April 2006, 13:53
At this point you can't use other dgdecode.dll than the one included on the package...

Ok 10x, the one in the package works good, bit slow but it's ok i'll wait for the upgrade

jdobbs
27th April 2006, 15:56
I can't imagine how it could be 4x faster just because of a version upgrade???? Are you sure? For normal decoding I've tested the latest and the one included in the package and their speed is virtually identical (without deen() at least).

The Pro Version uses DGDECODE v1.4.5

Voodoochild
27th April 2006, 16:42
I can't imagine how it could be 4x faster just because of a version upgrade???? Are you sure? For normal decoding I've tested the latest and the one included in the package and their speed is virtually identical (without deen() at least).

The Pro Version uses DGDECODE v1.4.5

Hi jdobbs
First 10x for the fast reply and the great software. for heavy compressions it's the best
second I backed up seinfeld dvd season 6 disc 1
removed all extras, left with only main moovie
and menu
with DGDECODE v1.4.7 and there difference in speed
between v1.4.5 and 1.4.7
used deen()
with v.1.4.7 took 69 min
with v.1.1.0 took 224 min
speed in ecc SP.v2.70.02.06 v1.4.7b6 shown 3.80-3.90
speed in ecc SP.v2.70.02.06 v.1.1.0 shown 0.90-1.00
i'll be glad to give more details and help if you need

Voodoochild
27th April 2006, 16:48
without deen() v.1.1.0 worked at 1.80-2.04 speed

jdobbs
27th April 2006, 16:50
That sounds about right for the difference between having deen() in and out... are you sure you had deed() enabled in both runs?

[edit] Answered... we posted at the same time.

Has Neuron2 posted saying changes to 1.4.7 have made it 2x faster? What speed are you getting with v1.4.5? Also, what kind of processor are you using?

Rockas
27th April 2006, 16:52
ummmm... that's very strange... I don't think that even changing the "Decoder iDCT" anyone ever pointed such a difference on speeds...

are you sure you tested with the same project "properties"?

edit: uups.... sorry almost at the same time :D

jdobbs
27th April 2006, 16:59
Sorry if I sound too sceptical -- but I've heard these kinds of reports before and they historically don't prove accurate. Almost all of the processor time during an encode is spent in CCE -- so saying that the frame server can make it that much faster just seems suspect.

Sir Didymus
27th April 2006, 17:13
Sorry if I sound too sceptical -- but I've heard these kinds of reports before and they historically don't prove accurate. Almost all of the processor time during an encode is spent in CCE -- so saying that the frame server can make it that much faster just seems suspect.

Want to second the quoted reply...

It happened to me something similar into a different context; most probably the new decoder is not properly matching with the dgindex project prepared for the previous version, so you are (IMHO) encoding just an avisynth error message, taking very little time to encode, but producing definitely some garbage...

Did you check that the two different sets of m2v files actually contain useful information (the encoded segments of your title) ?

Voodoochild
27th April 2006, 19:05
Want to second the quoted reply...

It happened to me something similar into a different context; most probably the new decoder is not properly matching with the dgindex project prepared for the previous version, so you are (IMHO) encoding just an avisynth error message, taking very little time to encode, but producing definitely some garbage...

Did you check that the two different sets of m2v files actually contain useful information (the encoded segments of your title) ?

I guess you may have a point there...
over all the DVD rb output folder was 2.5g instead of 4.7 or a bit less meaning the encoder could run faster making garbage... unfortunly I can't test it with any other DGDecoder since the dgindex wont match and that would rouin the test...
how ever if any other test that i can do are needed, don't hasitate to ask.
thanks..

l8nights
29th April 2006, 16:47
But Have lot's of Experience with DVD rips.
I used to work and steel do with DVD shrink, How ever I discovered DVD RB, and for heavy compressions.. yes it's the best.
I have some tips that may help some people with error 0006.
1. no matter how you ripped the DVD, Use FixVts at the end, it remove all the garbage, and DVD- RB can rebuild.


sorry to interupt but wondering if this(the quoted text) could/should be added to stickies in some way :)

at least til 1.09.3 is released and tested :goodpost:

jdobbs
29th April 2006, 20:13
Hmmm... the problem is -- I don't know if I agree. I've personally never used FixVTS -- but have never found a disc that couldn't be backed up. Maybe it's just that AnyDVD (which I have never regretted buying for one minute) takes care of it -- I don't know. But I'd hate to recommend adding a step that (at least in my experience) may not be necessary.

How long does it take, btw?

Voodoochild
30th April 2006, 11:40
Hmmm... the problem is -- I don't know if I agree. I've personally never used FixVTS -- but have never found a disc that couldn't be backed up. Maybe it's just that AnyDVD (which I have never regretted buying for one minute) takes care of it -- I don't know. But I'd hate to recommend adding a step that (at least in my experience) may not be necessary.

How long does it take, btw?

on the files inplace
about 3-5 minutes
i had to used it on my Seinfeld DVD and it solve the 0006 error problem, In general I think it's good idea to do this since it get reed of some junk on the dvd.

Now since encoding time takes more then 2 hours, I do not want to get to the rebuilder part only to discover that I have to do the hall process again because I was to lazy to begin with, by fixing the vts, A process that takes 5 minutes.

Again, since then I used dvd-rb to back up Matrix after removing angles shrink menu and cut end credits,
The 5th Element , again shrinking menu, remove end credits, edited pcg commands... used FixVts ----> Result ---->
ABSOLUTE FANTASTIC Compred it with DVD shrink which I steel love but DVD-RB was way better.....in manner of pixelation problem, I love this program... even if i have to use FixVts or other software b4, Finall result that count and again all I can say Thanks jdobbs.

l8nights
30th April 2006, 16:15
Hmmm... the problem is -- I don't know if I agree. I've personally never used FixVTS -- but have never found a disc that couldn't be backed up. Maybe it's just that AnyDVD (which I have never regretted buying for one minute) takes care of it -- I don't know. But I'd hate to recommend adding a step that (at least in my experience) may not be necessary.

How long does it take, btw?

it may not be necessary in most cases like 99.9 but if you recieve the error then is an easy fast fix that is all to necessary.

alway's reccomend it never heard it doesn't work.

I heard that anydvd added this feature (on the fly) as a means to clean up there rips anyway's??

jdobbs
30th April 2006, 17:17
Version 1.09.3 is coming out shortly anyway, and there won't be any #0006 errors anymore -- so it's all academic discussion anyway.

triky40
30th April 2006, 17:43
Hmmm... the problem is -- I don't know if I agree. I've personally never used FixVTS -- but have never found a disc that couldn't be backed up. Maybe it's just that AnyDVD (which I have never regretted buying for one minute) takes care of it -- I don't know. But I'd hate to recommend adding a step that (at least in my experience) may not be necessary.

How long does it take, btw?

I read it somewhere (maybe in Digital Video Forum) that AnyDVD will (maybe did) incorporate FixVTS in their software.

lamster
30th April 2006, 18:00
Just an update on this one.... I don't know how you ripped "Narnia" with DVD Decrypter alone... I tried it and it fails within a minute or so of the start with a read error...
How? I just stuck in the disc and clicked "Decrypt". :sly:

I've gotten back to playing with this. I'm running DVD-RB on one computer against a copy made via the latest DVDFab Decrypter. Tried using DVD Decrypter again on a different computer, just to be sure I'm not confused. This is the "Two-disc Collector's Edition", widescreen, region 1 NTSC. ISBN 0-7888-6826-8; UPC 7-86936-70380-1. Ripped in File mode. Verified that "Ignore read errors" on the I/O tab is not checked.
I 10:42:16 DVD Decrypter Version 3.5.4.0 started!
I 10:42:16 Microsoft Windows 2000 Professional (5.0, Build 2195 : Service Pack 4)
I 10:42:16 Initialising SPTI...
I 10:42:16 Searching for SCSI / ATAPI devices...
I 10:42:16 Found 1 CD-ROM and 1 DVD+RW!
W 10:42:24 Possible Structure Protection Found!
W 10:42:24 2 areas have been marked as 'suspect'.
W 10:42:24 Dummy sectors will be inserted where necessary.
I 10:43:49 Operation Started!
I 10:43:49 Source Device: [1:1:0] HP DVD Writer 200j 1.72 (D:) (ATA)
I 10:43:49 Source Media Type: DVD-ROM
I 10:43:49 Source Media Region Code: 1
I 10:43:49 Source Media Copyright Protection System Type: CSS/CPPM
I 10:43:49 Source Media Application Identifier: GEAR UDF Application
I 10:43:49 Source Media Implementation Identifier: GEAR UDF
I 10:43:49 Destination Folder: E:\DVD_Videos\LSE0NNW1\VIDEO_TS\
I 10:43:49 File Splitting: By File
I 10:43:49 Remove Structure Protection: Yes
I 10:43:49 Bad Sector Removal Method: Normal
I 10:43:49 Detect Mastering Errors: No
I 10:43:49 Multi Angle Processing: No
I 10:43:49 Remove Macrovision Protection: Yes
I 10:43:49 Stream Processing: No
I 10:43:49 Copying VIDEO_TS.IFO... (LBA: 712 - 724) - KEY: N/A
I 10:43:50 Decrypting VIDEO_TS.VOB... (LBA: 725 - 135589) - KEY: C0 00 00 00 01
I 10:45:22 Copying VIDEO_TS.BUP... (LBA: 135590 - 135602) - KEY: N/A
I 10:45:22 Copying VTS_01_0.IFO... (LBA: 135603 - 135671) - KEY: N/A
I 10:45:22 Decrypting VTS_01_0.VOB... (LBA: 135672 - 233093) - KEY: C0 00 00 00 01
I 10:46:35 Decrypting VTS_01_1.VOB... (LBA: 233094 - 757380) - KEY: C0 00 00 00 01
W 10:46:44 Inserting Dummy Sectors... (LBA: 233254 - 233605)
I 10:46:44 Extracting Sectors...
W 10:46:56 Inserting Dummy Sectors... (LBA: 233778 - 236941)
I 10:46:56 Extracting Sectors...
I 10:53:27 Decrypting VTS_01_2.VOB... (LBA: 757381 - 1281667) - KEY: C0 00 00 00 01
I 10:59:59 Decrypting VTS_01_3.VOB... (LBA: 1281668 - 1805954) - KEY: C0 00 00 00 01
I 11:06:36 Decrypting VTS_01_4.VOB... (LBA: 1805955 - 2330241) - KEY: C0 00 00 00 01
I 11:13:10 Decrypting VTS_01_5.VOB... (LBA: 2330242 - 2854528) - KEY: C0 00 00 00 01
I 11:19:42 Decrypting VTS_01_6.VOB... (LBA: 2854529 - 3378815) - KEY: C0 00 00 00 01
I 11:26:15 Decrypting VTS_01_7.VOB... (LBA: 3378816 - 3741162) - KEY: C0 00 00 00 01
I 11:30:49 Copying VTS_01_0.BUP... (LBA: 3741163 - 3741231) - KEY: N/A
I 11:30:49 Copying VTS_02_0.IFO... (LBA: 3741232 - 3741240) - KEY: N/A
I 11:30:50 Decrypting VTS_02_0.VOB... (LBA: 3741241 - 3741846) - KEY: C0 00 00 00 02
I 11:30:51 Decrypting VTS_02_1.VOB... (LBA: 3741847 - 3742266) - KEY: C0 00 00 00 02
I 11:30:51 Copying VTS_02_0.BUP... (LBA: 3742267 - 3742275) - KEY: N/A
I 11:30:51 Copying VTS_03_0.IFO... (LBA: 3742276 - 3742283) - KEY: N/A
I 11:30:52 Decrypting VTS_03_0.VOB... (LBA: 3742284 - 3742470) - KEY: C0 00 00 00 03
I 11:30:52 Decrypting VTS_03_1.VOB... (LBA: 3742471 - 3742914) - KEY: C0 00 00 00 03
I 11:30:53 Copying VTS_03_0.BUP... (LBA: 3742915 - 3742922) - KEY: N/A
I 11:30:53 Copying VTS_04_0.IFO... (LBA: 3742923 - 3742931) - KEY: N/A
I 11:30:53 Decrypting VTS_04_0.VOB... (LBA: 3742932 - 3743118) - KEY: C0 00 00 00 04
I 11:30:54 Decrypting VTS_04_1.VOB... (LBA: 3743119 - 3745827) - KEY: C0 00 00 00 04
I 11:30:56 Copying VTS_04_0.BUP... (LBA: 3745828 - 3745836) - KEY: N/A
I 11:30:57 Copying VTS_05_0.IFO... (LBA: 3745837 - 3745845) - KEY: N/A
I 11:30:57 Decrypting VTS_05_0.VOB... (LBA: 3745846 - 3746032) - KEY: C0 00 00 00 05
I 11:30:57 Decrypting VTS_05_1.VOB... (LBA: 3746033 - 3752527) - KEY: C0 00 00 00 05
I 11:31:03 Copying VTS_05_0.BUP... (LBA: 3752528 - 3752536) - KEY: N/A
I 11:31:03 Copying VTS_06_0.IFO... (LBA: 3752537 - 3752545) - KEY: N/A
I 11:31:03 Decrypting VTS_06_0.VOB... (LBA: 3752546 - 3752732) - KEY: C0 00 00 00 06
I 11:31:04 Decrypting VTS_06_1.VOB... (LBA: 3752733 - 3753524) - KEY: C0 00 00 00 06
I 11:31:05 Copying VTS_06_0.BUP... (LBA: 3753525 - 3753533) - KEY: N/A
I 11:31:05 Copying VTS_07_0.IFO... (LBA: 3753534 - 3753549) - KEY: N/A
I 11:31:05 Decrypting VTS_07_0.VOB... (LBA: 3753550 - 3753736) - KEY: C0 00 00 00 07
I 11:31:06 Decrypting VTS_07_1.VOB... (LBA: 3753737 - 3930289) - KEY: C0 00 00 00 07
I 11:33:19 Copying VTS_07_0.BUP... (LBA: 3930290 - 3930305) - KEY: N/A
I 11:33:19 Copying VTS_08_0.IFO... (LBA: 3930306 - 3930314) - KEY: N/A
I 11:33:20 Decrypting VTS_08_0.VOB... (LBA: 3930315 - 3930501) - KEY: C0 00 00 00 08
I 11:33:20 Decrypting VTS_08_1.VOB... (LBA: 3930502 - 3944212) - KEY: C0 00 00 00 08
I 11:33:31 Copying VTS_08_0.BUP... (LBA: 3944213 - 3944221) - KEY: N/A
I 11:33:31 Copying VTS_09_0.IFO... (LBA: 3944222 - 3944231) - KEY: N/A
I 11:33:31 Decrypting VTS_09_0.VOB... (LBA: 3944232 - 3944418) - KEY: C0 00 00 00 09
I 11:33:32 Decrypting VTS_09_1.VOB... (LBA: 3944419 - 4008418) - KEY: C0 00 00 00 09
I 11:34:20 Copying VTS_09_0.BUP... (LBA: 4008419 - 4008428) - KEY: N/A
I 11:34:21 Operation Successfully Completed! - Duration: 00:50:31
I 11:34:21 Average Read Rate: 2,644 KB/s (1.9x) - Maximum Read Rate: 3,422 KB/s (2.5x)

No read errors.

jdobbs
30th April 2006, 18:06
The only difference I see is that I was using ISO mode and you appear to be using file mode.

layer3maniac
18th May 2006, 05:51
Same problem here with Narnia...

Ripped with DVD Decrypter in iso mode, no reported errors, with "Ignore Read Errors" was unchecked.

No preprocessing, DVD-RB hangs in Rebuild stage with 0006 error.

Shrink has no problems. ???

lamster
18th May 2006, 06:27
You might want to try using the latest DVDFab Decrypter. It worked for me...

jdobbs
18th May 2006, 12:31
Same problem here with Narnia...

Ripped with DVD Decrypter in iso mode, no reported errors, with "Ignore Read Errors" was unchecked.

No preprocessing, DVD-RB hangs in Rebuild stage with 0006 error.

Shrink has no problems. ???Upgrade. There is no such thing as a 0006 error any more. As I have said a couple of hundred times -- Shrink having "no problem" means absolutely nothing. Shrink doesn't have to decode or understand the source at all so it will just pass many source errors through and they will still be there in the output.

layer3maniac
19th May 2006, 03:15
There is no such thing as a 0006 error any more. There is for poor folks.


@ lamster
Thanks, that worked perfectly!

jdobbs
19th May 2006, 04:57
Oh... freeware. It will be gone in the next release.

SAPSTAR
19th May 2006, 22:01
Oh... freeware. It will be gone in the next release.
That's why people should contribute....after all, given the effort driven into this dev, it's really a small compensation...