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. |
8th July 2014, 19:23 | #121 | Link | |
Registered User
Join Date: Dec 2004
Location: Terneuzen, Zeeland, the Netherlands, Europe, Earth, Milky Way,Universe
Posts: 689
|
Quote:
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 |
|
9th July 2014, 15:56 | #124 | Link | |
Registered User
Join Date: Dec 2004
Location: Terneuzen, Zeeland, the Netherlands, Europe, Earth, Milky Way,Universe
Posts: 689
|
Quote:
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 |
|
11th July 2014, 09:19 | #125 | Link |
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 |
12th July 2014, 09:13 | #126 | Link |
Registered User
Join Date: Dec 2004
Location: Terneuzen, Zeeland, the Netherlands, Europe, Earth, Milky Way,Universe
Posts: 689
|
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 |
5th September 2014, 07:45 | #130 | Link | |
Join Date: Mar 2006
Location: Barcelona
Posts: 5,034
|
Quote:
|
|
5th September 2014, 10:24 | #131 | Link | |
Registered User
Join Date: May 2005
Posts: 1,462
|
Quote:
Code:
SetMemoryMax(768) SetMTMode(5,4) FFVideoSource("f:\jobs\whatever.mkv") SetMTMode(3) the rest of the filters 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! |
|
5th September 2014, 14:07 | #132 | Link |
I'm Siri
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 |
5th September 2014, 14:23 | #133 | Link |
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 |
5th September 2014, 15:27 | #134 | Link |
I'm Siri
Join Date: Oct 2012
Location: void
Posts: 2,633
|
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.
|
5th September 2014, 16:09 | #136 | Link | |
Registered User
Join Date: May 2005
Posts: 1,462
|
Quote:
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! |
|
5th September 2014, 16:13 | #137 | Link |
Registered User
Join Date: May 2005
Posts: 1,462
|
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! |
5th September 2014, 21:10 | #138 | Link | |
LaTo INV.
Join Date: Jun 2007
Location: France
Posts: 701
|
Quote:
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. |
|
5th September 2014, 23:23 | #139 | Link | |
Registered User
Join Date: May 2005
Posts: 1,462
|
Quote:
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! |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|