1 |
LinuxSampler - modular, streaming capable sampler |
2 |
|
3 |
by Benno Senoner (benno@gardena.net) |
4 |
and Christian Schoenebeck (cuse@users.sourceforge.net) |
5 |
|
6 |
This software is distributed under the GNU General Public License (see |
7 |
COPYING file), and may not be used in commercial applications without asking |
8 |
the authors for permission. |
9 |
|
10 |
LinuxSampler is sampler backend, thus server-like console application. It |
11 |
provides a TCP based network interface with a custom ASCII based protocol |
12 |
called "LSCP" to control the sampler and manage sampler sessions. You either |
13 |
have to send commands manually to LinuxSampler, e.g. by connecting via |
14 |
'telnet' or by using 'netcat' or you might want to use a graphical user |
15 |
interface (frontend) like QSampler. |
16 |
|
17 |
For more informations visit http://www.linuxsampler.org/documentation.html |
18 |
|
19 |
|
20 |
Requirements on Linux |
21 |
--------------------- |
22 |
|
23 |
o A low latency enabled kernel |
24 |
(see http://www.linuxsampler.org/faq.html#dropouts). |
25 |
o At least ALSA and optionally JACK and their respective development |
26 |
(header) files as MIDI input and audio output drivers. |
27 |
o libgig and its development (header) files for loading Gigasampler |
28 |
format files. |
29 |
o If you are compiling from CVS you need to have the autotools installed |
30 |
(autoconf, automake and libtool). |
31 |
|
32 |
|
33 |
Compiling on Linux |
34 |
------------------ |
35 |
|
36 |
a) Compiling and installing directly |
37 |
|
38 |
The general procedure by calling './configure && make' on the source's |
39 |
toplevel directory will compile and 'make install' as root will install |
40 |
LinuxSampler on your system. |
41 |
|
42 |
Note: if you are compiling from CVS you have to explicitly call |
43 |
'make -f Makefile.cvs' before doing the above procedure. This will |
44 |
generate all autotools managed build files. |
45 |
|
46 |
|
47 |
b) Creating Debian packages |
48 |
|
49 |
Simply calling 'dpkg-buildpackage -rfakeroot -b' from the source's |
50 |
toplevel directory will compile and build the Debian binary package. |
51 |
The Debian package will be placed one directory above the source's |
52 |
toplevel directory (thus ../). |
53 |
|
54 |
|
55 |
c) Creating Redhat packages |
56 |
|
57 |
You need to have the rpmbuild tool installed and properly configured to |
58 |
create RPM packages. To create the RPM packages do the following: |
59 |
|
60 |
* Get .spec file generated by ./configure and edit it as appropriate. |
61 |
|
62 |
* Copy the source tarball to "/usr/src/<rpmdir>/SOURCES" directory, |
63 |
where <rpmdir> is dependent to the system you are using. For SuSE |
64 |
<rmpdir> will be "packages", for Mandrake <rpmdir> is "RPM" and for |
65 |
Redhat / Fedora <rpmdir> always equals "redhat". |
66 |
|
67 |
* Build the rpm(s) by invoking 'rpmbuild -bb <specfile>' from the |
68 |
command line. |
69 |
|
70 |
On success, the resulting rpm(s) can usually be found under the proper |
71 |
"/usr/src/<rpmdir>/RPMS/<arch>" directory. |
72 |
|
73 |
|
74 |
Compilation on OSX : Stephane Letz (letz@grame.fr) |
75 |
-------------------------------------------------- |
76 |
|
77 |
The compilation on OSX currently uses an XCode project. |
78 |
|
79 |
- Download and install the JackOSX package (www.jackosx.com) |
80 |
|
81 |
- In the "osx" folder, possibly manually edit the version.h to change the version number |
82 |
|
83 |
- In the XCode project, build the "LinuxSampler" target |
84 |
|