26 |
called "LSCP" to control the sampler and manage sampler sessions. You either |
called "LSCP" to control the sampler and manage sampler sessions. You either |
27 |
have to send commands manually to LinuxSampler, e.g. by connecting via |
have to send commands manually to LinuxSampler, e.g. by connecting via |
28 |
'telnet' or by using 'netcat' or you might want to use a graphical user |
'telnet' or by using 'netcat' or you might want to use a graphical user |
29 |
interface (frontend) like QSampler. |
interface (frontend) like QSampler (C++/Qt based) or JSampler (Java based). |
30 |
|
|
31 |
For more informations visit http://www.linuxsampler.org/documentation.html |
For more informations visit http://www.linuxsampler.org/documentation.html |
32 |
|
|
36 |
|
|
37 |
o A low latency enabled kernel |
o A low latency enabled kernel |
38 |
(see http://www.linuxsampler.org/faq.html#dropouts). |
(see http://www.linuxsampler.org/faq.html#dropouts). |
39 |
o At least ALSA and optionally JACK and their respective development |
o At least one supported MIDI input system (i.e. ALSA, CoreMIDI or |
40 |
(header) files as MIDI input and audio output drivers. |
MidiShare) and at least one support audio output system (i.e. ALSA, |
41 |
|
JACK or ARTS) have to be installed, along with their respective |
42 |
|
development (header) files. |
43 |
o libgig and its development (header) files for loading Gigasampler |
o libgig and its development (header) files for loading Gigasampler |
44 |
format files. |
format files. |
45 |
o libtool |
o libtool |