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

[Alf Bundy]

Originally Posted by kemuri-_9

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]

Originally Posted by Alf Bundy

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]

Originally Posted by Gavino

@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

[kemuri-_9]

Originally Posted by cegy

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

[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 ? as the only thing i can see if links to only x64 (64bit)

[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.ph...74#post1412274

[cegy]

Originally Posted by Atak_Snajpera

here you angry boy (or girl)
http://forum.doom9.org/showthread.ph...74#post1412274

thank you but you missed my point of where was it in this thread 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]

Originally Posted by Atak_Snajpera

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]

Originally Posted by Lyle_JP

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?...97&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]

Originally Posted by 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.

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]

Originally Posted by aegisofrime

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

[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)

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