I'm suddenly getting the following error message when dragging a script into VDub2:

Script Error: No Function Named QTGMC.

I've tried the below very basic script (from where I started from) but still getting the error message. QTGMC is in the plugins64+ folder, and I didn't have this issue yesterday.

Does anyone know what the issue could be? I'm not doing well on the script writing front as of yet, am I missing something with the below? Thank you!

Script:

-- merged --

Ok - I'm not sure what is going on, but the SysWOW64 folder is empty. This doesn't look good from my online search, and have no idea how this could've happened...anyone with any thoughts, I'd greatly appreciate them.

-- merged --

Nevermind - I guess the SysWOW64 folder I should be looking in always is in C:\Windows - not C:
The second one has all relevant files/dll's.

Still having the script issues, thanks again.

-- merged --

Got it - I uninstalled AviSynth+, and reinstalled a fresh file, reloaded the essential plugins...Working now. Thanks!

Hello, I am having the same issue here.

I have uninstalled AviSynth+ and reinstalled it with no luck. I have deleted VirtualDub, downloaded it again and still, whenever I drag&drop the .avs into VD gets me the error. Even if try to load the .avs from VD menu File->open video file->select the script.

What does your script look like?
Did you install the qtgmc script and all its dependencies?

Yeah I believe everything is correct for the qtgmc dependencies. I have checked more than once. qtgmc.avsi, masktools2.dll, mvtools2.dll, nnedi3.dll, rgtools, zs_rf_shared.avsi, FFTW3.dll+libfftw3f-3.dll

a. do other scripts work?
b. guessing that there might be something wrong with the autoloading, have you tried explicitly loading the scripts with something like
?

Cu Selur

no other scripts don't work. The only thing that works is the preview window inside avspmd. I have tried importing, still no luck.

You still get the same error when you import manually? => Are you sure you only got one Avisynth version on your system? (maybe deinstall and also check file system and registry manually, before reinstalling)

Same error I received back when. Honestly, I fiddled with so many things to get everything working - I'll have to review my notes to see if I can offer additional steps I took, but I remember copying my plugins to a new folder and wiping avisynth+ (there was a second version somewhere too) delete them all, reinstall, copy plugins64+ over, ensure .avs / .avsi accuracy. Hope this helps...

Thanks selur & bogie, I did try import, load plugin commands found online , had also tried to wipe everything and reinstall (4times), I had also set the folders in different location, created new user account and tried there.. i have only 64bit avspmod installed. Everything I got was x64, except vd.1.9.11+filters from here (for capturing) , and vd2 in both 32/64 (using x64). Today i am having new errors, this time in avspmod when trying to preview (same script no changes), nothing changed to my pc, This is the error : AVISource: couldn't locate a decompressor for fourcc HFYU (C:users\........\deinterlace.avs, line1).. since i don't know how to check things in registy, and to be more precise, what to look for and where, I believe it would be better to proceed with formating the computer

-- merged --

I have managed to fix (with the help of google AI thing...) BOTH issues of AvsPmod not previewing and throwing back the error "AVISource: couldn't locate a decompressor for fourcc HFYU" AND the "Script error: There is no function named 'QTGMC'" while draging+droping the avs script in VirtualDub(2).

1) To fix the QTGMC script error turned out to be that I had placed on my desktop the shortcut/link towards the wrong .exe (VirtualDub.exe)....:smack: Changed it from VirtualDub.exe to "VirtualDub64.exe" now and it's working.

2) To fix the preview error in AvsPmod(x64) is takes longer because the fix to it, has to be done in a way to preserve the ability of virtualdub(1.9.11+filters) to capture while using the huffyuv compression method. What I mean is that we need both 32&64bit huffyuv.dll's. This is tricky and I will write the steps in sequence so no confusion will be made.

A) I headed to C:\Windows\System32 and deleted the HUFFYUV.DLL
B) I headed to C:\Windows\SysWOW64 in order to delete another HUFFYUV.DLL but there was no dll there
(the reason is whenever you install a 32 or a 64 bit huffyuv.dll with right clicking the .inf file it came with, it goes automaticaly to the system32 folder)
C) Downloaded from https://www.videohelp.com/software/HuffYUV both huffyuv versions (32&64)
D) Then I extracted the 32 bit zip (do not right click->install the.inf), and placed manually the huffyuv.dll at C:\Windows\SysWOW64
E) Then I extracted the 64 bit zip (do not right click->install the.inf) and placed manually the huffyuv.dll at C:\Windows\System32

Opened registry editor as an admin and did the following changes:

F)Go to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32 and find the VIDC.HFYU (which was missing in my case and i had to create it with right click-new string and name it) and then double click it and change the value data from huffyuv.dll to C:\Windows\SysWOW64\huffyuv.dll

G)Lastly HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 find VIDC.HFYU double click it and change the value data from huffyuv.dll to C:\Windows\System32\huffyuv.dll

That's it.. It worked for me and hopefully it will help others having the same problems.. This method seperated and installed the different vesion .dll's to their appropriate setup path, the x32bit .dll for vd1 at SysWOW64 folder and the x64bit .dll for AvsPmod at System32 folder. The registry value changes was for the applications to know where to head by path name and use the dll version that was meant for them.

another thing that AI said is that this can be fixed also with the hofmand's msi installers which i didn't try.

an extra bonus fix that i have now is in vd1 under the compression menu the huffyuv2.1.1 option is available, but before there wasn't

Excellent job, George. I also had several issues multiple times with huffy codec not showing up in V-dub, different versions showing up in Vdub1.9 vs Vdub2. I couldnt tell you how I fixed everything, it just took alot of fiddling around - and your fix method looks solid - I'm saving the info for later given I've had issues crop up after months of everything working, so your steps may help me in the future and others. Many thanks for clearly outlining what you did (I should have done the same each time I fixed one of my many issues I've encountered...) Well done!