DVD-RB Error #0004 (merged)

[ZuZu]

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]

@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]

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]

@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]

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]

@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]

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]

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]

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 for clearing that up jdobbs.

That would translate to vts_05_2.vob and you would want cell 9.

[absinthe]

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]

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]

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]

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]

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]

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]

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

[absinthe]

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]

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]

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

-abs

[robot1]

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]

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]

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]

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

What is the size of that .m2v file?

[jdobbs]

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]

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.

[HanSolo00]

Originally posted by robot1
What is the size of that .m2v file?

All the single frame M2V's come out the same, 30.5kb. Perhaps they are the problem and need replacing/fixing. I've seen this discussed somewhere here, I'll go read up on that.

Since this is no longer an error #0004 issue, but a stutter problem, I've moved on to this stutter thread. (http://forum.doom9.org/showthread.php?s=&threadid=88984)