DVD-RB Error #0004 (merged) [Archive]

rpboy

4th May 2004, 15:52

Originally posted by jdobbs
You are configured incorrectly. Follow the instructions here (http://forum.doom9.org/showthread.php?s=&threadid=74308) to install properly.
Okay, my bad. I didn't read his problem exactly.

I think I am configured correctly. Previous versions of DVD-RB have all worked fine for me. I dropped in the new REBUILDER.EXE and now I get this error:

"DVD Rebuilder experienced a buffer overflow. Error #0004. Process must abort."

I double checked my setup against the post you mentioned, and I don't see what I have incorrect.

I have CCE SP 2.67.0.23 and EclCCE 1.8b. The "Path to CCE SP (New)" is pointing to the ECL EXE. The "Path MPEG2DEC3DG" is pointing to the DLL file correctly and the "Add to AVS file" is checked. (Though it was not checked originally, so I checked it and tried again - same error.) I have the correct DLL file and verified it against the link posted on the instructions. Mode is One-Click Mode. Dynamically Assign Cell Bit Rates is checked.

The process goes through the encode phase completely (took many hours) and ends in the rebuilding phase, I believe. (Its at 96.5% in my case with the LUPIN DVD.) It ends with VTS12, VOB ID 1, Cell 6, referencing this (pulled from REBUILDER.INF file):

[V12000500001006]
SCR=40276236.000
PTS=40297257.000
Frame_Rate_Code=1
Pulldown=0
Structure=3
Frames=1916
Last_Sector=156559
Reduction=73.2
Aspect_Ratio=2
HalfD1=0
EndPTM=47099052.000

If there is anything else I can tell you. please let me know.

jdobbs

4th May 2004, 17:29

I was speaking specifically to the error in which it to "about a minute" to encode... that is very definitely a configuration error.

redfive19

4th May 2004, 17:34

Since you mentioned you had ECLCCE 1.81b, I am assuming you are using the demo. In that case, you must have your config pointing towards the ECLCCE executable and not the CCE executable.

-redfive

Bluesilo

4th May 2004, 17:58

I have my directory pointing to eclcce and i still get the error...any help would be greatly appreciated

rpboy

4th May 2004, 21:54

Originally posted by redfive19
Since you mentioned you had ECLCCE 1.81b, I am assuming you are using the demo. In that case, you must have your config pointing towards the ECLCCE executable and not the CCE executable.

-redfive
Actually, I mistyped that. I have it pointing to the ECLCCE EXE. It gets through the encode process just fine.

mpennel

5th May 2004, 22:23

I get the exact same error at the end of rebuilding on Region 1 disc of "The Passion of Anna"

My configuration works fine on other discs, so this is a new error to me.

configuration is:

CCE 2.50
DVD-RB 0.46
Half D1 for extras was NOT enabled
Dynamically assign cell bitrates IS enabled
One Click mode (although it does it in REBUILD of 3-click too)

I kept all 3 audio tracks, if that makes any kind of difference.

-----------

oops, another day, same error message, i used dvd-r .44, but got the same buffer overflow error, ahwell, the passion of anna maybe aint so hot ;)

Knocks

8th May 2004, 20:51

jdobbs: now that most other problems are taken care of, including error 0009 and subtitle glitches, do you think you have the energy (and desire) to concentrate on 0004 for one release? I, for one, have been waiting to reap the benefits of DVD-RB and have gigabytes worth of DVD9 movies patiently waiting to be shrunk but 0004 has prevented me from doing that all this time.

jdobbs

8th May 2004, 20:55

The 0004 error is an indicator of a problem in the source and should be a rare exception at this point in the programs state. If you are consistently getting 0004 errors -- it is very likely there is something else wrong in the way you are doing your backups. I personally have done many, many, many discs -- without this error With that said, I will look again and see if I am missing something.

Have you had any successful backups?

Knocks

10th May 2004, 10:03

jdobbs: I have only tried DVD-RB with 2 movies so far and got #0004 in both of them, although at different stages of rebuilding. They were both some Russian DVDs, and it is possible that they were modified by pirates or just badly mastered.

I do have a lot of normal NTSC DVD-9's though and I will try a couple of them and report the results. Just to make sure, instead of the CCE SP trial exe you have to point to EclCCE.exe (if you use one), correct? Because that's what I've been doing.

jdobbs

10th May 2004, 12:09

Originally posted by Knocks
jdobbs: I have only tried DVD-RB with 2 movies so far and got #0004 in both of them, although at different stages of rebuilding. They were both some Russian DVDs, and it is possible that they were modified by pirates or just badly mastered.

I do have a lot of normal NTSC DVD-9's though and I will try a couple of them and report the results. Just to make sure, instead of the CCE SP trial exe you have to point to EclCCE.exe (if you use one), correct? Because that's what I've been doing. Yes. If you are using the trial version you must point to eclCCE.exe.

Knocks

14th May 2004, 07:36

Thanks for making me double-check everything. My version of Avisynth was 2.0.8. That was causing major problems. The Avisynth site has the 2.08 version listed at the top of the page so I assumed it was the latest version. Upgrading to 2.5.4 fixed the #0004 error. Thanks!

PXH

14th May 2004, 10:01

I have used Rebulider V 0.46 (with CCE SP 2.5) successfully to back up several discs.

However, the latest backup of Master & Commander R2 prepared and encoded successfully but at the rebuild stage there was a buffer Overflow error #0004 very near the start.

I do not believe I have changed anything (on system or method)since perfoming successful back-ups.

Any thoughts?

gort9k

19th May 2004, 13:49

More on this Error #0004 business.

I've read through all the posting, and I've not found any clue about this error.

I'm using DVD Rebuilder v.0.40 (beta), Cinema Craft Encoder Basic (v.2.69.01.04)

Any time I try to backup a movie everything goes right up to the point the program starts rebuilding. Then at different stages of the rebuilding (different for each movie) pops up the buffer overflow #0004 error.

It is easy to blame configuration, but this is not going to resolve anything. When so many people complain, surely there is an error in the program.

Pity, as it looks very promising.

Joergen

19th May 2004, 15:14

Originally posted by gort9k
I'm using DVD Rebuilder v.0.40
Bug reports for old versions NATURALLY are redundant. Only report bugs with the latest or second latest version.

PXH

19th May 2004, 15:17

I retried using V0.48 and got the same error at the same point of the Re-build phase

Joergen

19th May 2004, 15:21

Originally posted by PXH
I retried using V0.48 and got the same error at the same point of the Re-build phase

Did you prepare and re-encode it using 0.48 aswell?

gort9k

19th May 2004, 17:58

In my post about error #0004 I said tha I was using DVD rebuilder version 0.40.., it was a typo, I am using versión 0.49.

I'm sorry about the mystake, but the error #0004 keeps on.

jdobbs

20th May 2004, 03:59

gort9k

20th May 2004, 14:12

It looks like it is no good complaining about any kind of error.

It seems like jdobss doesn't like hearing about #0004 error.

So, no more asking for advice.

I'll keep reading the forum just in case sombebody find an answer to this error

Joergen

20th May 2004, 15:18

I have to defend jdobbs here cause if you have the RARE (RARE RARE!) #0004 error with almost every movie, your setup (or method) is MOST PROBABLY at fault.

I havent seen the #0004 error since it was fixed (and only saw it with one movie), and counting 20+ succesful movies so far.

It's easy to blame setup, but it's even easier to be lazy, pompous and arrogant and blame the software.

CeD

20th May 2004, 16:32

Hello, i'm new here...;)

I have also this #0004 error on every backup, and if i consider one precise DVD, it is always at the same stage.
I tried to reinstall everything many times but there is something wrong i don't understand.

My configuration :
Athlon XP 2500+
WinXP
DVD-RB 0.49
CCE Basic 2.69
Half D1 for extras : NOT enabled
Dynamically assign cell bitrates : enabled
One Click mode : enabled

If it's a problem of setup, maybe it is due to the computer itself ? or is it possible that we don't have all the files needed ?

May the force be with us :)

jdobbs

20th May 2004, 17:36

Originally posted by gort9k
It looks like it is no good complaining about any kind of error.

It seems like jdobss doesn't like hearing about #0004 error.

So, no more asking for advice.

I'll keep reading the forum just in case sombebody find an answer to this error I think my history of responding to reported errors speaks for itself. But I can't come over to your house and configure it for you.

Knocks

20th May 2004, 17:43

Make sure your AviSynth is installed correctly and that you have MPEG2Dec3dg.dll in AviSynth\plugins. That basically solved the #0004 error for me.

jdobbs

20th May 2004, 17:47

Originally posted by CeD
Hello, i'm new here...;)

I have also this #0004 error on every backup, and if i consider one precise DVD, it is always at the same stage.
I tried to reinstall everything many times but there is something wrong i don't understand.

My configuration :
Athlon XP 2500+
WinXP
DVD-RB 0.49
CCE Basic 2.69
Half D1 for extras : NOT enabled
Dynamically assign cell bitrates : enabled
One Click mode : enabled

If it's a problem of setup, maybe it is due to the computer itself ? or is it possible that we don't have all the files needed ?

May the force be with us :) Some things to look for:

1. Are you using the correct version of MPEG2DEC3.DLL? Some other software packages can "force" AVISYNTH through a registry setting to look in the wrong place. Use the path to it in SETUP to be sure.

2. Are you using the latest DVD Decrypter version? If not it is possible (a couple versions back) that a zero length file in the original could leave one of the VOBs encrypted (when used in ISO mode). This will DEFINITELY result in 0004 errors.

3. Are you preprocessing with some other package to get rid of extras or other things? Some packages result in a clean DVD -- some will screw up the output and cause 0004 errors.

4. Are you trying to read directly from the DVD rather than using DVD Decrypter. This will definitely result in a 0004 error.

5. Try three click mode and go in and review the movie using the .AVS file after PREPARE. It will show you whether your AVISYNTH is working correctly. Also look at the .M2V files after ENCODE. If they won't play... something is misconfigured.

Once you get past the first successful encode (meaning you are configured correctly) you will very likely never see 0004 again.

jdobbs

Sir Didymus

20th May 2004, 17:50

@CeD & gort9k.

Maybe it's a good idea you to take a little time to read carefully and check the faq and the sticky threads our dear Moderator Wmansir has written, where you may find specific support to many basic set up and configuration issues.

Please consider it is very easy to see and verify if at least the preparation step completed in the proper way: just play some (or all...) of the avs files produced by DVD-RB in the D2VAVS folder, using windows media player (or the player you like more...).

Please consider also it is equally easy to see and verify if the encoding step completed in the proper way: again just play some (or all...) of the m2v files produced by DVD-RB in the D2VAVS folder, using the same player.

You may understand that people becomes a little bit upset of repeating almost every day the same things...

I wolud not mean that some basic support is not due...
but at least:

:search: :readfaq:

DocDragon

20th May 2004, 17:59

Originally posted by gort9k
More on this Error #0004 business.

I've read through all the posting, and I've not found any clue about this error.

I'm using DVD Rebuilder v.0.40 (beta), Cinema Craft Encoder Basic (v.2.69.01.04)

Any time I try to backup a movie everything goes right up to the point the program starts rebuilding. Then at different stages of the rebuilding (different for each movie) pops up the buffer overflow #0004 error.

It is easy to blame configuration, but this is not going to resolve anything. When so many people complain, surely there is an error in the program.

Pity, as it looks very promising.

no offense, gort9k, but what's your definition of "any time [you] try to backup a movie?" on how many dvd's did you try DVD-RB? do you have pal or ntsc system? region code? i have been backing up around 3 dozen ntsc movies since DVD-RB v0.4x and have experienced only very few problems.

also, jdobbs' response time regarding errors and comments is phenomenal! you won't get such service even from commercial companies -- that's why i donated a couple of times already. therefore, don't get defensive so quickly just because YOUR system is not working and you obviously won't accept that it might be related to YOUR configuration. it's easy to blame other ppl :sly:. i had problems at the beginning with my configuration because i didn't RTFM :D. i admit (and that has already been suggested) that DVD-RB's installation would be easier, if all the required programs would come bundled as one unit. but then again there might be copyright issues. :(

and BTW, DVD-RB does not only "look" promising -- this freebie already does in its beta stage (!) what other commercial programs are TRYING to do!!!

my 2 cents.

DD

ps: jdobbs, what do you think about this suggestion (http://forum.doom9.org/showthread.php?s=&threadid=76453) of implementing a template?

gort9k

20th May 2004, 18:17

This #0004 error business is getting too big and out of context.

There are two kind of people in these forums:
Tech people. Those who know a lot about the matter. That, even, make the program.

The other group, like myself. Are users, we use the programs, we like them, or not. And when we encounter a trouble we bring it to the forums looking for an explanation. We ask because we don't have the knowledge. And we don't like being patroniced.

I'd like to use DVD rebuilder to make my backups. As I'm looking for quality. But I keep finding this error. You say it is misconfiguration, well, it could be.

By the way my player is not affected by the phases of the moon

Subject closed

jdobbs

20th May 2004, 23:00

@gort9k

I do this pretty much for free. Yes I accept donations -- but with a very, very, very few exceptions (like DocDragon) no one contributes. No big deal. That's just people. (e.g. the last time I got a donation was 5 days ago and it was only one)

I'm not begging, I'm making a point. When I do this for nothing I am not inclined, nor obligated to listen to smart-ass remarks from people who think I exist on this planet for no other reason than to give them free online support when they don't even take the time to simply read the FAQ or ask the question in a semi-courteous manner.

When I suggested you were not configured properly -- I meant it. If you don't want to accept that possibility, I suggest you simply use another program. There are lots of them.

To everyone else: Please forgive my rant. I enjoy helping people, I enjoy writing code, and I really want to make this a good free program. But that doesn't mean I will accept rude comments.

DocDragon

21st May 2004, 02:26

[...]
I'm not begging, I'm making a point. When I do this for nothing I am not inclined, nor obligated to listen to smart-ass remarks from people who think I exist on this planet for no other reason than to give them free online support when they don't even take the time to simply read the FAQ or ask the question in a semi-courteous manner.

When I suggested you were not configured properly -- I meant it. If you don't want to accept that possibility, I suggest you simply use another program. There are lots of them.

To everyone else: Please forgive my rant. I enjoy helping people, I enjoy writing code, and I really want to make this a good free program. But that doesn't mean I will accept rude comments.

i absolutely agree :D...

"it's the tone that makes the music."
"c'est le ton qui fait la musique."
"der ton macht die musik."

there's certainly one language that some smart-ass should understand :p.

DD

ps: jdobbs, what do you think about implementing a filter template for different picture settings as suggested here (http://forum.doom9.org/showthread.php?s=&threadid=76453)? i think this might be quite "easy" to program for a super-coder like you, huh? ;). i just sent you another 10 bucks as a motivation. that should also stop your 5-day donation dry-spell :D.

PXH

21st May 2004, 11:10

I think we are in danger of letting some not very well thought out comments take over the thread.

I have used Re-Builder successfully on several occasions and only experienced the #0004 error with one disc ( Master & Commander R2. I experienced the error twice with versions 0.46 and 0.48 starting the whole process again each time.

Interestingly, I used Re-builder 0.48 on the main movie only (after re-authoring with DVD Shrink) and everything worked fine.

This would lead me to conclude that my setup is OK and that it is something unique in the structure of the DVD or the ISO image was somehow corrupted during the ripping process.

PS.

I think given that the software does something for free that nothing else can do and it is clearly distributed as beta none of us has any grounds for "complaining" about bugs. I just hope I won't see this error again.

Sir Didymus

21st May 2004, 11:55

Originally posted by PXH
... skip ...

This would lead me to conclude that my setup is OK and that it is something unique in the structure of the DVD or the ISO image was somehow corrupted during the ripping process.

Sorry for asking (I know it will eventually take some time...), but just as a weak conjecture, and for eventually excluding that the problem is related to the rip done in iso mode, could you try to repeat the whole process decripting in file mode ?

Cheers,
SD

sadik

21st May 2004, 13:28

Originally posted by gort9k
This #0004 error business is getting too big and out of context.

There are two kind of people in these forums:
Tech people. Those who know a lot about the matter. That, even, make the program.

The other group, like myself. Are users, we use the programs, we like them, or not. And when we encounter a trouble we bring it to the forums looking for an explanation. We ask because we don't have the knowledge. And we don't like being patroniced.

I'd like to use DVD rebuilder to make my backups. As I'm looking for quality. But I keep finding this error. You say it is misconfiguration, well, it could be.

By the way my player is not affected by the phases of the moon

Subject closed

I got the same error, but i tried fixing it by myself. I didnt come to the forums and bitch about it like you did. It happened to be a configuration error. If you follow jbobbs installation guide you'll get no problem. It helped me. Just delete the .ini config file and start over again. Get CCESP and EclCCE. Rip an iSO of the DVD using DVD Decrypter, and mount it using Daemon Tools. If you do things right, there is no way things will go wrong.

PXH

21st May 2004, 14:00

Originally posted by Sir Didymus
Sorry for asking (I know it will eventually take some time...), but just as a weak conjecture, and for eventually excluding that the problem is related to the rip done in iso mode, could you try to repeat the whole process decripting in file mode ?

Cheers,
SD

When, I have time I will do as you suggest. For future reference, is there any difference from a Rebuilder perspective as to whether the DVD is Ripped in File or ISO mode?

sadik

21st May 2004, 14:05

i dont think so. as long as you have all the files that are on the dvd on your pc it will be ok. i just prefer to make an iso. :)

begu

21st May 2004, 14:15

to sadik:
"..., and mount it using Daemon Tools." ?
Why use daemon tools? I got it working just by ripping the DVD content with decrypter to HD in filemode and then open the ripped directory in rebuilder.

Is there something that might go better when the rebuilder 'thinks' that it is reading the real DVD disc (mounted with daemontools) compared to situation when the rebuilder is reading from the HD?

jdobbs

21st May 2004, 14:26

Originally posted by PXH
When, I have time I will do as you suggest. For future reference, is there any difference from a Rebuilder perspective as to whether the DVD is Ripped in File or ISO mode? No. But there are two more variables thrown into the equation. The DVD drive emulation software and the way in which it it created with DVD Decrypter. I can tell you, though, that I do all my discs now using ISO mode and Daemon Tools (after suggestions by DDogg, I decided to give it a whirl, and I like it) -- so I don't think there is a systemic problem related to mounting drives in ISO mode.

gort9k

21st May 2004, 14:36

To sadik:

I had this error #0004 matter closed for good. But I feel obligued to give you an answer. With your kind of actitude you deserve the status of senior instead of junior.

I've tried using DVDRebuilder .49(beta)and different instances of CCE (2.5 with eclcce, CCE Basic (v2.69)

Error 0004 keeps on appearing at the rebuilding stage.

I have deleted and reinstalled the whole bunch (DVDrb, CCE, Avisynth). I've been over my configuration many times. And still that dreaded error.

I'll keep trying

Thanks again, sadik

sadik

21st May 2004, 14:37

jdobbs knows whats good :)
dvd iso+daemontools = :>

sadik

21st May 2004, 14:42

Originally posted by gort9k
To sadik:

I had this error #0004 matter closed for good. But I feel obligued to give you an answer. With your kind of actitude you deserve the status of senior instead of junior.

I've tried using DVDRebuilder .49(beta)and different instances of CCE (2.5 with eclcce, CCE Basic (v2.69)

Error 0004 keeps on appearing at the rebuilding stage.

I have deleted and reinstalled the whole bunch (DVDrb, CCE, Avisynth). I've been over my configuration many times. And still that dreaded error.

I'll keep trying

Thanks again, sadik

:)
btw.. when that error happened to me i had like two eclcce's. one pointed in cce basic and the other in cce 2.66+. then i deleted the ini file and just used eclcce with ccesp 2.66+ and nothing more.
add the avisynth plugins to your avisynth plugins directory and make sure that everything is setup properly.
rip in iso mode with dvd decrypter and mount it using daemon tools.
i hope it works :)

PINOBIRD

21st May 2004, 15:01

@ gort9k

A friend of mine just tried out his ultra fast PC with cce basic 2.69.
At the rebuild stage he got the buffer overflow #0004 error.
Then he tried again with cce 2.67 and everything went fine.
I think you should give it a try with cce 2.67 ( trial ) and eclcce.
The second option is Quenc.
Then you know for sure that your configuration is O.K.
And then you also know that you were dealing with a real bug or not.

Good luck

sadik

21st May 2004, 15:05

yep. using CCE SP 2.67.00.23 + EclCCE 1.81 in here!
everything works fine and dandy.
just select one EclCCE in the options the one for 2.66+.

gort9k

21st May 2004, 15:51

pinobird and sadik:

Searching the forum I've read that people have foundsome kind of trouble with high end pcs. Could this be the real problem?

It seems strange that having a fast computer works against you. I my case I've got a PIV 3.06 hyper threading with one gigabyte ram (dual, in fact there are two gigs ram).

I'll make a try with CCE 2.67 and tell you what I got.

gracias

sadik

21st May 2004, 15:56

actually dvd-rb runs pretty nice on my pc. :D
i have no problems with it.

gort9k

21st May 2004, 18:57

Sadik, this time it worked.

I used CCE SP v2.67 instead of CCE Basic. Deinstalled CCe Basic, and replaced it with CCE SP and EclCCE.

As I didn't want extras (menus, foreing languages, subs, etc) I used IFOEDIT to strip all the unwanted elements. After that used DVD Rebuilder. And everything went fine. I'll have to make some tries more. But I think this time I got it.

Thanks so much for your help.

sadik

21st May 2004, 19:58

I'm glad it worked. :)

You gotta show your PC who's the boss!

:P

gort9k

22nd May 2004, 00:59

Well, in this case "pc vs me" I ain't sure about who's the boss

Thanks

jdobbs

22nd May 2004, 10:53

@DocDrAGONps: jdobbs, what do you think about this suggestion of implementing a template? The problem is that changing those settings can easily result in poor picture, and it gets complicated by which features exist (and how they are implemented) in different CCE versions. I also believe that the better route if someone is going to use filters is to use them in AVISYNTH. The internal options in CCE are pretty basic and frankly don't work that well. AVISYNTH has lots and lots of filters available that could specifically address almost anything.

DocDragon

22nd May 2004, 11:30

Originally posted by jdobbs
@DocDrAGON The problem is that changing those settings can easily result in poor picture, and it gets complicated by which features exist (and how they are implemented) in different CCE versions. I also believe that the better route if someone is going to use filters is to use them in AVISYNTH. The internal options in CCE are pretty basic and frankly don't work that well. AVISYNTH has lots and lots of filters available that could specifically address almost anything.

ahh, i see. thanks a lot for your response! so i probably have to bug quantum for some filter tips. :p

DD

CeD

25th May 2004, 10:34

I wanted to thank jdobbs, Knocks and Sir Didymus for theirs replies (a few posts before), i tried many times and i don't have this error anymore (i installed version 0.50 since), but i have other problems which are not yet solved. :eek:

However, i don't know what was going wrong before to get this error #0004. :rolleyes:

cu

biggy7

5th June 2004, 19:05

ripped Police Story to Hard drive using DVD decrypter, then used DVDRB 0.51c in CCE mode with CCE Basic.

Did 2 pass enocode, all went well, did rebuild and at about 44%, it came up as 0004 error, buffer overflow.

i didnt rip anything out of police story, was a 7Gb disk, did all files.

im gona try it again with CCE SP and dvdrb 0.51c.

smreid

7th June 2004, 10:48

Hi Guys,

I have never posted to this forum and in fact subcribed because of this problem. I was using CCE Basic 2.69, Avisynth 2.54, mpeg2dec3g.dll 1.0.1 and I had this consistantly with every DVD I tried to burn (8 dvds). I tried DVD-RB versions 0.49, 0.51 and 0.51c and even tried using mpeg2dec3g.dll 1.0.0 aswell. Everytime I had the same error.

I changed the CCE version to CCE SP 2.67 trial with eclcce.exe and... no more #0004 error.

Just thought this might be of help to people who suffering like myself.

Stephen

goc

8th June 2004, 10:34

hi,

i'm not sure but what is the relation between version of CCE installed and rebulding phase ? none ?

and q to creator of this cool tool : can i put all required files into one folder and manually edit rebuilder.ini and remove paths to files with just *.exe and *.dll names ?

thanks in advance

P.S. as i said "COOL TOOL" if you need tag line or sumtin' like that :cool:

jdobbs

8th June 2004, 14:26

Originally posted by smreid
Hi Guys,

I have never posted to this forum and in fact subcribed because of this problem. I was using CCE Basic 2.69, Avisynth 2.54, mpeg2dec3g.dll 1.0.1 and I had this consistantly with every DVD I tried to burn (8 dvds). I tried DVD-RB versions 0.49, 0.51 and 0.51c and even tried using mpeg2dec3g.dll 1.0.0 aswell. Everytime I had the same error.

I changed the CCE version to CCE SP 2.67 trial with eclcce.exe and... no more #0004 error.

Just thought this might be of help to people who suffering like myself.

Stephen I'll take a look at this to see why it would act differently using CCE Basic 2.69.

smreid

9th June 2004, 08:43

Thanks

It would be nice to know why this was happening. It seems that loads of people have got it working with basic (from what I can gather by reading the forums) but however hard I tried I just couldn't get it working. The configuration in DVD-RB was exactly the same with both versions of CCE yet one give the 0004 error and the other didn't.

If you want me to post the configuration I used to help you recreate the problem then let me know.

By the way, thanks for a GREAT application.

Stephen

k-c-ksum

9th June 2004, 18:44

ive been getting the 0004 error on alot of titles, it always seams to happen at or near the end.

The only fix i have found is to copy over uncompiled vts's and ifoedit get vts sectors and then run the whole thing through a transcoder leaving the correctly authored vts's untouched.

Jomile

10th June 2004, 16:37

Hello all.
I have read through all your posts and dont see anything that solves my issue. I have cce 2.67 and DVR-RB .51c.
I have backed up about 20 dvds with DVD-RB and more importantly 5 or so with this version of dvd-rb and had no problems.

I am working on American Beauty and during the rebuild phase i get the overflow error. Any advice is muchly appreciated.

Thanks

JoMiLe

Dreeke

15th June 2004, 19:42

1. DVD-RB Version: 0.51c (and b)
2. Encoder being used: CCE BASIC 2.69.01.08
3. Using eclCCE? No
4. DVD: The longest day (PAL)
5. Bug encountered: Error #0004 when rebuilding buffer overflow

I didn´t test this with the latest version because the dvd used is a bit long.
Whit the following everything was fine:
2. Encoder being used: CCE SP 2.67.00.23
3. Using eclCCE? Yes

The error came up when rebuilding and in the first 10%, maybe this will help.

geezer

16th June 2004, 00:52

There is a new version of CCE-Basic 2.69.01.09.

Bug Fix
- In 2.69.01.08, 2-pass mode encoding was not stable.

May be worth a shot ??

clarkkent333

16th June 2004, 03:15

I was having this same problem using CCE Basic 2.6+. I switched over to CCESP 2.66+ and elCCE and haven't encountered it since.

old-hack

19th June 2004, 18:28

I purchased CCE Basic 2.69. I'm not happy hearing that people have to switch to a trial version or bootlegged version of CCE to eliminate the #0004 error.

jdobbs

19th June 2004, 19:28

Originally posted by old-hack
I purchased CCE Basic 2.69. I'm not happy hearing that people have to switch to a trial version or bootlegged version of CCE to eliminate the #0004 error. Just to clear the air... the 0004 error is not related to the use of CCE at all (version 2.69 or any other).

In fact, error 0004 relates to the flow of data that is being pulled from the original DVD, not the MV2 stream that was generated by CCE.

I would suggest, though, that you download the latest update from Cinemacraft (2.69.01.09), because it says the previous version wasn't stable in 2 pass mode (which is what DVD-RB uses).

jdobbs

19th June 2004, 21:26

Also... I am using Basic 2.69, and have been consistently -- and I've never gotten a 0004 error (at least not in any of the last several versions of DVD-R).

geezer

19th June 2004, 22:05

I use CCE-Basic 2.69 as well and haven't experienced the 0004 error either. I use DVDDecrypter v 3.2.2.0 or DVDShrink 3.1.7 to rip. I also use DVDRemake Pro 2.0.1 or Shrink to preprocess before rebuilding.

System Specs
XP SP1a
P4 2.4 w/ 512 MB RAM <-- yes, I have another 512 on the way...
100Gb Western Digital HD NTFS file system
Avisynth 2.54
MPEG2dec2dg.dll v1.01
DVD-RB 0.52

old-hack

20th June 2004, 07:10

Just to clear my own mind, I stripped the angles of the movie I was working on with DVDDecryptor instead of DVDRemake Pro. DVDRebuild processed the movie without generating error #0004. So clearly it must be how angles are stripped that impacts DVDRebuild's ability to complete the process without error.

old-hack

20th June 2004, 21:08

Just downloaded DVDRemake Pro 2.1 and DVDRebuild .053. Need a few hours to test out the angle thing and report back. Also have version 2.69.01.09 of CCE Basic.

old-hack

20th June 2004, 22:27

Not sure if this was a valid test, but wanted to report it anyway.

Since my successful rebuild process started with DVDDecryptor to remove angles and then DVDRemake Pro to remove unwanted video segments, I already had the encoded video segments (from the encode step of DVDRebuild) and the contents of the D2VAVS folder still there.

So I only re-did my stripping process using DVDRemake Pro 2.1 to remove angles and unwanted video segments. With these files as the source for DVDRebuild.053, I was able to rebuild the already encoded video created during the encoding process of DVDRebuild (using CCE Basic 2.69.01.09).

On this pass, DVDRebuild did not generate Error #0004. So I believe DVDRemake Pro 2.1 solved the angle stripping issue.

I didn't think it was necessary to go through the encoding step of DVDRebuild to verify if the DVDRemake 2.1 source files were stable for rebuilding with the encoded video streams.

EDIT: There was an error at the end of the rebuild process (error 6). So I'm re-encoding and will report results later tonight.

old-hack

21st June 2004, 03:21

Just finished my Star Wars Episode 1 backup project. DVDRemake Pro 2.1 stripped angles, unwanted menus, unnecessary video, and allowed me to select which of 3 menu systems to keep.

No DVDRebuild errors.

wmansir

21st June 2004, 03:27

jdobbs has informed me 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. Since DVD-RB doesn't support modified files, I'm going to close this in the known issues sticky.

thesicilian

21st June 2004, 08:20

Originally posted by wmansir
jdobbs has informed me 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. Since DVD-RB doesn't support modified files, I'm going to close this in the known issues sticky.

I know this statement is incorect, i've tried 2 rips using dvd decrypter. Nothing was changed & not other processing was attempted. Both trys at encoding resulting in the error 0004.

Is it actually the cce basic version that people are using?

Does this software actually give better backups that Dvd shrink etc...?

Is it worth buying the latest cce basic?

Is it worth percivering with the software to get to work?

NobbyNobbs

21st June 2004, 11:05

What version of DVDDecrypter did you use, did you rip in ISO mode ?
Older versions of DVDDecrypter had a bug, that left a small (0 byte ?) vob file encrypted, this gives the 004 error in RB.

thesicilian

21st June 2004, 11:30

Originally posted by NobbyNobbs
What version of DVDDecrypter did you use, did you rip in ISO mode ?
Older versions of DVDDecrypter had a bug, that left a small (0 byte ?) vob file encrypted, this gives the 004 error in RB.

Pretty sure its the latest versio, i'll check when I get home.

What difference would iso mode do? Please explain.

NobbyNobbs

21st June 2004, 11:35

There was a bug that was fixed in the latest version, I have experienced this myself, (also believed I had used the latest version, but had actually used the version before)
As far as I know, the bug only showed in ISO mode.

thesicilian

21st June 2004, 11:50

OK, let me get this right. :)

Non iso mode & latest version, should work ok?

I know I never used iso mode & i'll check version lunch time.

NobbyNobbs

21st June 2004, 12:14

Latest version works ok with ISO mode, on older versions some discs (Babylon 5 season 5 & 6 among others )will give the 004 error in RB.
Older versions should work ok in file mode, but I personally prefer ISO mode.

thesicilian

21st June 2004, 13:56

I check my dvd decrypter version. It is the latest version. I've left it encoding using QuEnc to see if it works with the rip I tried with CCE Basic.

Why would iso mode make any difference?

I'll post QuEnc results tonight.

old-hack

21st June 2004, 16:27

Originally posted by wmansir
jdobbs has informed me 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. Since DVD-RB doesn't support modified files, I'm going to close this in the known issues sticky.

Thought I'd double check this response. If the intent of DVD-RB is to only process original DVD content, then DVD-RB has no responsibility for successful processing of any DVD material that is the result of stripping unwanted material?

Here are some examples of preprocessing programs:

DVD Stripper
DVD Remake
DVD Remake Pro (strips angles and unwanted video)
DVD_Decryptor (strips angles, audio streams, and subtitle streams)
IFOEdit (strips lots of stuff)
DVD-Replica

Let me know if I've interpreted the statement above correctly.

wmansir

21st June 2004, 17:30

That's correct. The problem is that those programs can alter the structure in any number of ways and jdobbs wants to concentrate on getting original, unmodified discs to work. So if users are receiving this error with original discs it would still be helpful to report it here.

Of course you can still use preprocessing tools. I use them all the time myself and have never gotten error #0004. But if you encounter an error you should rerun your job on the original source and see if the problem still exits.

thesicilian

21st June 2004, 22:48

I'm ripping from orig discs. Been using dvd decrypter in file mode & iso mode. Same error with both. I've just tried smart ripper, encoding as I type this. Will post results in morn. If this fails I'm gonna try it with QuEnc.

jdobbs

22nd June 2004, 02:07

Originally posted by thesicilian
I'm ripping from orig discs. Been using dvd decrypter in file mode & iso mode. Same error with both. I've just tried smart ripper, encoding as I type this. Will post results in morn. If this fails I'm gonna try it with QuEnc. Are you removing angles when using DVD Decrypter? Also, ISO or not should be the same.

thesicilian

22nd June 2004, 06:16

Originally posted by jdobbs
Are you removing angles when using DVD Decrypter? Also, ISO or not should be the same.

Just looked in DVD Decrypter settings -> File Mode tab. Multi Angle Processing was unchecked so I suppose angles would be stripped ;)
Remove IFO/BUP RC Protection was checked, Remove IFO/BUP RCE Protection was checked and alos Patch M2V Timecode was checked.

My guess is that rip has been altered. I'm gonna uncheck all & enable multi angle processing with all the angles. Stream processing I will check show all. Select files is set to all.

Please can someone else post their settings In file mode. Once I have someone elses settings I will re rip & encode again.

BTW the rip I done with smartripper failed also. Different movie altogether.

thesicilian

22nd June 2004, 11:53

Is version 0.53a a fix for this error?

Version 0.53a

- IMPORTANT BUG FIX. Fixed an error in which original (unchanged) files were not being copied correctly into the destination directory. This could cause created directories to fail upon write.

Sir Didymus

22nd June 2004, 12:17

Originally posted by thesicilian
Is version 0.53a a fix for this error?

Version 0.53a

- IMPORTANT BUG FIX. Fixed an error in which original (unchanged) files were not being copied correctly into the destination directory. This could cause created directories to fail upon write.

No. Error #0004 is related to troubles in the source, while the fix is for missing copy of original vob files (no point in processing "fragments" less than 50 MB).

Error #0004 is most probably depending to specific problems in your configuration.

Please read carefully all the pages of this thread, since useful suggestions to people that actually have solved the problem have been already indicated...

EDIT: Obvious to say, but in any case 0.53a is more recent than 0.53, so better anyway to use the newer available release...

thesicilian

22nd June 2004, 16:52

Checked the config over & over again. Re installed software etc etc.

Sir Didymus

22nd June 2004, 18:12

@thesicilian

- Is it occurring to just one title or it is a systematic error, on every DVD you try to backup ?
- What release of decrypter are you using ?
- What release of avisynth ?
- What type and release of CCE are you using ?
- Are you using eclcce ? What release ?
- Is eclcce pointing to the right cce exe file ?
- Is DVD-RB pointing to eclcce (not directly to cce) ?
- Are the CCE Options of DVD-RB set to the right type of CCE ?
- How long did it take to complete the prepare step ?
- And the encoding ?
- Did you check if the results of the prepare step are all ok [playing the avs files with a media player] ?
- Did you check if all of the results of the encode are ok [playing the m2v files] ?

Sorry for asking all of this stuff, but errors #0004 are supposed to be absent at the present stage of development, and the beta testing on the subject has been carried out by lot of people for a lot of time, so the possibility of a problem in the application is now very low, at least on my undestanding (and on my experience); on the other hand what I have seen is that the error is a clear indication of some configuration problems, and this is a certainty if you observe #0004 on all of your attempts.

Cheers,
SD

Gurm

22nd June 2004, 18:44

Ok here's the situation.

I receive Error #0004 on exactly ONE DVD so far.

Paycheck.

I ripped it using the last version of DVD Decrypter (currently it's on 3.2.2.0 and I was using 3.2.1.0), so that might have something to do with it. I can re-rip using the newest version and see if that helps at all...

At any rate, I have done NOTHING to it. I simply ripped it to a folder, and pointed DVD Rebuilder (0.52) at it, and it went all the way through encoding to the last phase (rebuilding) and on the 7th segment it gets an Error #0004. That's it.

It's not imaginary, I'm not getting it for EVERY disc, but it DOES happen, reproducibly. If you need me to jump through some hoops for the sake of debugging, I'll be happy to fiddle. Just PM me on here.

- Gurm

Sir Didymus

23rd June 2004, 08:46

@Gurm:
Please give it a try with the latest release of decrypter. It is fundamental. I experienced #0004 errors, but just on few titles, and just up to release 0.44 of DVD-RB. Starting with release 0.45, I never got the error any longer.

This is just my experience, and I did not want to say other else than: please double and triple check your configuration in order to be totally sure the trouble is not depending to some configuration troubles, since this was the case for other people.

Also, could you please check your title has not ILVU units or multiangle features ? These are actually not (yet...) supported, and DVD-RB should report it; it is anyway easy to check with ifoedit...

see:
http://forum.doom9.org/showthread.php?s=&threadid=76680&highlight=how+to+check+multiangle

thesicilian

23rd June 2004, 08:52

@ Sir Didymus

Yes its happening on every rip.
Latest release of DVD Decrypter 3.2.2.0.
Latest release of avi synth 2.5.4
Latest release of eclcce with CCE 2.5SP
Yes eclcce is pointing to the correct CCE.exe
Yes DVD-RB is pointing to eclcce
Yes the cce option are correct
Prepare takes between 5-8 minutes, depends on length of movie
Encoding takes 1-2 hours, again depends on movie length
Have not checked the results.

This morning I set up latest DVD-RB with CCE 2.5 SP & eclcce. Set it to one click mode & left it. My earlier trials were done with CCE Bascic 2.69. Will be going home lunch time & I will post results. I will also post a screen shot of my set up tonight to prove I all setup correctly. The rip I am currently backing up is attack of the clones.

One thing I do want to point out though is that I ripped phantom manace with DVD Decrypter in file mode, all with default settings. I loaded it into DVD-RB & I got an error message saying that the movie was multiangle or something like that & that DVD-RB does not support it. I will also post a screen shot of this error later. This must prove that DVD Decryepter is not stripping angles like mention earlier in this thread.

thesicilian

23rd June 2004, 13:10

YES!!!!

It worked perfect with eclcce & CCE 2.500 SP. I must say, the results are excellent compared to dvd shrink.

Gonna test now with CCE2.67 & eclcce.

Will post results.

robot1

23rd June 2004, 20:55

Originally posted by thesicilian
The rip I am currently backing up is attack of the clones.

One thing I do want to point out though is that I ripped phantom manace with DVD Decrypter in file mode, all with default settings. I loaded it into DVD-RB & I got an error message saying that the movie was multiangle or something like that & that DVD-RB does not support it. Attack of the clones R2 is multiangle: initial text and end credits in two languages.

thesicilian

24th June 2004, 07:27

Originally posted by robot1
Attack of the clones R2 is multiangle: initial text and end credits in two languages.

Well if it was multiangle it converted ok. :)

Just done another with CCE 2.67 & eclcce, worked great again.

Dimad

24th June 2004, 09:48

Could the problem be related to "Steal Space" option?

http://forum.doom9.org/showthread.php?postid=515433#post515433

scioper

25th June 2004, 07:44

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

25th June 2004, 08:01

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

25th June 2004, 10:30

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

25th June 2004, 10:47

Try upgrading to the newest CCE Basic first.

scioper

25th June 2004, 13:36

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

25th June 2004, 13:43

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

25th June 2004, 13:52

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

25th June 2004, 14:06

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

25th June 2004, 14:14

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

25th June 2004, 16:20

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

26th June 2004, 12:26

So am I.

Axlemar

27th June 2004, 10:43

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

27th June 2004, 12:50

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

27th June 2004, 13:44

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

27th June 2004, 19:45

:( 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

27th June 2004, 23:40

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

28th June 2004, 05:22

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

28th June 2004, 08:35

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

28th June 2004, 08:55

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

28th June 2004, 09:31

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

28th June 2004, 10:13

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

28th June 2004, 17:10

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

28th June 2004, 19:59

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

30th June 2004, 08:11

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

30th June 2004, 11:49

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

scioper

30th June 2004, 13:14

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

1st July 2004, 10:02

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

1st July 2004, 11:40

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

1st July 2004, 12:23

@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

1st July 2004, 16:01

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

1st July 2004, 16:31

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

1st July 2004, 18:09

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

1st July 2004, 22:34

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

1st July 2004, 22:58

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

1st July 2004, 23:25

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

2nd July 2004, 08:01

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

2nd July 2004, 09:50

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

2nd July 2004, 10:56

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

2nd July 2004, 11:59

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

2nd July 2004, 13:22

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

2nd July 2004, 14:56

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

2nd July 2004, 17:21

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

3rd July 2004, 14:55

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

12th July 2004, 17:51

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

16th July 2004, 11:05

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

17th July 2004, 01:52

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

18th July 2004, 14:53

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

18th July 2004, 15:20

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

johnnyquid

24th July 2004, 16:50

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

24th July 2004, 20:26

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.

goc

24th July 2004, 20:46

i'm confused here ...
it seemes that some of us are getting 0004 buffer overflow while encoding and others like me while rebuilding ?

or need i some coffee ? thanks.

jdobbs

24th July 2004, 21:41

Originally posted by goc
i'm confused here ...
it seemes that some of us are getting 0004 buffer overflow while encoding and others like me while rebuilding ?

or need i some coffee ? thanks. Well... since the error #0004 only exists in the rebuilding phase, I'd say getting it during encoding would be something along the lines of virgin birth... ;)

johnnyquid

25th July 2004, 04:41

Jdobbs,

I did not see any settings in Rebuilder to cause deinterlacing. I used the default settings of Rebuilder. I did set the path for decomb in the setup settings. Does that cause deinterlacing to be done?

I did latter use vobblanker to blank of all but the first VTS of the American Beauty DVD and rebuilder worked fine (except that of course I did not get any of the extra material).

goc

25th July 2004, 19:31

Originally posted by jdobbs
Well... since the error #0004 only exists in the rebuilding phase, I'd say getting it during encoding would be something along the lines of virgin birth... ;)

aha. :D ok, i'll better get me some beer ...

and yes ... i have to admit it, when getting 0004 with cce i simply start over again with quenc and everything works fine ... even the quality of the quenc encoding is great

q: when will procoder or tmgenc support be available in dvd-rb ?

seeyaz

Jester700

26th July 2004, 01:35

So, I've noticed that on my current backup (The Sound of Music, R1) it gives me the #0004 error on the first segment where there IS an AVS file in the D2VAVS folder, but NO corresponding .m2v file. If the error is caused because there IS supposed to be such a file, would it be possible to go in and modify the script so that any "missing" .m2v files were generated (and only those), and then continue on with rebuilding?

This problem happens on a good third of my movies or so, but not all of them. I've reinstalled Avisynth and plugin several times, and redid a new dvdrebuilder.ini with each new beta.

Sir Didymus

26th July 2004, 10:43

Originally posted by Jester700
So, I've noticed that on my current backup (The Sound of Music, R1) it gives me the #0004 error on the first segment where there IS an AVS file in the D2VAVS folder, but NO corresponding .m2v file. If the error is caused because there IS supposed to be such a file, would it be possible to go in and modify the script so that any "missing" .m2v files were generated (and only those), and then continue on with rebuilding?

This problem happens on a good third of my movies or so, but not all of them. I've reinstalled Avisynth and plugin several times, and redid a new dvdrebuilder.ini with each new beta.

An m2v file should be present for every avs in the D2AVS folder.

It should be very interesting to know why in your setup this file is missing...

You may try to manually encode the missing file; it is quite simple: you extract and save as a temporary ecl, from the rebuilder.ecl file, using a text editor the [item] and [file] part corresponding to the missing file. Then you start eclcce feeding it with the temporary ecl. It should produce a m2v corresponding to the avs...

johnnyquid

29th July 2004, 03:32

Jdobbs,

I restarted the rebuild process from scratch for NTSC American Beauty DVD using Quenc instead of CCE and got the same #0004 error message. It appears to occur during the extras. As I mentioned before a large number of small m2v files are getting created (about 50-60 files less than 20KB) perhaps this is the cause.

brownstem

21st August 2004, 06:36

Hi, I'm also having trouble with getting "buffer overflow, Error #0004" in Rebuilder. I've read the other similar postings but can't seem to figure out what I should do next. So far it's happened with both discs I've tried. Some details:

FIRST DISC (Ripley's Game):

The status box behind the error reads this at the point the error occurs:

Phase III, Rebuild started.....
.......
.......
- Rebuilding segment 3 VOBID:1 CELLID: 4

So I'm guessing that CCE has done it's job correctly prior to the error happening. More details:

- AviSynth is the latest version (2.54)

- The MPEG2Dec3dg.dll file is inside the main Rebuilder folder (per the main afterdawn Rebuilder guide)

- CCE Basic is version 2.69.1.4

- DVD Decrypter is the latest version as well

- I ripped all files in file mode, removing nothing (I did set Rebuilder to remove subtitles except English, per the guide)

- There is over 150GB available on a brand-new machine (P4, 512, 3.2GHz)

So far this error has repeated itself over three attempts.

SECOND DISC (Out of the Ashes):

Everything the same (full file mode in Decrypter, no changes, etc.). This time the 0004 error comes here:

- Rebuilding segment 66 VOBID:58 CELLID: 5

As I said before, I've configured everything via the instrux in the afterdawn.com guide (very straightforward). Is there anything else I can change to get Rebuilder (or CCE, if that's in fact where the problem is) working? I'm about to give up and go back to Shrink and Pinnacle Instant Copy! Thanks.

brownstem

21st August 2004, 07:19

Since the forum won't let me edit my own post (go figure), here's yet another example. My third try was with Open Range, this time the error comes at:

Rebuilding Segment 5 VOBID:3 CELLID: 4

Pretty obvious this is going to continue with every dvd I try, so what am I doing wrong? Is there something in the afterdawn.com guide settings instructions (http://www.afterdawn.com/guides/archive/dvd_rebuilder_tutorial.cfm) that's wrong? Thanks.

jdobbs

21st August 2004, 10:55

I've done Open Range (NTSC) many times as it is one of my test discs. Best guess as to why you'd get this:

1. Are you editing out anything (extras or menus)?
- If so, what are you using to do it?
2. Are you performing other functions during encode?
- If so, are you accidentally stopping encode of one of the segments?

erdoke

21st August 2004, 13:31

Originally posted by brownstem
Since the forum won't let me edit my own post (go figure), here's yet another example. My third try was with Open Range, this time the error comes at:

Rebuilding Segment 5 VOBID:3 CELLID: 4

Pretty obvious this is going to continue with every dvd I try, so what am I doing wrong? Is there something in the afterdawn.com guide settings instructions (http://www.afterdawn.com/guides/archive/dvd_rebuilder_tutorial.cfm) that's wrong? Thanks.

Try to reinstall AviSynth first, then copy the MPEG2Dec3dg.dll file into the Avisynth plugins directory, and finally reconfigure RB (show it every file that needed).
I know a couple of guys who succeeded this way after having Buffer Overflow errors. I know nobody who succeeded with increasing Win pagefile though. I guess it is an avisynth issue, and RB fails during the Rebuild phase because the actual file is different to the info of it.
Maybe I am totally wrong and jdobbs will correct me, but I guess it worths a try.

brownstem

21st August 2004, 16:18

Thanks, but I'm neither editing anything out (I rip all files in Decrypter) nor am I performing any other functions during encoding (no AV software, screensaver, or anything). The whole process seems to be quite tidy right up until the inevitable 0004 error. What can I try next? Thanks.

Faust2

22nd August 2004, 00:26

I remember dimly I had once a 0004 during rebuild. I had rebuilder reading directly from the HD. I re-ripped the DVD, now using ISO-mode and mounted with daemontools, and guess what, the 0004 was gone.
Now if you ask me how on earth could this be related, I have no idea. But since then, I always used images as the source and never had a problem...

brownstem

22nd August 2004, 06:54

First off, thanks to all for your advice! OK, here's what I did:

1) uninstalled and reinstalled Avisynth, then moved MPEG2Dec3dg.dll to Avisynth plugin file (from Rebuilder folder)

2) installed latest version of Daemon Tools, then mounted a Decrypter-ripped ISO of Open Range.

Then I ran Rebuilder and once again (as always) completed the first two phases successfully. And also got another 0004 error at Segment 6 VOBID:3 CELLID:5

Once again I throw myself on the mercy of those who know more than I! Help!

Trahald

22nd August 2004, 19:31

@brownstem

some users in this thread have reported success trying quenc instead of cce. May be worth a shot.

brownstem

22nd August 2004, 21:12

Thanks, Trahald. Just tried my first go at Quenc, and it immediately delivered a "Bad Parameter" error as soon as Phase 2 began. I suppose this should be less frustrating since at least it's happening very early in the process ;-)

So now I'm back where I started. Given that EVERYTHING I've tried has resulted in errors, I'm now thinking that the decrypted files could be causing the problem. On the other hand, these same decrypted files (whether in File or ISO mode) work just dandy when used with Shrink, InstantCopy, DVD2One, you name it.

Should I simply uninstall everything and start over, trying to use EclCCE with CCE instead of Basic or Quenc? I am truly at the end of my rope :scared:

jdobbs

22nd August 2004, 21:53

The QuEnc error is easy. DVD-RB v0.56 doesn't support QuEnc above version 0.51. It will, though, starting with DVD-RB v0.57 (at which point it will no longer support the earlier QuEnc versions)...

brownstem

22nd August 2004, 22:23

Easy enough on QuEnc, then. So now I'm trying Open Range (using file mode rip) with CCE SP and EclCCE. If I get another 0004 I may overflow my own buffer!

Sweet...I may have to deal with the logo, but at least it works. Plus, no probs with the earlier version of QuEnc. Thanks, guys.

One last question: Since I was asked if I had removed anything from the dvd before beginning the whole process, is there something I can use which will safely remove unwanted stuff (extras, warnings, etc.) before I begin the Rebuilder/CCE process? It would be ideal to have a Rebuilder-viable set of files which have already had the extra garbage removed, right?

TheSeeker

23rd August 2004, 14:20

Use ifoedit (free, but more complicated) or dvd remake to get rid of unwanted extras, or buttons before running through cce+rebuilder.

erdoke

23rd August 2004, 14:56

Originally posted by TheSeeker
Use ifoedit (free, but more complicated) or dvd remake to get rid of unwanted extras, or buttons before running through cce+rebuilder.

VobBlanker and PGCEdit are also very good at stripping and blanking. They are free and not so complicated that IFOEdit.

brownstem

23rd August 2004, 18:02

Thanks for the tips. JDobbs, do you "officially" give the OK to using any of these tools before running Rebuilder/CCE?

erdoke

23rd August 2004, 23:25

I was reading the CCE FAQ here in the forum (exactly here (http://forum.doom9.org/showthread.php?s=&threadid=53770)) and look what I've found:

Q14.3: CCE-SP 2.66/2.67/CCE-Basic leaks memory when encoding from an AVISynth script. How can I fix this?

A: Yes, there is a bug in CCE-SP 2.66 throughout 2.67.00.23. When you are monitoring memory usage in task manager during encoding and AVISynth script in these versions, you'll notice that for each file and for each encoding pass (be that one pass VBR, CBR or multipass VBR) the program grabs another large chunk of memory and never releases it until the program is closed. Depending on the number of files and passes, you can eventually run out of memory.

The fix for this again is to add a fake audio track to the AVISynth script as outlined in Q14.1, above. However, another memory leak with AVISynth scripts that cannot be worked around this way occurs every time you open the "File Settings" dialog in CCE (where you specify chapters and encode range etc.).

Both issues are finally fixed in CCE-SP 2.67.00.27, not fake audio tracks necessary anymore.

Do you think what I do, or I am completely going in the wrong direction? Anybody got this buffer overflow error with CCE SP 2.50?

SansGrip

26th August 2004, 16:57

I too am getting a buffer overflow, error #0004, on Gambling, Gods and LSD, NTSC R1. What I did:

- Ripped to HD with DVD Decrypter 3.2.3.0 (file mode, remove Macrovision, splitting by file, no multi angle processing, remove IFO/BUP RC protection, remove IFO/BUP RCE protection, remove IFO/BUP PUOs, remove VOB PUOs, patch M2V timecode)
- Prepare with DVD-RB 0.56 (remove audio track 2, CCE 2.66+ mode, dynamically assign bitrates)
- Encode with CCE 2.67.00.23 and EclCCE 1.81 (VBR bias 25, quality prec 16, 2 passes)
- Rebuild fails with error #0004 at the very end of segment 10

I'm using Avisynth 2.54 (build Jan 26 2004), and the version of Mpeg2Dec recommended in the DVD-RB sticky.

Avisynth and CCE seem to be working 100% correctly, since I tested a number of the cells and found the resulting M2V to have precisely the right number of frames (as well as the right resolution, frame rate, etc.).

I didn't do any preprocessing, though I get the same error if I use VOBs first stripped of extras etc.

I'm more or less certain that this is not a problem with my configuration. I've done at least 15 backups successfully with those versions of DVD Decrypter, Avisynth and Mpeg2Dec. I switched to CCE 2.67.00.23 last night (from .27) in an effort to resolve this, but it didn't help.

From what I've read it seems this is a problem with the source material, in which when it comes to flushing the buffer at the end of the cell DVD-RB will error out if there's a large number of video or audio packets remaining, indicating a possible timestamp corruption. I can understand why jdobbs says this should never happen if you run DVD-RB on the original VOBs...

Could this be caused by "patch M2V timecode" in DVD Decrypter?

I'm going to try doing a "no compression" pass in DVD Shrink to remove the extras and second audio track, then rerunning DVD-RB on that set of VOBs. I don't hold out much hope, but it's worth a try.

Any suggestions appreciated.

SansGrip

26th August 2004, 21:20

UPDATE: Much to my surprise, running it through DVD Shrink seemed to fix the #0004 error. Here's what I did:

- Took the stripped version (minus extras, warning screens, menus edited to remove buttons, etc.) -- which also produced a #0004 error from DVD-RB -- and ran it through DVD Shrink 3.2.0.15, selecting "no compression" for all the parts. I also unselected the 2-channel AC3 audio from the main movie
- "Backed up" with those settings to a folder on my HD
- Used that folder as the source for DVD-RB

Hey presto, no more #0004 error. Which leads me to believe either:

1) There's some flaw in the original VOBs which causes problems for DVD-RB but not DVD Shrink, and DVD Shrink fixes the flaw upon remuxing (it must remux in this case, since I removed one of the audio streams), or
2) DVD-RB has a bug that produces a #0004 very rarely, even on the original VOBs of a movie

Either way, it appears it's not as simple as being a configuration error.

SansGrip

28th August 2004, 22:14

Bump.

Faust2

28th August 2004, 22:18

UPDATE: Much to my surprise, running it through DVD Shrink seemed to fix the #0004 error. Here's what I did:

- Took the stripped version (minus extras, warning screens, menus edited to remove buttons, etc.) -- which also produced a #0004 error from DVD-RB -- and ran it through DVD Shrink 3.2.0.15, selecting "no compression" for all the parts. I also unselected the 2-channel AC3 audio from the main movie
- "Backed up" with those settings to a folder on my HD
- Used that folder as the source for DVD-RB

Hey presto, no more #0004 error. Which leads me to believe either:

1) There's some flaw in the original VOBs which causes problems for DVD-RB but not DVD Shrink, and DVD Shrink fixes the flaw upon remuxing (it must remux in this case, since I removed one of the audio streams), or
2) DVD-RB has a bug that produces a #0004 very rarely, even on the original VOBs of a movie

Now that's really interesting! I must remember this for my next meeting with "#4 lives!" (wich is not very likely, but not impossible either!)

But, isn't there also:

3) something in the preprocessing step screwed up the structure, and shrink fixed THIS error(s)?

Or am I just not getting something... :)

SansGrip

28th August 2004, 23:46

Originally posted by Faust2
3) something in the preprocessing step screwed up the structure, and shrink fixed THIS error(s)?
Nope. With that disc I got #0004 on the original, unaltered VOBs.

SansGrip

1st September 2004, 00:31

*Bump* again ;)

progoth

13th September 2004, 07:19

I just wanted to add my own "me too" to this issue

I started using DVD-RB just a few weeks ago and have had great success with every dvd I've tried. Today I did a straight all-files rip of American Beauty ("Awards Edition" or something), didn't try to remove anything, and was reencoding that. I have CCE SP 2.50.01.00, using EclCCE.exe since it wouldn't work without it, CCE SP (v2.50) selected in CCE menu. DVD-RB 0.59

* Dynamically Assign cell bitrates
* steal space from extras -> 33%
* half-d1 and half space for extras

The re-encoding happens fine, m2vs all play fine, and it seems to rebuild just fine, until the very end when i get the #0004 error.

So anyway I can provide any more details if they'd be of any use; I've got enough hd to keep the files around for a while. Post if i can provide any useful information

UPDATE

I read the beginning and end pages, but not the middle...seems johnnyquid and I are having the exact same problem, 98% done, dying on the tiny extras segments of vts4 or 5. We are definitely using different versions of CCE, same version of MPEG2Dec3dg (1.0.1.0). I don't know my Decomb.dll version, but I just downloaded all this stuff a few weeks ago, and I'm sure I got the latest (or whatever was recommended in the guide). I'm currently rebuilding again, so perhaps i can give some more exact details on when it happens.

OK my rebuild went exactly the same as last time, DVD Rebuilder experienced a buffer overflow. Error #0004. Process must abort. 99.7% done, rebuilding segment 7 vobid:1 cellid:1 I don't suppose that's a help, but...there it is.

(as a side note, for my own burning purposes I copied the original VTS 4 & 5 ifo/vobs, and still made it by 5.66megs....ha)

jdobbs

13th September 2004, 13:27

@progoth

How small are the segments that are being affected? I just had a thought that maybe this as a result of the reduction being too great on a small segment.

progoth

13th September 2004, 14:31

OK the original VTS_04_1.VOB is 111,013,888 bytes

in D2VAVS there are 52 sets of 4 V04###########.(AVS|FLG|m2v|vaf)

Each m2v in this is right around 31 KB, for a grand total of 1.60 MB. I suppose they are stills, with audio, to have an original size of ~100megs...

absinthe

26th January 2005, 20:59

Whew, I believe I've read this whole darn thread. Now I'm having this problem and I don't see any answers as yet ... and the thread seems to have gotten ooooooold.

This is the first time I've had this problem with Rebuilder (latest public release version - 0.70). I used CCE SP 2.67, the latest AviSynth, and the brand new DGDecode.dll. Yes, I have altered the source files considerably with VobBlanker, but in reading previous entries in this thread that doesn't necessarily seem to be the source of the problem.

What's most frustrating is when the error happens, at about 85-90% of rebuilding. I tried rebuilding the same encoded files twice.

Now I'm giving QuEnc a try. We'll see how that goes. If I get the 0004 error again I may try the "SansGrip method" and run the files through DVD Shrink without compression before rebuilding.

Man, this is like 20 hours of encoding on my lil' Athlon XP 1600 :(

-abs

jdobbs

26th January 2005, 21:16

Yes, I have altered the source files considerably with VobBlanker, but in reading previous entries in this thread that doesn't necessarily seem to be the source of the problem. I don't think I'd agree with that... my experience has been that often the "preprocessing" step is left out of the problem description, or was believed to be "unrelated" (not always -- but often).

With that said... I've added some code in v0.73 that will make it more robust toward timing inconsistencies which is almost always the source of this problem.

Some of the examples I've seen that have caused this are huge SCR gaps in the middle of a cell, or inconsistencies between the DTS/PTS and the SCR.

I noted someone making a comment earlier about how I don't want to hear about the #0004 -- that error is kicked out by my code when it finds something wrong with the source. It isn't my error, it is my software identifying an error that exists in the source. I don't think I could have been clearer.

dannyv

26th January 2005, 23:02

Originally posted by jdobbs

With that said... I've added some code in v0.73 that will make it more robust toward timing inconsistencies which is almost always the source of this problem.

Any idea when you will release 0.73 and do you think it will help with my cce 2.67 problems. I beleave you are fimilure with the problems I was having with blank cells in interlaced TV eposodic dvd's. We discussed it in several prior threads.

absinthe

27th January 2005, 00:10

jdobbs,

QuEnc is still encoding, and I've been previewing some of the segments as they complete. I've come across one that is "0 bytes," and Media Player Classic "Cannot render the file." The corresponding script indicates that it should be 251 frames.

Is this normal, or indicative of a problem ... ?

Encoding is now about 85% finished, so if the rebuilding phase puts things back together in the same order ... this is about where I would get an error #0004.

-abs

jdobbs

27th January 2005, 01:48

That's not normal. Look at the .AVS file, play it back, and see (with a text editor) the frame range.

absinthe

27th January 2005, 03:20

Ok, encoding is done and I got the 0004 error at about the same spot in the rebuilding phase. There is definitely that one, single segment that is 0 kb in size and cannot be rendered.

It's script indicates it should be 251 frames (Trim(127813,128063)). The script will open in VirtualDub, and it's 10 seconds of blank/black, which is what I would expect.

I can't explain why this one segment didn't encode, but I'm assuming the same thing might have happened when I used CCE, and I'm thinking this is the reason for the 0004 error (eh?).

Is there a way I can properly re-encode this one segment, and then rebuild?

-abs

jdobbs

27th January 2005, 04:49

Which DVD are you attempting?

absinthe

27th January 2005, 05:06

Originally posted by jdobbs
Which DVD are you attempting? Code 46 (region 1)

I have blanked all PGCs with previews, warnings, and logos with VobBlanker. I've kept the main movie, deleted scenes, trailer, and a 15-minute "making of" featurette.

-abs

edit: Hey wow, this was my 100th post :D

absinthe

27th January 2005, 15:06

Does anyone know if I can manually re-encode a single segment? I remember seeing a post somewhere in this sub-forum on doing this, but I've searched and searched and can't find it ...

-abs

Sir Didymus

27th January 2005, 16:02

Here it is:

1. Open with a text editor the file rebuilder.ecl, in your D2VAVS folder

2. Extract the segment you want to re-encode [the part of the file including the "item2 and "file" tags]

3. Save this segment as item.ecl [or whatever name.ecl you want].

4. Manually Open CCE [or ECLCCE]. Drag & Drop or manually open the file you have saved.

5. Encode it...

An example, for re-encoding just the first segment of a given title, should be something like this:

; Cinema Craft Encoder SP -- Encoder Control List
; Created by DVD Rebuilder

[item]
title=V01000000001001
aud_out=0
vaf_file=E:\KILLBILL_VOL2\OUT\D2VAVS\V01000000001001.vaf
aud_file=E:\KILLBILL_VOL2\OUT\D2VAVS\V01000000001001.mpa
file_focused=0
packet_size=2048
width=720
height=576
frame_rate_idx=3
cbr_brate=6000
vbr_brate_avg=2576
vbr_brate_min=0
vbr_brate_max=8552
seq_endcode=0
dvd=0
half_width=0
half_height=0
lum_level=0
aspect_ratio=3
gop_m=3
gop_nm=4
gop_hdr=12
seq_hdr=1
all_closed_gop=0
fix_gop_length=0
samples_per_sec=44100
stereo=2
brate_idx=7
crc=1
progressive=0
alternate_scan=1
intra_dc_prec=2
aud_mode=0
tc_ref_frm=0
drop_frame=0
fix_vbv_delay=0
letter_box=0
pulldown_detect=0
offset_line=0
create_new_vaf=1
credits_tweak=0
credits_start=0x00000
credits_brate=1000
h_filter=0
h_filter_idx=8
dither=0
dither_max=8
qmat_idx=0
quality_prec=16
timecode=0x0000000
video_type=4
vid_file0=E:\KILLBILL_VOL2\OUT\D2VAVS\V01000000001001.m2v
vid_file1=E:\KILLBILL_VOL2\OUT\D2VAVS\V01000000001001.m2v
vid_out=1
vaf_out=1
opv_q_factor=20
opv_brate_min=0
opv_brate_max=6841
vbr_bias=25
vbr_pass=1
use_filter=0
filter_val=6
non_linear=1
top_first=0
mpeg1=0
mpeg1_cps=1

[file]
name=E:\KILLBILL_VOL2\OUT\D2VAVS\V01000000001001.avs
frame_first=0
frame_last=2875
encode_first=0
encode_last=2875

Also - On this thread:
http://forum.doom9.org/showthread.php?s=&threadid=75168
pages 6 & 7, it is explained how to extract one single m2v segment from the original title and reinserting this in the movie. Thinking better at this, the "No Compression" Mode of rebuilder is a very handy and useful manner for quickly demux (in another folder...) the whole source title... This way you may perform the tests you want, just taking the right m2v file from the uncompressed project and reinserting the same in your destination folder... Then rebuild it...

Cheers,
SD

absinthe

27th January 2005, 17:09

Thanks Sir Didymus! But how can I do this with QuEnc?

-abs

dannyv

27th January 2005, 17:14

Originally posted by absinthe

It's script indicates it should be 251 frames (Trim(127813,128063)). The script will open in VirtualDub, and it's 10 seconds of blank/black, which is what I would expect.
-abs

@Jdobbs

This is exactly the same problem I have with cce 2.67 and jtherippper is also having. Sir Didymus refers back to the discussion we had in his above post (look at link at bottom of post). In that post we substituted the corrupt single cell for the original cell and it did complete the rebuild process but the resulting project was full of audio dropouts. If you recall if you played the AVS file it had 10 seconds of black frames when the original was only .01-.07 seconds long. When done with cce 2.50 it completed fine with no errors and no dropouts. I still have the three titles on my hard drive if further testing is needed.

absinthe

27th January 2005, 17:30

Originally posted by absinthe
Thanks Sir Didymus! But how can I do this with QuEnc?

-abs
Oh, and if the answer is: just open the ECL file with QuEnc, I did that and received a "bad parameter" message. Could this be why the file didn't encode?

Here's the ECL file for the segment.
; QuEncode -- Encoder Information List
; Created by DVD Rebuilder

[item]
title=V05003400002009
aud_out=0
vaf_file=D:\REBUILD\D2VAVS\V05003400002009.vaf
aud_file=D:\REBUILD\D2VAVS\V05003400002009.mpa
file_focused=0
packet_size=2048
width=720
height=480
frame_rate_idx=1
cbr_brate=6000
vbr_brate_avg=161
vbr_brate_min=0
vbr_brate_max=8552
seq_endcode=0
dvd=0
half_width=0
half_height=0
lum_level=0
aspect_ratio=3
gop_m=3
gop_nm=4
gop_hdr=12
seq_hdr=1
all_closed_gop=0
fix_gop_length=0
samples_per_sec=44100
stereo=2
brate_idx=7
crc=1
progressive=1
alternate_scan=0
intra_dc_prec=2
encode_mode=0
vmode=2
fast_mode=0
quality_prec=24
timecode=0x0000000
vid_file0=D:\REBUILD\D2VAVS\V05003400002009.m2v
vid_file1=D:\REBUILD\D2VAVS\V05003400002009.m2v
vid_out=1
vaf_out=1
opv_q_factor=20
opv_brate_min=0
opv_brate_max=8552
vbr_bias=25
vbr_pass=6
use_filter=0
filter_val=6
non_linear=1
top_first=0
mpeg1=0
mpeg1_cps=1

[file]
name=D:\REBUILD\D2VAVS\V05003400002009.avs
frame_first=0
frame_last=251
encode_first=0
encode_last=251Any idea what the "bad parameter" might be?

-abs

Sir Didymus

27th January 2005, 17:35

@absinthe

If you want to substitute one segment with the original m2v file, the procedure is the same. If you want just to re-encode one single m2v sector using quenc, I suggest to run, in three click mode, a parallel project using the same source path and a different working path.

Then:

1. Run prepare for this parallel project.
2. Change manually, in the rebuilder.inf the section:

[Status]
mode=2
Original_Size=3849825
Excluded_Audio_Sub_Size=182484
VTS_01_SIZE=2599487
VTS_04_SIZE=415632
VTS_05_SIZE=302410
VTS_07_SIZE=47208
VTS_08_SIZE=45266
Progress=1
CCEType=3

adding the line "Encode_Progress"

[Status]
mode=2
Original_Size=3849825
Excluded_Audio_Sub_Size=182484
VTS_01_SIZE=2599487
VTS_04_SIZE=415632
VTS_05_SIZE=302410
VTS_07_SIZE=47208
VTS_08_SIZE=45266
Progress=1
CCEType=3
Encode_Progress=15

Putting the right progress nr. of the new segment you want to encode...

3. Close DVD-RB and restart it, in order to for the application to read the change you made in the .inf file.

4. Then run "Encode", that will start from the segment you have indicated...

Edit: QuEnc has a cli interface, so it is directly controlled by DVD-RB, without passing the control parameters by means of an external file. You simply can not prepare an ecl file to pass to QuEnc. You may manually prepare a dos script, feeding the right parameter extracted by the ecl files, but the previous method is easier... :)

absinthe

27th January 2005, 18:05

Hmmm ... a "0 kb" file is still created, and on watching it looks like QuEnc only did one pass on it.

I'm going to give extracting the original segment a try. If that doesn't work, I'm going to start all over with the original files ripped from the DVD. I will use VobBlanker as before, but I will not blank out all the short little several-second-long segments of blackness as I did before.

-abs

dannyv

27th January 2005, 18:16

Originally posted by absinthe

I'm going to give extracting the original segment a try.

-abs

Incerting the original blank cell for the corrupt cell and rebuilding again will most likly work. Make sure when you burn the finished project you do it to a DVD-RW then check it thorougly in a stand alone set top player. I found that after substituting the corrupt cells It played fine on the PC but I had a lot of audio dropouts on a set top player.

absinthe

27th January 2005, 18:43

Originally posted by dannyv
Incerting the original blank cell for the corrupt cell and rebuilding again will most likly work. Make sure when you burn the finished project you do it to a DVD-RW then check it thorougly in a stand alone set top player. I found that after substituting the corrupt cells It played fine on the PC but I had a lot of audio dropouts on a set top player. Will do. Thanks. Of course, the original cell isn't blank. It's blank. That is to say, what it contains is blankness. The segment encoded by Rebuilder is blank, but not in the sense that it contains blankness; rather in the sense of being truly blank, containing nothing at all (but nothing at all in the sense of containing some nothing). To sum up, the original blank cell is not blank (it contains blankness), but the segment encoded through Rebuilder is blank in the sense of being blank (sans blankness).

:D

Yeah, I was a sick child.

You ever try opening a "blank" segment with the latest GSpot. It reports it as being "blank, barren, and bare - vacant, vacuous, and void".

-abs

dannyv

27th January 2005, 18:52

Originally posted by absinthe
Will do. Thanks. Of course, the original cell isn't blank. It's blank. That is to say, what it contains is blankness. The segment encoded by Rebuilder is blank, but not in the sense that it contains blankness; rather in the sense of being truly blank, containing nothing at all (but nothing at all in the sense of containing some nothing). To sum up, the original blank cell is not blank (it contains blankness), but the segment encoded through Rebuilder is blank in the sense of being blank (sans blankness).

:D

Yeah, I was a sick child.

You ever try opening a "blank" segment with the latest GSpot. It reports it as being "blank, barren, and bare - vacant, vacuous, and void".

-abs

I am just as sick as you. Know why!!!!. I had no problem understanding what you just wrote:)

And as the same with my corrupt m2v's. What was said to be blank was really the blackest of blank blackness.

absinthe

27th January 2005, 19:10

Ok, VobEdit is driving me nuts. How do you identify a particular cell??

Rebuilder's script for the segment in question is V05003400002009.AVS. So I guess I need to open a VOB from VTS 5?? (my project only did encoding in VTS 5 and VTS 6).

But then I cannot identify a cell. The program is very frustrating. My script indicates "VOB ID 2, cell 9." In the left frame in VobEdit, I am able to find lines which read something like "VOB ID 2, Cell ...", but there's not enough room apparently for the cell number so there's just "..." And, I cannot resize the panels.

Dear Lord.

-abs

ZuZu

27th January 2005, 19:12

from the posts I've been reading I guess my last m2v file that the error occurs on was encoded wrong? is there any program that can tell wheather the video is compliant?

Sir Didymus

27th January 2005, 19:25

@ZuZu

Hey, what are you talking about ?
And what compliancy are you looking at ?

If DVD-RB ends its job without reporting errors, you shouldn't worry about.

Are you suffering from Error #0004 ?
Most probably you did some preprocessing...

If you didn't do any preprocessing and you experience #0004 then you may try to apply some patch like the one described previously... Or wait a little bit, since Jdobbs is working for making DVD-RB accepting some singularities in the input files, introduced some times by thirdy party preprocessing tools...

Cheers
SD

dannyv

27th January 2005, 19:35

Originally posted by absinthe
Ok, VobEdit is driving me nuts. How do you identify a particular cell??

Rebuilder's script for the segment in question is V05003400002009.AVS. So I guess I need to open a VOB from VTS 5?? (my project only did encoding in VTS 5 and VTS 6).

But then I cannot identify a cell. The program is very frustrating. My script indicates "VOB ID 2, cell 9." In the left frame in VobEdit, I am able to find lines which read something like "VOB ID 2, Cell ...", but there's not enough room apparently for the cell number so there's just "..." And, I cannot resize the panels.

Dear Lord.

-abs

in vobedit Open vts 5 and don't select anything from the left window just press the demux button and select cell id and select a temperary directory to save to. It will demux the entire vob via cell id and will save each cell id with the vob extension e.g. vts_05_001.vob.

Next in vobedit open vts_05_009.vob from the temperary directory where you saved the fies and press the demux button and select mpeg stream this will demux it into vts_05_009.m2v. Simply rename that file to the name of the corrupt file copy it to the d2vavs directory and do the rebuild again (Make sure your in 3 step mode so you don't do the whole prepare and encodde phase again).

Note: before rebuilding bring the M2V file into powerdvd and play it. It will most likly be a cell that is black (blank) and is .01 - .07 seconds long

ZuZu

27th January 2005, 19:41

@Sir Didymus

yes I did do some pre-processing, I didn't know it at the time that it would cause problems.

what if I prepared it again and moved the encoded files there, would it rebuild? then I could just blank it afterwards.

absinthe

27th January 2005, 19:51

Ok, I'm really getting thrown by these numbers.

How do I know exactly what original VOB my segment is in? Would "V05003400002009.AVS" indicate that it's titleset 5 ? ... but then which VOB of titleset 5? The script says "VOB ID 2 CELL ID 9."

So do I need to open VTS_05_2.VOB and demux, looking for cell 9?

-abs

Sir Didymus

27th January 2005, 19:55

@ZuZu:

That's exactely one of my favourite suggestions: if you have troubles with preprocessing, change your approach and do all of the modifications you need after the rebuild.

My second suggestion, especially if you are not sure about what are the right m2v files to keep, is to simply start from scratch. It is simple and straight. Only drawback is the time it needs to reencode the whole.

Third hint, if you have an idea of the amount of cuts you want to apply, is to tune a little bit the Hidden Setting [TargetSectors=nnnn], see the sticky threads, ... for telling DVD-RB to produce an oversized result, in order to compensate for the cuts to be applied later...

Cheers,
SD

Sir Didymus

27th January 2005, 19:58

Originally posted by absinthe
Ok, I'm really getting thrown by these numbers.

How do I know exactly what original VOB my segment is in? Would "V05003400002009.AVS" indicate that it's titleset 5 ? ... but then which VOB of titleset 5? The script says "VOB ID 2 CELL ID 9."

So do I need to open VTS_05_2.VOB and demux, looking for cell 9?

-abs

Hey, absinthe, you may consider to let DVD-RB doing the "dirty job" for you: if you prepare a parallel project in "No Compression" mode, running both the prepare and the encode steps, it will demux for you the whole title, and it is very quick...

jdobbs

27th January 2005, 20:13

V05003400002009.AVS
V05 = Titleset 5
VXX0034 = Segment 34 (unique ID)
VXXXXXX00002 = VOBID 2
VXXXXXXXXXXX009 = CELLID 9

V05003400002009.AVS = Titleset 5, VOB 2, CELL 9

The segment is just to keep it unique and in order. There can be more than one segment for each VOB/CELL pair (still frames, for example).

dannyv

27th January 2005, 20:19

absinthe

27th January 2005, 20:46

Originally posted by jdobbs
V05003400002009.AVS
V05 = Titleset 5
VXX0034 = Segment 34 (unique ID)
VXXXXXX00002 = VOBID 2
VXXXXXXXXXXX009 = CELLID 9

V05003400002009.AVS = Titleset 5, VOB 2, CELL 9

The segment is just to keep it unique and in order. There can be more than one segment for each VOB/CELL pair (still frames, for example).

Thanks jdobbs for the very useful info.

However, after extracting the cell and using it to replace the blank one, I still get error 0004 upon rebuilding. I've erased everything in frustration, and I'm just going to start again with a fresh DVD rip. I'll let it encode overnight, and we'll try to rebuild in the morning.

-abs

dannyv

27th January 2005, 20:53

Originally posted by absinthe
Thanks jdobbs for the very useful info.

However, after extracting the cell and using it to replace the blank one, I still get error 0004 upon rebuilding. I've erased everything in frustration, and I'm just going to start again with a fresh DVD rip. I'll let it encode overnight, and we'll try to rebuild in the morning.

-abs

Did it error on the same m2v file or a different one? Did you play the original m2v to make sure it worked before replacing it? If so was it blank? If it was not blank you may have extracted the wrong original cell. Chances are if you do the whole thing over you may wind up with the same problem. If it did not happen on the same cell that means you have more then 1 blank corrupt cell. I did star trek voyager and had 10 corrupt cells on the last disk containing the extras.

jdobbs

27th January 2005, 21:22

Originally posted by dannyv
Thanks for clearing that up jdobbs.

That would translate to vts_05_2.vob and you would want cell 9. No. The VOBID is not related to the file "vts_05_2.vob" -- it is an internal identification. The VOBID/CELLID exists in every NAVPACK. You might have 30 VOB units in a single .VOB file. For example you might have a file VTS_05_1.VOB that has:

VOBID 1, CELLID 1
VOBID 1, CELLID 2
VOBID 2, CELLID 1
VOBID 2, CELLID 2
VOBID 2, CELLID 3
VOBID 3, CELLID 1

As far as the player is concerned the entire VTS is treated like a single file. Offsets are listed as sector numbers with 0 being the first 2048 byte sector of VTS_XX_1.VOB and the last sector (x) being the final sector of VTS_XX_X.VOB (the last of the set).

absinthe

27th January 2005, 21:29

Oh, yes it was the correct cell. It was 10 seconds of black, which is what it should have been and which is what I would see when playing the AVS script in a media player. I didn't exactly checked to see if rebuilding failed on the exact same file, but it happened at about the same phase in the process so I'm willing to bet the bank it was the same file.

I'm just disgusted with trying and my drive was getting clogged with all these copies of copies of copies of files. Just wanna start fresh. If it happens again, I'm gonna move on to another DVD to see if maybe this problem isn't related to this DVD or if it's going to be a chronic problem.

-abs

absinthe

27th January 2005, 21:48

Originally posted by jdobbs
No. The VOBID is not related to the file "vts_05_2.vob" -- it is an internal identification. The VOBID/CELLID exists in every NAVPACK. You might have 30 VOB units in a single .VOB file. For example you might have a file VTS_05_1.VOB that has:

VOBID 1, CELLID 1
VOBID 1, CELLID 2
VOBID 2, CELLID 1
VOBID 2, CELLID 2
VOBID 2, CELLID 3
VOBID 3, CELLID 1

As far as the player is concerned the entire VTS is treated like a single file. Offsets are listed as sector numbers with 0 being the first 2048 byte sector of VTS_XX_1.VOB and the last sector (x) being the final sector of VTS_XX_X.VOB (the last of the set). Then I remain confused on that point. How can I manually locate the segment cell (with, say, VobEdit for instance) with the information provided by the AVS script generated by Rebuilder? Specifically, how do I know which VOB (as ripped with Decrypter and used for source) to open to look for it?

-abs

jdobbs

27th January 2005, 21:48

There are some newer copy protections that I know can cause this. v0.73 will help.

All: I'm working diligently on v0.73 -- I've received a lot of PMs and e-mails asking when it will be released.... all I can say is "when it's done" The one thing that is always worse than releasing something slow is releasing it bad.

MaxT

27th January 2005, 21:49

Originally posted by jdobbs
The one thing that is always worse than releasing something slow is releasing it bad. Damn right!

absinthe

28th January 2005, 21:34

Okay, here's the skinny ....

I have now encoded this entire movie about 4 times (whew ... !). Basically, it comes down to this: DVD files that I altered with VobBlanker would not rebuild. I even tried the method mentioned earlier in this thread of running the altered files through DVD Shrink with "no video compression" before using DVD-RB. I was excited because it almost made it (93+% in the rebuilding process), but again I got the error 0004.

Notably, it was not on the same segment as before.

DVD files ripped directly from the DVD and not altered in any way, however, would encode and rebuild fine (though I did not preview the resulting files). I do understand, however, that some folks have gotten this error even without altering files in any way.

So I'm disappointed. Not in Rebuilder of course, which is a great program (kudos out to jdobbs), but disappointed that I can't get rid of crappy unwanted material before using my favorite DVD program. Oh, well, I'm gonna just run my altered files through DVD Shrink on this one.

If nothing else, I would at least like to achieve getting the DVD to go straight to the main menu upon insertion. That's a bare minimum for me. I'm tempted to just try to alter the navigation with PgcEdit (i.e., not actually blanking the Vobs) and seeing if that works with Rebuilder. But man am I tired of having my computer tied up with encoding (gotta get a new processor!) ... I've just been doing 1-pass in CCE with analysis for these tests.

So I hope jdobbs can get the bottom of this for 0.73. I think I'll be contributing so I can get the latest version.

Good Luck!

-abs

MaxT

29th January 2005, 02:40

DVD RB 0.66a
CCE 2.67.0.23
VobBlanker 1.6.0.3
MenuEdit 2.3.0
IfoEdit 0.96

works every time...

absinthe

29th January 2005, 04:49

Mmm ... I see you use a newer VobBlanker. Perhaps that would make a difference.

-abs

robot1

29th January 2005, 07:28

My opinion on usage of VobBlanker - DVDRemake - CloneDVD2 ...
If you blank completely a VTS, or if its size becomes not greater than 50 MB, you will not have problem with DVD-RB simply because the VTS isn't processed. (ex.: you delete all the extras, which are in separate VTS from the film)
But a partially blanked VTS, processed by DVD-RB, will lead almost always to problems (ex: extras or logos or preview in the same VTS of the film, or extras partially blanked).
Wait for DVD-RB 0.73, or avoid to preprocess. You can change targetsectors to have an oversized DVD, and postprocess it blanking extras to reduce it to a proper size.
Processing of menus never leads to problems.

NobbyNobbs

29th January 2005, 13:43

I have never had problems with DVDRemake Pro blanking cells in a VTS, but on a few disc's cutting a cell will lead to problems. (not always, just every now and then)

HanSolo00

5th February 2005, 08:43

I've never had a #0004 error with Rebuilder after hundreds(?) of discs until recently working on TROY R1 NTSC. It has single frames in between all chapters, and it fails during rebuilding every time at the same place ('Rebuilding segment 8 VOBID: 9 CELLID: 1'). It's a single frame M2V:

name=C:\TEMP\D2VAVS\V01000800009001.avs
frame_first=0
frame_last=3779
encode_first=0
encode_last=3779

DVDDecrypter 3.5.2.0
DVD RB 0.72
CCE 2.70.01.05 (tried 2.67.00.27 also)
DVDRemake 2.6.4
IFOedit 0.96

I preprocessed the main movie with IFOedit to remove language streams, and fixed the language menu with DVDRemake (minor changes), which is more or less the same procedure I use on many discs.

I'm out of ideas at the moment on how to fix this, but I'm going to try to rip the files again without any IFOedit or Remake processing and see what happens when I compress it. If I have to, I can compute the oversize, then run IFOedit/Remake afterwards to fix the menus or strip streams. Or perhaps I'll just wait until I can try a new version of DVD-RB:)

robot1

5th February 2005, 09:26

Originally posted by HanSolo00
It's a single frame M2V:

What is the size of that .m2v file?

jdobbs

5th February 2005, 13:02

Originally posted by HanSolo00
I've never had a #0004 error with Rebuilder after hundreds(?) of discs until recently working on TROY R1 NTSC. It has single frames in between all chapters, and it fails during rebuilding every time at the same place ('Rebuilding segment 8 VOBID: 9 CELLID: 1'). It's a single frame M2V:

name=C:\TEMP\D2VAVS\V01000800009001.avs
frame_first=0
frame_last=3779
encode_first=0
encode_last=3779

DVDDecrypter 3.5.2.0
DVD RB 0.72
CCE 2.70.01.05 (tried 2.67.00.27 also)
DVDRemake 2.6.4
IFOedit 0.96

I preprocessed the main movie with IFOedit to remove language streams, and fixed the language menu with DVDRemake (minor changes), which is more or less the same procedure I use on many discs.

I'm out of ideas at the moment on how to fix this, but I'm going to try to rip the files again without any IFOedit or Remake processing and see what happens when I compress it. If I have to, I can compute the oversize, then run IFOedit/Remake afterwards to fix the menus or strip streams. Or perhaps I'll just wait until I can try a new version of DVD-RB:) Let me know what happens. I did this disc and had no problems.

I'm also confused. You say it's a single frame M2V, but the ECL files you show says the it goes from 0-3779?

HanSolo00

5th February 2005, 21:14

Sorry, you are correct, I was looking at the wrong part of the ECL.

Anyhow, I tried two things at once:

1) passed the preprocessed files through DVDShrink with no compression
2) compressed the whole thing over using DVD-RB v0.74

Now the project completes just fine with no #0004 error... but there are visible split-second stutters all chapter changes (played back on my PC in PowerDVD), which aren't visible in the files after Shrink but before being compressed.