DVD-RB Error #0004 (merged)

[scioper]

hi

at first thanks for the time spent on this app

unfortunetally like many folks im having the same error(both with 052 053)
It happens while the last stage (rebuilding) is about 50% done

im working on

amd xp 1800
256 mb of ram
nvidia gfx
(if that matters :) )

i use the basic version of cce (retail)
i have the latest avisynth
and the material has been stripped of the protection cy Decrypter

I have only tried one title with the same result every time:devil:

its Matrix reloaded rc2

take care

[thesicilian]

Originally posted by scioper
hi

at first thanks for the time spent on this app

unfortunetally like many folks im having the same error(both with 052 053)
It happens while the last stage (rebuilding) is about 50% done

im working on

amd xp 1800
256 mb of ram
nvidia gfx
(if that matters :) )

i use the basic version of cce (retail)
i have the latest avisynth
and the material has been stripped of the protection cy Decrypter

I have only tried one title with the same result every time:devil:

its Matrix reloaded rc2

take care

Please confirm which version of CCE Basic you are using. Also please post which versions of dvd decrypter & DVD-RB.

[scioper]

Originally posted by thesicilian
Please confirm which version of CCE Basic you are using. Also please post which versions of dvd decrypter & DVD-RB.

U got it

cce basic is 2.69.01.06
dvd decryper well (does it really matter) was downed like 2 weeks ago (im not on my home pc right know)
DVD-rb both 0.52 and 0.53 (both mentioned in my first post)

avisynth is above 2.5 also downed bout 2 weeks ago

[thesicilian]

Try upgrading to the newest CCE Basic first.

[scioper]

Originally posted by thesicilian
Try upgrading to the newest CCE Basic first.


mine is the latest
http://www.cinemacraft.com/eng/download.html#basic

:)

[thesicilian]

Originally posted by scioper
mine is the latest
http://www.cinemacraft.com/eng/download.html#basic

:)

Not its not, latest is 2.69.01.09

If you have a legit license for it you can download the update.

[scioper]

Originally posted by thesicilian
Not its not, latest is 2.69.01.09

If you have a legit license for it you can download the update.


oh sorry

will do that


thanks

but i doubt thta this is the issue here

take care

[Gurm]

I think it would be helpful if those of us experiencing the problem on ONLY ONE OR TWO DISCS (not those who are having it on EVERY disc) were to:

1. Make sure that we have the latest versions of CCE, DVD Decryptor, and DVD-RB, all the correct libraries, etc.

and then...

2. Make a list (perhaps in another topic) of which movie(s) fail(s), and at what point in the final phase.

We should DEFINITELY try to be helpful to jdobbs on this one, since there's clearly some irksome thing that happens only on certain films in certain spots that is killing his code, and he clearly wasn't expecting it and/or hasn't managed to replicate it himself.

And we should DEFINITELY separate the issues here. Those people that are CONSISTENTLY getting this error with EVERY film are simply misconfigured. End of story. They can insist that they aren't, but getting this error on every film is just misconfiguration. However, there are certainly plenty of us who get it on ONE film, or TWO films out of the dozens that we've tried... and we should make a little list and see if we can't help jdobbs figure it out.

Whaddya all think?

- Gurm

[thesicilian]

I was getting it on every rip untill I stopped using CCE Basic 2.69.01.04. Started using CCE2.5 SP with eclcce & it worked great. After my experiance I would defo say its a config problem.

[Sir Didymus]

Originally posted by Gurm
I think it would be helpful if those of us experiencing the problem on ONLY ONE OR TWO DISCS (not those who are having it on EVERY disc) were to:

1. Make sure that we have the latest versions of CCE, DVD Decryptor, and DVD-RB, all the correct libraries, etc.

and then...

2. Make a list (perhaps in another topic) of which movie(s) fail(s), and at what point in the final phase.

We should DEFINITELY try to be helpful to jdobbs on this one, since there's clearly some irksome thing that happens only on certain films in certain spots that is killing his code, and he clearly wasn't expecting it and/or hasn't managed to replicate it himself.

And we should DEFINITELY separate the issues here. Those people that are CONSISTENTLY getting this error with EVERY film are simply misconfigured. End of story. They can insist that they aren't, but getting this error on every film is just misconfiguration. However, there are certainly plenty of us who get it on ONE film, or TWO films out of the dozens that we've tried... and we should make a little list and see if we can't help jdobbs figure it out.

Whaddya all think?

- Gurm

At the end, since many days, I read something that is very reasonable, in mo, on the subject.

I quote, and share all what you wrote EXCEPT the following statement:

-- However, there are certainly plenty of us who get it on ONE film, or TWO films out of the dozens that we've tried... --

I am very curious to know how many people are still suffering from #0004 with a straight backup [I mean no preprocessing] of any title...

Cheers,
SD

[jdobbs]

So am I.

[Axlemar]

I tried to backup a couple of dvds made from tmpgenc dvd author, simple menus and no protection, and still got this error. The newer versions of dvdrb, .50+, have been giving me 0004 on many of the dvds I have tried. Right now I have been trying to backup dvds with the newest version of cce basic 2.69.01.09, the newest dvdrb .54, newest avisynth 2.55 alpha that just came out, mpeg2dec3dg v1.0.1.0, and anydvd 3.8.1.3. It seems this problem is related to the dvd structure so anydvd might be what is causing it for me, since I have removed user prohibitions from the dvds I have tried to backup. I will mess with different versions of avisynth and see if the steal from extras option may be messing it up. Please let me know if there is anything else I should try.

btw: cce seems to be encoding too quickly (if i set the passes to anything it does 2) and avisynth doesn't let me do simple idct even though I have a new enough mpeg2dec3 to support it, gives me the error "there is no function named mpeg2source." Does this mean I can't use the simple idct feature? isn't it supposed to be better? Thanks for your time.

[jdobbs]

1. Have you been getting this on commercial DVDs?
2. Have you also had successful backups?

It sounds like you may possibly not be pointing to the MPEG2DEC3dg.dll file that you think you are... have you set the explicit path to the file in DVD-RB's setup? If not, try that. Also click the "Add To AVS" checkbox.

Also -- remember that AVISYNTH 2.55 is still in Alpha status, so you are taking a chance using it...

[Gurm]

Well I for one am still seeing the #0004 error on ONE commercial DVD - Paycheck.

And I know there are others who have posted in this thread (speak up, guys!) who have seen it in ONE movie or TWO movies out of the dozens they've done... scroll back up. :)

- Gurm

[Piaf]

:( same error for me
the previous error i posted is fixed now in 0.54

error: "DVDRB experienced a buffer overflow,error #0004,process must abort" this happens on rebuilding the disc(i used 1click-mode this time on same movie)

tools:
dvdrb 0.54
dvd-decrypter 3.2.2.0 -ISO-mounted whit daemontools 3.44
cce2.96.04.01( full)
eclcce: No
The movie: Master and Commander original R2 disc.

btw: when the error apears its rebuilding and it seems to have problems building the files back up?! i checked the VIDEO_TS folder and its 1.10GB.

gonna try same disc on older dvdrb version and put cce2.96.04.01 aside and testing it whit older 2.50/2.67
ill report back
=======================================================================
alright did same movie whitout errors on the way!:
dvdrb 0.50a
dd 32.2.0/mounted whit daemon 3.44
cce 2.67.0.23
eclcce: Yes >>eclcce 1.8b
Master and Commander R2
came out 4.31Gb

let me test some more whit latest 0.54 and cce2.67 instead of 2.69 see if thats make any diff.

its either a bug whit cce 2.69 and/or dvdrb 0.54?

[Axlemar]

adding the mpeg2dec3dg to avs file has allowed me to use simple idct, even though the only mpeg2dec3 file I could find on my system was 1.0.1.0. Using avisynth 2.54 or 2.55 doesn't seem to make a difference, I still get 0004. I have tried not using steal space and simple idct and I have messed with turning the dynamically assign cell bitrates feature on and off while using the different versions of avisynth. Also, the newest version of cce basic still doesn't do the right number of passes I have set it to which leads me to believe that this issue has something to do with the current version of cce basic. The avs files that would normally tell me if something was wrong with an avisynth setting just play the movie segment instead while using either version of avisynth. Has anybody backed up using dvdrb and anydvd? Please let me know if you have any more ideas to what might be the problem.

[Axlemar]

ok ran more tests using rejig and quenc with many different settings and different versions of avisynth on same dvd that cce basic was failing on. All of them worked with no errors on rebuild stage. It seems the 0004 errors are being caused from an incompatibility between dvdrb and cce 2.69 basic and newer. They have updated the engine in the newer versions of cce basic, so I guess you should try to use the new 2.69 basic and see if you get the 0004 error as well. Thank you for your time and I hope that I am right and that this helps.

[scioper]

btw: when the error apears its rebuilding and it seems to have problems building the files back up?! i checked the VIDEO_TS folder and its 1.10GB.



the same here


and bout the couse of those errors being the miscofiguration of RB
well as i am not an experienced ripper so this could be the issue but i did do everything as in the guide on dooms guides


i will try it though with sp

[Lazza]

First time I've had this error after about 50 trouble free backups but it was not at the rebuild stage but 25% into encode.

tools:
dvdrb 0.54
dvd-decrypter 3.2.2.0
cce2.50 (25/16 - Set to 3 pass)
eclcce: yes

Film was:- Warming by the Devil's Fire. Pal

[Axlemar]

Lazza, if you can try to update your cce basic to 2.69 and see if you still don't get the 0004 error during rebuild.

[Lazza]

Originally posted by Axlemar
Lazza, if you can try to update your cce basic to 2.69 and see if you still don't get the 0004 error during rebuild.
Not running basic. 2.50 SP

[robot1]

Originally posted by Axlemar
Also, the newest version of cce basic still doesn't do the right number of passes I have set it to which leads me to believe that this issue has something to do with the current version of cce basic. CCE Basic (all versions) supports only two passes. If you set more passes, it still does two. That's OK: it's a limit of the Basic version.

[Piaf]

Hi back from testing its a sunny day so a bit later posting update;)

All is good whitout CCE 2.69, i tested the same movie whitout problems using cce2.67, i'm sure cce2.50SP works to.

tools used:

dvdrb 0.54
dd 3.2.2.0/ISO mounted whit daemon-tools 3.44
cce 2.67.0.23
eclcce: yes eclcce 1.8b
avisynth 2.54
Master and Commander R2 original 6,77Gb

came out perfect @ 4.31Gb

so i'm sure its a CCE 2.69 bug not dvdrb0.54:)

[scioper]

ok did some testing

as i said before with basic cce i was having this 0004 issue during rebuiulding

i have tested RB with a trial :) Sp and everything came out perfect

so its either a bug of RB or cce or simply a incomatibility issue

take care

[wmansir]

I was just reading "rule 6 (http://forum.doom9.org/forum-rules.htm)" ;)

[scioper]

Originally posted by wmansir
I was just reading "rule 6 (http://forum.doom9.org/forum-rules.htm)" ;)

rule states:"6) No warez, cracks, serials or illegally obtained copyrighted content! Links to content of a questionable nature, asking for, offering, or asking for help/helping to process such content in any way or form is not tolerated."

90 proc of the rule doesnt apply to me post but a agree to:
"illegally obtained copyrighted content"
so sorry for this i will edit my post :)

[tin2019]

Hi, I subscribed to this forum so I can report what I found. Didn't really have time to read through all of the latest posts, so you will excuse if somebody already found out the same thing.

When I first tried DVD-RB I got the same error (#0004) during the "rebuild" phase. The error appeared on two DVDs, but in different times during the rebuild phase.

Later I found out that my CCE (I have several versions) does not finish encoding long movie clips but just stops (without any error) after encoding about 2 minutes and 56 seconds of the clip. I went on to see on which m2v file DVD-RB reported the #0004 error and as far as I can see that file has not been encoded till the end, but instead it has been cut at a certain point.

I have tried CCE on a couple of more clips and noticed that my mem-usage has exceeded the limit in paging files which caused CCE to stop encoding.

This could explain why some people experience the #0004 error and some do not.

I don't have time right now to play with this, but if anyone is willing, please be my guest

Hope this helps

[butterfm]

Hi,

I've been following this forum for a while but this is my first post.

Firstly I would like to congratulate jdobbs on a quality product. The final result surpasses any other DVD backup utility I've used by a considerable margin. The wait is well worth it.

I too encountered the #004 error in the rebuild phase while using CCE SP 2.69. I re-installed and re-configured a number of times but to no avail. The error still occured.

I then switched to CCE SP 2.67 with the same DVD-RB configuration and it woked perfectly.

I would aggree with some of the other posters on this forum that there is either a bug in the CCE SP 2.69 or some incompatibility issues with DVD-RB.

Matt.

[Sir Didymus]

@tin2019:
:goodpost:

At least there is a specific hypothesis that could explain the source of #0004...

@Gurm, and other people that are experiencing the same error:

An implication of the same post is that the reason of the error could be the wrong number of total frames encoded by CCE for some specific cells. But this should be easy to verify using VirtualDubMod (or any other tool capable of counting quickly the total nr of frames in a m2v file). In the offending cell, the reported total number of frames in the encoded m2v file should be different from the number reported in the trim statement for the corresponding AVS file:

Total nr of frames ?=? (Trim.last - Trim.first + 1)

If this applies, it could be also very useful for jdobbs, in the form of a kind suggestion for including this test, as a sanity check, into the application...

Cheers,
SD

[Sir Didymus]

Trying to reproduce the behaviour of DVD-RB in presence of this error, I substitute one of the m2v produced in the encode step with another file, extracted from it, cutting out the last two frames...

:scared:

I was really surprised to see that no error was generated...

Then I was even more bad, cutting out more than ten seconds of movie from the end of the encoded cell...

Even in this case the rebuild step completed flawlessly...

What do you think about ?

:confused:

EDIT: of course I didn't burn it, but the play on my PC is not so jerky...

[jptheripper]

Originally posted by Sir Didymus
@tin2019:
:goodpost:

At least there is a specific hypothesis that could explain the source of #0004...

@Gurm, and other people that are experiencing the same error:

An implication of the same post is that the reason of the error could be the wrong number of total frames encoded by CCE for some specific cells. But this should be easy to verify using VirtualDubMod (or any other tool capable of counting quickly the total nr of frames in a m2v file). In the offending cell, the reported total number of frames in the encoded m2v file should be different from the number reported in the trim statement for the corresponding AVS file:

Total nr of frames ?=? (Trim.last - Trim.first + 1)

If this applies, it could be also very useful for jdobbs, in the form of a kind suggestion for including this test, as a sanity check, into the application...

Cheers,
SD


excellent hypothesis. If this is the case it might be easy to isolate problem and avoid, in some type of logic sequence

if total frames should = 1000
and encoded m2v frame = 450
then reprocess avs with trim (1,450) and (450,1000) (or whatever) using same parameters.
If still problem, then do 1-449 and 501-1000 and do 450 and 451 (or whatever offending frame is) as still cell

only problem i see is naming scheme as this would add a sub cell.

hmm

am i babbling?

-JP

[TheSeeker]

Where could I find a trial version of CCE SP 2.67.00.23?? Just wondering cause I wanted to try it and see if it fixed my own error #0004 problems?

EDIT: Nevermind I found it. Hope it takes care of my errors.

[jdobbs]

I'd like to remind everyone what error #0004 means so we don't go off in wild directions.

1. As DVD-RB is reconstructing the DVD is is pulling in video from the newly created M2V files. It packetizes them using proper DVD specifications and generates Navigation Packs for them.

2. As it is bringing in the video it calculates proper presentation timestamps and system clock references.

3. The packetized video is prepared to be added to the output VTS, but first the original VTS is scanned to get the next available non-video packet (audio/subpicture) that is not identified for removal. The non-video packet will have a timestamp also associated with it.

4. In the output stream either the video, or the audio/subpicture is added depending upon which has the lower timestamp (please note there is a lot more to it in terms of timing -- I'm simplifying).

5. For very good technical and performance reasons, DVD-RB buffers packets so that an entire GOP is available in memory at a given point.

6. When the last video packet for a particular cell is added, DVD-RB make one last scan for remaining audio/subpicture packet within that cell so it can be flushed into the buffer.

Error 0004 occurs when there is such a huge number of remaining audio/subpicture packets that they cannot fit in the available buffer or the timestamp has been corrupted.

[TheSeeker]

So based on that what is the fix? To increase the buffer somehow? Or is it just that for some reason or another the m2v file in question got corrupted?

[jdobbs]

It's not the buffer size. It is ridiculously large already.

What I'm trying to say is that something else is wrong with your source when you get this error, it isn't DVD-RB. Don't shoot DVD-RB, it is only the messenger.

There was a DVD-RB error related to 0004 that was fixed long ago. I have done many, many discs and I haven't gotten a 0004 error in any of the last several versions. If someone could point me to one single NTSC disc that will cause this error as it comes off the shelf (no modifications with other 3rd party software) I will go out, buy it, and fix the error. I haven't been able to find one that has failed yet.

This seems to happen exclusively when a third party stripper has been used. Which I have very clearly stated I cannot, nor would attempt to try and debug.

[scioper]

If someone could point me to one single NTSC disc that will cause this error as it comes off the shelf
This seems to happen exclusively when a third party stripper has been used. Which I have very clearly stated I cannot, nor would attempt to try and debug. [/B]

the error happend to me on a PAL rc2 dics :matrix reloaded. I have made an iso image of it so everything was kept

[Sir Didymus]

Originally posted by jdobbs
It's not the buffer size. It is ridiculously large already.
...
This seems to happen exclusively when a third party stripper has been used.
...

Reading the last posts of the thread, it seems it could be also produced by another condition: if for some reasons CCE is breaking in the middle of an encode (maybe for some configuration issues, and without reporting error messages), it may happen that the encoded m2v has much less frames than the ones expected.

Since it is mandatory to comply with the following condition:
- for each encoded cell the number of video frames encoded by CCE should be equal to the number of frames in the source cell -

What do you thing about the possibility of explicitely introducing this test during the rebuild phase ?

It seems to me that it could be very helpful for focusing to the source of the #0004 errors...

I ask this fully understanding and quoting your statement:
-------------------------------------------------------------------
What I'm trying to say is that something else is wrong with your source when you get this error, it isn't DVD-RB. Don't shoot DVD-RB, it is only the messenger.
-------------------------------------------------------------------

No point about DVD-RB is doing perfectly its task when also the encoder is doing the same. It could be just useful, imho, to introduce an additional test, in DVD-RB, for ENSURING that the job carried out by CCE is well done...

In addition getting an error message of the form:

"Bad number of frames in file ---> V02001200004005.m2v"

could give to the user some opportunity to take some repair actions in such case (i.e trying to reencode the file, or simply including the original cell, in place of the broken one, in the backup)...

Cheers,
SD

[jdobbs]

I'll take another look at it -- but I already have another error process that checks to see if the frame count is wrong. That condition should generate an error 0006.

In my experience I haven't seen CCE create a short M2V except in those instances where I've accidentally aborted by hitting a key at the wrong time during encode.

[Sir Didymus]

Originally posted by jptheripper
...
am i babbling?
-JP
I think so (respectfully speaking...)... :)

Let me tell you why (imho, of course):

- If we assume CCE is never producing less frames than expected, then no reason to include additional tests and complex error checking algorithms in an application which is already properly working.

- If we assume that in some circumstances CCE may eventually produce less frames than what is expected, then all what is reasonable to do is to report the problem, because we hardly may assume where the missing frames are placed: they may be at the beginning, in the middle, or at the end.

In other words: if you know CCE failed its encoding task, do you think it is wise to take and use anyway its output ? I think it is better just to trow away the wrong file, trying to reencode it properly...

Cheers
SD

[Gurm]

I will try Paycheck again tonight and let you know, but it CONSISTENTLY gives me this error when used with CCE 2.69 versions. Ripped with latest DVD Decrypter. No 3rd party stripping utils.

- Gurm

[Dimad]

Originally posted by jdobbs
...
2. As it is bringing in the video it calculates proper presentation timestamps and system clock references.

3. The packetized video is prepared to be added to the output VTS, but first the original VTS is scanned to get the next available non-video packet (audio/subpicture) that is not identified for removal. The non-video packet will have a timestamp also associated with it.

4. In the output stream either the video, or the audio/subpicture is added depending upon which has the lower timestamp (please note there is a lot more to it in terms of timing -- I'm simplifying).
...
6. When the last video packet for a particular cell is added, DVD-RB make one last scan for remaining audio/subpicture packet within that cell so it can be flushed into the buffer.

Error 0004 occurs when there is such a huge number of remaining audio/subpicture packets that they cannot fit in the available buffer or the timestamp has been corrupted.

Is it a necessary requirement for the algorithm that PTS and SCR of the original cell start from 0? Or you use PTS of a first available frame in original cell (or something similar) as a starting time for new video?

It is easy to imagine situation when remaining packets will be "far away" in time from new video if its timestamps start with 0. Say,
there was a 100 sec cell. First 90 seconds were chopped (thus presentation time of subs/audio/video will start with 90sec). Multiplexing with video that starts with 0 will give a gap of 80sec between end of video and start of subs/audio.

Sorry if I'm talking BS, its end of Friday and a good rest is needed :)

[jdobbs]

Each cell doesn't have to start at zero and most don't. But if it doesn't start with zero, it should match the expected time (based on where the previous cell ended). If it doesn't I adjust it with an offset variable (the difference between what it should be and what was found). But, for example, if it is not the beginning of a cell and a large gap is created somewhere in the middle or at the end of the cell it could cause an error #0003 (middle) or error #0004 (end). The exception is when a still is encountered -- at which point the audio is expected to continue without video.

[Dimad]

Thanks for explanation. I don't think DvdReMake should cause any problems (in this sense). I'll ask on DRM forum if users have any problems with latest DRM and DRB.

[Trevelyan]

Hi! I'm an idiot--no one who knows what they're talking about needs to read this. This exact issue is addressed in the sticky, but, to my credit, no one had linked this directly to Error #0004, and total newbies like me might still benefit from the post if they come here and search "0004," like I previously did.

I just want to report my own Error #0004 and how I fixed it, in the hope it might help the developers or some other fool like me who got the error.

I followed the DVD Rebuilder guide found here (http://www.doom9.org/mpg/dvdrb.htm) (using CCE SP 2.67), and downloaded the DGMPGDec found here (http://www.doom9.org/Soft21/Decoders/dgmpgdec1012a.zip) in the "Download" section of this site.

That's not the same version of DGMPGDec as is linked from the DVD Rebuilder guide; that version, 1.1.0 can be found here (http://www.doom9.org/Soft21/Decoders/decodefix110.zip).

The former is DGMPGDecVersion 1.0.12, while the latter is DVD2AVIdg/MPEG2DEC3dg 1.1.0. Using the former repeatedly produced Error 0004s during encoding; whenever I looked at the AVS files, they were a black screen with a message about "MPEGSource" errors. Moving to MPEG2DEC3dg 1.1.0's DLL fixed the problem entirely and now it works fine.

Perhaps that's of some use to someone, I hadn't seen anyone mention this in the forum.

Thanks for the great program! My only recommendation would be the addition, eventually, of linking to audio compression possibilities within the program as well, making it a complete one-stop shop.

[sillKotscha]

Hi folks,

this time I got "Error #0004" for the first time. It's just to let you know in which scenario...

RB - v0.55b
AviSynth 2.5.5 CVS Releases. [July. 12th]

movie: Die Hard III

all went fine with the first setup (Edit: all as it should, no preprocessing, just default RB settings) but as the source is slightly noisy, the result after rebuilding was a bit noisy as well. So, I tried <undot().deen()> as my 2nd setup ... after about 20% of transcoding the "Error #0004" occured.

3rd setup: now I deleted <undot().deen()> within avs editor and rebuilding was no problem again.

Well, maybe the "Error #0004" has something to do with avisynth, even though jdobbs has informed us that the current cause of this problem is due to problems with the source files, most likely due to the use of a preprocessing program to modify them.

just my experience and my 2 cent

Sill

[jdobbs]

Go back to AVISYNTH version 2.5.4 and see if it still happens. I'd say that using one beta software package to test another beta software package is pretty much is a formula for failure.

[sillKotscha]

Originally posted by jdobbs
Go back to AVISYNTH version 2.5.4 and see if it still happens...

yes, U were right. I went back to stable AVS and that solved the error. Well, sometimes it's a nono to update stable releases with beta-testing software BUT as DVD-RB is concerned updating "a beta software package" is a must ;)

have a nice sunday

Sill

[jdobbs]

Originally posted by sillKotscha
have a nice sunday And you too.:)

[johnnyquid]

I too am getting the Error #0004 message. This occurs when rebuilding NTSC American Beauty DVD. I noticed that another post has also mentioned this DVD. I have used DVD Rebuilder before and have not had a problem (great program thanks Jdobbs). I am using the following:

CCE 2.66.1.7
mpeg2dec3 1.0.1.0
decomb 5.2.1
avisynth 2.5.4

The error occurs at around 98% completion. Even though the error message occurs, the video folder created still plays in Power DVD but I do not know what if anything is corrupted. I did notice that a large number of very small MPV files get created during the process perhaps this has something to do with the error message.

[jdobbs]

How are you using decomb? If you are using it to do IVTC it can change the framecount and cause unpredictable results... I would definitely not doing anything beyond FieldDeinterlace(). Telecide() certainly shouldn't be used with DVD-RB.