/[svn]/web/trunk/www.linuxsampler.org/documentation.html
ViewVC logotype

Diff of /web/trunk/www.linuxsampler.org/documentation.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1241 by schoenebeck, Sat Jun 16 16:15:03 2007 UTC revision 1377 by schoenebeck, Wed Oct 3 21:05:46 2007 UTC
# Line 137  Line 137 
137                          edge development version of gigedit from CVS.                          edge development version of gigedit from CVS.
138                          </p>                          </p>
139    
140                            <h2>JSampler</h2>
141                            <p class="default">
142                            JSampler is an opensource, platform-independent,
143                            GUI front-end for LinuxSampler, written entirely in Java.
144                            Read the <a href="jsampler/manual/html/jsampler.html">JSampler manual</a>
145                            for more information.
146                            </p>
147    
148                            <h2>libgig</h2>
149                            <p class="default">
150                            libgig is a C++ library used to load and modify Gigasampler format files.
151                            If you're a developer and might want to use libgig, here is its
152                            <a href="http://download.linuxsampler.org/doc/libgig/api/">API documentation</a>
153                            (automatically daily updated from CVS).
154                            </p>
155    
156                            <h2>liblscp</h2>
157                            <p class="default">
158                            liblscp is C library as convenient wrapper around the <i>LinuxSampler Control Protocol</i>.
159                            If you're a developer and might want to use liblscp, here is its
160                            <a href="http://download.linuxsampler.org/doc/liblscp/">API documentation</a>
161                            (automatically daily updated from CVS).
162                            </p>
163    
164                          <h2>LSCP Reference</h2>                          <h2>LSCP Reference</h2>
165                          <p class="default">                          <p class="default">
166                          The following document defines the network protocol with which LinuxSampler can be controlled.                          The following documents define the <i>LinuxSampler Control Protocol</i>,
167                            a network protocol with which LinuxSampler can be controlled locally as well as remotely.
168                          As this is a simple ASCII based protocol it's possible to write a frontend for LinuxSampler in                          As this is a simple ASCII based protocol it's possible to write a frontend for LinuxSampler in
169                          any programming language and GUI library. There's still a big demand especially for a Gtk and                          any programming language and GUI library. There's still a big demand especially for a Gtk and
170                          ncurses based frontend, so be encouraged and let                          ncurses based frontend, so be encouraged and let
171                          <a href="http://www.linuxsampler.org/developers.html">us</a> know if you wrote a frontend for                          <a href="http://www.linuxsampler.org/developers.html">us</a> know if you wrote a frontend for
172                          LinuxSampler! This is the protocol specification of the old                          LinuxSampler!
173                          official release of LinuxSampler (0.3.3):                          </p>
174                          <br>  
175                          </p>        <table class="decorated">
176                          <center>          <thead>
177                          LinuxSampler Control Protocol v1.0            <tr>
178                          (<a href="http://www.linuxsampler.org/api/lscp-1.0.txt">ASCII</a>,              <td class="decorated_header">Protocol Name</td>
179                          <a href="http://www.linuxsampler.org/api/lscp-1.0.html">HTML</a>,              <td class="decorated_header">Document Types</td>
180                          <a href="http://www.linuxsampler.org/api/lscp-1.0.xml">XML</a>)              <td class="decorated_header">Description</td>
181                          </center>            </tr>
182                          <p class="default">          </thead>
183                          This is the protocol specification of the latest          <tbody>
184                          official release of LinuxSampler (0.4.0):            <tr>
185                          <br>              <td class="decorated">LSCP&nbsp;1.0</td>
186                          </p>              <td class="decorated">
187                          <center>                <a href="http://www.linuxsampler.org/api/lscp-1.0.txt">ASCII</a>,
188                          LinuxSampler Control Protocol v1.1                <a href="http://www.linuxsampler.org/api/lscp-1.0.html">HTML</a>,
189                          (<a href="http://www.linuxsampler.org/api/lscp-1.1.txt">ASCII</a>,                <a href="http://www.linuxsampler.org/api/lscp-1.0.xml">XML</a>
190                          <a href="http://www.linuxsampler.org/api/lscp-1.1.html">HTML</a>,              </td>
191                          <a href="http://www.linuxsampler.org/api/lscp-1.1.xml">XML</a>)              <td class="decorated">
192                          </center>                Protocol specification of the old official release of LinuxSampler (0.3.3).
193                          <p class="default">              </td>
194                          The following is the very latest draft of the protocol (which            </tr>
195                          usually reflects the latest development state from CVS or may            <tr>
196                          even not be implemented yet):              <td class="decorated">LSCP&nbsp;1.1</td>
197                          <br>              <td class="decorated">
198                          </p>                <a href="http://www.linuxsampler.org/api/lscp-1.1.txt">ASCII</a>,
199                          <center>                <a href="http://www.linuxsampler.org/api/lscp-1.1.html">HTML</a>,
200                          LinuxSampler Control Protocol Draft                <a href="http://www.linuxsampler.org/api/lscp-1.1.xml">XML</a>
201                          (<a href="http://www.linuxsampler.org/api/draft-linuxsampler-protocol.txt">ASCII</a>,              </td>
202                          <a href="http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html">HTML</a>,              <td class="decorated">
203                          <a href="http://cvs.linuxsampler.org/cgi-bin/viewcvs.cgi/*checkout*/linuxsampler/Documentation/lscp.xml?rev=HEAD&content-type=text/xml">XML</a>)                Protocol specification of the latest official release of LinuxSampler (0.4.0).
204                          </center>              </td>
205              </tr>
206              <tr>
207                <td class="decorated">LSCP&nbsp;draft</td>
208                <td class="decorated">
209                  <a href="http://www.linuxsampler.org/api/draft-linuxsampler-protocol.txt">ASCII</a>,
210                  <a href="http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html">HTML</a>,
211                  <a href="http://cvs.linuxsampler.org/cgi-bin/viewcvs.cgi/*checkout*/linuxsampler/Documentation/lscp.xml?rev=HEAD&content-type=text/xml">XML</a>
212                </td>
213                <td class="decorated">
214                  Very latest draft of the protocol (which usually reflects the
215                  latest development state from CVS or may even not be implemented
216                  yet).
217                </td>
218              </tr>
219            </tbody>
220          </table>
221    
222                          <p class="default">                          <p class="default">
223                          The protocol will be extended from time to time. You may look at the                          The protocol will be extended from time to time. You may look at the
224                          <a href="features.html#LSCP">features</a> site to see which control                          <a href="features.html#LSCP">features</a> site to see which control
# Line 192  Line 234 
234                          examples to give you a good starting point for writing your own ones. Adjust it to your needs                          examples to give you a good starting point for writing your own ones. Adjust it to your needs
235                          and send it to the running linuxsampler application with:                          and send it to the running linuxsampler application with:
236                          </p>                          </p>
237                          <table class="default" border="0" cellpadding="1" cellspacing="5">                          <pre class="code">cat yourscript.lscp | netcat localhost 8888</pre>
238                                  <tr>                          <p class="default">
239                                    <td><pre class="code">1</pre>                          Optionally you can also use a graphical frontend like QSampler one time to setup a working
240                                    </td>                          sampler session for your needs and save it. Because you have to know that the files saved
241                                    <td width="100%">                          by our frontends are actually pure LSCP scripts, thus you can i.e. use those files simply with
242                                      <pre class="code">cat yourscript.lscp | netcat -t localhost 8888</pre>                          the mentioned netcat command from above to setup the sampler session without a frontend.
243                                    </td>                          </p>
                                 </tr>  
                         </table>  
244                          <p class="default">                          <p class="default">
245                          Here is a simple LSCP example which uses ALSA as MIDI input and as audio output driver as well,                          Here is a simple LSCP example which uses ALSA as MIDI input and as audio output driver as well,
246                          it creates only one sampler channel using the Gigasampler engine and loads a Piano instrument                          it creates only one sampler channel using the Gigasampler engine and loads a Piano instrument
247                          on that sampler channel:                          on that sampler channel:
248                          </p>                          </p>
249                          <table class="default" border="0" cellpadding="1" cellspacing="5">                          <pre class="code">#enable echo mode
                                 <tr>  
                                   <td><pre class="code">1  
 2  
 3  
 4  
 5  
 6  
 7  
 8  
 9  
 10  
 11  
 12  
 13  
 14  
 15  
 16  
 17  
 18  
 19  
 20  
 21  
 22  
 23  
 24  
 25  
 26  
 27  
 28  
 29</pre>  
                                   </td>  
                                   <td width="100%">  
                                     <pre class="code">#enable echo mode  
250  SET ECHO 1  SET ECHO 1
251    
252  # load the ALSA audio driver  # load the ALSA audio driver
# Line 268  GET CHANNEL INFO 0 Line 275  GET CHANNEL INFO 0
275    
276  # quit connection  # quit connection
277  QUIT</pre>  QUIT</pre>
                                   </td>  
                                 </tr>  
                         </table>  
278                          <p class="default">                          <p class="default">
279                          The next example uses JACK as audio output driver instead and automatically connects the two                          The next example uses JACK as audio output driver instead and automatically connects the two
280                          output channels of LS's JACK client to the first two ALSA PCM channels, so you can hear                          output channels of LS's JACK client to the first two ALSA PCM channels, so you can hear
281                          something without having to manually connect it e.g. with qjackctl:                          something without having to manually connect it e.g. with qjackctl:
282                          </p>                          </p>
283                          <table class="default" border="0" cellpadding="1" cellspacing="5">                          <pre class="code">#enable echo mode
                                 <tr>  
                                   <td><pre class="code">1  
 2  
 3  
 4  
 5  
 6  
 7  
 8  
 9  
 10  
 11  
 12  
 13  
 14  
 15  
 16  
 17  
 18  
 19  
 20  
 21  
 22  
 23  
 24  
 25  
 26  
 27  
 28  
 29  
 30  
 31  
 32</pre>  
                                   </td>  
                                   <td width="100%">  
                                     <pre class="code">#enable echo mode  
284  SET ECHO 1  SET ECHO 1
285    
286  # load the JACK audio driver  # load the JACK audio driver
# Line 344  GET CHANNEL INFO 0 Line 312  GET CHANNEL INFO 0
312    
313  # quit connection  # quit connection
314  QUIT</pre>  QUIT</pre>
                                   </td>  
                                 </tr>  
                         </table>  
315                          <p class="default">                          <p class="default">
316                          The next example is a bit more complex.                          The next example is a bit more complex.
317                          It shows how to setup a more realistic sampler session, handle routing of MIDI input channels,                          It shows how to setup a more realistic sampler session, handle routing of MIDI input channels,
# Line 358  QUIT</pre> Line 323  QUIT</pre>
323                          the second pair of the JACK client's output channels. That way you could e.g. record the output                          the second pair of the JACK client's output channels. That way you could e.g. record the output
324                          of those two sampler channels independently or apply independent LADSPA effects on it.                          of those two sampler channels independently or apply independent LADSPA effects on it.
325                          </p>                          </p>
326                          <table class="default" border="0" cellpadding="1" cellspacing="5">                          <pre class="code"># enable echo mode
                                 <tr>  
                                   <td><pre class="code">1  
 2  
 3  
 4  
 5  
 6  
 7  
 8  
 9  
 10  
 11  
 12  
 13  
 14  
 15  
 16  
 17  
 18  
 19  
 20  
 21  
 22  
 23  
 24  
 25  
 26  
 27  
 28  
 29  
 30  
 31  
 32  
 33  
 34  
 35  
 36  
 37  
 38  
 39  
 40  
 41  
 42  
 43  
 44  
 45  
 46  
 47  
 48  
 49  
 50</pre>  
                                   </td>  
                                   <td width="100%">  
                                     <pre class="code"># enable echo mode  
327  SET ECHO 1  SET ECHO 1
328    
329  # load audio and MIDI driver  # load audio and MIDI driver
# Line 462  SET AUDIO_OUTPUT_CHANNEL_PARAMETER 0 3 J Line 373  SET AUDIO_OUTPUT_CHANNEL_PARAMETER 0 3 J
373  # not necessary, just to see our setup  # not necessary, just to see our setup
374  GET CHANNEL INFO 0  GET CHANNEL INFO 0
375  GET CHANNEL INFO 1</pre>  GET CHANNEL INFO 1</pre>
                                   </td>  
                                 </tr>  
                         </table>  
376                          <p class="default">                          <p class="default">
377                          For a detailed description about LSCP read the <a href="api/draft-linuxsampler-protocol.html">LSCP reference</a>.                          For a detailed description about LSCP read the <a href="api/draft-linuxsampler-protocol.html">LSCP reference</a>.
378                          Be welcome to ask details on the mailing list.                          Be welcome to ask details on the mailing list.
Legend:
Removed from v.1241  
changed lines
  Added in v.1377
  ViewVC Help
Powered by ViewVC