Some solution for Error: #0003 - buffer overflow ...

[_Payti_]

Hello,
two days ago I tryed backup Alien III and I always (twice) in Rebuild Phase III I got error "DVR Rebuilder experienced a buffer overflow. Error #0003. Process must abort." I read all threads on forum about thats error #0003 and nothing wasn't help me (eg. Special Error Processing, etc.). Then I look into V01.D2V file on \Work Path\D2VAVS folder and I saw:

DGIndexProjectFile06
7
36 E:\ISO\OBCY_IV\VIDEO_TS\VTS_01_1.VOB
36 E:\ISO\OBCY_IV\VIDEO_TS\VTS_01_3.VOB
36 E:\ISO\OBCY_IV\VIDEO_TS\Vts_01_2.vob
36 E:\ISO\OBCY_IV\VIDEO_TS\Vts_01_4.vob
36 E:\ISO\OBCY_IV\VIDEO_TS\Vts_01_5.vob
36 E:\ISO\OBCY_IV\VIDEO_TS\Vts_01_6.vob
36 E:\ISO\OBCY_IV\VIDEO_TS\Vts_01_7.vob

......


When I backuped .vob files from DVD in DVD Decrypter I had too small free space on hard drive and I copy some files to second drive. Then I copy all .vob .ifo and .bup files to VIDEO_TS folder on one partition. When I copied files system must changed names some files with small letters. That was the problem. In all versions DVD-RB procedure finding and sorting .VOB files in VIDEO_TS folder doesn't work fine when files have names with BIG and small letters and always I got error #0003 in Phase III after repeating :(. After that I renamed all files in VIDEO_TS folder to names with BIG letters and problem goes one :) No more error #0003 in Rebuild Phase III ;)

After that into V01.D2V file created by repeated Prepare Phase I
I saw:

DGIndexProjectFile06
7
36 E:\ISO\OBCY_IV\VIDEO_TS\VTS_01_1.VOB
36 E:\ISO\OBCY_IV\VIDEO_TS\VTS_01_2.VOB
36 E:\ISO\OBCY_IV\VIDEO_TS\VTS_01_3.VOB
36 E:\ISO\OBCY_IV\VIDEO_TS\VTS_01_4.VOB
36 E:\ISO\OBCY_IV\VIDEO_TS\VTS_01_5.VOB
36 E:\ISO\OBCY_IV\VIDEO_TS\VTS_01_6.VOB
36 E:\ISO\OBCY_IV\VIDEO_TS\VTS_01_7.VOB

......


No more error #0003 after Encode in Rebuild Phase III ;)

How check files if are have BIG/small letters in names? In VIDEO_TS folder run cmd.exe then put "dir" command and look all files names and if need correct them to names with all BIG letters :) (mayby Prepare Phase I work good with all names with small letters, I don't tryed it).

To author DVD-RB: Mayby will be good idea to change precedure of finding/sorting .VOB files in Prepare Phase I? I'll feel grateful if You do that :)

Regards with no more error #0003 :)

Payti

[jdobbs]

Now that is interesting. I can't understand is how the got renamed... but they obviously did. I'll modify DVD-RB to look for misnamed input files and catch it before sorting the input...

Thanks!

[_Payti_]

I think that is some bug in copying software whitch I used and names of files was changed to small letters :(.

Thanks for future modify! DVD-RB is very good DVD rebuilding software!

Regards,

[jdobbs]

Thanks. :)

[jamos]

I am getting the same error in 1.09 in phase 3. nothing wrong with my names..though my vobs are 2 gig. instead of 1 gig. I am sure rebuilder can handle this right (note: in 1.08 I do not get this error)?

[jdobbs]

Look in your log and see if you are have segments that are missing lots of frames... it sounds like the encoder is crashing.

Also, are you preprocessing? Incorrect preprocessing is almost always the cause of #0003 buffer overflows. It's usually the result of incorrect removal of portions of video.

[jamos]

Look in your log and see if you are have segments that are missing lots of frames... it sounds like the encoder is crashing.

Also, are you preprocessing? Incorrect preprocessing is almost always the cause of #0003 buffer overflows. It's usually the result of incorrect removal of portions of video.
I did remove some video with dvd remake pro, ie split a cell deleted new split part. but I have done this before. could this be a bug in dvd remake pro do you think..ie should i have removed the program too?

[jdobbs]

Can't say what may or may not have caused it... only that th #0003 means there is a timing discrepancy.

[jamos]

Can't say what may or may not have caused it... only that th #0003 means there is a timing discrepancy.
Ok thanks, I will try ifo edit and create new ifos for the vobs and see if that fixes it.

[jdobbs]

I don't think it will. The problem is in the VOBs.

[jamos]

I don't think it will. The problem is in the VOBs.
thanks, I will do a mock strip of the vobs with ifo edit and see if that fixes it.

[jamos]

no fix for the mock strip it seems to always abort on the same cell though. does rebuilder care if my vobs are 2 gig.? Nero recode seems to handel it fine..would like to be able to use rebuilder pro and better encoders.

[jdobbs]

How did you get 2Gig VOB files? That's definitely not kosher... But I don't know if that's the problem... #0003 means there is a huge timing gap in the source....

[jamos]

How did you get 2Gig VOB files? That's definitely not kosher... But I don't know if that's the problem... #0003 means there is a huge timing gap in the source....
easy and quite neccesary if you want to join two dvd-9s onto one disk with no compression to be playable from your harddrive :}

I use ifoedit strip the streams use custom 1 for my vob size which i set to 2 gig in the ini file. that way i avoid the 10 and above issue with vob names. all my computer dvd players play this fine no skipping etc.

ok even with using 1 gig vobs (14 of them) something is still not kosher here. using all default settings cce it seems to extract stills for seg 43 for some odd reason..and its not always the same segment (tried different computer and different encoder). this is still running but I am sure when i get to this segment on rebuild it will give me a #0003 error.

Is there a limit to the number of segments that dvdrb can handle?

[jdobbs]

It's not unheard of for a STILL to be in a VTS...

I think your source is hosed. You really need to do an encode with no preprocessing at all...

I don't think the 2gig files will be a problem... but if you go one byte over two gig is probably will (because of the 32 bit limit for pointers).

[jamos]

thanks jdobbs..

somethings going on it almost finished this time with 1 gig vobs but still i got a different error on phase 3. Must be the source because I have done this before with two dvds and had no issues doing this.

Log for dvd-9 build

19:55:58] One Click encoding activated...
-----------------
[19:55:59] Phase I, PREPARATION started.
- CCE 2.70.2.4 encoder selected.
- VTS_01: 4,717,266 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 289,779 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 60.8%
- Overall Bitrate : 3,753/3,002Kbs
- Space for Video : 4,429,472KB
- HIGH/LOW/TYPICAL Bitrates: 4,001/393/3,002 Kbs
[19:59:31] Phase I, PREPARATION completed in 4 minutes.
[19:59:31] 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
- Extracting STILLS for VTS_01 segment 43
- Creating M2V for VTS_01 segment 44
- Creating M2V for VTS_01 segment 45
- Creating M2V for VTS_01 segment 46
- Creating M2V for VTS_01 segment 47
- Creating M2V for VTS_01 segment 48
- Creating M2V for VTS_01 segment 49
- Creating M2V for VTS_01 segment 50
- Creating M2V for VTS_01 segment 51
- Creating M2V for VTS_01 segment 52
- Creating M2V for VTS_01 segment 53
- Creating M2V for VTS_01 segment 54
- Creating M2V for VTS_01 segment 55
- Creating M2V for VTS_01 segment 56
- Creating M2V for VTS_01 segment 57
- Creating M2V for VTS_01 segment 58
- Creating M2V for VTS_01 segment 59
- Creating M2V for VTS_01 segment 60
- Creating M2V for VTS_01 segment 61
- Creating M2V for VTS_01 segment 62
- Creating M2V for VTS_01 segment 63
- Creating M2V for VTS_01 segment 64
- Creating M2V for VTS_01 segment 65
- Creating M2V for VTS_01 segment 66
- Creating M2V for VTS_01 segment 67
- Creating M2V for VTS_01 segment 68
- Creating M2V for VTS_01 segment 69
- Creating M2V for VTS_01 segment 70
- Creating M2V for VTS_01 segment 71
- Creating M2V for VTS_01 segment 72
- Creating M2V for VTS_01 segment 73
- Creating M2V for VTS_01 segment 74
- Creating M2V for VTS_01 segment 75
- Creating M2V for VTS_01 segment 76
[23:14:48] Phase II ENCODING completed in 195 minutes.
[23:14:49] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 4 VOBID 2 CELLID 4
- Rebuilding seg 5 VOBID 2 CELLID 5
- Rebuilding seg 6 VOBID 2 CELLID 6
- Rebuilding seg 7 VOBID 2 CELLID 7
- Rebuilding seg 8 VOBID 2 CELLID 8
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 9 VOBID 3 CELLID 8
- Rebuilding seg 10 VOBID 3 CELLID 9
- Rebuilding seg 11 VOBID 3 CELLID 10
- Rebuilding seg 12 VOBID 3 CELLID 11
- Rebuilding seg 13 VOBID 3 CELLID 12
- Rebuilding seg 14 VOBID 3 CELLID 13
- Rebuilding seg 15 VOBID 3 CELLID 14
- Rebuilding seg 16 VOBID 3 CELLID 15
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 17 VOBID 4 CELLID 15
- Rebuilding seg 18 VOBID 4 CELLID 16
- Rebuilding seg 19 VOBID 4 CELLID 17
- Rebuilding seg 20 VOBID 4 CELLID 18
- Rebuilding seg 21 VOBID 4 CELLID 19
- Rebuilding seg 22 VOBID 4 CELLID 20
- Rebuilding seg 23 VOBID 4 CELLID 21
- Rebuilding seg 24 VOBID 4 CELLID 22
- Rebuilding seg 25 VOBID 4 CELLID 23
- Rebuilding seg 26 VOBID 4 CELLID 24
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 27 VOBID 5 CELLID 24
- Rebuilding seg 28 VOBID 5 CELLID 25
- Rebuilding seg 29 VOBID 5 CELLID 26
- Rebuilding seg 30 VOBID 5 CELLID 27
- Rebuilding seg 31 VOBID 5 CELLID 28
- Rebuilding seg 32 VOBID 5 CELLID 29
- Rebuilding seg 33 VOBID 5 CELLID 30
- Rebuilding seg 34 VOBID 5 CELLID 31
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 35 VOBID 6 CELLID 31
- Rebuilding seg 36 VOBID 6 CELLID 32
- Rebuilding seg 37 VOBID 6 CELLID 33
- Rebuilding seg 38 VOBID 6 CELLID 34
- Rebuilding seg 39 VOBID 6 CELLID 35
- Rebuilding seg 40 VOBID 6 CELLID 36
- Rebuilding seg 41 VOBID 6 CELLID 37
- Updating NAVPACKS for VOBID_06
- Rebuilding seg 42 VOBID 7 CELLID 37
- Updating NAVPACKS for VOBID_07
- Rebuilding seg 43 VOBID 8 CELLID 1
- Updating NAVPACKS for VOBID_08
- Rebuilding seg 44 VOBID 9 CELLID 1
- Rebuilding seg 45 VOBID 9 CELLID 2
- Rebuilding seg 46 VOBID 9 CELLID 3
- Rebuilding seg 47 VOBID 9 CELLID 4
- Rebuilding seg 48 VOBID 9 CELLID 5
- Rebuilding seg 49 VOBID 9 CELLID 6
- Rebuilding seg 50 VOBID 9 CELLID 7
- Updating NAVPACKS for VOBID_09
- Rebuilding seg 51 VOBID 10 CELLID 7
- Rebuilding seg 52 VOBID 10 CELLID 8
- Rebuilding seg 53 VOBID 10 CELLID 9
- Rebuilding seg 54 VOBID 10 CELLID 10
- Rebuilding seg 55 VOBID 10 CELLID 11
- Rebuilding seg 56 VOBID 10 CELLID 12
- Rebuilding seg 57 VOBID 10 CELLID 13
- Updating NAVPACKS for VOBID_10
- Rebuilding seg 58 VOBID 11 CELLID 13
- Rebuilding seg 59 VOBID 11 CELLID 14
- Rebuilding seg 60 VOBID 11 CELLID 15
- Rebuilding seg 61 VOBID 11 CELLID 16
- Rebuilding seg 62 VOBID 11 CELLID 17
- Rebuilding seg 63 VOBID 11 CELLID 18
- Rebuilding seg 64 VOBID 11 CELLID 19
- Rebuilding seg 65 VOBID 11 CELLID 20
- Rebuilding seg 66 VOBID 11 CELLID 21
- Rebuilding seg 67 VOBID 11 CELLID 22
- Rebuilding seg 68 VOBID 11 CELLID 23
- Updating NAVPACKS for VOBID_11
- Rebuilding seg 69 VOBID 12 CELLID 23
- Rebuilding seg 70 VOBID 12 CELLID 24
- Rebuilding seg 71 VOBID 12 CELLID 25
- Rebuilding seg 72 VOBID 12 CELLID 26
- Rebuilding seg 73 VOBID 12 CELLID 27
- Rebuilding seg 74 VOBID 12 CELLID 28
- Rebuilding seg 75 VOBID 12 CELLID 29
- Rebuilding seg 76 VOBID 12 CELLID 30
- Updating NAVPACKS for VOBID_12

[jdobbs]

That means the IFO is referencing a cell that is completely missing.

[jamos]

That means the IFO is referencing a cell that is completely missing.
Thats what it looks like but the cell is there. like I said this movie works fine with powerdvd, winddvd6, dvdremake, and recode. I am not sure what is going on going to start over from scratch with the original two dvds.

1st step rip.
2nd step copy only main title vobs over to directory rename 001-014 run vobedit and join.
3rd step run ifoedit create ifos on new vobs.
4th step use vob extras to strip vobs clean up ifo and reset pointers etc and make vobs a little smaller than 2 gig to get to under 10 total vobs using custom 1 (size set by editing ifoedit.ini).
5th step use pgcedit to remove extra chapters and set seemless (leaving cells alone).
6th step rename streams and copy subtitle colors with pgcedit or ifoedit.
7th step run either recode, remakepro, or rebuilderpro to fit to target size.

[jdobbs]

I'm sorry -- but there are way too many possibilities for problems in that scenario. A small mistake anywhere along the way and I wouldn't be able to predict what might happen.

I can assure you that if DVD-RB tells you that the cell is missing --- it is missing. It's possible that it was given a different VOBID/CELLID and orphaned the reference or any of several other possibilities... but the referenced cell doesn't exist.

Players have the luxury of being able to ignore lots of problems. If a reference to a cell points to a sector that doesn't have the correct ID -- no big deal, it can keep playing whatever happens to be at that sector. But a authoring package needs a cell to exist in order to put it in the correct sequence.

[jdobbs]

Can you send me a listing of the D2VAVS directory to dvd-rb@dvd-rb.com? Please make sure it shows the file sizes as well as names.

[jamos]

I'm sorry -- but there are way too many possibilities for problems in that scenario. A small mistake anywhere along the way and I wouldn't be able to predict what might happen.

I can assure you that if DVD-RB tells you that the cell is missing --- it is missing. It's possible that it was given a different VOBID/CELLID and orphaned the reference or any of several other possibilities... but the referenced cell doesn't exist.

Players have the luxury of being able to ignore lots of problems. If a reference to a cell points to a sector that doesn't have the correct ID -- no big deal, it can keep playing whatever happens to be at that sector. But a authoring package needs a cell to exist in order to put it in the correct sequence.

I agree that ifoedit has been known to randomly give errors like this.

[seagame2009]

[20:23:55] Phase I, PREPARATION started.
- CCE 2.70.2.0 encoder selected.
- AVS Filters are enabled.
- VTS_01: 4,159,386 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 454,865 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 51.1%
- Overall Bitrate : 2,179/1,743Kbs
- Space for Video : 4,036,528KB
- HIGH/LOW/TYPICAL Bitrates: 1,796/1,714/1,743 Kbs
[20:37:37] Phase I, PREPARATION completed in 14 minutes.
[20:37:42] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
-- V01000100001001 empty .M2V, retrying.
- Creating M2V for VTS_01 segment 1
-- V01000100001001 empty .M2V, retrying.
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
-- V01000300002001 empty .M2V, retrying.
- 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
-- V01001300005001 empty .M2V, retrying.
- 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
-- V01001700006001 empty .M2V, retrying.
- Creating M2V for VTS_01 segment 17
-- V01001700006001 empty .M2V, retrying.
- Creating M2V for VTS_01 segment 17
-- Zero length .M2V file for V01001700006001.

I had zero lenght .m2v file
Any idea why?
I tried to re-author my DVD file two times already and run DVDRB again but nothing change after that

[jdobbs]

That usually means CCE is crashing in the first pass. Most typically it is caused by an overclocked system... but it could actually be from any system instability.

CCE really puts your system to the test in terms of memory and processor usage. It will find problems that even the "system checkers" won't find.

[jamos]

Ok found out it was dvdremakepro that was causing the buffer overflow issue, corrected it with ifoedit and stripping the vobs, after (not before like i was doing) running dvdremake to cut some vobs. Now all is good.

[Boulder]

I just had this infamous error with R2 "Jeeves and Wooster season 1" Nordic release, disc 1. I tried encoding with both HC and CCE with no luck. No preprocessing whatsoever..and no dropped frames either.

[jdobbs]

Hmmm... I've never seen this error happen on a source that wasn't preprocessed or had sections missing. Is there any chance you may have had something set in DVD Decrypter (for example) that removes anything?

[Boulder]

I've only set it to remove those PUO protections etc, but I just tried reripping the disc with all protection removals disabled and will try re-encoding the disc.

FYI, NaN's DGDecode v1.10 had problems with the videos - DGDecode 1.4.5 works - so it could be that the source is just bad.

[jdobbs]

So the problem goes away with v1.4.5? That's interesting. While I've see v1.1.0 hang on a couple of sources (a field oriented picture structure as I recall), I don't think I've seen it cause a #0003 error.

[spiffy]

Sorry if I should have started a new thread instead -- but I've been getting "Runtime Error 203 at xxxxxx" messages during my sessions -- is this the same as Error 003? I tried searching to see if others have the same issues, but there doesn't seem to be any mentioning of Runtime Error 203. I seem to get this when I have a fairly large files to process -- 6.5/7 GB and more -- however, the end product looks OK though. My settings are as followed:

P4 3.0Ghz, 1 GB RAM
Ripped using Decrypter
DVD-RB 0.96 and 0.97 (got the error on both versions, using full installers and the included plug-ins)
One Click Mode
CCE Trial 2.7

And DVD-RB log didn't report any errors either. So I am not sure if this is even a problem? But seeing the error message makes me think there was a problem with the session.

Thanks so much for your help

[jdobbs]

I've never even heard of a "Runtime Error 203". I did a google search and got a range of possibilities ranging from firewall software to the registry... It seems the general consensus, though, is that it is coming from the O/S and it is triggered by memory problems. Is your memory overclocked by any chance (via FSB for example)?

When you say "fairly large files to process" -- are you talking about "files" or "directories"?

I'm pretty sure this error is not related to DVD-RB except possibly by the fact that the encoder can use a lot of memory. The lack of other reports is also a good indicator that it is peculiar to your computer.

[spiffy]

I've never even heard of a "Runtime Error 203". I did a google search and got a range of possibilities ranging from firewall software to the registry... It seems the general consensus, though, is that it is coming from the O/S and it is triggered by memory problems. Is your memory overclocked by any chance (via FSB for example)?

When you say "fairly large files to process" -- are you talking about "files" or "directories"?

I'm pretty sure this error is not related to DVD-RB except possibly by the fact that the encoder can use a lot of memory. The lack of other reports is also a good indicator that it is peculiar to your computer.

No, the memory is not overclocked as far as I know.

When I said large files, I meant the total file size in the video_ts directory.

This is a recent occurance; the ONLY thing I have changed to my system is updating some software, none of which is running at the time of the RB sessions -- except a Microsoft Intellipoint software for my mouse that is a different version than what I used to have. So I am going to revert to the old version and see if that makes any difference...

[jdobbs]

Not sure what "old version" you could mean. Your report says you get the error with both v0.96 and v0.97 -- v0.96 was released last November...

[Rippraff]

Not sure what "old version" you could mean.
I think he's talking about old version of his Microsoft intellipoint software. ;)
But I doubt that this will have any effect.

Cu Rippraff

[jdobbs]

Ahhh... that makes sense. I wish I'd learned how to read when I was in school.

[Rippraff]

I wish I'd learned how to program when I was in school. :p

Cu Rippraff

[Capsbackup]

I'm just glad to be a member of your class in this school.

[Boulder]

So the problem goes away with v1.4.5? That's interesting. While I've see v1.1.0 hang on a couple of sources (a field oriented picture structure as I recall), I don't think I've seen it cause a #0003 error.
Ah, sorry, I should have been more precise.

1) The buffer overflow problem occurs with both decoders.

2) NaN's DGDecode had problems with one segment which caused errors when encoding.

I reripped the DVD in ISO mode this time and mounted it via Daemon Tools. The disc is not protected at all, I also disabled all PUO removals etc. in DVD Decrypter. I haven't had the time to finish the backup process yet but I'll report as soon as it's done.

I somehow suspect that the source is pretty flaky itself. I've seen several releases from the same authoring house and have not been impressed at all.

[Boulder]

Looks like disabling the PUO removals etc. (or ripping to ISO) fixed things as now it works:)

[jdobbs]

Wow. That's one I never would have guessed...