VideoHelp Forum




+ Reply to Thread
Results 1 to 17 of 17
  1. I am trying to install TempGaussMC for use in de-interlacing SVHS videos that plan to capture with a ATI Theater 550 card I have in my Quad core 9550 system with 4GB of memory running Win XP Pro. I use MeGUI and have used it successfully with the YADIF filter that comes with the install package for MeGUI, but the results are unsatisfactory. I understand how to use the edit tab to edit the AviSynth script and have entered the following in an attempt to use TempGaussMC:

    AVISource("C:\Test.avi", audio=false)
    TempGaussMC_beta1()
    #deinterlace
    #crop
    #resize
    #denoise

    I get errors because of missing dependencies and have tried to install MVTools, Remove Grain and Repair, Mask Tools v2, and NNEDI2. However, after downloading these versions:

    MVTools-v1.11.4.5
    RemoveGrain-1.0
    masktools-v2.0a36
    nnedi2 v1.4

    I find I do not know how to place all the dll's in the proper places in the Avisynth 2.5\plugins directory.

    nnedi2.dll seems to just get copied into the plugins dir, same with mvtools.dll, but masktools has two dll's and some other files in it I that I do not know what to do with...all into the plugins dir or what? RemoveGrain has 12 dll's in it. Do these all get copied to the plugins dir? How do I know I have compatible versions of each of these? Do I need to edit anything in these files for my particular project?

    Also, what is the difference between TempGaussMC_beta1 and TempGaussMC_beta1mod? I have both.

    In short, I have been unable to find step by step instructions for setting up TempGaussMC. I have been trying to get this to work on my own by reading individual posts and the limited info in the avisynth wiki. It is taking too long that way. Would someone be willing to post the detailed steps to set up TempGaussMC with its dependencies for quad core operation? Thank you.
    Quote Quote  
  2. The .dll's go into the plugins directory, the other files like text files etc... don't matter

    beta1mod uses then newer masktools version, multithreaded and is marginally faster. Both .dll versions can coexist in the plugins directory, you will find some filters rely on 1 version or the other

    If you are using nnedi2, it has to be specified in the edimode (otherwise eedi2 is the default, and that is a requirement as well)
    TempGaussMC_beta1(edimode="nnedi2")

    This is a bobber, so you will get 2x the framerate of a single rate deinterlacer, and it's very slow, and poorly multithreaded (doesn't make use of multicores very well)

    If you still have problems, post the exact error message avisynth or the preview is giving you
    Quote Quote  
  3. Member
    Join Date
    Jul 2009
    Location
    Spain
    Search Comp PM
    As far as masktools is concerned, you should install only mt_masktools-25.dll, not mt_masktools-26.dll, which is only for the later, still experimental, Avisynth 2.6.
    Quote Quote  
  4. Member Soopafresh's Avatar
    Join Date
    Jan 2004
    Location
    United States
    Search Comp PM
    And the version of MVtools is important. I can't recall any longer, but I think it was a pre 1.x version that was needed on the single threaded version.

    It's probably the best deinterlacer out there, but it is too slow for real world applications. Also remember it is a bobbing deinterlacer, so your fps is going to double, as PDR mentioned.

    Edit: Looks like someone modded it to be multicore friendly. See here:

    http://avisynth.org/mediawiki/TempGaussMC

    Requires MVTools 1.9.7.7
    "Quality is cool, but don't forget... Content is King!"
    Quote Quote  
  5. GSpot shows my test.avi file codec is YUY2 and the name is YUV packed 4:2:2. I used GBPVR to capture the SVHS video input from my ATI Theater 550 card. I have misplaced the software that came with the card for capturing. Did I do my capture right, or should I have used something different to get another colorspace in my orignal capture?

    I got an error about the color space with ConvertToYV12 at the end of the script, I moved it to the line above TempGaussMC and it now is running. My 11 minute test clip shows it is going to take 3 hours to complete the first pass of the automated two pass mode in MeGUI. With YADIF this took 3 minutes. I expected very very slow, so I will live with it for my test clip. To get more speed do I just substitute TempGaussMC_beta1mod(edimode="nnedi2") for TempGaussMC_beta1(edimode="nnedi2") in the script below? Seeing as how I may have wait until tomorrow morning to find out if this worked, can someone tell me if my script is correct and will give me a good output?

    AVISource("C:\Test.avi", audio=false)
    ConvertToYV12()
    TempGaussMC_beta1(edimode="nnedi2")
    #crop
    #resize
    #denoise
    Quote Quote  
  6. Member Soopafresh's Avatar
    Join Date
    Jan 2004
    Location
    United States
    Search Comp PM
    Read the TempGaussMC_beta1mod avsi file. At the top it'll explain how to use more procs
    "Quality is cool, but don't forget... Content is King!"
    Quote Quote  
  7. Hmmm. I don't see anything different about the set up in the file for TempGaussMC_beta1mod. Maybe you just swap out the call in the avisynth script and that is it. Anyone?
    Quote Quote  
  8. Yep thats all , but you also need the mt version of mvtools, and specify MT=true

    Instead of wasting time, you could preview a few frames in your script in vdub or avsp, before encoding it. This should only take a few seconds (ok maybe a minute )

    If there is an error message, post it
    Quote Quote  
  9. Originally Posted by pshooper
    My 11 minute test clip shows it is going to take 3 hours to complete the first pass of the automated two pass mode in MeGUI. With YADIF this took 3 minutes.
    You make a first pass using a lossless AVI codec, one such as Lagarith. Then you run the real 2 passes off of the Lagarith AVI (using AviSource in another script). It's a bit slower than using Yadif to begin with, but if making the Lagarith AVI takes 3 hours, and if encoding with Yadif before took 3 minutes, maybe the 2 passes will take around 6 minutes each, so 3 hours + 6 minutes + 6 minutes gives 3 hours 12 minutes, rather than the 6 hours you're looking at running both passes using TempGaussMC.
    Quote Quote  
  10. Manono, I am familiar with Lagarith, I can switch to capturing to that codec using a tool I have around here somewhere called amcap, but I don't understand what you are suggesting I do to shorten my times.
    Quote Quote  
  11. Originally Posted by poisondeathray
    Yep thats all , but you also need the mt version of mvtools, and specify MT=true
    I would change this statement in TempGaussMC_beta1mod.avsi

    MT = default( MT, false )

    to

    MT = default( MT, true )

    correct?

    How do I know if I have the mt version of mvtools?

    I am running MVTools-v1.11.4.5 now. Should I move to MVTools v2.5.8.1? Do I need to change anything else when moving to MVTools v2.5.8.1?
    Quote Quote  
  12. Yes, the MVTools 2.x branch is multithreaded, and as I said earlier, it can co-exist with the 1.x branch. Some older filters still rely on the old branch.

    If you change the actual avsi, I think that changes the default settings to use MT (not sure)

    What are your CPU/PC specs? It may actually make things slower if your listed specs are correct

    It will take you a few seconds to test out to preview a script. Just open it up in avsp or vdub. If it throws an error you know something is wrong. The error message will give you clues as to what is wrong.

    Since this filter is very slow, Manono is suggesting you deinterlace to a lossless intermediate, then use that lossless intermediate as a source for your final encode. If you do a 2pass encode, the filter is applied on both passes. When you have CPU heavy filters, this strategy significantly reduces overall time (almost 1/2).
    Quote Quote  
  13. Originally Posted by poisondeathray
    What are your CPU/PC specs?
    I was updating my profile while you were replying I'll bet. My profile now reflects my best machine, which I am using for this:

    Intel Quad 9550 2.83 Ghz
    Gigabyte X48-DQ6 MB
    4GB memory
    NEC ND3550A DVDRW
    300GB 10K Raptor Drive with Win XP Pro SP3
    (2) 1.5 TB Seagates for data
    ATI Radeon HD 2400 Pro 256 Mb memory (will upgrade this soon)
    ATI Theater 550 PCI card (I am wondering if I can do better than this for capturing analog inputs)

    Source deck for SVHS - JVC HR-S5912U

    I have a standalone BluRay player - Panasonic DMP-BD30, but no BluRay recorder.
    This project might change that, I really need to get this finished once and for all before all my old tapes are unrecoverable.
    I recently backed up (archived) all my original HDV tapes to DVD, I had to split the files with QuickPar and spread each tape across 4 DVD's. The cost of a BluRay recorder is getting to where it might be worth it to avoid that much busywork. But I digress...
    Quote Quote  
  14. Moved to another thread.
    Quote Quote  
  15. Originally Posted by pshooper
    I just realized that before I go to all the trouble of finding my registered AMCap program I should ask, what is the best software for capturing uncompressed video from analog sources?

    Is there something better than my ATI Theater 550 for capturing?

    I want to get all the quality I can out of these tapes so that I never have to go back to them again after this. This will be my archive for all time of them. I want to do this the best I can without spending a thousand dollars on it. (A few hundred would be okay if it really made a difference...)
    It might be a good idea to start a new thread on that particular topic
    Quote Quote  
  16. agreed.
    Quote Quote  
  17. Member
    Join Date
    Jul 2009
    Location
    Spain
    Search Comp PM
    Originally Posted by pshooper
    I would change this statement in TempGaussMC_beta1mod.avsi

    MT = default( MT, false )

    to

    MT = default( MT, true )

    correct?
    That would work, but rather than changing the code, you can just call it as TempGaussMC_beta1mod(..., MT=true).
    How do I know if I have the mt version of mvtools?

    I am running MVTools-v1.11.4.5 now. Should I move to MVTools v2.5.8.1? Do I need to change anything else when moving to MVTools v2.5.8.1?
    With MT=true, you need version 1.9.6.x or 1.9.7.x.
    I'm not sure if version 1.11.4.5 will work at all with the mod version. You may be better moving to v2.5.8.1 (and running without MT=true).
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!