Thanks for the reminder Hydeus. I had forgotten this in another thread
perhaps, if I recommeber correctly (and my wanting t give it a try) what a
dummy I am

-vhelp

Hey, v I didn't have time to test anything yet. I'll keep you updated when I do.
It seams it will have to be checked on an "eyes" based test. Maybe we'll run a poll?
About the GOP size...maybe better try with real DVD source??
Also I have never tried huffyuv, so I wouldn't know.
Maybe one of the guys have tried it?
Hey guys, give "v" a hand will you?
BTW and a bit OT: I just saw a week ago Jorel posting in the Ptg forum about you being a genious. Why haven't him showed up again since?
And yes I agree with Jorel: I also think you're a genious
Cheers guys

__________________
Rui

Hey,
Just thought about one thing I don't know if it's been said here.
The encoded stream produce by mencoder is just like the one that ffmpeg produced when we were testing.
Thus even though we're encoding with -nosound we are forced to demux it.
Only then we can mux with our mp2 or ac3, ok?
At least until we find out how to encode like in ffvfw with "raw frames".
Cheers

__________________
Rui

Yes, nice idea!!!
I guess he is a little busy right now... Jorel is really a great guy!
Yes, we have to demux unless we want to do audio via mencoder. I searched throught the manpage, but there's no mention on that. Of course, in linux, we could pipe throught a command-line demuxer and everything would work. Here at Bill's place I am not sure if this can be done.
EDIT: I just tried the pipe thing with mpgtx and it doesn't work. Maybe using the port of bash?

I'm forever having trouble getting mc to work. anyways..

But, to add in your mux 'ness ..

Isn't muxing the prefered way to go anyways. I mean, this is an MPEG
encoder, is it not ?
Audio quality is always on everyone's mind. Unless, there are other reasons
to just encode/w video

-vhelp

I just found out how to make avisynth work with mencoder. Check it out:

http://www.kvcd.net/forum/viewtopic.php?t=9078

The downside is that it works a lot slower than without avisynth... In the other hand, it's 37% faster than FFVFW, and very close to CCE in speed with the DialHot v4 DivX
FFVFW: 0.8 realtime (8 fps)
Mencoder: 0.45 realtime (11 fps)
CCE: 0.51 realtime

EDIT: My script wasn't very well optimized, I was applying filters in the black borders. I let mencoder resize instead of avisynth, and now it reached 16 fps. But I have to try cce again to make a fair comparisson.

@ all (or Hydeus, rds, vmes, russianexpinant etc)

As you all know about my W98 and it's DOS limitation w/ SET command,
when writing .BAT script files to process for mencoder..

Can anyone provider a working variation of the script (or two) sample, but
does not need the Matrix part. The W98 dos version of SET does not like
to process anything in between it's "" that has an equal sine (ie, "=") in it.
It give me an "Syntax error" message if it finds an "bla bla bla=" sign in the
.bat script.

Please, if anyone can provide a few mencoder command-line parameter
examples, but w/out the Matrix (hopefully, it does no need to have it) I would
be very greatful. I'm still testing mencoder for windows

Thanks very much all,
-vhelp

Hi V.
I don't thik I quite follow you, but here are mencoder encoding options:
GENERAL ENCODING OPTIONS (MENCODER ONLY)
CODEC SPECIFIC ENCODING OPTIONS (MENCODER ONLY) (skip divx and lame section till lavc).

And the simply comand line could look like this:
Of cource all in one line (do not insert spaces after : when line is splited).


What build of ffvfw you tested? This 20030927 is ~30% faster than 20041301, and I read everywhere that 20041301 is a crap.

__________________
Go for SECAM =)

@ Hydeus,

Thanks. However, the snip you posted just won't work!!
I get error messages (see below)
.
.
But, this one works like a charm, but it encodes to divX:
* mencoder.exe -vfm huffyuv -ovc lavc 5.avi -o 5_encoded.avi

and I didn't need to provide a folder name for it either

Here is your snip (cut and pasted as is, from your prev post) I copied it
from my GUI app's window, and pasted it here (below)

and here is my DOS windows' contents (w/ error messages)
Do you have any other command-line param "alternates" for mpeg encodings ??
I'm trying to narrow down the "param" that is bailing out of mencoder

Thanks,
-vhelp

The simpliest cmd I can imagine is:
and it works without problem.

Now you can put previos mpeg param's one by one after vcodec=mpeg1video:, this way you find the "exploding" parameter.

__________________
Go for SECAM =)

@ Hydeus,

You post came, while I was typing this message.. anyways..

YAHOO !!

It worked. I had to do a little debugging around. It turns out that those
snips that you post, somehome you have spaces in them
.
.
So, I took them out, and re-ran from my GUI, and bingo, it workd

Now however, there's another problem. Mencoder, after encoding fine, is
pushing a bunch of "Error in stream: PTS ... " etc etc error messages.

Here is a snip of when mencoder first encodes:
Its right after this that mencoder display screen fulls of error messages
below:

Time for some more debuggin
-vhelp

Yes, I also can sell error screens at lower prices And I have no idea even what this PTC to SCR, and other combination of this leters, with errors, mean

__________________
Go for SECAM =)

Oh, althought the source mpeg is MPEG-1, it looked great in my vdub's window

Now, to encode to mpeg-2, I would just change to -lavcopts vcodec=mpeg2video ??

-vhelp

Yes, only this change. But, as always Phil says, for lower bitrates MPEG1 is beter, no mater with what encoder, and I can confirm this. So dont be afraid if quality will be worst with MPEG2.

__________________
Go for SECAM =)

Ok guys,
Here are my 2 cents.
It seams that those f!ck!ng PTS SCR messages are only coming up when we use constant quality.
That's probably because either:
-we don't try to restrain the bitrate with vrc_minrate&vrc_maxrate
-or because for instance our vrc_maxrate is too low for the vqscale of 2 that will sometimes produce peaks above 8000. If you're using vrc_maxrate=5000 then it will either "buffer overflow" or PTS SCR.
Try vqscale=5 and vrc_minrate=300 and vrc_maxrate=5000.
That shouldn't present us any wrongful messages.
Though the quality will suffer a lot.
Also, try vrc_minrate=300, vrc_maxrate=3000 and vbitrate=2200.
That's almost constant bitrate of 2200. But the Q curve is going crazy as there is many flaws in the picture in high motion slices...
Hell I don't think we can tweak this baby because it's too damn like ffvfw.
It has almost all the flaws present in ffvfw, though there is more documentation to it.
Cheers

__________________
Rui

@ rds, Hydeus, vmes, russianxxx (if you're still around) and others..

I found out how to write configuration files, but I am having trouble w/ the
proper param setting (or syntax usage)

Here is how I have my scripts layed out:

DOS BAT script:

Notice the -include param. This is our hook to open (or include)
our external settings.

Next, we have the following script that I'm working on:

Filename: men.ini

Notes ...

At the moment, I've now modified my GUI to include another editor for the
configuration scripts. I'm calling (or refering to my scripts) as *.INI files.
They could probably be anything you like, but I'm shooting for consistancy,
I think

I'm sorry, but the .html hep docs just arent clear enough to me, to understand
and properly write the configuration syntax. Actually, the docs do not have
an actual working copy of a configuration file. It would be nice if it did so
that we could have a framework of how things are layed out.

Also, my take is like this. Once we get over the hurdle of DOS limitations, through
the use of scripting, then there will probably be more flexibility or less errors
to work with

Any assistance to my new finding would be greatly appreciated
-vhelp

Some notes..

from the .html docs, under General Notes heading:

Some Notes..

N1, The above is the best I could come up w/ in setting up a config file.
N2, I noticed mencoder is lacking an "include" param for our INPUT soure
......that's why you sat the 5.avi in my BAT script file, and in the first
......line.
N3, How I know that the men.ini script works.. ?? .. ?? well, for one, I started
......including single params and worked my way around. I started w/ the
......-ofps param. If you put the opfs=23.976 all by itself, in your *.INI
......config file, and run the BAT script file you'll get no errors,
......other than those related to mencoder's internal lack of an Encoder source,
......as noted by the (-ovc) line.

I do hope that the above made some sense I have ben drilling
my head w/ this damn mencoder vs. DOS batch scripting limitation all weekend
long - Pfew!

-vhelp

I don't understand how it works. I only get No video encoder (-ovc) selected. Select one (see -ovc help).
Exiting...

__________________
Go for SECAM =)

@ Hydeus,

Sorry, but I ended up copying more than I should have in my prev post.

Once again...

Here is how I have my scripts layed out:

DOS BAT script:

Notice the -include param. This is our hook to open (or include)
our external settings.

** The above is my DOS batch file. the -include is the param used for calling
.....up the ..\..men.ini file.


Next, we have the following INI script that I'm working on:

Filename: men.ini

Now, when you run the BAT script inside a DOS window, this is what you'll
get if all goes well (substitute your .AVI source file)

Notice, there is no error given in the: Reading config file h:\mencoder\men.ini
line.

I think I figured out why the other likes (linux error lines) show up. They
only show up when there is something wrong. At least, I'm thinking
that this is he reason why.

Also, does anyone know where I can find the font.desc files. I figure,
if I can find this, and copy it to my ..\mplayer\ folder, that even this error
will go away. And, the less garbadge on ones screen, the better it is

@ Hydeus,

I see you noticed that (-ovc) line. I can't figure this out. Even when I use
it the same in in command-line mode, it bails out w/ the error message.

However, if I use my original batch script, that creates a divX file, this configuration
file (men.ini) works fine, I think - - more testing.

-vhelp

@Hydeous
I was using the latest FFVFW build. So I guess mencoder and ffvfw speed can be about the same (what actually makes a lot of sense, since they come from the same code.

@vhelp
Nice you found out about a config file, even for WinXP users, editing the command-line can be very confusing sometimes! It's also great to know you're writing a GUI.

@rds_correia
I think the conclusion is that constant quantisizer is not that great thing we believed. Like bilu pointed in the other thread, if you need to discard half of 20.000 kbps, you'll never be able to obey the max and min bitrate. Quantisizer must vary the encoder doesn't go beyond max bitrate or below min bitrate. But I think the great power we have in our hands is that the rate control of mencoder can be tweaked. Maybe this can lead us somewhere.