| 186 |
<img src="screenshots/qs_0_2_1_ubuntu_preview.png"> |
<img src="screenshots/qs_0_2_1_ubuntu_preview.png"> |
| 187 |
</a><br> |
</a><br> |
| 188 |
<br> |
<br> |
| 189 |
|
Note however, QSampler does not fully support all features of |
| 190 |
|
the sampler engine (LinuxSampler) yet. Most notably the |
| 191 |
|
engine's instruments database feature is not yet covered by |
| 192 |
|
QSampler. But if you don't need that particular feature, |
| 193 |
|
you're certainly fine with QSampler as well.<br> |
| 194 |
|
<br> |
| 195 |
</li> |
</li> |
| 196 |
|
|
| 197 |
<li> |
<li> |
| 204 |
<a href="screenshots/fantasia.png"><img src="screenshots/fantasia-preview.png"></a> |
<a href="screenshots/fantasia.png"><img src="screenshots/fantasia-preview.png"></a> |
| 205 |
<br> |
<br> |
| 206 |
JSampler supports all features currently available in the |
JSampler supports all features currently available in the |
| 207 |
sampler engine (LinuxSampler).<br> |
sampler engine (LinuxSampler). Also note that even though |
| 208 |
|
JSampler is written in Java and slightly more hungry |
| 209 |
|
regarding resources (compared to QSampler), this usually |
| 210 |
|
does not have any impact on the audio rendering performance |
| 211 |
|
of the sampler, since the engine runs completely independently |
| 212 |
|
and with much higher CPU priority than the frontend(s).<br> |
| 213 |
</li> |
</li> |
| 214 |
</ul> |
</ul> |
| 215 |
<p class="default"> |
<p class="default"> |
| 216 |
It's completely up to you which frontend to use. You could even use |
It's completely up to you which frontend to use. You could even use |
| 217 |
both parallel at the same time for the same sampler engine |
both parallel at the same time for the same sampler engine |
| 218 |
instance, really! ;-) |
instance, really! ;-) You're concerned that your sampler frontend |
| 219 |
|
might waste precious resources of your computer? No problem, just |
| 220 |
|
setup the sampler session for your needs and then quit the |
| 221 |
|
frontend application. The sampler engine doesn't care! It continues |
| 222 |
|
to do its job. You need to change something? Start the frontend |
| 223 |
|
again (or another frontend) and you see what you expect to see: the |
| 224 |
|
current setup and state of the running sampler engine. |
| 225 |
</p> |
</p> |
| 226 |
|
|
| 227 |
<h2>The Format</h2> |
<h2>The Format</h2> |
| 261 |
into the sampler engine, so the engine (and with it the frontends) |
into the sampler engine, so the engine (and with it the frontends) |
| 262 |
knows that gigedit actually exists and can handle the .gig format. |
knows that gigedit actually exists and can handle the .gig format. |
| 263 |
So even though we decoupled the sampler's components into |
So even though we decoupled the sampler's components into |
| 264 |
independent applications, they all work seamlessly together. Just |
independent applications, they all work seamlessly together. |
| 265 |
press the "Edit" button on a channel strip of a frontend and |
<a href="http://download.linuxsampler.org/doc/gigedit/quickstart/gigedit_quickstart.html#live_editing"> |
| 266 |
|
Just press the "Edit" button |
| 267 |
|
</a> on a channel strip of a frontend and |
| 268 |
gigedit will automatically popup on the screen and you're |
gigedit will automatically popup on the screen and you're |
| 269 |
immediately ready to edit your selected instrument, making all your |
immediately ready to edit your selected instrument, making all your |
| 270 |
modifications audible in realtime. Even when editing huge |
modifications audible in realtime. Even when editing huge |
| 287 |
as well as a network interface using an ASCII based protocol which |
as well as a network interface using an ASCII based protocol which |
| 288 |
we call "<a href="http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html" title="LinuxSampler Control Protocol">LSCP</a>" |
we call "<a href="http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html" title="LinuxSampler Control Protocol">LSCP</a>" |
| 289 |
for controlling the sampler engine and managing sampler sessions. |
for controlling the sampler engine and managing sampler sessions. |
| 290 |
Our frontends support that network interface, which also allwos |
Our frontends support that network interface, which also allows to |
| 291 |
control the sampler engine with the GUI frontend(s) remotely from |
control the sampler engine with the GUI frontend(s) remotely from |
| 292 |
another computer, probably even running a completely different |
another computer, probably even running a completely different |
| 293 |
Operating System. |
Operating System. And compared to other remote control solutions, |
| 294 |
|
the frontend won't feel sluggish, as the frontend is running on |
| 295 |
|
your local machine.<br> |
| 296 |
|
<br> |
| 297 |
|
You can also configure your computer to automatically start the |
| 298 |
|
sampler engine and loading your prefered sampler session without |
| 299 |
|
any frontend, simply by using a <i>LSCP session file</i>. How do |
| 300 |
|
you get such a "LSCP session file"? Both frontends write LSCP |
| 301 |
|
session files for you when you request them to save your current |
| 302 |
|
sampler session. And as those LSCP session files are ordinary |
| 303 |
|
human readable text files, you can adjust them with any text |
| 304 |
|
editor if you want. |
| 305 |
|
</p> |
| 306 |
|
|
| 307 |
|
<h2>The Compatibility</h2> |
| 308 |
|
<p class="default"> |
| 309 |
|
LinuxSampler is available for the most popular operating |
| 310 |
|
systems and already supports a variety of audio and MIDI driver |
| 311 |
|
systems on each OS. It does not require any special dedicated |
| 312 |
|
device drivers from the sound card manufacturers, so you can |
| 313 |
|
also use it with cheap consumer cards. Due to its clean design |
| 314 |
|
the sampler can be ported to other operating systems and |
| 315 |
|
extended for further driver systems with a minimum of effort. |
| 316 |
|
So we're prepared for the future! |
| 317 |
</p> |
</p> |
| 318 |
|
|
| 319 |
<h2>The Community</h2> |
<h2>The Community</h2> |
Parent Directory
| 
Revision Log
| 
Patch