View Full Version : DVD-RB Error #0004 (merged)
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).
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
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.