Imported Upstream version 0.2.0.dfsg.1

Main author, project leader:
Dennis Smit <>
Duilio J. Protti <>
Vitaly V. Bursov <>
Gustavo Sverzut Barbieri <> (From freevo)
The original JESS work:
Remi Arquier <>
The original Infinity work:
Julien Carme <>
The original lv_gltest work, which is the gl analyzer from xmms:
Peter Alm, Mikael Alm, Olle Hallnas, Thomas Nilsson and 4Front Technologies
Current maintainer, port to libvisual, cleanups, fixes, additions by:
Dennis Smit <>
The previous maintainer and hackers:
Pascal Brochart <>
tunnel effect derived from the tides of time by
Mirko Teran-Ravnikar <>
child effect derived from the star child demo by
Andreas Gustafsson <>
energy effect derived from the tesla demo by
Konrad "Yoghurt" Zagorowicz (sunflower)
knot effect derived from the knot another torus demo
by Jan Horn <>
tentacles derived from the biohazard demo by
Jan Horn <>
spectrum analyzer derived from the spectrum plugin
by the XMMS team
face effect derived from the radial blur demo by
Dario Corno / Jeff Molofee and converted to delphi
by Jan Horn <>
twist effect derived from the twisting cylinder by
Andreas Gustafsson <>
beat detection written by Steve Kirkendall <>
Delphi/C | C++/C conversion by Pascal Brochart <>
Richard Asbury <>
Linux port by: Jean-Christophe Hoelt <>
Many thanks for quality suggestions and input:
Jean-Christophe Hoelt <> (Goom2 main author)
This diff is collapsed.
This diff is collapsed.
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
Basic Installation
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').
It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring. (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.
The file `' (or `') is used to create
`configure' by a program called `autoconf'. You only need
`' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. Run `./configure --help'
for details on some of the pertinent environment variables.
You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment. Here
is an example:
./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
*Note Defining Variables::, for more details.
Compiling For Multiple Architectures
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory. After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.
Installation Names
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
There may be some features `configure' cannot figure out
automatically, but needs to determine by the type of machine the package
will run on. Usually, assuming the package is built to be run on the
_same_ architectures, `configure' can figure that out, but if it prints
a message saying it cannot guess the machine type, give it the
`--build=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:
where SYSTEM can have one of these forms:
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.
If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.
If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.
Sharing Defaults
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/' if it exists, then
`PREFIX/etc/' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Defining Variables
Variables not defined in a site shell script can be set in the
environment passed to `configure'. However, some packages may run
configure again during the build, and the customized values of these
variables may be lost. In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'. For example:
./configure CC=/usr/local2/bin/gcc
will cause the specified gcc to be used as the C compiler (unless it is
overridden in the site shell script).
`configure' Invocation
`configure' recognizes the following options to control how it
Print a summary of the options to `configure', and exit.
Print the version of Autoconf used to generate the `configure'
script, and exit.
Enable the cache: use and save the results of the tests in FILE,
traditionally `config.cache'. FILE defaults to `/dev/null' to
disable caching.
Alias for `--cache-file=config.cache'.
Do not print messages saying which checks are being made. To
suppress all normal output, redirect it to `/dev/null' (any error
messages will still be shown).
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`configure' also accepts some other, not widely useful, options. Run
`configure --help' for more details.
## Process this file with automake to generate a
SUBDIRS = plugins
EXTRA_DIST = libvisual-plugins.spec
This diff is collapsed.
NEWS - list of user-visible changes between releases
of Libvisual plugins.
These are only visible changes, for more details look at the ChangeLog.
New in 0.2.0: 2005-02-09:
* Adding pseudotoad flower actor plugin, ported. (Dennis)
* Adding dancing particles plugin, ported. (Dennis)
* Including G-Force in package. (Dennis)
* Including Nebulus in package. (Dennis)
* Adding corona actor plugin, ported. (Dennis, Jean-Christophe)
* Fixed bumpscope actor plugin. (Dennis)
* MMX code added to JESS, alphablend, oinksie (Dennis)
* Fixing many bugs in plugins. (Everyone)
* Adding VisUI userinterfaces to plugins, not usable yet
because there is no client support yet. (Dennis)
New in 0.1.7: 2004-10-14:
* Updates to API changes.
* All plugins use the VisRandom stuff for randomizing.
* New slide morph plugin.
* Bugfix in flash plugin, that caused it to not work on 8bits depth.
New in 0.1.6: 2004-09-10:
* New ALSA capture input plugin. (Vitaly)
* New MPlayer export input plugin. (Gustavo)
* New Plazma actor plugin, ported from xmms. (Dennis)
* New Jakdaw actor plugin, ported from xmms. (Dennis)
* New Bumpscope actor plugin (has issues), ported from xmms. (Dennis)
* New GdkPixbuf actor plugin to be used with images. (Dennis)
New in 0.1.5: 2004-06-27:
* Removed the videotest plugin, it was used for early debugging.
* Esound dependency lowered from 0.2.29 to 0.2.28.
* Major cleanups and a new build tree.
-- What is libvisual --
Libvisual is a library that acts as a middle layer between
applications that want audio visualisation and audio visualisation
Libvisual is aimed at developers who, have a need for audio
visualisation and those who actually write the visualisation
By writing an audio visualisation plugin for libvisual
every application that uses libvisual is capable of using
this plugin. The application handles the end drawing of
the graphics and thus rendering done by plugins using
libvisual can be drawn everywhere. That is but not limited
to: ascii art, sdl, on gl object as a surface , alpha blended
or just, anywhere.
Libvisual also provides complete easy to use transparant
depth transformation, so that even when the display
isn't supported by the plugin, libvisual will make
it suite. Besides using libvisual for rendering your
2d buffers, you can also render openGL when an openGL
context is open. Besides you don't have to render
to a buffer. You can also make hardware hacks
that do visualisation using libvisual. There are simply no borders
-- Why should you use libvisual --
As an application writer, using libvisual provides you an easy
way to do audio visualisation. Also when using libvisual you'll
have easy access to all the plugins that are written for libvisual.
As an plugin writer, libvisual provides a nice host for your plugin.
It runs analyzes over the audio input for easy usage and it handles
all the displaying stuff through the library and application. And
mainly your plugin will be accessible to all the applications.
-- License --
The plugins in the plugins/ directory are licensed under the GPL
unless noted otherwise.
-- Development --
If you'd like to use libvisual for your applications, write plugins
or hack on the core. Please read HACKING. It contains some very
useful information regarding to policies and such.
-- Requirement --
The library is quite self containing and there is almost no depency
at all to get it working. Libvisual it self does not depend on
anything besides glibc ofcourse.
ESD: To compile the esd input plugin esd and esd development packages
needs to be installed.
Goom2: To compile the goom2 plugin goom2k4-devel-15 or higher needs
to be installed.
lv_gltest: To compile the opengl libraries and development packages
needs to be installed.
-- Compiling and installing --
To set a prefix use --prefix, other options can be seen by
using ./configure --help
This will compile the plugins
make install
This will install the plugins
Update 'rand' usage everywhere, to use randomness from libvisual, through the plugin random context.
update doc on goom version required
check copyrights add copyright notices to all the files.
input/esd: (post 0.1)
Esd plugin isn't timing.
I HATE THE WAY ESD BLOCKS ON EVERYTHING. (actually i just hate esd generally)
(keep in minds that stuff will change within audio after 0.1)
Esd plugin isn't timing, should be fixed when buffer queues land before 0.2 (post 0.1)
ESD BLOCKS ON LIKE EVERYTHING (post 0.1) (if it is fixable at all)
Fix the small issues within the plugin
(alsa_init) Take parameters from the 'params'
field of the given plugin.
Make an usound server plugin (someone else)
Make an artsd plugin (someone else, i'm not running kde)
mplayer mmap output:
visual_video_set_depth (video, V
Make an mplayer mmap thingy plugin (someone else)
finish it actually.
Any other input method:
Make plugins for these (someone else),
remember rather add a plugin than use the callback method
so everyone can make use of it.
A plugin which can be used to easily import frames into libvisual
through mmap, shared mem, function callback. SPECIALIZED PLUGIN
Fix the light.
make sure the states are being resetted very well.
cleanup the code.
translate from french to english (some of the code).
cleanup, hang the configs to params, have some automatic
config cycling.
build tables in strides instead of blocking (post 0.2)
add two param VisColors to use it as a gradient for the palette.
build tables in strides instead of blocking (post 0.2)
could someone from france PLEASE translate
the plugin to english? (post 0.1)
cthugha: (suggestion for someone with too much time)
leaking quite seriously
use extern "C" stuff in the headers
does not compile on alpha (because of mmx, sse, should use a C fallback)
make an libvisual gfx effect that enables libvisual
plugins to draw within goom
port the port that is done by the mythtv people (post 0.1).
use the libvisual palette blender
use the libvisual timer module
fix the 24 bit mode again.
a gdkpixbuf image loader:
implement depth requester, (needs bits in libvisual as well).
implement support for alpha transparency.
implement support for animated image files.
auto sched plugin:
have a auto schedded bin running in an actor so that
gstreamer, xine and such can easily use
the auto scheduler.
Fix leaks in the dtors.
Make the image not a copy, but do a direct pointer
Unmirror the image in the code itself
bin in actor:
have a plugin that embeds a complete bin. that is configurable through params.
More: (post 0.2)
When api is stable, start porting over some more xmms plugins.
morph: (lots of these effects can be taken from the demo world, this should turn
visuals into scenes rather than standalone plugins, o boy!)
mmx sse optimize.
Add a soft edges variant.
make 16, 24, 32 bits support.
blockwise flash in, like in the ODD demo:
negative flash:
that uses the audio as example.
burn in:
JC says he knew what he was talking about
so JC make this !! :)
This diff is collapsed.
This diff is collapsed.
/* Generated from by autoheader. */
/* Alsa Library is from 0.9 series */
#undef HAVE_0_9_X_ALSA
/* Alsa Library is from 1 series */
#undef HAVE_1_X_X_ALSA
/* Define to 1 if you have the <dlfcn.h> header file. */
/* Define to 1 if you have the <fcntl.h> header file. */
/* Define to 1 if you have the `floor' function. */
/* Define to 1 if you have the `getpagesize' function. */
/* Define to 1 if you have the `gettimeofday' function. */
/* Define to 1 if you have the <GL/glx.h> header file. */
#undef HAVE_GL_GLX_H
/* Define to 1 if you have the <GL/gl.h> header file. */
#undef HAVE_GL_GL_H
/* Define to 1 if you have the <inttypes.h> header file. */
/* Define to 1 if you have the `asound' library (-lasound). */
/* Define to 1 if your system has a GNU libc compatible `malloc' function, and
to 0 otherwise. */
/* Define to 1 if you have the `memmove' function. */
/* Define to 1 if you have the <memory.h> header file. */
/* Define to 1 if you have the `memset' function. */
/* Define to 1 if you have a working `mmap' system call. */
#undef HAVE_MMAP
/* Define to 1 if you have the `pow' function. */
#undef HAVE_POW
/* Define to 1 if you have the `sqrt' function. */
#undef HAVE_SQRT
/* Define to 1 if you have the <stdint.h> header file. */
/* Define to 1 if you have the <stdlib.h> header file. */
/* Define to 1 if you have the <strings.h> header file. */
/* Define to 1 if you have the <string.h> header file. */
/* Define to 1 if you have the <sys/stat.h> header file. */
/* Define to 1 if you have the <sys/time.h> header file. */
/* Define to 1 if you have the <sys/types.h> header file. */
/* Define to 1 if you have the <unistd.h> header file. */
/* Define to 1 if you have the <X11/extensions/xf86vmode.h> header file. */
/* Define to 1 if you have the <X11/keysym.h> header file. */
#undef HAVE_X11_KEYSYM_H
/* Define to 1 if you have the <X11/Xlib.h> header file. */
#undef HAVE_X11_XLIB_H
/* Define to 1 if you have the <X11/Xutil.h> header file. */
#undef HAVE_X11_XUTIL_H
/* Define to 1 if you have the <X11/X.h> header file. */
#undef HAVE_X11_X_H
/* XF86VidMode is available */
/* Name of package */
#undef PACKAGE
/* Define to the address where bug reports for this package should be sent. */
/* Define to the full name of this package. */
/* Define to the full name and version of this package. */
/* Define to the one symbol short name of this package. */
/* Define to the version of this package. */
/* Define to 1 if you have the ANSI C header files. */
/* Define to 1 if you can safely include both <sys/time.h> and <time.h>. */
/* Version number of package */
#undef VERSION
/* Define to empty if `const' does not conform to ANSI C. */
#undef const