View Full Version : problem in beta 4
SiXXGuNNZ
20th April 2003, 05:01
error code -2 when encoding credits
replaced the gknot.exe with the beta3 .exe and the problem went away :)
len0x
20th April 2003, 09:52
Originally posted by SiXXGuNNZ
error code -2 when encoding credits
replaced the gknot.exe with the beta3 .exe and the problem went away :)
can you try deleting *.settings in GK folder and try beta 4 again ?
SiXXGuNNZ
20th April 2003, 11:51
Originally posted by len0x
can you try deleting *.settings in GK folder and try beta 4 again ?
sure tommorrow when I wake up, I will try that out, gotta let this encode finsih while I sleep first, but I can try that out for ya :)
SiXXGuNNZ
20th April 2003, 22:13
works fine now after removing the settings
N_F
21st April 2003, 00:25
I had the same error about an hour ago. I played around with the codec settings and managed to fix it.
I can't be sure, but it seemed it had something to do with it trying to write an mv and log-file for the credits encoding or something like that.
SiXXGuNNZ
21st April 2003, 08:21
okay I recreated the problem
in beta 4 and 5
if I set the credits at q28(10%) it gives me that error, works in beta 3 fine. I set this by clicking the button for credits in the encode tab, then after I set that to 28 I change the value in the check box to 28 also.
works fine if I set it to q25(21%) also
len0x
21st April 2003, 10:27
Originally posted by SiXXGuNNZ
okay I recreated the problem
in beta 4 and 5
if I set the credits at q28(10%) it gives me that error, works in beta 3 fine. I set this by clicking the button for credits in the encode tab, then after I set that to 28 I change the value in the check box to 28 also.
works fine if I set it to q25(21%) also
are you sure that just by replacing exe file of GK the problem goes away ? Which codec are you using ? 5.0.4 ? I have all sort of problems when doing credits with it (crashes etc.) Never happens for me with 5.0.2. Can you try that as well ?
SiXXGuNNZ
21st April 2003, 20:32
the problem only happens when I set it to quant28(10%), with divx 503 and divx 504
and it happens in beta 4 and 5
beta 3 seemed to be able to let me choose q28
right now I am using 503 and beta 5 and decided on q25(21%)
I went back to 503 after I noticed the mv bug in 504
len0x
21st April 2003, 20:43
When does error occur ? (beginning, end of encode)
p.s. who needs mv files anyway (they're only for speed, not quality)
SiXXGuNNZ
21st April 2003, 21:20
Originally posted by len0x
When does error occur ? (beginning, end of encode)
p.s. who needs mv files anyway (they're only for speed, not quality)
it happens when you start the credits encode in the batch mode
after the error happens the rest of the encoding goes on normally.
about mv, true, yet I don't notice bad rips when using mv in 5.03, the job just gets done faster.
len0x
22nd April 2003, 10:35
can you make a screenshot of that error ?
(I have hard time picturing that error...)
N_F
22nd April 2003, 11:46
I've been playing around with it a bit more and I'm quite certain it's not the quant used. I think it has something to do with if you press the credit configuration button (where the DivX 5 config comes up) before starting the work or something like this (it'd be a lot easier if you could "read" the .settings files, but I don't read hexadecimal :)).
I also encountered something else I've never seen before. Sometimes I get the -2 error, sometimes it works as it's supposed to. But sometimes I get a very small file (58 kb instead of ~600 kb) that shows the proper length, but doesn't contain any data. Sort of like the .avs file you get from the first pass when doing multi/2-passes.
I'd suspect they are somehow related to eachother. I'll see if I can pin down the problem.
(DivX 5.03 and GK 0.28 beta 4 used)
len0x
22nd April 2003, 12:01
can everybody having it try this:
1) set default credits settings on options tab
2) just set different quantizer on encoder page _without_ clicking on credits settings
see if you still have -2 error...
SiXXGuNNZ
24th April 2003, 02:02
without clicking the credits button on encode tab it works fine
but how do we know we are using the quant we set it to?
I will run some quick tests at diff quants and let you know how they turn out
also, here is the error code
http://home.attbi.com/~sixxy01/credits.jpg
edit: I am currently running beta 6 and divx 5.03 pro
SiXXGuNNZ
24th April 2003, 02:17
okay, it works with the quant you enter as long as you do not push the credits button.
one suggestion, the box where we type in the quant is only 2 digits, could you make it xx.x so we could type let's say, 25.2 which is 20%
len0x
24th April 2003, 10:16
Originally posted by SiXXGuNNZ
edit: I am currently running beta 6 and divx 5.03 pro
any chance you can reproduce it with 5.0.4 as well?
(just to make sure...)
len0x
24th April 2003, 10:32
sorry - wrong thread :)
N_F
24th April 2003, 11:41
I spent some time last night trying to find the exact problem. I wasn't entirely succesful but a good bit on the way. (Note that I used beta 5 as I didn't have beta 6 on that particular computer at the time and only tested with DivX 5.03)
The problem is definitely something with the credits button.
First of all, when I change the "Encode Credits at average quant" value and then press the credits button, the DivX 5 config is not always updated to the right quant (it may display an old value). If it shows the right value, then the "-2 problem" seems to happen every time if the credits button was the last thing I clicked on in the GK window. If I start clicking on other stuff in between the situation becomes much more random and it's hard to tell when the problem will occur. If the DivX 5 config is not updated, everything seems to work fine every time.
The above I'm certain of; I can always tell before starting the job if the error will occur by checking if the DivX 5 config is updated.
You (len0x) mentioned something about that it may be fixed in beta 6, as I said I haven't been able to try it yet, but I will as soon as possible (which will be friday morning). Though perhaps you can duplicate the problem based on my discription above and see for yourself.
If it isn't fixed in beta 6 then I guess the thing to examine is why or why not the credits DivX config is updated.
len0x
24th April 2003, 11:53
10x a lot - I finally got it as well (with beta 6 + 5.0.4)
*Edit*
Moreover I know why the error occurs - it's because pass is incorrect.
I think I'm not restoring _credits.settings properly...
N_F
24th April 2003, 12:00
Originally posted by len0x
10x a lot - I finally got it as well (with beta 6 + 5.0.4)
Good (or bad depending on how you look at it :)) to hear. No need for me testing it with beta 6 in that case.
len0x
24th April 2003, 12:09
I didn't restore credits.settings...
Sorry about that ;)
SiXXGuNNZ
24th April 2003, 20:17
what about this?
Originally posted by SiXXGuNNZ
one suggestion, the box where we type in the quant is only 2 digits, could you make it xx.x so we could type let's say, 25.2 which is 20%
len0x
25th April 2003, 12:12
about decimal - sorry, not at the moment (that editbox is tuned for integers...)
SiXXGuNNZ
25th April 2003, 19:54
Originally posted by len0x
about decimal - sorry, not at the moment (that editbox is tuned for integers...)
okay, fair enuff :D
personally I am just glad someone has grabbed the ball and ran with it, keep up the good work :)
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.