MeGUI .196 very strange things happened, Mr. doom9 comein plz

[MeteorRain]

have a look at pic.1
1. the time of the 1st & 2nd pass of job6 & job5 seems to be so strange...
what i did is:
1. ran the job5, and job6+ were in queue
2. the job5 returned coz the weight/height didn't 16-mod'd, and then job6-1 started
3. i fixed my avs so it should work. i moved job5 down after job6-1 so job5 should have had been processed secondly
4. i went to sleep:p
5. i woke up and found the strange things :o
2. what's the difference between the procesing and processing :eek: :eek:
and pic.2
i bet you can understand what's on the picture as you can read chinese/japanese but just in case and for other members so i mark the english text. what i want to ask is:
x264 and mencoder(if you choose it to process) are both over-handled when processed in meGUI. so is the overhandle cozed by the encoder or the GUI?

best regards
MeteorRain

=============================
well, my windows xp has just show his blue face when encoding process at about 95%... f:o:oks bill gates...

[Doom9]

Could you please reproduce the problem with as little as possible jobs in the queue.. you have many jobs.. it would be excessively difficult to reproduce your scenario (you'd have to tell me how you created each one of them). A scenario with 2 jobs would be most useful. Thanks

[MeteorRain]

well
first add a small clip and set automatic 2pass, queue it.(say job1-1,1-2)
add a movie job(well, clip is also ok), CQmode, and avs should have a mistake so that it won't work. (my avs has a non-16-moded error so it just didn't work)(say job2)
close the meGUI, so it will produce job files to your HD
go into the jobs folder, make a copy of the job1-1&2(say jobc-1,c-2), open them using notepad, change the 'name' attribute and then save
run meGUI, and close it.
you should see another 2 job files produced. (say jobn-1,n-2)
delete the jobc-1,c-2 job file.
run meGUI, and postporn job1-1,1-2, put jobn-1&2 after the job2
then start encode.
now the job2 should have finished with returned value non-zero.
and jobn-1 should be encoding now.
open the job2-avs and correct the mistake, confirm that it will work ok.
move job2 down after jobn-1 but before jobn-2
and wait until jobn-1 finished and see what happened then
i cannot garantee that it will cause the situation like i met this morning i can only say this *may* cause it.

regards ^ ^
MeteorRain

[Doom9]

can you please verify that this scenario does indeed cause the error.. I don't want to go on a wild goose chase.. I believe that there may be problem but I need a proven to be working scenario before I can start solving it.

[MeteorRain]

well, i now have an easier way to show the problem.
add an automatic 2pass job and a 1pass(say, CQ) job into queue
put the 1passjob between the 1st and 2nd of the first job
run and see what happens
(even if they all failed when encoding, the problem will still happen)

and another way to catch the problem:
search your source code for the word "procesing" and i'm sure you will find the currect bug-place

[Doom9]

well, i now have an easier way to show the problem.
add an automatic 2pass job and a 1pass(say, CQ) job into queue
put the 1passjob between the 1st and 2nd of the first jobThat is all without closing the GUI, right? So in the end in the queue you have the following:

job1-1
job3
job1-2
job2

Is that correct? And what is the order of processing then? I suppose job1-1 is encoded, then job1-2, then job2 and job 3 remains in processing state but is not encoded. Is that correct?

[MeteorRain]

well i just add a 1pass job into queue so it's just like:

job1-1
job2
job1-2

and the rest, you says maybe right - i say maybe becoz you have 4 jobs but i have only tested the 3job situation
it's like
job1-1 -> job1-2 -> job2
but the state is
job1-1 done
job2 procesing <-- -_-!!!
job1-2 done


if job3 exists, maybe job3 will be in processing state, i guess...

[Doom9]

job1-1
job2
job1-2Alright.. thanks for working that out. With that info I should be able to reproduce and fix this issue tonight.

[Doom9]

Ok, identified and fixed :) It'll still encode job1-1, job1-2 and only then job2.. jobs that belong together will always be encoded together.