MSmooth for Avisynth 2.5

Hi Donald, Just a quick question or possible bug. When I'm using the strength parameter the speed drops a lot. I know in the readme, you state that it would, but what I'm finding is that there's a large difference (13 vs 3fps) when I do: Msmooth(threshold=11) -> 13fps vs Msmooth(threshold=11,strength=3) -> 3fps Since strength=3 is the default (according to the readme), I would assume they should be the same speeds. I can only get the same speeds while including the strength parameter when using strength=0. Do you have any ideas on this? Thanks, Mr. B

My testing shows identical timings and the code is definitely defaulted to strength=3. I can think of only two possibilities: 1) you have an msmooth.def that overrides the defaults, or 2) you just did things late at night and got confused. :-) But seriously, are you sure??? When you leave off the strength parameter are you getting smoothing (strength=0 passes the video through untouched)?

@Neuron 2 things about latest msmooth : - high value for strength seem to strangely affect chroma - high threshold seem to show a problem with borders 3 pictures (see attached file) pic0 : strenghth = 2, threshold = 2 pic1 : strenghth = 25, threshold = 2 pic2 : strenghth = 25, threshold = 200 my script : ----------- LoadPlugin("C:\video\avsfilters\yv12\MPEG2Dec3.dll") LoadPlugin("C:\video\avsfilters\yv12\Msmooth.dll") mpeg2source("F:\test\vts_01.d2v",cpu=0,idct=2) Crop(20,72,680,432) msmooth(strength=25,threshold=200) bicubicresize(448,320,0,0.6) AddBorders(16,128,16,128) Regards, FuPP

@FuPP Thank you for your feedback. A blur cannot be applied at the edges because neighboring pixels are unavailable, so I copy them over from the source. For reasonable strengths (not 25!), you don't notice it. I don't get your chroma point. But anyway, suppose I said: "Noticed problems with my car. With high RPM (20000 rpm) the engine gets real hot. With watered down gas, the engine runs rough." :) Why in heaven's name would you want to run MSmooth with a strength of 25 and/or a threshold of 2 (or 200)?

I allways do that kind of tests in order to accentuate consequences of a possible bug, which are sometimes less noticeable with default or soft settings. These settings are therefore only for testing purpose. about chroma : I've just realised that pictures I attached are in the wrong order compared to the description I gave : pic0 (=msmooth0.jpg) : strenghth = 2, threshold = 2 pic1 (=msmooth2.jpg): strenghth = 25, threshold = 2 pic2 (=msmooth1.jpg): strenghth = 25, threshold = 200 if you compare msmooth0 and msmooth2, you should see that picture msmooth2 is more "green" Regards, FuPP.

I notice the "green-shift", but I notice aswell that these are two pictures with different horizontal resolutions. And they show a different content aswell :P IMHO you can make decisions easier when you use the same source/picture. Haven't made tests for myself yet, so I can't confirm nor deny anything. CU, lamer_de

I can't duplicate your chroma result. Please provide a one-frame HUFYUV clip that demonstrates the alleged problem. I think my car has a bug. When I drove it into a wall (just to test for possible bugs), it stopped working! :)

ok, forget it; I'm going to drive another car. :) Best regards, FuPP.

When I used msmooth the video had a small green tint to it (anime). But it did clean up the raw well.

Maybe you can provide a one-frame clip for me to download that I can use to see the problem? FuPP gave up on me. :( Was your source RGB or YV12? Also please post the script. Thank you.