Avisynth x64 MT install/user guide for clueless noobs

[Zoran]

Hello all,

I spent a few weeks with trying to get x64 MT avisynth running, but had no luck. I admit I am both not a programmer, nor was I familiar with avisynth up to two weeks ago.

I read about 200 pages of more and less relevant info, jumped back and forth through links pointing to other threads and ended up with 20+ tabs in my browser, half of which were the same.

I downloaded possibly all builds, both official and unofficial. Read all the packed readmes, guides I've found no this forum, unfortunately I am still not able to get it running ( The avisynth64_install.cmd tells me I am running 32bit though the system I use is win7 x64 so I tried to figure out what needs to be done by opening it in notepad. (at the moment even win media player won't open my recordings)

I am properly confused!

I would like to ask someone who knows how to do it, to create a guide - along with links to all the necessary base files (please - no links to existing forum posts as I had enough of those and my head hurts badly already ).

I am quite sure there will be a lot of newbies who will appreciate this just as much as I will!

Thank you very much in advance dear Gurus!

PS: I'd like to de-interlace, de-alias, and sharpen 1080i recorded TV Content (F1) for my own (actually my wife's) archive and viewing pleasure. Unfortunately with 32bit MT I only get less than 2 FPS with QTGMC that drives me crazy seeing only 3 cores are loaded out of 8.

[Atak_Snajpera]

go to next section avisynth development. in avisynth 2.6 mt there is my installer.

[Zoran]

You mean this?: http://forum.doom9.org/showthread.ph...26#post1568726

Is it 64bit?

[Atak_Snajpera]

forget about x64 . developers say that 64bit is very unfinished. also not all plugins are available for x64

[Zoran]

I explicitly asked for 64bit, as all the plugins I need are there.

32bit is working OK, but the most threads I am able to use is 3 because of memory limitations and I only get up to 2fps out of that.

I neeeeeeed 64bit and I am sure I am not alone, given the amount of 1080 content people are processing nowadays.

[Didée]

Back when I tried TGMC in 64bit, first I was all excited about the speed ( +15% or something).

However, I got pretty dis-excited when I noted that no TGMC-job in 64bit did ever finish. It always crashed after a few thousand frames.

[Zoran]

Did no memory tuning help at all?

EDIT: Maybe splitting long clips into shorter ones could help overcoming this too...
EDIT2: if per thread I get 15%+ and I can use all 8 threads (memory is no issue over here) that would be something...

I am willing to spend hours experimenting to get it running properly, so all my wife needs to do is trim the adverts, etc. and run a prepared script...
I need a working 64bit avisynth first, though

EDIT3: Also, if I am not mistaken, I can run parts (that would crash in x64) of QTGMC in 32bit and still enjoy the raised memory limitaions, more threads... (correct me if I am wrong)

[SEt]

No one maintains x64 build for a long time now. That's why it's buggy and totally unstable. You aren't forbidden to use it, but in current state don't expect it to do anything right.

[Selur]

the 15%+ is with all threads not just one,.. (also tested x64 Avisynth but gave up after to many scripts just died randomly,.. and I decided that the Speedboost isn't worth it, but the extra memory is really missed,..)

[MrVideo]

Originally Posted by Zoran

I neeeeeeed 64bit and I am sure I am not alone, given the amount of 1080 content people are processing nowadays.

Actually you don't. Here are my reasons for not deinterlacing the 1080i source.

1) For scripted TV content you want to IVTC it to 1080p23.976, i.e., restore the 2:3 pulldown formatted 1080i video back to 23,976 progressive video. That is a speedy process, done with a simple script:

LoadPlugin("C:\Program Files\DGAVCDecNV\DGDecodeNV.dll")
dgsource("e:\\video_file.dgi")
assumetff()
telecide(guide=1,post=0,y0=750,y1=1079)
decimate()

The y0 and y1 values are to tell AVISynth to not use video that potentially contains bugs/snipes so that it can accurately determine the whole frames.

On my 4-core Athlon X64 WinXP 32bit, I get about 6.7 fps during the 2nd pass.

Plus, you really do not want to deinterlace 2:3 pulldown 1080i video. IVTC is best.

2) For pure video 1080i sources you do not want to deinterlace and convert 1080i29.97 to 1080p29.97 because you throw away one-half of the spatial information. For example, if someone were to run from one side of the screen to the other and say that the resulting images showed that there were 8 fields of the person crossing the screen (yes, each of the 8 images would only contain 540 lines), deinterlacing would result in only 4 images of the person crossing the screen. Time spatial info is lost. I hate throwing away spatial info. But I've run into people who can't stand the jagged lines resulting from the motion. You lived with it all through NTSC analog days, so why the need to get rid of it now (not meant to be answered).

Unless your wife is heavy into reality programming (YUCK!), the video will fit #1 above. IVTCing the video will provide a much better result and take less time doing it.

[TheRyuu]

Originally Posted by Zoran

I only get less than 2 FPS with QTGMC that drives me crazy seeing only 3 cores are loaded out of 8.

QTGMC is like the one thing that actually works with SetMTMode and will scale up to 8 threads p. well. Even still SetMTMode and all of the MT stuff is basically a giant hack.

As for x64 the recommended method of installation is don't.

[SEt]

Please don't repost that. Author obviously have no idea about what he's talking.
I can agree that MTMode is hack, but I fear we have nothing better working atm.