--- web/trunk/www.linuxsampler.org/about.html 2008/01/02 19:16:43 1613 +++ web/trunk/www.linuxsampler.org/about.html 2008/09/10 10:15:03 1770 @@ -50,6 +50,11 @@ downloadsout = new Image(); downloadsout.src = dir + "mdownloads.png"; + supportover = new Image(); + supportover.src = dir + "msupporthover.png"; + supportout = new Image(); + supportout.src = dir + "msupport.png"; + developersover = new Image(); developersover.src = dir + "mdevelopershover.png"; @@ -112,6 +117,7 @@ screenshots demos download + support developers faq documentation @@ -125,11 +131,11 @@

The Project

The LinuxSampler project was founded with the - goal to produce a free, open source pure software audio sampler - with professional grade features, comparable to both hardware and - commercial Windows/Mac software samplers - and to introduce new features not yet available by any other - sampler in the world. + goal to produce a free, streaming capable open source pure + software audio sampler with professional grade features, + comparable to both hardware and commercial Windows/Mac software + samplers and to introduce new features not yet available by any + other sampler in the world.

The Engine

@@ -186,6 +192,12 @@

+ Note however, QSampler does not fully support all features of + the sampler engine (LinuxSampler) yet. Most notably the + engine's instruments database feature is not yet covered by + QSampler. But if you don't need that particular feature, + you're certainly fine with QSampler as well.
+
  • @@ -198,13 +210,24 @@
    JSampler supports all features currently available in the - sampler engine (LinuxSampler).
    + sampler engine (LinuxSampler). Also note that even though + JSampler is written in Java and slightly more hungry + regarding resources (compared to QSampler), this usually + does not have any impact on the audio rendering performance + of the sampler, since the engine runs completely independently + and with much higher CPU priority than the frontend(s).

    • It's completely up to you which frontend to use. You could even use both parallel at the same time for the same sampler engine - instance, really! ;-) + instance, really! ;-) You're concerned that your sampler frontend + might waste precious resources of your computer? No problem, just + setup the sampler session for your needs and then quit the + frontend application. The sampler engine doesn't care! It continues + to do its job. You need to change something? Start the frontend + again (or another frontend) and you see what you expect to see: the + current setup and state of the running sampler engine.

    The Format

    @@ -244,8 +267,10 @@ into the sampler engine, so the engine (and with it the frontends) knows that gigedit actually exists and can handle the .gig format. So even though we decoupled the sampler's components into - independent applications, they all work seamlessly together. Just - press the "Edit" button on a channel strip of a frontend and + independent applications, they all work seamlessly together. + + Just press the "Edit" button + on a channel strip of a frontend and gigedit will automatically popup on the screen and you're immediately ready to edit your selected instrument, making all your modifications audible in realtime. Even when editing huge @@ -268,14 +293,41 @@ as well as a network interface using an ASCII based protocol which we call "LSCP" for controlling the sampler engine and managing sampler sessions. - Our frontends support that network interface, which also allwos + Our frontends support that network interface, which also allows to control the sampler engine with the GUI frontend(s) remotely from another computer, probably even running a completely different - Operating System. + Operating System. And compared to other remote control solutions, + the frontend won't feel sluggish, as the frontend is running on + your local machine.
    +
    + You can also configure your computer to automatically start the + sampler engine and loading your prefered sampler session without + any frontend, simply by using a LSCP session file. How do + you get such a "LSCP session file"? Both frontends write LSCP + session files for you when you request them to save your current + sampler session. And as those LSCP session files are ordinary + human readable text files, you can adjust them with any text + editor if you want. +

    + +

    The Compatibility

    +

    + LinuxSampler is available for the most popular operating + systems and already supports a variety of audio and MIDI driver + systems on each OS. It does not require any special dedicated + device drivers from the sound card manufacturers, so you can + also use it with cheap consumer cards. Due to its clean design + the sampler can be ported to other operating systems and + extended for further driver systems with a minimum of effort. + So we're prepared for the future!

    The Community

    + You need a helping hand? You certainly get the answers on your + personal questions on our + web forum.
    +
    All applications are under active development. However we all work on this project for fun in our spare time. There are still so many things to do and our hands are limited. So don't hesitate on @@ -285,7 +337,7 @@ documentation, providing artwork, themes for frontends, etc. helps us and all users a lot! Simply subscribe to our - mailing list + developers mailing list and we'll of course take you by the hand in case you want to participate with active source code development. Don't be afraid! You have your own ideas and concepts for making the sampler better?