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.