New filter: NoMoSmooth

[SansGrip]

I just uploaded 0.1a (http://www.jungleweb.net/~sansgrip/avisynth/NoMoSmooth-0.1a.zip) (and source (http://www.jungleweb.net/~sansgrip/avisynth/NoMoSmooth-0.1a_src.zip)) to my web site which fixed the (wouldn't you know it) off-by-one bug that caused an access violation when height > 464.

[OUTPinged_]

You mean 17.3 without NoMo and 7.1 with it? What other filters are in the chain with those results?

No filters at all. Only Lanczos3 resize.

But how does it look compared to the source?

Well it looks same except no noise :-)

Huge radius makes me happy.

Fast tool with huge temporal thresh and no ghosting makes me even more happy. Like that:

^______________________________^ (c)Manne

[SansGrip]

Fast tool with huge temporal thresh and no ghosting makes me even more happy.

Ummm... What tool? :)

[MaTTeR]

Wanted to setup an encode while I slept tonight but can't get my script to work for some reason-

mpeg2source("D:\apost.d2v",iDCT=2,cpu2="oxoooo",moderate_h=55,moderate_v=75)
crop(4,4,712,472)
Lumafilter(-1)
NoMoSmooth(40,1,6,1,3,false)
convolution3d(0,0,1,0,5,2.8,0)
Unfilter(5,5)
BicubicResize(512,380,0.333,0.333)
undot()
Limiter()

Maybe I'm just too tired to see my mistake but I'm getting unrecognized exceptions when opening the file:confused:

Edit: Maybe I jumped the gun a bit and assumed this was YV12 capable since I seen mention of it earlier in the thread. Ooops, well you know what they say about people assuming...

[SansGrip]

Edit: Maybe I jumped the gun a bit and assumed this was YV12 capable since I seen mention of it earlier in the thread. Ooops, well you know what they say about people assuming...

You need the specific YV12 version of NoMoSmooth, which you should be able to find attached earlier in the thread. It was mainly intended as a testbed for porting to YV12 and is somewhat limited, but it works for me.

If you're using the correct version and still get an access violation, I'll try to duplicate it and figure out what's going on. I'm probably going to be rewriting it anyway since 0.1a (currently 2.0/YUY2-only) has some changes I'd like to include in the YV12 version.

On a positive note, FluxSmooth 0.2 includes a 2.5/YV12 DLL identical in every respect to the 2.0/YUY2 version. I'd love to hear from 2.5 testers regarding the stability etc. of my YV12 ports.

[MaTTeR]

Got it, as a last ditch effort I created a new script file and for whatever reason it worked. I've had this rare problem for the past few months and have yet to figure out why. Oh well...

Starting the encode now and anxious to wake up and see the results. Nice to see your YV12 ports have started trickling out, seems it didn't take you long to figure it out;) Many thx.

[SansGrip]

Got it, as a last ditch effort I created a new script file and for whatever reason it worked.

Weird. I find YV12 stuff very sensitive to frame size, maybe it was something to do with that.

Nice to see your YV12 ports have started trickling out, seems it didn't take you long to figure it out;)

It's pretty easy to grasp (actually easier than a packed format like YUY2), and as long as you're not working with many pointers pretty easy to port. In NoMoSmooth, unfortunately, I'm working with many pointers ;).

[drebel]

Always nice to hear about the evolution of NoMo, but also rather sad because it's keeping you away from my favourite blockbuster(saved my life after more than 20 attempts to encode PANIC ROOM -R2, a very dark and badly remastered DVD at low bitrate,plenty of blocks.)The line...


Blockbuster(method="sharpen",block_size=3,detail_min=1,detail_max=100,luma_offset=-2,luma_threshold=100,strength=20)

...really made the difference!Of couse,there's a lot to say about all other value settings,but it would be absolutely great to have this irreplacable filter in YV12 port...

regards,
george

[MaTTeR]

Originally posted by drebel
but also rather sad because it's keeping you away from my favourite blockbuster(saved my life after more than 20 attempts to encode PANIC ROOM -R2, a very dark and badly remastered DVD at low bitrate,plenty of blocks.)The line... I totally agree man, one of the most disappointing mater jobs I've seen on a new release. Now they have the nerve to release a SuperBit version of it *sigh*

SansGrip,
Ran full 2-pass with NoMo last night and I must say it looked very nice. The speed was certainly acceptable IMO. I really like the concept and suspect the low action source I used to test with didn't do the filter justice. I think I still prefer BlockBuster myself but havent tested it muc lately due to me completely switching over to YV12 methods. I'll test NoMo some more for now. Nice work!

[SansGrip]

Of couse,there's a lot to say about all other value settings,but it would be absolutely great to have this irreplacable filter in YV12 port...

Well, given that the Flux port went so smoothly and the NoMo port is at least usable, I think my YV12 to-do list is now:

1. Blockbuster
2. NoMo
3. The rest ;)

[SansGrip]

I think I still prefer BlockBuster myself but havent tested it muc lately due to me completely switching over to YV12 methods.

That's a pretty big step, but I guess most of the "essential" filters are ported now (except for Decomb, which I would miss greatly).

Ok ok, once I've coded up a quick test of an idea I had last night I'll return to Blockbuster and see if I can persuade it to be YV12-friendly ;) :p.

[drebel]

Once you have the filter converted,I would like very much to discuss
some of the "weak points" that could cause heavy artifacts(i mean visually,i'm not a coder..),as i 've played around with almost EVERY setting of that line.
Keep up the good work(...or else we're in a big trouble).I missed your site-it's down for more than two days.

regards,
george

[SansGrip]

Once you have the filter converted,I would like very much to discuss some of the "weak points" that could cause heavy artifacts(i mean visually,i'm not a coder..),as i 've played around with almost EVERY setting of that line.

Cool, let's discuss them now! But in the Blockbuster thread (http://forum.doom9.org/showthread.php?s=&threadid=37135)... If it means any significant changes I'd rather implement them first, then port to YV12.

I missed your site-it's down for more than two days.

That's really weird, because most people are still able to access it. Could you do me a favour and PM me a traceroute to www.jungleweb.net? I'd like to know where the problem is at.

[MaTTeR]

Anyone else seeing the flashing white line at the top of the encodes? I'm just using the defaults and seen it happen on 2 different machines with 2 different sources.

[SansGrip]

Anyone else seeing the flashing white line at the top of the encodes? I'm just using the defaults and seen it happen on 2 different machines with 2 different sources.

I've not seen that. What were the dimensions of the sources? Is this the YUY2 or YV12 version?

[DarkNite]

I get white lines on the top, bottom, and left borders in both vdub preview and finished encode. I'm using avisynth 2.5 (a_251102), mpeg2dec3 v0.93b and NoMoSmooth yv12 0.0c

LoadPlugin("H:\mpeg2dec3\mpeg2dec3.dll")
LoadPlugin("H:\TomsMoComp\TomsMoComp.dll")
LoadPlugin("H:\NoMoSmooth\NoMoSmooth.dll")
LoadPlugin("H:\asharp\asharp.dll")
mpeg2source("H:\X_VOL1\EP0\vts_06.d2v",iPP=true,idct=2,cpu=4)
TomsMoComp(1,9,1)
crop(10,0,702,480)
LumaFilter(+5,1.1)
NoMoSmooth(30,2,6,2,3,false)
BilinearResize(640,480)
Asharp(1,3,1,true)

On a positive note:

Your FluxSmooth is working wonders for me as we speak. :D Thank you for your hard work, it is appreciated.

[MaTTeR]

Originally posted by SansGrip
I've not seen that. What were the dimensions of the sources? Is this the YUY2 or YV12 version? Actually I noticed they happen on the top and bottom also.

crop(4,4,712,472)
Lumafilter(-1)
LanczosResize(608,344)
Undot()
Limiter()

This is the YV12 version and I tried various MOD-4 resolutions along with different cropping variables. Nothing seemed to help for some reason.

Edit- The confusing thing for me is I don't understand why I never noticed this before on previous encodes.

[SansGrip]

I get white lines on the top, bottom, and left borders in both vdub preview and finished encode.

Eek. It must be a bug in the edge-handling code. I'll take a look at it tomorrow and post a fix.

Your FluxSmooth is working wonders for me as we speak. :D

Yes, I think that one's my favourite too :). I'm currently attempting to port it to SSE, so the next release should be significantly faster.

[DarkNite]

I'm currently attempting to port it to SSE, so the next release should be significantly faster.

That's music to my ears.

[OUTPinged_]

SG, did you dump NoMoSmooth or we can expect more versions in the future?

YV12 version of 0.1a i.e. :-)

[SansGrip]

Originally posted by OUTPinged_
SG, did you dump NoMoSmooth or we can expect more versions in the future?

YV12 version of 0.1a i.e. :-) Well that's a possibility. I have no idea how many people actually use it though :).

[OUTPinged_]

It is really better than FluxSmooth for sources with heavy temporal noise. It leaves a more cleaner picture behind.


Now as I am trying YV12-only encoding (didnt get any fps increase hehe) and i seem to be separated from my favorite temporal filter :-(

[SansGrip]

Originally posted by OUTPinged_
Now as I am trying YV12-only encoding (didnt get any fps increase hehe) and i seem to be separated from my favorite temporal filter :-( Well, we can't have that, now can we? :D

I think I can chuck out a YV12 version pretty quick. It won't be MMX-optimized, though -- I'll wait for another release to do that. Stay tuned :).

[OUTPinged_]

btw, why not implement that FluxSmooth's ability to "detect fluctuating pixels and compensate their value changes" for NoMoSmooth as an option? It would be an interesting experience to check if it will improve an output.

[SansGrip]

Originally posted by OUTPinged_
btw, why not implement that FluxSmooth's ability to "detect fluctuating pixels and compensate their value changes" for NoMoSmooth as an option? Well, NoMo and Flux are really just two different ways to skin a similarly coloured cat. Flux's "fluctuation detector" is basically just a technique to try to determine what's noise and what's motion. NoMo already does this, using another technique.

So adding a fluctuation detector to NoMo wouldn't achieve a lot, since in theory it should already have figured out what's motion and what isn't.

[iago]

@SansGrip

Like many other people (I guess), I'm also waiting for a new version of NoMoSmooth! ;)

iago

[SansGrip]

Like many other people (I guess), I'm also waiting for a new version of NoMoSmooth! ;)

hehehe ok ok, you guys have convinced me :D.

[iago]

That's good news pal! ;)

[iago]

@SansGrip

Btw, to speed up the process of your releasing a new version of the filter, I will report the results of my full 2-pass encode with the following script in a short time: ;)

------------------------------------------------
LoadPlugin("C:\FILTERS\mpeg2dec2.dll")
LoadPlugin("C:\FILTERS\NoMoSmooth.dll")
LoadPlugin("C:\FILTERS\LegalClip.dll")
mpeg2source("D:\MOVIE\MOVIE.d2v")
crop(12,20,696,536)
BicubicResize(576,304,0,0.5)
NoMoSmooth(30,2,6,2,6)
LegalClip()
----------------------------------------------------

regards,
iago

[iago]

Hehe, what about this one? ;)

Imho, this filter doesn't deserve its current state of oblivion! ;)

best regards,
iago

[SansGrip]

:D

You know, it's because I've not used it recently. When I use my filters I'm always thinking of ways to improve them.

Hopefully I'll get some time to look at optimizing this one. I think I might try the method Sh0dan posted in the C3D thread (i.e. preprocessing to avoid having to monkey around with different frames and offsets).

I'll let you know if I make any progress :).

[Wilbert]

Hi,

Did you recompile this filter already, so that we can use it with AviSynth v2.5 ?

[AmiRage]

Originally posted by Wilbert
Did you recompile this filter already, so that we can use it with AviSynth v2.5 ?
SansGrip doesn't seem to be around at the moment. His last posting is nearly 12 days old now.

BlockBuster too needs to be updated. :D

[drebel]

Any news about porting this great filter to avisynth 2.5 Sansgrip?
We 're all looking forward to this version,you know...:)

regards,
george

[sh0dan]

Sansgrip: "Last Post: 22nd January 2003 14:00". I doubt you'll get an answer - you could try emailing him, if he enabled that.

[Valky]

there is nothing wrong using Blockbuster with avisynth 2.5b. Just find the latest version.

And Sansgrip is alive in other forums..maybe pissed off to this one..dont know really :)

Anyway..he is doing a great job with his filters and I hope he gets hang of things with de-noising too.

[drebel]

...mpeeeep.Wrong answer.The topic is NoMoSmooth.:p
I would try to get in touch there if i knew the places...

regards,
george

[Wilbert]

For those who are interested: I compiled a version for AviSynth v2.5.

http://www.geocities.com/wilbertdijkhof/NoMoSmooth_v01b.zip

Of course, YUY2 is required.

[digitalman]

Thanks!!!