In my case I need to type

cd X:/Path to extracted Mplayer CVS folder where compiled mencoder.exe resists

upx mencoder exe

./upx mencoder.exe ... wont work ;-)

1.529 kb :arrow: the smallest mencoder I ever had :lol:

BTW for readers of this thread.

Whe I did download the CygWin ... I did NOT download the whole thing!
I just downloaded the base install (default) and checked also "gcc", "make" and also "upx" ... that was enough and by this less MBs for downloading ... well for the purpose of the intention to just compile mencoder 8)

@ Fozzieb

DID you set the option in the ./configure line as quoted by VMesquita above?
Did you change BEFORE processing ./configure the codecs.config in the "etc" Folder of "MPlayer-XXXXX" Folder to the one VMesquita suggested??

@ Vmesquita

Can the UPX'ed version of the mencoder.exe be just provided to other who do not have UPX, neither CygWin installed??

@incredible

I have done both and still no joy, I'll do once more to be sure

cheers

Hi guys,
I think this needs to have a sticky here.
@Inc.,
Please post as much as you can on your method since you are one of the latest most succefull guys compiling mencoder.
Pls state which Cygwin packages you downloaded.
Also which methods used for a general CPU compilation.
We'll add CPU optimizations later :wink:
Cheers

Well even I did set the right path to the "mplayer" dir where the config files are placed ...

./configure --enable-largefiles --enable-static --confdir=mplayer/ -- enable-win32

.... I still get that "not found" error in the log.

I did one compiling using just "mplayer/" and one compiling using the whole path "C:/Programme/MPlayer/mplayer/".
As you see on the first try "he" cant recognise it, ..... and on the second try he finds the codecs.conf (although the codecs.config is set before compiling in the "etc" Folder of "MPlayer CVS XXXX").

So mencoder still gots not the correct path 8O


It would make more sense if he just recognises the path "mplayer/" as its not possible to provide compilings to others where a special user system path is set.

Another Point....

VMesquita ... where can I find a list of all ./configure ... settings which could be added for compiling??

Cause that could be VERY helpful for others reading this and for shure for me for tweaking purposes when doing the compiling :D

Thanks a lot!
Inc.

@ riu

Well ... until I dont know the whole list of possible configure parameters it would not make sense to post a clear "howto" ... so lets get into this a bit more and the result will be a sticky Ill make for all :)

Hi Inc.,
Fair enough buddy.
Hope you post a sticky in the next 12 hours :lol:
Gotta rush :wink:
Cheers

@inc
This is wierd... Using that setting works for me... :? Please try --confdir=./mplayer/ (notice the dot).

To get a complete list of setting, just do:
:wink:

Hi, maybe your right.
I thought mencoder is able to detect the right opts:

Maybe i've missed something yesterday, but is that codecs.conf error really important :?:
Isn't it using the default codecs.conf which we have already patched :?:

This is the log vmesquita's build is giving me:

Do you got in the same folder where mencoder.exe is another folder "mplayer" where the codecs.conf file exists ??

using Cygwin to compile, my exe is 6Mb, after "strip mencoder.exe" it is 5Mb,
why is it so big?

I think I will install linux on my other drive and have a bash (feeling brave)

any news on the gui front (allowing to change crop settings)?

fozzieb,

Yep, mencoder.exe will take about 5.1xx kb when its compiled (not yet stripped!). So stripping should result in less MBs.
BUT as you can read VMesquitas suggestions more above you also can download the UPX package for CygWin which allows you a REAL compression to almost 1-2 MBs! So read the thread in here carefully :wink:
To add packages to a ready installed CygWin .. just open the setup.exe ... choose a download server from the list and then enter the package options/choosing in the Setup.exe Window. There you will see by hitting "View" the packages which are avaiable. ;-)
So you don't need to download that whole CygWin system :!:

(BTW: I also did download the whole Win32 codec package and installed it to my CygWin system manually! before I did compile ... maybe thats also necessary!? maybe the compiler refers also to them?!)

According to cropping .... seems that MencoderME DOES NOT crop! even its mentioned in the GUI ... there are only Scale and Expand set in the commandline which means (IMHO) resize & addborders.

Best would be to use :Crop:scale:Expand .And also these parameters to set in the GUI .... in the GUI you only have to enter the values which will be outputted by FitCD or Moviestacker.

Also there could be "ready made" choices for i.E. 720To704 (only cropping)

Watch my posting in the GUI Thread, there I did post a Commandline where only the needed Crop: is used for 720 to 704 conversion :arrow: much faster :)

The win32 codec pack is not needed in windows, if I recall correctly.
MencoderMe does not crop, because it doesn't detect the cropping parameters (yet). The names "cropped width and height" can be a little misleading.
This. and "detect that we going from 720 to 704 and just crop" is in my to-do list. Unfortunatelly right now I have to finish a command-line mail client for university... I hate this stupid projects where every student creates exactly the same project with the same strict rules so the teacher can verify and them throw in the garbage can... :evil:

That was no "hurry up" :D (and I think you didnt understand it like that), just an advice as the config files can be tweaked manually.

So we should also take note that this is a newbie from scratch GUI which allows (already in this state) very good automatisms.

So if someone is a bit in mencoder line programming (which is easy), he just can add/delete what he wants so it fits personal purposes.
:)

@incredible
would u ever make your compile(s) available or it's all just for fun. i'd love if i'd get well maintained athlon compile(s).
thx
y (the selfish)
ps. u wouldn't keep 'old' makeavis. milan has heavily debugged this part of ffdshow too but there's no ffvfw.dll anymore. the codec.conf should be sg like this:
videocodec makeavis
info "FFdshow makeavis"
status untested
fourcc AVIS
driver vfw
dll "(path)/ffdshow.ax"
out YV12

As you can read above my last compile is still not perfect.
I want that there doesn't have to be a codecs.conf WITHING the compiling so the codecs.conf will be found in the folder "mplayer" within the folder where mencoder will exist on the HD
By this you can tweak yor codecs.conf manually "independent" from the compiling ----> That's exact your purpose :wink:

Also I first want to see which configure options are also avaiable for compiling.

Whats about that "...there's no ffvfw.dll anymore..." ???
Whats the issue or whats the advantage if set to .../ffdshow.ax ???

I wouldn't do that as if for example I feed makeavis using a YUY2 source I leave it as it is as mencoder Commandwindows also says "prefered planar YUY2"! So as mencoder already wants finally a YUY2 why should I do another colorspace conversion?

the new ffdshow releases do not install any ffvfw.dll (the 'decoder' for .avis) anymore. ffdshow.ax is used also for serving avis.
advantage? u can use the debugged makeavis. that's all. i just noted it cus i see always quite old makeavis recommended for mencoder.
the bests
y

I do see in our old used codecs.conf only YV12 is still used 8O

I ll try tonight

out YV12,YUY2

... yep youre rigth I still got that makeavis which refers to ffvfw.dll ... but if everything works, is there a reason why I should upgrade to thenewest makeavis? Whats debugged? (I do not remember now)

@inc.
yv12 is ok. afaik, it's native to menc. if u feed sg different menc will convert it. (at least, it should)
why to change? why not to change ? :-))) till u got no problem, there's no reason, really. but if u have, u can never tell whether it's the source, it's avisynth, it's the serving or it's mencoder. i'm just taming mencoder so i'd like to keep other source of error as minimal as can. that's my point.
the bests
y

Hey yaz :)

Thats the problem ... everytime I do start encding .. the command window gives me besides the whole lines a line where mencoder says ".... planar YUY2 prefered..."

Thats why I was " 8O " when I saw that only YV12 is set to the codecs.conf file in the "ffvfw makeavis" part.

Till now I dont know any encoder who likes yv12 as input c.space, also CCE uses YUY2.

So thats waht I will find out if its really native cause if yv12 would not be native this would mean more speed consumption for a not needed YUY2 to YV12 and then back to YUY2 conversion :arrow: slower encoding and less quality :!:
In case of DVD source no matter as it will so or so be in yv12, but if you do use mjpeg sources which are in YUY2 or going into makeavis using YUY2 in your AVS script (maybe as some filters need it) it would be better to keep it IF in mencoder YUY2 would be native. And that would also be responsable for less encoding speed by using makeavis compared to direct VOB input (although VOBs are yv12)

:)

Hi,
Good thinking yaz.
It took me several days to reach the same result as you did.
But I only came up to that conclusion last night.
Where were you last week :evil:
Just kidding with you of course :D although I did the same finding yesterday night :?

@Inc.
Two good things about working with makeAVIS from FFdshow:
1-It's based on directshow routines and doesn't have a bug from VfW that whenever you hover your mouse pointer on top of a fake avi file explorer.exe would crash.
2-Guys like Hydeus or Marcellus that loved FFvfw from the begining and that helped us on the 1st mencoder findings will only have one version of FFvfw installed on their system. You see now FFdshow is a package with old FFdshow+FFvfw+makeAVIS :)
This way they install one FF package that will encode through FFvfw and be able to make a fake avi to test with mencoder and match results.
So I am inclined to provide a general non cpu optimized compiling of mencoder with a modded codecs.conf file for use with new makeAVIS on the newbie page.
Maybe this way we gather more people around us :wink:
Cheers

@ yaz

DO you see the line:
VDec: vo config request - 704 x 576 (preferred csp: Packed YUY2)

To me that seems to be an advice of mencoder that he prefers YUY2 input?? Or maybe I do see something wrong.... :?: ... so everything will be internally converted to YUY2 before the encoding part of the mencoder engine starts its work. ;-) (like in CCE, maybe)

@ RDS
Yep, sounds very logical ... (although i never had problems when using FFvfw makeavis via ffvfw.dll) :? :)

@ Vmesquita

No matter what I do set as "--confdir=XXXXX" before compiling ... the path everytime will point to linux system logic:
:(

Hi Inc.,
Don't remember how the window looked like when I was using ffvfw.dll but look at mine with ffdshow.ax.
No colorspace convertion.
Am I Right?
Or are you talking about the red font text?

But then I changed to YUY2 and look what it did. It called SwS...

So what's a packed YUY2? Ideas anyone?
Cheers

May it help you?

www.viewcast.com/faq.asp%3Ffaqcat%3DOsprey%2BProducts+%22packed+YUY 2%22+explanation&hl=es]In order to compress with DivX you must utilize a YUV format and not RGB. If you are using a capture application like VirtualDub simply open VirtualDub and, after selecting File>Capture AVI, select the video>format menu and verify that the color format is set to Yuv12 or recommended 4:2:2 packed(YUY2).[/url]

Packed YUY2 seems to be a color space 4:2:2
Is your avi captured, created or maybe your avi codec set to 4:2:2 color space?

In my Windows version, when I cancel 2 pass encode, crop values became not grayed. Can you use that for now, until VM updates the GUI?

Please note that cropped width and height doesn't really crop, because I haven't implemented autocrop for now. I really need to come up with a better name, this is gettins misleading. Right now, there's no way to crop from inside MEncodeME and probably there still won't be for the next version because I need to test how mencoder autocrop works and I am lacking time now (as usual). :wink:

Then, are these values film pixel width and height?

This values are resized height and width. No cropping is done right now. MEncodeME does not detect and remove black borders right now.

@ RDS

If compiling Mencoder, try to setup the makeavis part of the codecs.conf to YV12,YUY2 ! Maybe by this you wont keep the YV12 IF you also did change in your avs script to YUY2! (thats what we should test - wich col.conversion ist fatser and better)

@ Prodater

a) YEP, if you capture in mjpeg the most common colSpace is YUY2, also when using HuffYUV

b) In vdub or elsewehre in case of 90% of capture cards you have to choose YUY2 (or in very less cases RGB) cause almost no capture card supports digizing in YV12 - which also would be output a worse chroma quality!

Easy on the beer Inc., or you'll get "fat" :lol:

-kwag

@rds_correia
the pleasure is mine :-) i'm here around very frequently but my time & bandwith is quite limited, so i spend that for downloading rather than posting this & that. shame on me :-)
- codecs.conf
it's needed by the player. afaik, menc only needs it on serving fake sources. (i've never tested what'd happen if it's missing completely but i will tonight. the vidc.avis regkey should do everything we want here)
anyway, for feeding avis there's no need to hack the orig file (loading hundreds of codecs defs) u can use your own. a simple text file is accepted but u must drop a 'release yyyymmdd' line to the top. if it's missing menc feels that some outtadate stuff is attempted & kicks off.
my present problem is that the -codecs-file options seems to be b0rked. i've found no way of putting codecs.conf anywhere else than to mplayer/codecs.conf (i hate it)

@incy
imho, menc does not bother too much about what's feeded. & so do all the encoders i know. even cce 2.67 can eat anything. all present encoders have inner conversion routins needed. imho, there's no need (& there's no reason) to keep up with yuy2 anymore. yv12 is the native form of the most common digi sources, so the encoders prefer that by nature. yuy2 is preferred rather on the capture size but it's an other business.
so, imho, your message about 'yuy2 preference' refers to the source u fed not to menc.
btw, u left behind again :-) vmesquita released a brand new compile. so where's yours ? :-)

the bests
y ( gone to test the new menc(me) )

Makes sense .. but I do see it like "get out the best" ;-)
As I also wanted to do tests on the internal chroma subsampling quality from YV12 to YUY2 (before it gets into mpv YV12 again) done by CCE compared to a ColConversion in avisynth before. But seen as general youre right that all encoders now dont bother and do an conversion-source preparation internally before.

a) Im not in a compile contest with VMesquita :D :lol:

b) As mentioned there's still that "path" error ... in my compilings but ok as I did set the codecs.conf before compiling this should not matter.
And there are soooo many options in ./configure which I would like to figure out before releasing a build - maybe there's something more to tweak ;-)

I think if Vmesquita did compile the latest CVS then mine wouldn't be different :lol:

@incy
u get me down, really. i hoped a smart little toy to play with on the weekend but ... life's hard ... (sigh)
the bests
y (living now in shadow)

Means?

Do you want a latest build? But as I understood VMesquita already provided one latest build? Or do you refer to CygWin?


PS:
"inky" 8O :?: :lol:

Pleeeease: Inc., Ink., Andres, Andrew, Andre :arrow: Choose the one you like

:lol:

dear mr/ms incredible ! (nooo, it's sounds so stupid :-))
no, no & no :-) just a simple fully optimized athlon version. just as u promised (years ago :-))
the bests
y

Well as I know Vmesquita offers Athlon optimized versions :?:

Tonight is my "mencoder"-night and I will post a latest CVS compile for Athlon! Promised!
Also I do offer two versions

- Compile where the ffvfw.dll is accepted incl. supported YV12 and YUY2

- Compile where the ffvfw.ax is accepted (as I did check that right, Ill look for riu's (rds_correia) quote on these lines of the codecs.conf ..... and here also incl. supported YV12 and YUY2


what does (path)/ffdshow.ax mean??

which path do I have to set?


Inc.

-(path) is the route to the forlder where ffdshow.ax is installed. (u can put it wherever u want on install) if it's in its right place (sys32), u wouldn't need it at all (i'll test it tonight)
- imho, no need to tackle with the ffvfw/ffdshow business. if the vidc.avis regkey is ok, menc should find the appropriate decoder. why do we have windows, anyway ? :-) (i'll test it tonight)
- would u check why 'codecs-file' option is neglected ? that bothers me much. iirc, this is for finding an other 'codecs.conf' insted of the orig (./mplayer/..) or of the built-in. but maybe i'm wrong about it.
- no need for the orig codecs.conf file ! u can use your own (see my post above) if u put ffvfw there that 'd be used, if u put ffdshow ... (it worx)
- u can serve d2v directly, as dvd2avidg has it's own vfapi. so, if u want to filter within mencoder, u don't need makeavis at all.
the bests
y

8O ............ :bawl:
now i'm confused!

choosing...
:eyebrows:
....maybe i choose....all!
:lol:

hey,...what about....AN-DRINK ?!?!?
:drunkard:

To clearify that:

My real name is "Andre" but Im known in here as Inc. or Ink (Well I think so) :lol:

Would that mean:

d2vsource.ax driver
http://aleron.dl.sourceforge.net/sou...e_20030603.zip

Or via VFAPI .. Source via .d2v or if it has to be via "VFAPIConv.exe"

http://www.doom9.org/Soft21/SupportU...nv-1.05-EN.zip
(anti leech! link just to show where you will find it)

:?:

(Im sitting in front of a MAC in my job right now, so these only "brain" assumptions :wink: )