Log in

View Full Version : Avisynth 2.50 (Feb 25. 2003) (test)


DDogg
25th February 2003, 18:51
Please remove or move if this is not where you want this info.

I installed the above and had a total failure. By that I mean even Version.avs would not play with a "failed to render" in MPC. I changed the DLL to release 2.50 (28 Jan) and all worked again.

As we are having a freak ice storm in Texas, I will be around to do any tests requested.

(AMD T-Bird 1.4)

sh0dan
25th February 2003, 19:22
Edit: Ah - missing zlib.dll - I'll fix it!

Thanks for the report!

sh0dan
25th February 2003, 19:36
26 Feb binary is up (a bit premature though :)

REIGN_
25th February 2003, 20:14
I downloaded 26 Feb version and avisynth disappeared.In vdubmod--> script editor--> help--> avisynth version it said: "avisynth dll not found"

sillKotscha
25th February 2003, 20:21
Originally posted by sh0dan
26 Feb binary is up (a bit premature though :)

mmmm,

vdub gives me an error...

-> can't determine filetype of "lalala\test.avs" [= version()]

and trying to open version() with ZPlayer... Zplayer complains about a missing libjpeg.dll :(

just my lousy input...

with kind regards

Sill

sh0dan
25th February 2003, 20:30
No - your help is very useful!

Try redownloading the new 260203 (the new binary is exactly 423.521 bytes, if you're in doubt).

Sine I have those libraries installed on my computer it is hard to know if they are installed correctly - so please bear over with my "trial-and-error" fixes. :rolleyes:

sillKotscha
25th February 2003, 20:42
Originally posted by sh0dan
Try redownloading the new 260203

aahhhh, wonderfull!!

thank you, Sir.

edit: just a little note... version() still shows 28.Jan 03 ;)

DDogg
25th February 2003, 20:46
Is it still supposed to say 28 Jan? If so, all is roses.

Edit: He snuck in an edit on me with the same question so please delete this.

sh0dan
25th February 2003, 20:53
Yes it should. Version or date is not updated on CVS-releases (at least until I find a nice way to automate it) ;)

SILICON
25th February 2003, 21:35
Shodan lives in the future.
Now is 25/02/2003 and he put the release of 26/02/2003 :-))))

sh0dan
25th February 2003, 21:42
Just as Doom9 (Some silly thread I just remembered (http://forum.doom9.org/showthread.php?s=&threadid=23711&highlight=doom9+lives+in+the+future))

JuanC
26th February 2003, 03:52
Originally posted by sh0dan
Try redownloading the new 260203 (the new binary is exactly 423.521 bytes, if you're in doubt). I just redownloaded it (it is exactly that size) but I get the following message in vdubmod when opening any avs script: "This application has failed to start because libpng13.dll was not found. Reinstalling the application may fix this problem." After that one I get "Can not determine the file type of ...\version.avs"

After reinstalling the 2.5 beta from jan28 the problem is gone

Within the latest needed dlls for vdubmod pack (2002-11-25) there is a libpng.dll version 1.2.4.0, Do I need the newer one? Where to get it? Thanks, :J

EDIT: Workaround: I copied libpng.dll as libpng13.dll, and got to work. :J

celtic_druid
26th February 2003, 04:47
Same here, cannot determine file type. Also the install screws with my AVS settings (play, edit, shellnew) even with the associate setting deselected and I do like being able to right-click and create a new AVS.

sh0dan
26th February 2003, 08:49
**** - ok - so the files should be:

libpng13.dll
libjpeg.dll
zlib.dll

I don't know if libpng/libjpeg are the latest versions - Richard is the one to properly answer that question.

Updated version in "AviSynth_260203-2.exe" - now I'm almost 100% sure that dll names are correct! :cool:

N_F
26th February 2003, 10:44
May I ask where to download this? The latest one that shows up on sourceforge is from 2003-01-27.

Whoops... To anyone else with the same question: Check sh0dan's "Avisynth 2 CVS binaries" instead of "Avisynth 2 project".

AmiRage
26th February 2003, 18:55
Strange ... after installing 260203-2 XSharpen() from WarpSharp.dll no longer works with XSharpen() after Crop(4,4,-4,-6) (AVI input 696x458). I only get a distorted image. WarpSharp() still works.

I'm using a WarpSharp.dll dated 03.01.2003 (24653 bytes).

AVISource("696x458",false,"YV12")
Trim(35000,38000)
#Crop(4,4,-4,-6)
#WarpSharp()
XSharpen()

Kurosu
26th February 2003, 22:59
AVISource("696x458",false,"YV12")


First, I don't think it's a valid syntax for the Avisynth Avisource (http://www.avisynth.org/index.php?page=AviSource), second, this filters package by some japanese genius implements his own functions, like a tweaked loadplugin able to load AVS2.0x and/or 2.5 plugins and make them run together in the same script...

Maybe by using the native Avisource(), the problem will disappear.

AmiRage
26th February 2003, 23:03
Why isn't the syntax valid and which AVISource do you think I'm using?

BTW ... with "696x458" I mean the resolution of the AVI source. :D

Kurosu
27th February 2003, 00:09
Oh... I never thought AviSource was automatically adding an extension to the string passed, that's what confused me. About the 'other' Avisource, I thought I had seen it in a plugin by a japanese person. Anyway, I'm totally wrong.

Your problem might be a coding problem (related to memory alignement). I would suggest to move Xsharpen before the crop, and do a larger crop as the black borders will certainly give a nasty effect once gone through Xsharpen(). I guess Sh0dan is the one to fix that, besides the ffdshow author of this plugin.

UPollaehne
27th February 2003, 08:26
@shodan: I installed and deinstalled the test version and found that the additional DLLs are not removed.

sh0dan
27th February 2003, 08:41
@UPollaehne: Since these are general libraries, that might also be used by other packages - I don't think it is safe to remove them. We might breaks other software packages by doing so.

@AmiRage: Xsharpen has never worked after a crop, except if it a small crop with some special conditions (not-mod16, other stuff). Use it before the crop.

UPollaehne
27th February 2003, 08:48
@sh0dan: the usual DLL-Hell. ;-)
I do not have a problem with this I just mentioned it and maybe it would be worth a small message box on uninstalling.

ARDA
27th February 2003, 09:07
I think there is a bug in avisynth_260203-2.exe
This is my script:

MPEGSource("D:\VIDOCQ_SCN\VIDEO_TS\pista1vidocq.d2v").
\Crop(10,14,702,552).Converttoyuy2().SimpleResize(640,352)

There is some distortion in chromas diagonals red lines.
If I change the Converttoyuy2() before the crop or after resize
there is no more problem.

I'm attaching a frame that shows the problem

Wilbert
27th February 2003, 11:54
Could you give a bunch of examples how this ImageWriter (PNG, JPEG, BMP) is supposed to work. I guess the compression is between 0-100 for PNG and JPEG, none for BMP.

Syntax:

ImageWriter(PClip _child, const char * _base_name, const char * _ext, const int compression);

PClip _child = clip
char _base_name = ???
char * _ext = something with PNG, JPEG or BMP ???
int compression = between 0 and 100

Suppose for example that you want to save the frames 12 and 14 to JPEG with compression 60, what will be the command ?

sh0dan
27th February 2003, 13:37
@UPollaehne: I personally hate too many Yes/No selections in an installer. I personally would also like to remove the "This will install AviSynth blah blah blah". And they are something like 200k max.

@Arda: What's the problem? ;) I'll have a look at it :)

Thanks for the detailed report!


Edit: Regarding the image funtions, Richard will have to answer that one.

Belgabor
27th February 2003, 14:10
Hm, doesnt an image writer defeat the purpose of AviSynth? If you open a script, how do you guaratee that all frames are writen? If you go through the whole movie, like you would need to, you can also use VDub's save image sequence...
Also isnt there a performance loss depending on the position? If its not used last (ok, nut very sensible, but...), it might be called multiple times...

sh0dan
27th February 2003, 15:05
Originally posted by ARDA
Crop(10,14,702,552).Converttoyuy2()


Now that was a silly bug. ;)

Anyway - it's fixed - will be up in the next version.

sh0dan
27th February 2003, 19:46
New version is up - should fix the distorted colors. It has new YUY2->YV12 (ISSE ONLY!!) and some other minor fixes.

Wilbert
3rd March 2003, 12:08
The following doesn't produce a clip with twice the frame height (using newest binary):

AviSource("D:\Disc4\Temp2\test.avi").AssumeFieldBased.Weave

although

AviSource("D:\Disc4\Temp2\test.avi").SeparateFields.Weave

works fine.

sh0dan
3rd March 2003, 13:59
Fieldbased/Framebased isn't complete yet, so this is to be expected. But thanks for the info!