SEt's Avisynth 2.5.8 MT compiled for *X86_64*, Latest Build 4/16/2010

[Alf Bundy]

Tdeint x64 already exists (see on first post)
DegrainMedian x64 already exists (here (http://members.optusnet.com.au/squid_80/), as seen on first post)

:)

[Hiritsuki]

Who can compile yeadif and dedup x86 to x64 version?
This two plugin is now I had used long time for Subteam working.
Thanks a lot.

[steamroller]

I'm not able to get avisynth x64 (the 4/16/10 build linked to from the first post in this thread) to work with MPC x64 although it works perfectly with x264 x64 and virtualdub x64. MPC x64 says Cannot render the file. I'm just trying a simple script.

DirectShowSource("test.avi")

Playing test.avi directly with MPC x64 works. It loads ffdshow x64.
I followed the installation procedure outlined in the readme included in avisynth64_4-16-10.rar.
Any ideas why this might be happening? Any way to fix this? Thanks in advance.

[infiniter]

I had several problems with the installation. I'm running W7 64 bit on a quad core Intel CPU.

1. PROCESSOR_ARCHITECTURE
The install script aborts because it detects x86 by the variable PROCESSOR_ARCHITECTURE. I found out that, when opening the extended system setting in My Computer, where the environment variables are, that variable is set to AMD64 by Windows. But when opening a console and listing those variables with the SET command, it is PROCESSOR_ARCHITECTURE=x86 and PROCESSOR_ARCHITEW6432=AMD64. So the script can't work.

OK, so I removed the corresponding line in the script.

2. BCDEDIT
I'm logged in as administrator and chose right-click and "Run as administrator" to run the script, but it brings out "Administrator privileges required" error. Investigating the script, I found this is caused by trying to run bcdedit.exe. From the administrator console, this command is unknown. Searching for bcdedit, it is found in a WINSXS subfolder. So it seems that running bcdedit as test for admin privileges is the wrong way.

After I removed the corresponding line too, the script worked.

[kemuri-_9]

there are two command prompt modes for x64 window systems.

there's x86 mode where the environment is primarily setup for running x86 programs, e.g. PROCESSOR_ARCHITECTURE=x86 and ProgramFiles points to the x86 directory.
%WINDIR%\system32 is automatically redirected to point to %WINDIR%\syswow64
this mode is generated by using %WINDIR%\syswow64\cmd.exe

then there's the x64 mode, where everything is primarily setup to run x64 programs where the variables are the 'normal' ones.
this mode is generated by using %WINDIR%\system32\cmd.exe or more generally cmd.exe from the search/run prompt in w7 and other systems

overall though, yes, the script is known to have issues but with the development at a stand still on development of avisynth x86_64, there's not much of a point in fixing it avisynth x86_64 is going to stay broken/incomplete.

[muerteazul]

hi i run the %WINDIR%\system32\cmd.exe and i copy de files of avisynth64_4-16-10 on syswow64 then i write avisynth64_install.cmd
enter and say 64-bit windows not detected

reply to daimroc
Well, I have problems to install avisynth64. I am following these steps:

1) I have installed avisynth x86 version 2.5.8.

2) I have copy devil.dll and avisynth.dll in c:\windows\systems32 directory.

3) I have execute avisynth64_install.cmd. I get the following message: up this step is the problem i try and dont works
i am the administrator and say "priviliges required"
y si hablo español soy mexicano

[turbojet]

The install script on google code has a bunch of problems with non-admin accounts and uac.

The script posted here (http://forum.doom9.org/showthread.php?p=1394453#post1394453) should fix infiniter and muerteazul problems. Please report if they don't.

JoshyD said he was going to include the fixed install script in a new version months ago but that never came to fruition.

[Eric L]

Great job guys, Avisynth x64 Rocks!

There is only one key filter missing to use mainstream it in my everyday workflow.

May I request an x64 version of the SmartDecimate (http://web.missouri.edu/~kes25c/smartdecimate_avisynthc.zip) filter corrected by Tritical? Sources are included in the download.

Thanks

[muerteazul]

Thanks turbojet Avisynth its instaled now
Gracias turbojet Avisynth esta instalado ahora gracias por esa vercion

[The_Paya]

Hello.

Here's an attempt at porting one of the filters I use in my scripts to x64 avisynth.

FluxSmooth_icc_x64.7z (http://www.mediafire.com/file/a0qkrq13l17dgsn/FluxSmooth_icc_x64.7z)

This is by no means a "well done" job, I've left the __asm inlines there, used the Intel compiler to avoid having to rewrite them into .asm files, and just renamed address operations to their (x64) r-conterparts where it made sense. IMHO, it's a miracle that it compiled without warnings, and that it worked afterwards.

The modified sources are included as well as 3 precompiled binaries, all done in VS2008 with ICC 11.1.060. One without any kind of weird optimizations, another with SSE4.1 and the last one with more weird optimizations. Needless to say, it's very unlikely that there would be any noticeable speed differences between each version, given most of the code is MMX/SSE2 assembler.

As a long time lurker and first time poster, I'd like to thank the community and these x64 builds (they work better than the 32bit ones in my box for some reason). :thanks:

Salu2,
Paya.

[Overdrive80]

Hello first of all to congratulate on this job. The second is a question maybe simple but I have not clear. If I install this version of avisynth filters could also use 32-bit? An example would be my code (I say this because the title says "for *X86_64*, Latest Build 4/16/2010"):

#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
#MERGE
#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-

DGDecode_mpeg2source("E:\DB_1\Opening\ope.d2v", info=3)+\
DGDecode_mpeg2source("E:\DB_9\53\53.d2v", info=3)

ColorMatrix(hints=true, threads=0)

#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
#DEINTERLACED is used FORCE FILM, ISNT NECESARY
#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-

#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
#CROOPING&RESIZE
#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-

D0=trim(0,2594).Crop(4,0,0,0).Spline64Resize(720,480)
D1=trim(2595,34718).Crop(6,0,-2,0).Spline64Resize(720,480)
D2=trim(34719,0).Crop(6,0,-2,-2).Spline64Resize(720,480)

UnalignedSplice(D0,D1,D2)

Tweak(sat=1.1)

#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
#FILTERED RENDERING
#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-

TemporalDegrain(degrain=2, ov=2, blksize=4)#temporal

Denoised=FFT3DFilter(sigma=2.1,bw=32,bh=32,ow=16,oh=16,plane=0,sharpen=0.5)#spatial-temporal

MCTemporalDenoisePP(denoised,settings="very low")

TBilateral(diameterL=5,diameterC=5,sDevL=1.300,sDevC=1.300,iDevL=7.000,iDevC=7.000,\
csL=1.000,csC=1.000,d2=false,chroma=true,kernS=2,kernI=2,resType=0)#spatial

LSFMOD(defaults="slow") #Si queremos mas sharpen pero lo relentiza aun mas

threads=6

x=(framecount()/threads)

A=trim(0,x)
B=trim(x+1,2*x)
C=trim(2*x+1,3*x)
D=trim(3*x+1,4*x)
E=trim(4*x+1,5*x)
F=trim(5*x+1,0)

c

Thanks.

[Didée]

No. 64bit Avisynth can not use 32bit plugins. That's why people frequently ask about porting this-or-that filter to x64.

[Overdrive80]

No. 64bit Avisynth can not use 32bit plugins. That's why people frequently ask about porting this-or-that filter to x64.

Ok, thanks for your answer, dream with possibility of that it was true ^^. Imagine that to use avisynth in x64 system up to speed processating, doesnt it?

[trevaaar]

Just built this if anyone's interested:

Yadifmod x64 (http://www.mediafire.com/?tj93hvxillp35gf)
Unfortunately I don't have ICL (it's built with VC2010) so I had to remove the inline MMX asm. The asm methods in PlanarFrame were replaced by the implementations in joshyd's memcpy_x64.asm file.

[LeXXuz]

Here's an attempt at porting one of the filters I use in my scripts to x64 avisynth.

FluxSmooth_icc_x64.7z (http://www.mediafire.com/file/a0qkrq13l17dgsn/FluxSmooth_icc_x64.7z)


Thanks. I will try it out. We could use more denoisers on x64. :)

[Hagbard23]

Please Help!

I get strange green frames now, when i use DGDecode64 (1.5.8) together with DGIndex 1.5.8 and AviSynth64 (Build 16/4/2010).

It seems to be a DGDecode64 Problem, because the green frames do NOT appear in the VOB-Files, nor in DGIndex (w/ VOB), nor in DGIndex when i load the Project file (->Reload d2v). I can reproduce this "bug" with all possible DVD's.

I'm trying around now for some hours - but i couldn't find a solution - maybe someone can have an eye on the DGDecode64 Source? I am not experienced enough for that...

Thank you very much...

BTW:Green Frames appear every second/third/fourth frame regulary (difficult to distinguish - VD doesn't progress frame by frame with this error) ...yes, and they are totally green... ;(...I used VirtualDub 1.9.9 x64 AND MPC-HC x64 (SVN 2235) - both with the same result - green flickering frames

P.S.: MOD16 is confirmed - resolution is (as almost any PAL DVD) 720x576

Sys:
i7 870
WinVista
Geforce 9500GT
4GiG RAM


€DIT:
NO Problems occur, when i demux the MPEG2 Stream(with DGIndex) and load it into AviSynth64 via DirectShowSource64

[aegisofrime]

Please Help!

I get strange green frames now, when i use DGDecode64 (1.5.8) together with DGIndex 1.5.8 and AviSynth64 (Build 16/4/2010).

It seems to be a DGDecode64 Problem, because the green frames do NOT appear in the VOB-Files, nor in DGIndex (w/ VOB), nor in DGIndex when i load the Project file (->Reload d2v). I can reproduce this "bug" with all possible DVD's.

I'm trying around now for some hours - but i couldn't find a solution - maybe someone can have an eye on the DGDecode64 Source? I am not experienced enough for that...

Thank you very much...

BTW:Green Frames appear every second/third/fourth frame regulary (difficult to distinguish - VD doesn't progress frame by frame with this error) ...yes, and they are totally green... ;(...I used VirtualDub 1.9.9 x64 AND MPC-HC x64 (SVN 2235) - both with the same result - green flickering frames

P.S.: MOD16 is confirmed - resolution is (as almost any PAL DVD) 720x576

Sys:
i7 870
WinVista
Geforce 9500GT
4GiG RAM


€DIT:
NO Problems occur, when i demux the MPEG2 Stream(with DGIndex) and load it into AviSynth64 via DirectShowSource64

I have come across this problem before. To fix it, try using Colormatrix. Like so:

MpegSource2(info=3)
Colormatrix(hints=true)

[Hagbard23]

No - as expected - colormatrix has nothing to do with this error.

I've tried your proposal out ... it's the same error as before :confused:

any suggestions?

€dit: Testing with ordinary 32Bit Binaries (Avisynth,VDub,DGDecode) results in perfect behaviour without any error...

I KNOW that it worked a few weeks ago with all 64 Binaries, but now i can't get rid of these green frames - what have i done wrong?

[aegisofrime]

No - as expected - colormatrix has nothing to do with this error.

I've tried your proposal out ... it's the same error as before :confused:

any suggestions?

€dit: Testing with ordinary 32Bit Binaries (Avisynth,VDub,DGDecode) results in perfect behaviour without any error...

I KNOW that it worked a few weeks ago with all 64 Binaries, but now i can't get rid of these green frames - what have i done wrong?

Hmmm that's weird. I had a similar problem with green frames flashing randomly, which I fixed with ColorMatrix :(

[Hagbard23]

Because noone in here seems willing to help me with the described bug, i find myself pushed to the 32Bit Binaries again - :confused:

BTW: The FPS are nearly equal, so i don't see real advantages in processing in 64Bit.

Maybe someone in here gets the same Bug sometimes...if it is fixed then, i will give 64Bit another try...

Its a pity...

[trevaaar]

It wouldn't happen to be HD content you're having trouble with would it? MPEG2Source has worked perfectly for all the DVDs I've done with Avisynth64 but gives all green output every other frame when doing a Blu-ray. Unfortunately I can't help with a fix since I don't know assembly.

[Hagbard23]

Nope - it didn't happen with Directshowsource64 + HD Content (x264 encoded to speak more detailed), nor did it happen with Directshowsource64+MPEG2 Stream. And -no- i am not as dumb to try loading HD-Content via DGDecode... ;)... Testing with DGAVCSource was not possible, since there is no free version ATM - the old version is too old for me, so i've thrown it away. (btw: "thanks" to Donald Graft for his capitalistic sense, being commercial is a "no-go" for me, and i will avoid using his tools as far as possible. Nevertheless he is technically an overwhelming coder but that's not enough actually, there are new coders with good "free" tools/plugins, which i would prefer)

The Problem is, that one can't use Directshowsource with (unindexed) MPEG2 Sources - severe Problems with the video-length would occur. So there is no way for me to load MPEG2-Content with AVISYNTH64 as long as i don't get DGDECODE64 working. (Except loading and converting every VOB one by one)

It makes me a little paranoid, because it worked a few months ago without errors and i would say i am well experienced with avisynth.
This error really disturbs me, because i don't see the cause for that.

That exactly is the reason why i switch to the 32Bit Binaries again.

Maybe there is a problem with the Multithreading function of the newest build of AviSynth64+DGDecode64, but i don't exactly know - my knowledge regarding Coding is really limited.

Why noone of the developers is responding my question? Am i too stupid or what? I'm starting to really believe in that... ;-(

It is really a pity, because i liked the 64Bit Project in here....

[kemuri-_9]

It seems like you're purposefully excluding ffms2 as a valid option, which does have a working x64 plugin version...
(no one's told me that it has issues specific to it that are not in the standard x86 version)

see the ffmpegsource thread for the binary link, unless you come up with some reasoning why it's not a valid option here.

[Stephen R. Savage]

Can FFMS2 actually load VOB sequences? I was under the impression that VOBs are not cut at frame boundaries but simply at the 1 GB mark, so loading each VOB individually would lose frames at the ends of the files.

[lych_necross]

I think you would have to demux the vob files first if you want to go that route. I've personally never loaded a vob sequence directly into ffms2 before. I always index first and use dgsource.

[kemuri-_9]

Can FFMS2 actually load VOB sequences? I was under the impression that VOBs are not cut at frame boundaries but simply at the 1 GB mark, so loading each VOB individually would lose frames at the ends of the files.

it depends on how you ripped the DVD/source:
on DVDs themselves VOB files are generally at the 1 GB mark, but there are options in some (if not most/all) rippers that allow for concatenating all the relevant split VOBs into a single resultant one.
if you are reading the 1GB split VOB files, then you will likely have dropped frames if you utilize ffms2 and thus is not a valid option, but if you concatenated all of them when you ripped to your HDD then it becomes valid.

[Blue_MiSfit]

Indeed. If you made the mistake of configuring your ripping software to leave the VOBs as 1GB each, you can usually get away with a simple binary concatenate... i.e.


copy /b vts_01_00.vob+vts_01_01.vob joined.vob


USUALLY. Not always :)

Re-ripping is probably a good idea... or DGDecNV which has native, up-to-date 64 bit binaries

[Boogerlad]

Could you compile the soundout filter to x64 as well?

[JoshyD]

I'm not dead yet . . .

Here's a test release (http://code.google.com/p/avisynth64/downloads/detail?name=avisynth64_8-29-10.rar&can=2&q=)

I've not done any testing beyond the resize code, which is what I've mostly changed.

It's been updated to actually save the volatile XMM registers that were causing some problems with x264.

I can't promise quick responses to anything, I've been extremely busy, sorry guys, hopefully this will tide everyone over for a bit.

[Lyle_JP]

I'm not dead yet . . .

Here's a test release (http://code.google.com/p/avisynth64/downloads/detail?name=avisynth64_8-29-10.rar&can=2&q=)

http://i73.photobucket.com/albums/i228/steady_thinker/banana5.gif

So glad it's not abandonware!!

EDIT: Okay, so I tested this new avisynth by resizing with Spline64 to a mod2 (not mod4) height, which works with 32-bit avisynth. It worked the first time I opened it, but the second time gave me this crash:

Problem signature:
Problem Event Name: APPCRASH
Application Name: MeGUI.exe
Application Version: 0.3.5.8
Application Timestamp: 4c6ae542
Fault Module Name: StackHash_2ef6
Fault Module Version: 6.1.7600.16559
Fault Module Timestamp: 4ba9b802
Exception Code: c0000374
Exception Offset: 00000000000c6df2
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Information 1: 2ef6
Additional Information 2: 2ef6e93bbf5e6d4df380510142a2d6b7
Additional Information 3: c756
Additional Information 4: c7562d668f76b39cc9466cba9c05d37a

[levi]

I'm not dead yet . . .

Here's a test release (http://code.google.com/p/avisynth64/downloads/detail?name=avisynth64_8-29-10.rar&can=2&q=)

I've not done any testing beyond the resize code, which is what I've mostly changed.

It's been updated to actually save the volatile XMM registers that were causing some problems with x264.

I can't promise quick responses to anything, I've been extremely busy, sorry guys, hopefully this will tide everyone over for a bit.

Awesome! Thanks for not giving up!!

[livetolove92]

Anyone upload ffms2 dll for me? Link in page 1 is dead.

[Didée]

Still there, it just moved in the folder hierarchy.

See? (http://kemuri9.net/dev/avs/ffms2/) ;)

[kemuri-_9]

Anyone upload ffms2 dll for me? Link in page 1 is dead.

I moved it so i could put it into a package.
sorry for the hassle.

[LeXXuz]

I'm not sure where to put my problem, since it works fine with my x86 system I thought to put it here.

Anybody managed to run ac3filter x64 with Megui x64/Avisynth x64 and DirectShow audio?

On my x86 sys everything's fine, no problem at all. On the x64 machine I cant get it to work. I installed ac3filter x64 and it is used and working in the system since MPC-HC x64 works with it just fine, but Megui/Avisynth doesnt. I've forced the use of DirectShow Audio in the encoder settings and already gave ac3filter a very high filter merrit but it does not work. The output file is very small, like 4MB while it should be 100 or more and is completely silent.

I dont know where to look anymore, I dont even know if avisynth's Directshowsource maybe uses some other (broken) decoder filter.

Would appreciate any ideo/help how I could fix this or how to find out which DirectShow audiofilter is used by Avisynth.

[Stephen R. Savage]

If you use GraphEdit or GraphStudio, you can build a custom filter chain and save it to a GRF file, which DirectShowSource will accept. The "Connect to Remote Graph" function in GraphEdit/GraphStudio is supposed to be able to determine what chain is being used in a running application, but I have never figured out how to use it.

[ajp_anton]

Could someone please compile a 64-bit eedi3 for me?
There appears to be a source code in the zip file (http://bengal.missouri.edu/~kes25c/eedi3.zip).

edit: Actually, nevermind that. I also need nnedi2 x64 to make 64-bit Avisynth useful...

[aegisofrime]

Could someone please compile a 64-bit eedi3 for me?
There appears to be a source code in the zip file (http://bengal.missouri.edu/~kes25c/eedi3.zip).

edit: Actually, nevermind that. I also need nnedi2 x64 to make 64-bit Avisynth useful...

You and everyone else. x64 NNEDI2 is the only thing missing in 64-bit TGMC... Unfortunately since it's closed source the only thing we can do is to wait for tritical to compile it...

[Prettz]

Hello.

Here's an attempt at porting one of the filters I use in my scripts to x64 avisynth.

FluxSmooth_icc_x64.7z (http://www.mediafire.com/file/a0qkrq13l17dgsn/FluxSmooth_icc_x64.7z)

This is by no means a "well done" job, I've left the __asm inlines there, used the Intel compiler to avoid having to rewrite them into .asm files, and just renamed address operations to their (x64) r-conterparts where it made sense. IMHO, it's a miracle that it compiled without warnings, and that it worked afterwards.

The modified sources are included as well as 3 precompiled binaries, all done in VS2008 with ICC 11.1.060. One without any kind of weird optimizations, another with SSE4.1 and the last one with more weird optimizations. Needless to say, it's very unlikely that there would be any noticeable speed differences between each version, given most of the code is MMX/SSE2 assembler.

As a long time lurker and first time poster, I'd like to thank the community and these x64 builds (they work better than the 32bit ones in my box for some reason). :thanks:

Salu2,
Paya.
Ahhhhh, nice. I've been hoping for an x64 port of FluxSmooth. (And Convolution3D.) It's pretty much my main denoiser... I still don't get why it isn't the same among many others.

I definitely can't promise I'll test this properly for you, but I think I'll start looking at the code right away -- I've been wanting to get my foot in the door on helping the Avisynth project. What better way to start than one of my dearest filters. I recently cut my teeth at making the jump from x86 to x86-64 assembly, so I'd love to look at the iSSE code and see if I can do anything to help rewrite it for the doubled number of XMM registers.

[levi]

I'm not dead yet . . .

Here's a test release (http://code.google.com/p/avisynth64/downloads/detail?name=avisynth64_8-29-10.rar&can=2&q=)

I've not done any testing beyond the resize code, which is what I've mostly changed.

It's been updated to actually save the volatile XMM registers that were causing some problems with x264.

I can't promise quick responses to anything, I've been extremely busy, sorry guys, hopefully this will tide everyone over for a bit.

No Problems with x264 now. Great Work! :thanks:

[royia]

Is there a 64 Bit version of yadif, or any other fast yet solid deinterlace plug in?

Is there a compatible MeGUI version to use with?

I wish many people will join to the development of this project to push AVISynth into the next level.

Thanks.

[Didée]

> Is there a 64 Bit version of yadif,

http://yo4kazu.110mb.com/

[royia]

I'm not dead yet . . .

Here's a test release (http://code.google.com/p/avisynth64/downloads/detail?name=avisynth64_8-29-10.rar&can=2&q=)

For daily use, would you recommend it?
I hope you get more time to work it out.

Thanks.

[STaRGaZeR]

Joshy, I PMed you some time ago asking for GradFun2DB x64's source code, can you share it please?

[jpsdr]

I'm not dead yet . . .
I've not done any testing beyond the resize code, which is what I've mostly changed.
It's been updated to actually save the volatile XMM registers that were causing some problems with x264.
I can't promise quick responses to anything, I've been extremely busy, sorry guys, hopefully this will tide everyone over for a bit.

This new release make QTGMC v2.46r crash, wich is working fine with 4-16-10 release.

[tschi]

Sorry if I am irrelevant with this thread, I don't really know if it could be solved by avisynth dev's or ffdshow dev's and where I can post it :confused:
Since rev2374 (DLL-Vulnerability fix) mpc-hc is not anymore compatible with avisynth script in ffdshow :(
http://forum.doom9.org/showpost.php?p=1431247&postcount=14424

[kemuri-_9]

Sorry if I am irrelevant with this thread, I don't really know if it could be solved by avisynth dev's or ffdshow dev's and where I can post it :confused:
Since rev2374 (DLL-Vulnerability fix) mpc-hc is not anymore compatible with avisynth script in ffdshow :(
http://forum.doom9.org/showpost.php?p=1431247&postcount=14424

This thread is for a specialized version of avisynth for x64.
Issues like that which are caused by external applications using/breaking avisynth by altering the windows DLL search path are outside of this thread's purpose.
you should take your complaints back to the mpc-hc thread(s)

[LeXXuz]

If you use GraphEdit or GraphStudio, you can build a custom filter chain and save it to a GRF file, which DirectShowSource will accept. The "Connect to Remote Graph" function in GraphEdit/GraphStudio is supposed to be able to determine what chain is being used in a running application, but I have never figured out how to use it.

I played around a little the last couple of days. Graphedit shows me the normal filter chain, same as on my x86 sys:

input => AC3 parser filter => AC3 filter > Output.

That made me suspicious. So I copied my x86 MeGui installation to my x64 system. And guess what: it worked as it should.

So I'm back to square one, having no idea why I can't use DirectShowAudio on Megui x64. Since AC3filter x64 is installed and properly used by MPC-HC x64 it's either a problem with Megui x64 or Avisynth x64 or both.

Would appreciate any ideas.

[GRKNGLR]

Hi,

When do you expect the x64 compilation of SangNom.dll? I can't use filters like LSF with Avisynth64. And one more thing... Can't Avisynth64 run 32bit filters?

[Didée]

Avisynth64 can not use 32bit plugins. That's why people ask for porting plugins to x64, after all.

You don't need SangNom for LSF. And for me, LSF works fine with Avisynth64. What problem do you experience?