Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Capturing and Editing Video > Avisynth Usage

Reply
 
Thread Tools Search this Thread Display Modes
Old 8th July 2014, 19:23   #121  |  Link
videoFred
Registered User
 
videoFred's Avatar
 
Join Date: Dec 2004
Location: Terneuzen, Zeeland, the Netherlands, Europe, Earth, Milky Way,Universe
Posts: 689
Quote:
Originally Posted by johnmeyer View Post
Fred,

Any chance you will post, in one of your 8mm restoration threads, the updates to your script that use AutoAdjust? I was very impressed by the color grading you achieved, especially the greens. I have found it very difficult to get decent greens from my film transfers.
Hi John,

I will send you a PM

many greetings,
Fred.
__________________
About 8mm film:
http://www.super-8.be
Film Transfer Tutorial and example clips:
https://www.youtube.com/watch?v=W4QBsWXKuV8
More Example clips:
http://www.vimeo.com/user678523/videos/sort:newest
videoFred is offline   Reply With Quote
Old 9th July 2014, 10:01   #122  |  Link
LaTo
LaTo INV.
 
LaTo's Avatar
 
Join Date: Jun 2007
Location: France
Posts: 701
AutoAdjust [v2.50 - Update 2014/07/09]

Quote:
v2.50:
fixed crash with external_clip
fixed chroma processing bug
removed temporal_radius=-1
reintroduced internal caching
Hope all problems are fixed
LaTo is offline   Reply With Quote
Old 9th July 2014, 11:58   #123  |  Link
JK1974
Registered User
 
Join Date: Mar 2005
Posts: 89
@videoFred: I would be also interested in you updated scripts. I never had bigger success with former color adjustment plugins, so an easier-to-use solution combined with your scripts would be fantastic.
JK1974 is offline   Reply With Quote
Old 9th July 2014, 15:56   #124  |  Link
videoFred
Registered User
 
videoFred's Avatar
 
Join Date: Dec 2004
Location: Terneuzen, Zeeland, the Netherlands, Europe, Earth, Milky Way,Universe
Posts: 689
Quote:
Originally Posted by JK1974 View Post
@videoFred: I would be also interested in you updated scripts. I never had bigger success with former color adjustment plugins, so an easier-to-use solution combined with your scripts would be fantastic.
The updated script will be tested now by Johnmeyer. After his feedback, I will make it available for everyone.

Fred.
__________________
About 8mm film:
http://www.super-8.be
Film Transfer Tutorial and example clips:
https://www.youtube.com/watch?v=W4QBsWXKuV8
More Example clips:
http://www.vimeo.com/user678523/videos/sort:newest
videoFred is offline   Reply With Quote
Old 11th July 2014, 09:19   #125  |  Link
GillesH
Registered User
 
Join Date: Dec 2013
Location: France
Posts: 64
Hello,

I confirm that AutoAdjust is a great tool.

I take this exchange between Fred, John and Lato for, everyone, thank them.
With their kindly offered ideas on this forum, we have improved our old movies.

And favour to them, and other designers of this forum, my friend Roland and I were able to develop software film restoration.
Of course, this software is completely free and uses, so, some of the ideas of our friends Fred, John, Lato and others ..
This freeware is called FILM9.

This is not the place of the promotion, but if you want to take a look, there is the demonstration here:
All links are provided with the demo.

Very humbly, it is our pleasure to share our contribution.

Thank you again and sorry for my "google english" !!!!
Gilles
GillesH is offline   Reply With Quote
Old 12th July 2014, 09:13   #126  |  Link
videoFred
Registered User
 
videoFred's Avatar
 
Join Date: Dec 2004
Location: Terneuzen, Zeeland, the Netherlands, Europe, Earth, Milky Way,Universe
Posts: 689
Quote:
Originally Posted by GillesH View Post
This freeware is called FILM9.
Hi Gilles,

Film9 is a very nice project! I will take a closer look at it.

many greetings,
Fred.
__________________
About 8mm film:
http://www.super-8.be
Film Transfer Tutorial and example clips:
https://www.youtube.com/watch?v=W4QBsWXKuV8
More Example clips:
http://www.vimeo.com/user678523/videos/sort:newest
videoFred is offline   Reply With Quote
Old 12th July 2014, 23:21   #127  |  Link
johnmeyer
Registered User
 
Join Date: Feb 2002
Location: California
Posts: 2,691
I've been side-tracked by other projects, but still intend to test Fred's updated script.
johnmeyer is offline   Reply With Quote
Old 3rd September 2014, 22:41   #128  |  Link
asarian
Registered User
 
Join Date: May 2005
Posts: 1,462
Quote:
Originally Posted by LaTo View Post
Screenshot of AutoAdjust(debug_view=true):


* Click the image to enlarge *
My, AutoAdjust is real sweet! Thx!
__________________
Gorgeous, delicious, deculture!
asarian is offline   Reply With Quote
Old 5th September 2014, 03:39   #129  |  Link
asarian
Registered User
 
Join Date: May 2005
Posts: 1,462
"With AvisynthMT, SetMtMode(1) must be called before AutoAdjust."

Why SetMtMode(1) per se? SetMtMode(3), which I usually use, no good?!
__________________
Gorgeous, delicious, deculture!
asarian is offline   Reply With Quote
Old 5th September 2014, 07:45   #130  |  Link
Groucho2004
 
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
Quote:
Originally Posted by asarian View Post
"With AvisynthMT, SetMtMode(1) must be called before AutoAdjust."

Why SetMtMode(1) per se? SetMtMode(3), which I usually use, no good?!
I explained this to you before - mode 3 is for source filters. I suggest you read SEt's comments in the AVSMT thread.
Groucho2004 is offline   Reply With Quote
Old 5th September 2014, 10:24   #131  |  Link
asarian
Registered User
 
Join Date: May 2005
Posts: 1,462
Quote:
Originally Posted by Groucho2004 View Post
I explained this to you before - mode 3 is for source filters. I suggest you read SEt's comments in the AVSMT thread.
And as I explained in that thread, MTMode(1) simply isn't stable enough for the things I do. Nor MTMode(2), for that matter. I may not understand all the math behind it, but, after years of experimenting, the following incantation simply works for me:

Code:
SetMemoryMax(768)

SetMTMode(5,4)

FFVideoSource("f:\jobs\whatever.mkv")

SetMTMode(3)

the rest of the filters
MTMode(3) may be slightly slower, but anything below it, and things simply start crashing.

Now, there may be one or two filters out there that could, stand-alone, run stable with MTMode(1), but in the togetherness of what I usually do (lots of temporal denoising), MTMode(3) is the only mode for me that is guaranteed not to crash my job.

And I've read as much about MT AviSynth as I could find, but still found no reason AutoAdjust *must* work within MTMode(1) per se. Hence my question.
__________________
Gorgeous, delicious, deculture!
asarian is offline   Reply With Quote
Old 5th September 2014, 14:07   #132  |  Link
feisty2
I'm Siri
 
feisty2's Avatar
 
Join Date: Oct 2012
Location: void
Posts: 2,633
like I said, slow temporal denoise filters are almost all based on mvtools2 (mdegrain/mcompensate+external denoisers)
but mvtools2 is already mt internally, you don't need and actually can't use these SetMTMode stuff, remove them all
the script will run faster
feisty2 is offline   Reply With Quote
Old 5th September 2014, 14:23   #133  |  Link
SamKook
Registered User
 
Join Date: Mar 2011
Posts: 216
Nothings stopping you from doing multiple SetMTmode calls in your script after the original one, you can switch it to 1 before autoadjust and set it back to 3 after.
Not sure what that will do for speed though since I never needed to actually do that.

But I must admit it's the first time I see a filter that requires a better MT mode to work, that just seem odd.
__________________
AMD Ryzen 9 5950X and EVGA RTX 3080 with G.skill 64Gb 3600 (2 16x2 kit) on Asrock X570 Taichi with Samsung 980 Pro 500Gb NVMe SSD running Win10 x64 on LG 34GN850-B 34.0" 3440 x 1440 160 Hz
SamKook is offline   Reply With Quote
Old 5th September 2014, 15:27   #134  |  Link
feisty2
I'm Siri
 
feisty2's Avatar
 
Join Date: Oct 2012
Location: void
Posts: 2,633
Quote:
Originally Posted by SamKook View Post
But I must admit it's the first time I see a filter that requires a better MT mode to work, that just seem odd.
He's using filters that involve mvtools2, mvtools2 is freaking buggy, just bugs are hidden when calling it by default (single thread usage), and bugs pop out when calling it with unnecessary external mt functions.
feisty2 is offline   Reply With Quote
Old 5th September 2014, 15:45   #135  |  Link
feisty2
I'm Siri
 
feisty2's Avatar
 
Join Date: Oct 2012
Location: void
Posts: 2,633
if you do wanna use SetMTMode on mvtools2, set all "mt" parameters false first which are true by default
and see which mt mode works correctly
feisty2 is offline   Reply With Quote
Old 5th September 2014, 16:09   #136  |  Link
asarian
Registered User
 
Join Date: May 2005
Posts: 1,462
Quote:
Originally Posted by feisty2 View Post
like I said, slow temporal denoise filters are almost all based on mvtools2 (mdegrain/mcompensate+external denoisers)
but mvtools2 is already mt internally, you don't need and actually can't use these SetMTMode stuff, remove them all
the script will run faster
I've tried that before, of course. Removed all MT stuff. Most of the scripts you wrote for me earlier, for example, actually hang in there for quite a while, but then crash after all, after a while. Usuallly with some CACHE_EXCEPTION type of error. And cache-handling is precisely one of the things MTMode(3) improves on greatly. With MTMode(3) my jobs are simply guaranteed not to crash.

One thing I can still try is to remove the MT dll altogether (and put the 2.6 AviSynth one back in its stead again). For instance, I saw that AutoAdjust() is MT aware, even when no MT stuff is used in the script at all, and stops using AS internal threading altogether when it detects an MT AviSynth. So, it may be that other filters are seeing it too, and revert to single-threading (and then crash).

MTMode(3) scripts still run at 100% CPU utilization here, btw: all 12 logical cores (i7 980X) are fully occupied. The speed penalty of MTMode(3) is largely usurped, as it were, by x264 using up the idle time. Only when the script output is so ridiculously low, x264 simply won't have enough material to work with any more to use 100% CPU. But that rarely ever happens.

N.B. It's actually mostly MCTemporalDenoise that needs the MTMode(3) for some reason.
__________________
Gorgeous, delicious, deculture!
asarian is offline   Reply With Quote
Old 5th September 2014, 16:13   #137  |  Link
asarian
Registered User
 
Join Date: May 2005
Posts: 1,462
Quote:
Originally Posted by feisty2 View Post
if you do wanna use SetMTMode on mvtools2, set all "mt" parameters false first which are true by default
and see which mt mode works correctly
Yes, LOL, that was akin to what I was thinking of myself (to just put back the non-MT dll). But yes, I saw there's actually commands to disable MT from within the script itself. So I will try that. Thx.
__________________
Gorgeous, delicious, deculture!
asarian is offline   Reply With Quote
Old 5th September 2014, 21:10   #138  |  Link
LaTo
LaTo INV.
 
LaTo's Avatar
 
Join Date: Jun 2007
Location: France
Posts: 701
Quote:
Originally Posted by asarian View Post
"With AvisynthMT, SetMtMode(1) must be called before AutoAdjust."

Why SetMtMode(1) per se? SetMtMode(3), which I usually use, no good?!
AutoAdjust is a heavy temporal filter (it requests a lot of frames, temporal radius is 20 by default).
MtMode=1 was recommended (but not mandatory) in v2.00 because of this.

Now it is less significant, but if you do not use MtMode=1 AutoAdjust will be slower and will use more memory because:
- identical calculations will be performed in each instance
- identical data will be stored in each instance
- avisynth's cache will be more stressed
- frames will not be requested in linear order

MtMode=1 is not a mandatory, but it works and is better... So why don't use it?

Last edited by LaTo; 5th September 2014 at 21:22.
LaTo is offline   Reply With Quote
Old 5th September 2014, 23:23   #139  |  Link
asarian
Registered User
 
Join Date: May 2005
Posts: 1,462
Quote:
Originally Posted by LaTo View Post
AutoAdjust is a heavy temporal filter (it requests a lot of frames, temporal radius is 20 by default).
MtMode=1 was recommended (but not mandatory) in v2.00 because of this.

Now it is less significant, but if you do not use MtMode=1 AutoAdjust will be slower and will use more memory because:
- identical calculations will be performed in each instance
- identical data will be stored in each instance
- avisynth's cache will be more stressed
- frames will not be requested in linear order

MtMode=1 is not a mandatory, but it works and is better... So why don't use it?
Thx for the explanation! As soon as this process is done (just another 6 hours), I will try and rerun it with Mode 1. I will let you know what it does.

Quote:
Originally Posted by LaTo View Post

Code:
SetMemoryMax(1024)
SetMTMode(5,4)
ffdshow_source()
SetMTMode(1,4)
AutoAdjust(auto_gain=true, auto_balance=true, balance_str=1.0)
GetMTMode(false) > 0 ? distributor() : last
Not sure the '4' in SetMTMode(1,4) has any effect there, really; but it looks like you're saying you can just use Mode 1 for your filter alone, which is good.
__________________
Gorgeous, delicious, deculture!
asarian is offline   Reply With Quote
Old 13th October 2014, 05:45   #140  |  Link
czerro
Registered User
 
Join Date: Feb 2008
Posts: 31
Edit: Going to retest something as a possible Avisynth+ build incompatibility, please disregard.

Last edited by czerro; 13th October 2014 at 05:52.
czerro is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 03:23.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.