tap-plugins-doc-20140526/ 0000755 0002004 0002004 00000000000 12340666244 013136 5 ustar tom tom tap-plugins-doc-20140526/index.html 0000644 0002004 0002004 00000011643 12340666065 015141 0 ustar tom tom
TAP-plugins Tom's Audio Processing plugins for audio engineering on the Linux platform |
|
This website holds information concerning some audio software usable on UNIX-like operating systems, particularly GNU/Linux. The project producing this software started out in January 2004 when the author took the plunge of using Linux Audio (particularly Ardour) in his recording studio. Initially four LADSPA plugins were written, but the number of available plugins steadily increased over time. Today, the package comprises an established set of plugins.
It was in early June 2004 that the author realized he needed a reverb solution with such flexibility that a LADSPA plugin could never provide; not because the sound processing was lacking, but user accessibility to the internal structure and variables of the reverb algorithm was needed. As a result, TAP Reverb Editor was written as a separate JACK application.
Today the project provides two software packages for download:
Please go to the SourceForge project page to download any of these packages. The authoritative source repository of tap-plugins is on GitHub; feel free to fork and send pull requests.
As a supplement, this website (which acts both as a homepage and as a manual for all TAP-plugins software) is available for download as a separate package called tap-plugins-doc (get it from the SourceForge project page).
TAP-plugins is being developed by Tom Szilagyi. You can send him mail to <tomszilagyi at gmail>. (You should generally receive a reply in 48 hours, if your mail deserves it; please note that I have a life, I have to sleep sometimes and I live on the other side of the planet.)
If you'd just like to thank me for the software, consider buying me an item on my public Amazon wishlist.
TAP-plugins are released under the GNU General Public License, version 2. See the file COPYING (included in the tarball releases of all software packages) for details.
DISCLAIMER: The plugins described here are available to you free of charge, and you are welcome to examine their internal workings, modify and re-distribute them. But keep in mind that TAP-plugins is provided "AS IS", and it comes with ABSOLUTELY NO WARRANTY of any kind, either expressed or implied, included, but not limited to, the implied warranties of MERCHANTABILITY and FITNESS FOR A PARTICULAR PURPOSE. Again, see the file COPYING for details.
TAP-plugins Tom's Audio Processing plugins for audio engineering on the Linux platform |
|
You need the following libraries to compile TAP Reverb Editor:
You also need to have:
If you have all these, just go on and type ./configure
,
then make
. The configure
script will
complain if anything is missing. Note: when you install packages like
JACK from source, always specify the correct prefix parameter to the
package's configure script; this way you can be sure the package will
be installed in the right location (the question is usually whether
the local
path should be used,
eg. /usr/local
vs. /usr
).
After a clean make
, type make install
(as
root) to install the executable. If you want to change the default
place (which depends on your system, but is usually something like
/usr/local/bin
), please pass the appropriate
--prefix
option to ./configure
.
IMPORTANT: TAP Reverb Editor writes to and reads from a file
named .reverbed
, which is always expected to be found in
the home directory of the user who runs the program. TAP Reverb Editor
comes with a default .reverbed
file (located in the
src/
subdirectory along with the source code), which you
should manually copy to all those user's home directories who will
want to use the program -- 'make install' does not do this for
you! Don't forget to set the file permissions so that the user who
will run the program has read and write permissions on his/her copy.
Finally (if everything went fine) you can start the program by typing
reverbed
. You need an already running JACK server of
course.