View Profile
View Forum Posts
Private Message
Originally Posted by jagabo
Would you send me the "avsi" script file? i loved it ^^
+ Reply to Thread
Results 31 to 52 of 52
-
-
You can get QTGMC.avsi here:Originally Posted by yaston
http://avisynth.nl/index.php/QTGMC
You may also need to get the filters listed under Requirements:
http://avisynth.nl/index.php/QTGMC#Requirements -
But i've got a problem with the use of extern filter !!! how do i use it?
Also, "Yadif and Awarsharp" filters wouldn't work !! Look at the screen:
Last edited by yaston; 13th Jan 2015 at 02:52.
-
If your video is interlaced, you must deinterlace before resizing. If the source video is not YV12 to begin with, you should convert to YV12 before running any filters.
If interlaced:
If not interlaced:Code:ConvertToYV12(interlaced=true)
deinterlace and resize:Code:ConvertToYV12()
Note that 720x528 is an aspect ratio of 1.37:1 and is a non-standard frame size. For 4:3 aspect ratio it would be 720x536. Do you intend for this video to be PC playback only? That frame size cannot be encoded for DVD, BluRay, or AVCHD but it can be encoded to a square-pixel format like mp4. For most websites, it is not a suitable frame size for web display. What do you want to do with this converted video?Code:yadif() LanczosResize(720,528) aWarpSharp(depth=16.0,blurlevel=2)
Last edited by LMotlow; 13th Jan 2015 at 08:07.
- My sister Ann's brother -
Yadif isn't a standard Avisynth plugin. It needs to be loaded like this:Originally Posted by yaston
Load_Stdcall_Plugin("yadif.dll")
Or this:
LoadCPlugin("yadif.dll")
But not this:
LoadPlugin("yadif.dll")
Not all filters work with every colour space. Many are YV12 only. That'd be the format of much of the video most of us re-encode, but when it's not, you can convert it like this:
ConvertToYV12()
Or if it's interlaced:
ConvertToYV12(interlaced=true)
Do you have AVISynth installed? MeGUI can use it's own portable version of AVISynth but do you also have Avisynth installed? If you don't, it might be a good idea to install it. I'd go with Avisynth 2.6.0 Alpha 5 (not Avisynth 2.5.8). There's a link on this page.
When it's installed, you'll have an Avisynth Program Files/Plugins folder. I'm not 100% where it installs for newer versions of Windows, but for XP it'd probably be something like this:
C:\Program Files\AviSynth 2.5\plugins
It has absolutely nothing to do with MeGUI's avisynth_plugin folder. That could be anywhere, depending on where you unzipped MeGUI. Something like:
MeGUI_2418_x68\tools\avisynth_plugin
I'd probably leave the MeGUI avisynth_plugin folder for MeGUI to use. If you start adding and remove plugins yourself, you might end up deleting one MeGUI expects to find there.
When you download plugins, or scripts that use multiple plugins such as QTGMC, if you put the required plugins in the "installed" AVISynth plugins folder (not MeGUI's avisynth_plugin folder) they automatically load whenever AVIsynth runs. You don't need to load them with LoadPlugin() in a script in order to use them. If a script such as QTGMC has an avis extension, you can put it in the same plugins folder and it'll auto-load too.
You need to be a little careful. Multiple versions of the same plugin might cause problems, but plugins and avis scripts in the "installed" AVIsynth plugins folder will auto-load even if MeGUI is using it's own, portable version of AVIsynth.
Occasionally you'll come across an exception. Yadif is one of them. C-Plugins can't be auto-loaded so for Yadif, I'd leave it in the MeGUI plugins folder as MeGUI expects to find it there, and load it using Load_Stdcall_Plugin("yadif.dll") when you need it.
So.... if AVIsynth is installed and you want to use QTGMC, download the QTGMC.avsi script from here and put it in the "installed" Avisynth plugins folder. There's a link to a zip file labelled "Plugin Package with all Requirements". Use it to download the required plugins. Unzip it and follow the instructions carefully. Most of the plugins just get copied to the AviSynth plugins folder but I think there's a couple of folders in the zip file called "2.5 plugins" and 2.6 plugins". You'd copy only the plugins from one of those folders, according to the version of Avisynth you have installed. And you really should have Avisynth 2.6 installed, because then the plugins will be compatible with the portable version of Avisynth MeGUI uses.
There's also a "32 bit system files" folder in the zip file. Follow the instructions. The files in there need to be put in a Windows folder.
When you've done all that, you should be able to use QTGMC with it's default settings in a script like this:
QTGMC()
No need to load plugins manually (except maybe Yadif). If you get errors, you've probably done something wrong (not copied the files to the correct locations). -
Guys thank you so much huuuuuuuuug ♥♥♥
Just have a problem with "QTGMC()" i didn't understand how to use it... i foud "avis" file but it wouldn't work !! How ?? -
The post above yours contains fairly detailed instructions on how to install QTGMC and the required plugins. As Long as you have AVIsynth "installed" (not just the portable version that comes with MeGUI), otherwise you'll need to load all the required plugins manually every time you use it in a script.Originally Posted by yaston
If you can't get it to work, explain exactly how you installed everything and what's happening when you try to use it (any error messages etc) otherwise it'll be impossible to help you. If all you've downloaded is the QTGMC avis script itself, read the post above yours again for details regarding downloading and installing the required files. -
-
You need that avsi (located in Avisynth plugin folder) and , not sure, 14 or 15 dll's files, downloaded from links above, also put them into Avisynth plugin directory.
Avisynth loads everything that is in Avisynth plugin folder automatically while processing any Avisynth script, so you do not have to import that or load in avisynth script.
If all those files are not in Avisynth plugin folder, you'd need to load that avsi and all dll's files manually in your script, that would look like that:
where those paths are whenever those files sit on your hardriveCode:Import("C:\........\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\QTGMC-3.32.avsi") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\mvtools2.dll") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\RemoveGrainSSE2.dll") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\RepairSSE2.dll") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\mt_masktools-25.dll") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\nnedi3.dll") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\dfttest.dll") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\EEDI2.dll") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\FFT3DFilter.dll") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\nnedi.dll") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\nnedi2.dll") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\SSE2Tools.dll") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\VerticalCleanerSSE2.dll") LoadPlugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\AddGrainC.dll") Load_Stdcall_plugin("C:\.......\QTGMC 32-bit Plugins\Avisynth 32-bit Plugins\yadif.dll") #rest of your script
And I forgot, you need to put fftw3.dll and libfftw3f-3.dll into System32 or SysWow64 directory (depending on what your OS is: 32 bit or 64bit).
NOt sure 100%, but, if you do not do that last step, then placebo and very slow preset for QTGMC would not work, and also denoise and manual input variables do not work, script would not work, just simple QTGMC(Preset="slow") , QTGMC(Preset="medium") etc.Last edited by _Al_; 17th Jan 2015 at 10:09.
-
would you send me your own AviSynth Pluging coz mine is empty totaly
-
when someone offers a filter in here giving you tip and info in form of avisynth script, for example :
#loading clip lines
assumetff()
qtgmc()
#etc
it is up to you to decide what to gather so avisynth script works, sometimes you do not need to do anything, some lines in script are build in avisynth already, like assumetff() for example, but most filters might not be and you have to download them and put them into plugin folder or just load them into script as I mentioned. Use search engines, like download qtgmc etc. Problem is that that one is one of most difficult to make work, it is a code that includes 15 or so other filters ... you know in this avisynth world people build up upon someone else's work, so it can build up like that,
you test the script and reading what script tells you, if script is ready to run or is missing some filters or there is syntax error problem. Problem with Megui is that it reports NOT what avisyth error feedback would tell you, so you'd need to fish out avisynth script from hardisk that Megui creates and then just drop it onto MPC-HC player icon or VirtualDub icon on desktop, to see errors, and try to fix them or what you need to download,
in your case go into that page, http://avisynth.nl/index.php/QTGMC and look to top right corner and locate "Plugin package with all requirements". Some good person, remember in this instance, in Avisynth world, everything is freely available, it is not a commercially running thing, and that person gathered those all filters together for download at once. READ readme files, that is always first thing to do and follow instructions what to do with bunch of those files, I already mentioned above a bit. -
Well...good effort, _Al_, but at this point I don't think yaston knows how to find those QTGMC support files or what to do with them. I guess we're going to have to step back and get into very basic details.
@yaston:
Your Avisynth plugins belong in the plugins folder of your Avisynth program files They DO NOT belong on your desktop. They DO NOT belong in MEGUI. You should not have Avisynth plugins scattered everywhere in your system.
So, let's start again:
You already have a copy of the main QTGMC plugin, which is named "QTGMC-3.32.avsi". If it is not in your Avisynth\plugins folder at this time, remove the .avsi from its current location and move it into your Avisynth\plugins folder. In some versions of Windows such as XP, the Avisynth plugins folder is located in C:\Program Files\Avisynth 2.5\plugins. If you don't see Avisynth in that folder, then it will be located in C:\Program Files (x86)\Avisynth 2.5\plugins.
You should NOT download .zip or other compressed Avisynth plugins and filter packages directly to your Avisynth\plugins folder. If you do that, you will fill your plugins folder with junk you don't need. Instead, create a new folder on your hard drive and name the folder "Filters". Use this new "Filters" folder for your Avisynth downloads to keep them organized.
Inside your new "Filters" folder, create a new subfolder and name the new subfolder as "QTGMC". This new "QTGMC" subfolder will be the home for your QTGMC downloads. Later, you can create other subfolders in your "Filters" folder when you download other plugins that you want.
The QTGMC filter needs several supporting files. You can download a package of all QTGMC support files at this link: http://www.spirton.com/uploads/QTGMC/QTGMC%2032-bit%20Plugins.zip. The file that will be downloaded is named "QTGMC 32-bit Plugins.zip". Place that .zip file inside your "QTGMC" subfolder.
When you decompress the QTGMC 32-bit Plugins.zip file, you will see some new files and some new folders.
- A folder named "32-bit System dlls"
- A folder named "Avisynth 32-bit Plugins"
- A folder named "Source and Documentation"
- a small file named "gpl.txt"
- a small file named "READ_ME.txt"
For the present time you will not need anything in the "Source and Documentation" subfolder. But do not destroy it. It contains more detail and more information about each plugin.
Open the subfolder named "Avisynth 32-bit Plugins". Inside that subfolder you will find several files. One of the files is named "Where_to_put_these.txt". This .txt file is NOT an Avisynth plugin.
You will see 15 ".dll" files in this subfolder. The .dll files are Avisynth plugins. Copy all 15 of the .dll files into your Avisynth\plugins folder. Do not copy the .txt file. Do not copy the two subfolders that you see here. Copy only the 15 .dll files into your Avisynth\plugins folder.
After you copy all of the 15 .dll's into Avisynth\plugins, open the subfolder named "2.6x plugins". This small subfolder contains a .dll that matches your version of Avisynth, which is 2.6 Alpha 5. The name of the .dll inside the "2.6x plugins" subfolder is "mt_masktools-26.dll". This .dll is an Avisynth plugin. Copy the file "mt_masktools-26.dll" into your Avisynth\plugins folder. Then close the subfolder named ""2.6x plugins". You will not need any other plugins in the "Avisynth 32-bit Plugins" folder.
Return to your "QTGMC" folder where you placed the downloaded "QTGMC 32-bit Plugins.zip" file. Inside that "QTGMC" folder you will see a subfolder named "32-bit System dlls". Open the "32-bit System dlls" subfolder, where you will see 3 files:
- fftw3.dll
- libfftw3f-3.dll
- Where_to_put_these.txt
Take very careful note of the following statement: the two .dll files in this subfolder ARE NOT Avisynth plugins. DO NOT PLACE THEM in the Avisynth plugins folder. These two dll's are support files for the Windows operating system. They are not Avisynth filters. The small .txt file is not a plugin.
Open the .txt file named "Where_to_put_these.txt" and follow its instructions for copying the two Windows .dll files into your system folders. These two .dll's SHOULD NOT be copied into Avisynth\plugins.
That should complete the installation of QTGMC support files. All of the plugins are either .avsi files or dll's, so they should load automatically if they are in your Avisynth\plugins folder. The only dll that requires a manual load statement is yadif.dll, which hello_hello described earlier. Usually, you will not need yadif when running QTGMC. QTGMC can use yadif for very specific QTGMC processing modes, which you will not be using now.Last edited by LMotlow; 18th Jan 2015 at 03:44.
- My sister Ann's brother -
I've lost interest in trying to help. If you look at my post #35, you'll see I posted pretty clear instructions on how to install QTGMC (although not as detailed as yours). I provided a link to the page from which the zip file containing all the required plugins could be downloaded and instructions as to where they go (were my instructions particularly hard to follow?).Originally Posted by LMotlow
Proceeding that I explained how using the "installed" AVISynth plugins folder rather than MeGUI's plugins folder was preferable as it can be used to auto-load plugins, and I even explained which version of AVIsynth it'd be best to "install" so the plugins are compatible with the portable version of AVIsynth MeGUI uses.
Post #36 yaston says he doesn't know how to use QTGMC.
Post #37 I point him back to the instructions in post #35.
Post #38 and he's still just repeating he doesn't know how to use QTGMC (in a fairly terse manner), but at least we've finally been informed he does have AVIsynth installed, although no indication as to which version, and he's still got QTGMC.avsi in MeGUI's avisynth_plugin folder, not the AVISynth plugins folder as instructed.
Post #40 and now he's wanting someone to zip up their plugins folder and upload it, even though a link to all the required plugins in a zip file has already been provided (and more than once, I think).
Maybe there's a language barrier involved, but it's a pity yaston doesn't seem interested in putting in the same amount of effort to help yaston as everyone else has.Last edited by hello_hello; 18th Jan 2015 at 04:14.
-
Yep, I know. Thought I'd get to more step-by-step and consolidate stuff from earlier posts. The O.P. seems to ignore instructions, or just can't understand them. Language barrier, I suspect. I try to use simple king's english, because lots of American slang ain't translated very well. This is something like the merry-go-round with yaston in PM for several days. Ask for a script, you get a link to UTube. Ask for a sample, you get a different question. Ask to please post in the forum instead of PM, you get another question in PM.
Well, maybe some of it will sink in. Until yaston can get plugins loaded properly, he can't go to the next steps. Wait and see, I guess.- My sister Ann's brother -
Yep, you're right... i need to get it step by step some of it is unlcrear and some english words as well, but what should i do? you wouldn't PM me anymore...Originally Posted by LMotlow
Thank you guys for everything i apreciate it and i'll here if something got wrong ^^ -
Originally Posted by hello_hello
I've lost interest in trying to help. If you look at my post #35, you'll see I posted pretty clear instructions on how to install QTGMC (although not as detailed as yours). I provided a link to the page from which the zip file containing all the required plugins could be downloaded and instructions as to where they go (were my instructions particularly hard to follow?).Originally Posted by LMotlow
Proceeding that I explained how using the "installed" AVISynth plugins folder rather than MeGUI's plugins folder was preferable as it can be used to auto-load plugins, and I even explained which version of AVIsynth it'd be best to "install" so the plugins are compatible with the portable version of AVIsynth MeGUI uses.
Post #36 yaston says he doesn't know how to use QTGMC.
Post #37 I point him back to the instructions in post #35.
Post #38 and he's still just repeating he doesn't know how to use QTGMC (in a fairly terse manner), but at least we've finally been informed he does have AVIsynth installed, although no indication as to which version, and he's still got QTGMC.avsi in MeGUI's avisynth_plugin folder, not the AVISynth plugins folder as instructed.
Post #40 and now he's wanting someone to zip up their plugins folder and upload it, even though a link to all the required plugins in a zip file has already been provided (and more than once, I think).
Maybe there's a language barrier involved, but it's a pity yaston doesn't seem interested in putting in the same amount of effort to help yaston as everyone else has.
Believe me dear i'm trying to do my best to understand... i agree i have a poblem with english. but i got some informations
greetings guys -
Everyone realizes that you are making an effort. But I say again, PM is not the proper place to conduct projects. It is too limited, and other forum members cannot see answers and solutions in PM.
Many members from many countries use Google translate to translate from one language to another. The translations are not perfect, but they are helpful. https://translate.google.com/
If you cannot understand a language in the forum, you cannot understand the same language in PM.
You were asking in PM how to use MEGUI. I have not used MEGUI for many years, and the program has changed much since that time. But many members here use MEGUI and can help with that. Whether MEGUI is used or not, it depends on Avisynth. First, you have to learn to use Avisynth. You don't have to know how to use MEGUI to learn Avisynth. Avisynth is often used without MEGUI.
Which version of Windows are you using? XP? Windows Vista? Windows 7? Windows 8?
Have you copied QTGMC-3.32.avsi into your Avisynth plugins folder?
Have you downloaded the .zip file of QTGMC support files referenced earlier?
Have you copied the 15 dll filters into your Avisytnh plugins folder?
Have you copied the Avisynth 2.6 version of mt_masktools-26.dll into your Avisynth plugins folder?
Have you copied fftw3.dll and libfftw3f-3.dll into your Windows system folder?
The step by step instructions for doing this are in #35 and in #42.Last edited by LMotlow; 18th Jan 2015 at 22:16.
- My sister Ann's brother -
Have you seen how many replies are here?! just for easy things... that's what made asking for TeamViwer. Ok doesn't matter ^^
I'm using "Windows 7"
Look at here i did everything you told me:
And another point just see if i organized the filters properly
And by the way i loaded them on my own they didn't load automatically.Last edited by yaston; 19th Jan 2015 at 01:23.
-
But you did understand all of that post.Originally Posted by yaston
So it wasn't really that hard?Originally Posted by yaston
There are some files in the QTGMC "required plugins" zip file that don't go in the Avisynth plugins folder, so I assume they're in the correct location.
You don't need both mt_masktools-25.dll and mt_masktools-26.dll.
Auto-loading both is bad. Pick one according to the version of AVIsynth you have installed. Remove the other. I "think" you have Avisynth 2.6 installed, but look at the top of MeGUI's log file under "versions" if you're not sure.
Yadif cannot be auto-loaded. Don't put it in the AVISynth plugins folder. Put it somewhere else and load it manually.
Load_Stdcall_Plugin("yadif.dll")
QTGMC only uses Yadif for the very fast preset (I think) so you don't need to load Yadif most of the time.
Your script makes no sense by the way. QTGMC() de-interlaces. Yadif() de-interlaces. You wouldn't use both. Likewise you wouldn't use TFM() after de-interlacing.Originally Posted by yaston
"Auto load" doesn't mean the dlls are added to a script automatically, it means they don't need to be loaded in a script. A simple example would be using SmoothD. If the dll is not in the AVIsynth plugins folder you can't use it without loading it in a script, so to get it to work, you need to do this:Originally Posted by yaston
LoadPlugin("C:\Folder\Another Folder\SmoothD.dll")
SmoothD(2,4,0,1)
When SmoothD.dll is in the AVIsynth plugins folder and auto-loading, all you need to use SmoothD in a script is this:
SmoothD(2,4,0,1)
The same applies to all the plugins QTGMC requires (except Yadif). When they're auto-loading, all you need to add to a script to use QTGMC is this:
QTGMC(preset="fast")
MeGUI will still use LoadPlugin() to load plugins it requires when it creates a script as it has no way of knowing if they're also in the "installed" AVISynth plugin folder and auto-loading, but that's okay.
I strongly recommend you tell MeGUI to use it's own portable version of AVISynth. There's an option in settings. It's a little faster than the "official" AVISynth and there's some situations where MeGUI's script creator gets a little buggy when an "installed" version of AVISynth is used.
Even when MeGUI is using it's own version of AVISynth, all plugins in the "installed" AVIsynth plugins folder will still auto-load. That's why it's a good idea to have it installed even if you're only using MeGUI to open scripts.Last edited by hello_hello; 19th Jan 2015 at 03:04.
-
Ok, now seems clear ^^
just want to know how do i organize the codes: like "QTGMC(preset="fast")" and "SmoothD(2,4,0,1)"....ect exactly?
You can show me a screen to be more clear -
true. yadif is required with QTGMC for the "Ultra fast" preset.Originally Posted by hello_hello
The current MEGUI (v.2507) comes with Avisynth.dll 2.6.0.5.
yaston is using MEGUI v.2418, which comes with Avisynth.dll v2.6.0.4.
If code is displayed as a picture, we cannot copy the code. Copy text into the forum.Originally Posted by yaston
We thought you wanted 720p. 700x400 is not 720p.Code:Import("C:\Program Files (x86)\Avisynth 2.5\plugins\QTGMC-3.32.avsi") LoadPlugin("C:\Program Files (x86)\Avisynth 2.5\plugins\mt_masktools_26.dll") LoadPlugin("C:\Program Files (x86)\Avisynth 2.5\plugins\mvtools2.dll") LoadPlugin("C:\Program Files (x86)\Avisynth 2.5\plugins\RemoveGrainSSE2.dll.dll") LoadPlugin("C:\Program Files (x86)\Avisynth 2.5\plugins\RepairSSE2.dll") LoadPlugin("C:\Program Files (x86)\Avisynth 2.5\plugins\dfttest.dll") LoadPlugin("C:\Program Files (x86)\Avisynth 2.5\plugins\EEDI2.dll") LoadPlugin("C:\Program Files (x86)\Avisynth 2.5\plugins\FFT3DFilter.dll") LoadPlugin("C:\Program Files (x86)\Avisynth 2.5\plugins\nnedi2.dll") LoadPlugin("C:\Program Files (x86)\Avisynth 2.5\plugins\nnedi.dll") LoadPlugin("C:\Program Files (x86)\Avisynth 2.5\plugins\nnedi3.dll") LoadPlugin("C:\Program Files (x86)\Avisynth 2.5\plugins\AddGrainC.dll") LoadPlugin("C:\Users\Yacin0\Desktop\MeGUI_2418_x86\MeGUI_2418_x86\tools\avisynth_plugin\SmoothD.dll") LoadPlugin("C:\Users\Yacin0\Desktop\MeGUI_2418_x86\MeGUI_2418_x86\tools\avisynth_plugin\awarpsharp.dll") DirectShowSource ("C:\Users\Yacin0\Desktop\aa.ts", pixel_type="YV12") #deinterlace #crop AssumeTFF().QTGMC(preset="fast") Tweak(hue=5,sat=1.5,bright=-5,cont=1) SmoothD(2,4,0,1) LanczosResize(1280,720) # Lanczos (sharp) #denoise awarpsharp(depth=10, blurlevel=2) Sharpen(0.12, 0.12, MMX=false)
700x400 is not a valid size. It is not 16x9. The width cannot be divided by 8.
16x9 720p (1280x720)
Small 16x9 (856x480)
Smaller 16x9 (712x400)
If you want to encode standard HD (PAL) use 1280x720.
If you want to encode standard DVD (PAL), you must make more changes.- My sister Ann's brother -
There's not too many rules. Mostly it's up to you to decide. The filters are applied in the order they're included in a script, so......Originally Posted by yaston
QTGMC()
Spline36Resize(720,400)
would de-interlace first and resize second.
If there's any rule, it'd be to de-interlace before you do anything else.
That's just a basic example. I tend to use as little filtering as possible, but it's personal taste. Whatever order they're listed in the script is the order they'll be applied, so experiment if need be. But less is more. Don't filter a video to death because you can.
QTGMC is quite good at stabilising the picture and removing noise (it's not great for animation but for film and video it is). It also tends to de-block a bit, especially if it's noise removal is enabled. I'd rarely use a seperate deblocking filter and most of the time you probably wouldn't need one anyway.
If the video is interlaced, de-interlace with QTGMC as you normally would. Specify a speed preset if you want to, and if the video is noisy, maybe try QTGMC's de-noising before anything else. You generally only need low values. So QTGMC deinterlacing, fast preset and a little de-noising might look like this:
QTGMC(Preset="Fast", EzDenoise=1)
I use QTGMC for noise filtering progressive video quite a bit, so if it doesn't require de-interlacing, you could do this:
QTGMC(InputType=1, Preset="Fast", EzDenoise=2)
I noticed you're using DirectShowSource to open video in your script. It's not the best method, especially with more complex filtering. When you first open a video with MeGUI it should ask how you want to open it. Choose the File Indexer. Add the indexing job to the queue and run it. When it's done the script creator will open. For MKV it'll probably use ffms2 to open the video. It's more reliable than DirectShow. So the video would be opened something like this:
LoadPlugin("C:\Program Files\MeGUI\tools\ffms\ffms2.dll")
FFVideoSource("E:\video.mkv, fpsnum=25, fpsden=1, threads=1)
Use the script creator to crop and resize etc, and if need be use it to analyse the video to see if it needs de-interlacing, then from there you can make your own changes to the script. It's up to you.
Quote