Removing horizontal/vertical film lines and scratches? - Page 6

sanlyn · #**101** 05-20-2018, 10:04 AM

DeFlicker is a Virtualdub plugin. There is nothing in the posted scripts that calls it, and nothing that loads a Virtualdub plugin.

yukukuhi · #**102** 05-20-2018, 12:50 PM

That's what I also wondered but it mentions about something to be present in the line 135 of this RemoveSpotsMC4.avsi plugin. I checked it out in notepad and found that particular line to be present with the name DeFlicker. Would you please help me out.

sanlyn · #**103** 05-20-2018, 07:13 PM

You can work around that by getting the old Avs 2.5 version of DeFlicker for Avisynth, download here; http://avisynth.org.ru/deflicker/deflicker04.zip. Unzip the file and copy DeFlicker.dll into your Avisynth plugins. It will load automatically.

You will also need despot.dll. Get it here: http://avisynth.org.ru/despot/despot3610.zip. Unzip the file and copy Despot.dll to your Avisynth plugins.

You will need 32-but dll's for DePan tools version 1.13.1 and DePanEstimate version 1.10. These two specialized functions also require the FFTW library version 3.

If you already have QTGMC or FFT3D filter installed on your PC, you already have the FFTW library files. This involves two files: FFTW3.dll and libfftw3f-3.dll. If you don't have these, get FFTW3.dll at ftp://ftp.fftw.org/pub/fftw/fftw3win32mingw.zip. Unzip that file and do this:
(a) In the unzip'd files, find FFTW3.dll
(b) Make an exact copy of the FFTW3.dll file, and rename the copy as libfftw3f-3.dll.
If you think this means you will have two copies of the same .dll using two different names, you're correct.
(c) Copy FFTW3.dll and libfftw3f-3.dll into C:\Windows\SYSWOW64.

The FFTW3 library files are NOT Avisynth filters. They are Windows system files. Do not put FFTW3 or libfftw3f-3 in your Avisynth plugins folder.

yukukuhi · #**104** 05-21-2018, 10:51 AM

Thanks for that sanlyn, it solved the RemoveSpotsMC issue. So that narrow downs the ntdll problem to be coming from RemoveDirtMC.

sanlyn · #**105** 05-21-2018, 02:14 PM

This recent thread might help: Fix for problems running Avisynth's RemoveDirtMC

While you're at it, you might check your Installed Programs in Control Panel to see if you have the following Microsoft Visual c++ Runtime redistributables:

2005 https://www.microsoft.com/en-us/down...s.aspx?id=3387
2008 https://www.microsoft.com/en-us/down...ils.aspx?id=29
2010 https://www.microsoft.com/en-us/down...s.aspx?id=5555
2012 https://www.microsoft.com/en-us/down....aspx?id=30679
2013 https://www.microsoft.com/en-us/down....aspx?id=40784
2015 https://www.microsoft.com/en-us/down....aspx?id=48145

yukukuhi · #**106** 05-22-2018, 07:54 AM

All done but it's still the same. Yet this time around, instead of crashing it displays a error message.

Avisynth open failure:
Avisynth access violation at 0x0003F2E1 in C:\WINDOWS\SYSTEM32\ntdll.dll,
attempting to read from 0x0CA7542F

sanlyn · #**107** 05-22-2018, 06:30 PM

There's not much anyoner c an do beyond this point without going over everything you have installed on your system. Windows 10 is a nightmare, and not just with video, and most ntdll errors never gets solved. Others have W10/ntdll problems with MEGUI, Avidemux, DirectShowSource, many filters, Adobe Encore, and on and on.

Are you using your PC with one hard drive? The operating system, apps, video storage, running scripts and video processing and writing processed files, all to the same C: drive? Even without Windows 10 or 8, that's asking for trouble. All you need is one bad sector on an overworked or overloaded drive and you're in for difficulties.

yukukuhi · #**108** 05-23-2018, 11:37 AM

Is there an alternative filter for RemoveDirtMC?

sanlyn · #**109** 05-23-2018, 06:20 PM

Well, there's RemoveDirtMC2. It's similar, but you can try it (attached as RemoveDirtMC.avs). Its syntax has three parameters instead of two. The original RemoveDirtMC is called with two parameters: the first parameter can be anywhere from 10 to 100 (the higher you go, the more detail it removes). The second parameter should be false.

Code:

RemoveDirtMC(50,false)

RemoveDirtMC2 has three values. The first can be 10 to 100. the second must always be 2, the third should be false:

Code:

RemoveDirtMC2(50,2,false)

RemoveDirtMC2 requires two additional support plugins, if you don't already have them:
FluxSmooth.dll (http://avisynth.nl/index.php/FluxSmooth)
VagueDenoiser.dll (https://avisynth.org.ru/vague/vaguedenoiser0351.zip)

But that doesn't address the core ntdll problem. Many other plugins use similar code and support files as RemoveDirtMC. Versions of RemoveSpots even use the same RemoveGrain dll's.

If you are using the older versions of RemoveGrain dll's, you can try removing them temporarily and replacing them with the newer RgTools, which contains newer versions of all the old RG dll's (http://avisynth.nl/index.php/RgTools). Actually you should be able to have RGTools.dll and the older RemoveGrain dll's in your plugins at the same time, but you can try keeping RgTools and removing the old Remove Grain dll's temporarily. The older dll's are:
RemoveGrainSSE2.dll
RepairSSE2.dll
SSE2Toools.dll
VerticalCleaner.dll

And BTW, if you have any of the "SSE3" versions of those SSE2 dll's, remove them. The SSE3's are known bugs, even with Windows XP.

ntdll problems have almost always been traced back to codecs that Windows10 doesn't like. Fortu7nately the newest versions of huffyuv and Lagarith aren't a problem. Older stuff like Xvid seems to be a problem even if it's not being used in a script (mystery of mysteries, no one knows why). Also make sure you have 32-bit versions of everything you're using in Avisynth and Virtualdub. Don't mix 32-bit and 64-bit plugins or codecs.

yukukuhi · #**110** 05-24-2018, 06:57 AM

RemoveDirtMC2 emits the same error.

Would installing XP guarantee the fix for the error?

If so, then would installing the 10th edition of Windows XP 2017 a wise decision as it's available online. If it's not a good one, else what edition to install?

sanlyn · #**111** 05-24-2018, 04:33 PM

There is no "10th" edition of Windows XP. It's an XP Virtual Machine version that gets downloaded. I'm not familiar with using it, but people are using it for XP games and other software. You can give it a try, but someone with VM experience will have to help you with any problems.

yukukuhi · #**112** 05-25-2018, 05:35 AM

Ok so when did you buy and start using XP?

And is it a home edition or a pro one?

sanlyn · #**113** 05-25-2018, 06:27 AM

I first used XP in 2001. My current XP machines were built in 2004, 2007, 2015, and 2016. Over the years I've used the Home edition and the Pro Edition. The 2004 machine is XP Home and is used only for VHS capture nowadays. The others are XP Pro.

I've had two Win10 machines, a PC and a laptop. They were so frustrating to use that I returned both of them within a few days.

My laptop is a used Win7 machine. I plan to get a refurbished Win7 Pro PC strictly for HD video processing. My 2015 and 2016 XP's are powerful enough for it, but they're usually tied up with VHS captures that I haven't finished. I don't use all of these XP's at the same time. The XP's not being used are kept for backup. I keep an old 2005 Gateway XP Media Edition laptop strictly for use on an annual project that requires Adobe Acrobat Pro for making .pdf files. That software, Photoshop Pro, and AfterEffects Pro cost plenty of money but won't work on Windows 10. I don't intend to pay for Adobe software or any other software multiple times whenever Microsoft designs an incompatible operating system.

My wife has a Windows 10 laptop. She constantly complains about it, but it was required for her workplace when it was purchased. She doesn't use a PC often enough to justify buying a replacement.

yukukuhi · #**114** 05-25-2018, 09:38 AM

Quote:

My laptop is a used Win7 machine. I plan to get a refurbished Win7 Pro PC strictly for HD video processing.

What do you specify by HD video processing & why Win7 specifically, what's unique about it?

sanlyn · #**115** 05-25-2018, 12:10 PM

I'd consider HD any frame size bigger than 720x480.

What's useful about Win7 is that I can use a slightly smaller/slower processor than I need with XP for the same HD work and faster run times. Otherwise it's mostly for internet browsing with strong anti virus protection (many of the best anti virus products will no longer support XP by 2020. Fine with me, I don't need internet browsing to run Avisynth or encoding.

Unique? What's unique about W7 is that all of my software that won't run on W10 works quite well on W7. The exceptions are AfterEffects Pro, an astrological mapping program, some Adobe Photoshop Pro plugins, Adobe Acrobat, and some older TMPGenc products -- I won't give up that software. The latter few items require XP. And since my capture cards are ATI All In Wonders with AGP mounts, that disqualifies Vista, Win8, and Win10 for capture. I also disqualify Win8 and Win10 as being too graphically convoluted for intuitive use, and too intrusive (please login using your Microsoft Account so that we can slow down your system by tracking everything you do). How about a plain old-fashioned login (or no login, if desired) and an of-fashioned F8 for Safe Mode? And what's this b.s. about not being able to turn off Windows Update?

yukukuhi · #**116** 05-25-2018, 12:26 PM

Would installing XP guarantee the fix for the error?

sanlyn · #**117** 05-25-2018, 04:41 PM

We would need an OS system expert to answer that one.
One is supposed to be able to install an XP Virtual Machine in Windows 7 and W10. The VM acts just like XP, as far as I know. The best solution is to reinstall W10 if possible and get all of its updates. But W10 still isn't ideal for video work. so you could be back where you started.
I don't see why it wouldn't work, although I do know that VirtualDub capture and some Adobe apps won't run in a Virtual Machine.

yukukuhi · #**118** 05-26-2018, 08:07 AM

Forget the VM. I'm asking wether if installing the plain old XP solve the ntdll.dll error?

lordsmurf · #**119** 05-26-2018, 11:22 AM

Quote:

Originally Posted by yukukuhi

Forget the VM. I'm asking wether if installing the plain old XP solve the ntdll.dll error?

It should. A fresh OS install should lack such issues. Just be sure to properly install Avisynth.

I use Win7 for my Avisynth system, both with 32-bit and the +64-bit install. For Avisynth, XP is a bit dated. It really depends on what hardware is being used as to which OS is best (XP or 7). I have 16gb RAM, SSD, and i7-6700K Skylake.

sanlyn · #**120** 05-26-2018, 08:40 PM

Two more complaints about Win10 upgrades, and software that no longer works. Followed by a bunch of convoluted fixes that may or may not work:
https://forum.videohelp.com/threads/...-win-10-update
https://forum.videohelp.com/threads/...-start-anymore

Those are new posts, just today.
I posted it once, I post it again: I'll never recommend Windows 10 for video work.