Error 0003 at the end of Rebuild Phase

[TheMaverick]

Hello!

Im using 0.77 (VIP) version of DVDRB and get the 0003 Buffer Overflow error near at the end of the Rebuild phase (when he is rebuilding VTS03)
It the Metal Dreams DVD (which i think no one knows ;) )

@Jdobbs I can provide you with files if you need sth!

Anything I can do?


Thanks for reading!
Maverick.

___ Edit:
I tried it wih 0.76 also ... same prob.
I'm using: CCE: 2.67.0.27
Avisynth: 2.5.5.0

[Msc_Alex]

Did you try the Special Error Processing ?

[TheMaverick]

Jep. But only with 0.76.

I try it now with 0.77 and report back.

[TheMaverick]

I tried it with 0.77 and Special Error Processing on --> same problem @ the same point.

:(

[Msc_Alex]

I'm not sure but you could try the "whole" process again. Not just the rebuild phase.

[DK]

before doing the whole dvd again, redo the very segment and afterwards try rebuilding

[jptheripper]

any pre processing? other than ripping with decrypter only

[TheMaverick]

@jptheripper
No just ripping with DVD-Decrypter. And then recoding with DVDRB.

How can I just recode the VTS_03 segment? @DK

[DK]

when your rebuilding process stops it will tell which segment it was just processing

if for example rebuilder quits at segment 13, you could open the rebuilder.ecl file, which lists all the segments, that will have to be processed

go to that very segment and copy all information starting with:

[item]
title=.......

until

[file]
...
...
...



it might look like this:

[item]
title=V01000300004001
aud_out=0
vaf_file=x:\D2VAVS\V01000300004001.vaf
aud_file=x:\D2VAVS\V01000300004001.mpa
file_focused=0
packet_size=2048
width=720
height=576
frame_rate_idx=3
cbr_brate=6000
vbr_brate_avg=5336
vbr_brate_min=0
vbr_brate_max=8808
seq_endcode=0
dvd=0
half_width=0
half_height=0
lum_level=0
aspect_ratio=2
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
encode_mode=0
vmode=2
fast_mode=0
quality_prec=24
timecode=0x0000000
vid_file0=x:\D2VAVS\V01000300004001.m2v
vid_file1=x:\D2VAVS\V01000300004001.m2v
vid_out=1
vaf_out=1
opv_q_factor=20
opv_brate_min=0
opv_brate_max=8808
vbr_bias=25
vbr_pass=2
use_filter=0
filter_val=6
non_linear=1
top_first=0
mpeg1=0
mpeg1_cps=1

[file]
name=x:\D2VAVS\V01000300004001.avs
frame_first=0
frame_last=845
encode_first=0
encode_last=845


copy all these lines to a new file (with e.g. notepad) and name that file your_movie.ecl

now load this ecl into your encoder and let it process this very job

finally rename the NEW file to what the *faulty* one was called
e.g.: V01000300004001.m2v

fire up rebuilder again and make sure it is set to 3 click method

now try rebuilding again


good luck

[TheMaverick]

hm, i didn't see any goal of this. @DK
The CCE coded the files without problems.

But i will try it, maybe it helps.


I don't know if this matters but the VTS_03 contains a movie and a slide show (but the slideshow on other dvd's didn't make probs).

[TheMaverick]

Hello again.

I rebuilded the _complete_ DVD with "Special Error Processing" turned on.

The same problem :(


Rebuilding Segment 4 VOBID: 3 Cell: 1

and then Buffer Overflow.

Hm, how can I figure out which file that is?

Edit:
I tested the files of VTS_03 with Dr. M (a lill tool from M2 Edit to test MPEG files) it says:

Claimed video bitrate is 6000000 but the real video bitrate is 7397600 (more than 10% diff)

is that the problem? How can i fix this?

[Msc_Alex]

Have seen posts with error 3 problems when using CCE: 2.67.0.27
You could try a new trail cce version. I have always like 2.5.

[TheMaverick]

I try it ... thanks.

[mpennel]

Try following this thread: http://forum.doom9.org/showthread.php?s=&threadid=89363&highlight=ugly+head

Once you learn to figure out what files are missing (usually .m2v files), you can manually make CCE encode them, and then rebuild. It will work. I've done it several times now.

One easy way to see which .m2v files are missing is to go to Windows Explorer (the file program, not the web browser), and go to your working directory, and make explorer list the files by type. That way, you can easily see which files are missing. Something like this:

0100002001.m2v
0100002002.m2v
0100002003.m2v
0100002004.m2v
0100002006.m2v

Obviously, file 0100002005.m2v is missing from that example. Get it?

[lamster]

Originally posted by mpennel
One easy way to see which .m2v files are missing
Here's an easier way. Save it as Check4M2V.bat somewhere in your path, and run it from a command prompt, passing the name of your D2VAVS directory as the argument.
@echo off
@rem Check4M2V.bat, by lamster
if not "%os%" == "Windows_NT" echo Sorry, requires Windows NT or better.
if not "%os%" == "Windows_NT" goto end

if "%1" == "" echo Missing argument - requires name of D2VAVS directory.
if "%1" == "" goto :EOF

if not exist %1\*.AVS echo Invalid argument - %1\*.AVS not found.
if not exist %1\*.AVS goto :EOF

for %%X in (%1\*.AVS) do if not exist %%~dpnX.m2v echo Missing: %%~dpnX.m2v
for %%X in (%1\*.M2V) do if %%~zX == 0 echo Warning: %%X is 0 bytes long !!!
echo ...Done!
:end
(Edited to add a check for 0-sized M2V files.)

Note that if you're in the D2VAVS directory, you can just run this as:Check4M2V .

[mpennel]

Cool. I'll have to try that! That might be worth a sticky at the top of the page for anyone to find when needed to find what files are missing easily!:)

[TheMaverick]

So, I tried it with CCE Trail 2.70.01.05.
But I have the same prob with CCE 2.69.
There are no files missing and I truned "Spezial Error Processing" on.

Still any Ideas ?

Thanks, Maverick.

[mpennel]

Could you post your rebuilder.log file? That MIGHT shed some light on the subject.

[TheMaverick]

There it is.

Edit: Sorry i have problems attaching it, i will include it here ... sorry for the very long post.

I have removed PHASE II, cuz the msg is to long

[07:44:53] Phase I, PREPARATION started.
- VTS_01: 2.741.279 sectors.
-- Scanning and writing .D2V file
-- Processed 146.900 frames.
-- Building .AVS and .ECL files
- VTS_03: 566.316 sectors.
-- Scanning and writing .D2V file
-- Processed 10.072 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 49,8%
- Overall Bitrate : 3.009Kbs
- Space for Video : 2.306.420KB
- HIGH/LOW/AVERAGE Cell Bitrates: 7.464/410/3.009 Kbs
[07:50:02] Phase I, PREPARATION completed in 6 minutes.
[PHASE II, VTS_01 was removed in the log]
- Creating M2V for VTS_03 segment 0
- Creating M2V for VTS_03 segment 1
- Creating M2V for VTS_03 segment 2
- Creating M2V for VTS_03 segment 3
- Creating M2V for VTS_03 segment 4
- Creating M2V for VTS_03 segment 5
- Creating M2V for VTS_03 segment 6
- Creating M2V for VTS_03 segment 7
- Creating M2V for VTS_03 segment 8
- Creating M2V for VTS_03 segment 9
- Creating M2V for VTS_03 segment 10
- Creating M2V for VTS_03 segment 11
- Creating M2V for VTS_03 segment 12
- Creating M2V for VTS_03 segment 13
- Creating M2V for VTS_03 segment 14
- Creating M2V for VTS_03 segment 15
- Creating M2V for VTS_03 segment 16
- Creating M2V for VTS_03 segment 17
- Creating M2V for VTS_03 segment 18
- Creating M2V for VTS_03 segment 19
- Creating M2V for VTS_03 segment 20
- Creating M2V for VTS_03 segment 21
- Creating M2V for VTS_03 segment 22
- Creating M2V for VTS_03 segment 23
- Creating M2V for VTS_03 segment 24
- Creating M2V for VTS_03 segment 25
- Creating M2V for VTS_03 segment 26
- Creating M2V for VTS_03 segment 27
- Creating M2V for VTS_03 segment 28
- Creating M2V for VTS_03 segment 29
- Creating M2V for VTS_03 segment 30
- Creating M2V for VTS_03 segment 31
- Creating M2V for VTS_03 segment 32
- Creating M2V for VTS_03 segment 33
- Creating M2V for VTS_03 segment 34
- Creating M2V for VTS_03 segment 35
- Creating M2V for VTS_03 segment 36
- Creating M2V for VTS_03 segment 37
- Creating M2V for VTS_03 segment 38
- Creating M2V for VTS_03 segment 39
- Creating M2V for VTS_03 segment 40
- Creating M2V for VTS_03 segment 41
- Creating M2V for VTS_03 segment 42
- Creating M2V for VTS_03 segment 43
- Creating M2V for VTS_03 segment 44
- Creating M2V for VTS_03 segment 45
- Creating M2V for VTS_03 segment 46
- Creating M2V for VTS_03 segment 47
- Creating M2V for VTS_03 segment 48
- Creating M2V for VTS_03 segment 49
- Creating M2V for VTS_03 segment 50
- Creating M2V for VTS_03 segment 51
- Creating M2V for VTS_03 segment 52
- Creating M2V for VTS_03 segment 53
- Creating M2V for VTS_03 segment 54
- Creating M2V for VTS_03 segment 55
- Creating M2V for VTS_03 segment 56
- Creating M2V for VTS_03 segment 57
- Creating M2V for VTS_03 segment 58
- Creating M2V for VTS_03 segment 59
- Creating M2V for VTS_03 segment 60
- Creating M2V for VTS_03 segment 61
- Creating M2V for VTS_03 segment 62
- Creating M2V for VTS_03 segment 63
- Creating M2V for VTS_03 segment 64
- Creating M2V for VTS_03 segment 65
- Creating M2V for VTS_03 segment 66
- Creating M2V for VTS_03 segment 67
- Creating M2V for VTS_03 segment 68
- Creating M2V for VTS_03 segment 69
- Creating M2V for VTS_03 segment 70
- Creating M2V for VTS_03 segment 71
- Creating M2V for VTS_03 segment 72
- Creating M2V for VTS_03 segment 73
- Creating M2V for VTS_03 segment 74
- Creating M2V for VTS_03 segment 75
- Creating M2V for VTS_03 segment 76
- Creating M2V for VTS_03 segment 77
- Creating M2V for VTS_03 segment 78
- Creating M2V for VTS_03 segment 79
- Creating M2V for VTS_03 segment 80
- Creating M2V for VTS_03 segment 81
- Creating M2V for VTS_03 segment 82
- Creating M2V for VTS_03 segment 83
- Creating M2V for VTS_03 segment 84
- Creating M2V for VTS_03 segment 85
- Creating M2V for VTS_03 segment 86
- Creating M2V for VTS_03 segment 87
- Creating M2V for VTS_03 segment 88
- Creating M2V for VTS_03 segment 89
- Creating M2V for VTS_03 segment 90
- Creating M2V for VTS_03 segment 91
- Creating M2V for VTS_03 segment 92
- Creating M2V for VTS_03 segment 93
- Creating M2V for VTS_03 segment 94
- Creating M2V for VTS_03 segment 95
- Creating M2V for VTS_03 segment 96
- Creating M2V for VTS_03 segment 97
- Creating M2V for VTS_03 segment 98
- Creating M2V for VTS_03 segment 99
- Creating M2V for VTS_03 segment 100
- Creating M2V for VTS_03 segment 101
- Creating M2V for VTS_03 segment 102
- Creating M2V for VTS_03 segment 103
- Creating M2V for VTS_03 segment 104
- Creating M2V for VTS_03 segment 105
- Creating M2V for VTS_03 segment 106
- Creating M2V for VTS_03 segment 107
- Creating M2V for VTS_03 segment 108
- Creating M2V for VTS_03 segment 109
- Creating M2V for VTS_03 segment 110
- Creating M2V for VTS_03 segment 111
- Creating M2V for VTS_03 segment 112
- Creating M2V for VTS_03 segment 113
- Creating M2V for VTS_03 segment 114
- Creating M2V for VTS_03 segment 115
- Creating M2V for VTS_03 segment 116
- Creating M2V for VTS_03 segment 117
- Creating M2V for VTS_03 segment 118
- Creating M2V for VTS_03 segment 119
- Creating M2V for VTS_03 segment 120
- Creating M2V for VTS_03 segment 121
- Creating M2V for VTS_03 segment 122
- Creating M2V for VTS_03 segment 123
- Creating M2V for VTS_03 segment 124
- Creating M2V for VTS_03 segment 125
- Creating M2V for VTS_03 segment 126
- Creating M2V for VTS_03 segment 127
- Creating M2V for VTS_03 segment 128
- Creating M2V for VTS_03 segment 129
- Creating M2V for VTS_03 segment 130
- Creating M2V for VTS_03 segment 131
- Creating M2V for VTS_03 segment 132
- Creating M2V for VTS_03 segment 133
- Creating M2V for VTS_03 segment 134
- Creating M2V for VTS_03 segment 135
- Creating M2V for VTS_03 segment 136
- Creating M2V for VTS_03 segment 137
- Creating M2V for VTS_03 segment 138
- Creating M2V for VTS_03 segment 139
- Creating M2V for VTS_03 segment 140
- Creating M2V for VTS_03 segment 141
- Creating M2V for VTS_03 segment 142
- Creating M2V for VTS_03 segment 143
- Creating M2V for VTS_03 segment 144
- Creating M2V for VTS_03 segment 145
- Creating M2V for VTS_03 segment 146
- Creating M2V for VTS_03 segment 147
- Creating M2V for VTS_03 segment 148
- Creating M2V for VTS_03 segment 149
[11:55:52] Phase II ENCODING completed in 245 minutes.
[11:55:53] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
removed cuz the messege is too long.
- Processing VTS_03
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 1 VOBID: 2 CELLID: 1
- Updating NAVPACKS for VOBID_02
- Rebuilding segment 2 VOBID: 3 CELLID: 1
- Rebuilding segment 3 VOBID: 3 CELLID: 1
- Rebuilding segment 4 VOBID: 3 CELLID: 1
- Rebuilding segment 5 VOBID: 3 CELLID: 1
- Rebuilding segment 6 VOBID: 3 CELLID: 1
- Rebuilding segment 7 VOBID: 3 CELLID: 1
- Rebuilding segment 8 VOBID: 3 CELLID: 1
- Rebuilding segment 9 VOBID: 3 CELLID: 1
- Rebuilding segment 10 VOBID: 3 CELLID: 1
- Rebuilding segment 11 VOBID: 3 CELLID: 1
- Updating NAVPACKS for VOBID_03
- Rebuilding segment 12 VOBID: 4 CELLID: 1
- Updating NAVPACKS for VOBID_04
- Rebuilding segment 13 VOBID: 5 CELLID: 1

[jdobbs]

Originally posted by mpennel
Cool. I'll have to try that! That might be worth a sticky at the top of the page for anyone to find when needed to find what files are missing easily!:) I'm going to build that check into the program. I've gotten a few reports of failed rebuilds due to missing M2V files.

Interestingly, I don't think I've ever run into that problem. But I run all my jobs on a dedicated PC so I'm never doing any other tasks concurrently -- my best guess is that when there are M2V files missing it may be accidental keystrokes that trigger the "Cancel" button on CCE that is the root of this. Not sure what I can do about that, other than do the file check before rebuild.

[TheMaverick]

currently there are no files missing, to get this right.
they are all there :)

[Sir Didymus]

Originally posted by jdobbs
I'm going to build that check into the program. I've gotten a few reports of failed rebuilds due to missing M2V files.


That's very nice to hear.

Me too never had this type of problems, but [due to variety of the versions and types of supported encoders] convinced that some type of check of the encoding task may have benefical effects for improving the reliability of DVD-RB.

Sorry for asking, and please take this more as a curiousity than as a request, but do think it could be worthwile to explicitely count (via DGIndex for example) the number of encoded pictures in the produced m2v files ?

Cheers,
SD

[jdobbs]

I already do that. In fact you will find that the length of the .FLG file is exactly the number of frames. The flags in that file is applied against the source when it is read in. BTW, DGIndex is not used in DVD-RB processing -- only DGDECODE.DLL. The type of scan that DGIndex normally does is performed by DVD-RB and it creates the .D2V files.

[Sir Didymus]

:confused:

I am sure I miss some thing...

If the flags are applied against the source when it is read in, this does not provide any check on the work of the encoder...

What I was coriuos about is the possibility of analyse each m2v file, after the encoding phase, in order to ensure that each one of the encoded file have the same number of pictures of the source...

Many months ago I did some nasty tests, cutting intentionally someone of the encoded m2v files, and no error was reported at the beginning of the rebuild phase by the application...

Edit: Mhhh. Maybe I am wrong... I will do again some "simulation" :D of a bad encoding and report...

Cheers,
SD

[DK]

Not sure what I can do about that, other than do the file check before rebuild

rebuilder.ecl lists all parameters, so maybe the missing parts could be redone?

not sure though how much trouble this would be to implement
:rolleyes:

[mpennel]

Jdobbs,

I can tell you without a shadow of a doubt, that the problems I've experienced with missing .m2v files have nothing to do with canceling CCE with keystrokes. I usually run DVD-RB overnight, and no one is around. Also, I've had the same problem with missing .m2v files in exactly the same place on a couple of DVDs. The most recent was the DTS R1 release of The Eagles-Hell Freezes Over (DTS version) DVD. I tried to back that DVD up a before Christmas with DVD-RB, and received the Error 0003 buffer overun error then (and didn't realize .m2v files were missing at that time). See this thread from back then. (http://forum.doom9.org/showthread.php?s=&threadid=85918) Then, last week, I tried it again, with version 0.77, and got the same 0003 error, but this time I understood how/where to look for the missing .m2v files, and rebuilt the 2 missing files manually, and it works just fine. I don't know why it didn't create those missing .m2v files, but I'm glad I understand how to do it now.:)

[TheMaverick]

Hm, is there sth with that i can help figure out the problem?
maybe testing an extended debug version ? anything?
Send jdobbs some files (oh im sure it helps sending my dvd to his email adress ;-) ).

[schumi77]

Originally posted by mpennel
Then, last week, I tried it again, with version 0.77, and got the same 0003 error, but this time I understood how/where to look for the missing .m2v files, and rebuilt the 2 missing files manually, and it works just fine. I don't know why it didn't create those missing .m2v files, but I'm glad I understand how to do it now.:)
Hi all,

How do you rebuild it manually ?

[DK]

Originally posted by schumi77
Hi all,

How do you rebuild it manually ?

see my second posting in this thread

[Sir Didymus]

Carried out the following tests:

1. Set up and run Rebuilder (v0.77 Beta) on a title [it is Donnie Darko, PAL, R2]; 2 title sets, 17 Segments in total.

2. The rebuild process completed normally [as usual :) ], and the title playback was ok. in all of its aspects; just checked on a sw player; no need to verify on a standalone...

3. First test. Completely removed from the D2V folder the m2v file relative to the second segment. Rebuilded the title. In this condition (simulating a "wrong" behaviour of the encoder, not outputting a given m2v file), the behaviour of DVD-RB is timely and proper: the application stopped at the start of the rebuilding of the third segment, with the #0003 error.

4. Second test. Substituted from the D2V folder the m2v file relative to the second segment with a 0 byte file, having the same name [ V01000100001002.m2v ] expected by DVD-RB. In this condition (simulating a "wrong" encoding job, just outputting a 0 lenght m2v file), the behaviour of DVD-RB has been improper: the anomalous condition was simply not detected, and the application successfully completed its task. Obviously the playback of the title was crappy: picture froozen to the last valid image, but audio played back in a regular way.

5. Third test. Substituted from the D2V folder the m2v file relative to the second segment with a regular m2v file, containing just 200 frames, and the same name as expected by DVD-RB. In this condition (simulating a "wrong" encoding job, prematurely terminated), the behaviour of DVD-RB is similar to the one of the previous test: again the anomalous condition was not detected, and the application successfully completed its task. Video playback of the cell stopped at the last valid image, with the audio continuing its regular play.

@Jdobbs. Suggestion [please take this a "loud voice" consideration]: do you think is it possible [or useful], during the rebuild stage, when opening a new m2v file, to check if the cumulative number of pictures inserted up to this time in the authored VOBs is matching with the sum of the frames in source pictures, as this information is already available, as you stated in a previous post, in the flg files ?

All the best,
SD

[jdobbs]

@Jdobbs. Suggestion [please take this a "loud voice" consideration]: do you think is it possible [or useful], during the rebuild stage, when opening a new m2v file, to check if the cumulative number of pictures inserted up to this time in the authored VOBs is matching with the sum of the frames in source pictures, as this information is already available, as you stated in a previous post, in the flg files ? I'm working on it now. Finding a frame count mismatch is easy... deciding what to do about it when it happens -- that's another story.

[TheMaverick]

Just for information, i tried the same DVD with the newest version of DVD - Rebuilder (PRO) -> same problem.

[Sir Didymus]

Originally posted by jdobbs
I'm working on it now. Finding a frame count mismatch is easy... deciding what to do about it when it happens -- that's another story.

I share all of your doubts: in any application the error handling may be performed at many different levels at it may be absolutely complex.

My personal opinion is that if DVD-RB is capable of timely detecting this type of errors, with a proper message to the user about the anomalous condition, this is much more than enough...

Trying to reecode automatically a segment (for how many times ?) may lead to heavy headaches for the programmer (you...), "spaghetti" fashioned coding (trying to catch the intricacies of a given anomalous condition), without the guarantee of completely solving all of the singularities generated by the wrong behaviour of a thirdy party application (the encoder...)...

Fortunately this decision is not on my shoulders :) ... it's on yours ... :scared:

[jdobbs]

I gotta do what I gotta do. ;)

[TheMaverick]

Tried it (complete Rebuilding) with 0.81 Pro, still the same prob :(