View Full Version : Rebuilder Errors
howki
6th October 2004, 14:36
Using QEnc, DeCrypter, & Rebuilder .63. When starting Encode, received "AVS File is not outputing (Use ConvertToYV12()at end of script)", also during rebuild, following "Error in Update-Shouldn't Happen - Contact Developer" & "Stop Statement Encountered". This happened with Version 0.61 as well. Have tried encoding, etc. with different settings, & seem to be ending up short of success.
Thanks in advance for any insight.
TheSeeker
6th October 2004, 14:59
Did you make sure that that line (ConvertToYV12()) was in your avs scripts that were made by rebuilder in the prepare phase? Also try opening one of your avs script files with WMP and see if it gives you an error. If it does it should tell on which line the error appears in your avs script. Are you using one click mode or 3 click?
jdobbs
6th October 2004, 15:32
The error you are seeing with QuEnc is probably an AVISYNTH error being output (that isn't in YV12). The second error... well.... it's logical that there may be a problem trying to rebuild from an encode that didn't work.
Daedalus8745
6th October 2004, 22:33
Hmm, after upgrading to 0.63a I too get this error :
In the first run of QuEnc the filename is omitted (QuEnc shows '.avs' as Filename).
IMHO if you do run the first Segment (likely 'V01000000001001.AVS') manually through QuEnc and afterwards continue encoding, then I bet your Rebuild sequence will too function.
Daedalus8745.
howki
7th October 2004, 17:32
Tx for the ideas. ConvertToYV12() appears in all the AVS files. Same results if using single pass or 2 pass encoding, or 1 click or 3 click. If WMP is Windows Media Player, I get an error in downloading codec, so am unable to open avs file. Haven't had a chance yet to try manual code on 1st segment. Could the particular movie (RCE prot.) have anything to do with anything? Additionally, log file shows nothing unusual.
Oldeman
8th October 2004, 05:45
I am sad to say that I am also getting the "Avsfile is not outputing blah blah" error message on ver.63a during first encode.
I have gotten it on three straight movies. Works fine on ver.62.
I have the first two options checked in the avs options setup as well as adding the MPEG2DECDG path thingy to the AVS file option.
Using DVD-RB .63a Quenc.54 with mem-aligned avcodec on P4.
I tried deleting the Rebuilder .ini and reinstalling AVsynth 2.54 to no avail.
; Created by DVD Rebuilder
[item]
title=V01000000001001
aud_out=0
vaf_file=E:\DVD-RB-WORK\D2VAVS\V01000000001001.vaf
aud_file=E:\DVD-RB-WORK\D2VAVS\V01000000001001.mpa
file_focused=0
packet_size=2048
width=720
height=480
frame_rate_idx=1
cbr_brate=6000
vbr_brate_avg=786
vbr_brate_min=0
vbr_brate_max=8552
seq_endcode=1
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=1
alternate_scan=0
intra_dc_prec=2
name=E:\DVD-RB-WORK\D2VAVS\V01000000001001.avs
frame_first=0
frame_last=1
encode_first=0
encode_last=1
howki
8th October 2004, 14:57
Tried the routine again. Manually ran first AVS file through QEnc. Still got ConvertToYV12() message @ resumption of encoding. The rebuilder did finish, but when trying to burn the following appears:
DVD-Video files reallocation started
"File VTS_02_0.VOB is not referenced and should not be present
DVD-Video Files reallocation failed.
Reallocation failed. Resulting DVD-Video might be unplayable. Do you want to continue?"
If I do continue, sometimes I can play back on the computer, but the simple minded home DVD player won't accept it.
TheSeeker
8th October 2004, 15:40
I dont know if you did this already or not but do you have the newest version of avisynth from their homepage? I would look into that and see if that does anything.
Oldeman
8th October 2004, 22:38
I "upgraded" from Avsynth 2.54 to 2.55 and still get the same error. Again it works on v.62.:scared:
howki
8th October 2004, 23:01
Was using AviS 2.5.5, went to 2.6, and from RB .61 to .63. Never tried .62. I think I've got a pretty active "Murphy" & his ravens occupying my computer. This reference business when trying to burn has me a little confused.
nwg
13th October 2004, 16:36
I am using DVD-RV 0.63a for the first time and now getting the same (Use ConvertToYV12()at end of script error with Quenc 0.54.
It has worked fine in the past and whatever I do, I cannot get rid of it.
jdobbs
13th October 2004, 20:49
Have you looked at the output of the .AVS files with MS Media player? If not, do so.
nwg
13th October 2004, 20:57
Originally posted by jdobbs
Have you looked at the output of the .AVS files with MS Media player? If not, do so.
If you are referring to me. The m2v's are encoding fine. The error only came up once before the first encode.
Edit.
The rebuild failed straight away and got a error 3 buffer overflow. Haven't had one of those for ages. This is with 0.63a.
I try to rebuild with a previous version.
Corintio
13th October 2004, 21:36
Same here. Just updated to .63a and started having this very problem. The Quenc window starts encoding a source file named .avs and an output named .m2v and stops with "Convertoyv12()...". If I click on ok, Quenc goes on to the second .avs in the rebuilder.inf file.
Tried reinstalling avisynth, but didn't fix anything. The avs play fine, though, and rebuilder works flawlessly with CCE.
If you need some experimentation, I'm willing to help.
BTW, I've never came around to say it, but thank you jdobbs for this wonderful program :)
nwg
13th October 2004, 21:40
I can't finish the job and rebuild. I get the same error 3 with whatever version of DVD-RB.
I also re-installed avisynth and it didn't change anything.
lamster
14th October 2004, 00:21
Originally posted by Corintio
The Quenc window starts encoding a source file named .avs and an output named .m2v and stops with "Convertoyv12()...". If I click on ok, Quenc goes on to the second .avs in the rebuilder.inf file.
This sounds like what I posted in the v.63 error msg AVS file not outputing? (http://forum.doom9.org/showthread.php?s=&threadid=83369) thread; the work-around I used was to not click OK on the "AVS file not outputing" message. Instead, I started another QuEnc session, set it to all the same parameters as the one with the error dialog (except inserting the missing V02000000001001 for both filenames), let that run, then dismissed the error dialog.
@jdobbs - full details, including good and bad .ecl files, in the referenced thread.
Corintio
14th October 2004, 01:15
Originally posted by lamster
I started another QuEnc session, set it to all the same parameters as the one with the error dialog (except inserting the missing V02000000001001 for both filenames), let that run, then dismissed the error dialog.
Wow, nice & simple. Sounds like a reasonable solution to what looks as a small glitch in the parsing of the .ecl file. I'm trying it right now, and will let the rest of the encode run through the night, hopefully I'll be able to rebuild the project tomorrow.
jdobbs
14th October 2004, 13:23
I'll take a look at the .ECL parsing code. I wonder why it only happens randomly, though... you'd think more people would have experienced it?
howki
14th October 2004, 22:41
I've been getting no M2V file on beginning the encode on segment "0". It produces the .FLG, & then the "--not outputing---YV12--" etc. shows up with "creating M2V file" showing. Click okay, & it continues on to segment "1". When it does finish encoding, it causes an 0003 error on beginning rebuild.
nwg
14th October 2004, 23:44
Originally posted by howki
I've been getting no M2V file on beginning the encode on segment "0".
I didn't notice that.
So, is the non encoding of segment 0 the reason why the error 3 came up?
Fishman0919
15th October 2004, 00:01
I get the same error with QuEnc. I do QuEnc in three click mode, when I get the error on the first one I just click "OK" and let it finish. When it's done encoding all the m2v's files and before the rebuild stage I go back and redo the missed m2v manually (I open the REBUILDER.ECL file in the D2AVS folder and find the bitrate for the missed m2v). After they are done I do the rebuild stage and I get one great looking movie.
howki
15th October 2004, 00:13
I don't know, but suspect that a buffer overflow could occur if, for instance, due to faulty encoding, a boundary or some such was not set. Additionally, I cannot open any of the AVS files in WMP (Ver. 10)--get error saying can't download codec--error 80040200. Microsoft's help on this is gibberish. Oddly enough, it will open the examples in Avisynth's file.
Fishman0919
15th October 2004, 00:49
Every movie with QuEnc I have tried (maybe 12)with DVD-RB .63a has had this problem but every one worked fine after I did the "work around". Haven't try DVD-RB .60b to see if I get the same error but really no need, it's 2 mins manual work to get it to work and I'm sure jdobbs will fix it when he gets a sec ;)
lamster
17th October 2004, 17:43
Originally posted by jdobbs
I'll take a look at the .ECL parsing code. I wonder why it only happens randomly, though... you'd think more people would have experienced it?
I'd think you should be able to reproduce it using the files I posted here (http://forum.doom9.org/showthread.php?s=&postid=555276#post555276) ; if not, please let me know if there's anything else I can provide.
Obviously, the QuEnc error can only be seen using QuEnc - perhaps the same thing is occurring with other encoders, but you don't see the QuEnc "AVS file not outputting" error, so the only symptom is a mysterious "Error 0003" hours later?
nwg
17th October 2004, 18:04
Originally posted by Fishman0919
I get the same error with QuEnc. I do QuEnc in three click mode, when I get the error on the first one I just click "OK" and let it finish. When it's done encoding all the m2v's files and before the rebuild stage I go back and redo the missed m2v manually (I open the REBUILDER.ECL file in the D2AVS folder and find the bitrate for the missed m2v). After they are done I do the rebuild stage and I get one great looking movie.
Thanks for that.
I forgot I could do that and erased the working directory. I redid it,did the segment 0 m2v manually and then rebuild.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.