I think mencoder paramters need to be tweaked for mpeg1. Probably it's the "can't quantisize lower than this" thing, tweaking some variables would solve.

Ok, nice idea. The problem is that temp.conf is generated when you click on encode. I would have to change that, but shouldn't be a problem.
The GUI doesn't use encode.bat, so this doesn't make sense in this case. I can't use a batch file and redict the mencoder I/O to a text box.
This way I would be starting to make MencodeMe a batch tool. But I have another batch tool program, fully developed that already does all the "thinking" about bitrate calculation, conversions, dowmix, etc (DIKO). So I'd rather add dvd/mencoder support to DIKO. Otherwise I'll start developing two tools that do the same job.

It also does the same thing with mpeg2, ussually way to small of a file.

Aha
So maybe MEncoder is not respecting the vbitrate value.
I've had this problem and Inc. too.
I don't know if he solved it already but I still have it here.
Most of my tests only go near 3000kbps but sometimes I have vbitrate set to 5000 and vrc_maxrate set to 9800 without vrc_minrate at all.
So can someone else tell us if this small movie is also happening?
Cheers

__________________
Rui

Then, could be, in a easy way for you, that parameters was writed step by step in the test box, meanwhile you are making settings (as besweet way). In addition text box could be edited, I mean paste onto it, besweet command line, and could mencodeme process it when click in encode, like a batch file. Or at least, copy text from text box to a batch file (it would be a help for advanced users)

Thats the point of that looong becoming threads ... there will no be any overwiev anymore

As I did say some postings above and suggested:

Set lmin to smaller values then 1, I did set that to 0.3 and have no probs.

lmin=1 works like a minimal Quantisation factor and if you set it lower, quantisation also gets lower larger filesize incl. even more quality.

Even lmin is set to 0.1 there's still a barrier which didn't let me go aver approx 4000kbit in avg .... but I think thats not our purpose in here to get even more above.

BUT!: This is a Videostream encoding GUI "only" ... and if we could build an 1:1 DVD backup GUI which gives better output then a DVDshrink or so on .... an even higher avg will sometime be needed.

Im just working on a working way to get a full DVD backup incl. orig menues and all extras working with an ENCODED stream (not transformed!) and if that works the next step would be 2DVDs incl EVERYTHING on 1DVD-R.

@anyone,

I tried mpeg-1 704x480 resize and a frame rate of 23.976 from dvd2avi.
MEncoder translated that to 23.98 fps. The final video skips every 15 to
20 seconds through the entire movie. It believe MEncoder supports
only certain frame rates and either converts your input to something
it wants, gives you a default frame rate, or stops with an error.

-BP

Well Inc, the minimal quantisation factor is vqmin (together with mbqmin related to macroblocks) indeed. Lmin, to explain in simple words, marks a "tendency". If you set lmin=0.1, this doesn't mean that the minimal quantizer will be 0.1, but minimal will be vqmin, and Q will tend to 0.1... In my tests, with vqmin=2 and lmin<<vqmin, in extreme cases I got an almost flat Q value of 2, but not below nor equal to lmin. But Q was 2 as lmin always was pulling Q as low as possible.

@vmesquita

About this log:

Writing AVI header...
New_Face failed. Maybe the font path is wrong.
Pos: 0.0s 1f ( 0%) 0fps Trem: 0min 0mb A-V:0.000 [0:0]Please supply the text font file (~/.mplayer/subfont.ttf).
subtitle font: load_sub_face failed.
Pos: 0.1s 3f ( 0%) 0fps Trem: 0min 0mb A-V:0.000 [0:0][mpeg2video @ 0x9b50a0]rc buffer underflow
Pos: 118.1s 2832f (99%) 8fps Trem: 0min 12mb A-V:0.000 [883:0]

Is there anyway of getting rid of this bufferunderrun that occurs every time I'm doing an encode? I believe that this is the cause of the "2 frames ahead"* that I get with Mencode-me.

*=When comparing the same sample encoded with two different encoders, the clip with Mencode-me is 2 frames ahead of the other sample when looking to the same frame number (I hope you get what I mean? ) Frames 2 & 3 are gone from the clip...

__________________
AudioSlave

Quoting myself

The encoded MPEG-2, muxed as SVCD and burned as SVCD, plays EXCELENT on my Cyberhome and JVC players
No sync issues whatsoever.
Here's a sample cut.
http://www.kvcd.net/payback.mpeg2.mpg.cut.37.mpg

-kwag

WOW! Nice clip and good news, Kwag!

Off-topic:
PS I did notice a swedish car in the clip.

__________________
AudioSlave

I understood that
And I did set vqmin to 1 and also lmin to 0.3 (or so) and I had a nice dynamically Q curve with more avg bitrate possible above 2000kbit if needed. You already told me your issue with the flat Q curve ... but I never had that issue ...

@black prince
Could test encoding in 24 fps (using the command-line)? Maybe it solves this issue.

@audioslave
I don't know why it drops the first frames...

@kwag
This is great news!

I have tried MEncodec-me and i really like it (very fast), but quality results are still far from tmpeg/quenc (due to avs support).

1. implement avs support (raw encoding, no filters)
2. auto crop/resize (gripcrop-like)
3. try to implement better the optimal scripts (wich are avs)

Thanks for the attention !

@ Patchworks

You can still gain from full Avisynth gain as an AVS Import can be done via a fake AVI made by using "Makeavis"

EVEN if autocrop works great in mencoder, you stll have to implementate a automatic calculation routine like in Moviestacker to receive perfect crop/resize/expand parameters for macroblock based images and for shure on individual sized Avi inputs MEGA Work !
So its very easy to use moviestacker and get the needed crop/resize values wich can be easely used in mencoder by Cropxx:yyy:y and scale xxx:yyy -- adding borders will then be done by Expandxx:yyy

There are already optimal scripts set in the provided templates of MencoderME .. like for AVis or SVCD.
Further OptimalScripting can still be done via Avisynth & Makeavis.

@ Vmesquita

Maybe Im Wrong, but a resulted tmp.conf gots these lines inclued:

kerndeint=15:0:1yuvcsp........

Output of commandline:

Opening video filter: [kerndeint=15:0:1yuvcsp]

I think there should be a "," between these to vf parameters as it seems that mencoder just takes it as it is set? As I always used a "," to separate them if encoding via manual generated bat files.

Maybe you give your String in the Programcode a nice "," added

vmesquita....V...we need a new thread of Mencode-me.
who can follow the great changes and features that you did here?


this is too big and deserve a new fresh thread with downloads, explanations about changes, general informations, little guide and maybe locked, only you can post and change in that new thread!

@vmesquita,

Could you add selectable DC precision to Mencoder-ME
So you can choose 8, 9, 10, 11 bits

Thanks,
-kwag

@inc,

Would be nice to build a list of MEncoder parms similiar Avisynth filters
and Tmpgenc settings. I found some that are part of Mplayer manpage
and have been slowly removing avisynth filters replacing them with
mencoder parms. The results are sometimes surprising. But replacing
them has speeded-up the encoder.

Some more -vf parms:

1) -vf rectangle=704:480 --> (displays rectangle on frame)

2) -vf crop=704:480:0:0 --> (3 and 4 parms are position on screen)

3) -vf scale=704:480 --> (resize frame)

4) -vf expand=0:1:0:1 --> (addborders top/bot, left/right)

5) -vf eq2=A:B:C: D --> (A=alpha, B=contrast, C=brightness, D=saturation)

6) -vf boxblur=2:3 --> (blur)

-BP

You can use MakeAVIS for that, look in the forum and read RDS_correia guide
Yes, this needs to be added.
Use the DVD script, it's designed to reproduce optimal script effect.

@incredible
Looks like you found a bug. Actually I should make this field operations another set of txt files or something like that so everyone can add their favorite field operations.

@jorel
Maybe we need a new forum then. Because many issues are just being discussed here, it would be better to have a thread for each issue. Maybe it would be better to open a new MencodeMe forum or make the DIKO forum "VMesquita programs forum" (not sure this is a good idea because MencodeMe is totally unrelated to DIKO). I'll PM kwag about this.

If I only knew how to do that in Mencoder...

Done Ok, it's just that I don't see the options, not even on the sources for libavcodec, but I see another program that already gives this precision
I'll look more into it

-kwag