History and Present
These features, in combination with the large number of plugable modules (plugins) developed for Avisynth by noumerous third-party developers, provide the foundations for a system with enhanced NLE capabilities, extensibility and ease of deployment of new editing projects.
Up to its present state AVSLib development concentrated on the creation of the above mentioned machinery. In summary, as of today (version 1.1.0):
- The array container data type (initially deployed at version 1.0.0) has been enhanced with new capabilities and reached a mature state.
- A large set of basic string and numeric capabilities have been developed.
- A basic set of script debuging facilities have been developed.
- A number of basic filters has been developed; some of them are already ported to C++ to increase speed performance.
- A generic library loader and a package-subpackage-module library structure which allows unlimited extensibility and unification of script-based and plugin-based extensions with regard to their use (they are all loaded through the same interface) has been developed.
While this is a trend that will still be followed during the next few releases, additional targets have been added to the project's agenda, as the next section briefly outlines.
This section provides a gross insight of the plans of AVSLib developers for the future. Only the major steps are presented; addition of more functions on any module is a procedure that will be routinely performed and thus it does not need special mention.
- Development of tools for command line execution of Avisynth scripts, with input variables taken from the command line and/or from configuration files.
- Addition of presets (ready to run scripts) that will take advantage of the above tools.
- Porting of AVSLib core (at least) to C++ plugins to enhance execution speed.
- Extension of the debug package with new debugging tools.
- Creation of a debug version of the AVSLib library.
- Development of new filters.
- (Maybe) creation of a "Filters"library with the most common plugins developed by the Avisynth community wrapped by script code into a single distribution of packages and modules.
Any additional ideas or suggestions are welcomed.
Support & Communication
- Bug reports should be filed using the project's bug tracker system.
- Feature requests should be made using the project's features request system.
- Support requests should be made using the project's support request system.
- Questions, ideas, proposals, etc. regarding AVSlib should go to the most appropriate of the project's forums.
Any communication not falling in any of the above categories should be addressed to the project admininstrator.
Additional information may be found in the FAQs page.
This section has moved to the change log (and also inline to each specific filter / function documentation that is applicable).