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

[quantum5uicid3]

nvm it's pointless

[Buggle]

Is there any news on the non-monotonic bug experienced in x264 yet? Judging from the reactions in the thread on doom10, it was supposed to be caused by AVS64.

[Stephen R. Savage]

The real question is where JoshyD went. The project is essentially dead without him, as he was the only developer. Last I heard, he was rewriting the resize code to fix the PTS warning.

[cretindesalpes]

I also asked him to send me the source code of a few plug-ins (as he doesn't publish the modified source code, whatever the original plug-in license) two weeks ago, and still no reply...

[Underground78]

I also asked him to send me the source code of a few plug-ins (as he doesn't publish the modified source code, whatever the original plug-in license) two weeks ago, and still no reply...

"Last Activity: 23rd May 2010 08:18"

[Didée]

Yeah, the pace of development has broken down noticeably ...

One thing I'm still missing on the side of plugins is: Median-filtering (spatial and temporal). Here are two rough scripts that mimick two not-yet-ported-to-x64 filters:

TemporalMedian1 is, big surprise, a radius=1 temporal median filter (like MedianBlurT(0,0,0,1) or Clense(reduceflicker=false)

ScriptedFluxSmoothT is, big surprise, a scripted version of the FluxSmoothT filter.

For the moment, both filters support only YV12 input. Lunchbreaks are short.
YUY2 will be added somewhen later, maybe also RGB. Also radius=2 temporal median, by using the nice Median2 script (http://forum.doom9.org/showthread.php?p=1169990&highlight=median2#post1169990) of g-force.

function TemporalMedian1(clip c, int "Y", int "U", int "V")
{
Y = default(Y,3)
U = default(U,2)
V = default(V,2)
p1 = c.selectevery(1,-1)
n1 = c.selectevery(1, 1)
mt_logic( mt_logic(c,p1,"min",Y=Y,U=U,V=V),
\ mt_logic(c,n1,"min",Y=Y,U=U,V=V),
\ "max",Y=Y,U=U,V=V)
mt_logic( last,
\ mt_logic(p1,n1,"min",Y=Y,U=U,V=V),
\ "max",Y=Y,U=U,V=V)
}


function ScriptedFluxSmoothT(clip c, int "th")
{
th = default(th,7)
diff1 = mt_makediff(c,c.TemporalMedian1(3,3,3),U=3,V=3)
diff2 = mt_makediff(c,c.TemporalSoften(1,th,th,255,2),U=3,V=3)
DD = mt_lutxy(diff1,diff2,"x 128 - abs 1 < 128 y ?",U=3,V=3)
c.mt_makediff(DD,U=3,V=3)
}

Better to have something, than nothing at all.

[pokazene_maslo]

Hello, I found a strange bug. First of all here is my avs script:global MeGUI_darx = 31
global MeGUI_dary = 17
LoadPlugin("D:\Install\meGUIx64\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("D:\work\VIDEO_TS\VTS_01_1.d2v", info=3)
LoadPlugin("d:\Install\meGUIx64\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, interlaced=true, threads=0)
LoadPlugin("D:\Install\meGUIx64\tools\avisynth_plugin\TDeint.dll")
TDeint(full=false)
fft3dGPU(sigma=2.2, precision=2, sharpen=0, plane=4)
trim(188903,0)

when i try to open this script in megui following error will come up: "MeGUI encountered a fatal error and may not be able to proceed. Reason: attempted to read or write protected memory. This is often an indication that other memory is corrupt."
opening this script in virtual dub is fine until I start playback then this error will come up: "Avisynth read error: Avisynth: unknown exception."
When I disable TDeint in that script everything is running fine. When I disable fft3dgpu and leave Tdeint enabled everything is running fine.
Seems like those two filters don't like each other :)

[SaintDeath]

Well I know i am new to these been reading alot in the forum. but i would like to request 64 bit of these 32 bit dlls.

Deen
TemporalCleaner
SangNom
nnedi

[kjh7232]

I downloaded ffms2.dll and ffmsindex.exe x64 ver from this thread and ffms2.avsi from ffms2 project. but I got a error when use "FFmpegSource2". This error is 'There is no function named "ffindex"'. Why This problem happened?

P.S Sorry for my bad English ;)

[Alf Bundy]

I think the function's name is

FFvideoSource() #for video
FFaudioSource() #for audio

At least, it is with the 32bit version of ffms2 ...

[onesloth]

I downloaded ffms2.dll and ffmsindex.exe x64 ver from this thread and ffms2.avsi from ffms2 project. but I got a error when use "FFmpegSource2". This error is 'There is no function named "ffindex"'. Why This problem happened?

P.S Sorry for my bad English ;)

You need to load the 64-bit ffms2.dll with LoadCPlugin() in the beginning of the script.

[Alf Bundy]

I have a dumb problem : I've just installed Avisynth x64 and all is working fine (preview of my scripts with VDx64 & encoding them through MeGUI x64). :)

But sometimes I use plugins which don't have a x64 version yet. Unfortunately it seems that I can't use avisynth 32bit anymore.
If I add a 32bit-only plugin in my script, both VD x32 & x64 complains ! :(

VDmod 32bit says : AVI import filter error (unknown) (80040154)
VD x64 says : LoadPlugin : unable to load "C:\Program File (x86)\AviSynth 2.5\plugins\blockbuster.dll"

I tried LoadPlugin, LoadCPlugin and Load_Stdcall_Plugin
If I remove the 32bit plugin, the script is loading fine again in VDx64.

Is there some basic information that I missed when reading this topic ?
Because I wanted to use x64 when possible, but I didn't expected to lose the ability of using 32bit avisynth when needed.

[cegy]

someone should really change the title to x64 as it don't have anything to do with x86 nor is there is any x86 version of it aswelll !! :confused:

[Lyle_JP]

I have a dumb problem : I've just installed Avisynth x64 and all is working fine (preview of my scripts with VDx64 & encoding them through MeGUI x64). :)

But sometimes I use plugins which don't have a x64 version yet. Unfortunately it seems that I can't use avisynth 32bit anymore.

It's not a dumb problem, it's a dumb feature! :p

But seriously, x64 avisynth requires x64 plugins. No exceptions.

[Alf Bundy]

So it's not a mistake on my side, I can't use 32bit avisynth when x64 version is installed ?

That's good to know. So I won't have a headache figuring what I've done wrong.
And x64 version is easy and fast to uninstal/reinstall anyway, so when I'll need to use a 32bit plugin, I will temporarily uninstall avisynthx64.

Thanks.

[Stephen R. Savage]

someone should really change the title to x64 as it don't have anything to do with x86 nor is there is any x86 version of it aswelll !! :confused:

There's nothing wrong with the title. This thread is about Avisynth for x86-64.

So it's not a mistake on my side, I can't use 32bit avisynth when x64 version is installed ?

That's good to know. So I won't have a headache figuring what I've done wrong.
And x64 version is easy and fast to uninstal/reinstall anyway, so when I'll need to use a 32bit plugin, I will temporarily uninstall avisynthx64.

Thanks.

I'm using both versions simultaneously, and it works just fine. Which Avisynth version is loaded depends on whether the program you start is 32 or 64-bit. You just have to make sure your script is only loading 32 or 64-bit plugins and not a mix. Alternatively, you can use try/catch statements to make a script "cross-platform" which I detailed in this post (http://forum.doom9.org/showpost.php?p=1395050&postcount=395).


VDmod 32bit says : AVI import filter error (unknown) (80040154)


This error means that you have failed to install Avisynth 32-bit correctly.

[kjh7232]

You need to load the 64-bit ffms2.dll with LoadCPlugin() in the beginning of the script.

That works. thx :)

[cegy]

[QUOTE=Stephen R. Savage;1416218]There's nothing wrong with the title. This thread is about Avisynth for x86-64.

sure there is unless you can tell me where the x86 avisynth is for the users who want the x86 ?:confused: (the installer/install files are only for x64 this is what i am going on about !!!!)

the only thing on this forum i would class as x86/x64 is "Simple x264 Launcher" http://forum.doom9.org/showthread.php?t=144140

[Gavino]

@cegy
http://en.wikipedia.org/wiki/X86-64

[Alf Bundy]

This error means that you have failed to install Avisynth 32-bit correctly.

You're right, I did messed up Avisynth 32bit when installing x64 version.

My 64bit script worked fine in VDx64, I was happy, so I tried to drag & drop it in the main window of MeGUI.
But MeGUI told me "cannot find avisynth.dll".
That's where I made a stupid thing : I copied the 64bit dll in my Windows/sysWOW64 folder (thus overwriting the 32bit dll).

In fact it was a problem between Drag & Drop and MeGUI running with admin rights. It just doesn't work.
Instead I have to use the open dialog (CTRL+O) to browse for my 64bit script. This way the script is loaded correctly.

Long story short : I did a fresh clean install of AviSynth 32bit & 64bit, and now they both work simultaneously. :)

[Alf Bundy]

No, It looks fine enough.
I am not able to replicate a crash in x264 r1659 nor vdub 1.9.6 though.



Ah, I was unaware of MeGUI being this braindead (I never use it, since it has a history of irritating me to no ends with its consistent stupidities):
SWScale() does flag the video as being I420 instead of YV12 when outputting YV12 video.
(SWScale does not formally support YV12 itself, but due to the below reasoning this is not particularly an issue in most cases)

the difference between I420 and YV12 is simply
I420 is Y-U-V. YV12 is Y-V-U
- the chroma planes are simply swapped in memory
but the way avisynth handles acquiring the plane pointers, the above difference is generally unnoticeable.
for this same reason, ConvertToYV12() is a NOOP (No operation) when the video is I420 (in avs 2.5.x that is, in 2.6.0 looks like there might be a bug in this situation)

But it appears MeGUI is not capable of handling this properly either way, so I dare say to file a bug report to MeGUI.
It appears that you will not be able to use SWScale if you plan to use MeGUI due to the above, unless it fixes itself sometime rather soon

The same thing happens with FFvideoSource().
And I don't think we should blame MeGUI for that.
Flagging the video as being I420 instead of YV12 when outputting YV12 video is the problem.

When the Warning Dialog appears in MeGUI, we can hit the "Continue anyway" button, and we can encode the script without any further problem.
So it's not really a bug.

I guess the coders of MeGUI could remove the warning. But then, what would happen if someone try to encode a script which is really not YV12 ?

[kemuri-_9]

The same thing happens with FFvideoSource().
And I don't think we should blame MeGUI for that.
Flagging the video as being I420 instead of YV12 when outputting YV12 video is the problem.


I should've worded my statement more carefully:
FFVideoSouce()/SWScale() within ffms2 are both ffmpeg based.
anything and everything ffmpeg does not recognize YV12 as a valid colorspace, it only recognizes/supports I420.

so the video is I420 within avisynth, my previous statement of "flagging YV12 video as I420" is slightly incorrect:
what i was trying to say was more along the lines of
"the video is indeed I420, but within avisynth there's no real difference between I420 and YV12 past the point where the frames are created"

the difference can arise when dealing with Avisynth with the VFW interface,
but when working with the Avisynth through its own interface like x264 does, it doesn't matter as doing a isYV12() test returns true for both I420 and YV12.

[cegy]

@cegy
http://en.wikipedia.org/wiki/X86-64

ok you have a point there but still it says on there its 32bit (meaning there is both x86 and x64) when the installer is only for 64bit and not 32bit!!! he should add (x64) or (64bit) in the title as this is one big f*ck up other wise and can be very confusing so i'll quota a line for you

"Although most x86 processors used in new personal computers and servers have 64-bit capabilities, to avoid compatibility problems with older computers or systems, the term x86-64 (or x64) is often used to denote 64-bit software, with the term x86 implying only 32-bit."

p.s. my point will always stand untill the topic is changed or corrected :mad:

[kemuri-_9]

ok you have a point there but still it says on there its 32bit (meaning there is both x86 and x64) when the installer is only for 64bit and not 32bit!!! he should add (x64) or (64bit) in the title as this is one big f*ck up other wise and can be very confusing so i'll quota a line for you

"Although most x86 processors used in new personal computers and servers have 64-bit capabilities, to avoid compatibility problems with older computers or systems, the term x86-64 (or x64) is often used to denote 64-bit software, with the term x86 implying only 32-bit."


this topic says that this avisynth is for x86_64, in how any way does this conflict with your 'quote'?

code that is targeting the x86_64 architecture can only be executed by the x86_64 architecture alone.
code that is targeting the x86 architecture can be executed by the x86 and x86_64 architectures.


p.s. my point will always stand untill the topic is changed or corrected :mad:

[cegy]

code that is targeting the x86_64 architecture can only be executed by the x86_64 architecture alone.
code that is targeting the x86 architecture can be executed by the x86 and x86_64 architectures.


ok so where is the x86 (32bit) version of it then ?:eek: as the only thing i can see if links to only x64 (64bit):mad:

[Didée]

You are beating a dead horse.

A 32bit build to be executed under x86-64 is not needed. That is just the standard 32bit build.

The 64bit build to be executed under x86-64 is this thread's topic.

There is nothing more to it. You may stop it now.

[Atak_Snajpera]

ok so where is the x86 (32bit) version of it then ? as the only thing i can see if links to only x64 (64bit)
here you
http://forum.doom9.org/showthread.php?p=1412274#post1412274

[cegy]

here you angry boy (or girl)
http://forum.doom9.org/showthread.php?p=1412274#post1412274

thank you but you missed my point of where was it in this thread :p and this is why i am asking for the title to add (x64) to it at least to let users know its only for 64bit windows!

[Atak_Snajpera]

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

[Lyle_JP]

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

His vision seems fine. The problem is somewhere behind the eyes. To mister cegy, x86 means 32 bit, period. Which is wrong, of course, but no one seems able to sink that one into him.

[cegy]

His vision seems fine. The problem is somewhere behind the eyes. To mister cegy, x86 means 32 bit, period. Which is wrong, of course, but no one seems able to sink that one into him.

ahhh now your saying its x86 as in 32bit which is isn't is it ? as its only for 64bit thats why the installer and plugins on the first page is x64 only!

ps. check this http://forum.doom9.org/showpost.php?p=1390397&postcount=1 as you can see this person also says its x64 (grab the x64 avisynth from this thread)

[Atak_Snajpera]

x86-64 = 64 bit extension for old x86. So it is logical that this version will not work on 186 (16bit),286(16bit),386(32bit),486(32bit),586(32bit) and so on ... ;)

[Overdrive80]

Hi, fantastic job. My question is if you go to migrate all filters from x86 to x64, for in the list are not seen some as: TBilateral, TemporalDegrain ... Although it strikes me that are not necessarily convert AVSI files, only those who are dlls?

Thanks and sorry for the inconvenience

[cegy]

ok your right there but the last thing i will say from the wikipedia page it says
"x86-64 is still used by many in the industry as a vendor-neutral term, as is x64."
The x86-64 specification is distinct from the Intel Itanium (formerly IA-64) architecture, which is not compatible on the native instruction set level with either the x86 or x86-64 architectures.

[aegisofrime]

ok your right there but the last thing i will say from the wikipedia page it says
"x86-64 is still used by many in the industry as a vendor-neutral term, as is x64."
The x86-64 specification is distinct from the Intel Itanium (formerly IA-64) architecture, which is not compatible on the native instruction set level with either the x86 or x86-64 architectures.

What's your point? What the sentence you have quoted there means is that x86-64 is used to refer to the 64-bit extension to the x86 architecture in general. The reason for this is that Intel's name for x86-64 is Intel EMT64 and for AMD it's AMD64.

If JoshyD had used either of these vendor specific terms then people like you would be up in arms demanding that the title be changed!

[cegy]

What's your point? What the sentence you have quoted there means is that x86-64 is used to refer to the 64-bit extension to the x86 architecture in general. The reason for this is that Intel's name for x86-64 is Intel EMT64 and for AMD it's AMD64.

If JoshyD had used either of these vendor specific terms then people like you would be up in arms demanding that the title be changed!

ok so it should be intel ia-64/emt 64 or amd 64 (it still means you need a 64bit windows to run it or the intal ia of windows)

my point is vaild and still stand untill the title is correct also i won't be replying to any questions in this thread :mad:

[Guest]

Drop it cegy, you're starting to look like a troll. Followup to PM if you must.

[Chikuzen]

I found a bug.
I'm using latest version(build 4/16/2010).
Colorbars(320,240,"YUY2")
FadeIn(60)

http://img685.imageshack.us/img685/1357/fade32bitand64bit.png

A blackboarder appears left side when FadeIn(FadeIn0) is used with 64bit-AviSynth.

[Alf Bundy]

I can reproduce it.
And with FadeIO(), during the fade out the left border is in negative colors, not black.

[pokazene_maslo]

Alright, nobody was paying attention to my previous post so this time I prepared everything needed to reproduce the bug.
In zip is short sample of video I was trying to encode, d2v, avs script, and plugin that's causing crashes. Try it by yourself.

My setup: latest megui x64, avisynth x64 MT 4/16/2010, core 2 duo e6300.

http://hotfile.com/dl/54428190/eaf2166/sample.ZIP.html

[Alf Bundy]

Hi,

Is there a thread where I can politely ask for a plugin that is not yet compiled for x64 ?

I really miss Deblock (http://avisynth.org/warpenterprises/files/deblock_25_dll_20060214.zip) and BlockBuster (http://avisynth.org/warpenterprises/files/blockbuster_25_src_20021229.zip) in avisynth x64. :(

:thanks:

[Buggle]

I was wondering, since JoshyD seems preoccupied with matters other than AVS64 (which is completely understandable and he has every right to, of course), why is this code not merged with the main AVS branch/tree/whateveryoucallit? It seems somewhat inefficient to maintain two versions of the same origin. And it has become quite clear that there is a large crowd of people using and wanting to use full x64 capabilities, so it wouldn't really be a strange idea for the main developer(s) of AVS to also start paying attention to adjusting AVS to also include x64 out of the box, like x264 for instance now has for a while. Also, there seem to be so many filters compiled for x64, or even more and more. I'd even go so far as to say that 32bit is moving toward obsolescence: there is a good chance for instance that Win8 will only be available in a x64 edition. I for one support that; 32bit is lingering too long, while the transition from 16bit to 32bit was quite fast and almost painless, back then.

[kemuri-_9]

avisynth's compiler of choice is out-of-the box visual studio.
this version of avs x64 can not use visual studio out-of-the-box as it requires the use of Intel's compiler, which also costs a pretty penny to get.
You might ask "Why does it require Intel's Compiler?", the answer is "because of the inline asm which only Intel's compiler supports on x64."

and to my knowledge all that inline asm that was in avs x86 has been changed to to be for x64.
as long as there is inline asm in avisynth, this x64 version will forever remain incompatible with merging with the x86 version.

[asarian]

Also, there seem to be so many filters compiled for x64, or even more and more. I'd even go so far as to say that 32bit is moving toward obsolescence:.
That's a bit extreme. :) Gathering all the stuff for MCTemporalDenoise, for instance, not even half is available in x64 format. I guess we'll just have to wait a bit longer.

[muerteazul]

hi i try of install avisynth64_install.cmd but dont work it say "priviliges required" i install avisynth 2.5.8 before i think its for de xp x64 editon
some details
http://img9.imageshack.us/img9/123/capture07242010001538.jpg

[daimroc]

@Muerte Azul:

you must right click over the install.cmd and choose the option "execute as administrator" to be able to install it.

How you like to speak spanish for your nick, I tell you in spanish: para poder ejecutar el cmd con privilegios de administrador no tienes que hacer doble click sobre el cmd, sino pinchar con el botón derecho y elegir la opción de ejecutar como administrador.

___________________________________________________


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:

AviSynth64 installed. To auto load put 64 bit dll's in
C:\Program Files (x86)\AviSynth 2.5\plugins64

So I understand that this steps it's correct.

4) I havae copied all the dlls of the zip to plugins64, incluided avisynth.dll and devil.dll. I think that's this is not neccessary, so I have in system32, but I prefer to avoid problems.

5) I import avisynth.reg in the register. The import it's correct.

So I understand that I have installed all correctly.

I have used the following avs:

DirectSHowSource("myVideo.mkv")

I try to open this avs with media player classic home cinema x64 and I have no problems. Also, with virtualdub x64 I have not problems.

How ever, If I try to use virtualdubmod, that is a x86 version, I get the following error:

Couldn't locate decompressor for format 'YV12' (unkonwn).
VirtualDub requires a Video for Windows (VFW) compatible codec to decompress video.

However, if I try to open the avs with media player classic home cinema x86 I have not any problem, it uses ffdshow to decompress the video.

So Why can't use now avs with virtualdubmod?.



Thanks.
Daimroc.

[kemuri-_9]

don't use virtualdubmod, it is beyond 'out-dated' - it is completely ancient.
use the x86 version of whatever virtualdub you also have as the x64 version

[tormento]

I saw somebody compiled RemoveGrain and Repair for x64. As ReduceFlicker is from the same author, would be possible to get it for x64 too?

[Overdrive80]

I saw somebody compiled RemoveGrain and Repair for x64. As ReduceFlicker is from the same author, would be possible to get it for x64 too?

And Tbilateral?

[crasus]

Many appreciations to all the creators of the x64 avisynth developments. One does hope to see someday a native x64 2.6 version available (dreaming....)

Adding to the list of kind requests for 64bits compiles of certain filters, would it be possible to have tdeint & degrainmedian?

All the warmest very best!