Can Avisynth save this?

[helplessandlost]

Can't fire the Videographer (it's my wife). First time she shot in low light and for some ungodly reason she turned off the auto-iris and for obvious resons, Murphy's law, it wasn't set at "open" so the footage in it's current state is pretty useless.

This shoot was for a good friend/collegue so I'd really like to save some of the footage. Here is a 5 sec clip ~107 MB if anyone can help!

http://www.sendspace.com/file/vmbspa

A screen grab if that is sufficent to diagnose:









Thanks!

[helplessandlost]

and if it helps this is more what it should have looked like - we were at opposite ends of the stage

[Emulgator]

Just for kicks: some adjustY, ColourYUV with spread cont_u and cont_v and MCTD high to denoise afterwards:
4:20 min per frame... MCTD medium around 20s per frame.

[Reuf Toc]

You can also try HDR AGC Plugin : link
As Emulgator said, your footage may need a denoising afterward

[helplessandlost]

engrish pls (i.e. script examples)

[Emulgator]

The HDR AGC version with MCTD:
This is not bad, faster than my version, but maybe a bit more noisy; around 0.25 fps.

......sourcefilter.....
HDRAGC(shift=16, reducer=0.5, max_gain=4.0, coef_gain=1.5)
MCTemporalDenoise(settings="medium", deblock=false, interlaced=false, chroma=true, sharp=true, strength=300, GPU=true)

Now my sloooow version (this is by no means useful or efficient, too many conversions, but gave a picture):

....sourcefilter...
ConvertToYV12#(interlaced=true)
ColorYUV(cont_u=400, cont_v=400, off_u=-1, off_v=2, analyze=false, showyuv=false)
ConvertToYUY2
adjustY("spline(Y, 0, 0, 8, 0, 16, 11, 20, 16, 55, 90, 70, 140, 90, 180, 250, 220, 255, 235, true)", false)
ConvertToYV12
MCTemporalDenoise(settings="medium", deblock=false, interlaced=false, chroma=true, sharp=true, strength=300, GPU=true)
#MCTemporalDenoise(settings="high", deblock=false, interlaced=false, chroma=true, sharp=true, strength=400, GPU=true)#only if you can afford to wait, maybe never returns...nah, throw it away, this is ridiculous, it never returns a picture, gone fishing...

Best is to separate into 2 Passes, first pass for ColorYUV and adjustY together,
the second pass for MCTD alone. Now you may try "high"...

[helplessandlost]

Thanks Emulgator, let me ask for clarification. Are you saying in your edit that your "slooow" script is useable if I run it in two passes?

So pass 1:

....sourcefilter...
ConvertToYV12#(interlaced=true)
ColorYUV(cont_u=400, cont_v=400, off_u=-1, off_v=2, analyze=false, showyuv=false)
ConvertToYUY2
adjustY("spline(Y, 0, 0, 8, 0, 16, 11, 20, 16, 55, 90, 70, 140, 90, 180, 250, 220, 255, 235, true)", false)

Pass 2:

ConvertToYV12
MCTemporalDenoise(settings="medium", deblock=false, interlaced=false, chroma=true, sharp=true, strength=300, GPU=true) < set for either medium or high

[helplessandlost]

And another dumb question

### /!\ Needed filters: MVTools (v2.5.8), Masktools (v2.0a36),
### ------------------- LSFmod (v1.9), FFT3Dgpu (v0.8.2.7) or FFT3Dfilter (v2.1.1),
### TTempsmooth (v0.9.4), Removegrain + Repair (v1.0PR),
### Deblock (v1.2), Deblock_QED (18.aug.2008), DctFilter (v0.0.1.4),
### EEDI2 (v0.9.2), Sangnom (v1.0beta),
### GradFun2DBmod (v1.5), Gradfun2db (v1.0), AddgrainC (v1.4).


I can't find some of these versions that are being asked for this auto script. Is there a specific place to find them?

[Didée]

Which ones?

The reason that settings="medium" works and settings="high" not is simply memory related. "medium" does a normal clip.MDegrain (twopass=false), where "high" does clip.MDegrain.Mdegrain (twopass=true). The difference seems rather harmless, but in fact the twopass method causes HUGE memory requirements, in particular with Full-HD.

Instead of using the most huge hammer you can only find, I'd rather try to use a standard MDegrain, with the vector search done on the original (not-enhanced) input. Saves a major part of MCTD's exorbitant complexity with twopass=true, but should be similarly effective in this case.

[helplessandlost]

I haven't gone through the whole list yet, getting ready for work, but started with the MVtools off the main filter page.

On that too I am assuming just dump the whole "pack" into the plugins foler and let the subdirectories go underneath?

[Didée]

Originally Posted by helplessandlost

I am assuming just dump the whole "pack" into the plugins foler

^That^ you should only do when you're asking for trouble.

Example: RemoveGrain 1.0pre contains (among others) RemoveGrain.dll, RemoveGrainS.dll, RemoveGrainSSE2.dll, RemoveGrainSSE3.dll. If you put all of them into \plugins, Avisynth will not work anmore at all (most probably). In this case, use the ~SSE2 one to be on the safe side.

Do not pollute the plugin directory with stuff that doesn't belong there. One DLL of a kind, and the according documentation if you like. Nothing more.

[Emulgator]

(me back again)

Thanks Emulgator, let me ask for clarification.
Are you saying in your edit that your "slooow" script is useable if I run it in two passes?
So pass 1:
....sourcefilter...
ConvertToYV12#(interlaced=true)
ColorYUV(cont_u=400, cont_v=400, off_u=-1, off_v=2, analyze=false, showyuv=false)
ConvertToYUY2
adjustY("spline(Y, 0, 0, 8, 0, 16, 11, 20, 16, 55, 90, 70, 140, 90, 180, 250, 220, 255, 235, true)", false)
Pass 2:
ConvertToYV12
MCTemporalDenoise(settings="medium", deblock=false, interlaced=false, chroma=true, sharp=true, strength=300, GPU=true) < set for either medium or high

Yes.

Memory requirements (as Didée mentioned) and inefficiencies of the calculation process
(when filters of this kind are stacked) can be overcome a bit
if HD denoiser passes are executed separately where possible.

[helplessandlost]

Thanks Emulgator, if I'm not being a pain can you point me to where all the filters needed for this are? Or throw them up in a sendspace?

[Emulgator]

I am continuously working, so I can not walk you through...

Best if you search, try and find out, because some filters are tailored to CPU architecture.
If in doubt, use older filters, some SSEn do not work with certain scripts/CPUs, many dependencies.
Avisynth reports if something crashes. Some plugins, functions and scripts do also report nicely what they need.

Many filters are at warpenterprises, many at avisynth mediawiki,

http://avisynth.org/mediawiki/Main_Page

some only in doom9 threads...

I sent you a PM.