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. Domains: forum.doom9.org / forum.doom9.net / forum.doom9.se |
|
|
#422 | Link | |
|
Registered User
Join Date: May 2005
Posts: 1,572
|
Quote:
FFVideoSource, eh? Hmm, if that's true, then I'm having a problem, as I replace DirectShowSource with FFVideoSource calls, these days, because the former is frame-consistent (and DirectShowSource is not!). So, is there anything else out there, besides FFVideoSource, which is frame consistent? With a heavy script like MCTemporalDenoise, I really need frame-consistency. :(
__________________
Gorgeous, delicious, deculture! |
|
|
|
|
|
|
#423 | Link |
|
LaTo INV.
Join Date: Jun 2007
Location: France
Posts: 701
|
I haven't FFVideoSource on my PC, so for testing I have replaced this one by DirectShowSource in your script.
No ghosting at all, maybe a bug in your version of FFVideoSource? Try with DGAVCIndex or DGNVTools, the problem should be solved. |
|
|
|
|
|
#425 | Link |
|
Registered User
Join Date: May 2005
Posts: 1,572
|
I wonder, if I have a really grainy source, could I just double the MCTemporalDenoise line? Like so:
MCTemporalDenoise(settings="medium") MCTemporalDenoise(settings="medium") GradFun2DBmod(thr=1.8,thrC=1.0,mode=0,str=2.4,strC=0.0,temp=50,adapt=64,mask=false,show=false) Instead of using 1x MCTemporalDenoise(settings="high"). Or does that mess up the lookahead functionality of MCTemporalDenoise? Reason I ask, is that MCTemporalDenoise(settings="high") takes incredibly long on HD material (several hundred hours on my i7 980x). So maybe just doubling is the way to go.
__________________
Gorgeous, delicious, deculture! |
|
|
|
|
|
#426 | Link | |
|
LaTo INV.
Join Date: Jun 2007
Location: France
Posts: 701
|
Quote:
It should be a good speed boost
|
|
|
|
|
|
|
#427 | Link | |
|
Registered User
Join Date: May 2005
Posts: 1,572
|
Quote:
I guess the real issue is still that I can't get MCTemporalDenoise to utilize the CPU properly. At 'high' CPU usage drops tp about 8% (over all 12 logical cores). And an MT"" call, or using any of the SetMTMode calls, makes MCTemporalDenoise crash; at least on my Highlander Blu-Ray. P.S. Callimg MCTemporalDenoise twice in a row, btw, doesn't seem to work: it uses CPU, but x264 never starts up; so I guess it just hangs at initializong things, or gets into a loop of some sort; or twice 'medium' is simply even slower than 1x 'high'. :)
__________________
Gorgeous, delicious, deculture! |
|
|
|
|
|
|
#431 | Link | |
|
Registered User
Join Date: Jan 2009
Posts: 18
|
Thanks poisondeathray
I saw the link but yesterday I didn't know what to do with it. I expected a zip or something like most other filters. Thanks to another post of yours Quote:
What is not clear to me is what do you do about the required filters? Do you need to load the 15 filters before loading the avsi? Should you make a script so that they are all loaded in one go? |
|
|
|
|
|
|
#432 | Link |
|
Registered User
Join Date: Sep 2007
Posts: 5,669
|
The prerequisite filters are listed at the top of the script. You have to get them (not included)
If the prereq's are .dll's most are autoloading if placed in the plugins folder. Otherwise use LoadPlugin() , or you can make your own custom .avsi file . But beware the more autoloading filters you have, the slower and more memory consumption . Once you start accumulating a bunch of filters, it can make a difference The reason why a static .zip file is not provded, is the filters are always being updated . You should get them from the original source, with original documentation. People sometimes modify filters. This way no mixups or filter version errors occur when debugging You don't need all the pre-req's for this one . Only if you use some of the PP functions. It will tell you what one you are missing if you try to use it. |
|
|
|
|
|
#433 | Link |
|
Registered User
Join Date: Jan 2009
Posts: 18
|
Thank you poisondeathray
So if I understand correctly, Only the most frequently used .dll's and .avsi's should remain in the plugins folder. When in another folder, should a .avsi be loaded with "loadplugin" or with "import" like a .avs or should it be renamed .avs? For this script, I don't need to load all pre-req filters, the MCTemporalDenoise script will tell me which one I am missing and then I can incorporate it in my .avs and although it may be easier, as I was asking before, to make a .avs that would contain all the loadplugin/import of the pre-req filters The first solution would be more efficient in the long run. Am I correct? Last edited by skaleton; 23rd August 2010 at 01:00. |
|
|
|
|
|
#434 | Link | ||
|
Registered User
Join Date: Sep 2007
Posts: 5,669
|
Quote:
Quote:
![]() some people load everything with loadplugin or import at the top of each and every script you can make your own avsi that autoloads everything if you want |
||
|
|
|
|
|
#435 | Link |
|
Learning fast
Join Date: May 2008
Location: Bucharest
Posts: 33
|
Any chance of this getting a bit of multithreading? Using GPU is a big boost (0.9 to 1.5 fps). Two instances don't work.
Also I think post-TTempSmooth is broken (i added vis_blur=1 inside the scrip but nothing happened). |
|
|
|
|
|
#436 | Link |
|
Registered User
Join Date: May 2005
Posts: 1,572
|
I'm having trouble with MCTemporalDenoise 'hanging' at times. Well, it doesn't really hang, in the sense of not responding any more; it just doesn't output anything any more, like being caught in a loop somehow. Here's a good example of a video fragment (5 MB) causing this, from the movie 'Push':
Push fragment Processed as follows: Code:
DSS2("c:\video\push_test.m2ts", fps=24).ConvertToYV12()
Crop(0, 132, 0, -132)
MCTemporalDenoise(settings="low")
GradFun2DBmod(thr=1.4,thrC=1.0,mode=0,str=1.2,strC=0.0,temp=50,adapt=64,mask=false,show=false)
I would really like to know what's causing this; and how to fix it, of course. Thanks.
__________________
Gorgeous, delicious, deculture! |
|
|
|
|
|
#437 | Link |
|
Guest
Posts: n/a
|
Use a different source filter, DSS2 is pretty bad at direct M2TS ...
Index it first for a much better chance at success (I know indexing is stable, I tried a few source filters on BD M2TS files and DSS2 was the least likely to complete the encode ... I use DGDecNV to consistently run 30GB M2TS's thru MCTemporalDenoise() for the compression boost) ... 7ek Last edited by 7ekno; 18th September 2010 at 12:37. |
|
|
|
#438 | Link | |
|
Registered User
Join Date: May 2005
Posts: 1,572
|
Quote:
Mind you, I use MCTemporalDenoise a lot (~300GB a week, as I'm reprocessing my now vast Blu-Ray collection). Mostly it goes very well. There's just a few films where the process gets stuck somehow, like with 'Push'. EDIT: I'll be d*amned. :) Finally bought a license for DGDecNV (about time; no point in spending $1,000 on a i7 980x CPU, only to skimp out on this cheap decoder license), and now it actually works. :) Guess FFVideoSource isn't at good at indexing as it thinks. I should have done this much earlier! P.S. DGDecNV is also the only decoder, so far, that gets the framerate right without external help.
__________________
Gorgeous, delicious, deculture! Last edited by asarian; 18th September 2010 at 15:02. Reason: New info |
|
|
|
|
|
|
#439 | Link | |
|
lurkster
Join Date: Jul 2009
Location: D9|D10
Posts: 123
|
Quote:
|
|
|
|
|
|
|
#440 | Link |
|
User of free A/V tools
Join Date: Jul 2006
Location: SK
Posts: 826
|
True multithreading
Is there anybody out there who successfully runs this script in MT mode?
I mean, though I've an Intel i7-920 (quad core+HT = 8 threads) I can't make it to use more than 13% of CPU (which effectively means that only 1 thread is always running). Here's my AVS script: PHP Code:
Any suggestions of proven solutions are welcome, quality of LaTo's script is outstanding but not being able to utilize the full power of my CPU efficiently is just so frustrating ![]() Maybe 64-bit MT Avisynth build is needed? But are there all required plugins available in 64-bit then? |
|
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|