PDA

View Full Version : eek!! MeGUI is slowly driving me Insane :(


SnapCount
24th December 2006, 01:15
MeGUI is slowly driving me MAD!!:eek:

I got no problems with the encoding side of things, and it does take around 30-45min longer to encode a Xvid file than it did with Gordian Knot (not AutoGK). But my main problem atm is that while im converting stuff from digital TV (mpeg2) then deciding on the size of the file its going to be (399-400mb for a 41min tv episode). MeGUI sometimes decides to change the file size of the video and makes it smaller!! For a 41min show the vid is usually 365mb and the audio is 34mb to make it a total of 399mb. But lately its been converting the video to 334mb!! And ive done it 3 to 4 times converting the video and its always 334mb and not 365mb.

Can anyone help me?

berrinam
24th December 2006, 02:04
Well, you can stick with an old version.

Or you could update to a 0.2.4.1018, which should have fixed the bitrate calculation, and then you can post your log for that.

SnapCount
24th December 2006, 02:32
Cool, didn't know there was an updated version.

But the only updated version i can find is ver 0.2.3.2193 and the server for the AutoUpdate is down.:(

berrinam
24th December 2006, 02:52
What version are you running right now?

SnapCount
24th December 2006, 03:35
0.2.3.2192

spanky123
24th December 2006, 06:08
Or you could update to a 0.2.4.1018, which should have fixed the bitrate calculation, and then you can post your log for that.

Yes. I was having this problem also with the bitrate sticking to 1000kbps (from the profile).

This was fixed in the 0.2.4.1017 update.

:)

It's a good idea to keep up to date with MeGUI (especially with 'x264' and 'core' and any filters you use). The AutoUpdate feature in MeGUI makes this much easier

SnapCount
30th December 2006, 02:15
eek, I finally got the latest "core" via the autoupdate, and finally got something to encode.
I was hoping that my problems would be fixed.... but alas it was not.

The video file size still is way too small, and still not the 365-8mb video file it should be making with a 32mb audio mp3 file :(

Here is the log file... hope you can find out what's going on :) This is with the new core 0.2.4.1023.

Looking for job processor for job...
Processor found!
Starting job job3 at 10:08:08 AM
Starting preprocessing of job...
Preprocessing finished!
encoder commandline:
-AIF=[C:\Mpg to DviX\vmars.mpg] -OF=[C:\Mpg to DviX\encoding\vmars] -exit -minimize -OM=2
successfully started encoding
Processing ended at 10:08:48 AM
----------------------------------------------------------------------------------------------------------

Log for job job3


----------------------------------------------------------------------------------------------------------
Starting postprocessing of job...
Job completed successfully and deletion of intermediate files is activated
Postprocessing finished!
Looking for job processor for job...
Processor found!
Starting job job1 at 10:09:15 AM
Starting preprocessing of job...
Preprocessing finished!
encoder commandline:

successfully started encoding
Processing ended at 10:15:43 AM
----------------------------------------------------------------------------------------------------------

Log for job job1

Channels=2, BitsPerSample=16, SampleRate=48000Hz
C:\Program Files\megui\tools\lame\lame.exe --abr 128 -h --silent - "C:\Mpg to DviX\encoding\vmars T01 DELAY 0ms.mp3"
----------------------------------------------------------------------------------------------------------
Starting postprocessing of job...
Job completed successfully and deletion of intermediate files is activated
Postprocessing finished!
Looking for job processor for job...
Processor found!
Starting job job2-1 at 10:21:02 AM
Starting preprocessing of job...
Preprocessing finished!
encoder commandline:
-i "C:\Mpg to DviX\encoding\vmars.avs" -pass1 "C:\Mpg to DviX\encoding\vmars.stats" -bitrate 1258 -kboost 100 -overhead 0 -turbo -max_key_interval 250 -nopacked -vhqmode 2 -qpel -closed_gop -max_bframes 2 -bvhq -threads 1
successfully started encoding
Processing ended at 10:53:59 AM
----------------------------------------------------------------------------------------------------------

Log for job job2-1

xvid_encraw - raw mpeg4 bitstream encoder written by Christoph Lampert 2002-2003

Trying to retrieve width and height from input header
Input colorspace is YV12
xvidcore build version: xvid-1.2.0-dev
Bitstream version: 1.2.-127
Detected CPU flags: ASM MMX MMXEXT SSE 3DNOW 3DNOWEXT TSC
Detected 1 cpus, using 1 threads.

Tot: enctime(ms) =727840.00, length(bytes) = 378039964
Avg: enctime(ms) = 11.96, fps = 83.62, length(bytes) = 6211
I frames: 668 frames, size = 27626/18454168, quants = 2 / 2.00 / 2
P frames: 20913 frames, size = 13033/272573957, quants = 2 / 2.00 / 2
B frames: 39274 frames, size = 2215/87011823, quants = 4 / 4.00 / 4
N frames: 2 frames, size = 8/ 16

----------------------------------------------------------------------------------------------------------
Starting postprocessing of job...
Job completed successfully and deletion of intermediate files is activated
Postprocessing finished!
Looking for job processor for job...
Processor found!
Starting job job2-2 at 10:53:59 AM
Starting preprocessing of job...
Preprocessing finished!
encoder commandline:
-i "C:\Mpg to DviX\encoding\vmars.avs" -pass2 "C:\Mpg to DviX\encoding\vmars.stats" -bitrate 1258 -kboost 100 -overhead 0 -max_key_interval 250 -nopacked -vhqmode 2 -qpel -closed_gop -max_bframes 2 -bvhq -threads 1 -avi "C:\Mpg to DviX\encoding\vmars.avi"
successfully started encoding
Processing ended at 12:05:55 PM
----------------------------------------------------------------------------------------------------------

Log for job job2-2

xvid_encraw - raw mpeg4 bitstream encoder written by Christoph Lampert 2002-2003

Trying to retrieve width and height from input header
Input colorspace is YV12
xvidcore build version: xvid-1.2.0-dev
Bitstream version: 1.2.-127
Detected CPU flags: ASM MMX MMXEXT SSE 3DNOW 3DNOWEXT TSC
Detected 1 cpus, using 1 threads.

Tot: enctime(ms) =3090748.00, length(bytes) = 342187583
Avg: enctime(ms) = 50.79, fps = 19.69, length(bytes) = 5622
I frames: 668 frames, size = 27273/18218608, quants = 2 / 2.00 / 2
P frames: 20913 frames, size = 11474/239958488, quants = 2 / 2.00 / 2
B frames: 39260 frames, size = 2139/84010359, quants = 4 / 4.00 / 4
N frames: 16 frames, size = 8/ 128
desired video bitrate of this job: 1258 kbit/s - obtained video bitrate (approximate): 1129 kbit/s
----------------------------------------------------------------------------------------------------------
Starting postprocessing of job...
Job completed successfully and deletion of intermediate files is activated
Found intermediate output file 'C:\Mpg to DviX\encoding\vmars.stats', deleting...
Deletion succeeded.Postprocessing finished!

ChronoCross
30th December 2006, 02:23
it's already hitting the max. if you want a higher bitrate/size you need to use a custom matrix/restricted quants. This is a problem even for xvid vfw and is covered in a sticky in the xvid forum.

desired video bitrate of this job: 1258 kbit/s - obtained video bitrate (approximate): 1129 kbit/s

not a megui issue cause it's passing the correct params. this is an xvid issue.

SnapCount
30th December 2006, 02:31
This is what I selected in the Bitrate Calculator:
http://img175.imageshack.us/img175/3457/calox4.jpg

As you can see it shows that it video file size should be 365mb, and the audio file size is really closer to 32mb than 31mb (31.9mb).

But after the rendering is done with the video, the video file is 327mb!!:eek: :eek:

SnapCount
30th December 2006, 02:36
This is the config:

http://img95.imageshack.us/img95/4663/configke3.jpg

ChronoCross
30th December 2006, 02:37
This is what I selected in the Bitrate Calculator:
http://img175.imageshack.us/img175/3457/calox4.jpg

As you can see it shows that it video file size should be 365mb, and the audio file size is really closer to 32mb than 31mb (31.9mb).

But after the rendering is done with the video, the video file is 327mb!!:eek: :eek:

Tot: enctime(ms) =3090748.00, length(bytes) = 342187583
Avg: enctime(ms) = 50.79, fps = 19.69, length(bytes) = 5622
I frames: 668 frames, size = 27273/18218608, quants = 2 / 2.00 / 2
P frames: 20913 frames, size = 11474/239958488, quants = 2 / 2.00 / 2
B frames: 39260 frames, size = 2139/84010359, quants = 4 / 4.00 / 4
N frames: 16 frames, size = 8/ 128
desired video bitrate of this job: 1258 kbit/s - obtained video bitrate (approximate): 1129 kbit/s
----------------------------------------------------------------------------------------------------------

xvid is the issue!!!!!!1258 is what megui is passing to xvid. 1129 is what xvid outputs.

You need to go here!!!: http://forum.doom9.org/showthread.php?t=92046

SnapCount
30th December 2006, 02:37
it's already hitting the max. if you want a higher bitrate/size you need to use a custom matrix/restricted quants. This is a problem even for xvid vfw and is covered in a sticky in the xvid forum.

desired video bitrate of this job: 1258 kbit/s - obtained video bitrate (approximate): 1129 kbit/s

not a megui issue cause it's passing the correct params. this is an xvid issue.

I'll have a look into this...

But I never had this problem with Gordian Knot.

Sharktooth
30th December 2006, 04:59
you saturated the codec. so you cant just obtain a higher bitrate than 1129kbps.
Lower the min quantizers (advanced tab in codec config) and try again.
if it's not enough use a high bitrate matrix.

SnapCount
30th December 2006, 05:10
:thanks:

I had a look at the Min Quantizations, and all were at 2. So i changed it to 1, did the same file to render and the file size is what it should be!! Very happy now!!

Now if only I could get the MeGUI mux to work instead of opening up AVIMux_GUI, I would be set!

Thanks guys for ya help!! :) Have a happy New Year's!!

Sharktooth
30th December 2006, 05:24
well, divxmux is the cause... we cant do much about that.
once i proposed to use ffmpeg as muxer, but that would require to rewrite some code...

check
30th December 2006, 05:40
just so you are aware, can you see a difference between the undersized video and the new one? There will be little visual difference.

spanky123
30th December 2006, 10:41
just so you are aware, can you see a difference between the undersized video and the new one? There will be little visual difference.

Yes.

This used to happen to me before when I chose rediculously high bitrates for videos at too smaller resolution.

The output was almost exactly the same as if I chose a decent bitrate/resolution (say a bits/pixel*frame of around .200 as opposed to .250+).

If you run a comp.test, then anything above say 40% and a b/p*f of around .200 should produce pretty good results - unless it's sports or somethin with a lot of action. Then you'll need to use a higher bitrate or smaller resolution etc.