Thanks for the link.

But anyway:

Bug:

• MencodeMe hangs up if mplayer it is not in mencodeme folder. It hangs up in a special way. We can press buttons but encode and preview keeps grayed, stop can be pressed but do nothing.

Ideas:

• Save settings as default.
• In open dialog, show all supported files as default.

Quoting vmesquita, from first page of this thread:
"You also need to put a mencoder and mplayer binary in the same folder."


-kwag

But does it even start encoding in your case?
Because I have mencodeme in a different folder than mencoder/mplayer and it starts encoding but it's slower than usual.
I'd say it's half as fast as usually and it made my pc reboot itself.
Nothing that ever happened with bat and ini file only...
Maybe the log box is doing that.
Maybe the new mencoder build.
Let's see if I can find why.
Cheers

Kwag, don't take it in such way. I had read all thread and don't remembered that. Further than this, with time it will be much people that uses mencodeme and not had read "first page of this thread". For this people it would be better that mencoderme could have a readmefirst. I think just now too, that for these people and for other too it would be better 2 releases 1 with mencoder.exe and mplayer.exe and other without it (or maybe only one full packet, in spit that other ppl don't like this last one)
I only want to help. It was not for me (finally yes), as I searched and downoloaded a mplayer version that not worked, before rds link.
If you think that in any way i'm hussling in this thread, please tell me and I would try be more carefull with my posts.

Edited: Karl reply is not necessary, don't worry.

Just Relaxing: ommmmmmmmmmmmmmmmm

:D :D :D :D :D :D :D :D :D :D :D :D

Well, all of you can start laughing for a wile. I just had needed mplayer installer in my HD.

:lol: :lol: :lol: :lol: :lol: :lol: :lol: :lol: :lol:

Why would I think that 8O
I just pointed to vmesquita's comment, thinking you had overseen it :!:

-kwag

I beg your pardon. I don't understand english connotation so good as I would wish.

Hmm,
Not trying to write on kwag's behalf Prodater but, I saw that post by kwag as a aid for all of us.
He knows the thread is very long now, and he knows many people have already forgotten what's written in the first 5 or 10 pages.
I speak for myself: I have forgotten.
Eventually my problem is different than yours but I still had a crash from my WinXP.
So I'll go by Vmesquita's 1st post and I'll put everything in the same folder for safety.
And I should say that you were helping when you posted your problem.
No hussling from your side for sure.
I just interpreted kwag's post as a help for both of us and other guys.
BTW did it work on your side?
Cheers

Gee,
Prodater don't do that again :D
Everybody knows this has been difficult days here :wink:
If you do that again I'll strike you with 2 months without posting here :lol: :lol: :lol: :lol: :lol: (just kidding of course)
Anyway it work did it?
I wonder why I don't need to have everything in the same folder :?:
Cheers

@Vmesquita,

Coud you add a VBV buffer size override in the GUI :?:
I find that for high resolutions (ex: 704x480), the VBV value is too low, when selection *->KVCD presets.
The VBV size is fine for low resolution, so it would be good option to have a selectable VBV value, or if you can automatically select a VBV value, depending on the resolution.
Example: 352x240 is 40, 352x480 and 480x480 is 112, anything over that, it's 224

-kwag

@rds_correia
Everything (MEncodeme.exe, mplayer.exe and mencoder.exe) must be in the same folder.

@kwag
If this parameter is set according to resolution, that it's better make it automatic. I just didn't knew how to set:
Is there anything else I should know to automatically set this?

Without mplayer it start encoding, and without filter (neither avs nor mencoder) 1 pass rate = 30 fps (in P3 450).

I don't think so :!:
It's just that I see many quantization errors (blinks) when you use a low VBV value on high resolutions.
But when I choose your KSVCD settings, I don't see the errors, because the VBV is set higher.
You have a fixed value for MPEG-1. Change it the same way you do as for MPEG-2, depending on the resilution, adjust the VBV value.
The values I gave above, should be the correct values for each resolution.

Edit: 528X and 544X should also be 112 :!:

-kwag

@VM
Please, include this values in a help file (with more thinks too of course) and a button for that. --> todo: Help file.

todo: Can you include commands buttons in preview window or in mencodeme window.
I request that for... you will see.
:idea: :idea: :idea: :idea: :idea: :idea: :idea: :idea:

You can open 2 (or more if you machine could) MencodeMe instances and preview both simultaneosuly (waiting to first player begin, related with temp.conf. It would be wonderfull if you can pause playing in same frame and begin to play almost together. Better than this, it would be possible a "play together from frame" control?
Also you can encode 2 or more simultaneous files.
Now my logs:

Note: I don't know if once a file is previewing or encoding, temp.conf can safely overwrited to permit preview or encode second file.

Nice Link.
Buen Link.
Several languages link.

@ VMesquita

I just made an example avi (sliced) via makeavis and used in MencoderME the 2pass option ...( I wanted to see a bitrate/Q behaviour in comparison 1pass/2pass on a sliced sample).

... Could it be that since you write an "encode.bat" the 2nd pass wont start??

The logwindow:
Then it stops and nothing happens.
Means the GUI doesn't create a new "encode.bat" incl. the variable %Vpass% set to 2.

:?:

:) Inc

I'm trying to make a ksvcd with this software but I get this error

Failed to open frameno.avi

: No such file or directory
Reading /cygdrive/c/Documents and Settings/Administrator/.mplayer/codecs.conf: Reading mplayer//codecs.conf: Using built-in default codecs.conf.
The vbitrate option must be >= 4: -115
Reading config file /cygdrive/c/Documents and Settings/Administrator/.mplayer/mencoderReading config file temp.conf
Exiting... (error parsing cmdline)

what does it mean?

Mauro

I just finished encoding from avi with makeavis two passes. Not problem like you, but many errors.

My log

What "cliping 1 dct coefficents to..." means? Can I use this encoded file for making an qualified KVCD ?

@vmesquita,

Just tried MEncoderME v0.22 and when encoding 2pass I get stack_error
and program ends immediately without finishing?
I decided to use 1pass and to encode without avs motion adaptive script.
I used the batch file generated by MEncoder "encode.bat"

My avs scritp and results are as follows:

1) video file size prediction was 745mb with audio 42mb (64kbps).
The actual file size was 733mb with 12mb overhead = 745mb. Perfect!! :D
The MA script must be effecting quantizer which limits file size somehow :roll:

2) There were changes in picture quality. More blockiness, less gibbs
effects, frames were dropped as before (probably that dct error or
underflow error) :roll:

3) Generally not bad 8) It's getting there.

I have questions:

1) which MEncoder filter effects blockiness??

2) What is causing underflow error and dct errors. The encoder is
dropping these frames.

Thanks

-BP

@Prodater64
I understand your idea, but unfortunatelly, I hvae no control over the frames being shown by mplayer. I just launch the player and that's it. :(

@incredible
The batch is used for nothing internally, it's only for debugging. But I'll check if 2pass is still working, I may have made a mistake when implementing preview.

@mbaluda
Looks like your bitrate was too low for some reason. Please post your complete logfile.

@Prodater64
MEncoder always shows this messages when encoding mpeg1... I have no idea what it means.

@BP
If you are using avisynth, no filter is used for encoding (you have to select makeavis template). The stackdump seems to be a mencoder problem, today I got one with a captured AVI.
I also don't know about the overflow/DCTs. Maybe a search in mplayer mailing list could clarify.

Not always. It seems these errors are conected with Notch matrix. If you use the default matrix there aren't such errors. Maybe this is the way in which mencoder calculate the dct coefficients regarding the matrix. Well, I can be completely wrong here...