@Dialhot
Do you use only Deen() or do you change any parameters?
(I'm talking about Deen 1.0 beta 1...)

Only Deen.
I just did "fast test campaign" and didn't want to bother with all possibilites allowed by parameters. So I used the defaults.

@Dialhot
Yep, works for me. The default settings sure look good without any tweaks :wink: .

Most of the movies I've done lately, I only use:

That's it :!:

And if it's a VHS capture, or something other than a DVD, then:

That's good enough for me :)

Only on very noisy analog satellite captures, I add: STMedianFilter(3, 3, 1, 1 ) to the beginning of the script.

-kwag

no resizes...only the dvd source :?:

No No :!: :lol:
Of course the resize and addborders, etc. are still in there :!:

-kwag

cool!
then i will do double test:
the new CQMatic 1.3 and that script with resize!
8)

i have only one problem....
only 443Mb free in 140GB ! (60Gb + 80Gb)
i need to finish some jobs and tests first.

:rotf:

correia.....what ?
:screwy:

Jorel, thats a nice avatar!

I was killing myself of laughing because I still remember when I had a diskless PC (only one 360Kb Floppy) and when I got my 1st external harddrive for a Schneider Euro-PC with 10Mb.
Man that was quite some space for storing :)
And here we are nowadays complaining about lack of space on 140Gb disks :D
That's hilarious isn't it :?:
Hmm, coming to think of it maybe for you it's not, right :wink:
I'm running with 40Gb+20Gb and I'm fine for now but if I install Mandrake on this baby I'll have to live with roughly 12Gb of empty space.
Then maybe I won't be so hilarious, will I?
Cheers

Oh! I almost forgot.
That's quite a nice avatar Jorel :)
Cheers

ink and correia, thanks :wink:

it's not an avatar, it's our salvation!
:lol:

yes correia,
in 1996 i had one ibm aptiva using win95, 8 MbRam,
100Mhz(not pentium,i forgot what is)
with hd 820Mb and was a big size, 80% space free.
now with 140GB in pc and another 40Gb for backup(external hd)
i need to trash some tests to got "just a little" space....~5Gb (just a little?!?! )
:compress:

:lol:

I remember when I got my 486 with 120MB HD!!!!
I thought... WOW!! I'LL NEVER FILL UP SOM MUCH SPACE!!! :mrgreen:

You don't use a threshold any more? :roll:

Nope. It's now fully dynamic ;)

-kwag

for me only works using ;

Mpeg2Source("D:\source\d2a.D2V",cpu=4)

BicubicResize(xxx,xxx,...) # overscan 1

ScriptClip("nf=YDifferenceToNext()"+chr(13)+"unfil ter(-(fmin(round(nf)*2,100)),-(fmin(round(nf)*2,100))).TemporalSoften(fmin(round (2/nf),6),round(1/nf),round(3/nf),1,1)")
AddBorders(x,x,...) # overscan 1

function fmin(int f1,int f2){return(f1<f2)?f1:f2}
# without "function" don't work

something wrong ?

As a minimal MA script, it would be used like this:

-kwag

[quote="kwag"]Most of the movies I've done lately, I only use:

That's it :!:

Wow interesting! I didn't do an actual encode test yet but just by going thru frames in virtualdub, comparing this MA script to your other one in the sticky, I can see a huge difference in details gained.

I do have one problem with your MA script, and it's something I noticed before stumbling upon this post. It seems that this ScriptClip line has problems with black and white text fading in during an opening credit sequence. The exact movie I'm encoding is Kill Bill, Vol 1. The beginning credits for this film feature a black background with white text slowly fading in, then fading out. The problem is that with this MA line, text will fade in for about 3 frames, then disappear, and fade in again. If I remove the MA line the text fades in as normal. It's a very strange phenomenon and one I haven't seen before! Any clues what's causing it?

I've been having the same problems with unnatural surfaces using your old MA script for quite some time now, so this thread is of extreme interest to me! I'm going to try out Phil's "new deen" script and give it a try.

[quote="J-Wo"]No, that's not it :lol:
I haven't used AviSynth now for over 2 months, and I have no plans to go back :cool:
I'm completely into mencoder right now, doing symetrical encode tests on Windows and on FreeBSD.
If AviSynth existed for other platforms, then I would definitely use it. But the way I see things, Mencoder has most of the basic necessary filters, and they work on every supported platform. For me, that's a clear advantage.
Catch up to some of the Mencoder threads ;)

-kwag

Oops I forgot to put an end quote tag in my previous post, because the line "That's it!" wasn't actually written by me!!! :D Oh well...

Wow that's the 2nd time you've told me to move over to Mencoder. I didn't even know you guys have even dumped AviSynth! I keep trying to go over to those threads but I don't even know where to begin! There are so many stickies there but I feel like I'm back to square one, on the day I first came to kvcd.net and knew not a THING about KVCDs or Tmpgenc or Avisynth!

If there are any basic "primer" threads I should be reading first, please pass along some links! Thanks

And so I tell you to NOT do that.

Kwag is actually "playing" with that encoder that is completly unable to produce any really trustable stream for the moment. It has big issues that must be fixed before to say it is a stable encoder.
More over, the line suggested by Kwag to bypass one of the problem (adding noise to avoid underflow - that doesn't work so much BTW) gives a picture grainy as hell and I'm just waiting for the moment when he will admit that (he already reduced the value on the noise for lower resolutions, even if 3 days ago he was saying the noise was so light that it can't be seen...)

So in other words : go to mencoder if you want to play (that's realy a funny tool ;-)) but not if you "need" to work :-). And go only if you do KDVD :!:

Trust me, we don't.
Mencoder has only ONE denoiser, equivalent to convolution3D or deen. He has NO temporal only denoiser.

If C3D was abble to do ALL the jobs we need in avisynth, we would have drop all others since a long time. Did we ?

Do not think that because Kwag does or tells something, there is no other way anymore.
Two months ago the only words that he could tell was ffvfw :-). He is just like a kid with a new toy :-D

They are all in sticky post (guide from Vmesquita if I remember well and look at packshot, the tool done by Inc taht will help you to start easily).

I do agree in case of avisynth, as avisynth filters are much more developed (ok that hq3dn is really good on really noisy sources like caps where you have to rise the temp threshold a lot) and there are much more filters.

I didnt tested Karls new filtering routine on mencoder. But is it really luma adaptive? I dont know so I do just ask.

The mega pro on avisynth is still that you can generate complex routines in a really script syntax way. So for shure on tricky capture sources like bad converted to 25fps by the broadcast station I do still need avisynth using for example restore24() or unblendpattern().

:wink:

But for generaly good source encodings like DVD sources the filters of Mencoder really do a more than good job if we set up them right.

"You" referes to many. I didn't say that. I said "" I " moved over to mencoder ;)
And yes, as dialhot said, I suggest you do a lot of reading, because mencoder is really a very complex tool.

@Phil,

I don't know why you say that Phil, because the reality (in my case), is that I have already done at least 10 encodes with the latest parameters, all KDVDs 704x480 and one KSVCD at 352x480, and I have no issues :!:
So I think mencoder is not really an "alpha stage" encoder. It's beta stage, but the problem is really the amount of settings it has, and I like that :D It has so many options, that it's complex to understand. About the "noise" trick" to maintain low bitrate, I see no problem with that at all.
But as I said in another thread, 3th seems too strong at lower resolutions, and must be adjusted.
And I'll say it again, after I've seen the results of all my currently encoded movies, there's just no way for me to turn back ;)

-kwag

I mean underflow problems mainly. And peak burst also.
Two points that does not give problems on your standalone but that make mencoder not being a reliable encoder. Because "who knows..."...

It's a little like if you have an encoder that can't do MPEG2 in GOP shorter than 25. If 25 fps is okay on your standalone despite the fact that is not in the DVD standard, you can still use this encoder _for yours jobs_. But will you consider this encoder as reliable for KVCD.net ?

The problem is that a software that is not abble to certify the respect of min and maxbitrate can't be qualified as "video encoder". Till then, it's nothing but an alpha "video stream producer".

Sorry to disappoint you but : 1/ I see it A LOT even on DVD res (did you try to do a job with and without the noise, with no concern for the underflow problem, just to compare ?)
and 2/ somethign that is so noticiable at 544*576 can't be absolutly unoticiable a 704 :!:

How much time you worked on CQMatic before to realise that what you wanted to obtain (and was sure to obtain) couldn't be performed ?

Let's take an appointement : unless the minrate problem is solved in the next weeks, you will stop to use mencoder.

See ya :-)