Log in

View Full Version : AVIsynth v1.0 Beta 6???


Pages : [1] 2

civ
25th February 2002, 14:13
Hi

Does anyone know if this is an offical version.

I found this version on my work computer, I generally install alot of tools/programs for testing. And some program must of installed this file.

When I put 'Version' on a single line is an avs file, it displays v1.0 Beta 6.. I also had some issues with b5 where it would gen an access violation on some clips, after copying b6 to my home comp. Those clips don't gen access violation anymore.

Also, have anyone had a problem with VirtualDub where when they loaded an avs for encoding it said something about 'Empty FPU state'

Guest
25th February 2002, 14:50
There are no "official" versions, because Ben is no longer active and several groups are making releases. I seem to recall someone made a fix to beta 5 and released it as beta 6. I suppose the closest thing to official we have now is videotools.net.

VirtualDub reports when it detects that an emms instruction has been omitted. It probably means one of the filters loaded in your AVS is MMX optimized but the author has forgotten to reset the multimedia state. It's not likely in VirtualDub itself because Avery never forgets stuff like that. :)

trbarry
25th February 2002, 19:10
Also, have anyone had a problem with VirtualDub where when they loaded an avs for encoding it said something about 'Empty FPU state'

No, I haven't, but there have been a few reported problems possibly related to this. From your post I'm not sure which version of Avisynth you were running when you got this. Could you say?

- Tom

midi
25th February 2002, 19:34
I was searching the avisynth egroups just yesterday unsuccessfully trying to get MaskedMix from mpeg2dec working and saw a b7 version as well. I'll just quote the message in case there's any interest:


From: Ole Hansen <ole@r...>
Date: Tue Dec 4, 2001 12:55 pm
Subject: Avisynth 1.0beta7 available - includes ConvertFPS filter

Thanks to Edwin who has given me write-access to Avisynth on Sourceforge.
I have added some of the fixes and improvements that were recently posted
here:

- Resize filter fix (EMMS) from Avery
- RGB fixes from Brad
- Brad's Greyscale() and RGBAdjust() filters
- Blur() and Sharpen() with two arguments, also from Brad, but
with the second argument optional.

Also, I have included a new filter called ConvertFPS() which allows a
smooth frame rate conversion between NTSC and PAL.

Binary and source can be downloaded from

http://members.home.com/hansenjo1/avisynth-1.0b7.zip
http://members.home.com/hansenjo1/avisynth-source-1.0b7.zip

A description of the ConvertFPS() filter is here:

http://members.home.com/hansenjo1/ConvertFPS.html

I will see that these releases will appear in Sourceforge at some point.
The main stumbling block right now is the presence of a closed-source
component.

Maybe Edwin can mirror these versions at videotools for now?

Cheers,
Ole

civ
25th February 2002, 22:36
Thanks for the info guys

trbarry, I got the 'Empty FPU state' using beta 5, but once I install beta 6 the problem was gone.

The filters I was using in the script wasn't anything special, I had something like:

AVISource("clip.avi")
ResampleAudio(44100)
Crop(2,2,716,572)
BicubicResize(b=0,c=1,480,576)

This would give me the error, but if I took our the Crop and Resize it worked fine.

Guest
26th February 2002, 01:27
As I mentioned, the BicubicResize() in beta 5 is missing an "emms" call.

civ
26th February 2002, 03:25
You didn't mention it was "BicubicResize()"

Guest
26th February 2002, 04:44
True. The "As I mentioned" referred to the fact that I had already posted that one of the filters must have been missing an "emms" call, which accounts for the "empty FPU state" message.

ARDA
26th February 2002, 21:45
As this thread was about new versions of avisynth.I will go on about it.
I was looking in sourceforge and I've found all modifications that were reported here, in the cvs,more precisely most of them in effects.cpp .Those releases that has been pointed are from one of the developers page.
I was looking specially the RgbAdjust that has similar name to neuron2 filter and in a fast sight it is has also a similar behaviour; except for a fourth parameter that I didn't understand what is the use of it.
Maybe any of the developers that come to this forum could take a look and explain us how to use any of the new filters that has been added.

Thanks Arda

StephLG
2nd March 2002, 17:06
Hi,

I spent hours trying to understand why my bicubicresize refused to work (with the 'FPU' thing error) before I saw this thread :(

Can someone point me to a link where I could find these Beta6 or Beta7 versions? (the above links don't work anymore).

Thanx,
Steph.

civ
2nd March 2002, 20:35
What is your email? I can email both versions to you.

Divine
3rd March 2002, 08:26
http://members.cox.net/hansenjo1/avisynth-1.0b7a.zip

http://members.cox.net/hansenjo1/ConvertFPS.html

StephLG
10th March 2002, 22:12
Sorry civ for not having replied earlier, I was in vacation.
Thank you Divine for the link; I'm gonna try this new version.

Steph.

movmasty
11th March 2002, 07:06
on the closest thing to official we have now ,videotools.net.

they still offer the beta 5.............

Chibi Jasmin
24th April 2002, 10:19
Originally posted by ARDA
As this thread was about new versions of avisynth.I will go on about it.
I was looking in sourceforge and I've found all modifications that were reported here, in the cvs,more precisely most of them in effects.cpp .Those releases that has been pointed are from one of the developers page.
I was looking specially the RgbAdjust that has similar name to neuron2 filter and in a fast sight it is has also a similar behaviour; except for a fourth parameter that I didn't understand what is the use of it.
Maybe any of the developers that come to this forum could take a look and explain us how to use any of the new filters that has been added.

Thanks Arda

Somone please point me to the above mention sourceforge project...and is there a place, where there are always newest binaries of these more or less unofficial versions available? Is 1.0b7a the latest for now?

hakko504
24th April 2002, 10:24
Originally posted by Chibi Jasmin


Somone please point me to the above mention sourceforge project...and is there a place, where there are always newest binaries of these more or less unofficial versions available? Is 1.0b7a the latest for now?

AVISynth at sourceforge. (http://sourceforge.net/projects/avisynth/) Also look for SAVE-oe (new development of DVD2AVI)

Chibi Jasmin
24th April 2002, 11:48
Thanx...not much info there...

Any place where I can get more info (don't mind binaries) of these AviSynth 1.0 beta6/7 etc. versions?

About Save-oe...I am following the dvd2avi sourceforge thread...there seems to be more info...

ARDA
25th April 2002, 01:47
@Chibi Jasmin
You are right there is not too much information there.As you read in my above post two months ago
I asked help for more information and as nobody answered I had watched more carefully the sources
and could in few words summarize this:

The bug in Bicubic resize with emms call was fixed.

A new filter RGBAdjust has been included (obviously it just work in rgb mode.
Ex:
ConvertToRGB() #if you aren't already working in rgb
RgbAdjust(0.94,0.97,1,0) # the fourth parameter is for alpha channel
ConvertToYUY2() # if you need to convert.

A Greyscale filter has beed added. It just work in YUY2 .To use:
just
Greyscale

The most important change has been done in Sharpen-Blur filter
Many people has reported problems with it in avisynth 5 too.

The new Sharpen filter now includes two parameters ; vertical and horizontal
so if you write something like this
Sharpen (-0.5,0.4)
# you are blurring in vertical direction and sharpenning in horizontal direction
it is interesting to play with that values.I must confess I don't like too much how it works but
by now it is the only one sharp,blur filter we have for avisynth in yuy .
Besides they have included a rgb24 mode so I think it works correctly for some programams
that need that.
Unluckly there exists still a bug in AdjustFocusH (for developers) in width loop when you
work in yuy ;it works correctly in rgb.The bugs creates a strange line in the right side of
the frame.Using it before cropping you can cut that line.But if you can compile avisynth
(I have tried and couldn't),make some test with the following line (line 1517,revision1.7)

q[vi.width*2-4] = ScaledPixelClip(q[0] * center_weight + (yy + q[vi.width*2-2])
If I am not wrong the problem is there.Maybe Dividee could help us,he has released a
binary dll somedays ago.
There is also a ConvertFPS filter but I haven't test it at all.
It is not too much, if you have more details or new information please let us know.
Arda

Chibi Jasmin
25th April 2002, 11:51
Thanx a lot four your infos, I'm sorry, I don't know more than you...you referred to v1.0b7a, didn't you?

dividee
25th April 2002, 23:44
I'm a little confused by these version numbers too. The last version in the CVS tells "1.0 beta 7d" with the "Version" script.

Thanks ARDA, this line was indeed to blame, the correct line is:
q[vi.width*2-4] = ScaledPixelClip(q[vi.width*2-4] * center_weight + (yy + q[vi.width*2-2]) * outer_weight);

I attach my binary, which is the same as the one I posted some days ago, with the AdjustFocusH fix (Sharpen & Blur).

The other modifications from the CVS are:
- Fixed Dissolve (again)
- Convenience: Crop accepts negative arguments for width and height, interpreted as distances from the right and bottom borders (ex: Crop(20,20,-20,-20) crops 20 pixels from each side)
- Minor bug fixed in parameter checking for Sharpen.

Also included is msvcr70.dll, I think you may need it since it's compiled with MSVC7.

ARDA
26th April 2002, 00:13
@dividee

I must thank you,for your quickly reply and an old bug finally fixed.I know you have said you have not too much time
but; wouldn't be usefull as you have made with TemporalSoften ,to create a Sharpen2 plugin with mmx and sse implementention?
Anyway thanks in advance

Arda

dividee
26th April 2002, 00:33
@ARDA

That's already on my list ;) but there are other things I want to finish first: A "Logo" filter to replace the one from vdub and an (experimental) scene change detection for TemporalSmoother/TemporalSoften.

ARDA
26th April 2002, 00:44
@dividee
If I have understood right, we'll be albe to apply a smoother conditioned to motion detection.
l think many people will be happy with that , and I can wait more time for Sharpen2 very happy too.
Thanks again
Arda

Pko
26th April 2002, 09:52
Originally posted by dividee
I want to finish first: A "Logo" filter to replace the one from vdub

I am using "logo" filter a lot and it works very well, but I've found some important limitations (it is slow, hungs Virtual Dub when there are many instances of the filter in the .avs file, does not have anti aliasing capability, there are some bugs and limitations in animation...)

Also, I was thinking of overlying two videos, and I think it can be done with logo filter exporting one of the videos as a list of BMPs and treating that BMPs as an animated logo, but of course all the limitations of the filter will apply and also a large number of BMPs needs to be created...

So, if you need suggestions for the plugin and/or testers, please tell me.

Chibi Jasmin
26th April 2002, 12:42
Originally posted by dividee
I'm a little confused by these version numbers too. The last version in the CVS tells "1.0 beta 7d" with the "Version" script.

Mavbe I am too dumb, but could someone point me directly to where to find these new cvs-versions? Binaries preferred :-)

Koepi
26th April 2002, 14:22
Damn, I checked out the CVS nd tried to compile it, but it simply doesn't work.

(326 errors caused by redefinitions and I dunno where to find the "double" includes :-/ )

So I can't provide a binary.

Chibi Jasmin
26th April 2002, 18:58
Let us know, if it should ever work...

Psyche
30th April 2002, 06:23
I've got compiled binaries of avisynth 1.0b7, if somebody wants them drop me a PM with your mail and I'll send them. I've got no way to upload them to a server.
This is the version I'm currently using and I'm not having any problems (but again, I didn't have any problems with 1.0b5).
@Koepi: CVS checkout some days ago and compiled fine. Don't know why you can't.

EDIT: @Koepi, now I remember, I had to add these lines

#define _aligned_malloc(x,y) malloc(x)
#define _aligned_free(x) free(x)

in effects.cpp, 'cos it dodn't work.

BTW, my compiles are ICL, optimized for Pentium II and above, hope it doesn't mind.

Chibi Jasmin
30th April 2002, 10:15
I can't compile V1.07d because of missing include amvideo.h, can you help?

Psyche
30th April 2002, 14:19
amvideo.h are the video interface definitions for active movie. It gets installed in the default Visual Studio 6.0.
If not, you can always install the directx sdk (go microsoft), it's there also.

Chibi Jasmin
30th April 2002, 14:53
Originally posted by Psyche
amvideo.h are the video interface definitions for active movie. It gets installed in the default Visual Studio 6.0.
If not, you can always install the directx sdk (go microsoft), it's there also.

Well, Visual Studio.NET did not install it...but maybe I didn't choose to do so, who knows, I installed only C++ and a few things I thought to be necessary...

Thanx..

Chibi Jasmin
30th April 2002, 16:59
Okay, got the DirectX SDK...

but also a new problem...ignore, if you find it annoying, please:

Building gives me these errors now:

avisynth error LNK2019: unresolved external symbol _mmx_YUY2toRGB24 referenced in function "public: virtual class PVideoFrame __stdcall ConvertToRGB::GetFrame(int,class IScriptEnvironment *)" (?GetFrame@ConvertToRGB@@UAG?AVPVideoFrame@@HPAVIScriptEnvironment@@@Z)

avisynth error LNK2019: unresolved external symbol _mmx_YUY2toRGB32 referenced in function "public: virtual class PVideoFrame __stdcall ConvertToRGB::GetFrame(int,class IScriptEnvironment *)" (?GetFrame@ConvertToRGB@@UAG?AVPVideoFrame@@HPAVIScriptEnvironment@@@Z)

Any ideas?

And this warning:

avisynth warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/INCREMENTAL:NO' specification

But I have seen builds with lots of warnings work, so this is probably not that interesting :)

dividee
30th April 2002, 19:33
These two symbols are defined in avisynth_a.asm
Can you compile this file alone? (right click/Compile on the file in Solution Explorer). If no, check if you have ml.exe in the bin directory of VS.NET. If yes, verify the file is not excluded from build (right click/Properties in Solution Explorer).

And don't worry about the warning.

Psyche
30th April 2002, 19:46
check if you have ml.exe in the bin directory
That's the thing, I think, now I remember I had to put ml.exe in the bin directory (but I'm using VS6.0).
@dividee: what's the matter about those _aligned_malloc and _aligned_free, where are those defined? (Do you still remember FastDeinterlace? :p )

Chibi Jasmin
30th April 2002, 19:47
Thanx for trying to help...

Well, I have opened the project in VS.NET. ml.exe is available ($(VCInstallDir)bin, where cl.exe is, too).

right-clicking on the avisynth_a.asm compile is greyed out...properties show: excluded from build: no, tool custom build tool. under custom build step there is no command line entered.

changed to tool: c/c++ it doesn't compile...what can I do?

dividee
30th April 2002, 21:03
@Chibi Jasmin:
I have this command line for the custom build step:

ml /c /Zd /coff /nologo /Fo$(IntDir)\$(InputName).obj $(InputPath)


@Psyche:
Now I remember. I knew your nick was somehow familiar but it didn't strike me :). I hope you're not angry against me for letting you down with FastDeinterlace. Did you do anything with it since then? I could still add it to mpeg2dec.dll if you want.

About _aligned_malloc, it's defined in the malloc.h that comes with VS6 & 7, it seems.

Chibi Jasmin
30th April 2002, 21:37
Originally posted by dividee
@Chibi Jasmin:
I have this command line for the custom build step:

ml /c /Zd /coff /nologo /Fo$(IntDir)\$(InputName).obj $(InputPath)




Thanx...but why don't I have this line? Did it somehow get lost during conversion into VC++7.0 format (on opening the project file)? I got a fresh cvs checkout..

result after inserting the commandline, compile still greyed out...starting the build results in:

Performing Custom Build Step
avisynth_a.asm : The custom build step was not executed because the 'Outputs' property of this custom build rule has not been set.

:-) Some output file must be specified or something? The output field and the one below in the custom properties page under the command line is also empty...

BTW: I always have to edit linker/general/output file...it points to f:\winnt\system32\avisynth.dll ...f:\ is my DVD so it wouldn't work...

dividee
30th April 2002, 21:41
And to those of you that checked out avisynth from the CVS: I'm not familiar with that tool, and had problems with line endings (they were something like CR+LF+LF (0D0A0A), I can't remember exactly. I had to open each file in UltraEdit and convert them to DOS format. Did you had the same problem or did I miss an option in WinCVS ?

dividee
30th April 2002, 21:48
Outputs: $(IntDir)\$(InputName).obj

I don't know why you have this problem. The files in the CVS haven't changed for 2 months and I just had to double-click the project file (after converting line ending, see above) and let VS7 convert it, and it compiled beautifully.

Chibi Jasmin
30th April 2002, 21:49
I actually tried to figure out how WinCVS works shortly and then skipped it...I just did a checkout with the command line cvs....also without learning too much options...I simply took the command line from the sourceforge page:

cvs -z3 -d:pserver:anonymous@cvs.avisynth.sourceforge.net:/cvsroot/avisynth co modulename

replaced modulename with avisynth and it worked :-)

and btou the corrupt endings...I know that from XVid...sometimes you get an error about a corrupt project file...the solution was opening and saving in WordPad...but here with AviSynth I don't THINK it is this kind of error...

dividee
30th April 2002, 22:01
BTW: I always have to edit linker/general/output file...it points to f:\winnt\system32\avisynth.dll ...f:\ is my DVD so it wouldn't work...


By "always", do you mean each time you checkout the files from the CVS, or each time you open the project?

Psyche
1st May 2002, 11:37
My memory is getting worse each and every day!
Yeah, when I first checked out from CVS I realised that there was no custom build command line for *.asm, so I had to put it myself.
And for the CR,LF problem, I guess they are wrong in the server itself, some like a checkout from linux and a commit in windows or something alike.
@Chibi: I hope you don't get any more problems compiling :b
@dividee: I'm not angry at all, in fact the code is scattered somewhere in my HD, if you have lost it and want me to resend it to you I can (even your modifications).

Chibi Jasmin
1st May 2002, 12:06
Originally posted by dividee


By "always", do you mean each time you checkout the files from the CVS, or each time you open the project?

Well, I don't exactly know, because to be on the safe side I always replaced the working copy with an original copy of the cvs checkout before trying your suggested changes...

Will try your new output suggestion asap...

Chibi Jasmin
1st May 2002, 12:08
Originally posted by Psyche
My memory is getting worse each and every day!
Yeah, when I first checked out from CVS I realised that there was no custom build command line for *.asm, so I had to put it myself.
And for the CR,LF problem, I guess they are wrong in the server itself, some like a checkout from linux and a commit in windows or something alike.
@Chibi: I hope you don't get any more problems compiling :b


Thanx I will try it again now...

Chibi Jasmin
1st May 2002, 12:16
I can compile the asm thing now...but I still have these two erros on the whole build:

avisynth error LNK2019: unresolved external symbol _mmx_YUY2toRGB24 referenced in function "public: virtual class PVideoFrame __stdcall ConvertToRGB::GetFrame(int,class IScriptEnvironment *)" (?GetFrame@ConvertToRGB@@UAG?AVPVideoFrame@@HPAVIScriptEnvironment@@@Z)

avisynth error LNK2019: unresolved external symbol _mmx_YUY2toRGB32 referenced in function "public: virtual class PVideoFrame __stdcall ConvertToRGB::GetFrame(int,class IScriptEnvironment *)" (?GetFrame@ConvertToRGB@@UAG?AVPVideoFrame@@HPAVIScriptEnvironment@@@Z)

Well, strange others can compile it right off the CVS...

dividee
1st May 2002, 12:37
You can try to put the two files in this zip in your avisynth directory and open the project by double-clicking on the avisynth.vcproj file.

Chibi Jasmin
1st May 2002, 13:45
GREAT! 0 errors, 0 warning, right from the start! Thanx!!!

But what did you do to get these working project-files? Nothing? :)

There really seems to be some conversion problem from VC++6 Project to current ones...

dividee
1st May 2002, 14:06
Indeed, nothing. If I remember well, I just changed the build target to the Release & Debug directory, instead of the Windows System directory, because I prefer it that way.
But I converted the project with a Beta release of VS7. This is not the first time a Beta from MS would perform better than the final product ;)

Chibi Jasmin
1st May 2002, 14:51
Strange :-) But well, it works...with new version in CVS I'll have the problem again then...

Wilbert
8th May 2002, 22:23
@dividee

Edwin released a new version of AviSynth (v1.0b6). Is that the same version as your (I know about the sourceforge project) v1.0b7d? I ask this because his list of improvements is very short and I can't find any documentation on http://sourceforge.net/projects/avisynth/.