nomosmooth
 

hey where can i get this dll file from??? :D

Re: nomosmooth
 

See my sig ;).

While watching The Amazing Race I had a very good idea to improve motion detection: temporal smooth before the detector runs, instead of after. This way you eliminate noise first and can use a lower motion_threshold before getting false hits.

Some brief experiments show I can drop motion_threshold down to 30 before I get a similar number of false hits as before at 40. It might be the case that 30 is too sensitive, and that spatial smoothing would occur in areas where motion is not pronounced enough.

Anyway, that's the status right now: I'm trying to figure out an efficient way of temporally smoothing before detection. In theory it shouldn't be too much slower than the old method.

Hi SansGrip,

Would this imply a change on your default settings on the NoMoSmooth filter?

-kwag

I'm not sure. I'll think about defaults when the code works ;).

New version 0.1a
 

Here's NoMoSmooth 0.1a for y'all to try, as well as the source for y'all to look at should y'all so desire.

It's a total rewrite with a number of algorithmic improvements, so it should now be faster. Brief tests indicate it might even be slightly quicker than Convolution3D(preset="movieHQ"), at least on my system.

I added a simplistic "noise detector" which seems to help reduce temporal smoothing of important and very-noticible-if-missing details such as in skin tones.

This is the first official release, though I'm still classifying it as alpha until it gets more testing and I get more feedback.

Hope this works as good for y'all as it does for me ;).

In the end I didn't keep this change to the motion detector, since tests revealed it was both 2-3 times slower and destroyed slightly more details than the old version.

Some of the defaults did change for 0.1:

motion_threshold=40
temporal_radius=1
temporal_threshold=6
spatial_radius=1
spatial_threshold=3

These seem fairly suitable for relatively clean DVD sources.

Hi SansGrip,

Thanks :D
Giving it a try right now.

-kwag

Just got a bug report on Doom9 that it crashes if height > 462. I'm looking into that now.

I was testing at 352x240 with the LBR. No problems there.

-kwag

I just uploaded the bugfix and edited my previous message to reflect the new filename.

hey SansGrip,the link don't work! :(

This one works for me...?

sorry friend,this not work too! :( :(
waiting.......click in every minut....no work.

Hi jorel,

It works for me. Maybe the route to SansGrip from your provider is down. Go here: http://www.webwarper.net and from there, access his link. It's a web based anonymous proxy ;)

-kwag

Hi SansGrip,

SansGrip wrote:
Are these the default settings for NoMoSmooth() or should we use
NoMoSmooth(40,1,6,1,3) :?: NoMoSmooth is very slow. My encode
went from 6hrs to 17hrs. Is this due to the old default settings :?:

Thanks

-black prince

Yep, those are the values used if you don't specify any parameters.

You might find the new defaults a little faster (because of the lower radii), but it is very slow. You might find FluxSmooth performs better because it's simpler, but neither of them have any assembler/MMX/SSE optimizations yet, mainly because I need to learn it first :).

Hi SansGrip,

Kwag uses both NoMoSmooth and FluxSmooth. Is this the best way
or should I replace flux with NoMo. It's getting confusing and changes
are comming quicker than I can keep up with. :!: I changed my
avs scripts more than 15 times with NoMo, flux and blockbuster and
I'm still not sure what's the latest and the best settings :?: I'm
going to wait awhile until the testing settles down and there are
some final settings to work with. :)

-black prince

Technically Flux is (sort of) NoMo without motion detection. I'd have to think about how they would interact with each other.

Is anything ever final in this hobby? ;)