The power of Avisynth: restoring old 8mm films.

[johnmeyer]

Originally Posted by rjansen1

@Bernardd: tried replacing Gammac with your script and found that it gives good results on some scenes, but then again worse results on others. Also it doesn't seem to work multithreaded. Is that correct?

I guess there's no magic bullit and in the end it's a matter of selecting the method that works good for 80% of the movie and fix the other bits using different methods. From what I read that's what you guys do as well

Cheers,
Remco

1. It definitely works multi-threaded, with VD+.

2. There is no automated solution to either gamma or color correction. I always create two versions of my "restored" footage, one with GamMac (or equivalent tool) and one without, and I then cut between them on my NLE timeline to create the final version.

[rjansen1]

Originally Posted by johnmeyer

1. It definitely works multi-threaded, with VD+.

Ok, then I'm doing something wrong. I replaced Gammac with Bernardd's script and found the overall script failing on Prefetch(2).

I'm using Avisynth+ x64, what's VD+?

Cheers,
Remco

[johnmeyer]

Originally Posted by rjansen1

Ok, then I'm doing something wrong. I replaced Gammac with Bernardd's script and found the overall script failing on Prefetch(2).

I'm using Avisynth+ x64, what's VD+?

Cheers,
Remco

My bad. I wrote that in a hurry and didn't check. VD would be VirtualDub, but I really meant to say AVISynth+.

I'm using AVISynth+ version 0.1 r2508, 32-bit, running under WinXP Pro 32-bit.

[rjansen1]

No problemo. I'll tinker with it some more over the next couple of days and try to figure it out.

Thanks,
Remco

[rjansen1]

@Bernardd @Johnmeyer

I can't seem to get Bernardd's script to run multithreaded. Did a little testscript:

AviSource("Testclip.avi")

SetFilterMTMode("DEFAULT_MT_MODE", 2)

Import("C:\VideoTools\AvisynthRepository\AVSPLUS_x64\plugins\RGBAdapt_Awb_Process function.avs")

ConvertToRGB32()
AWB_Func()
converttoYV12()

Prefetch(threads=2)

Without the Prefetch line the script runs fine, with Prefetch it gives me an error on that line saying "I don't know what 'Fmt' means". I'm using Avisynth+ x64.

As far as I can tell 'Fmt' is a variable used somewhere within Bernardd's script. I've tried different ways of importing the script, even importing "RGBAdapt_Awb_Process script call.avs" since it seems to hold a bunch of variables. But so far I haven't been able to figure out how to get it to use MT.

Any tips are welcome therefore

Cheers,
Remco

[johnmeyer]

I've not used AVISynth+64. I only use the 32-bit version. Many of the plugins are 32-bit and I simply don't know how they behave in a 64-bit environment.

There is no reason whatsoever to use the 64-bit version. If you want to switch between several versions of AVISynth, this is such a common need that Groucho built a simple utility that lets you select which version you want to use. You just run this when you need the 32-bit version, do your work, and then when you need the 64-bit version, you switch back.

[real.finder]

Originally Posted by johnmeyer

I've not used AVISynth+64. I only use the 32-bit version. Many of the plugins are 32-bit and I simply don't know how they behave in a 64-bit environment.

There is no reason whatsoever to use the 64-bit version. If you want to switch between several versions of AVISynth, this is such a common need that Groucho built a simple utility that lets you select which version you want to use. You just run this when you need the 32-bit version, do your work, and then when you need the 64-bit version, you switch back.

you can have both 32 and 64 in the same time, switch between them depends on the program/tool/encoder you use

edit: also you can run both in same time in mpp (mp_pipeline)

[real.finder]

Originally Posted by rjansen1

@Bernardd @Johnmeyer

I can't seem to get Bernardd's script to run multithreaded. Did a little testscript:

AviSource("Testclip.avi")

SetFilterMTMode("DEFAULT_MT_MODE", 2)

Import("C:\VideoTools\AvisynthRepository\AVSPLUS_x64\plugins\RGBAdapt_Awb_Process function.avs")

ConvertToRGB32()
AWB_Func()
converttoYV12()

Prefetch(threads=2)

Without the Prefetch line the script runs fine, with Prefetch it gives me an error on that line saying "I don't know what 'Fmt' means". I'm using Avisynth+ x64.

As far as I can tell 'Fmt' is a variable used somewhere within Bernardd's script. I've tried different ways of importing the script, even importing "RGBAdapt_Awb_Process script call.avs" since it seems to hold a bunch of variables. But so far I haven't been able to figure out how to get it to use MT.

Any tips are welcome therefore

Cheers,
Remco

it's known problem with runtime and mt (Prefetch) that didn't fixed for long time (maybe it will be ever)

[rjansen1]

Originally Posted by johnmeyer

I've not used AVISynth+64. I only use the 32-bit version. Many of the plugins are 32-bit and I simply don't know how they behave in a 64-bit environment.

There is no reason whatsoever to use the 64-bit version. If you want to switch between several versions of AVISynth, this is such a common need that Groucho built a simple utility that lets you select which version you want to use. You just run this when you need the 32-bit version, do your work, and then when you need the 64-bit version, you switch back.

I'm using Groucho's installer already. Have tried running my testscript on 32-bits AVS+ in Vdub2-32 but get the same "don't know what 'Fmt' means" error.

Could (any of) you maybe post a simple example of how you use Bernardd's script in a multithreaded setup? And tbh... if I can't get it to run multithreaded that's no biggy. That one render will just take a little longer.

Cheers,
Remco

[StainlessS]

Could (any of) you

See Real.Finder last line,

it's known problem with runtime and mt (Prefetch) that didn't fixed for long time (maybe it will be ever)

I never use MT, its just not worth the hassle (so it takes a bit longer - who cares - Maybe can do multiple encodes at once instead of MT).

[rjansen1]

Originally Posted by StainlessS

See Real.Finder last line,

Yeah, I read that. Just seemed to read John saying he had it working multithreaded, so I wondered how.

But you're right; it's not an issue.

Thanks,
Remco

[StainlessS]

Maybe can do multiple encodes at once instead of MT

MakeMultiPartScripts & FFMS_MakeMultiPartScripts:- http://forum.doom9.org/showthread.ph...ltiPartScripts

# FFMS_MakeMultiPartScripts.avsi

Function FFMS_MakeMultiPartScript(String FnList,String "OutPath",Int "Parts") {
/*
    FFMS_MakeMultiPartScripts v0.04  :::  Requires RT_Stats, Avs+ OR GScript.

    FFMS_MakeMultiPartScript(String FnList,String "OutPath"="",Int "Parts"=4)
        FnList,   No default. Multi-line string of avs filenames(1 or more).
                  Source scripts to split must use FFMS2 source filter.
                  Source scripts clip length must be at least (20 * Parts) frames else error abort.
                  This function sets a Global FFMS_MakeMultiPartScript_Glb variable, can be detected in source
                    avs scripts so as to determine if called by this function (for whatever reason).
        OutPath,  Default "", Same Directory as source file directory. Path (must exist) where output scripts written.
                  Where OutPath = default "", and multiple input files with different directories given in FnList, OutPath will use input file directory
                  for each input file (even when different directories, will not be different paths where fileSelector client script used).
                  Use "." for current directory.
        Parts,    Default 4. Number of parts that source script is split into.
*/

[johnmeyer]

Originally Posted by rjansen1

Yeah, I read that. Just seemed to read John saying he had it working multithreaded, so I wondered how.

I looked into this, and I have a mystery for all the AVISynth developers and gurus.

Here it is:

My film script runs multi-threaded without any problem if I set the "play_speed" to 24 fps. However (and here is where it gets weird) if I set it to 23.976, it won't run multi-threaded and simply hangs on loading.

Well, I thought, it must be an integer/float issue. So, I tried 24.0 fps instead of 24.

Worked fine.

I then tried 24 * 1 / 1

Worked fine.

I then tried 24 * 1.0 / 1.0

Nope, that hung. So did 24.0 * 1 / 1

And, as I stated above, simply entering 23.976 also made the script hang.

The play_speed variable only gets used one time in the script, and that is as the main variable to AssumeFPS. That's it. Somehow that causes MT to fail and AVISynth to hang.

I am using AVISynth+ 0.1 r2508 32-bit under XP 32-bit.

[edit]I decided to simply remove the assumefps() statement since I am already feeding the script 23.976 sound film. Once I removed that, the film speed was now 23.976 and the script ran multi-threaded without a problem.

AVISynth sure is a mystery at times. [end edit]

[Reel.Deel]

Originally Posted by johnmeyer

I am using AVISynth+ 0.1 r2508 32-bit under XP 32-bit.

I am not sure if it will fix the problem, but why not update to the latest AviSynth+ (r2772)? r2508 is over 2 years old and there has been lots of bugfixes since then.

[bassquake]

Does anyone know what the min and max values are for the following AVISynth plugins:

- RemoveDirtMC (dirt_strength)
- UnSharpMask (strength, radius and threshold)

Its not mentioned in their wikis, only the default numbers are shown.

I ask as I'd like to use sliders in AvsPMod. Thanks.

[videoFred]

Originally Posted by bassquake

Does anyone know what the min and max values are for the following AVISynth plugins:

- RemoveDirtMC (dirt_strength)
- UnSharpMask (strength, radius and threshold)

Its not mentioned in their wikis, only the default numbers are shown.

I ask as I'd like to use sliders in AvsPMod. Thanks.

Hi Bassquake,

I do not know the max. values but I assume you will get an error message if you set the values over the limit. (if there is a limit)

Anyhow, you will never need dirt_strength above 100 for example.

For unsharpmask I suggest the following max. values:
strength: 200 radius: 6 threshold: 10

And if you need more, it's very easy to change the max. value from the AvsPmod sliders, as you know of cource.

Fred.

[bassquake]

Originally Posted by videoFred

Hi Bassquake,

I do not know the max. values but I assume you will get an error message if you set the values over the limit. (if there is a limit)

Anyhow, you will never need dirt_strength above 100 for example.

For unsharpmask I suggest the following max. values:
strength: 200 radius: 6 threshold: 10

And if you need more, it's very easy to change the max. value from the AvsPmod sliders, as you know of cource.

Fred.

Thanks, I went with:

Dirt Strength: 100

UnSharpmask Settings (Similar to VirtualDubs):
Strength: 0 - 200
Radius: 0 - 25
Threshold: 0 - 255

Doesn't seem to error no matter how large the values are!

One last thing, is there a way to hide the variables showing as highlighted? Its a bit cluttered.

[videoFred]

Originally Posted by bassquake

One last thing, is there a way to hide the variables showing as highlighted? Its a bit cluttered.

Set AVSPMod as followed:
Options > Program settings > User Sliders > Create user sliders automatically > Select "Type string(filename)" Please unselect all other options.

Fred.

[bassquake]

Originally Posted by videoFred

Set AVSPMod as followed:
Options > Program settings > User Sliders > Create user sliders automatically > Select "Type string(filename)" Please unselect all other options.

Fred.

Cool, thanks.

I kept "type string (list)" selected so I could change colorspace options on the fly.

Would be nice to be able add show/hide each of the variables separately. Oh well. It'll do for now.

[imsrk48]

Originally Posted by videoFred

UPDATE 20/06/2012
-------------------------

Newest version of the script:
http://www.super-8.be/avisynth/Film_...vs_06_2012.zip

- improved autolevels
- improved stabilisation
- improved sharpening
- less plugins
- plugins are now in "plugins' folder.
- better helpfiles



=================================================================

UPDATE 06/06/2011
--------------------
The script discussed in this thread only works good with high quality film transfers.
The digital source must be progressive and there should be no duplicate frames.

Many people, however, are having already a digital transfer of their old 8mm films on DVD.
My script is useless here. But you can use some parts of it.
For those people, FPP has made this exellent thread:
http://forum.doom9.org/showthread.php?t=161493

===================================================================







ORIGINAL POSTING 14th january 2009:
-----------------------------------------
I have posted an example clip on Vimeo to show the people the incredible power of Avisynth.



With special thanks to Fizick, Didée, Manao for making these exellent plugins available for all of us.

Special thanks to Josey_Wells too for the multithreaded version.
Averaging more then 4 frames in MVDegrainMulti() works very well for removing film dirt spots.

The example clip is showing the result of a special film restoring script I have made.

The filmtransfer itself was done by me, but that film needs a second wetgate transfer.
There was a dirt spot on the CCD from my camera too. But that's easy enough to fix.

I just could not wait to show you all these first results.

Fred.

Fabulous Work

Sent from my LG-M700 using Tapatalk