I forward this message from my collegue Paolo Coletta on the upcoming releases of EyesWeb. Best regards Antonio Camurri ======= Hi all, this is to announce that a new version of EyesWeb (2.5.0) will be released on May 7, 2002 (most probable date). This new version will include, among the other things: - OSC (OpenSound Control) support; - improvemetns to the Steinberg VST support (some settings could be lost in current implementation); - an improvement to the user interface to graphically distinguish among different datatypes; - improvements to the audio/midi libraries; - Motion Analysis Library: new real-time algorithms for movement analysis (expressive cues analysis), for color-based multiple blobs tracking, and other real-time trackers; - new (documented) datatype for MOtion CAPture data. By using this datatype developers can build new blocks using/providing data compatible with the EyesWeb new Motion Analysis Library; - improvements to the MultimediaFileReader block (support of non-realtime mode, to avoid skipping frames on CPU overload conditions); - Other significant extensions to existing libraries: integrators lib, filters, new modules to the Imaging Library (e.g. for 2D interactive graphics and animations); - new source code samples to help users in developing their own modules; - new demo patches; - manuals updated; - ...and more... Moreover, many blocks will be renamed in order to simplify the user interface and to better meet users' feedback. Since the new names will be chosen to meet the final users' preferences, your (possibly, concrete) proposals are welcome. Consider that currently any block can appear in more than one folder (=library), but always with the same name. Also consider that the number and names of the current folders can be changed as well. For example, the FrameGrabber block is available as Input.Imaging.FrameGrabber and Imaging.Input.FrameGrabber (the . [dot] separates the different folder nesting levels). Thus, for each block for which you want to propose a different name, please specify all the folders where it should appear. Example of a proposal: Old name: FrameGrabber (also specify the/a full path if there may be ambiguities with other blocks. E.g.: Input.Imaging.Framegrabber) New name: VideoInput Folders: Hardware.Video Therefore, to let us the time to make the modifications and update the documentation, please provide your proposals before April 15. Finally, from this new version we have set up another opportunity enabling users to access the experience of our Lab Staff for specific requests and services around EyesWeb, so to enable commercial or in general "pro" or "custom" applications with our support (e.g., specific s/w developments like automatic load and run of a patch at the boot, networked control of patches, as well as specific developments on request). Our Lab Staff experience includes, in the last decade, many developments to a number of artistic productions, museum exhibits, science centers, distributed installations, and other professional applications. Please submit your specific requests to staff@infomus.dist.unige.it * EyesWeb 3.0 We did not forget other important extensions, such as macro-patches and hierarchy of datatypes, which are in our agenda. After the release of version 2.5 we will start with the development of new important features, that will be released with EyesWeb 3.0. Intermediate versions might be released during the development. These new features include: + Macropatches. A step toward true subpatches: macropatches are prebuilt patches that can be seen in the EyesWeb treeview as all the other standard blocks. When they are istantiated the macropatch is added to the patch, instead of a single block. + Common-tasks for datatypes. For each datatype it will be possible to define a set of common operations, which will correspond to the instantiation of the corresponding block (or macropatch). For instance, a common task for the image datatype is "Render", which correspond to istantiating and linking a Imaging.Output.Display. More complex tasks might be defined, of course. + Treeview customization. The EyesWeb treeview, which contains the list of the available blocks as defined by the developers of the blocks, will be modifiable by the final users. It will be possible to hide some folders, to create new ones, to rename blocks (and macropatches) and to move/copy blocks to other folders. It will be possible to export/import configurations and to switch among different ones. + Protected behaviour. Details of the patch will be hidden: only labels and paramchangers will be visible to final users. + Hidden behaviour. In this case all the patch is hidden. Note that, even if param changer are not available for user interaction, the parameters of the patch can be changed via other means, e.g., network, midi, etc. Suggestions and comments are welcome. Paolo Coletta
This archive was generated by hypermail 2b30 : 04/04/02