No :cry:
If it's an action movie, you only have two choices: Either use a lower resolution and put it on one disk, or go for KVCDx3 (or even 704x480(576) ) but target for two CD's. With the new script and techniques, you should be able to put just about any movie on two CDs. No need for three ;)

-kwag

OK, that's what I guessed... :? I did just that - targeted the movie for two discs and got a CQ value around 63 (I don't remember exactly)... But hey, to fit a movie onto two discs ain't too shabby. Especially when it look almost identical to the DVD! :D

That clip kwag, that clip... AWESOME!!! 8O
I guess I'll have to start all over with my encode as soon as I get off work. It'll be SO worth it!
I'm amazed at how fast things are moving and changing on this forum. Who would have guessed that a VCD could look this good - ever! :lol:

VCD :?: What's that :mrgreen:

Sorry if I offended you kwag! :wink: What I meant was KVCD - of course! :D

Just kidding :mrgreen:

Makes me wonder, how much time we can really get now with KDVD and this script, and also KVCD ULBR (or LBR ) :idea:

-kwag

@kwag
Have you slept at all last night? You must have been up testing and tweaking, right? I went to bed at 2 p.m. and when I logged on this morning I saw the goodies! Great!

I really didn't get that much sleep last night. So here I am, in bed typing in my iBook via wireless 802.11b network :D
And now I'm going to bed. Let the scripts rest (for some centons) :mrgreen:

Have fun!
-kwag

Sweet dreams, kwag! :wink:

:(

Kwag my friend,
something is wrong with my sample in the new script.
( June 5, 2003 @05:45GMT )
i got CQ70,297 in 480x480 but the image is very "smoked"(blurred)
and with big staircases in thin lines.... :!:
with 704x480 the CQ is too low.

:cry:
"sniff"

Hi Jorel,

strange...I did a view samples on 5 different movies and different
resolutions, and they all came out sharp as a knife (maybe almost a little
to too sharp for my eyes)

and hey Jorel don't "sniff", I'am sure the master himself will lend you
a helping hand... :wink:

regards, ***mfb***

No mention of negative values being blurs!

Using Subtract, I saw that T < 0 blurred more until T=-1 but then made no further differences no matter how negative I made it.

Is it just luck / bugs that make T<0 blur the image?

I know :!: I found out because I thought it would, and indeed it did :D
I couldn't use BlockBuster(blur) because it didn't blur enough. I also tried another filter ( forgot now which! ), but only scaled in steps of 1, so that was a no no. So asharp used "in reverse" :lol: made our day :mrgreen: Another nice "Feature" :wink:

-kwag

hehe some day i really must install VC++ and write that MotionAdaptiveLumaBlurWithNoBugs() plugin :wink:

LOL :lol:
That's a good one :D

-kwag

While you're at it, please write a "AvoidMosquitoesAroundCartoonBorders()" filter :)

Minima change
 

Just made a minimal change to the script:

Changed asharp(2,4,0.25,hqbf=true) to asharp(2,4)
Changed MergeLuma(blur(0.1)) to MergeLuma(blur(0.2))

The result is sharper picture and lower file size.
Apparently "hqbf" method is still not very well optimized.
Also speed increased 5 seconds for every minute.

-kwag

Hi kwag...

I made thousands of samples today, and the script got better constantly... still haven't tried the VERY latest script ( :wink: ) with asharp(2,4) and MergeLuma(0.2)...
However, as the picture quality gets a lot better, there's still one scene in my movie, where I think Blockbuster noise would REALLY help a lot...
It's a very dark rain scene, and DCT blocks show up, and ugly artifacts all around the fast-moving rain-drops... this doesn't seem to get better, but in case worse, the more we apply sharpening... :cry:
any suggestions?

Hi Jellygoose,

Last night I played for about 2 hours, integrating BlockBuster(noise) into the script. I was able to make the variance adaptive :), but at 704x480, BlockBuster really doesn't help :!:
This was confirmed a long time ago by SansGrip, and I can confirm the same thing. Somehow, TMPEG's CQ mode can't "see" the noise correctly. You can see the noise clearly by loading the .avs in Vdub, but in TMPEG it's almost gone, and you have to use very high value for variance which then spoils the picture. So we have to find another way to deal with that :!:

Edit: I know this shouldn't make a difference, maybe it does!, but could you code that scene with a higher MIN bit rate and see if the DCT blocks dissapear :idea: This is something I've had on on my queue list to try, but haven't got to it yet :!:

-kwag

I'll give that a try right now, thanks for the tip kwag! :D

Edit: However, since it was last tested a long time ago, I'd like to give that a try too! remember CQ_VBR did beat CQ a long time ago too... :wink: TMPGEnc has changed maybe, so if you don't mind sending me the part of the script with adaptive Blockbuster variance, I'll give it a shot!

Sure :!: :D

Here you go:

First define these lines, right after the MaxTreshold line. Like this:

Now add this lines AFTER the scene detection line:

ScriptClip("bb_noise && nf > 0.001 ? BlockBuster(method=bb_method, detail_min=1, detail_max=6, variance=((1/nf)*8 ), seed=0) : \
BlockBuster(method=bb_method, detail_min=100, detail_max=100, variance=0, seed=0 ) ")


That's it :D
Play with the "8" in the variance, and also the detail_min. :wink:
If you don't want BlockBuster, you don't need to delete the functions :!: Just edit bb_noise=True to read bb_noise=False

Enjoy!,
-kwag

Much appreciated, thank you KleverWag... 8)

Ok, I raised the Min. Bitrate Value to 450, which is VERY high in my eyes... however, I don't see a difference in picture quality compared to the 100 kb min. Bitrate that I use... :cry:
I still see that the current script, seems to enhance artifacts around objects for some reason... well it's a matter of taste maybe... I'll try to play a little around with blockbuster and aSharp... if you're interested in the results just drop me a PM... :roll:

BtW: I just ordered myself the Cyberhome DV-CH 505 Player, to see if that wonderful picture that this player's supposed to have is for real... Well even if not, the player was a bargain for 105 Euro's, and it looks sooo cool 8) here's a pic: http://cgi.ebay.de/ws/eBayISAPI.dll?...&category=8329

Yep, you're right. I even did a test at 10,000Kbps constant bit rate on some special dark gray scenes, and DCT blocks are present. It's not a bitrate related issue :roll:

-kwag

Well I'm positive that it is always source related, although you might not see it at all in the source... I know of movies that I encoded myself, with very similar dark scenes with fog and rain, and DCT blocks did not show up at all on my backup...

Edit: I know this didn't help at all, but I just wanted to say something :lol:

Haven't had any luck with Blockbuster either, to get rid of those blocks... It seems pretty difficult to adjust the noise in the adaptive script...
I actually thought that blockbuster was already kind of adaptive, because noise was only added to areas where detail was below a certain value. so now the amount of noise added to those areas is linear adaptive right?
well are the values you posted your standard values?
Very agressive, as far as I can tell... I tried to lower the amount of noise by changing the 8 into a 5... am I on the right track? :roll:

I'm using the latest script, but for some reason my letterboxing is not working..here is the script from tok.

## DLL Section ##
#
LoadPlugin("C:\Filters25\MPEG2Dec3.dll")
LoadPlugin("C:\Filters25\STMedianFilter.dll")
LoadPlugin("C:\Filters25\UnFilter.dll")
LoadPlugin("C:\Filters25\asharp.dll")
LoadPlugin("C:\Filters25\undot.dll")
#
####

## Defined Variables and Constants ##
#
MaxTreshold = 1.50
scd_trigger = 15 # Scene change trigger value.
nf = 0 # Current frame.
#
####

## Main section and static filters ###
#
Mpeg2Source("C:\DVD\longkiss.d2v")
#
undot()
Limiter()
asharp(2, 4)
BicubicResize(352,240,0,0.6,8,0,704,480)
STMedianFilter(8, 32, 0, 0 )
MergeChroma(blur(MaxTreshold))
MergeLuma(blur(0.2))
#
#

## Dynamic Linear Adaptive Filtering and Scene Change Detection ##
#
# ( Portions from AviSynth's manual ) - This will apply temporalsoften to
# very static scenes, and apply variable blur on moving scenes.
# We also assign a variable - and this is why a line break is inserted:

ScriptClip("nf = YDifferenceToNext()"+chr(13)+ "nf > 2.5 ? asharp( -(fmin((nf/35), 1)), 0 ) : \
TemporalSoften(2,7,7,3,2) ")

#
# Scene change detection ( kwag ) - If a scene change is detected, we
# blur heavily. This affects the scene before and the one after the
# scene change, thus providing a softer transition for the encoder instead
# of a sharp "spike".
# If it's not a scene change, then we just blur dynamically, depending on
# the action.

ScriptClip("nf > scd_trigger ? asharp( -2,0) : asharp( -(fmin((nf/35), 1)), 0) ")

#
#
#

#LetterBox(16,16,16,16) # Depends on situation. Use MovieStacker!
#AddBorders(0,0,0,0) # Depends on situation. Use MovieStacker!
Limiter()

#
#
## Functions ###

function fmin(float f1, float f2) {
return (f1<f2) ? f1 : f2
}

#
####
AssumeFPS(23.976)
LoadPlugin("C:\TOK\ToK_EXTRAS\Sampler\Sampler-2.5.dll")
oldfps = framerate
interval = round((FrameCount/24)/59.940)/10
nFrames = round(24)
SelectRangeEvery( (round(framecount/interval)),nFrames)


David

Shouldn't it be :?:
Racer99

Yep your right :D ..just tested it out and its working again..thanks


David

Hi Tenra,

I've been playing with your script, and I have seen the horizon :mrgreen:

I just tried this:

Just to verify that indeed asharp would apply to the specific quadrant. It works :!: :mrgreen:
Now we just need to grab the YDifferenceToNext function to actually return ONLY the corresponding quadrant from the following frame. If this is possible, we're gonna be rocking :mrgreen:

-kwag

@ Tenra
Nice result , man , Your script will give us new addaptive filter in very soon future :lol: :lol: :lol:
@Kwag
Script rocks and results are cool too but are sure that deviding frame for 4 quadrants is enough ???
I think For battle scenes with many moving parts it'll be just not enough to get same effect as in the pictures above .
Maybe it makes sence to make more quadrants : lets say 16 or even 25 ,36 ....
So we can blur just small part of whole frame and sharpen the other pars :?: :?: :?:
Or maybe to make it flexible , to be dinamic number that will change according the movement on frame : more moveing parts bigger number and still picture just 4 .
It probably be not easy to program this kind or script but with our " Brilliant " minds I think it's quite possible to get .
Sorry for long blah,blah but when I see progress of this very same tread I get more appetite (I hope i wrote right)
Regards
bman

On some sources I've found that filesize can grow when adaptive filtering is applied. Encoding a fairly low movement - mostly people talking - AVI source at 480x480 my test samples grow by about 1.2Mb out of 50Mb when adaptive filtering from the latest optimal script is applied, where other higher action sources shrink by a similar amount, all compared to base non-adaptive filtered encodes.

Anyone else noticed this or have I stuffed the tests?

Here's the dynamic part of the script. I know it looks different to Kwag's but the filters applied to each frame should be the same.

On some sources I've found that filesize can grow when adaptive filtering is applied. Encoding a fairly low movement - mostly people talking - AVI source at 480x480 my test samples grow by about 1.2Mb out of 50Mb when adaptive filtering from the latest optimal script is applied, where other higher action sources shrink by a similar amount, all compared to base non-adaptive filtered encodes.

Anyone else noticed this or have I stuffed the tests?

Here's the dynamic part of the script. Anything wrong?

Hi Girv !
Did u compared clips resulted yours and Kwag's script on the same source by size and visual quality ???
Did u tested DVD sources too ???
bman

sorry if this was already mentioned in this long thread but has anyone tried the Motion Adaptive Mixer by MarcFD :?:

from the readme: It looks like this is exactly what we want to do :!:

@ rendal

It could be useless in avs 2.5 :cry: :cry: :wink:
bman

I already tried that MAM filter a long time ago with avisynth 2.07 and the quality was poor... It took extremely long and I remember I was really surprised how bad the result actually looked... :cry:

The reason is that on very low movement scenes, there is no blur applied at all :!: Only TemporalSoften.
But on the full encoded film, the total file size should be smaller than without the adaptive filtering. Unless the complete movie is a drama that there's barely any action :roll:
If that's the case, then I would lower the line:
"nf > 2.5 ?"
To read:
"nf > 1.0 ?"
So that bluring starts at a lower activity.

-kwag

Well my friends, my quadrant adaptive motion tests are over, at least for some time :roll:
I did it, but the result is unacceptable. I divided the screen in 32 quadrants, and applied the same filters that are on the current script to each quadrant.
The result in an encoding speed is 1 second every ~1 minute, 30 seconds on my P4 @1.6Ghz 8O
So obviously, this is a no no situation. So the current script is about as far as we can go, that is, we can add more stuff but on a complete frame by frame basis. Forget about slicing each frame :!:
Now I'm going to look at ren's recommendation on Motion Adaptive Mixer and see what it's all about. The description looks like it would fill in some gaps. So I'll take a look at that now.

Edit: MAM is a 2.0x filter. Bye! :x

-kwag

I already thought that it would take a LONG time to do all these kinds of calculations!!
I think we're already pretty well-off with the current script... However I'm still searching for a way to get rid of artifacts around objects and DCT Blocks in dark areas...
I know it's not bitrate related, because they're visible in every resolution I tested... :?