Compiling Tony » History » Version 3

Chris Cannam, 2014-06-17 10:17 AM

1 1 Chris Cannam
h1. Compiling Tony
2 1 Chris Cannam
3 1 Chris Cannam
_Warning: Not all that easy_
4 1 Chris Cannam
5 1 Chris Cannam
At the moment you need to compile three separate parts in order to have a working installation of Tony:
6 1 Chris Cannam
7 1 Chris Cannam
 # The Tony application itself
8 1 Chris Cannam
 # The pYIN Vamp plugin used for general pitch and note estimation
9 1 Chris Cannam
 # The CHP Vamp plugin used for detailed pitch analysis
10 1 Chris Cannam
11 1 Chris Cannam
The source code for the plugins is all included in the source package for Tony, in subdirectories called @pyin@ and @chp@ respectively, so you only need to download the one package. But after you've downloaded it, you need to compile and install the plugins separately from the main Tony application.
12 1 Chris Cannam
13 1 Chris Cannam
h2. On Linux
14 1 Chris Cannam
15 2 Chris Cannam
Tony depends on a lot of additional packages, including Qt (either Qt4 or Qt5), the Vamp plugin SDK, Rubber Band, libsamplerate, libsndfile, libmad, libid3tag, Serd and Sord, liboggz, libfishsound, FFTW3, JACK, and PulseAudio. The configure script should test for these.
16 1 Chris Cannam
17 2 Chris Cannam
 * Download the source code package from the "download page":/projects/tony/files, or check out the "Mercurial repository":/projects/tony/repository.
18 2 Chris Cannam
 * Run @./configure@ and (if that succeeds) run @make@.
19 3 Chris Cannam
 * For each of the @pyin@ and @chp@ subdirectories:
20 3 Chris Cannam
   ** @cd@ to that directory
21 3 Chris Cannam
   ** run @make -f Makefile.linux64@
22 3 Chris Cannam
   ** if that succeeds, install the compiled plugin by copying @*.so@ to the directory @$HOME/vamp/@ (create this directory first if it doesn't exist).