Mencoder GUI
 

http://membres.lycos.fr/dome2004/

Sounds interesting :D
Uses DoCCE Job-Lists...

Maybe I'll translate it to english... 2 much 2 do atm

:evil:
Razor friend, either you translate it in 5 or i'll eat my hat if i ain't applying for a Learn German in 21 lessons :wink:
Any way you coud be a sports and give us a hand.
Or maybe Inc, or Jell... :lol:
Guys, I'm :angryfire: because I've been :banghead: too much trying to understand the basics...
I don't even know for sure what DoCCE or ReAuthorist really do...
Thanks anyway.
C ya

ok... y not... I'll take 15 Minutes off of my schoolstuff :D


Inhalt:

doMe erstellt aus DoCCE Job-Listen DOS-Batchdateien, die es ermöglichen, die darin gelisteten Filmdaten mit Mencoder (anstatt CCE) zu codieren. Dazu müssen Mencoder (und optional bbdmux) korrekt installiert sein. Die Bitraten werden aus der Job-Liste übernommen, weitere Optionen können in doME festgelegt werden.


---> sth like:
Content:

doMe converts DoCCE Job Lists to DOS batch files which make it possible to encode the included movie data with mencoder (instead of CCE).
To do this, mencoder (and optionally bbdmux) have to be installed correctly. The Bitrates are imported from the job list, other options can be set up in doME

afaik DoCCE is a Batch tool for CCE... it helps you to do 5 pass encodings without the need of

"ReAuthorist is designed to take the effort out of CCE/Scenarist projects. It combines the functionality of several tools that are currently needed into one neat package, and adds a whole raft of new features that are available nowhere else. It's come on a very long way since the early alpha that was released in January 2003."

Hya Razor friend :D ,
Just exactly what software do we need?
I already have mencoder 4 windows, bbdmux that comes with bbtool19 package, docce4u v1.0.1.5beta and ReAuthorist v1.0.0..
Now what do I do? Whenever I try to start docce4u it keeps complaining that I don't have cce and eclcce installed.
I just want to make those batch files to work with mencoder.
I dont want cce installed at all because I can't afford it.
Otherwise I wouldn't be trying mencoder :wink:
Any ideas guys?
Thanks

Hi guys,

I'm also working on a GUI for mencoder. There is on out their already, but
would not work w/ my win98 setup. Kept crashing or just not allowing
mencoder to encode. Basically the same nonsense I have alrady with
mencoder :lol:

But, is a little different, so I'm happy again :lol: that someone has not created
the "same" flavor as I have. But, even if they do, that is fine. The one I'm
working on now, is good for my needs. I only need to figure out exactly
how to overcome the w98 cmd-line limit, and I'll be set. vmes/rds is also
aiding me w/ this - thanks guys.

With a little luck, I'll be able to post somwheres, my madness GUI :mrgreen:

-vhelp

Yeah,
Go for it vhelp!
In no time we'll be encoding like crazy with your GUI :mnkypile:
C ya

I'm trying out your idea w/ the dos variable :confused:

working..

I love the limitness I have to deal with, in opening separately, a .BAT file
and saving, and runing and all that nonsense :confused: my app is comming
along very nicely, thanks :mrgreen:

-vhelp

Hi vhelp,
Here is mine:
First I set the variable for the matixes.
Then I do the command for encoding.
Then I put a pause command so I can see what mencoder's log afterwards.
Of course I could always use > logfile.txt but you know: right now I just don't feel like making a lot of text files :wink:
C ya

EDIT: how come there is a line break between the matrix variable and the rem line??? I don't have that on my batch file... 8O
Anyway note that I got rid of vlelim&company arguments because I'm working with avs files now :wink:

hay rds,

how do you add in the logfile.txt for mencoder ??

I'd like to add that in my GUI (button or something)
thanks.
-vhelp

Hya vhelp,
Just edited my previous post so you can see how.
The only problem is this way you can't see in real time what the encoder is actually doing :cry:
Cheers

rds,

I may have a way to pipe the DOS window inside my GUI, like a progress
bar by "capturing" the DOS internal data. Mind you, I only done this twice,
but it looked really nice to have as a feature :mrgreen:
.
.
I'll have to dig around for that BETA app I was working on (this very same
thing w/ dos piping) and copy some of the code. we'll see :wink:

As for the reason why your script bugged out w/ a line-break, it's because
of the last char went beyond the browswers limit, and broke the line in half.
Note the "," at the end, while the others are just flushed. I be (as an experiement)
if you revise that line above, by one space (maybe in beginning) the line will
not break :wink: try that out just for the heck of it, so that you don't drive
yourself crazy in future posts like these :!:

-vhelp

Hya Razor friend,
Just exactly what software do we need to run dome GUI?
I already have mencoder win32, bbdmux, docce4u v1.0.1.5beta and ReAuthorist v1.0.0..
Now what do I do? Whenever I try to start docce4u it keeps complaining that I don't have cce and eclcce installed.
I just want to make those batch files to work with mencoder.
I dont want cce installed at all because I can't afford it.
Otherwise I wouldn't be trying mencoder, right
Any ideas guys?
Thanks

maybe the demo would do :idea:

I'll have to test it tomorrow (today I had/still have to prepare a big powerpoint presentation for school... "UN Security Policy and the Example of Irak"... loooots of work :( )

Both cce and docce4u is not needed. You've just to load the project in Reauthorist, so the needed txt-file is created when you click encode (even if RA complaints about the missing docce4u). then load the ReAuthorist_NewDoCCE.txt in DoME ('Einlesen') and create the batch file ('Erstellen'). After that you can close DoME.

when you execute the batch file, it encoded the all the m2v to smaller mpv files. the rest you can do the usual way (Scenarist, ifoupdate,...)

Hi, finally my mencoder GUI has moved a big step forward, now also avail. in english and no more limited to processing DoCCE batch files. Screenshots and Download here -> http://membres.lycos.fr/dome2004/english.php

key features:
- load any mencoder compatible file (mpg, avi, ogm, ...)
- encode them to mpeg2
- add pre processing filters (denoise, deinterlace,...)
- change resolution, frame rate,....
- batch processing
- encode them directly, oder just create a batchfile

Amenophis,

I just saw the screenshots, and they lok great. I can't wait to try. :D

EDIT: It is asking for vcl60.bpl... :( I'll try to find this file.

hi,
if you've already found the binary, start your search one line below ;)

All needed files (except of the mencoder and bbdmux package) should be in this Lib-File.

:douh:

there's again a new version out now, because min.quant=1 was broken in 0.4 and before.
by the way, some now settings have been added, too.

get it here (DoMencoder 0.5): http://membres.lycos.fr/dome2004/english.php

Hi guys,
Sorry it's way OT and all but I can't find a good guide on ripping a DVD with PGC. I just find a couple
of guides at doom9 that I'm not sure if they are rip PGC based.
Could someone point me to a good guide please?
Also, is a PGC rip stricktly needed to work with ReAuthorist?
I always rip my DVDs with DVDDecrypter in File mode. Will this tool and this mode produce PGC rips?
Would a PGC rip be one that only rips the main movie?
Thanks for bearing with me on this one.
Cheers

Amenophis my Friend! You did a very very amazing work!

I in a very big testing phase TmpgEnc-CCE-Mencoder-FFvfw and I really do love mencoder using the settings your GUI does output!

But I got problems to let run mencoder.exe with the commandline your GUI did output.

As you see below I had to change to the dir of where mencoder does exist, so I took your GUI's output, add him the alternate Matrix and the "cd" command at the beginning.

I did find out that this encoder with the new figuredout settings frome here does encode awesome dark underwater movieareas!

Not mention the speed!! 3x faster than TmpgEnc and a touch faster than CCE, even when using the FFvfw MakeAvis engine. HELL! :D

And when I do inspect the diff encoders outputs in Bitrateviewer, mencoder does output a very much better Q curve!!! More calm and changing in parts where it makes sense! Where on the other side in TmpgEnc or CCE the Q curve sometimes JUMPS up to 7-8 where mencoder keeps the Q in a range of 2-4.

Ill do try your new GUI right now!
Thanks again!

Inc.

Hi Inc,
Please post your methods using doMe.
I think I'm missing something with PGC ripping.
But I have other questions beside this one too.
You're use makeAVIS right?
What script do you load?
The script you load is for resizing purposes only or are you using MA script?
Do we need vlelim=-4 & vcelim=2 even if we're using avs scripts like MA?
Does anybody have a problem when erasing the fake avi made by makeAVIS?
Whenever I try to erase mine windows gives me a message saying that "an error has occured
and it will have to close the explorer.exe". Then I pick "don't send to microsoft" as usual.
Thanks

Hi RDS!

Well the script above is the method I used in doMe

but the problem was that I couldn' get the bat running! It closed immediately. Only when I did apply at the beginning
Means the pointer to mencoder.exe.
So I never Could make the encoding starting directly from the GUI, I had to make the line addings afterwards and then it worked.
The Script I'm using where I do the fake AVI from is just an import script, no resizing! Just a minimal TemporalSoften and switching to YUY2, thats all.

@Inc
Hi buddy,
But we have to resize right?
For instance. I have a DVD that is 720x552 without black bands.
Using FitCD v1.1.3pre1 and you're precious hints on using it, I made up a script like this:
I'm shooting for a non anamorphic KDVD of 704x576 with overscan=1.
So I figured: if I'm already filtering inside the avs script, there's no point on going filtering with mencoder, right?
From the man page of mencoder I understood that vlelim=-4 & vcelim=2 are both filters.
My question is: if I'm already filtering in the avs script I should drop those?
If so are there others I should drop in the mencoder CLI?
I haven't started using doMe because I don't know how to use ReAuthorist but as soon as I get it, I'll try it ASAP to give my feedback.
Also, looking at mencoder while it's encoding I get the sense that using makeAVIS avi it is switching to YUY2, am I right?
Isn't it better using YV12 instead? How do we switch to YV12?
Any problems deleting avi's created by makeAVIS?
Again, thanks for bearing with all my noob questions.
Cheers

Sorry for that, i forgot that most people haven't registered the the mencoder dir as an environment variable. i did that before i made the GUI, so it was working for me. you can do this my doing the steps shown in the image below, then you can access the mencoder command in the dos box from every dir. nevertheless, the 0.6 will let you specify the dir of the mencoder binary.

http://www.digitalfaq.com/archives/error.gif

Exactly in that Variable name: Path I got the Variable Value:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\Sy stem32\Wbem


???? Do should I just add the C:\mplayer there ??? Or the whole path to mplayer?


@ RDS...

You script looks fine, I did not resize cause of a correct captured stream at 704x576 pal just for testing but this night I will do my first full encoding on "The Rock" which was broadcasted this evening, ok that one I resized to overscan 2 so FitCD was used ;-)

In case of Colorconvversation via FFfvw, well YUY2 would be best as its the best one for mencoder as I saw in the command window.

I don't know any encoder which works best with YV12!

TmpgEnc uses rgb24
CCE uses YUY2

.. and mencoder IMHO also uses internally YUY2 to get to thge YV12 4:2:0 final m2v.

And its correct that u use Liniter() as as default mencoder uses a 0-255 Luma range encoding IMHO.

I everytime use a well configured Levels() Command to tweak to the right luma range and that command also gots a safe internally not to clip over the legal TV luma range.
And BTW Levels() or ColorYUV() use proportional luma range scaling, where on the other side Limiter() just "cuts"! the luma range. So be careful.

You've to enter the path to the directory, where the binaries are located. p.e. in my case, the mencoder binary is "c:\mplayer\mencoder.exe". Each directory which is part of the variable value must be separated by a ;

Hmm, its odd. Try using a VOB file instead of an AVI and you'll see that mencoder only uses YV12 from the begining and until the end of the whole process...
And since DVD is YV12 based, and the less with mess with colorspacing the better, I thought there could be a way to work in YV12 all the time.
I'm quite sure that Phil would highly advise us to go on YV12 the whole time :wink:

Ok, ok. Now I don't quite get it.
You mean I'm doing the right thing by using Limiter() in my script but you would advise me to use Levels() or ColorYUV() instead because these are not so radical?
Could you elaborate a bit on this one, please?
Cheers

Well Phil, I and many others to say thats its best to avoid Colorconversations as far as possible! Cause every colorconversation means quality loss. Example: I got a YUY2 based mjpeg Capture. In this case I try to do the WHOLE job in avisynth in YUY2 if I would use CCE later.

mjpeg = YUY2 :arrow: Avisynth in YUY2 :arrow: Going into CCE which keeps the YUY2 as it treats internally also the video in YUY2 :arrow: final mpeg output in YV12.

YUY2= 4:2:2 means 16Bit

YUY12=4:2:0 means 12bit and a differend Chroma subsampling.

And if you import a YV12 DVD d2v source you should keep the YV12 by using YV12 filtering, but anyhow ie. TmpgEnc processes internally in RGB24 so the way would be YV12 :arrow: YV12 :arrow: RGB24 :arrow: YV12

You see that you can't avoid a colorconverstion in the editing/encoding process seen as a whole, but you can avoid adding more conversations as really needed ;-)

Well Limiter() in case of encoding with tmpgenc afterwards makes (at the end of the script) no sense, maybe as a little compensation before using filtering in the script, but if you set the encoder to do a TV compilant lumarange encode he automatically scales the luma by itself and in your case this would mean DOUBLE luma scaling!

I did underline your "purpose" in the script cause to me it seems that mencoder in his defaults does not scale the luma to right TV specs settings.

;-)[/quote]

Sometimes I get during encoding some error lines containing:

PTS to SCR delay 8755 is too little!A-V:0.000 [821:0]

And If I don't set at DVD compilant encoding the min bitrate to maximal 300, ... a lot of buffer underrun errors do occur, larger values = buffer underrun!

?????

What happened? 8O

Same here buddy.
I always set vrc_minrate=300 otherwise those buffer underflows tend to appear...
As to the PTS SCR, I really haven't come up to a conclusion as why these appear. But these don't show up so often...
Anyone experiencing the same??
C ya

Hi all:
related to those PTS .... SCR ... yep, the same here. I make my tests with a 1000 frame
sample, and they aways appear between frame 619-637 (I should look at the source
and see what happens in this frames).
I think they slow down the encoding.
And they appeared in all my tests, with very different settings.

I got PTS SCR on "hungry for bitrate" scenes (high motion, high complexity). Thats all I can say.

Yep,
So this is infact happening to a lot of us.
I could tell you that I have tried full encodes with with mencoder without those messages, and I've tried it with 5min clips and have seen those.
Also think it has something to do with the source.
Oh well. Maybe that doesn't matter much now.
Cheers

Well I took the GUI and its default settings, where Bmin is set to zero. In the resulted command line there is no bmin defined! Only Vbitrate and VmaxBitrate.

This gave me no more buffer underflows! Problem solved. Afterwards inspecting the final whole movie in Bitrateviewer, the min Bitrate was never going under 800kbit.

I tweaked a bit the I-Quantizer and B-Quantizer Factor and of course the Vbitrate value to finally get to my needed final size of 1900 MB wich was wanted at 704x576 :arrow: result is amazing for a capture! Encoding Speed was 23fps!! Almost realtime.
Bitrateviewer gives me very nice dynamic Q curve, dynamically on those parts where it has to be. The Bitrate allocation is very good!

But Still there came up while encoding these few errors about PTS SCR Delay. Well I did ignore it and after encoding I opened that m2v in Restream to reset the GOP timestamps.

Both Streams, the one with and the other without resetted timestamps I muxed each using Mplex.exe with the assigned mp2 to DVD specs.

No errors came out and playback and synchronity using WinDVD was well.

I also did one encoding of 352x576 to one CDr before, where I first got many underflows when muxing that, but I cured it using a bigger bitratevalue in Mplex instead of the default and instead of the recommended ZERO.

Inc.