I don't know exactly, I am focus in developing the GUI so everyone can discover.
No filter resizes and add black borders if needed. MakeAVIs profile does not resize/add black borders, just feed the fake AVI to mencoder assuming that you already done that in your avs.
Use the default value.

Thank you again!

__________________
AudioSlave

1 - Since mencoder and ffvfw both uses libavcodec what differences are you specting find out?
2 - Does mencoder.exe perform same work that ffvfw.dll?
3 - Could ffvfw GUI (control panel) to be used for mencoder.exe (some like rename mencoder.exe to ffvfw.dll)?

Speed! As Mencoder.exe is accesset direct from dos console.
Both do base on libavcodec so the engine "would" be by this the same As I know structures of exes and dlls are different and cant just be renamed ... to my understanding exes = executables .. dlls = libraries?

Well, for that I said "some like...". Programmers maybe will know that? Any way possibility?

@vmesquita,

More trouble with MencoderME v0.21 GUI. It now hangs up my system using 1 pass or
2 pass. I decided to take my settings from MencoderME GUI and create them in
a batch file. Everything ran without any problems. There were some strange results
thought. I used dvd2avi (.d2v), avisynth v2.54 motion adapative script (.avs),
MakeAVIS or FakeAVIS (.avi) as input to batch Mencoder. Then I used 1cd KVCD
target and MakeAVIS filter. I used CalcuMatic to get the bitrate for a 92minute
movie for 1 80min CDR with 64 kb audio. The bitrate was 1122. So far no problems.
I changed vrc_buf_size=327, vrc_maxbitrate=2500, and vbitrate=1122. My
predicted video file size should be 754MB and audio 42MB. I started the batch file
and 1 hour 30 minutes later the mpeg-1 file is done. There were some strange results.

1.. During the batch run the following message repeated over 40+ times
[mpeg1video@ 0x908410] rc buffer underflow 0mb A-V: 0.000 [0:0]
[mpeg1video@ 0x908410] warning, clipping 1 dct coefficients to –255..255
[mpeg1video@ 0x908410] warning, clipping 1 dct coefficients to –255..255

2.. The actual video file size of 448MB was way off from predicted size of 745MB.
Is there any way to get this accurate??

Comments:

The picture quality was very good this time and the entire movie was there with
a file size of 448MB. This batch test was 1 pass. I’d like to try 2 pass and
compare quality and file size. I see advantages with batch as being easier to
intergrate with a automated process. If there were a batch program with
commandlines for MakeAVIS this would be very easy.

-BP

Same here
I got similar errors displayed. But I didn't use a batch file. I used a single command line, for test purposes.

-kwag

For some reason, this messages make the GUI hang, no idea why. Well, at least we know this. I'll try to find a stream that generated this kind of message when being encoded to MPEG1. Actually I didn't do any MPEG1 tests till now.

EDIT:
@BP
The undersize problem should have to do with that "can't quantisize less than this" problem. Maybe we should use a slower scplx_mask with mpeg1. This needs to be tested. So far most optimization was done with MPEG2.

EDIT2:
I think I found the MPEG1 problem. The messages to the error output stream (stderr in C++) were not being redirected. I already added this for the next version and now the GUI is showing "[mpeg1video @ 0x940380]warning, cliping 1 dct coefficents to -255..255" and continuing. I hope this fix works for everyone.

@Kwag,

BTW, in calculating Bitrate, I checked Moviestacker, CalcuMatic,
MPEG-1 bitrate calculator, MEncoderME GUI and
the DVD movie jewel case.

CalcuMatic was the most accurate:

DVD Movie: The Transporter
Movie Time: 92 minutes 8 seconds

CalcuMatic: Time: 92 min 8 sec
Moviestacker: Time: 90 min 20 sec
MEncoderME GUI: Time 90 min
MPEG-1 bitrate calculator: Time: 90 min 22 sec

Note:
In some of these programs a .d2v file is being read to get the time
and this may be why bitrate varied from 1073 to 1158. If file size
prediction relies on an accurate bitrate, CalcuMatic is a winner

-BP

@vmesquita,

Why not let the batch process display these messages instead of
capturing this display to a window. I wanted to add some suggestions
and wish options to MEncoderME v0.2x next release

1) Select output file name

2) Extend audio bitrate range to include 64, 80, 96, ....etc

3) PC Shutdown check box
This would add a shutdown program at the end of the batch file

4) Movie Time is not showing correctly where is it derived??

5) target 1cd KVCD should be changed for vrc_buf_size=327

BTW, what does Overhead represent (i.e. multiplex size)

EDIT- If it's possible could a batch file be created and saved for execution
so I can retry the run in batch. This is handy for debugging. Otherwise
I have to re-enter everyhing in MEncoderME to try again


Thanks

-BP

-kwag

Another suggestion:

A button to clear log .

Because it's too ugly and newbie unfriendly. Come on, it took me months to understand how this can be done. Now you want to take it way and make it uglier? No way!
Good idea.
Less than 112 kbps for audio... I don't know, it can confuse people. This bitrate can only be used for mono.
OK, good idea.
It's shown correctly when reading AVIs. For MPEGs/VOBs, Iwould have to scan the whole file to calculate movie time. Maybe in the future.
Ok.
Yes, represents the extra size that appears when you join audio and video.
Done.

I'll release a new version today, with the MPEG1 problem fixed.

Nice idea, too.

Hi everyone,

0.22 is out! What's new:
- preview filters/crop options/resize using MPlayer throught a nice preview button
- Crop added. Now overscan is possible.
- Deinterlace via KernelDeint added
- Clear Log button
- MPEG1 crashing should be solved.
- command-line is saved as "encode.bat"

Get it here:
http://www.jltoca.uaivip.com.br/files/MencodeME022.zip
You also need to put a mencoder and mplayer (for preview) binary in the same folder. You can use this one:
http://www.jltoca.uaivip.com.br/file...40423-0019.zip

Você é uma máquina de programação do car****!!!!
(Translation: You are a fuc....(friendly sense) programing machine!!!!)


Note: Edited by Mod. due to used terms in Portuguese

Hi Prodater,
I'm sorry but I had to edit your post.
Not that we see so many Portuguese speaking members, but we have to keep our maners.
Anyway now that it's fixed I have to say I completely agree with you
VM really is #$%#% programming machine
I just hope he keeps his pace.
Soon we'll have a GUI with all sexy options of MEncoder
Thanks V: you're da man
Cheers

__________________
Rui

@ rds:

@ VM: Not really very important but, did you forget mplayer in you dist file?

Get it here:
http://www.jltoca.uaivip.com.br/file...40423-0019.zip

Hi all,
This new mplayer that comes with 040423-0019 by VMesquita is funny.
Sorry VM. You're probably not responsible for that
Anyway it seems it's now using OpenGL to play my movies.
But it is way slower than previous builds and it says it is doing a YV12 RGB colorspace convertion.
Well sometimes to take a step forward they have to take a step backwards...the price we pay for building technology
And my VGA card is already a bit outdated: nVidia TNT2
Anyway I always wondered: how do they put that nice icon on mplayer executable file
Eheh. I guess I'm not cut out for compilings
Cheers

__________________
Rui