@ vmes,

Yes my friend, my goal.. is to create in interface similar to TMPG :mrgreen:
But, right now, it looks like Mr McGoo (spelling) :wink:

-vhelp

Agree with most of your post VM.
But where did you come up with that beautifull codec.conf file of yours?
I've browsed the whole internet looking for it as we may find more needed files next to it but I really can't find it...
Like that font file that vhelp mentioned.
I also agree with him where "the lesser the trash on screen the better".
Thanks and C ya

@Vmesquita
Probably you're right, but I've read (I somewhere in doom9) that lates ffvfw build is very alpha/beta/gama/delta/night-build and was not optimised for speed, also few bugs included for free ;)

@vhlep
Create subfolder \mencoder\mplayer\font and create in it empty file font.desc. But this still produces two lines in cmd window, reporting succes of find, and zera data ;)

:!: Update guys...

I did some more "what if's" and now the line looks like thus:


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)

The above works, and no more error message as previously demonstrated.

Here is the new DOS screen (similar to prev one)

Do I have everything correctly layout for an MPEG-2 encode ??
I ask because this script snip was based on an intial MPEG-1 and I only just
copied it and thanced it to mpeg2video - that's it :roll:

We're definately making some headway here :mrgreen:
But, I'm really getting bushed :( and there's no help from any else here :(
So, I'll do what I can for you all :roll: because its for everyone's best interest :)

-vhelp

Update !! !! !!

Guys, I MIGHT have it :mrgreen:

stay tuned :!:

FWIW.. the last hurdle w/ the (-ovc) error. It's looking for the encoder :roll:

-vhelp

Hang in there buddy. I can only try your way tomorrow.
You see I've been messing with the vrc_minrate&vrc_maxrate and the vqmin&vqmax to see if we can have a "average" quality mode between 3 and 5 or something.
We have to be able to constrain the bitrate a bit otherwise we'll end up with a super encoder, super GUI, super encoded video, but that is out of DVD specs and is not playable at all.
Anyway you haven't told me if you tested the ReactOS command.com.
I tried it today at work and I liked it so much that I'll start using it on the company's laptop that is running W98SE since it's a Celeron 300 with only 64Mb :lol:
Really neat features in ReactOS :D
And that way everybody could just use a loooong batch file without any problems.
Cheers

Hi VHelp,

A couple of suggestions, change vrc_minrate to at least 300, keyint to 18 and maybe vmax_b_frames to 2.

@ rds,

I scrapped ReactOS because I thought it was a TSR. TSR's require a user
intervention, and you can't close those down from a shell - not w/out having
a "leak".

Is this a TSR app ??
You can tell, because when you exit your DOS window, an TSR screen will
pop, asking you to press Ctrl+C to finally leave it.

If not, I'll give it a try :!: What is required to install this.. where and how ?
-vhelp

Hi vhelp,
Also download and try this ReactOS that is a substitute for the command.com that is brought on Win98/ME.
ReactOS shell
Here is the site hosting the file with some explanation ReactOS site
Hope it helps 8)
C ya

Note:sorry for double posting :wink:
And it's not a TSR. You can exit it with a simple "exit" command or by closing it's window. Give it a shot. I'm pretty sure it won't let u down.
Edit: just copy the exe file to your folder of choice (best where mencoder exe is located and rename it to Cmd.exe.
Double click it "Et voilá":nice windows 2000 like shell :wink:
Cheers

@ rds,

ut-oooo. looks like reactOS does not accept initial params. Looks like it
won't work :( :( :(

My delphi app can call it up, but when I pass it a simple param string (below)
only a dos window pops up.

** Note, I renamed the .exe to "command.com"
** Note 2, the od1.filename is my .BAT file.

I'm totally stumped !! :roll:
-vhelp

Hey,
Where are Karl, Inc., Phil, Razor, Krassi these days?
These guys can really twist encoder options.
I sure would like to have them around so we could try something.
It seams that ffvfw problem got everybody on the downside...
But that's just temporary guys.
If we can't do it with ffvfw or mencoder, heck we'll find something even better, faster and predictable.
We were born to put 3 seasons of the simpsons on one zip drive like SansGrip said :wink:
Come on guys, cheer up.
C ya

@ rds,

I revised my post above yours.
-vhelp

8O 8O 8O
Man I really don't know what that means...
You could be right.
Anyway the docs say we have to rename it to Cmd.exe specifically.
Else we better discard it :cry:
C ya

ok, will do. CMD.EXE it is :)
-vhelp

Aaaannnndddd, does it work now??? :D

So far, when I call CMD.EXE and my param string, the only thing that
happens, is that a DOS window pops upon and a screen full of CMD's nonsense :confused:

I'm still working on trying to get CMD to accept parameter string ie,

CMD h:\mencoder\mencoder.exe

Just doesn't want to happen. Perhaps CMD does not have param capabilities ??

-vhelp

Ok, here is (hopefully) the last place that I'm having trouble with. Because
I'm not familiar w/ mencoder's params and MPEG1 or MPEG2 intricicies, I
am flying blindly w/ errors. So, please guide me a little, with the proper
MEPG-2 settings :(

It looks like my mpeg2video is in error somewheres. Perhaps its a mixture
of mpeg1 and mpeg2. I don't know. But, I'm asking for an MPEG-2 specific
set of param strings.

Any help would be much appreciated,
-vhelp

the parameters seems to be ok, but if you have not changed the commandline (or ini) you mentioned some posts ago, this could be the reason:

the syntax of something like this would be better:

additionally, i would suggest the following settings:

@ Amenophis,

Yes, at first, that is what I did too :lol:

But, then I realize, for configuration files, they (the '-') has to be amitted
from the lines. Also, there seems to be a ass-backwards about its format
or syntax. Things don't add up the same, as when you write your command
line params. That's why I've had nothing but trouble w/ this configuration
file (aka, my men.ini file syntax) But, just believe me, the '-' has to be
amitted, and the file (for the most part) has to be line-delemited. I think
it's more stricker, but doesn't make any sense :confused:

@ rds,

Sorry chap, CMD.EXE is a bomb. I figured out how to execute it w/ a param
string. Unfortunately, it crashes out w/ Exception Errors :confused:

Still, becauase I'm under W98, I truley believe that mencoder does not work
w/ W98 (and probably W98SE/ME too) If it works at all, its only minor or the
simple things, that it can do. But, throw a long and cryptic param string at
it, as in our futile attempts, and it wines like a tight-ass baby :!:

@ rds, I think CMD is ok for minor scripts, but that's about it.

Also to note, until a proper configuration file can be standardized,
or known for its proper syntax, we are looking at a dead horse (us W98/SE/ME)
goe'ers :(

I might play around w/ it for a little while longer, but that's about it. Also,
because of this, looks like my GUI will freeze for the time being :?

I'm really pretty pooped now :confused:
-vhelp

Gee, sorry that. I'll give it a try today with my laptop running W98 and see if at least I can throw a big command line. Should I experience the same probls we should abandon it.
That's understandable big guy. I just would feel very sad if you had to leave us because of this W98 issue. You are a good programmer and a nice GUI could appear but that can only happen if at least you can use the encoder on your system...
I still remember using your nice GUI for bbmpeg. I still use it once in a while. It's really nice.
I'll keep you updated on my tests tonight.
Cheers and thanks