Log in

View Full Version : MeGUI encoding error

Reino
1st May 2008, 16:33
Good afternoon,

For personal use I've been using MeGUI (and Belight) to encode dvd material to MKV[H.264+Vorbis]. This has worked perfectly for me up until now.
The message that constantly returns is: "The current job contains errors. Skipping chained jobs". Let me just post the log-file:
Looking for job processor for job...
Processor found!

------------------------------------------------------

Starting job job1-1 at 14:24:44
Starting preprocessing of job...
Preprocessing finished!
encoder commandline:
--pass 1 --bitrate 534 --stats "D:\example.stats" --bframes 3 --b-pyramid --direct auto
--filter 1,1 --subme 1 --analyse none --vbv-maxrate 25000 --me dia --threads auto
--thread-input --progress --no-psnr --no-ssim --output NUL "D:\example.avs"
successfully started encoding
Processing ended at 16:04:15
----------------------

Log for job job1-1

avis [info]: 512x384 @ 25.00 fps (70961 frames)
x264 [info]: using cpu capabilities: MMX MMX2 SSE SSE2 SSE3 Cache64
x264 [warning]: VBV maxrate specified, but no bufsize.

----------------------
The current job contains errors. Skipping chained jobs
End of log for job1-1
-------------------------------------------------------
The actual x264.exe commandline: --pass 2 --bitrate 534 --stats ".stats" --ref 10 --mixed-refs --bframes 3 --b-pyramid
--b-rdo --bime --weightb --direct auto --filter 1,1 --subme 6 --trellis 1 --analyse all
--8x8dct --vbv-maxrate 25000 --me umh --threads auto --thread-input --progress --no-psnr
--no-ssim --output "D:\example.mkv" "D:\example.avs"
Maybe posting the aviscript is also useful: mpeg2source("D:\example.d2v")

TDeint(mode=1)
Mrestore(quality=2,numr=1001,denm=2002)

crop(6,2,-8,-2)
Lanczos4Resize(512,384)

LimitedSharpenFaster()
aWarpSharp(8.0,2,0.5)
Tweak(sat=1.05,cont=1.02)
Deen("a3d",1,3,5)
__film = last
__t0 = __film.trim(0, 70960)
__t0

Now, this hasn't happened for me before, but now everytime the first pass finishes it tells me the jobs contains errors somehow. I absolutely don't know what to do anymore. I've reinstalled MeGUI and AviSynth, updated x264.exe to the newest version and still the error shows up. I also haven't suddenly used different encoder settings. I haven't changed them at all actually!
Any help would greatly be appreciated!
Sharktooth
1st May 2008, 16:55
megui version?
Reino
1st May 2008, 17:09
MeGUI 0.2.5.1007
Sharktooth
2nd May 2008, 02:40
and why on earth are you still using such an old version?
get the latest and greatest one from www.sf.net/projects/megui and make it update all components when you start it.
Reino
2nd May 2008, 21:06
Well, excuse me for being so stupid, but I have my reasons for not using the latest version. I really dislike the bitratecalculator in the latest version, hench I'm using MeGUI 0.2.5.1007, I really need it.

But I was curious enough wanting to know if that could be it...that I had to update to the latest version in order to solve the problem. I was wrong in that believe. The errors still remains. Though it's not posted in the log-file anymore, but only in the Queue Status. This doesn't help at all of course.

Does anyone know if this a common situation with an easy solution, or could this be caused by numerous things?
Sharktooth
5th May 2008, 02:42
try removing all filters from your avs script (obviously, except the source filter) and see if it starts encoding.
Reino
5th May 2008, 21:11
I've unstalled everything again and I'm now using MeGUI 2.5.1007 with the latest versions of data and libs (megui-libs_1045.zip), avswrapper (AvisynthWrapper_0_2_6_1044.zip) and updatecopier (updatecopier_2148.zip), which I backupped from the cache directory. x264 rev.839 does the encoding.
The error is magically gone now (with the AVS-script still intact). I absolutely don't know how. I haven't changed anything towards the gui or the x264 settings. Weird...

I do have another question. I hope you're willing to answer this for me Sharktooth (or anyone else).
MeGUI finally spat out another encode now, but different compared to all the other encodes I made.
The quantizer was now fractured (if that's the right word), or in other words: 24.67, 25.39, 26.84 instead of 24.00, 25.00, 26.00 like I had before. Like I said, I haven't changed any of the encoder settings, so I don't think it might some secret setting, or is it? What's the cause for this to happen?
Dark Shikari
5th May 2008, 21:12
I do have another question. I hope you're willing to answer this for me Sharktooth (or anyone else).
MeGUI finally spat out another encode now, but different compared to all the other encodes I made.
The quantizer was now fractured (if that's the right word), or in other words: 24.67, 25.39, 26.84 instead of 24.00, 25.00, 26.00 like I had before. Like I said, I haven't changed any of the encoder settings, so I don't think it might some secret setting, or is it? What's the cause for this to happen?Adaptive quantization.
Reino
5th May 2008, 21:57
Ah okay, I already thought something like that. So updating x264 caused that to happen.
Thanks you two!
Octo-puss
5th May 2008, 22:17
Well, excuse me for being so stupid, but I have my reasons for not using the latest version. I really dislike the bitratecalculator in the latest version, hench I'm using MeGUI 0.2.5.1007, I really need it.

But I was curious enough wanting to know if that could be it...that I had to update to the latest version in order to solve the problem. I was wrong in that believe. The errors still remains. Though it's not posted in the log-file anymore, but only in the Queue Status. This doesn't help at all of course.

Does anyone know if this a common situation with an easy solution, or could this be caused by numerous things?

I wonder what's so bad about the bitrate calculator? Is it too simple for your tastes?
I wouldn't say you NEED old version of MeGUI... jeez
Reino
6th May 2008, 00:16
Well, the encodes I make need to fit exactly on a 4.37GB dvd. I calculated this all beforehand. I need to know the exact bitrate and amounts of KBs. Eventually I end up with dvds filled with only a couple of hundreds (sometimes even tenths) of KBs to spare.
And since version 2.6 of MeGUI the bitratecalculator shows only MBs, so I can sincerely say that I need the old bitratecalculator.
Sharktooth
6th May 2008, 18:11
you'll find a nice surprise on the next 0.3.x megui version then... ;)
Octo-puss
6th May 2008, 19:21
new version incoming? whoa... tell us more!
Reino
6th May 2008, 19:40
That's very nice to hear Sharktooth, thank you!
Sharktooth
7th May 2008, 01:55
version 0.3.x has a new bitrate calc. it will fit your needs for sure.
EuropeanMan
20th May 2008, 21:50
actually i do have the new 0.3 of megui, and bitrate calc is EXACTLY the same as 2.6 and it SUCKS...this is why i loved 2.5 so much
saint-francis
21st May 2008, 02:16
actually i do have the new 0.3 of megui,

Where did you get it? It's not public yet so surely any version you have is a beta.
Octo-puss
22nd May 2008, 20:09
Where did you get it? It's not public yet so surely any version you have is a beta.

I think he ate some 'shrooms :)
Sharktooth
22nd May 2008, 20:23
http://www.webalice.it/f.corriga/misc/bc.jpg