So what... it's a GUI... can't do much about it...

At least its open source and developed further!

Why not sit in our caves as we used to do...

Cause development should bring us something new, and not something that already exist.

__________________
Go for SECAM =)

There is also sth like personal development which can lead to more skills and thus resolve in a better software later on...

Good point. And let's no argue about it.

I'm very intrested in vHelp's project (even that I'm not using mencoder for my works), but it seems that we have anoter person disappear

__________________
Go for SECAM =)

** UPDATE #3 **

no, I haven't fallen off the face of the earth

I've just ben very busy w/ my personal life, and also my GUI app too
..working on it when I find new ideas to throw at it.

I believe to have figured out the command-line issues. From my point of
view, CMD.EXE is ok for some OS's, and mixed in w/ mencoder's strange
way of importing param strings/switches/values/options etc etc, it will work,
or it will not. CMD also has limitions. I found, that (so far) in the end, its
just best to stick w/ windows own DOS app. Anyways..

I've also fitured out how to work ini files for mencoder's imorting of config files
However, there may be a few items that I did not catch through my trial n
error process that I have ben exhausting myself over with, during this whole
weekend. I had Friday off too

I have yet to see anyone else's config files for mencoder, so.. basically, I'll
assume that I'm the first and only one who has discovered it's proper use
but, I could be wrong.
So, I'll keep a tight lid on it for the time being, untill someone else posts a
sample of an actual config file for mencoder's encoding options. I know mine
works but I'd like to finally see someone elses (for a change) instead of
others $ importing $ upon my hard work and all

Now, for the question I have for those of use... to be continued in next thread
-vhelp

.
.
Sorry guys, I almost forgot my question to you all

in command-line mode, how does one set (exactly) the bitrate, in order to
see a change in filesize ??

The reason for the DUMB question is because I've ben (what I'm assuming)
chaning the vitrate around a bit, but nothing seems to be changing the file
size any. Its always the same size. And, I don't get it.

What's the command-line param ??
Can someone give me a few examples, like if I want a 3000 bitrate file, and
it's size is (lets assume) 1mb for a 5 second clip, and I change the bitrate
to a 6000, I should get perhaps 1.5mb now. Mind you, that's just a random
example. Doesn't mean it actually works.

Thanks all,
-vhelp

Changing the vbitrate parameter should already do it. maybe your sample is too short, or you've to adjust the quantizer range. Also you shouldn't use vqscale in this case, because with this parameter vbitrate is ignored.