Avisynth 2 CVS binaries

[sh0dan]

I've done a page for downloading the newest CVS binaries, for those eager to try them out:

Avisynth 2 CVS snapshot binaries (http://cultact-server.novi.dk/kpo/avisynth/avs_cvs.html)

I'll keep it updated.

If anyone has objections to this, just PM or mail me, and I'll take it down.

[Wilbert]

Thanks! Are MergeChroma and Layer working again? In the changelog you didn't mention AssumeTFF() and AssumeBFF().

[sh0dan]

Both are working (hopefully!) - dividee fixed layer, and I fixed mergechroma/luma, so you should be ready to rock :)

AssumeTFF() and AssumeBFF() are in the build, but I haven't tested them myself. (Adding them to history)

[ARDA]

Thank you very much.I will not have to fight every change to compile
I am newbie for ever.By the way I've post in page 2 of http://sourceforge.net/projects/avisynth2 a small problem I've had with resample.cpp to be able to compile with last comits.

[sh0dan]

Have you done a Rebuild All? What's your build setup?

Check out you got the newest transform.c and transform.h, the Crop parameter was changed in (transform.h version 1.1, 2002/07/04 13:23:04) to include env.

[ARDA]

I am really sorry I hadn't update trasnform.h and cpp.
Please forgive this newbie mistake.
Thanks again all of you four your great work
Arda

[sh0dan]

No problem mate - we've all done that one time or another :)

[sh0dan]

Just updated:
- New function ConvertToMono(clip) - convert stereo to mono.
- New function KillAudio(clip) removes audio from clip. Use this if you get crashes with compressed AVI sound.
- Added sound to Loop() function.

Down'em if you need'em.

[Richard Berg]

I've given you rights to release files via SourceForge. That brings the total to 4 people (me, Koepi, dividee, you) so hopefully we can keep the binaries there more up to date now.

[MoonWalker]

Is there a prog tha can download all the files of a cvs and if you have them update only the new ones??

Thanks,
MoonWalker

[dividee]

@Richard:
I didn't even knew I had this right! Must have missed it somewhere.

@Moonwalker:
Yes of course there are such progs; how do you think developer works ? :) The most widely used CVS client seems to be WinCVS, for my part I use Tortoise CVS. Be warned these programs are usually a pain to set up.

[trbarry]

Good work guys.

@Richard - Could you add me to the project (as trbarry)?

- Tom

[Richard Berg]

:confused: You've been on the list since the beginning, which should at least let you work with CVS. If that doesn't work or you need other rights, let me know.

[Marc FD]

if you could release binaries more often on sourceforge (with the source) it would be usefull. I've never used CVS so i'm always waiting for a new updated src. one update per week seems good.

[Koepi]

Uh! Nice to know :)

But I still don't get avisynth to compile (elsy I would've been playing around with it much more already ;) ).

EDIT: dumb I am!
Finally found the switch wher the "full download" is selectable. now it's prime time *download* :)


Best regards,
Koepi

[sh0dan]

Once a week sounds reasonable, and we should make the source downloadable too - agree!

Just updated the page with aug. 5 binaries, new features include:

- GetLeftChannel - Returns left channel.
- GetRightChannel - Returns right channel.
- MonoToStereo(clip1_left,clip2_right) - muxes two clips together as one stereo clip.
- MixAudio(clip_1,clip_2,float clip1_volume, float clip2_volume) Mixes two audio sources together.
- Added ConvertBackToYUY2() That only uses chroma from the left pixel to avoid shifting chroma color by multiple YUY2->RGB>YUY2 conversions. ConvertToYUY2 remains unchanged.
- Added Documentation for new parameters

I'll try doing a seperate build with dividee's modified avisource. [EDIT: No - I wont - get it from the ACM thread].

I think we should wait until dividee has finished fixing avisource audio, until there'll be a new release.
The next release will probably be 2.10, due to the many new features.

[Richard Berg]

Could you (or Koepi or someone) also release the updated builds to SourceForge? Here's a shortcut (http://sourceforge.net/project/admin/newrelease.php?package_id=52439&group_id=57023) to the page (it'll make you login first) -- just type in the version # and follow the instructions.

[sh0dan]

Yes - I'll do it, but as stated above, I think we should wait a little bit, and do a major release - with PR and everything :)

Hopefully I get some time for updating the documentation.
I've been thinking of a restructuring, so each filter gets its own html-file. I've not worked much with sourceforge doumentation, but my first impression is, that it would be a lot easier, if documentation was a part of the CVS tree - how does that sound?

[hakko504]

... and don't release anything until you have settled the Decomb issue with Don Graft.

[sh0dan]

Originally posted by hakko504
... and don't release anything until you have settled the Decomb issue with Don Graft.

No - absolutely right!

[Richard Berg]

Yep - just saw that we have a small political issue to iron out, so no official releases yet :) Besides, I still have some of my own code I wanna get ready to submit (finally!)

I'd started to copy some of the latest docs to SourceForge, but now that I'm working with it again I'll heartily agree that the SF doc editor is pretty clumsy.

I vote we make a /doc/ subdirectory off the CVS and stick some HTML in there, then every time we do a "release" also publish a 3rd Zip with all the docs in it. Since most of the devs are using CVS already it should provide some incentive to keep changelists / filter descriptions / etc. up to date.

As far as structure, I definitely agree the single giant filter reference has outlived its welcome. How to split it up -- by individual filter? By category? By the CPP/H file it's defined in?

[sh0dan]

You got my vote for /docs - and perhaps a /docs/filters to keep the root clean (so there will only be reference.html, faq.html, etc.html, etc.html in the /docs root).

I think a per filter split would be the best, and the easiest to maintain and reference to. If you create the CVS stuff I could try to throw something together?

[Richard Berg]

Done. The only thing there right now is Koepi's changelist; right now I'm working on adapting Wilbert's FAQ (e.g. adding HTML anchors to each Q&A).

Dunno where to begin with filters...there are so many partial docs out there. I'll just link them all for now so we have a starting point:
BenRG's scripting tutorial (http://math.berkeley.edu/~benrg/avisynth-tutorial.html)
BenRG's scripting reference (http://math.berkeley.edu/~benrg/avisynth-reference.html)
VideoTools.net reference (http://videotools.net/doc/reference.htm)
Wilbert's thread for new filters (http://forum.doom9.org/showthread.php?s=&threadid=30014)
Koepi's list of filter updates (http://cultact-server.novi.dk/kpo/avisynth/updates.html)

[poptones]

Here's an idea: will the "avisynth.org" server support scripts?

How about setting up a wikki? It will make the task seem far less daunting for all.

[Richard Berg]

Funny - a day ago I wouldn't have a clue what you were talking about, but I came across a Wikki while surfing some blogs and thought it was very cool...never made the connection to Avisynth, but it sure couldn't hurt.

Anyway, the hard part isn't running scripts, it's finding a database backend. Luckily SF provides one of those for us too; I've downloaded a GPL'd script engine (http://tavi.sourceforge.net) and will put it to work once our MySQL backend is up & running (requests are only processed a couple times a day).

[sh0dan]

Originally posted by Richard Berg
Done. The only thing there right now is Koepi's changelist; right now I'm working on adapting Wilbert's FAQ (e.g. adding HTML anchors to each Q&A).

Great! I'll do an update and get it ASAP.


Koepi's list of filter updates (http://cultact-server.novi.dk/kpo/avisynth/updates.html)

Just to avoid any confusion, I wrote these additions (since these are the changes I know of). I still miss some better documentation for Layer - with more explanations of what each setting does, etc.

[Marc FD]

I think official release via SF are really the best :)

If you want to add Cnr2 to avisynth, just wait i release the 2.3 version :cool:
I would just demand you to keep the legal headers (or at least don't touch too much the code...)
I think each filter like Cnr2 needs it's own file.

Just suggestions ;)

[Koepi]

Oopsi!

http://cultact-server.novi.dk/kpo/avisynth/updates.html

I always have a "koepi" in accounts, and .dk is not .de ;)

But sh0dan already mentioned it. I was getting confused where I created a changelist, must've been in a delerium ;)

Please, refer to it with sh0dan's nick :)

Regards,
Koepi

[Richard Berg]

Heh, between that & an email mixup (don't ask) I'm obviously not firing on all cylinders today :) As you rightly assumed, I saw the "dk" (not "de") & "kpo" (not "koepi") and jumped to conclusions.

No matter - once I get Wikki working, "ownership" of docs won't be a factor anymore...

[Wilbert]

@Richard,

I hope you don't mind but I didn't find the faq-thread the appropriate thread to discuss this:

@Wilbert -- Start here (http://sourceforge.net/docman/?group_id=57023), you should be able to add/edit anything on this screen.
Read the end of this thread though -- we won't be using the SourceForge doc manager much longer, so I wouldn't bother. The changelist there is already out of date, in fact; I added a few lines to the one on the CVS, which in turn should be replaced by a website something driven by Wikki.

Ok, will wait for that. Just curious all I can do is "Submit new documentation" (and "View Documentation" and the third one "Admin" is protected for me) which must be approved by an editor/administrator. How can I edit/change stuff?

BTW. The link to "Avisynth 2.03 beta (August 5. 2002)" on page http://sourceforge.net/docman/display_doc.php?docid=12366&group_id=57023 doesn't work (page not found ...).

[Richard Berg]

Not at all -- a mod can delete my posts from the FAQ if they want.

After a couple of fun-fun hours with remote sessions of Pico, I'm pleased to present the Avisynth Wiki (http://avisynth.org/wiki/). What's a Wiki? Look here (http://tavi.sourceforge.net/WhatIsAWiki), then check out the formatting rules (http://tavi.sourceforge.net/FormattingRules) once you've got the general idea.

The default template works ok, but I'd like to steal the one this site (http://easytopicmaps.com/) is using -- very well done I have to say.

More important: content! Gotta run right now, but the links above plus the docs currently in the CVS (http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/avisynth2/avisynth/docs/) should be the starting point...converting to Wiki formatting shouldn't be too tough with a good text editor...

[sh0dan]

OK - spend HOURS of copy/pasting filter information into seperate files - getting out seperate paramters, etc. I used an HTML-pre-processor (much similar to a C-pre-processor) to generate indices, so for a little while I would just like feedback on the 'split-up' - does it make as much sense to you as to me?

Test it at the link on the top of the page.

(There shouldn't be anything in the way of a 2.1 release tomorrow, should there - hopefully with compressed audio support?)

[dividee]

Nice work sh0dan, I can imagine the time it takes as I once had to go through all this doc to update it.

I'd like something more straighforward for the quick ref: just an alphabetically sorted list of filters with params, the name there can serve as a link, no need to repeat it. Also, the categorization hinders me more than it helps me. I have no problem remembering a filter name, but I always have to stress my brain for fitting it in the right category :). I'm only talking about the quick ref, not the main one.

Of course if nobody agrees with me, I won't mind.

[Marc FD]

The best would be to add an internal filter who shows all the filters that avisynth can currently use. i think of a function like List()

The ouput would be something like 640x480 , and if there is too much lines it would scroll in time axis.

It should gives you the filters AND the param list with types and the names of args if they are defined.
Plugins loaded before a call to list() should be listed :) too

and an optional feature would be List("string") where the string is the first letters of the filters you want to list ..

I think it would be a MUST because you sometimes forget the arg types or the order and nothing is more boring than making a hex dump of a dll to use a filter (i already used an hex editor to find the arg of some plugins who were without doc (like SpatialSoftenMMX))

I really think it would be a great feature (and possible to code too, from what i have read from the avs sources)

EDIT : maybe List() could list by categories too ??

Hope it would be in avisynth 2.1 :cool:

PS : if you need a coder more to check the code of avisynth, it would be a pleasure ;)

[WarpEnterprises]

Wikki: It's a nice method but I miss some things:
- if really anybody can change things some half-truths will accumulate, and well-checked facts will be messed up with assumptions
- there is a lack of keeping a structure and getting it out again (a hardcopy or a conversion to a quick or not-so-quick reference), this can be seen in the examples you linked to.
It looks like the other extreme to the SF-doc (which seems TOO stringent).
I fear we will end up with a huge heap of bad-structured information.

Maybe there's some way in between?

[poptones]

How do you figure "half truths will accumulate?" That's like saying OSS is inherently flawed because just anyone can take code and change it.

Wanna see structure?

http://www.superant.com/cgi-bin/slencyclopedia.pl

[Richard Berg]

Fine -- you type up all the content and nobody will complain :)

[poptones]

Naw... they'll complain

;)

How adaptable is this? Is there a command for including others wikis into pages? That's a very useful and powerful feature for organizing content in various ways without having to cut and paste it into the database a dozen times.

[Richard Berg]

How adaptable is this? Is there a command for including others wikis into pages?
If you read everything at http://tavi.sourceforge.net you'll know more than me.

if really anybody can change things some half-truths will accumulate, and well-checked facts will be messed up with assumptions
Changes are logged CVS-style using diffs and indexed by username (or by IP mask if you haven't configured your profile), all stored in a MySQL database that's locked with a password and a hostmask that bars access from outside SourceForge. There are options to lock down the submission queues if necessary, but I've taken some care with the Apache permissions so I don't think it's possible to permanently delete anything without yet another password.Here's the page (http://www.avisynth.org/wiki/admin) to hack if you're so inspired :)

As for innocuous but misleading/incorrect additions -- if you see one, change it!

Just curious all I can do is "Submit new documentation" (and "View Documentation" and the third one "Admin" is protected for me) which must be approved by an editor/administrator. How can I edit/change stuff?
Maybe there's an option available after you click into a doc? You're logged in right?

In any case...it's clunky, forget it. Dunno if we want to maintain the new /docs/ branch of the CVS, but it's certainly better than messing with the normal doc manager.

The best would be to add an internal filter who shows all the filters that avisynth can currently use.
Not a bad idea, but will probably take awhile for a "proper" solution to come about, i.e. not just a buncha text we have to change manually every time a filter is update. I'm still quite enamored of the idea of exporting this functionality directly from the DLL to be read by a syntax-aware, Intellisense-powered editor...

I'd like something more straighforward for the quick ref: just an alphabetically sorted list of filters with params, the name there can serve as a link, no need to repeat it.
Agreed.

(There shouldn't be anything in the way of a 2.1 release tomorrow, should there - hopefully with compressed audio support?)
I've got a few pet projects I'd like to finish but probably won't in time...mostly just waiting on confidence in Dividee's revamped AVISource.

Edit: I see from the ACM thread he's posted the source but can't merge yet...I'll do it tonight if nobody else has done so by the time I get home.

[poptones]

Not a bad idea, but will probably take awhile for a "proper" solution to come about, i.e. not just a buncha text we have to change manually every time a filter is update. I'm still quite enamored of the idea of exporting this functionality directly from the DLL to be read by a syntax-aware, Intellisense-powered editor...

But that only buys very little. At best you get the same info you could get from looking at the templates in the source code. Why not just put together a document from all the templates?

I think what's really needed is more functionality in an easily constructed, maintainable GUI. So when you ad a filter or plugin, it doesn't take long to put together a control panel.

Anyway, that's my take. I've been trying to get as competent with python as I once was with jscript. And that's all I'm sayin' about that.

[Koepi]

Is it possible to compile python as native binary or do you need a runtime environment? (like with tk)...

Regards,
Koepi

[Richard Berg]

Why not just put together a document from all the templates?
The idea is to have the code do this automagically -- after all, the complete function definitions already get passed to avisynth.cpp.

[poptones]

You gotta have a runtime. Better still, because I'm using the wxWidgets, there's even more to install than just the basic package. And thus far (so far as I know) it's not integrated into the scripting engine. (Which is really not too big a deal; I'm probably one of ten people who actually went to the trouble to use those fancy hooks MS provides for desktop use of jscript, and I still found it far too limited).

But I really don't see the extra packages as a problem; if it works like I think people won't mind running an installer (it can all be bundled up nice and easy, ya know). And if it doesn't work like I envision - well, it won't matter anyway.

It's important to use python, I think, because it's so common on linux and that buys inroads into the pro and educational market. I'm still hoping that if this product is made compelling enough it'll find its way to the linux (and os x) desktop, and that would make me seriously happy. Yes, this is all about me ;)

Besides, I'm sick of all my work being confined to one desktop. I like working on user interfaces, and I think this is a chance to do something meaningful.

[Koepi]

Well, then head for gtk(++) (free in all cases) or qt (not free in all cases) ;)

It's still desktop then and you'd just need a huge dll or something ;)

Well, it's your choice, i just don't intend to install the XYZ package just to get a program running (no offense, but my system is already somewhat overloaded for my taste with the M$ devel environment).

But I'm eager to see screenshots then though! :)

Best regards,
Koepi

[poptones]

Eeew gtk? So then I can work in both python and tkinter?

It just needs to be python because it's already so widely used (where have I heard that argument before?) I mean, how many of these guys (http://www.mogge3d.com/) are already familiar with it? Standardization can be a good thing.

Use the source, luke.

[WarpEnterprises]

Two questions about the Wiki:
Is it possible to rename a created page? (e.g. if you chose a bad name?)

Is there a possibility to generate/print out a summary of e.g. all manual pages? I think it would be really tedious for a user to get a complete doc in hands.

Except that a good idea, the "one page per filter" comes out naturally.

[Wilbert]

@Richard,

Maybe there's an option available after you click into a doc? You're logged in right?

:D :D The login/password is that the usual login/password used to access Dooms site (cause these don't work)? You have to login via the tab Admin right?

[Marc FD]

my idea about the List command was something AUTOMATED.
It would not draw a predefined text !!
The idea is to list all the functions avaible in hte current avisynth env.
Since each function is "registered" to be used after, it should be easy to use these register arrays to draw them.
This way, each time a new function register itself, it would be listed.
even loaded plugins.

Do you think it's doable ? would really be cool :)

[Wilbert]

About Wikki,

I tried to make Anchors, but failed. Here is the url how do it: http://tavi.sourceforge.net/index.php?page=Anchor.

Creating one:

== Q1[[Anchor q1]] ==

Linking to this Anchor:

((Q1#q1))

the link doesn't work. Do you guys install v0.21 or later?

[dividee]

shouldn't the link be written like this ?

AviSynthFaq#q1