"DVD ReBuilder experienced a buffer overflow. Error #0004. Process must be aborted"

[krackato]

I got this error message: "DVD ReBuilder experienced a buffer overflow. Error #0004. Process must be aborted."

Does anyone know what happened?

[krackato]

Now I'm getting "error #0004" followed by "Stop statement encountered". What is going on?

[krackato]

Okay, now I've tried both Rejig and QuEnc. With QuEnc I get the error "AVS File is not outputting. (Use ConvertToYV12() at end of script)." With Rejig it states that the encode took 0 minutes which obviously means that it did nothing.

[ux-3]

Hook the "include in VAF" checkmark in the settings and run from scratch.

[krackato]

Originally posted by ux-3
Hook the "include in VAF" checkmark in the settings and run from scratch.

Where is this option? I mean, in which program. Cause I looked in Rejig, QuEnc, CCE SP 2.66, and DVD Rebuilder and I couldn't find that option.

[ux-3]

DVD rebuilder, Settings screen, the link to the avisynth plugin

[krackato]

I'm sorry, I don't see that option anywhere. I'm using Version 0.35. I clicked Options>Setup and I didn't see anything about an AviSynth plugin and then I clicked Options>AVS Options and didn't see anything about "include in VAF". Perhaps we have different versions. I appreciate your help.

[ux-3]

Options - Setup - mpeg2dec3dg - check "add to avs file" (and make sure that you have that plugin).
I got avs and vaf mixed up - sorry about that.

Just to add this: I had exactly the same error message when I tried it first. My encoding stage lasted only a minute, because the encoder could not read the video through the avs. Only after I made the change, the encoder would read the movie and be busy for a few hours. Then Rebuild did not have an error.

[dancis]

I am getting also buffer overflow errors. I have checked the add to avs..... option

But i am still getting the errors with version 0.35 , are there some other options i can try

I have tried 2 movies ( tombraider 2 and terminator 2 , both R2 and original)

[idbirch2]

I just got exactly the same thing with Tomb Raider 2 (PAL UK) too. Encoding lasted over 400 mins so that was fine - anyone know what causes this?

[Scoobydeux]

I got same error with v.41 on movie Speed 2 (I know, why am I bothering). Funny thing is, I was using the rejig method, so the AVS should have had nothing to do with it!

[oddwunn]

I am new to DVD ReBuilder and I am having this exact same error. Has a definitive solution been found as yet? The encode only takes 1 minute and then the rebuild bombs out with the overflow code (in the thread title). I am using DVD ReBuilder 0.44, CCE SP 2.67.00.23 with EclCCE. Any ideas?

[oddwunn]

I've been playing with this all day and after trying 5 different titles, I have gotten the exact same error each time, on two different machines, at different points in the rebuild process. If I repeat the same title on either machine, the rebuild process bombs out at the exact same spot every time, so the problem is easy to reproduce.

In the process I have learned a valuable lesson that maybe should be included in the FAQ - Do not install more than one version of CCE on any given machine! Since DVD-RB can support different versions of CCE, I tried installing a couple of different versions in different directories, and then just pointed DVD-RB to the version that I wanted to try. BAD IDEA!! For reasons unknown to me, CCE will not work right at all under these conditions and all I got were a bunch of tiny encoded files that took about a minute to create, which is obviously not right. Once I started fresh and installed just a single version of CCE, then at least the encoding process went smoothly once again, just to find out that DVD-RB succumbs to the dreaded "DVD ReBuilder experienced a buffer overflow. Error #0004. Process must be aborted" message once again.

On each title, the message popped up at a different point - sometimes very early in the process and sometimes very late, when it was just about done. I tried titles with episodic contents, movie only titles, and titles with extras, all of which came to the same fate. All titles were ripped using DVDDecrypter 3.2.1.0 and I used the resultant files from my hard drive as source material. I am running Win XP SP1 and DirectX 9.0b.

Since there seems to be quite a few people who are not having problems, can anyone suggest what I might be doing wrong?

[oddwunn]

I just tried DVD-RB 0.45 which I had high hopes would fix the "Error #004" problem - no luck.

[RB]

Originally posted by jdobbs
FYI. For those of you who get it I'm going to try very hard to, in my next posted version, fix the errors #0003 and #0004.

Great! I have a project waiting for rebuild here that will be a very good exercise (currently fails with #0004). VTS_01 is 612 MB but video is just 16 still frames, the rest is AC3 and LPCM audio. A typical slide show with music tracks.
v0.45 still fails with error #0004 for the first segment in this VTS.

jdobbs, is v0.45 supposed to fix the "no subs in standalones" issue?

[jdobbs]

Originally posted by oddwunn
I just tried DVD-RB 0.45 which I had high hopes would fix the "Error #004" problem - no luck. Are you sure you're using the 0.45? I'll check tonight, but I thought I'd removed the error message completely...

[jdobbs]

Originally posted by RB
jdobbs, is v0.45 supposed to fix the "no subs in standalones" issue? No, I'm still working that.

[jdobbs]

A note to everyone. You cannot continue jobs started with a previous version (e.g. just do a REBUILD) on ANY job with 0.45 -- there is an additional INF entry that is now inserted during PREPARE that is essential. I'm going to modify the notice for 0.45 to clarify that fact.

[RB]

Thanks jdobbs. OK, reran prepare with new version but kept already encoded M2V files. Modified INF to indicate encode was finished and now the rebuild completed without any issues. Congratulations!!

[jdobbs]

Originally posted by RB
Thanks jdobbs. OK, reran prepare with new version but kept already encoded M2V files. Modified INF to indicate encode was finished and now the rebuild completed without any issues. Congratulations!! I was going to mention that you could do that -- but I thought it might make it too complicated... I figured a guy like you would figure it out. ;)

[jdobbs]

Originally posted by RB
Thanks jdobbs. OK, reran prepare with new version but kept already encoded M2V files. Modified INF to indicate encode was finished and now the rebuild completed without any issues. Congratulations!! It just so happens that about half of the code I inserted to fix this was also related to BOV... so I should get that going soon also.

[RB]

Originally posted by jdobbs
I was going to mention that you could do that -- but I thought it might make it too complicated... I figured a guy like you would figure it out. ;)
:D Actually, I should print your reply and show that to my wife, just to prove that sometimes I do get things right ;)

[rui]

These are indeed great news. :)

I am going to test it with LOTR DVD nº 3 (only extras) that was giving me the 004 error.

Will report later.

[RB]

Originally posted by jdobbs
It just so happens that about half of the code I inserted to fix this was also related to BOV... so I should get that going soon also.
Excellent, thanks a lot! Hmm, I don't want to be selfish :) but maybe before enabling BOV you could try to fix the "no subs in standalone" issue so users affected by this (including me) can actually test BOV in their players?

Also, at the time you enable BOV, I'd suggest you also start processing the menu VOBs to make sure the BOV code is heavily exercised :)

[jdobbs]

Originally posted by RB
Excellent, thanks a lot! Hmm, I don't want to be selfish :) but maybe before enabling BOV you could try to fix the "no subs in standalone" issue so users affected by this (including me) can actually test BOV in their players?

Also, at the time you enable BOV, I'd suggest you also start processing the menu VOBs to make sure the BOV code is heavily exercised :) Is your player a Samsung?

[wmansir]

Originally posted by RB
Also, at the time you enable BOV, I'd suggest you also start processing the menu VOBs to make sure the BOV code is heavily exercised :)

Well, since everyone who joins Doom9 is required to own a copy of The Matrix DVD, we should have plenty of beta testers for BOV. :)

[RB]

Originally posted by jdobbs
Is your player a Samsung?
No, JVC. I've also seen someone reporting the issue with an Armstard (Amstard, Armstad?) player.

[Centurione]

Originally posted by RB
No, JVC. I've also seen someone reporting the issue with an Armstard (Amstard, Armstad?) player.

It was an AMSTRAD (but I know it is a clone of a SEG -german company -)

[robot1]

Originally posted by wmansir
Well, since everyone who joins Doom9 is required to own a copy of The Matrix DVD, we should have plenty of beta testers for BOV. :) The Matrix has also branching... It would be too sweet to backup already in so fast way...

[jdobbs]

Originally posted by RB
No, JVC. I've also seen someone reporting the issue with an Armstard (Amstard, Armstad?) player. Hmmm. My main player is a JVC also. I'm pretty sure the problem is that I'm not populating the sp_synca table of the DSI. I meant to do that a long time ago, but it worked on my players without it (my original plan for this program was for my personal use) so I've ignored it. I guess I need to get up off my duff and finish the (required) work.

[RB]

JVC XV-S300BK

[oddwunn]

Are you sure you're using the 0.45?

Yup, sho'nuff...:)

A note to everyone. You cannot continue jobs started with a previous version (e.g. just do a REBUILD) on ANY job with 0.45 -- there is an additional INF entry that is now inserted during PREPARE that is essential. I'm going to modify the notice for 0.45 to clarify that fact.

Ah, gotcha. I'll do the jobs over from scratch.

Thanks jdobbs. OK, reran prepare with new version but kept already encoded M2V files. Modified INF to indicate encode was finished and now the rebuild completed without any issues. Congratulations!!

I already deleted the files...bummer. I wish I had known that earlier. I assume that all I needed to do was to modify the line "progress=1" to read "progress=2" in the rebuilder.ini file, right? That sure would have been a time saver...;)

[rui]

Ok, i redone my backup of DVD nº 3 of LOTR extended edition, and not a single error :)

I was getting a 004 error in rebuild fase, but not this time.

Great work, Sir :)

Thank you for all your efforts.

[Knocks]

Upgrading to .45 hasn't helped me. I am still getting the error in the early stages of the rebuild phase. I did delete all the previous temp files and the old .ini file to make sure old bugs don't interfere with the new version.

I am using CCE SP Trial 2.67.00.27 with EclCCE 1.81. In the DVD RB settings I have pointed to the EclCCE.exe instead of the CCE SP exe although I have tried it both ways before.

[jdobbs]

Originally posted by Knocks
Upgrading to .45 hasn't helped me. I am still getting the error in the early stages of the rebuild phase. I did delete all the previous temp files and the old .ini file to make sure old bugs don't interfere with the new version.

I am using CCE SP Trial 2.67.00.27 with EclCCE 1.81. In the DVD RB settings I have pointed to the EclCCE.exe instead of the CCE SP exe although I have tried it both ways before. Is this happening on more than one DVD?

[Knocks]

Originally posted by jdobbs
Is this happening on more than one DVD?

Yes, it happens with two DVDs I have tried so far, both are Russian PAL DVDs, approximately 7.5 GB, ripped to the hdd and stripped of CSS.

[oddwunn]

Upgrading to .45 hasn't helped me. I am still getting the error in the early stages of the rebuild phase. I did delete all the previous temp files and the old .ini file to make sure old bugs don't interfere with the new version.

I am using CCE SP Trial 2.67.00.27 with EclCCE 1.81. In the DVD RB settings I have pointed to the EclCCE.exe instead of the CCE SP exe although I have tried it both ways before.

Test #1: Same here (as above), but for me the CCE SP Trial version is 2.67.00.23. I ran the project from scratch just to be absolutely sure it was not an old error (and that was before I knew I could just modify the INI file :) ).

Test #2: This project now worked perfectly where it had given me an error #0004 at 96.6% previously.

Test #3: I tried a new title that I had not done with any previous version of DVD-RB, and this worked flawlessly from beginning to end...:)

Three different computers - two successful and one still bad - I will try running the problem title on another computer. Things are looking very hopeful!

[timekills]

EDIT - > Scratch below the line - I'm keeping it just for clarity right now. I now get errors from CCE, which is basically what I expected when using the "Basic" setting s with SP. Looks like my initial assumptions were correct. Back to the drawing board.

____________________________________________________________________

FWIW, I am using CCE 2.67.whatever myself, and chose the 2.66 version of CCE in the Options -> CCE Options (i.e. CCE SP (v2.66+) ), since I wasn't usng "CCE Basic" - even thought that is followed by version number 2.67. I got the error #0004 repeatedly. When I switched to the CCE Basic (v2.67+) choice, it worked correctly.

Maybe I missed this clarification previously, but apparently the choices are for CCE Basic OR 2.67+ I assumed that the second option, CCE SP 2.66+ meant any version of CCE SP from 2.66 and higher, while the first option meant only users of CCE Basic.