/[svn]/linuxsampler/trunk/Documentation/lscp.xml
ViewVC logotype

Contents of /linuxsampler/trunk/Documentation/lscp.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1407 - (show annotations) (download) (as text)
Fri Oct 12 12:35:58 2007 UTC (16 years, 5 months ago) by schoenebeck
File MIME type: text/xml
File size: 378648 byte(s)
* slightly renamed recently added "EDIT INSTRUMENT <sampler-chan>" LSCP
  command to "EDIT CHANNEL INSTRUMENT <sampler-chan>"

1 <?xml version="1.0" encoding="UTF-8"?>
2
3 <!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
4 <!ENTITY rfc2119 PUBLIC ''
5 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml'>
6 ]>
7
8 <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
9
10 <?rfc toc="yes" ?>
11 <?rfc symrefs="yes" ?>
12 <?rfc sortrefs="yes"?>
13 <?rfc iprnotified="no" ?>
14
15 <!-- FIXME: next attribute should actually be "yes", temporarily disbled due
16 to an annoying "missing Normative/Informative References" error message -->
17 <?rfc strict="no" ?>
18
19 <rfc category="std" ipr="full3978" docName="LSCP 1.2cvs">
20 <front>
21 <title>LinuxSampler Control Protocol (draft)</title>
22 <author initials='C.S.' surname="Schoenebeck" fullname='C.
23 Schoenebeck'>
24 <organization>
25 Interessengemeinschaft Software Engineering e. V.
26 </organization>
27 <address>
28 <postal>
29 <street>Max-Planck-Str. 39</street>
30 <!-- <code>74081</code> -->
31 <city>74081 Heilbronn</city>
32 <country>Germany</country>
33 </postal>
34 <email>schoenebeck at software minus engineering dot org</email>
35 </address>
36 </author>
37 <date month="October" year="2007"/>
38 <workgroup>LinuxSampler Developers</workgroup>
39 <keyword>LSCP</keyword>
40 <abstract>
41 <t>The LinuxSampler Control Protocol (LSCP) is an
42 application-level protocol primarily intended for local and
43 remote controlling the LinuxSampler backend application, which is a
44 sophisticated server-like console application essentially playing
45 back audio samples and manipulating the samples in real time to
46 certain extent.</t>
47 </abstract>
48 </front>
49
50 <middle>
51 <section title="Requirements notation">
52 <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
53 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
54 and "OPTIONAL" in this document are to be interpreted as
55 described in <xref target="RFC2119"/>.</t>
56
57 <t>This protocol is always case-sensitive if not explicitly
58 claimed the opposite.</t>
59
60 <t>In examples, "C:" and "S:" indicate lines sent by the client
61 (front-end) and server (LinuxSampler) respectively. Lines in
62 examples must be interpreted as every line being CRLF
63 terminated (carriage return character followed by line feed
64 character as defined in the ASCII standard <xref target="RFC20"/>),
65 thus the following example:</t>
66
67 <t>
68 <list>
69 <t>C: "some line"</t>
70 <t>&nbsp;&nbsp;&nbsp;"another line"</t>
71 </list>
72 </t>
73
74 <t>must actually be interpreted as client sending the following
75 message:</t>
76
77 <t>
78 <list>
79 <t>"some line&lt;CR&gt;&lt;LF&gt;another
80 line&lt;CR&gt;&lt;LF&gt;"</t>
81 </list>
82 </t>
83
84 <t>where &lt;CR&gt; symbolizes the carriage return character and
85 &lt;LF&gt; the line feed character as defined in the ASCII
86 standard.</t>
87
88 <t>Due to technical reasons, messages can arbitrary be
89 fragmented, means the following example:</t>
90
91 <t>
92 <list>
93 <t>S: "abcd"</t>
94 </list>
95 </t>
96
97 <t>could also happen to be sent in three messages like in the
98 following sequence scenario:</t>
99
100 <t>
101 <list style="symbols">
102 <t>server sending message "a"</t>
103 <t>followed by a delay (pause) with
104 arbitrary duration</t>
105 <t>followed by server sending message
106 "bcd&lt;CR&gt;"</t>
107 <t>again followed by a delay (pause) with arbitrary
108 duration</t>
109 <t>followed by server sending the message
110 "&lt;LF&gt;"</t>
111 </list>
112 </t>
113
114 <t>where again &lt;CR&gt; and &lt;LF&gt; symbolize the carriage
115 return and line feed characters respectively.</t>
116 </section>
117
118 <section title="Versioning of this specification" anchor="LSCP versioning">
119 <t>LSCP will certainly be extended and enhanced by-and-by. Each official
120 release of the LSCP specification will be tagged with a unique version
121 tuple. The version tuple consists at least of a major and minor version
122 number like:
123 </t>
124 <t>
125 <list>
126 <t>"1.2"</t>
127 </list>
128 </t>
129 <t>
130 In this example the major version number would be "1" and the minor
131 version number would be "2". Note that the version tuple might also
132 have more than two elements. The major version number defines a
133 group of backward compatible versions. That means a frontend is
134 compatible to the connected sampler if and only if the LSCP versions
135 to which each of the two parties complies to, match both of the
136 following rules:
137 </t>
138 <t>Compatibility:</t>
139 <t>
140 <list style="numbers">
141 <t>The frontend's LSCP major version and the sampler's LSCP
142 major version are exactly equal.</t>
143 <t>The frontend's LSCP minor version is less or equal than
144 the sampler's LSCP minor version.</t>
145 </list>
146 </t>
147 <t>
148 Compatibility can only be claimed if both rules are true.
149 The frontend can use the
150 <xref target="GET SERVER INFO">"GET SERVER INFO"</xref> command to
151 get the version of the LSCP specification the sampler complies with.
152 </t>
153 </section>
154
155 <section title="Introduction">
156 <t>LinuxSampler is a so called software sampler application
157 capable to playback audio samples from a computer's Random
158 Access Memory (RAM) as well as directly streaming it from disk.
159 LinuxSampler is designed to be modular. It provides several so
160 called "sampler engines" where each engine is specialized for a
161 certain purpose. LinuxSampler has virtual channels which will be
162 referred in this document as "sampler channels". The channels
163 are in such way virtual as they can be connected to an
164 arbitrary MIDI input method and arbitrary MIDI channel (e.g.
165 sampler channel 17 could be connected to an ALSA sequencer
166 device 64:0 and listening to MIDI channel 1 there). Each sampler
167 channel will be associated with an instance of one of the available
168 sampler engines (e.g. GigEngine, DLSEngine). The audio output of
169 each sampler channel can be routed to an arbitrary audio output
170 method (ALSA / JACK) and an arbitrary audio output channel
171 there.</t>
172 </section>
173
174 <section title="Focus of this protocol">
175 <t>Main focus of this protocol is to provide a way to configure
176 a running LinuxSampler instance and to retrieve information
177 about it. The focus of this protocol is not to provide a way to
178 control synthesis parameters or even to trigger or release
179 notes. Or in other words; the focus are those functionalities
180 which are not covered by MIDI or which may at most be handled
181 via MIDI System Exclusive Messages.</t>
182 </section>
183
184 <section title="Communication Overview">
185 <t>There are two distinct methods of communication between a
186 running instance of LinuxSampler and one or more control
187 applications, so called "front-ends": a simple request/response
188 communication method used by the clients to give commands to the
189 server as well as to inquire about server's status and a
190 subscribe/notify communication method used by the client to
191 subscribe to and receive notifications of certain events as they
192 happen on the server. The latter needs more effort to be
193 implemented in the front-end application. The two communication
194 methods will be described next.</t>
195
196 <section title="Request/response communication method">
197 <t>This simple communication method is based on
198 <xref target="RFC793">TCP</xref>. The
199 front-end application establishes a TCP connection to the
200 LinuxSampler instance on a certain host system. Then the
201 front-end application will send certain ASCII based commands
202 as defined in this document (every command line must be CRLF
203 terminated - see "Conventions used in this document" at the
204 beginning of this document) and the LinuxSampler application
205 will response after a certain process time with an
206 appropriate ASCII based answer, also as defined in this
207 document. So this TCP communication is simply based on query
208 and answer paradigm. That way LinuxSampler is only able to
209 answer on queries from front-ends, but not able to
210 automatically send messages to the client if it's not asked
211 to. The fronted should not reconnect to LinuxSampler for
212 every single command, instead it should keep the connection
213 established and simply resend message(s) for subsequent
214 commands. To keep information in the front-end up-to-date
215 the front-end has to periodically send new requests to get
216 the current information from the LinuxSampler instance. This
217 is often referred to as "polling". While polling is simple
218 to implement and may be OK to use in some cases, there may
219 be disadvantages to polling such as network traffic overhead
220 and information being out of date.
221 It is possible for a client or several clients to open more
222 than one connection to the server at the same time. It is
223 also possible to send more than one request to the server
224 at the same time but if those requests are sent over the
225 same connection server MUST execute them sequentially. Upon
226 executing a request server will produce a result set and
227 send it to the client. Each and every request made by the
228 client MUST result in a result set being sent back to the
229 client. No other data other than a result set may be sent by
230 a server to a client. No result set may be sent to a client
231 without the client sending request to the server first. On
232 any particular connection, result sets MUST be sent in their
233 entirety without being interrupted by other result sets. If
234 several requests got queued up at the server they MUST be
235 processed in the order they were received and result sets
236 MUST be sent back in the same order.</t>
237
238 <section title="Result format">
239 <t>Result set could be one of the following types:</t>
240 <t>
241 <list style="numbers">
242 <t>Normal</t>
243 <t>Warning</t>
244 <t>Error</t>
245 </list>
246 </t>
247 <t>Warning and Error result sets MUST be single line and
248 have the following format:</t>
249 <t>
250 <list style="symbols">
251 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;"</t>
252 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;"</t>
253 </list>
254 </t>
255 <t>Where &lt;warning-code&gt; and &lt;error-code&gt; are
256 numeric unique identifiers of the warning or error and
257 &lt;warning-message&gt; and &lt;error-message&gt; are
258 human readable descriptions of the warning or error
259 respectively.</t>
260 <t>Examples:</t>
261 <t>
262 <list>
263 <t>C: "LOAD INSTRUMENT '/home/me/Boesendorfer24bit.gig" 0 0</t>
264 <t>S: "WRN:32:This is a 24 bit patch which is not supported natively yet."</t>
265 </list>
266 </t>
267 <t>
268 <list>
269 <t>C: "GET AUDIO_OUTPUT_DRIVER_PARAMETER INFO ALSA EAR"</t>
270 <t>S: "ERR:3456:Audio output driver 'ALSA' does not have a parameter 'EAR'."</t>
271 </list>
272 </t>
273 <t>
274 <list>
275 <t>C: "GET AUDIO_OUTPUT_DEVICE INFO 123456"</t>
276 <t>S: "ERR:9:There is no audio output device with index 123456."</t>
277 </list>
278 </t>
279 <t>Normal result sets could be:</t>
280 <t>
281 <list style="numbers">
282 <t>Empty</t>
283 <t>Single line</t>
284 <t>Multi-line</t>
285 </list>
286 </t>
287 <t> Empty result set is issued when the server only
288 needed to acknowledge the fact that the request was
289 received and it was processed successfully and no
290 additional information is available. This result set has
291 the following format:</t>
292 <t>
293 <list>
294 <t>"OK"</t>
295 </list>
296 </t>
297 <t>Example:</t>
298 <t>
299 <list>
300 <t>C: "SET AUDIO_OUTPUT_DEVICE_PARAMETER 0 CHANNELS=4"</t>
301 <t>S: "OK"</t>
302 </list>
303 </t>
304 <t>Single line result sets are command specific. One
305 example of a single line result set is an empty line.
306 Multi-line result sets are command specific and may
307 include one or more lines of information. They MUST
308 always end with the following line:</t>
309 <t>
310 <list>
311 <t>"."</t>
312 </list>
313 </t>
314 <t>Example:</t>
315 <t>
316 <list>
317 <t>C: "GET AUDIO_OUTPUT_DEVICE INFO 0"</t>
318 <t>S: "DRIVER: ALSA"</t>
319 <t>&nbsp;&nbsp;&nbsp;"CHANNELS: 2"</t>
320 <t>&nbsp;&nbsp;&nbsp;"SAMPLERATE: 44100"</t>
321 <t>&nbsp;&nbsp;&nbsp;"ACTIVE: true"</t>
322 <t>&nbsp;&nbsp;&nbsp;"FRAGMENTS: 2"</t>
323 <t>&nbsp;&nbsp;&nbsp;"FRAGMENTSIZE: 128"</t>
324 <t>&nbsp;&nbsp;&nbsp;"CARD: '0,0'"</t>
325 <t>&nbsp;&nbsp;&nbsp;"."</t>
326 </list>
327 </t>
328 <t>In addition to above mentioned formats, warnings and
329 empty result sets MAY be indexed. In this case, they
330 have the following formats respectively:</t>
331 <t>
332 <list style="symbols">
333 <t>"WRN[&lt;index&gt;]:&lt;warning-code&gt;:&lt;warning-message&gt;"</t>
334 <t>"OK[&lt;index&gt;]"</t>
335 </list>
336 </t>
337 <t>where &lt;index&gt; is command specific and is used
338 to indicate channel number that the result set was
339 related to or other integer value.</t>
340 <t>Each line of the result set MUST end with
341 &lt;CRLF&gt;.</t>
342 <t>Examples:</t>
343 <t>
344 <list>
345 <t>C: "ADD CHANNEL"</t>
346 <t>S: "OK[12]"</t>
347 </list>
348 </t>
349 <t>
350 <list>
351 <t>C: "CREATE AUDIO_OUTPUT_DEVICE ALSA SAMPLERATE=96000"</t>
352 <t>S: "WRN[0]:32:Sample rate not supported, using 44100 instead."</t>
353 </list>
354 </t>
355 </section>
356 </section>
357 <section title="Subscribe/notify communication method">
358 <t>This more sophisticated communication method is actually
359 only an extension of the simple request/response
360 communication method. The front-end still uses a TCP
361 connection and sends the same commands on the TCP
362 connection. Two extra commands are SUBSCRIBE and UNSUBSCRIBE
363 commands that allow a client to tell the server that it is
364 interested in receiving notifications about certain events
365 as they happen on the server. The SUBSCRIBE command has the
366 following syntax:</t>
367
368 <t>
369 <list>
370 <t>SUBSCRIBE &lt;event-id&gt;</t>
371 </list>
372 </t>
373
374 <t>where &lt;event-id&gt; will be replaced by the respective
375 event that client wants to subscribe to. Upon receiving such
376 request, server SHOULD respond with OK and start sending
377 EVENT notifications when a given even has occurred to the
378 front-end when an event has occurred. It MAY be possible
379 certain events may be sent before OK response during real
380 time nature of their generation. Event messages have the
381 following format:</t>
382
383 <t>
384 <list>
385 <t>NOTIFY:&lt;event-id&gt;:&lt;custom-event-data&gt;</t>
386 </list>
387 </t>
388
389 <t>where &lt;event-id&gt; uniquely identifies the event that
390 has occurred and &lt;custom-event-data&gt; is event
391 specific.</t>
392
393 <t>Several rules must be followed by the server when
394 generating events:</t>
395
396 <t>
397 <list style="numbers">
398 <t>Events MUST NOT be sent to any client who has not
399 issued an appropriate SUBSCRIBE command.</t>
400 <t>Events MUST only be sent using the same
401 connection that was used to subscribe to them.</t>
402 <t>When response is being sent to the client, event
403 MUST be inserted in the stream before or after the
404 response, but NOT in the middle. Same is true about
405 the response. It should never be inserted in the
406 middle of the event message as well as any other
407 response.</t>
408 </list>
409 </t>
410
411 <t>If the client is not interested in a particular event
412 anymore it MAY issue UNSUBSCRIBE command using the following
413 syntax:</t>
414
415 <t>
416 <list>
417 <t>UNSUBSCRIBE &lt;event-id&gt;</t>
418 </list>
419 </t>
420
421 <t>where &lt;event-id&gt; will be replace by the respective
422 event that client is no longer interested in receiving. For
423 a list of supported events see <xref target="events" />.</t>
424
425 <t>Example: the fill states of disk stream buffers have
426 changed on sampler channel 4 and the LinuxSampler instance
427 will react by sending the following message to all clients
428 who subscribed to this event:</t>
429
430 <t>
431 <list>
432 <t>NOTIFY:CHANNEL_BUFFER_FILL:4 [35]62%,[33]80%,[37]98%</t>
433 </list>
434 </t>
435
436 <t>Which means there are currently three active streams on
437 sampler channel 4, where the stream with ID "35" is filled
438 by 62%, stream with ID 33 is filled by 80% and stream with
439 ID 37 is filled by 98%.</t>
440
441 <t>Clients may choose to open more than one connection to
442 the server and use some connections to receive notifications
443 while using other connections to issue commands to the
444 back-end. This is entirely legal and up to the
445 implementation. This does not change the protocol in any way
446 and no special restrictions exist on the server to allow or
447 disallow this or to track what connections belong to what
448 front-ends. Server will listen on a single port, accept
449 multiple connections and support protocol described in this
450 specification in it's entirety on this single port on each
451 connection that it accepted.</t>
452
453 <t>Due to the fact that TCP is used for this communication,
454 dead peers will be detected automatically by the OS TCP
455 stack. While it may take a while to detect dead peers if no
456 traffic is being sent from server to client (TCP keep-alive
457 timer is set to 2 hours on many OSes) it will not be an
458 issue here as when notifications are sent by the server,
459 dead client will be detected quickly.</t>
460
461 <t>When connection is closed for any reason server MUST
462 forget all subscriptions that were made on this connection.
463 If client reconnects it MUST resubscribe to all events that
464 it wants to receive.</t>
465
466 </section>
467 </section>
468
469 <section title="Description for control commands" anchor="control_commands">
470 <t>This chapter will describe the available control commands
471 that can be sent on the TCP connection in detail. Some certain
472 commands (e.g. <xref target="GET CHANNEL INFO">"GET CHANNEL INFO"</xref>
473 or <xref target="GET ENGINE INFO">"GET ENGINE INFO"</xref>) lead to
474 multiple-line responses. In this case LinuxSampler signals the
475 end of the response by a "." (single dot) line.</t>
476
477 <section title="Ignored lines and comments">
478 <t>White lines, that is lines which only contain space and
479 tabulator characters, and lines that start with a "#"
480 character are ignored, thus it's possible for example to
481 group commands and to place comments in a LSCP script
482 file.</t>
483 </section>
484
485 <section title="Configuring audio drivers">
486 <t>Instances of drivers in LinuxSampler are called devices.
487 You can use multiple audio devices simultaneously, e.g. to
488 output the sound of one sampler channel using the ALSA audio
489 output driver, and on another sampler channel you might want
490 to use the JACK audio output driver. For particular audio
491 output systems it's also possible to create several devices
492 of the same audio output driver, e.g. two separate ALSA
493 audio output devices for using two different sound cards at
494 the same time. This chapter describes all commands to
495 configure LinuxSampler's audio output devices and their
496 parameters.</t>
497
498 <t>Instead of defining commands and parameters for each
499 driver individually, all possible parameters, their meanings
500 and possible values have to be obtained at runtime. This
501 makes the protocol a bit abstract, but has the advantage,
502 that front-ends can be written independently of what drivers
503 are currently implemented and what parameters these drivers
504 are actually offering. This means front-ends can even handle
505 drivers which are implemented somewhere in future without
506 modifying the front-end at all.</t>
507
508 <t>Note: examples in this chapter showing particular
509 parameters of drivers are not meant as specification of the
510 drivers' parameters. Driver implementations in LinuxSampler
511 might have complete different parameter names and meanings
512 than shown in these examples or might change in future, so
513 these examples are only meant for showing how to retrieve
514 what parameters drivers are offering, how to retrieve their
515 possible values, etc.</t>
516
517 <section title="Getting amount of available audio output drivers" anchor="GET AVAILABLE_AUDIO_OUTPUT_DRIVERS">
518 <t>Use the following command to get the number of
519 audio output drivers currently available for the
520 LinuxSampler instance:</t>
521 <t>
522 <list>
523 <t>GET AVAILABLE_AUDIO_OUTPUT_DRIVERS</t>
524 </list>
525 </t>
526 <t>Possible Answers:</t>
527 <t>
528 <list>
529 <t>LinuxSampler will answer by sending the
530 number of audio output drivers.</t>
531 </list>
532 </t>
533 <t>Example:</t>
534 <t>
535 <list>
536 <t>C: "GET AVAILABLE_AUDIO_OUTPUT_DRIVERS"</t>
537 <t>S: "2"</t>
538 </list>
539 </t>
540 </section>
541
542 <section title="Getting all available audio output drivers" anchor="LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS">
543 <t>Use the following command to list all audio output
544 drivers currently available for the LinuxSampler
545 instance:</t>
546 <t>
547 <list>
548 <t>LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS</t>
549 </list>
550 </t>
551 <t>Possible Answers:</t>
552 <t>
553 <list>
554 <t>LinuxSampler will answer by sending comma
555 separated character strings, each symbolizing an
556 audio output driver.</t>
557 </list>
558 </t>
559 <t>Example:</t>
560 <t>
561 <list>
562 <t>C: "LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS"</t>
563 <t>S: "ALSA,JACK"</t>
564 </list>
565 </t>
566 </section>
567
568 <section title="Getting information about a specific audio
569 output driver" anchor="GET AUDIO_OUTPUT_DRIVER INFO">
570 <t>Use the following command to get detailed information
571 about a specific audio output driver:</t>
572 <t>
573 <list>
574 <t>GET AUDIO_OUTPUT_DRIVER INFO
575 &lt;audio-output-driver&gt;</t>
576 </list>
577 </t>
578 <t>Where &lt;audio-output-driver&gt; is the name of the
579 audio output driver, returned by the
580 <xref target="LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS">"LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS"</xref> command.</t>
581 <t>Possible Answers:</t>
582 <t>
583 <list>
584 <t>LinuxSampler will answer by sending a
585 &lt;CRLF&gt; separated list. Each answer line
586 begins with the information category name
587 followed by a colon and then a space character
588 &lt;SP&gt; and finally the info character string
589 to that info category. At the moment the
590 following information categories are
591 defined:</t>
592
593 <t>
594 <list>
595 <t>DESCRIPTION -
596 <list>
597 <t> character string describing the
598 audio output driver</t>
599 </list>
600 </t>
601
602 <t>VERSION -
603 <list>
604 <t>character string reflecting the
605 driver's version</t>
606 </list>
607 </t>
608
609 <t>PARAMETERS -
610 <list>
611 <t>comma separated list of all
612 parameters available for the given
613 audio output driver, at least
614 parameters 'channels', 'samplerate'
615 and 'active' are offered by all audio
616 output drivers</t>
617 </list>
618 </t>
619 </list>
620 </t>
621
622 <t>The mentioned fields above don't have to be
623 in particular order.</t>
624 </list>
625 </t>
626 <t>Example:</t>
627 <t>
628 <list>
629 <t>C: "GET AUDIO_OUTPUT_DRIVER INFO ALSA"</t>
630 <t>S: "DESCRIPTION: Advanced Linux Sound
631 Architecture"</t>
632 <t>&nbsp;&nbsp;&nbsp;"VERSION: 1.0"</t>
633 <t>&nbsp;&nbsp;&nbsp;"PARAMETERS:
634 DRIVER,CHANNELS,SAMPLERATE,ACTIVE,FRAGMENTS,
635 FRAGMENTSIZE,CARD"</t>
636 <t>&nbsp;&nbsp;&nbsp;"."</t>
637 </list>
638 </t>
639 </section>
640
641 <section title="Getting information about specific audio
642 output driver parameter" anchor="GET AUDIO_OUTPUT_DRIVER_PARAMETER INFO">
643 <t>Use the following command to get detailed information
644 about a specific audio output driver parameter:</t>
645 <t>
646 <list>
647 <t>GET AUDIO_OUTPUT_DRIVER_PARAMETER INFO &lt;audio&gt; &lt;prm&gt; [&lt;deplist&gt;]</t>
648 </list>
649 </t>
650 <t>Where &lt;audio&gt; is the name of the audio output
651 driver as returned by the <xref target="LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS">
652 "LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS"</xref> command,
653 &lt;prm&gt; a specific parameter name for which information should be
654 obtained (as returned by the
655 <xref target="GET AUDIO_OUTPUT_DRIVER INFO">"GET AUDIO_OUTPUT_DRIVER INFO"</xref> command) and
656 &lt;deplist&gt; is an optional list of parameters on which the sought
657 parameter &lt;prm&gt; depends on, &lt;deplist&gt; is a list of key-value
658 pairs in form of "key1=val1 key2=val2 ...", where character string values
659 are encapsulated into apostrophes ('). Arguments given with &lt;deplist&gt;
660 which are not dependency parameters of &lt;prm&gt; will be ignored, means
661 the front-end application can simply put all parameters into &lt;deplist&gt;
662 with the values already selected by the user.</t>
663 <t>Possible Answers:</t>
664 <t>
665 <list>
666 <t>LinuxSampler will answer by sending a
667 &lt;CRLF&gt; separated list.
668 Each answer line begins with the information category name
669 followed by a colon and then a space character &lt;SP&gt; and
670 finally
671 the info character string to that info category. There are
672 information which is always returned, independently of the
673 given driver parameter and there are optional information
674 which is only shown dependently to given driver parameter. At
675 the moment the following information categories are defined:</t>
676 </list>
677 </t>
678
679 <t>
680 <list>
681 <t>TYPE -
682 <list>
683 <t>either "BOOL" for boolean value(s) or
684 "INT" for integer
685 value(s) or "FLOAT" for dotted number(s) or "STRING" for
686 character string(s)
687 (always returned, no matter which driver parameter)</t>
688 </list>
689 </t>
690
691 <t>DESCRIPTION -
692 <list>
693 <t>arbitrary text describing the purpose of the parameter
694 (always returned, no matter which driver parameter)</t>
695 </list>
696 </t>
697
698 <t>MANDATORY -
699 <list>
700 <t>either true or false, defines if this parameter must be
701 given when the device is to be created with the
702 <xref target="CREATE AUDIO_OUTPUT_DEVICE">'CREATE AUDIO_OUTPUT_DEVICE'</xref>
703 command (always returned, no matter which driver parameter)</t>
704 </list>
705 </t>
706
707 <t>FIX -
708 <list>
709 <t>either true or false, if false then this parameter can
710 be changed at any time, once the device is created by
711 the <xref target="CREATE AUDIO_OUTPUT_DEVICE">'CREATE AUDIO_OUTPUT_DEVICE'</xref>
712 command (always returned, no matter which driver parameter)</t>
713 </list>
714 </t>
715
716 <t>MULTIPLICITY -
717 <list>
718 <t>either true or false, defines if this parameter allows
719 only one value or a list of values, where true means
720 multiple values and false only a single value allowed
721 (always returned, no matter which driver parameter)</t>
722 </list>
723 </t>
724
725 <t>DEPENDS -
726 <list>
727 <t>comma separated list of parameters this parameter depends
728 on, means the values for fields 'DEFAULT', 'RANGE_MIN',
729 'RANGE_MAX' and 'POSSIBILITIES' might depend on these
730 listed parameters, for example assuming that an audio
731 driver (like the ALSA driver) offers parameters 'card'
732 and 'samplerate' then parameter 'samplerate' would
733 depend on 'card' because the possible values for
734 'samplerate' depends on the sound card which can be
735 chosen by the 'card' parameter
736 (optionally returned, dependent to driver parameter)</t>
737 </list>
738 </t>
739
740 <t>DEFAULT -
741 <list>
742 <t>reflects the default value for this parameter which is
743 used when the device is created and not explicitly
744 given with the <xref target="CREATE AUDIO_OUTPUT_DEVICE">
745 'CREATE AUDIO_OUTPUT_DEVICE'</xref> command,
746 in case of MULTIPLCITY=true, this is a comma separated
747 list, that's why character strings are encapsulated into
748 apostrophes (')
749 (optionally returned, dependent to driver parameter)</t>
750 </list>
751 </t>
752
753 <t>RANGE_MIN -
754 <list>
755 <t>defines lower limit of the allowed value range for this
756 parameter, can be an integer value as well as a dotted
757 number, this parameter is often used in conjunction
758 with RANGE_MAX, but may also appear without
759 (optionally returned, dependent to driver parameter)</t>
760 </list>
761 </t>
762
763 <t>RANGE_MAX -
764 <list>
765 <t>defines upper limit of the allowed value range for this
766 parameter, can be an integer value as well as a dotted
767 number, this parameter is often used in conjunction with
768 RANGE_MIN, but may also appear without
769 (optionally returned, dependent to driver parameter)</t>
770 </list>
771 </t>
772
773 <t>POSSIBILITIES -
774 <list>
775 <t>comma separated list of possible values for this
776 parameter, character strings are encapsulated into
777 apostrophes
778 (optionally returned, dependent to driver parameter)</t>
779 </list>
780 </t>
781 </list>
782 </t>
783
784 <t>The mentioned fields above don't have to be in particular order.</t>
785
786 <t>Examples:</t>
787 <t>
788 <list>
789 <t>C: "GET AUDIO_OUTPUT_DRIVER_PARAMETER INFO ALSA CARD"</t>
790 <t>S: "DESCRIPTION: sound card to be used"</t>
791 <t>&nbsp;&nbsp;&nbsp;"TYPE: STRING"</t>
792 <t>&nbsp;&nbsp;&nbsp;"MANDATORY: false"</t>
793 <t>&nbsp;&nbsp;&nbsp;"FIX: true"</t>
794 <t>&nbsp;&nbsp;&nbsp;"MULTIPLICITY: false"</t>
795 <t>&nbsp;&nbsp;&nbsp;"DEFAULT: '0,0'"</t>
796 <t>&nbsp;&nbsp;&nbsp;"POSSIBILITIES: '0,0','1,0','2,0'"</t>
797 <t>&nbsp;&nbsp;&nbsp;"."</t>
798 </list>
799 </t>
800 <t>
801 <list>
802 <t>C: "GET AUDIO_OUTPUT_DRIVER_PARAMETER INFO ALSA SAMPLERATE"</t>
803 <t>S: "DESCRIPTION: output sample rate in Hz"</t>
804 <t>&nbsp;&nbsp;&nbsp;"TYPE: INT"</t>
805 <t>&nbsp;&nbsp;&nbsp;"MANDATORY: false"</t>
806 <t>&nbsp;&nbsp;&nbsp;"FIX: false"</t>
807 <t>&nbsp;&nbsp;&nbsp;"MULTIPLICITY: false"</t>
808 <t>&nbsp;&nbsp;&nbsp;"DEPENDS: card"</t>
809 <t>&nbsp;&nbsp;&nbsp;"DEFAULT: 44100"</t>
810 <t>&nbsp;&nbsp;&nbsp;"."</t>
811 </list>
812 </t>
813 <t>
814 <list>
815 <t>C: "GET AUDIO_OUTPUT_DRIVER_PARAMETER INFO ALSA SAMPLERATE CARD='0,0'"</t>
816 <t>S: "DESCRIPTION: output sample rate in Hz"</t>
817 <t>&nbsp;&nbsp;&nbsp;"TYPE: INT"</t>
818 <t>&nbsp;&nbsp;&nbsp;"MANDATORY: false"</t>
819 <t>&nbsp;&nbsp;&nbsp;"FIX: false"</t>
820 <t>&nbsp;&nbsp;&nbsp;"MULTIPLICITY: false"</t>
821 <t>&nbsp;&nbsp;&nbsp;"DEPENDS: card"</t>
822 <t>&nbsp;&nbsp;&nbsp;"DEFAULT: 44100"</t>
823 <t>&nbsp;&nbsp;&nbsp;"RANGE_MIN: 22050"</t>
824 <t>&nbsp;&nbsp;&nbsp;"RANGE_MAX: 96000"</t>
825 <t>&nbsp;&nbsp;&nbsp;"."</t>
826 </list>
827 </t>
828 </section>
829
830 <section title="Creating an audio output device" anchor="CREATE AUDIO_OUTPUT_DEVICE">
831 <t>Use the following command to create a new audio output device for the desired audio output system:</t>
832
833 <t>
834 <list>
835 <t>CREATE AUDIO_OUTPUT_DEVICE &lt;audio-output-driver&gt; [&lt;param-list&gt;]</t>
836 </list>
837 </t>
838
839 <t>Where &lt;audio-output-driver&gt; should be replaced by the desired audio
840 output system as returned by the
841 <xref target="LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS">"LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS"</xref>
842 command and &lt;param-list&gt; by an optional list of driver
843 specific parameters in form of "key1=val1 key2=val2 ...", where
844 character string values should be encapsulated into apostrophes (').
845 Note that there might be drivers which require parameter(s) to be
846 given with this command. Use the previously described commands in
847 this chapter to get this information.</t>
848
849 <t>Possible Answers:</t>
850 <t>
851 <list>
852 <t>"OK[&lt;device-id&gt;]" -
853 <list>
854 <t>in case the device was successfully created, where
855 &lt;device-id&gt; is the numerical ID of the new device</t>
856 </list>
857 </t>
858 <t>"WRN[&lt;device-id&gt;]:&lt;warning-code&gt;:&lt;warning-message&gt;" -
859 <list>
860 <t>in case the device was created successfully, where
861 &lt;device-id&gt; is the numerical ID of the new device, but there
862 are noteworthy issue(s) related (e.g. sound card doesn't
863 support given hardware parameters and the driver is using
864 fall-back values), providing an appropriate warning code and
865 warning message</t>
866 </list>
867 </t>
868 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
869 <list>
870 <t>in case it failed, providing an appropriate error code and error message</t>
871 </list>
872 </t>
873 </list>
874 </t>
875 <t>Examples:</t>
876 <t>
877 <list>
878 <t>C: "CREATE AUDIO_OUTPUT_DEVICE ALSA"</t>
879 <t>S: "OK[0]"</t>
880 </list>
881 </t>
882 <t>
883 <list>
884 <t>C: "CREATE AUDIO_OUTPUT_DEVICE ALSA CARD='2,0' SAMPLERATE=96000"</t>
885 <t>S: "OK[1]"</t>
886 </list>
887 </t>
888 </section>
889
890 <section title="Destroying an audio output device" anchor="DESTROY AUDIO_OUTPUT_DEVICE">
891 <t>Use the following command to destroy a created output device:</t>
892 <t>
893 <list>
894 <t>DESTROY AUDIO_OUTPUT_DEVICE &lt;device-id&gt;</t>
895 </list>
896 </t>
897 <t>Where &lt;device-id&gt; should be replaced by the numerical ID of the
898 audio output device as given by the
899 <xref target="CREATE AUDIO_OUTPUT_DEVICE">"CREATE AUDIO_OUTPUT_DEVICE"</xref>
900 or <xref target="LIST AUDIO_OUTPUT_DEVICES">"LIST AUDIO_OUTPUT_DEVICES"</xref>
901 command.</t>
902 <t>Possible Answers:</t>
903 <t>
904 <list>
905 <t>"OK" -
906 <list>
907 <t>in case the device was successfully destroyed</t>
908 </list>
909 </t>
910 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
911 <list>
912 <t>in case the device was destroyed successfully, but there are
913 noteworthy issue(s) related (e.g. an audio over ethernet
914 driver was unloaded but the other host might not be
915 informed about this situation), providing an appropriate
916 warning code and warning message</t>
917 </list>
918 </t>
919 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
920 <list>
921 <t>in case it failed, providing an appropriate error code and
922 error message</t>
923 </list>
924 </t>
925 </list>
926 </t>
927 <t>Example:</t>
928 <t>
929 <list>
930 <t>C: "DESTROY AUDIO_OUTPUT_DEVICE 0"</t>
931 <t>S: "OK"</t>
932 </list>
933 </t>
934 </section>
935
936 <section title="Getting all created audio output device count" anchor="GET AUDIO_OUTPUT_DEVICES">
937 <t>Use the following command to count all created audio output devices:</t>
938 <t>
939 <list>
940 <t>GET AUDIO_OUTPUT_DEVICES</t>
941 </list>
942 </t>
943 <t>Possible Answers:</t>
944 <t>
945 <list>
946 <t>LinuxSampler will answer by sending the current number of all
947 audio output devices.</t>
948 </list>
949 </t>
950 <t>Example:</t>
951 <t>
952 <list>
953 <t>C: "GET AUDIO_OUTPUT_DEVICES"</t>
954 <t>S: "4"</t>
955 </list>
956 </t>
957 </section>
958
959 <section title="Getting all created audio output device list" anchor="LIST AUDIO_OUTPUT_DEVICES">
960 <t>Use the following command to list all created audio output devices:</t>
961 <t>
962 <list>
963 <t>LIST AUDIO_OUTPUT_DEVICES</t>
964 </list>
965 </t>
966 <t>Possible Answers:</t>
967 <t>
968 <list>
969 <t>LinuxSampler will answer by sending a comma separated list with
970 the numerical IDs of all audio output devices.</t>
971 </list>
972 </t>
973 <t>Example:</t>
974 <t>
975 <list>
976 <t>C: "LIST AUDIO_OUTPUT_DEVICES"</t>
977 <t>S: "0,1,4,5"</t>
978 </list>
979 </t>
980 </section>
981
982 <section title="Getting current settings of an audio output device" anchor="GET AUDIO_OUTPUT_DEVICE INFO">
983 <t>Use the following command to get current settings of a specific, created audio output device:</t>
984 <t>
985 <list>
986 <t>GET AUDIO_OUTPUT_DEVICE INFO &lt;device-id&gt;</t>
987 </list>
988 </t>
989 <t>Where &lt;device-id&gt; should be replaced by numerical ID
990 of the audio output device as e.g. returned by the
991 <xref target="LIST AUDIO_OUTPUT_DEVICES">"LIST AUDIO_OUTPUT_DEVICES"</xref> command.</t>
992 <t>Possible Answers:</t>
993 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
994 Each answer line begins with the information category name
995 followed by a colon and then a space character &lt;SP&gt; and finally
996 the info character string to that info category. As some
997 parameters might allow multiple values, character strings are
998 encapsulated into apostrophes ('). At the moment the following
999 information categories are defined (independently of device):</t>
1000 <t>
1001 <list>
1002 <t>DRIVER -
1003 <list>
1004 <t>identifier of the used audio output driver, as also
1005 returned by the
1006 <xref target="LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS">
1007 "LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS"</xref>
1008 command</t>
1009 </list>
1010 </t>
1011 <t>CHANNELS -
1012 <list>
1013 <t>amount of audio output channels this device currently
1014 offers</t>
1015 </list>
1016 </t>
1017 <t>SAMPLERATE -
1018 <list>
1019 <t>playback sample rate the device uses</t>
1020 </list>
1021 </t>
1022 <t>ACTIVE -
1023 <list>
1024 <t>either true or false, if false then the audio device is
1025 inactive and doesn't output any sound, nor do the
1026 sampler channels connected to this audio device render
1027 any audio</t>
1028 </list>
1029 </t>
1030 </list>
1031 </t>
1032 <t>The mentioned fields above don't have to be in particular
1033 order. The fields above are only those fields which are
1034 returned by all audio output devices. Every audio output driver
1035 might have its own, additional driver specific parameters (see
1036 <xref target="GET AUDIO_OUTPUT_DRIVER INFO" />)
1037 which are also returned by this command.</t>
1038 <t>Example:</t>
1039 <t>
1040 <list>
1041 <t>C: "GET AUDIO_OUTPUT_DEVICE INFO 0"</t>
1042 <t>S: "DRIVER: ALSA"</t>
1043 <t>&nbsp;&nbsp;&nbsp;"CHANNELS: 2"</t>
1044 <t>&nbsp;&nbsp;&nbsp;"SAMPLERATE: 44100"</t>
1045 <t>&nbsp;&nbsp;&nbsp;"ACTIVE: true"</t>
1046 <t>&nbsp;&nbsp;&nbsp;"FRAGMENTS: 2"</t>
1047 <t>&nbsp;&nbsp;&nbsp;"FRAGMENTSIZE: 128"</t>
1048 <t>&nbsp;&nbsp;&nbsp;"CARD: '0,0'"</t>
1049 <t>&nbsp;&nbsp;&nbsp;"."</t>
1050 </list>
1051 </t>
1052 </section>
1053
1054
1055 <section title="Changing settings of audio output devices" anchor="SET AUDIO_OUTPUT_DEVICE_PARAMETER">
1056 <t>Use the following command to alter a specific setting of a created audio output device:</t>
1057 <t>
1058 <list>
1059 <t>SET AUDIO_OUTPUT_DEVICE_PARAMETER &lt;device-id&gt; &lt;key&gt;=&lt;value&gt;</t>
1060 </list>
1061 </t>
1062 <t>Where &lt;device-id&gt; should be replaced by the numerical ID of the
1063 audio output device as given by the
1064 <xref target="CREATE AUDIO_OUTPUT_DEVICE">"CREATE AUDIO_OUTPUT_DEVICE"</xref>
1065 or <xref target="LIST AUDIO_OUTPUT_DEVICES">"LIST AUDIO_OUTPUT_DEVICES"</xref>
1066 command, &lt;key&gt; by the name of the parameter to change
1067 and &lt;value&gt; by the new value for this parameter.</t>
1068 <t>Possible Answers:</t>
1069 <t>
1070 <list>
1071 <t>"OK" -
1072 <list>
1073 <t>in case setting was successfully changed</t>
1074 </list>
1075 </t>
1076 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
1077 <list>
1078 <t>in case setting was changed successfully, but there are
1079 noteworthy issue(s) related, providing an appropriate
1080 warning code and warning message</t>
1081 </list>
1082 </t>
1083 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
1084 <list>
1085 <t>in case it failed, providing an appropriate error code and
1086 error message</t>
1087 </list>
1088 </t>
1089 </list>
1090 </t>
1091 <t>Example:</t>
1092 <t>
1093 <list>
1094 <t>C: "SET AUDIO_OUTPUT_DEVICE_PARAMETER 0 FRAGMENTSIZE=128"</t>
1095 <t>S: "OK"</t>
1096 </list>
1097 </t>
1098 </section>
1099
1100 <section title="Getting information about an audio channel" anchor="GET AUDIO_OUTPUT_CHANNEL INFO">
1101 <t>Use the following command to get information about an audio channel:</t>
1102 <t>
1103 <list>
1104 <t>GET AUDIO_OUTPUT_CHANNEL INFO &lt;device-id&gt; &lt;audio-chan&gt;</t>
1105 </list>
1106 </t>
1107 <t>Where &lt;device-id&gt; is the numerical ID of the audio output device as given by the
1108 <xref target="CREATE AUDIO_OUTPUT_DEVICE">"CREATE AUDIO_OUTPUT_DEVICE"</xref>
1109 or <xref target="LIST AUDIO_OUTPUT_DEVICES">"LIST AUDIO_OUTPUT_DEVICES"</xref>
1110 command and &lt;audio-chan&gt; the audio channel number.</t>
1111 <t>Possible Answers:</t>
1112 <t>
1113 <list>
1114 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
1115 Each answer line begins with the information category name
1116 followed by a colon and then a space character &lt;SP&gt; and finally
1117 the info character string to that info category. At the moment
1118 the following information categories are defined:</t>
1119
1120 <t>
1121 <list>
1122 <t>NAME -
1123 <list>
1124 <t>arbitrary character string naming the channel, which
1125 doesn't have to be unique (always returned by all audio channels)</t>
1126 </list>
1127 </t>
1128 <t>IS_MIX_CHANNEL -
1129 <list>
1130 <t>either true or false, a mix-channel is not a real,
1131 independent audio channel, but a virtual channel which
1132 is mixed to another real channel, this mechanism is
1133 needed for sampler engines which need more audio
1134 channels than the used audio system might be able to offer
1135 (always returned by all audio channels)</t>
1136 </list>
1137 </t>
1138 <t>MIX_CHANNEL_DESTINATION -
1139 <list>
1140 <t>numerical ID (positive integer including 0)
1141 which reflects the real audio channel (of the same audio
1142 output device) this mix channel refers to, means where
1143 the audio signal actually will be routed / added to
1144 (only returned in case the audio channel is mix channel)</t>
1145 </list>
1146 </t>
1147 </list>
1148 </t>
1149 </list>
1150 </t>
1151
1152 <t>The mentioned fields above don't have to be in particular
1153 order. The fields above are only those fields which are
1154 generally returned for the described cases by all audio
1155 channels regardless of the audio driver. Every audio channel
1156 might have its own, additional driver and channel specific
1157 parameters.</t>
1158
1159 <t>Examples:</t>
1160
1161 <t>
1162 <list>
1163 <t>C: "GET AUDIO_OUTPUT_CHANNEL INFO 0 0"</t>
1164 <t>S: "NAME: studio monitor left"</t>
1165 <t>&nbsp;&nbsp;&nbsp;"IS_MIX_CHANNEL: false"</t>
1166 <t>&nbsp;&nbsp;&nbsp;"."</t>
1167 </list>
1168 </t>
1169
1170 <t>
1171 <list>
1172 <t>C: "GET AUDIO_OUTPUT_CHANNEL INFO 0 1"</t>
1173 <t>S: "NAME: studio monitor right"</t>
1174 <t>&nbsp;&nbsp;&nbsp;"IS_MIX_CHANNEL: false"</t>
1175 <t>&nbsp;&nbsp;&nbsp;"."</t>
1176 </list>
1177 </t>
1178
1179 <t>
1180 <list>
1181 <t>C: "GET AUDIO_OUTPUT_CHANNEL INFO 0 2"</t>
1182 <t>S: "NAME: studio monitor left"</t>
1183 <t>&nbsp;&nbsp;&nbsp;"IS_MIX_CHANNEL: true"</t>
1184 <t>&nbsp;&nbsp;&nbsp;"MIX_CHANNEL_DESTINATION: 1"</t>
1185 <t>&nbsp;&nbsp;&nbsp;"."</t>
1186 </list>
1187 </t>
1188
1189 <t>
1190 <list>
1191 <t>C: "GET AUDIO_OUTPUT_CHANNEL INFO 1 0"</t>
1192 <t>S: "NAME: 'ardour (left)'"</t>
1193 <t>&nbsp;&nbsp;&nbsp;"IS_MIX_CHANNEL: false"</t>
1194 <t>&nbsp;&nbsp;&nbsp;"JACK_BINDINGS: 'ardour:0'"</t>
1195 <t>&nbsp;&nbsp;&nbsp;"."</t>
1196 </list>
1197 </t>
1198 </section>
1199
1200 <section title="Getting information about specific audio channel parameter" anchor="GET AUDIO_OUTPUT_CHANNEL_PARAMETER INFO">
1201 <t>Use the following command to get detailed information about specific audio channel parameter:</t>
1202
1203 <t>
1204 <list>
1205 <t>GET AUDIO_OUTPUT_CHANNEL_PARAMETER INFO &lt;dev-id&gt; &lt;chan&gt; &lt;param&gt;</t>
1206 </list>
1207 </t>
1208
1209 <t>Where &lt;dev-id&gt; is the numerical ID of the audio output device as returned by the
1210 <xref target="CREATE AUDIO_OUTPUT_DEVICE">"CREATE AUDIO_OUTPUT_DEVICE"</xref>
1211 or <xref target="LIST AUDIO_OUTPUT_DEVICES">"LIST AUDIO_OUTPUT_DEVICES"</xref>
1212 command, &lt;chan&gt; the audio channel number
1213 and &lt;param&gt; a specific channel parameter name for which information should
1214 be obtained (as returned by the <xref target="GET AUDIO_OUTPUT_CHANNEL INFO">
1215 "GET AUDIO_OUTPUT_CHANNEL INFO"</xref> command).</t>
1216 <t>Possible Answers:</t>
1217
1218 <t>
1219 <list>
1220 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
1221 Each answer line begins with the information category name
1222 followed by a colon and then a space character &lt;SP&gt; and finally
1223 the info character string to that info category. There are
1224 information which is always returned, independently of the
1225 given channel parameter and there is optional information
1226 which is only shown dependently to the given audio channel. At
1227 the moment the following information categories are defined:</t>
1228 <t>
1229 <list>
1230 <t>TYPE -
1231 <list>
1232 <t>either "BOOL" for boolean value(s) or "INT" for integer
1233 value(s) or "FLOAT" for dotted number(s) or "STRING" for
1234 character string(s)
1235 (always returned)</t>
1236 </list>
1237 </t>
1238 <t>DESCRIPTION -
1239 <list>
1240 <t>arbitrary text describing the purpose of the parameter (always returned)</t>
1241 </list>
1242 </t>
1243 <t>FIX -
1244 <list>
1245 <t>either true or false, if true then this parameter is
1246 read only, thus cannot be altered
1247 (always returned)</t>
1248 </list>
1249 </t>
1250 <t>MULTIPLICITY -
1251 <list>
1252 <t>either true or false, defines if this parameter allows
1253 only one value or a list of values, where true means
1254 multiple values and false only a single value allowed
1255 (always returned)</t>
1256 </list>
1257 </t>
1258 <t>RANGE_MIN -
1259 <list>
1260 <t>defines lower limit of the allowed value range for this
1261 parameter, can be an integer value as well as a dotted
1262 number, usually used in conjunction with 'RANGE_MAX',
1263 but may also appear without
1264 (optionally returned, dependent to driver and channel
1265 parameter)</t>
1266 </list>
1267 </t>
1268 <t>RANGE_MAX -
1269 <list>
1270 <t>defines upper limit of the allowed value range for this
1271 parameter, can be an integer value as well as a dotted
1272 number, usually used in conjunction with 'RANGE_MIN',
1273 but may also appear without
1274 (optionally returned, dependent to driver and channel
1275 parameter)</t>
1276 </list>
1277 </t>
1278 <t>POSSIBILITIES -
1279 <list>
1280 <t>comma separated list of possible values for this
1281 parameter, character strings are encapsulated into
1282 apostrophes
1283 (optionally returned, dependent to driver and channel
1284 parameter)</t>
1285 </list>
1286 </t>
1287 </list>
1288 </t>
1289 <t>The mentioned fields above don't have to be in particular order.</t>
1290 </list>
1291 </t>
1292 <t>Example:</t>
1293 <t>
1294 <list>
1295 <t>C: "GET AUDIO_OUTPUT_CHANNEL_PARAMETER INFO 1 0 JACK_BINDINGS"</t>
1296 <t>S: "DESCRIPTION: bindings to other JACK clients"</t>
1297 <t>&nbsp;&nbsp;&nbsp;"TYPE: STRING"</t>
1298 <t>&nbsp;&nbsp;&nbsp;"FIX: false"</t>
1299 <t>&nbsp;&nbsp;&nbsp;"MULTIPLICITY: true"</t>
1300 <t>&nbsp;&nbsp;&nbsp;"POSSIBILITIES: 'PCM:0','PCM:1','ardour:0','ardour:1'"</t>
1301 <t>&nbsp;&nbsp;&nbsp;"."</t>
1302 </list>
1303 </t>
1304 </section>
1305
1306 <section title="Changing settings of audio output channels" anchor="SET AUDIO_OUTPUT_CHANNEL_PARAMETER">
1307 <t>Use the following command to alter a specific setting of an audio output channel:</t>
1308 <t>
1309 <list>
1310 <t>SET AUDIO_OUTPUT_CHANNEL_PARAMETER &lt;dev-id&gt; &lt;chn&gt; &lt;key&gt;=&lt;value&gt;</t>
1311 </list>
1312 </t>
1313 <t>Where &lt;dev-id&gt; should be replaced by the numerical ID of the audio output device as returned by the
1314 <xref target="CREATE AUDIO_OUTPUT_DEVICE">"CREATE AUDIO_OUTPUT_DEVICE"</xref>
1315 or <xref target="LIST AUDIO_OUTPUT_DEVICES">"LIST AUDIO_OUTPUT_DEVICES"</xref>
1316 command, &lt;chn&gt; by the audio channel number, &lt;key&gt; by the name of the
1317 parameter to change and &lt;value&gt; by the new value for this parameter.</t>
1318 <t>Possible Answers:</t>
1319 <t>
1320 <list>
1321 <t>"OK" -
1322 <list>
1323 <t>in case setting was successfully changed</t>
1324 </list>
1325 </t>
1326 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
1327 <list>
1328 <t>in case setting was changed successfully, but there are
1329 noteworthy issue(s) related, providing an appropriate
1330 warning code and warning message</t>
1331 </list>
1332 </t>
1333 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
1334 <list>
1335 <t>in case it failed, providing an appropriate error code and
1336 error message</t>
1337 </list>
1338 </t>
1339 </list>
1340 </t>
1341 <t>Example:</t>
1342 <t>
1343 <list>
1344 <t>C: "SET AUDIO_OUTPUT_CHANNEL PARAMETER 0 0 JACK_BINDINGS='PCM:0'"</t>
1345 <t>S: "OK"</t>
1346 </list>
1347 </t>
1348 <t>
1349 <list>
1350 <t>C: "SET AUDIO_OUTPUT_CHANNEL PARAMETER 0 0 NAME='monitor left'"</t>
1351 <t>S: "OK"</t>
1352 </list>
1353 </t>
1354 </section>
1355 </section>
1356
1357 <section title="Configuring MIDI input drivers">
1358 <t>Instances of drivers in LinuxSampler are called devices. You can use
1359 multiple MIDI devices simultaneously, e.g. to use MIDI over ethernet as
1360 MIDI input on one sampler channel and ALSA as MIDI input on another sampler
1361 channel. For particular MIDI input systems it's also possible to create
1362 several devices of the same MIDI input type. This chapter describes all
1363 commands to configure LinuxSampler's MIDI input devices and their parameters.</t>
1364
1365 <t>Instead of defining commands and parameters for each driver individually,
1366 all possible parameters, their meanings and possible values have to be obtained
1367 at runtime. This makes the protocol a bit abstract, but has the advantage, that
1368 front-ends can be written independently of what drivers are currently implemented
1369 and what parameters these drivers are actually offering. This means front-ends can
1370 even handle drivers which are implemented somewhere in future without modifying
1371 the front-end at all.</t>
1372
1373 <t>Commands for configuring MIDI input devices are pretty much the same as the
1374 commands for configuring audio output drivers, already described in the last
1375 chapter.</t>
1376
1377 <t>Note: examples in this chapter showing particular parameters of drivers are
1378 not meant as specification of the drivers' parameters. Driver implementations in
1379 LinuxSampler might have complete different parameter names and meanings than shown
1380 in these examples or might change in future, so these examples are only meant for
1381 showing how to retrieve what parameters drivers are offering, how to retrieve their
1382 possible values, etc.</t>
1383
1384 <section title="Getting amount of available MIDI input drivers" anchor="GET AVAILABLE_MIDI_INPUT_DRIVERS">
1385 <t>Use the following command to get the number of
1386 MIDI input drivers currently available for the
1387 LinuxSampler instance:</t>
1388 <t>
1389 <list>
1390 <t>GET AVAILABLE_MIDI_INPUT_DRIVERS</t>
1391 </list>
1392 </t>
1393 <t>Possible Answers:</t>
1394 <t>
1395 <list>
1396 <t>LinuxSampler will answer by sending the
1397 number of available MIDI input drivers.</t>
1398 </list>
1399 </t>
1400 <t>Example:</t>
1401 <t>
1402 <list>
1403 <t>C: "GET AVAILABLE_MIDI_INPUT_DRIVERS"</t>
1404 <t>S: "2"</t>
1405 </list>
1406 </t>
1407 </section>
1408
1409 <section title="Getting all available MIDI input drivers" anchor="LIST AVAILABLE_MIDI_INPUT_DRIVERS">
1410 <t>Use the following command to list all MIDI input drivers currently available
1411 for the LinuxSampler instance:</t>
1412 <t>
1413 <list>
1414 <t>LIST AVAILABLE_MIDI_INPUT_DRIVERS</t>
1415 </list>
1416 </t>
1417 <t>Possible Answers:</t>
1418 <t>
1419 <list>
1420 <t>LinuxSampler will answer by sending comma separated character
1421 strings, each symbolizing a MIDI input driver.</t>
1422 </list>
1423 </t>
1424 <t>Example:</t>
1425 <t>
1426 <list>
1427 <t>C: "LIST AVAILABLE_MIDI_INPUT_DRIVERS"</t>
1428 <t>S: "ALSA,JACK"</t>
1429 </list>
1430 </t>
1431 </section>
1432
1433 <section title="Getting information about a specific MIDI input driver" anchor="GET MIDI_INPUT_DRIVER INFO">
1434 <t>Use the following command to get detailed information about a specific MIDI input driver:</t>
1435 <t>
1436 <list>
1437 <t>GET MIDI_INPUT_DRIVER INFO &lt;midi-input-driver&gt;</t>
1438 </list>
1439 </t>
1440 <t>Where &lt;midi-input-driver&gt; is the name of the MIDI input driver as returned
1441 by the <xref target="LIST AVAILABLE_MIDI_INPUT_DRIVERS">
1442 "LIST AVAILABLE_MIDI_INPUT_DRIVERS"</xref> command.</t>
1443 <t>Possible Answers:</t>
1444 <t>
1445 <list>
1446 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
1447 Each answer line begins with the information category name
1448 followed by a colon and then a space character &lt;SP&gt; and finally
1449 the info character string to that info category. At the moment
1450 the following information categories are defined:</t>
1451
1452 <t>
1453 <list>
1454 <t>DESCRIPTION -
1455 <list>
1456 <t>arbitrary description text about the MIDI input driver</t>
1457 </list>
1458 </t>
1459 <t>VERSION -
1460 <list>
1461 <t>arbitrary character string regarding the driver's version</t>
1462 </list>
1463 </t>
1464 <t>PARAMETERS -
1465 <list>
1466 <t>comma separated list of all parameters available for the given MIDI input driver</t>
1467 </list>
1468 </t>
1469 </list>
1470 </t>
1471
1472 <t>The mentioned fields above don't have to be in particular order.</t>
1473 </list>
1474 </t>
1475
1476 <t>Example:</t>
1477
1478 <t>
1479 <list>
1480 <t>C: "GET MIDI_INPUT_DRIVER INFO ALSA"</t>
1481 <t>S: "DESCRIPTION: Advanced Linux Sound Architecture"</t>
1482 <t>&nbsp;&nbsp;&nbsp;"VERSION: 1.0"</t>
1483 <t>&nbsp;&nbsp;&nbsp;"PARAMETERS: DRIVER,ACTIVE"</t>
1484 <t>&nbsp;&nbsp;&nbsp;"."</t>
1485 </list>
1486 </t>
1487 </section>
1488
1489 <section title="Getting information about specific MIDI input driver parameter" anchor="GET MIDI_INPUT_DRIVER_PARAMETER INFO">
1490 <t>Use the following command to get detailed information about a specific parameter of a specific MIDI input driver:</t>
1491 <t>
1492 <list>
1493 <t>GET MIDI_INPUT_DRIVER_PARAMETER INFO &lt;midit&gt; &lt;param&gt; [&lt;deplist&gt;]</t>
1494 </list>
1495 </t>
1496
1497 <t>Where &lt;midit&gt; is the name of the MIDI input driver as returned
1498 by the <xref target="LIST AVAILABLE_MIDI_INPUT_DRIVERS">
1499 "LIST AVAILABLE_MIDI_INPUT_DRIVERS"</xref> command, &lt;param&gt; a specific
1500 parameter name for which information should be obtained (as returned by the
1501 <xref target="GET MIDI_INPUT_DRIVER INFO">
1502 "GET MIDI_INPUT_DRIVER INFO"</xref> command) and &lt;deplist&gt; is an optional list
1503 of parameters on which the sought parameter &lt;param&gt; depends on,
1504 &lt;deplist&gt; is a key-value pair list in form of "key1=val1 key2=val2 ...",
1505 where character string values are encapsulated into apostrophes ('). Arguments
1506 given with &lt;deplist&gt; which are not dependency parameters of &lt;param&gt;
1507 will be ignored, means the front-end application can simply put all parameters
1508 in &lt;deplist&gt; with the values selected by the user.</t>
1509
1510 <t>Possible Answers:</t>
1511
1512 <t>LinuxSampler will answer by sending a &lt;CRLF> separated list.
1513 Each answer line begins with the information category name
1514 followed by a colon and then a space character &lt;SP> and finally
1515 the info character string to that info category. There is
1516 information which is always returned, independent of the
1517 given driver parameter and there is optional information
1518 which is only shown dependent to given driver parameter. At
1519 the moment the following information categories are defined:</t>
1520
1521 <t>
1522 <list>
1523 <t>TYPE -
1524 <list>
1525 <t>either "BOOL" for boolean value(s) or "INT" for integer
1526 value(s) or "FLOAT" for dotted number(s) or "STRING" for
1527 character string(s)
1528 (always returned, no matter which driver parameter)</t>
1529 </list>
1530 </t>
1531
1532 <t>DESCRIPTION -
1533 <list>
1534 <t>arbitrary text describing the purpose of the parameter
1535 (always returned, no matter which driver parameter)</t>
1536 </list>
1537 </t>
1538
1539 <t>MANDATORY -
1540 <list>
1541 <t>either true or false, defines if this parameter must be
1542 given when the device is to be created with the
1543 <xref target="CREATE MIDI_INPUT_DEVICE">
1544 'CREATE MIDI_INPUT_DEVICE'</xref> command
1545 (always returned, no matter which driver parameter)</t>
1546 </list>
1547 </t>
1548
1549 <t>FIX -
1550 <list>
1551 <t>either true or false, if false then this parameter can
1552 be changed at any time, once the device is created by
1553 the <xref target="CREATE MIDI_INPUT_DEVICE">
1554 'CREATE MIDI_INPUT_DEVICE'</xref> command
1555 (always returned, no matter which driver parameter)</t>
1556 </list>
1557 </t>
1558
1559 <t>MULTIPLICITY -
1560 <list>
1561 <t>either true or false, defines if this parameter allows
1562 only one value or a list of values, where true means
1563 multiple values and false only a single value allowed
1564 (always returned, no matter which driver parameter)</t>
1565 </list>
1566 </t>
1567
1568 <t>DEPENDS -
1569 <list>
1570 <t>comma separated list of parameters this parameter depends
1571 on, means the values for fields 'DEFAULT', 'RANGE_MIN',
1572 'RANGE_MAX' and 'POSSIBILITIES' might depend on these
1573 listed parameters, for example assuming that an audio
1574 driver (like the ALSA driver) offers parameters 'card'
1575 and 'samplerate' then parameter 'samplerate' would
1576 depend on 'card' because the possible values for
1577 'samplerate' depends on the sound card which can be
1578 chosen by the 'card' parameter
1579 (optionally returned, dependent to driver parameter)</t>
1580 </list>
1581 </t>
1582
1583 <t>DEFAULT -
1584 <list>
1585 <t>reflects the default value for this parameter which is
1586 used when the device is created and not explicitly
1587 given with the <xref target="CREATE MIDI_INPUT_DEVICE">
1588 'CREATE MIDI_INPUT_DEVICE'</xref> command,
1589 in case of MULTIPLCITY=true, this is a comma separated
1590 list, that's why character strings are encapsulated into
1591 apostrophes (')
1592 (optionally returned, dependent to driver parameter)</t>
1593 </list>
1594 </t>
1595
1596 <t>RANGE_MIN -
1597 <list>
1598 <t>defines lower limit of the allowed value range for this
1599 parameter, can be an integer value as well as a dotted
1600 number, this parameter is often used in conjunction
1601 with RANGE_MAX, but may also appear without
1602 (optionally returned, dependent to driver parameter)</t>
1603 </list>
1604 </t>
1605
1606 <t>RANGE_MAX -
1607 <list>
1608 <t>defines upper limit of the allowed value range for this
1609 parameter, can be an integer value as well as a dotted
1610 number, this parameter is often used in conjunction with
1611 RANGE_MIN, but may also appear without
1612 (optionally returned, dependent to driver parameter)</t>
1613 </list>
1614 </t>
1615
1616 <t>POSSIBILITIES -
1617 <list>
1618 <t>comma separated list of possible values for this
1619 parameter, character strings are encapsulated into
1620 apostrophes
1621 (optionally returned, dependent to driver parameter)</t>
1622 </list>
1623 </t>
1624 </list>
1625 </t>
1626
1627 <t>The mentioned fields above don't have to be in particular order.</t>
1628
1629 <t>Example:</t>
1630 <t>
1631 <list>
1632 <t>C: "GET MIDI_INPUT_DRIVER_PARAMETER INFO ALSA ACTIVE"</t>
1633 <t>S: "DESCRIPTION: Whether device is enabled"</t>
1634 <t>&nbsp;&nbsp;&nbsp;"TYPE: BOOL"</t>
1635 <t>&nbsp;&nbsp;&nbsp;"MANDATORY: false"</t>
1636 <t>&nbsp;&nbsp;&nbsp;"FIX: false"</t>
1637 <t>&nbsp;&nbsp;&nbsp;"MULTIPLICITY: false"</t>
1638 <t>&nbsp;&nbsp;&nbsp;"DEFAULT: true"</t>
1639 <t>&nbsp;&nbsp;&nbsp;"."</t>
1640 </list>
1641 </t>
1642 </section>
1643
1644 <section title="Creating a MIDI input device" anchor="CREATE MIDI_INPUT_DEVICE">
1645 <t>Use the following command to create a new MIDI input device for the desired MIDI input system:</t>
1646 <t>
1647 <list>
1648 <t>CREATE MIDI_INPUT_DEVICE &lt;midi-input-driver&gt; [&lt;param-list&gt;]</t>
1649 </list>
1650 </t>
1651
1652 <t>Where &lt;midi-input-driver&gt; should be replaced by the desired MIDI input system as returned
1653 by the <xref target="LIST AVAILABLE_MIDI_INPUT_DRIVERS">
1654 "LIST AVAILABLE_MIDI_INPUT_DRIVERS"</xref> command and &lt;param-list&gt; by an
1655 optional list of driver specific parameters in form of "key1=val1 key2=val2 ...", where
1656 character string values should be encapsulated into apostrophes (').
1657 Note that there might be drivers which require parameter(s) to be
1658 given with this command. Use the previously described commands in
1659 this chapter to get that information.</t>
1660
1661 <t>Possible Answers:</t>
1662 <t>
1663 <list>
1664 <t>"OK[&lt;device-id&gt;]" -
1665 <list>
1666 <t>in case the device was successfully created, where
1667 &lt;device-id&gt; is the numerical ID of the new device</t>
1668 </list>
1669 </t>
1670 <t>"WRN[&lt;device-id&gt;]:&lt;warning-code&gt;:&lt;warning-message&gt;" -
1671 <list>
1672 <t>in case the driver was loaded successfully, where
1673 &lt;device-id&gt; is the numerical ID of the new device, but
1674 there are noteworthy issue(s) related, providing an
1675 appropriate warning code and warning message</t>
1676 </list>
1677 </t>
1678 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
1679 <list>
1680 <t>in case it failed, providing an appropriate error code and error message</t>
1681 </list>
1682 </t>
1683 </list>
1684 </t>
1685 <t>Example:</t>
1686 <t>
1687 <list>
1688 <t>C: "CREATE MIDI_INPUT_DEVICE ALSA"</t>
1689 <t>S: "OK[0]"</t>
1690 </list>
1691 </t>
1692 </section>
1693
1694 <section title="Destroying a MIDI input device" anchor="DESTROY MIDI_INPUT_DEVICE">
1695 <t>Use the following command to destroy a created MIDI input device:</t>
1696 <t>
1697 <list>
1698 <t>DESTROY MIDI_INPUT_DEVICE &lt;device-id&gt;</t>
1699 </list>
1700 </t>
1701 <t>Where &lt;device-id&gt; should be replaced by the device's numerical ID as returned by the
1702 <xref target="CREATE MIDI_INPUT_DEVICE">"CREATE MIDI_INPUT_DEVICE"</xref>
1703 or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref>
1704 command.</t>
1705 <t>Possible Answers:</t>
1706 <t>
1707 <list>
1708 <t>"OK" -
1709 <list>
1710 <t>in case the device was successfully destroyed</t>
1711 </list>
1712 </t>
1713 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
1714 <list>
1715 <t>in case the device was destroyed, but there are noteworthy
1716 issue(s) related, providing an appropriate warning code and
1717 warning message</t>
1718 </list>
1719 </t>
1720 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
1721 <list>
1722 <t>in case it failed, providing an appropriate error code and error message</t>
1723 </list>
1724 </t>
1725 </list>
1726 </t>
1727 <t>Example:</t>
1728 <t>
1729 <list>
1730 <t>C: "DESTROY MIDI_INPUT_DEVICE 0"</t>
1731 <t>S: "OK"</t>
1732 </list>
1733 </t>
1734 </section>
1735
1736 <section title="Getting all created MIDI input device count" anchor="GET MIDI_INPUT_DEVICES">
1737 <t>Use the following command to count all created MIDI input devices:</t>
1738 <t>
1739 <list>
1740 <t>GET MIDI_INPUT_DEVICES</t>
1741 </list>
1742 </t>
1743 <t>Possible Answers:</t>
1744 <t>
1745 <list>
1746 <t>LinuxSampler will answer by sending the current number of all
1747 MIDI input devices.</t>
1748 </list>
1749 </t>
1750 <t>Example:</t>
1751 <t>
1752 <list>
1753 <t>C: "GET MIDI_INPUT_DEVICES"</t>
1754 <t>S: "3"</t>
1755 </list>
1756 </t>
1757 </section>
1758
1759
1760 <section title="Getting all created MIDI input device list" anchor="LIST MIDI_INPUT_DEVICES">
1761 <t>Use the following command to list all created MIDI input devices:</t>
1762 <t>
1763 <list>
1764 <t>LIST MIDI_INPUT_DEVICES</t>
1765 </list>
1766 </t>
1767 <t>Possible Answers:</t>
1768 <t>
1769 <list>
1770 <t>LinuxSampler will answer by sending a comma separated list
1771 with the numerical Ids of all created MIDI input devices.</t>
1772 </list>
1773 </t>
1774 <t>Examples:</t>
1775 <t>
1776 <list>
1777 <t>C: "LIST MIDI_INPUT_DEVICES"</t>
1778 <t>S: "0,1,2"</t>
1779 </list>
1780 </t>
1781 <t>
1782 <list>
1783 <t>C: "LIST MIDI_INPUT_DEVICES"</t>
1784 <t>S: "1,3"</t>
1785 </list>
1786 </t>
1787 </section>
1788
1789 <section title="Getting current settings of a MIDI input device" anchor="GET MIDI_INPUT_DEVICE INFO">
1790 <t>Use the following command to get current settings of a specific, created MIDI input device:</t>
1791 <t>
1792 <list>
1793 <t>GET MIDI_INPUT_DEVICE INFO &lt;device-id&gt;</t>
1794 </list>
1795 </t>
1796 <t>Where &lt;device-id&gt; is the numerical ID of the MIDI input device as returned by the
1797 <xref target="CREATE MIDI_INPUT_DEVICE">"CREATE MIDI_INPUT_DEVICE"</xref>
1798 or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref>
1799 command.</t>
1800 <t>Possible Answers:</t>
1801 <t>
1802 <list>
1803 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
1804 Each answer line begins with the information category name
1805 followed by a colon and then a space character &lt;SP&gt; and finally
1806 the info character string to that info category. As some
1807 parameters might allow multiple values, character strings are
1808 encapsulated into apostrophes ('). At the moment the following
1809 information categories are defined (independent of driver):</t>
1810
1811 <t>
1812 <list>
1813 <t>DRIVER -
1814 <list>
1815 <t>identifier of the used MIDI input driver, as e.g.
1816 returned by the <xref target="LIST AVAILABLE_MIDI_INPUT_DRIVERS">
1817 "LIST AVAILABLE_MIDI_INPUT_DRIVERS"</xref>
1818 command</t>
1819 </list>
1820 </t>
1821 </list>
1822 <list>
1823 <t>ACTIVE -
1824 <list>
1825 <t>either true or false, if false then the MIDI device is
1826 inactive and doesn't listen to any incoming MIDI events
1827 and thus doesn't forward them to connected sampler
1828 channels</t>
1829 </list>
1830 </t>
1831 </list>
1832 </t>
1833 </list>
1834 </t>
1835
1836 <t>The mentioned fields above don't have to be in particular
1837 order. The fields above are only those fields which are
1838 returned by all MIDI input devices. Every MIDI input driver
1839 might have its own, additional driver specific parameters (see
1840 <xref target="GET MIDI_INPUT_DRIVER INFO">
1841 "GET MIDI_INPUT_DRIVER INFO"</xref> command) which are also returned
1842 by this command.</t>
1843
1844 <t>Example:</t>
1845 <t>
1846 <list>
1847 <t>C: "GET MIDI_INPUT_DEVICE INFO 0"</t>
1848 <t>S: "DRIVER: ALSA"</t>
1849 <t>&nbsp;&nbsp;&nbsp;"ACTIVE: true"</t>
1850 <t>&nbsp;&nbsp;&nbsp;"."</t>
1851 </list>
1852 </t>
1853 </section>
1854
1855 <section title="Changing settings of MIDI input devices" anchor="SET MIDI_INPUT_DEVICE_PARAMETER">
1856 <t>Use the following command to alter a specific setting of a created MIDI input device:</t>
1857 <t>
1858 <list>
1859 <t>SET MIDI_INPUT_DEVICE_PARAMETER &lt;device-id&gt; &lt;key&gt;=&lt;value&gt;</t>
1860 </list>
1861 </t>
1862
1863 <t>Where &lt;device-id&gt; should be replaced by the numerical ID of the
1864 MIDI input device as returned by the
1865 <xref target="CREATE MIDI_INPUT_DEVICE">"CREATE MIDI_INPUT_DEVICE"</xref>
1866 or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref>
1867 command, &lt;key&gt; by the name of the parameter to change and
1868 &lt;value&gt; by the new value for this parameter.</t>
1869
1870 <t>Possible Answers:</t>
1871 <t>
1872 <list>
1873 <t>"OK" -
1874 <list>
1875 <t>in case setting was successfully changed</t>
1876 </list>
1877 </t>
1878 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
1879 <list>
1880 <t>in case setting was changed successfully, but there are
1881 noteworthy issue(s) related, providing an appropriate
1882 warning code and warning message</t>
1883 </list>
1884 </t>
1885 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
1886 <list>
1887 <t>in case it failed, providing an appropriate error code and error message</t>
1888 </list>
1889 </t>
1890 </list>
1891 </t>
1892 <t>Example:</t>
1893 <t>
1894 <list>
1895 <t>C: "SET MIDI_INPUT_DEVICE_PARAMETER 0 ACTIVE=false"</t>
1896 <t>S: "OK"</t>
1897 </list>
1898 </t>
1899 </section>
1900
1901 <section title="Getting information about a MIDI port" anchor="GET MIDI_INPUT_PORT INFO">
1902 <t>Use the following command to get information about a MIDI port:</t>
1903 <t>
1904 <list>
1905 <t>GET MIDI_INPUT_PORT INFO &lt;device-id&gt; &lt;midi-port&gt;</t>
1906 </list>
1907 </t>
1908 <t>Where &lt;device-id&gt; is the numerical ID of the MIDI input device as returned by the
1909 <xref target="CREATE MIDI_INPUT_DEVICE">"CREATE MIDI_INPUT_DEVICE"</xref>
1910 or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref>
1911 command and &lt;midi-port&gt; the MIDI input port number.</t>
1912 <t>Possible Answers:</t>
1913 <t>
1914 <list>
1915 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
1916 Each answer line begins with the information category name
1917 followed by a colon and then a space character &lt;SP&gt; and finally
1918 the info character string to that info category. At the moment
1919 the following information categories are defined:</t>
1920
1921 <t>NAME -
1922 <list>
1923 <t>arbitrary character string naming the port</t>
1924 </list>
1925 </t>
1926 </list>
1927 </t>
1928
1929 <t>The field above is only the one which is returned by all MIDI
1930 ports regardless of the MIDI driver and port. Every MIDI port
1931 might have its own, additional driver and port specific
1932 parameters.</t>
1933
1934 <t>Example:</t>
1935 <t>
1936 <list>
1937 <t>C: "GET MIDI_INPUT_PORT INFO 0 0"</t>
1938 <t>S: "NAME: 'Masterkeyboard'"</t>
1939 <t>&nbsp;&nbsp;&nbsp;"ALSA_SEQ_BINDINGS: '64:0'"</t>
1940 <t>&nbsp;&nbsp;&nbsp;"."</t>
1941 </list>
1942 </t>
1943 </section>
1944
1945 <section title="Getting information about specific MIDI port parameter" anchor="GET MIDI_INPUT_PORT_PARAMETER INFO">
1946 <t>Use the following command to get detailed information about specific MIDI port parameter:</t>
1947 <t>
1948 <list>
1949 <t>GET MIDI_INPUT_PORT_PARAMETER INFO &lt;dev-id&gt; &lt;port&gt; &lt;param&gt;</t>
1950 </list>
1951 </t>
1952
1953 <t>Where &lt;dev-id&gt; is the numerical ID of the MIDI input device as returned by the
1954 <xref target="CREATE MIDI_INPUT_DEVICE">"CREATE MIDI_INPUT_DEVICE"</xref>
1955 or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref>
1956 command, &lt;port&gt; the MIDI port number and
1957 &lt;param&gt; a specific port parameter name for which information should be
1958 obtained (as returned by the <xref target="GET MIDI_INPUT_PORT INFO">
1959 "GET MIDI_INPUT_PORT INFO"</xref> command).</t>
1960
1961 <t>Possible Answers:</t>
1962 <t>
1963 <list>
1964 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
1965 Each answer line begins with the information category name
1966 followed by a colon and then a space character &lt;SP&gt; and finally
1967 the info character string to that info category. There is
1968 information which is always returned, independently of the
1969 given channel parameter and there is optional information
1970 which are only shown dependently to the given MIDI port. At the
1971 moment the following information categories are defined:</t>
1972
1973 <t>TYPE -
1974 <list>
1975 <t>either "BOOL" for boolean value(s) or "INT" for integer
1976 value(s) or "FLOAT" for dotted number(s) or "STRING" for
1977 character string(s)
1978 (always returned)</t>
1979 </list>
1980 </t>
1981 <t>DESCRIPTION -
1982 <list>
1983 <t>arbitrary text describing the purpose of the parameter
1984 (always returned)</t>
1985 </list>
1986 </t>
1987 <t>FIX -
1988 <list>
1989 <t>either true or false, if true then this parameter is
1990 read only, thus cannot be altered
1991 (always returned)</t>
1992 </list>
1993 </t>
1994 <t>MULTIPLICITY -
1995 <list>
1996 <t>either true or false, defines if this parameter allows
1997 only one value or a list of values, where true means
1998 multiple values and false only a single value allowed
1999 (always returned)</t>
2000 </list>
2001 </t>
2002 <t>RANGE_MIN -
2003 <list>
2004 <t>defines lower limit of the allowed value range for this
2005 parameter, can be an integer value as well as a dotted
2006 number, this parameter is usually used in conjunction
2007 with 'RANGE_MAX' but may also appear without
2008 (optionally returned, dependent to driver and port
2009 parameter)</t>
2010 </list>
2011 </t>
2012 <t>RANGE_MAX -
2013 <list>
2014 <t>defines upper limit of the allowed value range for this
2015 parameter, can be an integer value as well as a dotted
2016 number, this parameter is usually used in conjunction
2017 with 'RANGE_MIN' but may also appear without
2018 (optionally returned, dependent to driver and port
2019 parameter)</t>
2020 </list>
2021 </t>
2022 <t>POSSIBILITIES -
2023 <list>
2024 <t>comma separated list of possible values for this
2025 parameter, character strings are encapsulated into
2026 apostrophes
2027 (optionally returned, dependent to device and port
2028 parameter)</t>
2029 </list>
2030 </t>
2031 </list>
2032 </t>
2033
2034 <t>The mentioned fields above don't have to be in particular order.</t>
2035
2036 <t>Example:</t>
2037 <t>
2038 <list>
2039 <t>C: "GET MIDI_INPUT_PORT_PARAMETER INFO 0 0 ALSA_SEQ_BINDINGS"</t>
2040 <t>S: "DESCRIPTION: bindings to other ALSA sequencer clients"</t>
2041 <t>&nbsp;&nbsp;&nbsp;"TYPE: STRING"</t>
2042 <t>&nbsp;&nbsp;&nbsp;"FIX: false"</t>
2043 <t>&nbsp;&nbsp;&nbsp;"MULTIPLICITY: true"</t>
2044 <t>&nbsp;&nbsp;&nbsp;"POSSIBILITIES: '64:0','68:0','68:1'"</t>
2045 <t>&nbsp;&nbsp;&nbsp;"."</t>
2046 </list>
2047 </t>
2048 </section>
2049
2050 <section title="Changing settings of MIDI input ports" anchor="SET MIDI_INPUT_PORT_PARAMETER">
2051 <t>Use the following command to alter a specific setting of a MIDI input port:</t>
2052 <t>
2053 <list>
2054 <t>SET MIDI_INPUT_PORT_PARAMETER &lt;device-id&gt; &lt;port&gt; &lt;key&gt;=&lt;value&gt;</t>
2055 </list>
2056 </t>
2057
2058 <t>Where &lt;device-id&gt; should be replaced by the numerical ID of the
2059 MIDI device as returned by the
2060 <xref target="CREATE MIDI_INPUT_DEVICE">"CREATE MIDI_INPUT_DEVICE"</xref>
2061 or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref>
2062 command, &lt;port&gt; by the MIDI port number, &lt;key&gt; by the name of
2063 the parameter to change and &lt;value&gt; by the new value for this
2064 parameter (encapsulated into apostrophes) or NONE (not encapsulated into apostrophes)
2065 for specifying no value for parameters allowing a list of values.</t>
2066
2067 <t>Possible Answers:</t>
2068 <t>
2069 <list>
2070 <t>"OK" -
2071 <list>
2072 <t>in case setting was successfully changed</t>
2073 </list>
2074 </t>
2075 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2076 <list>
2077 <t>in case setting was changed successfully, but there are
2078 noteworthy issue(s) related, providing an appropriate
2079 warning code and warning message</t>
2080 </list>
2081 </t>
2082 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2083 <list>
2084 <t>in case it failed, providing an appropriate error code and error message</t>
2085 </list>
2086 </t>
2087 </list>
2088 </t>
2089 <t>Example:</t>
2090 <t>
2091 <list>
2092 <t>C: "SET MIDI_INPUT_PORT_PARAMETER 0 0 ALSA_SEQ_BINDINGS='20:0'"</t>
2093 <t>S: "OK"</t>
2094 </list>
2095 </t>
2096 <t>
2097 <list>
2098 <t>C: "SET MIDI_INPUT_PORT_PARAMETER 0 0 ALSA_SEQ_BINDINGS=NONE"</t>
2099 <t>S: "OK"</t>
2100 </list>
2101 </t>
2102 </section>
2103 </section>
2104
2105 <section title="Configuring sampler channels">
2106 <t>The following commands describe how to add and remove sampler channels, associate a
2107 sampler channel with a sampler engine, load instruments and connect sampler channels to
2108 MIDI and audio devices.</t>
2109
2110 <section title="Loading an instrument" anchor="LOAD INSTRUMENT">
2111 <t>An instrument file can be loaded and assigned to a sampler channel by one of the following commands:</t>
2112 <t>
2113 <list>
2114 <t>LOAD INSTRUMENT [NON_MODAL] '&lt;filename&gt;' &lt;instr-index&gt; &lt;sampler-channel&gt;</t>
2115 </list>
2116 </t>
2117
2118 <t>Where &lt;filename&gt; is the name of the instrument file on the
2119 LinuxSampler instance's host system, &lt;instr-index&gt; the index of the
2120 instrument in the instrument file and &lt;sampler-channel> is the
2121 number of the sampler channel the instrument should be assigned to.
2122 Each sampler channel can only have one instrument.</t>
2123
2124 <t>Notice: since LSCP 1.2 the &lt;filename&gt; argument supports
2125 escape characters for special characters (see chapter
2126 "<xref target="character_set">Character Set and Escape Sequences</xref>"
2127 for details) and accordingly backslash characters in the filename
2128 MUST now be escaped as well!</t>
2129
2130 <t>The difference between regular and NON_MODAL versions of the command
2131 is that the regular command returns OK only after the instrument has been
2132 fully loaded and the channel is ready to be used while NON_MODAL version
2133 returns immediately and a background process is launched to load the instrument
2134 on the channel. The <xref target="GET CHANNEL INFO">GET CHANNEL INFO</xref>
2135 command can be used to obtain loading
2136 progress from INSTRUMENT_STATUS field. LOAD command will perform sanity checks
2137 such as making sure that the file could be read and it is of a proper format
2138 and SHOULD return ERR and SHOULD not launch the background process should any
2139 errors be detected at that point.</t>
2140
2141 <t>Possible Answers:</t>
2142 <t>
2143 <list>
2144 <t>"OK" -
2145 <list>
2146 <t>in case the instrument was successfully loaded</t>
2147 </list>
2148 </t>
2149 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2150 <list>
2151 <t>in case the instrument was loaded successfully, but there
2152 are noteworthy issue(s) related (e.g. Engine doesn't support
2153 one or more patch parameters provided by the loaded
2154 instrument file), providing an appropriate warning code and
2155 warning message</t>
2156 </list>
2157 </t>
2158 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2159 <list>
2160 <t>in case it failed, providing an appropriate error code and error message</t>
2161 </list>
2162 </t>
2163 </list>
2164 </t>
2165 <t>Example:</t>
2166 <t>
2167 <list>
2168 <t></t>
2169 </list>
2170 </t>
2171 </section>
2172
2173 <section title="Loading a sampler engine" anchor="LOAD ENGINE">
2174 <t>A sampler engine type can be associated to a specific sampler
2175 channel by the following command:</t>
2176 <t>
2177 <list>
2178 <t>LOAD ENGINE &lt;engine-name&gt; &lt;sampler-channel&gt;</t>
2179 </list>
2180 </t>
2181
2182 <t>Where &lt;engine-name&gt; is an engine name as obtained by the
2183 <xref target="LIST AVAILABLE_ENGINES">
2184 "LIST AVAILABLE_ENGINES"</xref> command and &lt;sampler-channel&gt;
2185 the sampler channel as returned by the
2186 <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> or
2187 <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command where
2188 the engine type should be assigned to. This command should be issued
2189 after adding a new sampler channel and before any other control
2190 commands on the new sampler channel. It can also be used to change
2191 the engine type of a sampler channel. This command has (currently) no
2192 way to define or force if a new engine instance should be created and
2193 assigned to the given sampler channel or if an already existing
2194 instance of that engine type, shared with other sampler channels,
2195 should be used.</t>
2196
2197 <t>Possible Answers:</t>
2198 <t>
2199 <list>
2200 <t>"OK" -
2201 <list>
2202 <t>in case the engine was successfully deployed</t>
2203 </list>
2204 </t>
2205 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2206 <list>
2207 <t>in case the engine was deployed successfully, but there
2208 are noteworthy issue(s) related, providing an appropriate
2209 warning code and warning message</t>
2210 </list>
2211 </t>
2212 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2213 <list>
2214 <t>in case it failed, providing an appropriate error code and
2215 error message</t>
2216 </list>
2217 </t>
2218 </list>
2219 </t>
2220 <t>Example:</t>
2221 <t>
2222 <list>
2223 <t></t>
2224 </list>
2225 </t>
2226 </section>
2227
2228 <section title="Getting all created sampler channel count" anchor="GET CHANNELS">
2229 <t>The number of sampler channels can change on runtime. To get the
2230 current amount of sampler channels, the front-end can send the
2231 following command:</t>
2232 <t>
2233 <list>
2234 <t>GET CHANNELS</t>
2235 </list>
2236 </t>
2237 <t>Possible Answers:</t>
2238 <t>
2239 <list>
2240 <t>LinuxSampler will answer by returning the current number of sampler channels.</t>
2241 </list>
2242 </t>
2243 <t>Example:</t>
2244 <t>
2245 <list>
2246 <t>C: "GET CHANNELS"</t>
2247 <t>S: "12"</t>
2248 </list>
2249 </t>
2250 </section>
2251
2252 <section title="Getting all created sampler channel list" anchor="LIST CHANNELS">
2253 <t>The number of sampler channels can change on runtime. To get the
2254 current list of sampler channels, the front-end can send the
2255 following command:</t>
2256 <t>
2257 <list>
2258 <t>LIST CHANNELS</t>
2259 </list>
2260 </t>
2261 <t>Possible Answers:</t>
2262 <t>
2263 <list>
2264 <t>LinuxSampler will answer by returning a comma separated list
2265 with all sampler channels numerical IDs.</t>
2266 </list>
2267 </t>
2268 <t>Example:</t>
2269 <t>
2270 <list>
2271 <t>C: "LIST CHANNELS"</t>
2272 <t>S: "0,1,2,3,4,5,6,9,10,11,15,20"</t>
2273 </list>
2274 </t>
2275 </section>
2276
2277 <section title="Adding a new sampler channel" anchor="ADD CHANNEL">
2278 <t>A new sampler channel can be added to the end of the sampler
2279 channel list by sending the following command:</t>
2280 <t>
2281 <list>
2282 <t>ADD CHANNEL</t>
2283 </list>
2284 </t>
2285 <t>This will increment the sampler channel count by one and the new
2286 sampler channel will be appended to the end of the sampler channel
2287 list. The front-end should send the respective, related commands
2288 right after to e.g. load an engine, load an instrument and setting
2289 input, output method and eventually other commands to initialize
2290 the new channel. The front-end should use the sampler channel
2291 returned by the answer of this command to perform the previously
2292 recommended commands, to avoid race conditions e.g. with other
2293 front-ends that might also have sent an "ADD CHANNEL" command.</t>
2294 <t>Possible Answers:</t>
2295 <t>
2296 <list>
2297 <t>"OK[&lt;sampler-channel&gt;]" -
2298 <list>
2299 <t>in case a new sampler channel could be added, where
2300 &lt;sampler-channel&gt; reflects the channel number of the new
2301 created sampler channel which should be used to set up
2302 the sampler channel by sending subsequent initialization
2303 commands</t>
2304 </list>
2305 </t>
2306 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2307 <list>
2308 <t>in case a new channel was added successfully, but there are
2309 noteworthy issue(s) related, providing an appropriate
2310 warning code and warning message</t>
2311 </list>
2312 </t>
2313 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2314 <list>
2315 <t>in case it failed, providing an appropriate error code and
2316 error message</t>
2317 </list>
2318 </t>
2319 </list>
2320 </t>
2321 <t>Example:</t>
2322 <t>
2323 <list>
2324 <t></t>
2325 </list>
2326 </t>
2327 </section>
2328
2329 <section title="Removing a sampler channel" anchor="REMOVE CHANNEL">
2330 <t>A sampler channel can be removed by sending the following command:</t>
2331 <t>
2332 <list>
2333 <t>REMOVE CHANNEL &lt;sampler-channel&gt;</t>
2334 </list>
2335 </t>
2336
2337 <t>Where &lt;sampler-channel&gt; should be replaced by the
2338 number of the sampler channel as given by the
2339 <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2340 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref>
2341 command. The channel numbers of all subsequent sampler channels
2342 remain the same.</t>
2343
2344 <t>Possible Answers:</t>
2345 <t>
2346 <list>
2347 <t>"OK" -
2348 <list>
2349 <t>in case the given sampler channel could be removed</t>
2350 </list>
2351 </t>
2352 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2353 <list>
2354 <t>in case the given channel was removed, but there are
2355 noteworthy issue(s) related, providing an appropriate
2356 warning code and warning message</t>
2357 </list>
2358 </t>
2359 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2360 <list>
2361 <t>in case it failed, providing an appropriate error code and
2362 error message</t>
2363 </list>
2364 </t>
2365 </list>
2366 </t>
2367 <t>Example:</t>
2368 <t>
2369 <list>
2370 <t></t>
2371 </list>
2372 </t>
2373 </section>
2374
2375 <section title="Getting amount of available engines" anchor="GET AVAILABLE_ENGINES">
2376 <t>The front-end can ask for the number of available engines by sending the following command:</t>
2377 <t>
2378 <list>
2379 <t>GET AVAILABLE_ENGINES</t>
2380 </list>
2381 </t>
2382 <t>Possible Answers:</t>
2383 <t>
2384 <list>
2385 <t>LinuxSampler will answer by sending the number of available engines.</t>
2386 </list>
2387 </t>
2388 <t>Example:</t>
2389 <t>
2390 <list>
2391 <t>C: "GET AVAILABLE_ENGINES"</t>
2392 <t>S: "4"</t>
2393 </list>
2394 </t>
2395 </section>
2396
2397 <section title="Getting all available engines" anchor="LIST AVAILABLE_ENGINES">
2398 <t>The front-end can ask for a list of all available engines by sending the following command:</t>
2399 <t>
2400 <list>
2401 <t>LIST AVAILABLE_ENGINES</t>
2402 </list>
2403 </t>
2404 <t>Possible Answers:</t>
2405 <t>
2406 <list>
2407 <t>LinuxSampler will answer by sending a comma separated list
2408 of the engines' names encapsulated into apostrophes (').
2409 Engine names can consist of lower and upper cases,
2410 digits and underlines ("_" character).</t>
2411 </list>
2412 </t>
2413 <t>Example:</t>
2414 <t>
2415 <list>
2416 <t>C: "LIST AVAILABLE_ENGINES"</t>
2417 <t>S: "'GigEngine','AkaiEngine','DLSEngine','JoesCustomEngine'"</t>
2418 </list>
2419 </t>
2420 </section>
2421
2422 <section title="Getting information about an engine" anchor="GET ENGINE INFO">
2423 <t>The front-end can ask for information about a specific engine by
2424 sending the following command:</t>
2425 <t>
2426 <list>
2427 <t>GET ENGINE INFO &lt;engine-name&gt;</t>
2428 </list>
2429 </t>
2430 <t>Where &lt;engine-name&gt; is an engine name as obtained by the
2431 <xref target="LIST AVAILABLE_ENGINES">
2432 "LIST AVAILABLE_ENGINES"</xref> command.</t>
2433 <t>Possible Answers:</t>
2434 <t>
2435 <list>
2436 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
2437 Each answer line begins with the information category name
2438 followed by a colon and then a space character &lt;SP&gt; and finally
2439 the info character string to that info category. At the moment
2440 the following categories are defined:</t>
2441
2442 <t>
2443 <list>
2444 <t>DESCRIPTION -
2445 <list>
2446 <t>arbitrary description text about the engine
2447 (note that the character string may contain
2448 <xref target="character_set">escape sequences</xref>)</t>
2449 </list>
2450 </t>
2451 <t>VERSION -
2452 <list>
2453 <t>arbitrary character string regarding the engine's version</t>
2454 </list>
2455 </t>
2456 </list>
2457 </t>
2458 </list>
2459 </t>
2460
2461 <t>The mentioned fields above don't have to be in particular order.</t>
2462
2463 <t>Example:</t>
2464 <t>
2465 <list>
2466 <t>C: "GET ENGINE INFO JoesCustomEngine"</t>
2467 <t>S: "DESCRIPTION: this is Joe's custom sampler engine"</t>
2468 <t>&nbsp;&nbsp;&nbsp;"VERSION: testing-1.0"</t>
2469 <t>&nbsp;&nbsp;&nbsp;"."</t>
2470 </list>
2471 </t>
2472 </section>
2473
2474 <section title="Getting sampler channel information" anchor="GET CHANNEL INFO">
2475 <t>The front-end can ask for the current settings of a sampler channel
2476 by sending the following command:</t>
2477 <t>
2478 <list>
2479 <t>GET CHANNEL INFO &lt;sampler-channel&gt;</t>
2480 </list>
2481 </t>
2482 <t>Where &lt;sampler-channel&gt; is the sampler channel number the front-end is interested in
2483 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2484 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t>
2485 <t>Possible Answers:</t>
2486 <t>
2487 <list>
2488 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
2489 Each answer line begins with the settings category name
2490 followed by a colon and then a space character &lt;SP&gt; and finally
2491 the info character string to that setting category. At the
2492 moment the following categories are defined:</t>
2493
2494 <t>
2495 <list>
2496 <t>ENGINE_NAME -
2497 <list>
2498 <t>name of the engine that is associated with the sampler
2499 channel, "NONE" if there's no engine associated yet for
2500 this sampler channel</t>
2501 </list>
2502 </t>
2503 <t>AUDIO_OUTPUT_DEVICE -
2504 <list>
2505 <t>numerical ID of the audio output device which is
2506 currently connected to this sampler channel to output
2507 the audio signal, "NONE" if there's no device
2508 connected to this sampler channel</t>
2509 </list>
2510 </t>
2511 <t>AUDIO_OUTPUT_CHANNELS -
2512 <list>
2513 <t>number of output channels the sampler channel offers
2514 (dependent to used sampler engine and loaded instrument)</t>
2515 </list>
2516 </t>
2517 <t>AUDIO_OUTPUT_ROUTING -
2518 <list>
2519 <t>comma separated list which reflects to which audio
2520 channel of the selected audio output device each
2521 sampler output channel is routed to, e.g. "0,3" would
2522 mean the engine's output channel 0 is routed to channel
2523 0 of the audio output device and the engine's output
2524 channel 1 is routed to the channel 3 of the audio
2525 output device</t>
2526 </list>
2527 </t>
2528 <t>INSTRUMENT_FILE -
2529 <list>
2530 <t>the file name of the loaded instrument, "NONE" if
2531 there's no instrument yet loaded for this sampler
2532 channel (note: since LSCP 1.2 this path may contain
2533 <xref target="character_set">escape sequences</xref>)</t>
2534 </list>
2535 </t>
2536 <t>INSTRUMENT_NR -
2537 <list>
2538 <t>the instrument index number of the loaded instrument</t>
2539 </list>
2540 </t>
2541 <t>INSTRUMENT_NAME -
2542 <list>
2543 <t>the instrument name of the loaded instrument
2544 (note: since LSCP 1.2 this character string may contain
2545 <xref target="character_set">escape sequences</xref>)</t>
2546 </list>
2547 </t>
2548 <t>INSTRUMENT_STATUS -
2549 <list>
2550 <t>integer values 0 to 100 indicating loading progress percentage for the instrument. Negative
2551 value indicates a loading exception. Value of 100 indicates that the instrument is fully
2552 loaded.</t>
2553 </list>
2554 </t>
2555 <t>MIDI_INPUT_DEVICE -
2556 <list>
2557 <t>numerical ID of the MIDI input device which is
2558 currently connected to this sampler channel to deliver
2559 MIDI input commands, "NONE" if there's no device
2560 connected to this sampler channel</t>
2561 </list>
2562 </t>
2563 <t>MIDI_INPUT_PORT -
2564 <list>
2565 <t>port number of the MIDI input device</t>
2566 </list>
2567 </t>
2568 <t>MIDI_INPUT_CHANNEL -
2569 <list>
2570 <t>the MIDI input channel number this sampler channel
2571 should listen to or "ALL" to listen on all MIDI channels</t>
2572 </list>
2573 </t>
2574 <t>VOLUME -
2575 <list>
2576 <t>optionally dotted number for the channel volume factor
2577 (where a value &lt; 1.0 means attenuation and a value >
2578 1.0 means amplification)</t>
2579 </list>
2580 </t>
2581 <t>MUTE -
2582 <list>
2583 <t>Determines whether the channel is muted, "true" if the
2584 channel is muted, "false" if the channel is not muted, and
2585 "MUTED_BY_SOLO" if the channel is muted because of the
2586 presence of a solo channel and will be unmuted when
2587 there are no solo channels left</t>
2588 </list>
2589 </t>
2590 <t>SOLO -
2591 <list>
2592 <t>Determines whether this is a solo channel, "true" if
2593 the channel is a solo channel; "false" otherwise</t>
2594 </list>
2595 </t>
2596 <t>MIDI_INSTRUMENT_MAP -
2597 <list>
2598 <t>Determines to which MIDI instrument map this sampler
2599 channel is assigned to. Read chapter
2600 <xref target="SET CHANNEL MIDI_INSTRUMENT_MAP">"SET CHANNEL MIDI_INSTRUMENT_MAP"</xref>
2601 for a list of possible values.</t>
2602 </list>
2603 </t>
2604 </list>
2605 </t>
2606 </list>
2607 </t>
2608 <t>The mentioned fields above don't have to be in particular order.</t>
2609
2610 <t>Example:</t>
2611 <t>
2612 <list>
2613 <t>C: "GET CHANNEL INFO 34"</t>
2614 <t>S: "ENGINE_NAME: GigEngine"</t>
2615 <t>&nbsp;&nbsp;&nbsp;"VOLUME: 1.0"</t>
2616 <t>&nbsp;&nbsp;&nbsp;"AUDIO_OUTPUT_DEVICE: 0"</t>
2617 <t>&nbsp;&nbsp;&nbsp;"AUDIO_OUTPUT_CHANNELS: 2"</t>
2618 <t>&nbsp;&nbsp;&nbsp;"AUDIO_OUTPUT_ROUTING: 0,1"</t>
2619 <t>&nbsp;&nbsp;&nbsp;"INSTRUMENT_FILE: /home/joe/FazioliPiano.gig"</t>
2620 <t>&nbsp;&nbsp;&nbsp;"INSTRUMENT_NR: 0"</t>
2621 <t>&nbsp;&nbsp;&nbsp;"INSTRUMENT_NAME: Fazioli Piano"</t>
2622 <t>&nbsp;&nbsp;&nbsp;"INSTRUMENT_STATUS: 100"</t>
2623 <t>&nbsp;&nbsp;&nbsp;"MIDI_INPUT_DEVICE: 0"</t>
2624 <t>&nbsp;&nbsp;&nbsp;"MIDI_INPUT_PORT: 0"</t>
2625 <t>&nbsp;&nbsp;&nbsp;"MIDI_INPUT_CHANNEL: 5"</t>
2626 <t>&nbsp;&nbsp;&nbsp;"VOLUME: 1.0"</t>
2627 <t>&nbsp;&nbsp;&nbsp;"MUTE: false"</t>
2628 <t>&nbsp;&nbsp;&nbsp;"SOLO: false"</t>
2629 <t>&nbsp;&nbsp;&nbsp;"MIDI_INSTRUMENT_MAP: NONE"</t>
2630 <t>&nbsp;&nbsp;&nbsp;"."</t>
2631 </list>
2632 </t>
2633 </section>
2634
2635 <section title="Current number of active voices" anchor="GET CHANNEL VOICE_COUNT">
2636 <t>The front-end can ask for the current number of active voices on a
2637 sampler channel by sending the following command:</t>
2638 <t>
2639 <list>
2640 <t>GET CHANNEL VOICE_COUNT &lt;sampler-channel&gt;</t>
2641 </list>
2642 </t>
2643 <t>Where &lt;sampler-channel&gt; is the sampler channel number the front-end is interested in
2644 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2645 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t>
2646
2647 <t>Possible Answers:</t>
2648 <t>
2649 <list>
2650 <t>LinuxSampler will answer by returning the number of active
2651 voices on that channel.</t>
2652 </list>
2653 </t>
2654 <t>Example:</t>
2655 <t>
2656 <list>
2657 <t></t>
2658 </list>
2659 </t>
2660 </section>
2661
2662 <section title="Current number of active disk streams" anchor="GET CHANNEL STREAM_COUNT">
2663 <t>The front-end can ask for the current number of active disk streams
2664 on a sampler channel by sending the following command:</t>
2665 <t>
2666 <list>
2667 <t>GET CHANNEL STREAM_COUNT &lt;sampler-channel&gt;</t>
2668 </list>
2669 </t>
2670 <t>Where &lt;sampler-channel&gt; is the sampler channel number the front-end is interested in
2671 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2672 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t>
2673
2674 <t>Possible Answers:</t>
2675 <t>
2676 <list>
2677 <t>LinuxSampler will answer by returning the number of active
2678 disk streams on that channel in case the engine supports disk
2679 streaming, if the engine doesn't support disk streaming it will
2680 return "NA" for not available.</t>
2681 </list>
2682 </t>
2683 <t>Example:</t>
2684 <t>
2685 <list>
2686 <t></t>
2687 </list>
2688 </t>
2689 </section>
2690
2691 <section title="Current fill state of disk stream buffers" anchor="GET CHANNEL BUFFER_FILL">
2692 <t>The front-end can ask for the current fill state of all disk streams
2693 on a sampler channel by sending the following command:</t>
2694 <t>
2695 <list>
2696 <t>GET CHANNEL BUFFER_FILL BYTES &lt;sampler-channel&gt;</t>
2697 </list>
2698 </t>
2699 <t>to get the fill state in bytes or</t>
2700 <t>
2701 <list>
2702 <t>GET CHANNEL BUFFER_FILL PERCENTAGE &lt;sampler-channel&gt;</t>
2703 </list>
2704 </t>
2705 <t>to get the fill state in percent, where &lt;sampler-channel&gt; is the
2706 sampler channel number the front-end is interested in
2707 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2708 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t>
2709
2710 <t>Possible Answers:</t>
2711 <t>
2712 <list>
2713 <t>LinuxSampler will either answer by returning a comma separated
2714 string with the fill state of all disk stream buffers on that
2715 channel or an empty line if there are no active disk streams or
2716 "NA" for *not available* in case the engine which is deployed
2717 doesn't support disk streaming. Each entry in the answer list
2718 will begin with the stream's ID in brackets followed by the
2719 numerical representation of the fill size (either in bytes or
2720 percentage). Note: due to efficiency reasons the fill states in
2721 the response are not in particular order, thus the front-end has
2722 to sort them by itself if necessary.</t>
2723 </list>
2724 </t>
2725 <t>Examples:</t>
2726 <t>
2727 <list>
2728 <t>C: "GET CHANNEL BUFFER_FILL BYTES 4"</t>
2729 <t>S: "[115]420500,[116]510300,[75]110000,[120]230700"</t>
2730 </list>
2731
2732 <list>
2733 <t>C: "GET CHANNEL BUFFER_FILL PERCENTAGE 4"</t>
2734 <t>S: "[115]90%,[116]98%,[75]40%,[120]62%"</t>
2735 </list>
2736
2737 <list>
2738 <t>C: "GET CHANNEL BUFFER_FILL PERCENTAGE 4"</t>
2739 <t>S: ""</t>
2740 </list>
2741 </t>
2742 </section>
2743
2744 <section title="Setting audio output device" anchor="SET CHANNEL AUDIO_OUTPUT_DEVICE">
2745 <t>The front-end can set the audio output device on a specific sampler
2746 channel by sending the following command:</t>
2747 <t>
2748 <list>
2749 <t>SET CHANNEL AUDIO_OUTPUT_DEVICE &lt;sampler-channel&gt; &lt;audio-device-id&gt;</t>
2750 </list>
2751 </t>
2752 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
2753 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2754 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and
2755 &lt;audio-device-id&gt; is the numerical ID of the audio output device as given by the
2756 <xref target="CREATE AUDIO_OUTPUT_DEVICE">"CREATE AUDIO_OUTPUT_DEVICE"</xref>
2757 or <xref target="LIST AUDIO_OUTPUT_DEVICES">"LIST AUDIO_OUTPUT_DEVICES"</xref>
2758 command.</t>
2759
2760 <t>Possible Answers:</t>
2761 <t>
2762 <list>
2763 <t>"OK" -
2764 <list>
2765 <t>on success</t>
2766 </list>
2767 </t>
2768 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2769 <list>
2770 <t>if audio output device was set, but there are noteworthy
2771 issue(s) related, providing an appropriate warning code and
2772 warning message</t>
2773 </list>
2774 </t>
2775 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2776 <list>
2777 <t>in case it failed, providing an appropriate error code and error message</t>
2778 </list>
2779 </t>
2780 </list>
2781 </t>
2782 <t>Examples:</t>
2783 <t>
2784 <list>
2785 <t></t>
2786 </list>
2787 </t>
2788 </section>
2789
2790 <section title="Setting audio output type" anchor="SET CHANNEL AUDIO_OUTPUT_TYPE">
2791 <t>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!</t>
2792
2793 <t>The front-end can alter the audio output type on a specific sampler
2794 channel by sending the following command:</t>
2795 <t>
2796 <list>
2797 <t>SET CHANNEL AUDIO_OUTPUT_TYPE &lt;sampler-channel&gt; &lt;audio-output-type&gt;</t>
2798 </list>
2799 </t>
2800 <t>Where &lt;audio-output-type&gt; is currently either "ALSA" or "JACK" and
2801 &lt;sampler-channel&gt; is the respective sampler channel number.</t>
2802
2803 <t>Possible Answers:</t>
2804 <t>
2805 <list>
2806 <t>"OK" -
2807 <list>
2808 <t>on success</t>
2809 </list>
2810 </t>
2811 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2812 <list>
2813 <t>if audio output type was set, but there are noteworthy
2814 issue(s) related, providing an appropriate warning code and
2815 warning message</t>
2816 </list>
2817 </t>
2818 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2819 <list>
2820 <t>in case it failed, providing an appropriate error code and error message</t>
2821 </list>
2822 </t>
2823 </list>
2824 </t>
2825 <t>Examples:</t>
2826 <t>
2827 <list>
2828 <t></t>
2829 </list>
2830 </t>
2831 </section>
2832
2833 <section title="Setting audio output channel" anchor="SET CHANNEL AUDIO_OUTPUT_CHANNEL">
2834 <t>The front-end can alter the audio output channel on a specific
2835 sampler channel by sending the following command:</t>
2836 <t>
2837 <list>
2838 <t>SET CHANNEL AUDIO_OUTPUT_CHANNEL &lt;sampler-chan&gt; &lt;audio-out&gt; &lt;audio-in&gt;</t>
2839 </list>
2840 </t>
2841 <t>Where &lt;sampler-chan&gt; is the sampler channel number
2842 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2843 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, &lt;audio-out&gt; is the
2844 numerical ID of the sampler channel's audio output channel which should be
2845 rerouted and &lt;audio-in&gt; is the numerical ID of the audio channel of the selected audio
2846 output device where &lt;audio-out&gt; should be routed to.</t>
2847
2848 <t>Possible Answers:</t>
2849 <t>
2850 <list>
2851 <t>"OK" -
2852 <list>
2853 <t>on success</t>
2854 </list>
2855 </t>
2856 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2857 <list>
2858 <t>if audio output channel was set, but there are noteworthy
2859 issue(s) related, providing an appropriate warning code and
2860 warning message</t>
2861 </list>
2862 </t>
2863 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2864 <list>
2865 <t>in case it failed, providing an appropriate error code and error message</t>
2866 </list>
2867 </t>
2868 </list>
2869 </t>
2870 <t>Examples:</t>
2871 <t>
2872 <list>
2873 <t></t>
2874 </list>
2875 </t>
2876 </section>
2877
2878 <section title="Setting MIDI input device" anchor="SET CHANNEL MIDI_INPUT_DEVICE">
2879 <t>The front-end can set the MIDI input device on a specific sampler
2880 channel by sending the following command:</t>
2881 <t>
2882 <list>
2883 <t>SET CHANNEL MIDI_INPUT_DEVICE &lt;sampler-channel&gt; &lt;midi-device-id&gt;</t>
2884 </list>
2885 </t>
2886 <t>Where &lt;sampler-channel&gt; is the sampler channel number
2887 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2888 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command
2889 and &lt;midi-device-id&gt; is the numerical ID of the MIDI input device as returned by the
2890 <xref target="CREATE MIDI_INPUT_DEVICE">"CREATE MIDI_INPUT_DEVICE"</xref>
2891 or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref> command.</t>
2892
2893 <t>Possible Answers:</t>
2894 <t>
2895 <list>
2896 <t>"OK" -
2897 <list>
2898 <t>on success</t>
2899 </list>
2900 </t>
2901 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2902 <list>
2903 <t>if MIDI input device was set, but there are noteworthy
2904 issue(s) related, providing an appropriate warning code and
2905 warning message</t>
2906 </list>
2907 </t>
2908 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2909 <list>
2910 <t>in case it failed, providing an appropriate error code and error message</t>
2911 </list>
2912 </t>
2913 </list>
2914 </t>
2915 <t>Examples:</t>
2916 <t>
2917 <list>
2918 <t></t>
2919 </list>
2920 </t>
2921 </section>
2922
2923 <section title="Setting MIDI input type" anchor="SET CHANNEL MIDI_INPUT_TYPE">
2924 <t>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!</t>
2925
2926 <t>The front-end can alter the MIDI input type on a specific sampler
2927 channel by sending the following command:</t>
2928 <t>
2929 <list>
2930 <t>SET CHANNEL MIDI_INPUT_TYPE &lt;sampler-channel&gt; &lt;midi-input-type&gt;</t>
2931 </list>
2932 </t>
2933 <t>Where &lt;midi-input-type&gt; is currently only "ALSA" and
2934 &lt;sampler-channel&gt; is the respective sampler channel number.</t>
2935
2936 <t>Possible Answers:</t>
2937 <t>
2938 <list>
2939 <t>"OK" -
2940 <list>
2941 <t>on success</t>
2942 </list>
2943 </t>
2944 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2945 <list>
2946 <t>if MIDI input type was set, but there are noteworthy
2947 issue(s) related, providing an appropriate warning code and
2948 warning message</t>
2949 </list>
2950 </t>
2951 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2952 <list>
2953 <t>in case it failed, providing an appropriate error code and error message</t>
2954 </list>
2955 </t>
2956 </list>
2957 </t>
2958 <t>Examples:</t>
2959 <t>
2960 <list>
2961 <t></t>
2962 </list>
2963 </t>
2964 </section>
2965
2966 <section title="Setting MIDI input port" anchor="SET CHANNEL MIDI_INPUT_PORT">
2967 <t>The front-end can alter the MIDI input port on a specific sampler
2968 channel by sending the following command:</t>
2969 <t>
2970 <list>
2971 <t>SET CHANNEL MIDI_INPUT_PORT &lt;sampler-channel&gt; &lt;midi-input-port&gt;</t>
2972 </list>
2973 </t>
2974 <t>Where &lt;midi-input-port&gt; is a MIDI input port number of the
2975 MIDI input device connected to the sampler channel given by
2976 &lt;sampler-channel&gt;.</t>
2977
2978 <t>Possible Answers:</t>
2979 <t>
2980 <list>
2981 <t>"OK" -
2982 <list>
2983 <t>on success</t>
2984 </list>
2985 </t>
2986 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2987 <list>
2988 <t>if MIDI input port was set, but there are noteworthy
2989 issue(s) related, providing an appropriate warning code and
2990 warning message</t>
2991 </list>
2992 </t>
2993 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2994 <list>
2995 <t>in case it failed, providing an appropriate error code and error message</t>
2996 </list>
2997 </t>
2998 </list>
2999 </t>
3000 <t>Examples:</t>
3001 <t>
3002 <list>
3003 <t></t>
3004 </list>
3005 </t>
3006 </section>
3007
3008 <section title="Setting MIDI input channel" anchor="SET CHANNEL MIDI_INPUT_CHANNEL">
3009 <t>The front-end can alter the MIDI channel a sampler channel should
3010 listen to by sending the following command:</t>
3011 <t>
3012 <list>
3013 <t>SET CHANNEL MIDI_INPUT_CHANNEL &lt;sampler-channel&gt; &lt;midi-input-chan&gt;</t>
3014 </list>
3015 </t>
3016 <t>Where &lt;midi-input-chan&gt; is the number of the new MIDI input channel where
3017 &lt;sampler-channel&gt; should listen to or "ALL" to listen on all 16 MIDI
3018 channels.</t>
3019
3020 <t>Possible Answers:</t>
3021 <t>
3022 <list>
3023 <t>"OK" -
3024 <list>
3025 <t>on success</t>
3026 </list>
3027 </t>
3028 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3029 <list>
3030 <t>if MIDI input channel was set, but there are noteworthy
3031 issue(s) related, providing an appropriate warning code and
3032 warning message</t>
3033 </list>
3034 </t>
3035 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3036 <list>
3037 <t>in case it failed, providing an appropriate error code and error message</t>
3038 </list>
3039 </t>
3040 </list>
3041 </t>
3042 <t>Examples:</t>
3043 <t>
3044 <list>
3045 <t></t>
3046 </list>
3047 </t>
3048 </section>
3049
3050 <section title="Setting channel volume" anchor="SET CHANNEL VOLUME">
3051 <t>The front-end can alter the volume of a sampler channel by sending
3052 the following command:</t>
3053 <t>
3054 <list>
3055 <t>SET CHANNEL VOLUME &lt;sampler-channel&gt; &lt;volume&gt;</t>
3056 </list>
3057 </t>
3058 <t>Where &lt;volume&gt; is an optionally dotted positive number (a value
3059 smaller than 1.0 means attenuation, whereas a value greater than
3060 1.0 means amplification) and &lt;sampler-channel&gt; defines the sampler
3061 channel where this volume factor should be set.</t>
3062
3063 <t>Possible Answers:</t>
3064 <t>
3065 <list>
3066 <t>"OK" -
3067 <list>
3068 <t>on success</t>
3069 </list>
3070 </t>
3071 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3072 <list>
3073 <t>if channel volume was set, but there are noteworthy
3074 issue(s) related, providing an appropriate warning code and
3075 warning message</t>
3076 </list>
3077 </t>
3078 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3079 <list>
3080 <t>in case it failed, providing an appropriate error code and error message</t>
3081 </list>
3082 </t>
3083 </list>
3084 </t>
3085 <t>Examples:</t>
3086 <t>
3087 <list>
3088 <t></t>
3089 </list>
3090 </t>
3091 </section>
3092
3093 <section title="Muting a sampler channel" anchor="SET CHANNEL MUTE">
3094 <t>The front-end can mute/unmute a specific sampler
3095 channel by sending the following command:</t>
3096 <t>
3097 <list>
3098 <t>SET CHANNEL MUTE &lt;sampler-channel&gt; &lt;mute&gt;</t>
3099 </list>
3100 </t>
3101 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3102 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3103 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and
3104 &lt;mute&gt; should be replaced either by "1" to mute the channel or "0"
3105 to unmute the channel.</t>
3106
3107 <t>Possible Answers:</t>
3108 <t>
3109 <list>
3110 <t>"OK" -
3111 <list>
3112 <t>on success</t>
3113 </list>
3114 </t>
3115 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3116 <list>
3117 <t>if the channel was muted/unmuted, but there are noteworthy
3118 issue(s) related, providing an appropriate warning code and
3119 warning message</t>
3120 </list>
3121 </t>
3122 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3123 <list>
3124 <t>in case it failed, providing an appropriate error code and error message</t>
3125 </list>
3126 </t>
3127 </list>
3128 </t>
3129 <t>Examples:</t>
3130 <t>
3131 <list>
3132 <t></t>
3133 </list>
3134 </t>
3135 </section>
3136
3137 <section title="Soloing a sampler channel" anchor="SET CHANNEL SOLO">
3138 <t>The front-end can solo/unsolo a specific sampler channel
3139 by sending the following command:</t>
3140 <t>
3141 <list>
3142 <t>SET CHANNEL SOLO &lt;sampler-channel&gt; &lt;solo&gt;</t>
3143 </list>
3144 </t>
3145 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3146 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3147 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and
3148 &lt;solo&gt; should be replaced either by "1" to solo the channel or "0"
3149 to unsolo the channel.</t>
3150
3151 <t>Possible Answers:</t>
3152 <t>
3153 <list>
3154 <t>"OK" -
3155 <list>
3156 <t>on success</t>
3157 </list>
3158 </t>
3159 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3160 <list>
3161 <t>if the channel was soloed/unsoloed, but there are noteworthy
3162 issue(s) related, providing an appropriate warning code and
3163 warning message</t>
3164 </list>
3165 </t>
3166 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3167 <list>
3168 <t>in case it failed, providing an appropriate error code and error message</t>
3169 </list>
3170 </t>
3171 </list>
3172 </t>
3173 <t>Examples:</t>
3174 <t>
3175 <list>
3176 <t></t>
3177 </list>
3178 </t>
3179 </section>
3180
3181 <section title="Assigning a MIDI instrument map to a sampler channel" anchor="SET CHANNEL MIDI_INSTRUMENT_MAP">
3182 <t>The front-end can assign a MIDI instrument map to a specific sampler channel
3183 by sending the following command:</t>
3184 <t>
3185 <list>
3186 <t>SET CHANNEL MIDI_INSTRUMENT_MAP &lt;sampler-channel&gt; &lt;map&gt;</t>
3187 </list>
3188 </t>
3189 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3190 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3191 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and
3192 &lt;map&gt; can have the following possibilites:</t>
3193 <t>
3194 <list>
3195 <t>"NONE" -
3196 <list>
3197 <t>This is the default setting. In this case
3198 the sampler channel is not assigned any MIDI
3199 instrument map and thus will ignore all MIDI
3200 program change messages.</t>
3201 </list>
3202 </t>
3203 <t>"DEFAULT" -
3204 <list>
3205 <t>The sampler channel will always use the
3206 default MIDI instrument map to handle MIDI
3207 program change messages.</t>
3208 </list>
3209 </t>
3210 <t>numeric ID -
3211 <list>
3212 <t>You can assign a specific MIDI instrument map
3213 by replacing &lt;map&gt; with the respective numeric
3214 ID of the MIDI instrument map as returned by the
3215 <xref target="LIST MIDI_INSTRUMENT_MAPS">"LIST MIDI_INSTRUMENT_MAPS"</xref>
3216 command. Once that map will be deleted, the sampler
3217 channel would fall back to "NONE".</t>
3218 </list>
3219 </t>
3220 </list>
3221 </t>
3222 <t>Read chapter <xref target="MIDI Instrument Mapping">"MIDI Instrument Mapping"</xref>
3223 for details regarding MIDI instrument mapping.</t>
3224
3225 <t>Possible Answers:</t>
3226 <t>
3227 <list>
3228 <t>"OK" -
3229 <list>
3230 <t>on success</t>
3231 </list>
3232 </t>
3233 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3234 <list>
3235 <t>in case it failed, providing an appropriate error code and error message</t>
3236 </list>
3237 </t>
3238 </list>
3239 </t>
3240
3241 <t>Examples:</t>
3242 <t>
3243 <list>
3244 <t></t>
3245 </list>
3246 </t>
3247 </section>
3248
3249 <section title="Adding an effect send to a sampler channel" anchor="CREATE FX_SEND">
3250 <t>The front-end can create an additional effect send on a specific sampler channel
3251 by sending the following command:</t>
3252 <t>
3253 <list>
3254 <t>CREATE FX_SEND &lt;sampler-channel&gt; &lt;midi-ctrl&gt; [&lt;name&gt;]</t>
3255 </list>
3256 </t>
3257 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3258 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3259 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, that is the
3260 sampler channel on which the effect send should be created on, &lt;midi-ctrl&gt;
3261 is a number between 0..127 defining the MIDI controller which can alter the
3262 effect send level and &lt;name&gt; is an optional argument defining a name
3263 for the effect send entity. The name does not have to be unique, but MUST be
3264 encapsulated into apostrophes and supports escape sequences as described in chapter
3265 "<xref target="character_set">Character Set and Escape Sequences</xref>".</t>
3266
3267 <t>By default, that is as initial routing, the effect send's audio channels
3268 are automatically routed to the last audio channels of the sampler channel's
3269 audio output device, that way you can i.e. first increase the amount of audio
3270 channels on the audio output device for having dedicated effect send output
3271 channels and when "CREATE FX_SEND" is called, those channels will automatically
3272 be picked. You can alter the destination channels however with
3273 <xref target="SET FX_SEND AUDIO_OUTPUT_CHANNEL">"SET FX_SEND AUDIO_OUTPUT_CHANNEL"</xref>.
3274 </t>
3275
3276 <t>Note: Create effect sends on a sampler channel only when needed, because having effect
3277 sends on a sampler channel will decrease runtime performance, because for implementing channel
3278 effect sends, separate (sampler channel local) audio buffers are needed to render and mix
3279 the voices and route the audio signal afterwards to the master outputs and effect send
3280 outputs (along with their respective effect send levels). A sampler channel without effect
3281 sends however can mix its voices directly into the audio output devices's audio buffers
3282 and is thus faster.
3283 </t>
3284
3285 <t>Possible Answers:</t>
3286 <t>
3287 <list>
3288 <t>"OK[&lt;fx-send-id&gt;]" -
3289 <list>
3290 <t>in case a new effect send could be added to the
3291 sampler channel, where &lt;fx-send-id&gt; reflects the
3292 unique ID of the newly created effect send entity</t>
3293 </list>
3294 </t>
3295 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3296 <list>
3297 <t>when a new effect send could not be added, i.e.
3298 due to invalid parameters</t>
3299 </list>
3300 </t>
3301 </list>
3302 </t>
3303
3304 <t>Examples:</t>
3305 <t>
3306 <list>
3307 <t>C: "CREATE FX_SEND 0 91 'Reverb Send'"</t>
3308 <t>S: "OK[0]"</t>
3309 </list>
3310 </t>
3311 <t>
3312 <list>
3313 <t>C: "CREATE FX_SEND 0 93"</t>
3314 <t>S: "OK[1]"</t>
3315 </list>
3316 </t>
3317 </section>
3318
3319 <section title="Removing an effect send from a sampler channel" anchor="DESTROY FX_SEND">
3320 <t>The front-end can remove an existing effect send on a specific sampler channel
3321 by sending the following command:</t>
3322 <t>
3323 <list>
3324 <t>DESTROY FX_SEND &lt;sampler-channel&gt; &lt;fx-send-id&gt;</t>
3325 </list>
3326 </t>
3327 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3328 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3329 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, that is the
3330 sampler channel from which the effect send should be removed from and
3331 &lt;fx-send-id&gt; is the respective effect send number as returned by the
3332 <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref>
3333 or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command.</t>
3334
3335 <t>Possible Answers:</t>
3336 <t>
3337 <list>
3338 <t>"OK" -
3339 <list>
3340 <t>on success</t>
3341 </list>
3342 </t>
3343 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3344 <list>
3345 <t>in case it failed, providing an appropriate error code and
3346 error message</t>
3347 </list>
3348 </t>
3349 </list>
3350 </t>
3351
3352 <t>Example:</t>
3353 <t>
3354 <list>
3355 <t>C: "DESTROY FX_SEND 0 0"</t>
3356 <t>S: "OK"</t>
3357 </list>
3358 </t>
3359 </section>
3360
3361 <section title="Getting amount of effect sends on a sampler channel" anchor="GET FX_SENDS">
3362 <t>The front-end can ask for the amount of effect sends on a specific sampler channel
3363 by sending the following command:</t>
3364 <t>
3365 <list>
3366 <t>GET FX_SENDS &lt;sampler-channel&gt;</t>
3367 </list>
3368 </t>
3369 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3370 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3371 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t>
3372
3373 <t>Possible Answers:</t>
3374 <t>
3375 <list>
3376 <t>The sampler will answer by returning the number of effect
3377 sends on the given sampler channel.</t>
3378 </list>
3379 </t>
3380
3381 <t>Example:</t>
3382 <t>
3383 <list>
3384 <t>C: "GET FX_SENDS 0"</t>
3385 <t>S: "2"</t>
3386 </list>
3387 </t>
3388 </section>
3389
3390 <section title="Listing all effect sends on a sampler channel" anchor="LIST FX_SENDS">
3391 <t>The front-end can ask for a list of effect sends on a specific sampler channel
3392 by sending the following command:</t>
3393 <t>
3394 <list>
3395 <t>LIST FX_SENDS &lt;sampler-channel&gt;</t>
3396 </list>
3397 </t>
3398 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3399 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3400 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t>
3401
3402 <t>Possible Answers:</t>
3403 <t>
3404 <list>
3405 <t>The sampler will answer by returning a comma separated list
3406 with all effect sends' numerical IDs on the given sampler
3407 channel.</t>
3408 </list>
3409 </t>
3410
3411 <t>Examples:</t>
3412 <t>
3413 <list>
3414 <t>C: "LIST FX_SENDS 0"</t>
3415 <t>S: "0,1"</t>
3416 </list>
3417 </t>
3418 <t>
3419 <list>
3420 <t>C: "LIST FX_SENDS 1"</t>
3421 <t>S: ""</t>
3422 </list>
3423 </t>
3424 </section>
3425
3426 <section title="Getting effect send information" anchor="GET FX_SEND INFO">
3427 <t>The front-end can ask for the current settings of an effect send entity
3428 by sending the following command:</t>
3429 <t>
3430 <list>
3431 <t>GET FX_SEND INFO &lt;sampler-channel&gt; &lt;fx-send-id&gt;</t>
3432 </list>
3433 </t>
3434 <t>Where &lt;sampler-channel&gt; is the sampler channel number
3435 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3436 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and
3437 &lt;fx-send-id&gt; reflects the numerical ID of the effect send entity
3438 as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref>
3439 or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command.
3440 </t>
3441
3442 <t>Possible Answers:</t>
3443 <t>
3444 <list>
3445 <t>The sampler will answer by sending a &lt;CRLF&gt; separated list.
3446 Each answer line begins with the settings category name
3447 followed by a colon and then a space character &lt;SP&gt; and finally
3448 the info character string to that setting category. At the
3449 moment the following categories are defined:</t>
3450
3451 <t>
3452 <list>
3453 <t>NAME -
3454 <list>
3455 <t>name of the effect send entity
3456 (note that this character string may contain
3457 <xref target="character_set">escape sequences</xref>)</t>
3458 </list>
3459 </t>
3460 <t>MIDI_CONTROLLER -
3461 <list>
3462 <t>a value between 0 and 127 reflecting the MIDI controller
3463 which is able to modify the effect send's send level</t>
3464 </list>
3465 </t>
3466 <t>LEVEL -
3467 <list>
3468 <t>optionally dotted number reflecting the effect send's
3469 current send level (where a value &lt; 1.0 means attenuation
3470 and a value > 1.0 means amplification)</t>
3471 </list>
3472 </t>
3473 <t>AUDIO_OUTPUT_ROUTING -
3474 <list>
3475 <t>comma separated list which reflects to which audio
3476 channel of the selected audio output device each
3477 effect send output channel is routed to, e.g. "0,3" would
3478 mean the effect send's output channel 0 is routed to channel
3479 0 of the audio output device and the effect send's output
3480 channel 1 is routed to the channel 3 of the audio
3481 output device (see
3482 <xref target="SET FX_SEND AUDIO_OUTPUT_CHANNEL">"SET FX_SEND AUDIO_OUTPUT_CHANNEL"</xref>
3483 for details)</t>
3484 </list>
3485 </t>
3486 </list>
3487 </t>
3488 </list>
3489 </t>
3490 <t>The mentioned fields above don't have to be in particular order.</t>
3491
3492 <t>Example:</t>
3493 <t>
3494 <list>
3495 <t>C: "GET FX_SEND INFO 0 0"</t>
3496 <t>S: "NAME: Reverb Send"</t>
3497 <t>&nbsp;&nbsp;&nbsp;"MIDI_CONTROLLER: 91"</t>
3498 <t>&nbsp;&nbsp;&nbsp;"LEVEL: 0.3"</t>
3499 <t>&nbsp;&nbsp;&nbsp;"AUDIO_OUTPUT_ROUTING: 2,3"</t>
3500 <t>&nbsp;&nbsp;&nbsp;"."</t>
3501 </list>
3502 </t>
3503 </section>
3504
3505 <section title="Changing effect send's name" anchor="SET FX_SEND NAME">
3506 <t>The front-end can alter the current name of an effect
3507 send entity by sending the following command:</t>
3508 <t>
3509 <list>
3510 <t>SET FX_SEND NAME &lt;sampler-chan&gt; &lt;fx-send-id&gt; &lt;name&gt;</t>
3511 </list>
3512 </t>
3513 <t>Where &lt;sampler-chan&gt; is the sampler channel number
3514 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3515 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command,
3516 &lt;fx-send-id&gt; reflects the numerical ID of the effect send entity
3517 as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref>
3518 or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command and
3519 &lt;name&gt; is the new name of the effect send entity, which
3520 does not have to be unique (name MUST be encapsulated into apostrophes
3521 and supports escape sequences as described in chapter
3522 "<xref target="character_set">Character Set and Escape Sequences</xref>").
3523 </t>
3524
3525 <t>Possible Answers:</t>
3526 <t>
3527 <list>
3528 <t>"OK" -
3529 <list>
3530 <t>on success</t>
3531 </list>
3532 </t>
3533 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3534 <list>
3535 <t>in case it failed, providing an appropriate error code and error message</t>
3536 </list>
3537 </t>
3538 </list>
3539 </t>
3540 <t>Example:</t>
3541 <t>
3542 <list>
3543 <t>C: "SET FX_SEND NAME 0 0 'Fx Send 1'"</t>
3544 <t>S: "OK"</t>
3545 </list>
3546 </t>
3547 </section>
3548
3549 <section title="Altering effect send's audio routing" anchor="SET FX_SEND AUDIO_OUTPUT_CHANNEL">
3550 <t>The front-end can alter the destination of an effect send's audio channel on a specific
3551 sampler channel by sending the following command:</t>
3552 <t>
3553 <list>
3554 <t>SET FX_SEND AUDIO_OUTPUT_CHANNEL &lt;sampler-chan&gt; &lt;fx-send-id&gt; &lt;audio-src&gt; &lt;audio-dst&gt;</t>
3555 </list>
3556 </t>
3557 <t>Where &lt;sampler-chan&gt; is the sampler channel number
3558 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3559 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command,
3560 &lt;fx-send-id&gt; reflects the numerical ID of the effect send entity
3561 as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref>
3562 or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command,
3563 &lt;audio-src&gt; is the numerical ID of the effect send's audio channel
3564 which should be rerouted and &lt;audio-dst&gt; is the numerical ID of
3565 the audio channel of the selected audio output device where &lt;audio-src&gt;
3566 should be routed to.</t>
3567
3568 <t>Note that effect sends can only route audio to the same audio output
3569 device as assigned to the effect send's sampler channel. Also note that an
3570 effect send entity does always have exactly as much audio channels as its
3571 sampler channel. So if the sampler channel is stereo, the effect send does
3572 have two audio channels as well. Also keep in mind that the amount of audio
3573 channels on a sampler channel might be dependant not only to the deployed
3574 sampler engine on the sampler channel, but also dependant to the instrument
3575 currently loaded. However you can (effectively) turn an i.e. stereo effect
3576 send into a mono one by simply altering its audio routing appropriately.</t>
3577
3578 <t>Possible Answers:</t>
3579 <t>
3580 <list>
3581 <t>"OK" -
3582 <list>
3583 <t>on success</t>
3584 </list>
3585 </t>
3586 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3587 <list>
3588 <t>if audio output channel was set, but there are noteworthy
3589 issue(s) related, providing an appropriate warning code and
3590 warning message</t>
3591 </list>
3592 </t>
3593 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3594 <list>
3595 <t>in case it failed, providing an appropriate error code and error message</t>
3596 </list>
3597 </t>
3598 </list>
3599 </t>
3600 <t>Example:</t>
3601 <t>
3602 <list>
3603 <t>C: "SET FX_SEND AUDIO_OUTPUT_CHANNEL 0 0 0 2"</t>
3604 <t>S: "OK"</t>
3605 </list>
3606 </t>
3607 </section>
3608
3609 <section title="Altering effect send's MIDI controller" anchor="SET FX_SEND MIDI_CONTROLLER">
3610 <t>The front-end can alter the MIDI controller of an effect
3611 send entity by sending the following command:</t>
3612 <t>
3613 <list>
3614 <t>SET FX_SEND MIDI_CONTROLLER &lt;sampler-chan&gt; &lt;fx-send-id&gt; &lt;midi-ctrl&gt;</t>
3615 </list>
3616 </t>
3617 <t>Where &lt;sampler-chan&gt; is the sampler channel number
3618 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3619 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command,
3620 &lt;fx-send-id&gt; reflects the numerical ID of the effect send entity
3621 as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref>
3622 or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command and
3623 &lt;midi-ctrl&gt; reflects the MIDI controller which shall be
3624 able to modify the effect send's send level.</t>
3625
3626 <t>Possible Answers:</t>
3627 <t>
3628 <list>
3629 <t>"OK" -
3630 <list>
3631 <t>on success</t>
3632 </list>
3633 </t>
3634 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3635 <list>
3636 <t>if MIDI controller was set, but there are noteworthy
3637 issue(s) related, providing an appropriate warning code and
3638 warning message</t>
3639 </list>
3640 </t>
3641 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3642 <list>
3643 <t>in case it failed, providing an appropriate error code and error message</t>
3644 </list>
3645 </t>
3646 </list>
3647 </t>
3648 <t>Example:</t>
3649 <t>
3650 <list>
3651 <t>C: "SET FX_SEND MIDI_CONTROLLER 0 0 91"</t>
3652 <t>S: "OK"</t>
3653 </list>
3654 </t>
3655 </section>
3656
3657 <section title="Altering effect send's send level" anchor="SET FX_SEND LEVEL">
3658 <t>The front-end can alter the current send level of an effect
3659 send entity by sending the following command:</t>
3660 <t>
3661 <list>
3662 <t>SET FX_SEND LEVEL &lt;sampler-chan&gt; &lt;fx-send-id&gt; &lt;volume&gt;</t>
3663 </list>
3664 </t>
3665 <t>Where &lt;sampler-chan&gt; is the sampler channel number
3666 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3667 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command,
3668 &lt;fx-send-id&gt; reflects the numerical ID of the effect send entity
3669 as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref>
3670 or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command and
3671 &lt;volume&gt; is an optionally dotted positive number (a value
3672 smaller than 1.0 means attenuation, whereas a value greater than
3673 1.0 means amplification) reflecting the new send level.</t>
3674
3675 <t>Possible Answers:</t>
3676 <t>
3677 <list>
3678 <t>"OK" -
3679 <list>
3680 <t>on success</t>
3681 </list>
3682 </t>
3683 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3684 <list>
3685 <t>if new send level was set, but there are noteworthy
3686 issue(s) related, providing an appropriate warning code and
3687 warning message</t>
3688 </list>
3689 </t>
3690 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3691 <list>
3692 <t>in case it failed, providing an appropriate error code and error message</t>
3693 </list>
3694 </t>
3695 </list>
3696 </t>
3697 <t>Example:</t>
3698 <t>
3699 <list>
3700 <t>C: "SET FX_SEND LEVEL 0 0 0.15"</t>
3701 <t>S: "OK"</t>
3702 </list>
3703 </t>
3704 </section>
3705
3706 <section title="Resetting a sampler channel" anchor="RESET CHANNEL">
3707 <t>The front-end can reset a particular sampler channel by sending the following command:</t>
3708 <t>
3709 <list>
3710 <t>RESET CHANNEL &lt;sampler-channel&gt;</t>
3711 </list>
3712 </t>
3713 <t>
3714 Where &lt;sampler-channel&gt; defines the sampler channel to be reset.
3715 This will cause the engine on that sampler channel, its voices and
3716 eventually disk streams and all control and status variables to be
3717 reset.</t>
3718
3719 <t>Possible Answers:</t>
3720 <t>
3721 <list>
3722 <t>"OK" -
3723 <list>
3724 <t>on success</t>
3725 </list>
3726 </t>
3727 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3728 <list>
3729 <t>if channel was reset, but there are noteworthy issue(s)
3730 related, providing an appropriate warning code and warning
3731 message</t>
3732 </list>
3733 </t>
3734 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3735 <list>
3736 <t>in case it failed, providing an appropriate error code and
3737 error message</t>
3738 </list>
3739 </t>
3740 </list>
3741 </t>
3742 <t>Examples:</t>
3743 <t>
3744 <list>
3745 <t></t>
3746 </list>
3747 </t>
3748 </section>
3749 </section>
3750
3751 <section title="Controlling connection">
3752 <t>The following commands are used to control the connection to LinuxSampler.</t>
3753
3754 <section title="Register front-end for receiving event messages" anchor="SUBSCRIBE">
3755 <t>The front-end can register itself to the LinuxSampler application to
3756 be informed about noteworthy events by sending this command:</t>
3757 <t>
3758 <list>
3759 <t>SUBSCRIBE &lt;event-id&gt;</t>
3760 </list>
3761 </t>
3762 <t>where &lt;event-id&gt; will be replaced by the respective event that
3763 client wants to subscribe to.</t>
3764
3765 <t>Possible Answers:</t>
3766 <t>
3767 <list>
3768 <t>"OK" -
3769 <list>
3770 <t>on success</t>
3771 </list>
3772 </t>
3773 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3774 <list>
3775 <t>if registration succeeded, but there are noteworthy
3776 issue(s) related, providing an appropriate warning code and
3777 warning message</t>
3778 </list>
3779 </t>
3780 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3781 <list>
3782 <t>in case it failed, providing an appropriate error code and
3783 error message</t>
3784 </list>
3785 </t>
3786 </list>
3787 </t>
3788 <t>Examples:</t>
3789 <t>
3790 <list>
3791 <t></t>
3792 </list>
3793 </t>
3794 </section>
3795
3796 <section title="Unregister front-end for not receiving event messages" anchor="UNSUBSCRIBE">
3797 <t>The front-end can unregister itself if it doesn't want to receive event
3798 messages anymore by sending the following command:</t>
3799 <t>
3800 <list>
3801 <t>UNSUBSCRIBE &lt;event-id&gt;</t>
3802 </list>
3803 </t>
3804 <t>Where &lt;event-id&gt; will be replaced by the respective event that
3805 client doesn't want to receive anymore.</t>
3806
3807 <t>Possible Answers:</t>
3808 <t>
3809 <list>
3810 <t>"OK" -
3811 <list>
3812 <t>on success</t>
3813 </list>
3814 </t>
3815 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3816 <list>
3817 <t>if unregistration succeeded, but there are noteworthy
3818 issue(s) related, providing an appropriate warning code and
3819 warning message</t>
3820 </list>
3821 </t>
3822 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3823 <list>
3824 <t>in case it failed, providing an appropriate error code and
3825 error message</t>
3826 </list>
3827 </t>
3828 </list>
3829 </t>
3830 <t>Examples:</t>
3831 <t>
3832 <list>
3833 <t></t>
3834 </list>
3835 </t>
3836 </section>
3837
3838 <section title="Enable or disable echo of commands" anchor="SET ECHO">
3839 <t>To enable or disable back sending of commands to the client the following command can be used:</t>
3840 <t>
3841 <list>
3842 <t>SET ECHO &lt;value&gt;</t>
3843 </list>
3844 </t>
3845 <t>Where &lt;value&gt; should be replaced either by "1" to enable echo mode
3846 or "0" to disable echo mode. When echo mode is enabled, all
3847 commands send to LinuxSampler will be immediately send back and
3848 after this echo the actual response to the command will be
3849 returned. Echo mode will only be altered for the client connection
3850 that issued the "SET ECHO" command, not globally for all client
3851 connections.</t>
3852
3853 <t>Possible Answers:</t>
3854 <t>
3855 <list>
3856 <t>"OK" -
3857 <list>
3858 <t>usually</t>
3859 </list>
3860 </t>
3861 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3862 <list>
3863 <t>on syntax error, e.g. non boolean value</t>
3864 </list>
3865 </t>
3866 </list>
3867 </t>
3868 <t>Examples:</t>
3869 <t>
3870 <list>
3871 <t></t>
3872 </list>
3873 </t>
3874 </section>
3875
3876 <section title="Close client connection" anchor="QUIT">
3877 <t>The client can close its network connection to LinuxSampler by sending the following command:</t>
3878 <t>
3879 <list>
3880 <t>QUIT</t>
3881 </list>
3882 </t>
3883 <t>This is probably more interesting for manual telnet connections to
3884 LinuxSampler than really useful for a front-end implementation.</t>
3885 </section>
3886 </section>
3887
3888 <section title="Global commands">
3889 <t>The following commands have global impact on the sampler.</t>
3890
3891 <section title="Current number of active voices" anchor="GET TOTAL_VOICE_COUNT">
3892 <t>The front-end can ask for the current number of active voices on
3893 the sampler by sending the following command:</t>
3894 <t>
3895 <list>
3896 <t>GET TOTAL_VOICE_COUNT</t>
3897 </list>
3898 </t>
3899
3900 <t>Possible Answers:</t>
3901 <t>
3902 <list>
3903 <t>LinuxSampler will answer by returning the number of all active
3904 voices on the sampler.</t>
3905 </list>
3906 </t>
3907 </section>
3908
3909 <section title="Maximum amount of active voices" anchor="GET TOTAL_VOICE_COUNT_MAX">
3910 <t>The front-end can ask for the maximum number of active voices
3911 by sending the following command:</t>
3912 <t>
3913 <list>
3914 <t>GET TOTAL_VOICE_COUNT_MAX</t>
3915 </list>
3916 </t>
3917
3918 <t>Possible Answers:</t>
3919 <t>
3920 <list>
3921 <t>LinuxSampler will answer by returning the maximum number
3922 of active voices.</t>
3923 </list>
3924 </t>
3925 </section>
3926
3927 <section title="Reset sampler" anchor="RESET">
3928 <t>The front-end can reset the whole sampler by sending the following command:</t>
3929 <t>
3930 <list>
3931 <t>RESET</t>
3932 </list>
3933 </t>
3934
3935 <t>Possible Answers:</t>
3936 <t>
3937 <list>
3938 <t>"OK" -
3939 <list>
3940 <t>always</t>
3941 </list>
3942 </t>
3943 </list>
3944 </t>
3945 <t>Examples:</t>
3946 <t>
3947 <list>
3948 <t></t>
3949 </list>
3950 </t>
3951 </section>
3952
3953 <section title="General sampler informations" anchor="GET SERVER INFO">
3954 <t>The client can ask for general informations about the LinuxSampler
3955 instance by sending the following command:</t>
3956 <t>
3957 <list>
3958 <t>GET SERVER INFO</t>
3959 </list>
3960 </t>
3961 <t>Possible Answers:</t>
3962 <t>
3963 <list>
3964 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
3965 Each answer line begins with the information category name
3966 followed by a colon and then a space character &lt;SP&gt; and finally
3967 the info character string to that information category. At the
3968 moment the following categories are defined:
3969 </t>
3970 <t>
3971 <list>
3972 <t>DESCRIPTION -
3973 <list>
3974 <t>arbitrary textual description about the sampler
3975 (note that the character string may contain
3976 <xref target="character_set">escape sequences</xref>)</t>
3977 </list>
3978 </t>
3979 <t>VERSION -
3980 <list>
3981 <t>version of the sampler</t>
3982 </list>
3983 </t>
3984 <t>PROTOCOL_VERSION -
3985 <list>
3986 <t>version of the LSCP specification the sampler
3987 complies with (see <xref target="LSCP versioning" /> for details)</t>
3988 </list>
3989 </t>
3990 <t>INSTRUMENTS_DB_SUPPORT -
3991 <list>
3992 <t>either yes or no, specifies whether the
3993 sampler is build with instruments database support.</t>
3994 </list>
3995 </t>
3996 </list>
3997 </t>
3998 </list>
3999 </t>
4000 <t>The mentioned fields above don't have to be in particular order.
4001 Other fields might be added in future.</t>
4002 </section>
4003
4004 <section title="Getting global volume attenuation" anchor="GET VOLUME">
4005 <t>The client can ask for the current global sampler-wide volume
4006 attenuation by sending the following command:</t>
4007 <t>
4008 <list>
4009 <t>GET VOLUME</t>
4010 </list>
4011 </t>
4012 <t>Possible Answers:</t>
4013 <t>
4014 <list>
4015 <t>The sampler will always answer by returning the optional
4016 dotted floating point coefficient, reflecting the current
4017 global volume attenuation.
4018 </t>
4019 </list>
4020 </t>
4021 <t>Note: it is up to the respective sampler engine whether to obey
4022 that global volume parameter or not, but in general all engines SHOULD
4023 use this parameter.</t>
4024 </section>
4025
4026 <section title="Setting global volume attenuation" anchor="SET VOLUME">
4027 <t>The client can alter the current global sampler-wide volume
4028 attenuation by sending the following command:</t>
4029 <t>
4030 <list>
4031 <t>SET VOLUME &lt;volume&gt;</t>
4032 </list>
4033 </t>
4034 <t>Where &lt;volume&gt; should be replaced by the optional dotted
4035 floating point value, reflecting the new global volume parameter.
4036 This value might usually be in the range between 0.0 and 1.0, that
4037 is for attenuating the overall volume.</t>
4038
4039 <t>Possible Answers:</t>
4040 <t>
4041 <list>
4042 <t>"OK" -
4043 <list>
4044 <t>on success</t>
4045 </list>
4046 </t>
4047 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
4048 <list>
4049 <t>if the global volume was set, but there are noteworthy
4050 issue(s) related, providing an appropriate warning code and
4051 warning message</t>
4052 </list>
4053 </t>
4054 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
4055 <list>
4056 <t>in case it failed, providing an appropriate error code and error message</t>
4057 </list>
4058 </t>
4059 </list>
4060 </t>
4061 </section>
4062 </section>
4063
4064
4065 <section title="MIDI Instrument Mapping" anchor="MIDI Instrument Mapping">
4066 <t>The MIDI protocol provides a way to switch between instruments
4067 by sending so called MIDI bank select and MIDI program change
4068 messages which are essentially just numbers. The following commands
4069 allow to actually map arbitrary MIDI bank select / program change
4070 numbers with real instruments.</t>
4071 <t>The sampler allows to manage an arbitrary amount of MIDI
4072 instrument maps which define which instrument to load on
4073 which MIDI program change message.</t>
4074 <t>By default, that is when the sampler is launched, there is no
4075 map, thus the sampler will simply ignore all program change
4076 messages. The front-end has to explicitly create at least one
4077 map, add entries to the map and tell the respective sampler
4078 channel(s) which MIDI instrument map to use, so the sampler
4079 knows how to react on a given program change message on the
4080 respective sampler channel, that is by switching to the
4081 respectively defined engine type and loading the respective
4082 instrument. See command
4083 <xref target="SET CHANNEL MIDI_INSTRUMENT_MAP">"SET CHANNEL MIDI_INSTRUMENT_MAP"</xref>
4084 for how to assign a MIDI instrument map to a sampler channel.</t>
4085 <t>Also note per MIDI specification a bank select message does not
4086 cause to switch to another instrument. Instead when receiving a
4087 bank select message the bank value will be stored and a subsequent
4088 program change message (which may occur at any time) will finally
4089 cause the sampler to switch to the respective instrument as
4090 reflected by the current MIDI instrument map.</t>
4091
4092 <section title="Create a new MIDI instrument map" anchor="ADD MIDI_INSTRUMENT_MAP">
4093 <t>The front-end can add a new MIDI instrument map by sending
4094 the following command:</t>
4095 <t>
4096 <list>
4097 <t>ADD MIDI_INSTRUMENT_MAP [&lt;name&gt;]</t>
4098 </list>
4099 </t>
4100 <t>Where &lt;name&gt; is an optional argument allowing to
4101 assign a custom name to the new map. MIDI instrument Map
4102 names do not have to be unique, but MUST be encapsulated
4103 into apostrophes and support escape sequences as described
4104 in chapter "<xref target="character_set">Character Set and Escape Sequences</xref>".
4105 </t>
4106
4107 <t>Possible Answers:</t>
4108 <t>
4109 <list>
4110 <t>"OK[&lt;map&gt;]" -
4111 <list>
4112 <t>in case a new MIDI instrument map could
4113 be added, where &lt;map&gt; reflects the
4114 unique ID of the newly created MIDI
4115 instrument map</t>
4116 </list>
4117 </t>
4118 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
4119 <list>
4120 <t>when a new map could not be created, which
4121 might never occur in practice</t>
4122 </list>
4123 </t>
4124 </list>
4125 </t>
4126
4127 <t>Examples:</t>
4128 <t>
4129 <list>
4130 <t>C: "ADD MIDI_INSTRUMENT_MAP 'Standard Map'"</t>
4131 <t>S: "OK[0]"</t>
4132 </list>
4133 </t>
4134 <t>
4135 <list>
4136 <t>C: "ADD MIDI_INSTRUMENT_MAP 'Standard Drumkit'"</t>
4137 <t>S: "OK[1]"</t>
4138 </list>
4139 </t>
4140 <t>
4141 <list>
4142 <t>C: "ADD MIDI_INSTRUMENT_MAP"</t>
4143 <t>S: "OK[5]"</t>
4144 </list>
4145 </t>
4146 </section>
4147
4148 <section title="Delete one particular or all MIDI instrument maps" anchor="REMOVE MIDI_INSTRUMENT_MAP">
4149 <t>The front-end can delete a particular MIDI instrument map
4150 by sending the following command:</t>
4151 <t>
4152 <list>
4153 <t>REMOVE MIDI_INSTRUMENT_MAP &lt;map&gt;</t>
4154 </list>
4155 </t>
4156 <t>Where &lt;map&gt; reflects the unique ID of the map to delete
4157 as returned by the <xref target="LIST MIDI_INSTRUMENT_MAPS">"LIST MIDI_INSTRUMENT_MAPS"</xref>
4158 command.</t>
4159 <t>The front-end can delete all MIDI instrument maps by
4160 sending the following command:</t>
4161 <t>
4162 <list>
4163 <t>REMOVE MIDI_INSTRUMENT_MAP ALL</t>
4164 </list>
4165 </t>
4166
4167 <t>Possible Answers:</t>
4168 <t>
4169 <list>
4170 <t>"OK" -
4171 <list>
4172 <t>in case the map(s) could be deleted</t>
4173 </list>
4174 </t>
4175 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
4176 <list>
4177 <t>when the given map does not exist</t>
4178 </list>
4179 </t>
4180 </list>
4181 </t>
4182
4183 <t>Examples:</t>
4184 <t>
4185 <list>
4186 <t>C: "REMOVE MIDI_INSTRUMENT_MAP 0"</t>
4187 <t>S: "OK"</t>
4188 </list>
4189 </t>
4190 <t>
4191 <list>
4192 <t>C: "REMOVE MIDI_INSTRUMENT_MAP ALL"</t>
4193 <t>S: "OK"</t>
4194 </list>
4195 </t>
4196 </section>
4197
4198 <section title="Get amount of existing MIDI instrument maps" anchor="GET MIDI_INSTRUMENT_MAPS">
4199 <t>The front-end can retrieve the current amount of MIDI
4200 instrument maps by sending the following command:</t>
4201 <t>
4202 <list>
4203 <t>GET MIDI_INSTRUMENT_MAPS</t>
4204 </list>
4205 </t>
4206
4207 <t>Possible Answers:</t>
4208 <t>
4209 <list>
4210 <t>The sampler will answer by returning the current
4211 number of MIDI instrument maps.</t>
4212 </list>
4213 </t>
4214
4215 <t>Example:</t>
4216 <t>
4217 <list>
4218 <t>C: "GET MIDI_INSTRUMENT_MAPS"</t>
4219 <t>S: "2"</t>
4220 </list>
4221 </t>
4222 </section>
4223
4224 <section title="Getting all created MIDI instrument maps" anchor="LIST MIDI_INSTRUMENT_MAPS">
4225 <t>The number of MIDI instrument maps can change on runtime. To get the
4226 current list of MIDI instrument maps, the front-end can send the
4227 following command:</t>
4228 <t>
4229 <list>
4230 <t>LIST MIDI_INSTRUMENT_MAPS</t>
4231 </list>
4232 </t>
4233 <t>Possible Answers:</t>
4234 <t>
4235 <list>
4236 <t>The sampler will answer by returning a comma separated list
4237 with all MIDI instrument maps' numerical IDs.</t>
4238 </list>
4239 </t>
4240 <t>Example:</t>
4241 <t>
4242 <list>
4243 <t>C: "LIST MIDI_INSTRUMENT_MAPS"</t>
4244 <t>S: "0,1,5,12"</t>
4245 </list>
4246 </t>
4247 </section>
4248
4249 <section title="Getting MIDI instrument map information" anchor="GET MIDI_INSTRUMENT_MAP INFO">
4250 <t>The front-end can ask for the current settings of a MIDI
4251 instrument map by sending the following command:</t>
4252 <t>
4253 <list>
4254 <t>GET MIDI_INSTRUMENT_MAP INFO &lt;map&gt;</t>
4255 </list>
4256 </t>
4257 <t>Where &lt;map&gt; is the numerical ID of the map the
4258 front-end is interested in as returned by the
4259 <xref target="LIST MIDI_INSTRUMENT_MAPS">"LIST MIDI_INSTRUMENT_MAPS"</xref>
4260 command.</t>
4261
4262 <t>Possible Answers:</t>
4263 <t>
4264 <list>
4265 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
4266 Each answer line begins with the settings category name
4267 followed by a colon and then a space character &lt;SP&gt; and finally
4268 the info character string to that setting category. At the
4269 moment the following categories are defined:</t>
4270
4271 <t>
4272 <list>
4273 <t>NAME -
4274 <list>
4275 <t>custom name of the given map,
4276 which does not have to be unique
4277 (note that this character string may contain
4278 <xref target="character_set">escape sequences</xref>)</t>
4279 </list>
4280 </t>
4281 <t>DEFAULT -
4282 <list>
4283 <t>either true or false,
4284 defines whether this map is the default map</t>
4285 </list>
4286 </t>
4287 </list>
4288 </t>
4289 </list>
4290 </t>
4291 <t>The mentioned fields above don't have to be in particular order.</t>
4292
4293 <t>Example:</t>
4294 <t>
4295 <list>
4296 <t>C: "GET MIDI_INSTRUMENT_MAP INFO 0"</t>
4297 <t>S: "NAME: Standard Map"</t>
4298 <t>&nbsp;&nbsp;&nbsp;"DEFAULT: true"</t>
4299 <t>&nbsp;&nbsp;&nbsp;"."</t>
4300 </list>
4301 </t>
4302 </section>
4303
4304 <section title="Renaming a MIDI instrument map" anchor="SET MIDI_INSTRUMENT_MAP NAME">
4305 <t>The front-end can alter the custom name of a MIDI
4306 instrument map by sending the following command:</t>
4307 <t>
4308 <list>
4309 <t>SET MIDI_INSTRUMENT_MAP NAME &lt;map&gt; &lt;name&gt;</t>
4310 </list>
4311 </t>
4312 <t>Where &lt;map&gt; is the numerical ID of the map and
4313 &lt;name&gt; the new custom name of the map, which does not
4314 have to be unique (name MUST be encapsulated into apostrophes
4315 and supports escape sequences as described in chapter
4316 "<xref target="character_set">Character Set and Escape Sequences</xref>").
4317 </t>
4318
4319 <t>Possible Answers:</t>
4320 <t>
4321 <list>
4322 <t>"OK" -
4323 <list>
4324 <t>on success</t>
4325 </list>
4326 </t>
4327 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
4328 <list>
4329 <t>in case the given map does not exist</t>
4330 </list>
4331 </t>
4332 </list>
4333 </t>
4334
4335 <t>Example:</t>
4336 <t>
4337 <list>
4338 <t>C: "SET MIDI_INSTRUMENT_MAP NAME 0 'Foo instruments'"</t>
4339 <t>S: "OK"</t>
4340 </list>
4341 </t>
4342 </section>
4343
4344 <section title="Create or replace a MIDI instrument map entry" anchor="MAP MIDI_INSTRUMENT">
4345 <t>The front-end can create a new or replace an existing entry
4346 in a sampler's MIDI instrument map by sending the following
4347 command:</t>
4348 <t>
4349 <list>
4350 <t>MAP MIDI_INSTRUMENT [NON_MODAL] &lt;map&gt;
4351 &lt;midi_bank&gt; &lt;midi_prog&gt; &lt;engine_name&gt;
4352 &lt;filename&gt; &lt;instrument_index&gt; &lt;volume_value&gt;
4353 [&lt;instr_load_mode&gt;] [&lt;name&gt;]</t>
4354 </list>
4355 </t>
4356 <t>Where &lt;map&gt; is the numeric ID of the map to alter,
4357 &lt;midi_bank&gt; is an integer value between
4358 0..16383 reflecting the MIDI bank select index,
4359 &lt;midi_prog&gt; an
4360 integer value between 0..127 reflecting the MIDI program change
4361 index, &lt;engine_name&gt; a sampler engine name as returned by
4362 the <xref target="LIST AVAILABLE_ENGINES">"LIST AVAILABLE_ENGINES"</xref>
4363 command (not encapsulated into apostrophes), &lt;filename&gt; the name
4364 of the instrument's file to be deployed (encapsulated into apostrophes,
4365 supporting escape sequences as described in chapter
4366 "<xref target="character_set">Character Set and Escape Sequences</xref>"),
4367 &lt;instrument_index&gt; the index (integer value) of the instrument
4368 within the given file, &lt;volume_value&gt; reflects the master
4369 volume of the instrument as optionally dotted number (where a
4370 value &lt; 1.0 means attenuation and a value > 1.0 means
4371 amplification). This parameter easily allows to adjust the
4372 volume of all intruments within a custom instrument map
4373 without having to adjust their instrument files. The
4374 OPTIONAL &lt;instr_load_mode&gt; argument defines the life
4375 time of the instrument, that is when the instrument should
4376 be loaded, when freed and has exactly the following
4377 possibilities:</t>
4378 <t>
4379 <list>
4380 <t>"ON_DEMAND" -
4381 <list>
4382 <t>The instrument will be loaded when needed,
4383 that is when demanded by at least one sampler
4384 channel. It will immediately be freed from memory
4385 when not needed by any sampler channel anymore.</t>
4386 </list>
4387 </t>
4388 <t>"ON_DEMAND_HOLD" -
4389 <list>
4390 <t>The instrument will be loaded when needed,
4391 that is when demanded by at least one sampler
4392 channel. It will be kept in memory even when
4393 not needed by any sampler channel anymore.
4394 Instruments with this mode are only freed
4395 when the sampler is reset or all mapping
4396 entries with this mode (and respective
4397 instrument) are explicitly changed to
4398 "ON_DEMAND" and no sampler channel is using
4399 the instrument anymore.</t>
4400 </list>
4401 </t>
4402 <t>"PERSISTENT" -
4403 <list>
4404 <t>The instrument will immediately be loaded
4405 into memory when this mapping
4406 command is sent and the instrument is kept all
4407 the time. Instruments with this mode are
4408 only freed when the sampler is reset or all
4409 mapping entries with this mode (and
4410 respective instrument) are explicitly
4411 changed to "ON_DEMAND" and no sampler
4412 channel is using the instrument anymore.</t>
4413 </list>
4414 </t>
4415 <t>not supplied -
4416 <list>
4417 <t>In case there is no &lt;instr_load_mode&gt;
4418 argument given, it will be up to the
4419 InstrumentManager to decide which mode to use.
4420 Usually it will use "ON_DEMAND" if an entry
4421 for the given instrument does not exist in
4422 the InstrumentManager's list yet, otherwise
4423 if an entry already exists, it will simply
4424 stick with the mode currently reflected by
4425 the already existing entry, that is it will
4426 not change the mode.</t>
4427 </list>
4428 </t>
4429 </list>
4430 </t>
4431 <t>
4432 The &lt;instr_load_mode&gt; argument thus allows to define an
4433 appropriate strategy (low memory consumption vs. fast
4434 instrument switching) for each instrument individually. Note, the
4435 following restrictions apply to this argument: "ON_DEMAND_HOLD" and
4436 "PERSISTENT" have to be supported by the respective sampler engine
4437 (which is technically the case when the engine provides an
4438 InstrumentManager for its format). If this is not the case the
4439 argument will automatically fall back to the default value
4440 "ON_DEMAND". Also the load mode of one instrument may
4441 automatically change the laod mode of other instrument(s), i.e.
4442 because the instruments are part of the same file and the
4443 engine does not allow a way to manage load modes for them
4444 individually. Due to this, in case the frontend shows the
4445 load modes of entries, the frontend should retrieve the actual
4446 mode by i.e. sending
4447 <xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref>
4448 command(s). Finally the OPTIONAL &lt;name&gt; argument allows to set a custom name
4449 (encapsulated into apostrophes, supporting escape sequences as described in chapter
4450 "<xref target="character_set">Character Set and Escape Sequences</xref>") for the
4451 mapping entry, useful for frontends for displaying an appropriate name for
4452 mapped instruments (using
4453 <xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref>).
4454 </t>
4455 <t>
4456 By default, "MAP MIDI_INSTRUMENT" commands block until the mapping is
4457 completely established in the sampler. The OPTIONAL "NON_MODAL" argument
4458 however causes the respective "MAP MIDI_INSTRUMENT" command to return
4459 immediately, that is to let the sampler establish the mapping in the
4460 background. So this argument might be especially useful for mappings with
4461 a "PERSISTENT" type, because these have to load the respective instruments
4462 immediately and might thus block for a very long time. It is recommended
4463 however to use the OPTIONAL "NON_MODAL" argument only if really necessary,
4464 because it has the following drawbacks: as "NON_MODAL" instructions return
4465 immediately, they may not necessarily return an error i.e. when the given
4466 instrument file turns out to be corrupt, beside that subsequent commands
4467 in a LSCP instruction sequence might fail, because mandatory mappings are
4468 not yet completed.
4469 </t>
4470
4471 <t>Possible Answers:</t>
4472 <t>
4473 <list>
4474 <t>"OK" -
4475 <list>
4476 <t>usually</t>
4477 </list>
4478 </t>
4479 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
4480 <list>
4481 <t>when the given map or engine does not exist or a value
4482 is out of range</t>
4483 </list>
4484 </t>
4485 </list>
4486 </t>
4487
4488 <t>Examples:</t>
4489 <t>
4490 <list>
4491 <t>C: "MAP MIDI_INSTRUMENT 0 3 0 gig '/usr/share/Steinway D.gig' 0 0.8 PERSISTENT"</t>
4492 <t>S: "OK"</t>
4493 </list>
4494 </t>
4495 <t>
4496 <list>
4497 <t>C: "MAP MIDI_INSTRUMENT 0 4 50 gig '/home/john/foostrings.gig' 7 1.0"</t>
4498 <t>S: "OK"</t>
4499 </list>
4500 </t>
4501 <t>
4502 <list>
4503 <t>C: "MAP MIDI_INSTRUMENT 0 0 0 gig '/usr/share/piano.gig' 0 1.0 'Normal Piano'"</t>
4504 <t>S: "OK"</t>
4505 <t>C: "MAP MIDI_INSTRUMENT 0 1 0 gig '/usr/share/piano.gig' 0 0.25 'Silent Piano'"</t>
4506 <t>S: "OK"</t>
4507 </list>
4508 </t>
4509 <t>
4510 <list>
4511 <t>C: "MAP MIDI_INSTRUMENT NON_MODAL 1 8 120 gig '/home/joe/foodrums.gig' 0 1.0 PERSISTENT 'Foo Drumkit'"</t>
4512 <t>S: "OK"</t>
4513 </list>
4514 </t>
4515 </section>
4516
4517 <section title="Getting ammount of MIDI instrument map entries" anchor="GET MIDI_INSTRUMENTS">
4518 <t>The front-end can query the amount of currently existing
4519 entries in a MIDI instrument map by sending the following
4520 command:</t>
4521 <t>
4522 <list>
4523 <t>GET MIDI_INSTRUMENTS &lt;map&gt;</t>
4524 </list>
4525 </t>
4526 <t>The front-end can query the amount of currently existing
4527 entries in all MIDI instrument maps by sending the following
4528 command:</t>
4529 <t>
4530 <list>
4531 <t>GET MIDI_INSTRUMENTS ALL</t>
4532 </list>
4533 </t>
4534 <t>Possible Answers:</t>
4535 <t>
4536 <list>
4537 <t>The sampler will answer by sending the current number of
4538 entries in the MIDI instrument map(s).</t>
4539 </list>
4540 </t>
4541
4542 <t>Example:</t>
4543 <t>
4544 <list>
4545 <t>C: "GET MIDI_INSTRUMENTS 0"</t>
4546 <t>S: "234"</t>
4547 </list>
4548 </t>
4549 <t>
4550 <list>
4551 <t>C: "GET MIDI_INSTRUMENTS ALL"</t>
4552 <t>S: "954"</t>
4553 </list>
4554 </t>
4555 </section>
4556
4557 <section title="Getting indeces of all entries of a MIDI instrument map" anchor="LIST MIDI_INSTRUMENTS">
4558 <t>The front-end can query a list of all currently existing
4559 entries in a certain MIDI instrument map by sending the following
4560 command:</t>
4561 <t>
4562 <list>
4563 <t>LIST MIDI_INSTRUMENTS &lt;map&gt;</t>
4564 </list>
4565 </t>
4566 <t>Where &lt;map&gt; is the numeric ID of the MIDI instrument map.</t>
4567 <t>The front-end can query a list of all currently existing
4568 entries of all MIDI instrument maps by sending the following
4569 command:</t>
4570 <t>
4571 <list>
4572 <t>LIST MIDI_INSTRUMENTS ALL</t>
4573 </list>
4574 </t>
4575
4576 <t>Possible Answers:</t>
4577 <t>
4578 <list>
4579 <t>The sampler will answer by sending a comma separated
4580 list of map ID - MIDI bank - MIDI program triples, where
4581 each triple is encapsulated into curly braces. The
4582 list is returned in one single line. Each triple
4583 just reflects the key of the respective map entry,
4584 thus subsequent
4585 <xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref>
4586 command(s) are necessary to retrieve detailed informations
4587 about each entry.</t>
4588 </list>
4589 </t>
4590
4591 <t>Example:</t>
4592 <t>
4593 <list>
4594 <t>C: "LIST MIDI_INSTRUMENTS 0"</t>
4595 <t>S: "{0,0,0},{0,0,1},{0,0,3},{0,1,4},{1,127,127}"</t>
4596 </list>
4597 </t>
4598 </section>
4599
4600 <section title="Remove an entry from the MIDI instrument map" anchor="UNMAP MIDI_INSTRUMENT">
4601 <t>The front-end can delete an entry from a MIDI instrument
4602 map by sending the following command:</t>
4603 <t>
4604 <list>
4605 <t>UNMAP MIDI_INSTRUMENT &lt;map&gt; &lt;midi_bank&gt; &lt;midi_prog&gt;</t>
4606 </list>
4607 </t>
4608 <t>
4609 Where &lt;map&gt; is the numeric ID of the MIDI instrument map,
4610 &lt;midi_bank&gt; is an integer value between 0..16383
4611 reflecting the MIDI bank value and
4612 &lt;midi_prog&gt; an integer value between
4613 0..127 reflecting the MIDI program value of the map's entrie's key
4614 index triple.
4615 </t>
4616
4617 <t>Possible Answers:</t>
4618 <t>
4619 <list>
4620 <t>"OK" -
4621 <list>
4622 <t>usually</t>
4623 </list>
4624 </t>
4625 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
4626 <list>
4627 <t>when index out of bounds</t>
4628 </list>
4629 </t>
4630 </list>
4631 </t>
4632
4633 <t>Example:</t>
4634 <t>
4635 <list>
4636 <t>C: "UNMAP MIDI_INSTRUMENT 0 2 127"</t>
4637 <t>S: "OK"</t>
4638 </list>
4639 </t>
4640 </section>
4641
4642 <section title="Get current settings of MIDI instrument map entry" anchor="GET MIDI_INSTRUMENT INFO">
4643 <t>The front-end can retrieve the current settings of a certain
4644 instrument map entry by sending the following command:</t>
4645 <t>
4646 <list>
4647 <t>GET MIDI_INSTRUMENT INFO &lt;map&gt; &lt;midi_bank&gt; &lt;midi_prog&gt;</t>
4648 </list>
4649 </t>
4650 <t>
4651 Where &lt;map&gt; is the numeric ID of the MIDI instrument map,
4652 &lt;midi_bank&gt; is an integer value between 0..16383
4653 reflecting the MIDI bank value, &lt;midi_bank&gt;
4654 and &lt;midi_prog&gt; an integer value between
4655 0..127 reflecting the MIDI program value of the map's entrie's key
4656 index triple.
4657 </t>
4658
4659 <t>Possible Answers:</t>
4660 <t>
4661 <list>
4662 <t>LinuxSampler will answer by sending a &lt;CRLF&gt;
4663 separated list. Each answer line begins with the
4664 information category name followed by a colon and then
4665 a space character &lt;SP&gt; and finally the info
4666 character string to that info category. At the moment
4667 the following categories are defined:</t>
4668 <t>"NAME" -
4669 <list>
4670 <t>Name for this MIDI instrument map entry (if defined).
4671 This name shall be used by frontends for displaying a
4672 name for this mapped instrument. It can be set and
4673 changed with the
4674 <xref target="MAP MIDI_INSTRUMENT">"MAP MIDI_INSTRUMENT"</xref>
4675 command and does not have to be unique.
4676 (note that this character string may contain
4677 <xref target="character_set">escape sequences</xref>)</t>
4678 </list>
4679 </t>
4680 <t>"ENGINE_NAME" -
4681 <list>
4682 <t>Name of the engine to be deployed for this
4683 instrument.</t>
4684 </list>
4685 </t>
4686 <t>"INSTRUMENT_FILE" -
4687 <list>
4688 <t>File name of the instrument
4689 (note that this path may contain
4690 <xref target="character_set">escape sequences</xref>).</t>
4691 </list>
4692 </t>
4693 <t>"INSTRUMENT_NR" -
4694 <list>
4695 <t>Index of the instrument within the file.</t>
4696 </list>
4697 </t>
4698 <t>"INSTRUMENT_NAME" -
4699 <list>
4700 <t>Name of the loaded instrument as reflected by its file.
4701 In contrast to the "NAME" field, the "INSTRUMENT_NAME" field
4702 cannot be changed (note that this character string may contain
4703 <xref target="character_set">escape sequences</xref>).</t>
4704 </list>
4705 </t>
4706 <t>"LOAD_MODE" -
4707 <list>
4708 <t>Life time of instrument
4709 (see <xref target="MAP MIDI_INSTRUMENT">"MAP MIDI_INSTRUMENT"</xref> for details about this setting).</t>
4710 </list>
4711 </t>
4712 <t>"VOLUME" -
4713 <list>
4714 <t>master volume of the instrument as optionally
4715 dotted number (where a value &lt; 1.0 means attenuation
4716 and a value > 1.0 means amplification)</t>
4717 </list>
4718 </t>
4719 <t>The mentioned fields above don't have to be in particular order.</t>
4720 </list>
4721 </t>
4722
4723 <t>Example:</t>
4724 <t>
4725 <list>
4726 <t>C: "GET MIDI_INSTRUMENT INFO 1 45 120"</t>
4727 <t>S: "NAME: Drums for Foo Song"</t>
4728 <t>&nbsp;&nbsp;&nbsp;"ENGINE_NAME: GigEngine"</t>
4729 <t>&nbsp;&nbsp;&nbsp;"INSTRUMENT_FILE: /usr/share/joesdrumkit.gig"</t>
4730 <t>&nbsp;&nbsp;&nbsp;"INSTRUMENT_NR: 0"</t>
4731 <t>&nbsp;&nbsp;&nbsp;"INSTRUMENT_NAME: Joe's Drumkit"</t>
4732 <t>&nbsp;&nbsp;&nbsp;"LOAD_MODE: PERSISTENT"</t>
4733 <t>&nbsp;&nbsp;&nbsp;"VOLUME: 1.0"</t>
4734 <t>&nbsp;&nbsp;&nbsp;"."</t>
4735 </list>
4736 </t>
4737 </section>
4738
4739 <section title="Clear MIDI instrument map" anchor="CLEAR MIDI_INSTRUMENTS">
4740 <t>The front-end can clear a whole MIDI instrument map, that
4741 is delete all its entries by sending the following command:</t>
4742 <t>
4743 <list>
4744 <t>CLEAR MIDI_INSTRUMENTS &lt;map&gt;</t>
4745 </list>
4746 </t>
4747 <t>Where &lt;map&gt; is the numeric ID of the map to clear.</t>
4748 <t>The front-end can clear all MIDI instrument maps, that
4749 is delete all entries of all maps by sending the following
4750 command:</t>
4751 <t>
4752 <list>
4753 <t>CLEAR MIDI_INSTRUMENTS ALL</t>
4754 </list>
4755 </t>
4756 <t>The command "CLEAR MIDI_INSTRUMENTS ALL" does not delete the
4757 maps, only their entries, thus the map's settings like
4758 custom name will be preservevd.</t>
4759
4760 <t>Possible Answers:</t>
4761 <t>
4762 <list>
4763 <t>"OK" -
4764 <list>
4765 <t>always</t>
4766 </list>
4767 </t>
4768 </list>
4769 </t>
4770
4771 <t>Examples:</t>
4772 <t>
4773 <list>
4774 <t>C: "CLEAR MIDI_INSTRUMENTS 0"</t>
4775 <t>S: "OK"</t>
4776 </list>
4777 </t>
4778 <t>
4779 <list>
4780 <t>C: "CLEAR MIDI_INSTRUMENTS ALL"</t>
4781 <t>S: "OK"</t>
4782 </list>
4783 </t>
4784 </section>
4785 </section>
4786
4787
4788 <section title="Managing Instruments Database" anchor="Managing Instruments Database">
4789 <t>The following commands describe how to use and manage
4790 the instruments database.</t>
4791 <t>Notice:</t>
4792 <t>
4793 <list>
4794 <t>All command arguments representing a path or
4795 instrument/directory name support escape sequences as described in chapter
4796 "<xref target="character_set">Character Set and Escape Sequences</xref>".
4797 </t>
4798 <t>All occurrences of a forward slash in instrument and directory
4799 names are escaped with its hex (\x2f) or octal (\057) escape sequence.
4800 </t>
4801 </list>
4802 </t>
4803
4804 <section title="Creating a new instrument directory" anchor="ADD DB_INSTRUMENT_DIRECTORY">
4805 <t>The front-end can add a new instrument directory to the
4806 instruments database by sending the following command:</t>
4807 <t>
4808 <list>
4809 <t>ADD DB_INSTRUMENT_DIRECTORY &lt;dir&gt;</t>
4810 </list>
4811 </t>
4812 <t>Where &lt;dir&gt; is the absolute path name of the directory
4813 to be created (encapsulated into apostrophes).</t>
4814
4815 <t>Possible Answers:</t>
4816 <t>
4817 <list>
4818 <t>"OK" -
4819 <list>
4820 <t>on success</t>
4821 </list>
4822 </t>
4823 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
4824 <list>
4825 <t>when the directory could not be created, which
4826 can happen if the directory already exists or the
4827 name contains not allowed symbols</t>
4828 </list>
4829 </t>
4830 </list>
4831 </t>
4832
4833 <t>Examples:</t>
4834 <t>
4835 <list>
4836 <t>C: "ADD DB_INSTRUMENT_DIRECTORY '/Piano Collection'"</t>
4837 <t>S: "OK"</t>
4838 </list>
4839 </t>
4840 </section>
4841
4842 <section title="Deleting an instrument directory" anchor="REMOVE DB_INSTRUMENT_DIRECTORY">
4843 <t>The front-end can delete a particular instrument directory
4844 from the instruments database by sending the following command:</t>
4845 <t>
4846 <list>
4847 <t>REMOVE DB_INSTRUMENT_DIRECTORY [FORCE] &lt;dir&gt;</t>
4848 </list>
4849 </t>
4850 <t>Where &lt;dir&gt; is the absolute path name of the directory
4851 to delete. The optional FORCE argument can be used to
4852 force the deletion of a non-empty directory and all its content.</t>
4853
4854 <t>Possible Answers:</t>
4855 <t>
4856 <list>
4857 <t>"OK" -
4858 <list>
4859 <t>if the directory is deleted successfully</t>
4860 </list>
4861 </t>
4862 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
4863 <list>
4864 <t>if the given directory does not exist, or
4865 if trying to delete a non-empty directory,
4866 without using the FORCE argument.</t>
4867 </list>
4868 </t>
4869 </list>
4870 </t>
4871
4872 <t>Examples:</t>
4873 <t>
4874 <list>
4875 <t>C: "REMOVE DB_INSTRUMENT_DIRECTORY FORCE '/Piano Collection'"</t>
4876 <t>S: "OK"</t>
4877 </list>
4878 </t>
4879 </section>
4880
4881 <section title="Getting amount of instrument directories" anchor="GET DB_INSTRUMENT_DIRECTORIES">
4882 <t>The front-end can retrieve the current amount of
4883 directories in a specific directory by sending the following command:</t>
4884 <t>
4885 <list>
4886 <t>GET DB_INSTRUMENT_DIRECTORIES [RECURSIVE] &lt;dir&gt;</t>
4887 </list>
4888 </t>
4889 <t>Where &lt;dir&gt; should be replaced by the absolute path
4890 name of the directory. If RECURSIVE is specified, the number of
4891 all directories, including those located in subdirectories of the
4892 specified directory, will be returned.</t>
4893
4894 <t>Possible Answers:</t>
4895 <t>
4896 <list>
4897 <t>The current number of instrument directories
4898 in the specified directory.</t>
4899 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
4900 <list>
4901 <t>if the given directory does not exist.</t>
4902 </list>
4903 </t>
4904 </list>
4905 </t>
4906
4907 <t>Example:</t>
4908 <t>
4909 <list>
4910 <t>C: "GET DB_INSTRUMENT_DIRECTORIES '/'"</t>
4911 <t>S: "2"</t>
4912 </list>
4913 </t>
4914 </section>
4915
4916 <section title="Listing all directories in specific directory" anchor="LIST DB_INSTRUMENT_DIRECTORIES">
4917 <t>The front-end can retrieve the current list of directories
4918 in specific directory by sending the following command:</t>
4919 <t>
4920 <list>
4921 <t>LIST DB_INSTRUMENT_DIRECTORIES [RECURSIVE] &lt;dir&gt;</t>
4922 </list>
4923 </t>
4924 <t>Where &lt;dir&gt; should be replaced by the absolute path
4925 name of the directory. If RECURSIVE is specified, the absolute path names
4926 of all directories, including those located in subdirectories of the
4927 specified directory, will be returned.</t>
4928
4929 <t>Possible Answers:</t>
4930 <t>
4931 <list>
4932 <t>A comma separated list of all instrument directories
4933 (encapsulated into apostrophes) in the specified directory.</t>
4934 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
4935 <list>
4936 <t>if the given directory does not exist.</t>
4937 </list>
4938 </t>
4939 </list>
4940 </t>
4941 <t>Example:</t>
4942 <t>
4943 <list>
4944 <t>C: "LIST DB_INSTRUMENT_DIRECTORIES '/'"</t>
4945 <t>S: "'Piano Collection','Percussion Collection'"</t>
4946 </list>
4947 </t>
4948 <t>
4949 <list>
4950 <t>C: "LIST DB_INSTRUMENT_DIRECTORIES RECURSIVE '/'"</t>
4951 <t>S: "'/Piano Collection','/Piano Collection/Acoustic','/Piano Collection/Acoustic/New','/Percussion Collection'"</t>
4952 </list>
4953 </t>
4954 </section>
4955
4956 <section title="Getting instrument directory information" anchor="GET DB_INSTRUMENT_DIRECTORY INFO">
4957 <t>The front-end can ask for the current settings of an
4958 instrument directory by sending the following command:</t>
4959 <t>
4960 <list>
4961 <t>GET DB_INSTRUMENT_DIRECTORY INFO &lt;dir&gt;</t>
4962 </list>
4963 </t>
4964 <t>Where &lt;dir&gt; should be replaced by the absolute path
4965 name of the directory the front-end is interested in.</t>
4966
4967 <t>Possible Answers:</t>
4968 <t>
4969 <list>
4970 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
4971 Each answer line begins with the settings category name
4972 followed by a colon and then a space character &lt;SP&gt; and finally
4973 the info character string to that setting category. At the
4974 moment the following categories are defined:</t>
4975
4976 <t>
4977 <list>
4978 <t>DESCRIPTION -
4979 <list>
4980 <t>A brief description of the directory content.
4981 Note that the character string may contain
4982 <xref target="character_set">escape sequences</xref>.</t>
4983 </list>
4984 </t>
4985 <t>CREATED -
4986 <list>
4987 <t>The creation date and time of the directory,
4988 represented in "YYYY-MM-DD HH:MM:SS" format</t>
4989 </list>
4990 </t>
4991 <t>MODIFIED -
4992 <list>
4993 <t>The date and time of the last modification of the
4994 directory, represented in "YYYY-MM-DD HH:MM:SS" format</t>
4995 </list>
4996 </t>
4997 </list>
4998 </t>
4999 </list>
5000 </t>
5001 <t>The mentioned fields above don't have to be in particular order.</t>
5002
5003 <t>Example:</t>
5004 <t>
5005 <list>
5006 <t>C: "GET DB_INSTRUMENT_DIRECTORY INFO '/Piano Collection'"</t>
5007 <t>S: "DESCRIPTION: Piano collection of instruments in GigaSampler format."</t>
5008 <t>&nbsp;&nbsp;&nbsp;"CREATED: 2007-02-05 10:23:12"</t>
5009 <t>&nbsp;&nbsp;&nbsp;"MODIFIED: 2007-04-07 12:50:21"</t>
5010 <t>&nbsp;&nbsp;&nbsp;"."</t>
5011 </list>
5012 </t>
5013 </section>
5014
5015 <section title="Renaming an instrument directory" anchor="SET DB_INSTRUMENT_DIRECTORY NAME">
5016 <t>The front-end can alter the name of a specific
5017 instrument directory by sending the following command:</t>
5018 <t>
5019 <list>
5020 <t>SET DB_INSTRUMENT_DIRECTORY NAME &lt;dir&gt; &lt;name&gt;</t>
5021 </list>
5022 </t>
5023 <t>Where &lt;dir&gt; is the absolute path name of the directory and
5024 &lt;name&gt; is the new name for that directory.</t>
5025
5026 <t>Possible Answers:</t>
5027 <t>
5028 <list>
5029 <t>"OK" -
5030 <list>
5031 <t>on success</t>
5032 </list>
5033 </t>
5034 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5035 <list>
5036 <t>in case the given directory does not exists,
5037 or if a directory with name equal to the new
5038 name already exists.</t>
5039 </list>
5040 </t>
5041 </list>
5042 </t>
5043
5044 <t>Example:</t>
5045 <t>
5046 <list>
5047 <t>C: "SET DB_INSTRUMENT_DIRECTORY NAME '/Piano Collection/Acustic' 'Acoustic'"</t>
5048 <t>S: "OK"</t>
5049 </list>
5050 </t>
5051 </section>
5052
5053 <section title="Moving an instrument directory" anchor="MOVE DB_INSTRUMENT_DIRECTORY">
5054 <t>The front-end can move a specific
5055 instrument directory by sending the following command:</t>
5056 <t>
5057 <list>
5058 <t>MOVE DB_INSTRUMENT_DIRECTORY &lt;dir&gt; &lt;dst&gt;</t>
5059 </list>
5060 </t>
5061 <t>Where &lt;dir&gt; is the absolute path name of the directory
5062 to move and &lt;dst&gt; is the location where the directory will
5063 be moved to.</t>
5064
5065 <t>Possible Answers:</t>
5066 <t>
5067 <list>
5068 <t>"OK" -
5069 <list>
5070 <t>on success</t>
5071 </list>
5072 </t>
5073 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5074 <list>
5075 <t>in case a given directory does not exists,
5076 or if a directory with name equal to the name
5077 of the specified directory already exists in
5078 the destination directory. Error is also thrown
5079 when trying to move a directory to a subdirectory
5080 of itself.</t>
5081 </list>
5082 </t>
5083 </list>
5084 </t>
5085
5086 <t>Example:</t>
5087 <t>
5088 <list>
5089 <t>C: "MOVE DB_INSTRUMENT_DIRECTORY '/Acoustic' '/Piano Collection/Acoustic'"</t>
5090 <t>S: "OK"</t>
5091 </list>
5092 </t>
5093 </section>
5094
5095 <section title="Copying instrument directories" anchor="COPY DB_INSTRUMENT_DIRECTORY">
5096 <t>The front-end can copy a specific
5097 instrument directory by sending the following command:</t>
5098 <t>
5099 <list>
5100 <t>COPY DB_INSTRUMENT_DIRECTORY &lt;dir&gt; &lt;dst&gt;</t>
5101 </list>
5102 </t>
5103 <t>Where &lt;dir&gt; is the absolute path name of the directory
5104 to copy and &lt;dst&gt; is the location where the directory will
5105 be copied to.</t>
5106
5107 <t>Possible Answers:</t>
5108 <t>
5109 <list>
5110 <t>"OK" -
5111 <list>
5112 <t>on success</t>
5113 </list>
5114 </t>
5115 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5116 <list>
5117 <t>in case a given directory does not exists,
5118 or if a directory with name equal to the name
5119 of the specified directory already exists in
5120 the destination directory. Error is also thrown
5121 when trying to copy a directory to a subdirectory
5122 of itself.</t>
5123 </list>
5124 </t>
5125 </list>
5126 </t>
5127
5128 <t>Example:</t>
5129 <t>
5130 <list>
5131 <t>C: "COPY DB_INSTRUMENT_DIRECTORY '/Piano Collection/Acoustic' '/Acoustic/Pianos'"</t>
5132 <t>S: "OK"</t>
5133 </list>
5134 </t>
5135 </section>
5136
5137 <section title="Changing the description of directory" anchor="SET DB_INSTRUMENT_DIRECTORY DESCRIPTION">
5138 <t>The front-end can alter the description of a specific
5139 instrument directory by sending the following command:</t>
5140 <t>
5141 <list>
5142 <t>SET DB_INSTRUMENT_DIRECTORY DESCRIPTION &lt;dir&gt; &lt;desc&gt;</t>
5143 </list>
5144 </t>
5145 <t>Where &lt;dir&gt; is the absolute path name of the directory and
5146 &lt;desc&gt; is the new description for the directory
5147 (encapsulated into apostrophes, supporting escape sequences as described in chapter
5148 "<xref target="character_set">Character Set and Escape Sequences</xref>").</t>
5149
5150 <t>Possible Answers:</t>
5151 <t>
5152 <list>
5153 <t>"OK" -
5154 <list>
5155 <t>on success</t>
5156 </list>
5157 </t>
5158 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5159 <list>
5160 <t>in case the given directory does not exists.</t>
5161 </list>
5162 </t>
5163 </list>
5164 </t>
5165
5166 <t>Example:</t>
5167 <t>
5168 <list>
5169 <t>C: "SET DB_INSTRUMENT_DIRECTORY DESCRIPTION '/Piano Collection' 'A collection of piano instruments in various format.'"</t>
5170 <t>S: "OK"</t>
5171 </list>
5172 </t>
5173 </section>
5174
5175 <section title="Finding directories" anchor="FIND DB_INSTRUMENT_DIRECTORIES">
5176 <t>The front-end can search for directories
5177 in specific directory by sending the following command:</t>
5178 <t>
5179 <list>
5180 <t>FIND DB_INSTRUMENT_DIRECTORIES [NON_RECURSIVE] &lt;dir&gt; &lt;criteria-list&gt;</t>
5181 </list>
5182 </t>
5183 <t>Where &lt;dir&gt; should be replaced by the absolute path
5184 name of the directory to search in. If NON_RECURSIVE is specified, the
5185 directories located in subdirectories of the specified directory will not
5186 be searched. &lt;criteria-list&gt; is a list of search criterias
5187 in form of "key1=val1 key2=val2 ...". The following criterias are
5188 allowed:</t>
5189 <t>
5190 <t>NAME='&lt;search-string&gt;'
5191 <list>
5192 <t>Restricts the search to directories, which names
5193 satisfy the supplied search string (encapsulated into apostrophes,
5194 supporting escape sequences as described in chapter
5195 "<xref target="character_set">Character Set and Escape Sequences</xref>").</t>
5196 </list>
5197 </t>
5198
5199 <t>CREATED='[&lt;date-after&gt;]..[&lt;date-before&gt;]'
5200 <list>
5201 <t>Restricts the search to directories, which creation
5202 date satisfies the specified period, where &lt;date-after&gt;
5203 and &lt;date-before&gt; are in "YYYY-MM-DD HH:MM:SS" format.
5204 If &lt;date-after&gt; is omitted the search is restricted to
5205 directories created before &lt;date-before&gt;. If
5206 &lt;date-before&gt; is omitted, the search is restricted
5207 to directories created after &lt;date-after&gt;.</t>
5208 </list>
5209 </t>
5210
5211 <t>MODIFIED='[&lt;date-after&gt;]..[&lt;date-before&gt;]'
5212 <list>
5213 <t>Restricts the search to directories, which
5214 date of last modification satisfies the specified period, where
5215 &lt;date-after&gt; and &lt;date-before&gt; are in "YYYY-MM-DD HH:MM:SS"
5216 format. If &lt;date-after&gt; is omitted the search is restricted to
5217 directories, which are last modified before &lt;date-before&gt;. If
5218 &lt;date-before&gt; is omitted, the search is restricted to directories,
5219 which are last modified after &lt;date-after&gt;.</t>
5220 </list>
5221 </t>
5222
5223 <t>DESCRIPTION='&lt;search-string&gt;'
5224 <list>
5225 <t>Restricts the search to directories with description
5226 that satisfies the supplied search string
5227 (encapsulated into apostrophes, supporting escape
5228 sequences as described in chapter
5229 "<xref target="character_set">Character Set and Escape Sequences</xref>").</t>
5230 </list>
5231 </t>
5232 </t>
5233
5234 <t>Where &lt;search-string&gt; is either a regular expression, or a
5235 word list separated with spaces for OR search and with '+' for AND search.</t>
5236
5237 <t>Possible Answers:</t>
5238 <t>
5239 <list>
5240 <t>A comma separated list with the absolute path names (encapsulated into
5241 apostrophes) of all directories in the specified directory that satisfy
5242 the supplied search criterias.</t>
5243 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5244 <list>
5245 <t>if the given directory does not exist.</t>
5246 </list>
5247 </t>
5248 </list>
5249 </t>
5250 <t>Example:</t>
5251 <t>
5252 <list>
5253 <t>C: "FIND DB_INSTRUMENT_DIRECTORIES '/' NAME='Piano'"</t>
5254 <t>S: "'/Piano Collection'"</t>
5255 </list>
5256 </t>
5257 <t>
5258 <list>
5259 <t>C: "FIND DB_INSTRUMENT_DIRECTORIES '/' CREATED='..2007-04-01 09:30:13'"</t>
5260 <t>S: "'/Piano Collection','/Percussions'"</t>
5261 </list>
5262 </t>
5263 </section>
5264
5265 <section title="Adding instruments to the instruments database" anchor="ADD DB_INSTRUMENTS">
5266 <t>The front-end can add one or more instruments
5267 to the instruments database by sending the following command:</t>
5268 <t>
5269 <list>
5270 <t>ADD DB_INSTRUMENTS [NON_MODAL] [&lt;mode&gt;] &lt;db_dir&gt; &lt;file_path&gt; [&lt;instr_index&gt;]</t>
5271 </list>
5272 </t>
5273 <t>Where &lt;db_dir&gt; is the absolute path name of a directory
5274 (encapsulated into apostrophes) in the instruments database in which
5275 only the new instruments (that are not already in the database) will
5276 be added, &lt;file_path&gt; is the absolute path name of a file or
5277 directory in the file system (encapsulated into apostrophes). In case
5278 an instrument file is supplied, only the instruments in the specified
5279 file will be added to the instruments database. If the optional
5280 &lt;instr_index&gt; (the index of the instrument within the given file)
5281 is supplied too, then only the specified instrument will be added.
5282 In case a directory is supplied, the instruments in that directory
5283 will be added. The OPTIONAL &lt;mode&gt; argument is only applied
5284 when a directory is provided as &lt;file_path&gt; and specifies how the
5285 scanning will be done and has exactly the following possibilities:</t>
5286 <t>
5287 <list>
5288 <t>"RECURSIVE" -
5289 <list>
5290 <t>All instruments will be processed, including those
5291 in the subdirectories, and the respective subdirectory
5292 tree structure will be recreated in the instruments
5293 database</t>
5294 </list>
5295 </t>
5296 <t>"NON_RECURSIVE" -
5297 <list>
5298 <t>Only the instruments in the specified directory
5299 will be added, the instruments in the subdirectories
5300 will not be processed.</t>
5301 </list>
5302 </t>
5303 <t>"FLAT" -
5304 <list>
5305 <t>All instruments will be processed, including those
5306 in the subdirectories, but the respective subdirectory
5307 structure will not be recreated in the instruments
5308 database. All instruments will be added directly in
5309 the specified database directory.</t>
5310 </list>
5311 </t>
5312 </list>
5313 </t>
5314
5315 <t>The difference between regular and NON_MODAL versions of the command
5316 is that the regular command returns when the scanning is finished
5317 while NON_MODAL version returns immediately and a background process is launched.
5318 The <xref target="GET DB_INSTRUMENTS_JOB INFO">GET DB_INSTRUMENTS_JOB INFO</xref>
5319 command can be used to monitor the scanning progress.</t>
5320
5321 <t>Possible Answers:</t>
5322 <t>
5323 <list>
5324 <t>"OK" -
5325 <list>
5326 <t>on success when NON_MODAL is not supplied</t>
5327 </list>
5328 </t>
5329 <t>"OK[&lt;job-id&gt;]" -
5330 <list>
5331 <t>on success when NON_MODAL is supplied, where &lt;job-id&gt;
5332 is a numerical ID used to obtain status information about the job progress.
5333 See <xref target="GET DB_INSTRUMENTS_JOB INFO">GET DB_INSTRUMENTS_JOB INFO</xref>
5334 </t>
5335 </list>
5336 </t>
5337 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5338 <list>
5339 <t>if an invalid path is specified.</t>
5340 </list>
5341 </t>
5342 </list>
5343 </t>
5344
5345 <t>Examples:</t>
5346 <t>
5347 <list>
5348 <t>C: "ADD DB_INSTRUMENTS '/Piano Collection' '/home/me/gigs/PMI Bosendorfer 290.gig' 0"</t>
5349 <t>S: "OK"</t>
5350 </list>
5351 </t>
5352 </section>
5353
5354 <section title="Removing an instrument" anchor="REMOVE DB_INSTRUMENT">
5355 <t>The front-end can remove a particular instrument
5356 from the instruments database by sending the following command:</t>
5357 <t>
5358 <list>
5359 <t>REMOVE DB_INSTRUMENT &lt;instr_path&gt;</t>
5360 </list>
5361 </t>
5362 <t>Where &lt;instr_path&gt; is the absolute path name
5363 (in the instruments database) of the instrument to remove.</t>
5364
5365 <t>Possible Answers:</t>
5366 <t>
5367 <list>
5368 <t>"OK" -
5369 <list>
5370 <t>if the instrument is removed successfully</t>
5371 </list>
5372 </t>
5373 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5374 <list>
5375 <t>if the given path does not exist or
5376 is a directory.</t>
5377 </list>
5378 </t>
5379 </list>
5380 </t>
5381
5382 <t>Examples:</t>
5383 <t>
5384 <list>
5385 <t>C: "REMOVE DB_INSTRUMENT '/Piano Collection/Bosendorfer 290'"</t>
5386 <t>S: "OK"</t>
5387 </list>
5388 </t>
5389 </section>
5390
5391 <section title="Getting amount of instruments" anchor="GET DB_INSTRUMENTS">
5392 <t>The front-end can retrieve the current amount of
5393 instruments in a specific directory by sending the following command:</t>
5394 <t>
5395 <list>
5396 <t>GET DB_INSTRUMENTS [RECURSIVE] &lt;dir&gt;</t>
5397 </list>
5398 </t>
5399 <t>Where &lt;dir&gt; should be replaced by the absolute path name
5400 of the directory. If RECURSIVE is specified, the number of all
5401 instruments, including those located in subdirectories of the
5402 specified directory, will be returned.</t>
5403
5404 <t>Possible Answers:</t>
5405 <t>
5406 <list>
5407 <t>The current number of instruments
5408 in the specified directory.</t>
5409 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5410 <list>
5411 <t>if the given directory does not exist.</t>
5412 </list>
5413 </t>
5414 </list>
5415 </t>
5416
5417 <t>Example:</t>
5418 <t>
5419 <list>
5420 <t>C: "GET DB_INSTRUMENTS '/Piano Collection'"</t>
5421 <t>S: "2"</t>
5422 </list>
5423 </t>
5424 </section>
5425
5426 <section title="Listing all instruments in specific directory" anchor="LIST DB_INSTRUMENTS">
5427 <t>The front-end can retrieve the current list of instruments
5428 in specific directory by sending the following command:</t>
5429 <t>
5430 <list>
5431 <t>LIST DB_INSTRUMENTS [RECURSIVE] &lt;dir&gt;</t>
5432 </list>
5433 </t>
5434 <t>Where &lt;dir&gt; should be replaced by the absolute path
5435 name of the directory. If RECURSIVE is specified, the absolute path
5436 names of all instruments, including those located in subdirectories
5437 of the specified directory, will be returned.</t>
5438
5439 <t>Possible Answers:</t>
5440 <t>
5441 <list>
5442 <t>A comma separated list of all instruments
5443 (encapsulated into apostrophes) in the specified directory.</t>
5444 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5445 <list>
5446 <t>if the given directory does not exist.</t>
5447 </list>
5448 </t>
5449 </list>
5450 </t>
5451 <t>Example:</t>
5452 <t>
5453 <list>
5454 <t>C: "LIST DB_INSTRUMENTS '/Piano Collection'"</t>
5455 <t>S: "'Bosendorfer 290','Steinway D'"</t>
5456 </list>
5457 </t>
5458 <t>
5459 <list>
5460 <t>C: "LIST DB_INSTRUMENTS RECURSIVE '/Piano Collection'"</t>
5461 <t>S: "'/Piano Collection/Bosendorfer 290','/Piano Collection/Steinway D','/Piano Collection/Lite/Free Piano'"</t>
5462 </list>
5463 </t>
5464 </section>
5465
5466 <section title="Getting instrument information" anchor="GET DB_INSTRUMENT INFO">
5467 <t>The front-end can ask for the current settings of an
5468 instrument by sending the following command:</t>
5469 <t>
5470 <list>
5471 <t>GET DB_INSTRUMENT INFO &lt;instr_path&gt;</t>
5472 </list>
5473 </t>
5474 <t>Where &lt;instr_path&gt; should be replaced by the absolute path
5475 name of the instrument the front-end is interested in.</t>
5476
5477 <t>Possible Answers:</t>
5478 <t>
5479 <list>
5480 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
5481 Each answer line begins with the settings category name
5482 followed by a colon and then a space character &lt;SP&gt; and finally
5483 the info character string to that setting category. At the
5484 moment the following categories are defined:</t>
5485
5486 <t>
5487 <list>
5488 <t>INSTRUMENT_FILE -
5489 <list>
5490 <t>File name of the instrument.
5491 Note that the character string may contain
5492 <xref target="character_set">escape sequences</xref>.</t>
5493 </list>
5494 </t>
5495 <t>INSTRUMENT_NR -
5496 <list>
5497 <t>Index of the instrument within the file.</t>
5498 </list>
5499 </t>
5500 <t>FORMAT_FAMILY -
5501 <list>
5502 <t>The format family of the instrument.</t>
5503 </list>
5504 </t>
5505 <t>FORMAT_VERSION -
5506 <list>
5507 <t>The format version of the instrument.</t>
5508 </list>
5509 </t>
5510 <t>SIZE -
5511 <list>
5512 <t>The size of the instrument in bytes.</t>
5513 </list>
5514 </t>
5515 <t>CREATED -
5516 <list>
5517 <t>The date and time when the instrument is added
5518 in the instruments database, represented in
5519 "YYYY-MM-DD HH:MM:SS" format</t>
5520 </list>
5521 </t>
5522 <t>MODIFIED -
5523 <list>
5524 <t>The date and time of the last modification of the
5525 instrument's database settings, represented in
5526 "YYYY-MM-DD HH:MM:SS" format</t>
5527 </list>
5528 </t>
5529 <t>DESCRIPTION -
5530 <list>
5531 <t>A brief description of the instrument.
5532 Note that the character string may contain
5533 <xref target="character_set">escape sequences</xref>.</t>
5534 </list>
5535 </t>
5536 <t>IS_DRUM -
5537 <list>
5538 <t>either true or false, determines whether the
5539 instrument is a drumkit or a chromatic instrument</t>
5540 </list>
5541 </t>
5542 <t>PRODUCT -
5543 <list>
5544 <t>The product title of the instrument.
5545 Note that the character string may contain
5546 <xref target="character_set">escape sequences</xref>.</t>
5547 </list>
5548 </t>
5549 <t>ARTISTS -
5550 <list>
5551 <t>Lists the artist names.
5552 Note that the character string may contain
5553 <xref target="character_set">escape sequences</xref>.</t>
5554 </list>
5555 </t>
5556 <t>KEYWORDS -
5557 <list>
5558 <t>Provides a list of keywords that refer to the instrument.
5559 Keywords are separated with semicolon and blank.
5560 Note that the character string may contain
5561 <xref target="character_set">escape sequences</xref>.</t>
5562 </list>
5563 </t>
5564 </list>
5565 </t>
5566 </list>
5567 </t>
5568 <t>The mentioned fields above don't have to be in particular order.</t>
5569
5570 <t>Example:</t>
5571 <t>
5572 <list>
5573 <t>C: "GET DB_INSTRUMENT INFO '/Piano Collection/Bosendorfer 290'"</t>
5574 <t>S: "INSTRUMENT_FILE: /home/me/gigs/Bosendorfer 290.gig"</t>
5575 <t>&nbsp;&nbsp;&nbsp;"INSTRUMENT_NR: 0"</t>
5576 <t>&nbsp;&nbsp;&nbsp;"FORMAT_FAMILY: GIG"</t>
5577 <t>&nbsp;&nbsp;&nbsp;"FORMAT_VERSION: 2"</t>
5578 <t>&nbsp;&nbsp;&nbsp;"SIZE: 2050871870"</t>
5579 <t>&nbsp;&nbsp;&nbsp;"CREATED: 2007-02-05 10:23:12"</t>
5580 <t>&nbsp;&nbsp;&nbsp;"MODIFIED: 2007-04-07 12:50:21"</t>
5581 <t>&nbsp;&nbsp;&nbsp;"DESCRIPTION: "</t>
5582 <t>&nbsp;&nbsp;&nbsp;"IS_DRUM: false"</t>
5583 <t>&nbsp;&nbsp;&nbsp;"PRODUCT: GRANDIOSO Bosendorfer 290"</t>
5584 <t>&nbsp;&nbsp;&nbsp;"ARTISTS: Post Musical Instruments"</t>
5585 <t>&nbsp;&nbsp;&nbsp;"KEYWORDS: Bosendorfer"</t>
5586 <t>&nbsp;&nbsp;&nbsp;"."</t>
5587 </list>
5588 </t>
5589 </section>
5590
5591 <section title="Renaming an instrument" anchor="SET DB_INSTRUMENT NAME">
5592 <t>The front-end can alter the name of a specific
5593 instrument by sending the following command:</t>
5594 <t>
5595 <list>
5596 <t>SET DB_INSTRUMENT NAME &lt;instr&gt; &lt;name&gt;</t>
5597 </list>
5598 </t>
5599 <t>Where &lt;instr&gt; is the absolute path name of the instrument and
5600 &lt;name&gt; is the new name for that instrument.</t>
5601
5602 <t>Possible Answers:</t>
5603 <t>
5604 <list>
5605 <t>"OK" -
5606 <list>
5607 <t>on success</t>
5608 </list>
5609 </t>
5610 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5611 <list>
5612 <t>in case the given instrument does not exists,
5613 or if an instrument with name equal to the new
5614 name already exists.</t>
5615 </list>
5616 </t>
5617 </list>
5618 </t>
5619
5620 <t>Example:</t>
5621 <t>
5622 <list>
5623 <t>C: "SET DB_INSTRUMENT NAME '/Piano Collection/Bosendorfer' 'Bosendorfer 290'"</t>
5624 <t>S: "OK"</t>
5625 </list>
5626 </t>
5627 </section>
5628
5629 <section title="Moving an instrument" anchor="MOVE DB_INSTRUMENT">
5630 <t>The front-end can move a specific instrument to another directory by
5631 sending the following command:</t>
5632 <t>
5633 <list>
5634 <t>MOVE DB_INSTRUMENT &lt;instr&gt; &lt;dst&gt;</t>
5635 </list>
5636 </t>
5637 <t>Where &lt;instr&gt; is the absolute path name of the instrument
5638 to move and &lt;dst&gt; is the directory where the instrument will
5639 be moved to.</t>
5640
5641 <t>Possible Answers:</t>
5642 <t>
5643 <list>
5644 <t>"OK" -
5645 <list>
5646 <t>on success</t>
5647 </list>
5648 </t>
5649 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5650 <list>
5651 <t>in case the given instrument does not exists,
5652 or if an instrument with name equal to the name of the
5653 specified instrument already exists in the destination
5654 directory.</t>
5655 </list>
5656 </t>
5657 </list>
5658 </t>
5659
5660 <t>Example:</t>
5661 <t>
5662 <list>
5663 <t>C: "MOVE DB_INSTRUMENT '/Piano Collection/Bosendorfer 290' '/Piano Collection/Acoustic'"</t>
5664 <t>S: "OK"</t>
5665 </list>
5666 </t>
5667 </section>
5668
5669 <section title="Copying instruments" anchor="COPY DB_INSTRUMENT">
5670 <t>The front-end can copy a specific instrument to another directory by
5671 sending the following command:</t>
5672 <t>
5673 <list>
5674 <t>COPY DB_INSTRUMENT &lt;instr&gt; &lt;dst&gt;</t>
5675 </list>
5676 </t>
5677 <t>Where &lt;instr&gt; is the absolute path name of the instrument
5678 to copy and &lt;dst&gt; is the directory where the instrument will
5679 be copied to.</t>
5680
5681 <t>Possible Answers:</t>
5682 <t>
5683 <list>
5684 <t>"OK" -
5685 <list>
5686 <t>on success</t>
5687 </list>
5688 </t>
5689 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5690 <list>
5691 <t>in case the given instrument does not exists,
5692 or if an instrument with name equal to the name of the
5693 specified instrument already exists in the destination
5694 directory.</t>
5695 </list>
5696 </t>
5697 </list>
5698 </t>
5699
5700 <t>Example:</t>
5701 <t>
5702 <list>
5703 <t>C: "COPY DB_INSTRUMENT '/Piano Collection/Bosendorfer 290' '/Acoustic/Pianos/'"</t>
5704 <t>S: "OK"</t>
5705 </list>
5706 </t>
5707 </section>
5708
5709 <section title="Changing the description of instrument" anchor="SET DB_INSTRUMENT DESCRIPTION">
5710 <t>The front-end can alter the description of a specific
5711 instrument by sending the following command:</t>
5712 <t>
5713 <list>
5714 <t>SET DB_INSTRUMENT DESCRIPTION &lt;instr&gt; &lt;desc&gt;</t>
5715 </list>
5716 </t>
5717 <t>Where &lt;instr&gt; is the absolute path name of the instrument and
5718 &lt;desc&gt; is the new description for the instrument
5719 (encapsulated into apostrophes, supporting escape sequences as described in chapter
5720 "<xref target="character_set">Character Set and Escape Sequences</xref>").</t>
5721
5722 <t>Possible Answers:</t>
5723 <t>
5724 <list>
5725 <t>"OK" -
5726 <list>
5727 <t>on success</t>
5728 </list>
5729 </t>
5730 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5731 <list>
5732 <t>in case the given instrument does not exists.</t>
5733 </list>
5734 </t>
5735 </list>
5736 </t>
5737
5738 <t>Example:</t>
5739 <t>
5740 <list>
5741 <t>C: "SET DB_INSTRUMENT DESCRIPTION '/Piano Collection/Acoustic/Bosendorfer 290' 'No comment :)'"</t>
5742 <t>S: "OK"</t>
5743 </list>
5744 </t>
5745 </section>
5746
5747 <section title="Finding instruments" anchor="FIND DB_INSTRUMENTS">
5748 <t>The front-end can search for instruments
5749 in specific directory by sending the following command:</t>
5750 <t>
5751 <list>
5752 <t>FIND DB_INSTRUMENTS [NON_RECURSIVE] &lt;dir&gt; &lt;criteria-list&gt;</t>
5753 </list>
5754 </t>
5755 <t>Where &lt;dir&gt; should be replaced by the absolute path
5756 name of the directory to search in. If NON_RECURSIVE is specified, the
5757 directories located in subdirectories of the specified directory will not
5758 be searched. &lt;criteria-list&gt; is a list of search criterias
5759 in form of "key1=val1 key2=val2 ...". The following criterias are
5760 allowed:</t>
5761 <t>
5762 <t>NAME='&lt;search-string&gt;'
5763 <list>
5764 <t>Restricts the search to instruments, which names
5765 satisfy the supplied search string (encapsulated into apostrophes,
5766 supporting escape sequences as described in chapter
5767 "<xref target="character_set">Character Set and Escape Sequences</xref>").</t>
5768 </list>
5769 </t>
5770
5771 <t>SIZE=[&lt;min&gt;]..[&lt;max&gt;]
5772 <list>
5773 <t>Restricts the search to instruments, which
5774 size is in the specified range. If &lt;min&gt; is omitted,
5775 the search results are restricted to instruments with size less then
5776 or equal to &lt;max&gt;. If &lt;max&gt; is omitted, the
5777 search is restricted to instruments with size greater then
5778 or equal to &lt;min&gt;.</t>
5779 </list>
5780 </t>
5781
5782 <t>CREATED='[&lt;date-after&gt;]..[&lt;date-before&gt;]'
5783 <list>
5784 <t>Restricts the search to instruments, which creation
5785 date satisfies the specified period, where &lt;date-after&gt;
5786 and &lt;date-before&gt; are in "YYYY-MM-DD HH:MM:SS" format.
5787 If &lt;date-after&gt; is omitted the search is restricted to
5788 instruments created before &lt;date-before&gt;. If
5789 &lt;date-before&gt; is omitted, the search is restricted
5790 to instruments created after &lt;date-after&gt;.</t>
5791 </list>
5792 </t>
5793
5794 <t>MODIFIED='[&lt;date-after&gt;]..[&lt;date-before&gt;]'
5795 <list>
5796 <t>Restricts the search to instruments, which
5797 date of last modification satisfies the specified period, where
5798 &lt;date-after&gt; and &lt;date-before&gt; are in "YYYY-MM-DD HH:MM:SS"
5799 format. If &lt;date-after&gt; is omitted the search is restricted to
5800 instruments, which are last modified before &lt;date-before&gt;. If
5801 &lt;date-before&gt; is omitted, the search is restricted to instruments,
5802 which are last modified after &lt;date-after&gt;.</t>
5803 </list>
5804 </t>
5805
5806 <t>DESCRIPTION='&lt;search-string&gt;'
5807 <list>
5808 <t>Restricts the search to instruments with description
5809 that satisfies the supplied search string (encapsulated into apostrophes,
5810 supporting escape sequences as described in chapter
5811 "<xref target="character_set">Character Set and Escape Sequences</xref>").</t>
5812 </list>
5813 </t>
5814
5815 <t>PRODUCT='&lt;search-string&gt;'
5816 <list>
5817 <t>Restricts the search to instruments with product info
5818 that satisfies the supplied search string (encapsulated into apostrophes,
5819 supporting escape sequences as described in chapter
5820 "<xref target="character_set">Character Set and Escape Sequences</xref>").</t>
5821 </list>
5822 </t>
5823
5824 <t>ARTISTS='&lt;search-string&gt;'
5825 <list>
5826 <t>Restricts the search to instruments with artists info
5827 that satisfies the supplied search string (encapsulated into apostrophes,
5828 supporting escape sequences as described in chapter
5829 "<xref target="character_set">Character Set and Escape Sequences</xref>").</t>
5830 </list>
5831 </t>
5832
5833 <t>KEYWORDS='&lt;search-string&gt;'
5834 <list>
5835 <t>Restricts the search to instruments with keyword list
5836 that satisfies the supplied search string (encapsulated into apostrophes,
5837 supporting escape sequences as described in chapter
5838 "<xref target="character_set">Character Set and Escape Sequences</xref>").</t>
5839 </list>
5840 </t>
5841
5842 <t>IS_DRUM=true | false
5843 <list>
5844 <t>Either true or false. Restricts the search to
5845 drum kits or chromatic instruments.</t>
5846 </list>
5847 </t>
5848
5849 <t>FORMAT_FAMILIES='&lt;format-list&gt;'
5850 <list>
5851 <t>Restricts the search to instruments of the supplied format families,
5852 where &lt;format-list&gt; is a comma separated list of format families.</t>
5853 </list>
5854 </t>
5855 </t>
5856
5857 <t>Where &lt;search-string&gt; is either a regular expression, or a
5858 word list separated with spaces for OR search and with '+' for AND search.</t>
5859
5860 <t>Possible Answers:</t>
5861 <t>
5862 <list>
5863 <t>A comma separated list with the absolute path names (encapsulated into
5864 apostrophes) of all instruments in the specified directory that satisfy
5865 the supplied search criterias.</t>
5866 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5867 <list>
5868 <t>if the given directory does not exist.</t>
5869 </list>
5870 </t>
5871 </list>
5872 </t>
5873 <t>Example:</t>
5874 <t>
5875 <list>
5876 <t>C: "FIND DB_INSTRUMENTS '/Piano Collection' NAME='bosendorfer+290'"</t>
5877 <t>S: "'/Piano Collection/Bosendorfer 290'"</t>
5878 </list>
5879 </t>
5880 <t>
5881 <list>
5882 <t>C: "FIND DB_INSTRUMENTS '/Piano Collection' CREATED='2007-04-01 09:30:13..'"</t>
5883 <t>S: "'/Piano Collection/Bosendorfer 290','/Piano Collection/Steinway D'"</t>
5884 </list>
5885 </t>
5886 </section>
5887
5888 <section title="Getting job status information" anchor="GET DB_INSTRUMENTS_JOB INFO">
5889 <t>The front-end can ask for the current status of a
5890 particular database instruments job by sending the following command:</t>
5891 <t>
5892 <list>
5893 <t>GET DB_INSTRUMENTS_JOB INFO &lt;job-id&gt;</t>
5894 </list>
5895 </t>
5896 <t>Where &lt;job-id&gt; should be replaced by the numerical ID
5897 of the job the front-end is interested in.</t>
5898
5899 <t>Possible Answers:</t>
5900 <t>
5901 <list>
5902 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
5903 Each answer line begins with the settings category name
5904 followed by a colon and then a space character &lt;SP&gt; and finally
5905 the info character string to that setting category. At the
5906 moment the following categories are defined:</t>
5907
5908 <t>
5909 <list>
5910 <t>FILES_TOTAL -
5911 <list>
5912 <t>The total number of files scheduled for scanning</t>
5913 </list>
5914 </t>
5915 <t>FILES_SCANNED -
5916 <list>
5917 <t>The current number of scanned files</t>
5918 </list>
5919 </t>
5920 <t>SCANNING -
5921 <list>
5922 <t>The absolute path name of the file which is currently
5923 being scanned</t>
5924 </list>
5925 </t>
5926 <t>STATUS -
5927 <list>
5928 <t>An integer value between 0 and 100 indicating the
5929 scanning progress percentage of the file which is
5930 currently being scanned</t>
5931 </list>
5932 </t>
5933 </list>
5934 </t>
5935 </list>
5936 </t>
5937 <t>The mentioned fields above don't have to be in particular order.</t>
5938
5939 <t>Example:</t>
5940 <t>
5941 <list>
5942 <t>C: "GET DB_INSTRUMENTS_JOB INFO 2"</t>
5943 <t>S: "FILES_TOTAL: 12"</t>
5944 <t>&nbsp;&nbsp;&nbsp;"FILES_SCANNED: 7"</t>
5945 <t>&nbsp;&nbsp;&nbsp;"SCANNING: /home/me/gigs/Bosendorfer 290.gig"</t>
5946 <t>&nbsp;&nbsp;&nbsp;"STATUS: 42"</t>
5947 <t>&nbsp;&nbsp;&nbsp;"."</t>
5948 </list>
5949 </t>
5950 </section>
5951
5952 <section title="Formatting the instruments database" anchor="FORMAT INSTRUMENTS_DB">
5953 <t>The front-end can remove all instruments and directories and re-create
5954 the instruments database structure (e.g., in case of a database corruption)
5955 by sending the following command:</t>
5956 <t>
5957 <list>
5958 <t>FORMAT INSTRUMENTS_DB</t>
5959 </list>
5960 </t>
5961
5962 <t>Possible Answers:</t>
5963 <t>
5964 <list>
5965 <t>"OK" -
5966 <list>
5967 <t>on success</t>
5968 </list>
5969 </t>
5970 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
5971 <list>
5972 <t>If the formatting of the instruments database
5973 failed.</t>
5974 </list>
5975 </t>
5976 </list>
5977 </t>
5978 </section>
5979
5980 </section>
5981
5982
5983
5984 <section title="Editing Instruments" anchor="editing_instruments">
5985 <t>The sampler allows to edit instruments while playing with the
5986 sampler by spawning an external (3rd party) instrument editor
5987 application for a given instrument. The 3rd party instrument
5988 editor applications have to place a respective plugin DLL file
5989 into the sampler's plugins directory. The sampler will
5990 automatically try to load all plugin DLLs in that directory on
5991 startup and only on startup!</t>
5992 <t>At the moment there is only one command for this feature set,
5993 but this will most probably change in future.</t>
5994
5995 <section title="Opening an appropriate instrument editor application" anchor="EDIT INSTRUMENT">
5996 <t>The front-end can request to open an appropriate instrument
5997 editor application by sending the following command:</t>
5998 <t>
5999 <list>
6000 <t>EDIT CHANNEL INSTRUMENT &lt;sampler-channel&gt;</t>
6001 </list>
6002 </t>
6003 <t>Where &lt;sampler-channel&gt; should be replaced by the
6004 number of the sampler channel as given by the
6005 <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
6006 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref>
6007 command.</t>
6008
6009 <t>The sampler will try to ask all registered instrument
6010 editors (or to be more specific: their sampler plugins)
6011 whether they are capable to handle the instrument on the
6012 given sampler channel. The sampler will simply use the first
6013 instrument editor application which replied with a positive
6014 answer and spawn that instrument editor application within
6015 the sampler's process and provide that application access
6016 to the instrument's data structures, so both applications
6017 can share and access the same instruments data at the same
6018 time, thus allowing to immediately hear changes with the
6019 sampler made by the instrument editor.</t>
6020
6021 <t>Note: consequently instrument editors are always spawned
6022 locally on the same machine where the sampler is running
6023 on!</t>
6024
6025 <t>Possible Answers:</t>
6026 <t>
6027 <list>
6028 <t>"OK" -
6029 <list>
6030 <t>when an appropriate instrument editor was
6031 launched</t>
6032 </list>
6033 </t>
6034 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
6035 <list>
6036 <t>when an appropriate instrument editor was
6037 launched, but there are noteworthy issues</t>
6038 </list>
6039 </t>
6040 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
6041 <list>
6042 <t>when an appropriate instrument editor
6043 could not be launched</t>
6044 </list>
6045 </t>
6046 </list>
6047 </t>
6048
6049 <t>Examples:</t>
6050 <t>
6051 <list>
6052 <t>C: "EDIT CHANNEL INSTRUMENT 0"</t>
6053 <t>S: "OK"</t>
6054 </list>
6055 </t>
6056 </section>
6057 </section>
6058 </section>
6059
6060
6061 <section title="Command Syntax" anchor="command_syntax">
6062 <t>The grammar of the control protocol as descibed in <xref target="control_commands"/>
6063 is defined below using Backus-Naur Form (BNF as described in <xref target="RFC2234"/>)
6064 where applicable.
6065 </t>
6066 <!--
6067 This section is automatically generated by scripts/update_grammar.pl
6068 from src/network/lscp.y (yacc input file). Do not modify this section
6069 manually !
6070 -->
6071 <!-- GRAMMAR_BNF_BEGIN - do NOT delete or modify this line !!! -->
6072
6073 <t>input =
6074 <list>
6075 <t>line LF
6076 </t>
6077 <t>/ line CR LF
6078 </t>
6079 </list>
6080 </t>
6081 <t>line =
6082 <list>
6083 <t>/* epsilon (empty line ignored) */
6084 </t>
6085 <t>/ comment
6086 </t>
6087 <t>/ command
6088 </t>
6089 <t>/ error
6090 </t>
6091 </list>
6092 </t>
6093 <t>comment =
6094 <list>
6095 <t>'#'
6096 </t>
6097 <t>/ comment '#'
6098 </t>
6099 <t>/ comment SP
6100 </t>
6101 <t>/ comment number
6102 </t>
6103 <t>/ comment string
6104 </t>
6105 </list>
6106 </t>
6107 <t>command =
6108 <list>
6109 <t>ADD SP add_instruction
6110 </t>
6111 <t>/ MAP SP map_instruction
6112 </t>
6113 <t>/ UNMAP SP unmap_instruction
6114 </t>
6115 <t>/ GET SP get_instruction
6116 </t>
6117 <t>/ CREATE SP create_instruction
6118 </t>
6119 <t>/ DESTROY SP destroy_instruction
6120 </t>
6121 <t>/ LIST SP list_instruction
6122 </t>
6123 <t>/ LOAD SP load_instruction
6124 </t>
6125 <t>/ REMOVE SP remove_instruction
6126 </t>
6127 <t>/ SET SP set_instruction
6128 </t>
6129 <t>/ SUBSCRIBE SP subscribe_event
6130 </t>
6131 <t>/ UNSUBSCRIBE SP unsubscribe_event
6132 </t>
6133 <t>/ RESET SP reset_instruction
6134 </t>
6135 <t>/ CLEAR SP clear_instruction
6136 </t>
6137 <t>/ FIND SP find_instruction
6138 </t>
6139 <t>/ MOVE SP move_instruction
6140 </t>
6141 <t>/ COPY SP copy_instruction
6142 </t>
6143 <t>/ EDIT SP edit_instruction
6144 </t>
6145 <t>/ FORMAT SP format_instruction
6146 </t>
6147 <t>/ RESET
6148 </t>
6149 <t>/ QUIT
6150 </t>
6151 </list>
6152 </t>
6153 <t>add_instruction =
6154 <list>
6155 <t>CHANNEL
6156 </t>
6157 <t>/ DB_INSTRUMENT_DIRECTORY SP db_path
6158 </t>
6159 <t>/ DB_INSTRUMENTS SP NON_MODAL SP scan_mode SP db_path SP filename
6160 </t>
6161 <t>/ DB_INSTRUMENTS SP scan_mode SP db_path SP filename
6162 </t>
6163 <t>/ DB_INSTRUMENTS SP NON_MODAL SP db_path SP filename
6164 </t>
6165 <t>/ DB_INSTRUMENTS SP NON_MODAL SP db_path SP filename SP instrument_index
6166 </t>
6167 <t>/ DB_INSTRUMENTS SP db_path SP filename
6168 </t>
6169 <t>/ DB_INSTRUMENTS SP db_path SP filename SP instrument_index
6170 </t>
6171 <t>/ MIDI_INSTRUMENT_MAP
6172 </t>
6173 <t>/ MIDI_INSTRUMENT_MAP SP map_name
6174 </t>
6175 </list>
6176 </t>
6177 <t>subscribe_event =
6178 <list>
6179 <t>AUDIO_OUTPUT_DEVICE_COUNT
6180 </t>
6181 <t>/ AUDIO_OUTPUT_DEVICE_INFO
6182 </t>
6183 <t>/ MIDI_INPUT_DEVICE_COUNT
6184 </t>
6185 <t>/ MIDI_INPUT_DEVICE_INFO
6186 </t>
6187 <t>/ CHANNEL_COUNT
6188 </t>
6189 <t>/ VOICE_COUNT
6190 </t>
6191 <t>/ STREAM_COUNT
6192 </t>
6193 <t>/ BUFFER_FILL
6194 </t>
6195 <t>/ CHANNEL_INFO
6196 </t>
6197 <t>/ FX_SEND_COUNT
6198 </t>
6199 <t>/ FX_SEND_INFO
6200 </t>
6201 <t>/ MIDI_INSTRUMENT_MAP_COUNT
6202 </t>
6203 <t>/ MIDI_INSTRUMENT_MAP_INFO
6204 </t>
6205 <t>/ MIDI_INSTRUMENT_COUNT
6206 </t>
6207 <t>/ MIDI_INSTRUMENT_INFO
6208 </t>
6209 <t>/ DB_INSTRUMENT_DIRECTORY_COUNT
6210 </t>
6211 <t>/ DB_INSTRUMENT_DIRECTORY_INFO
6212 </t>
6213 <t>/ DB_INSTRUMENT_COUNT
6214 </t>
6215 <t>/ DB_INSTRUMENT_INFO
6216 </t>
6217 <t>/ DB_INSTRUMENTS_JOB_INFO
6218 </t>
6219 <t>/ MISCELLANEOUS
6220 </t>
6221 <t>/ TOTAL_VOICE_COUNT
6222 </t>
6223 <t>/ GLOBAL_INFO
6224 </t>
6225 </list>
6226 </t>
6227 <t>unsubscribe_event =
6228 <list>
6229 <t>AUDIO_OUTPUT_DEVICE_COUNT
6230 </t>
6231 <t>/ AUDIO_OUTPUT_DEVICE_INFO
6232 </t>
6233 <t>/ MIDI_INPUT_DEVICE_COUNT
6234 </t>
6235 <t>/ MIDI_INPUT_DEVICE_INFO
6236 </t>
6237 <t>/ CHANNEL_COUNT
6238 </t>
6239 <t>/ VOICE_COUNT
6240 </t>
6241 <t>/ STREAM_COUNT
6242 </t>
6243 <t>/ BUFFER_FILL
6244 </t>
6245 <t>/ CHANNEL_INFO
6246 </t>
6247 <t>/ FX_SEND_COUNT
6248 </t>
6249 <t>/ FX_SEND_INFO
6250 </t>
6251 <t>/ MIDI_INSTRUMENT_MAP_COUNT
6252 </t>
6253 <t>/ MIDI_INSTRUMENT_MAP_INFO
6254 </t>
6255 <t>/ MIDI_INSTRUMENT_COUNT
6256 </t>
6257 <t>/ MIDI_INSTRUMENT_INFO
6258 </t>
6259 <t>/ DB_INSTRUMENT_DIRECTORY_COUNT
6260 </t>
6261 <t>/ DB_INSTRUMENT_DIRECTORY_INFO
6262 </t>
6263 <t>/ DB_INSTRUMENT_COUNT
6264 </t>
6265 <t>/ DB_INSTRUMENT_INFO
6266 </t>
6267 <t>/ DB_INSTRUMENTS_JOB_INFO
6268 </t>
6269 <t>/ MISCELLANEOUS
6270 </t>
6271 <t>/ TOTAL_VOICE_COUNT
6272 </t>
6273 <t>/ GLOBAL_INFO
6274 </t>
6275 </list>
6276 </t>
6277 <t>map_instruction =
6278 <list>
6279 <t>MIDI_INSTRUMENT SP modal_arg midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value
6280 </t>
6281 <t>/ MIDI_INSTRUMENT SP modal_arg midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP instr_load_mode
6282 </t>
6283 <t>/ MIDI_INSTRUMENT SP modal_arg midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP entry_name
6284 </t>
6285 <t>/ MIDI_INSTRUMENT SP modal_arg midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP instr_load_mode SP entry_name
6286 </t>
6287 </list>
6288 </t>
6289 <t>unmap_instruction =
6290 <list>
6291 <t>MIDI_INSTRUMENT SP midi_map SP midi_bank SP midi_prog
6292 </t>
6293 </list>
6294 </t>
6295 <t>remove_instruction =
6296 <list>
6297 <t>CHANNEL SP sampler_channel
6298 </t>
6299 <t>/ MIDI_INSTRUMENT_MAP SP midi_map
6300 </t>
6301 <t>/ MIDI_INSTRUMENT_MAP SP ALL
6302 </t>
6303 <t>/ DB_INSTRUMENT_DIRECTORY SP FORCE SP db_path
6304 </t>
6305 <t>/ DB_INSTRUMENT_DIRECTORY SP db_path
6306 </t>
6307 <t>/ DB_INSTRUMENT SP db_path
6308 </t>
6309 </list>
6310 </t>
6311 <t>get_instruction =
6312 <list>
6313 <t>AVAILABLE_ENGINES
6314 </t>
6315 <t>/ AVAILABLE_MIDI_INPUT_DRIVERS
6316 </t>
6317 <t>/ MIDI_INPUT_DRIVER SP INFO SP string
6318 </t>
6319 <t>/ MIDI_INPUT_DRIVER_PARAMETER SP INFO SP string SP string
6320 </t>
6321 <t>/ MIDI_INPUT_DRIVER_PARAMETER SP INFO SP string SP string SP key_val_list
6322 </t>
6323 <t>/ AVAILABLE_AUDIO_OUTPUT_DRIVERS
6324 </t>
6325 <t>/ AUDIO_OUTPUT_DRIVER SP INFO SP string
6326 </t>
6327 <t>/ AUDIO_OUTPUT_DRIVER_PARAMETER SP INFO SP string SP string
6328 </t>
6329 <t>/ AUDIO_OUTPUT_DRIVER_PARAMETER SP INFO SP string SP string SP key_val_list
6330 </t>
6331 <t>/ AUDIO_OUTPUT_DEVICES
6332 </t>
6333 <t>/ MIDI_INPUT_DEVICES
6334 </t>
6335 <t>/ AUDIO_OUTPUT_DEVICE SP INFO SP number
6336 </t>
6337 <t>/ MIDI_INPUT_DEVICE SP INFO SP number
6338 </t>
6339 <t>/ MIDI_INPUT_PORT SP INFO SP number SP number
6340 </t>
6341 <t>/ MIDI_INPUT_PORT_PARAMETER SP INFO SP number SP number SP string
6342 </t>
6343 <t>/ AUDIO_OUTPUT_CHANNEL SP INFO SP number SP number
6344 </t>
6345 <t>/ AUDIO_OUTPUT_CHANNEL_PARAMETER SP INFO SP number SP number SP string
6346 </t>
6347 <t>/ CHANNELS
6348 </t>
6349 <t>/ CHANNEL SP INFO SP sampler_channel
6350 </t>
6351 <t>/ CHANNEL SP BUFFER_FILL SP buffer_size_type SP sampler_channel
6352 </t>
6353 <t>/ CHANNEL SP STREAM_COUNT SP sampler_channel
6354 </t>
6355 <t>/ CHANNEL SP VOICE_COUNT SP sampler_channel
6356 </t>
6357 <t>/ ENGINE SP INFO SP engine_name
6358 </t>
6359 <t>/ SERVER SP INFO
6360 </t>
6361 <t>/ TOTAL_VOICE_COUNT
6362 </t>
6363 <t>/ TOTAL_VOICE_COUNT_MAX
6364 </t>
6365 <t>/ MIDI_INSTRUMENTS SP midi_map
6366 </t>
6367 <t>/ MIDI_INSTRUMENTS SP ALL
6368 </t>
6369 <t>/ MIDI_INSTRUMENT SP INFO SP midi_map SP midi_bank SP midi_prog
6370 </t>
6371 <t>/ MIDI_INSTRUMENT_MAPS
6372 </t>
6373 <t>/ MIDI_INSTRUMENT_MAP SP INFO SP midi_map
6374 </t>
6375 <t>/ FX_SENDS SP sampler_channel
6376 </t>
6377 <t>/ FX_SEND SP INFO SP sampler_channel SP fx_send_id
6378 </t>
6379 <t>/ DB_INSTRUMENT_DIRECTORIES SP RECURSIVE SP db_path
6380 </t>
6381 <t>/ DB_INSTRUMENT_DIRECTORIES SP db_path
6382 </t>
6383 <t>/ DB_INSTRUMENT_DIRECTORY SP INFO SP db_path
6384 </t>
6385 <t>/ DB_INSTRUMENTS SP RECURSIVE SP db_path
6386 </t>
6387 <t>/ DB_INSTRUMENTS SP db_path
6388 </t>
6389 <t>/ DB_INSTRUMENT SP INFO SP db_path
6390 </t>
6391 <t>/ DB_INSTRUMENTS_JOB SP INFO SP number
6392 </t>
6393 <t>/ VOLUME
6394 </t>
6395 </list>
6396 </t>
6397 <t>set_instruction =
6398 <list>
6399 <t>AUDIO_OUTPUT_DEVICE_PARAMETER SP number SP string '=' param_val_list
6400 </t>
6401 <t>/ AUDIO_OUTPUT_CHANNEL_PARAMETER SP number SP number SP string '=' param_val_list
6402 </t>
6403 <t>/ MIDI_INPUT_DEVICE_PARAMETER SP number SP string '=' param_val_list
6404 </t>
6405 <t>/ MIDI_INPUT_PORT_PARAMETER SP number SP number SP string '=' NONE
6406 </t>
6407 <t>/ MIDI_INPUT_PORT_PARAMETER SP number SP number SP string '=' param_val_list
6408 </t>
6409 <t>/ CHANNEL SP set_chan_instruction
6410 </t>
6411 <t>/ MIDI_INSTRUMENT_MAP SP NAME SP midi_map SP map_name
6412 </t>
6413 <t>/ FX_SEND SP NAME SP sampler_channel SP fx_send_id SP fx_send_name
6414 </t>
6415 <t>/ FX_SEND SP AUDIO_OUTPUT_CHANNEL SP sampler_channel SP fx_send_id SP audio_channel_index SP audio_channel_index
6416 </t>
6417 <t>/ FX_SEND SP MIDI_CONTROLLER SP sampler_channel SP fx_send_id SP midi_ctrl
6418 </t>
6419 <t>/ FX_SEND SP LEVEL SP sampler_channel SP fx_send_id SP volume_value
6420 </t>
6421 <t>/ DB_INSTRUMENT_DIRECTORY SP NAME SP db_path SP stringval_escaped
6422 </t>
6423 <t>/ DB_INSTRUMENT_DIRECTORY SP DESCRIPTION SP db_path SP stringval_escaped
6424 </t>
6425 <t>/ DB_INSTRUMENT SP NAME SP db_path SP stringval_escaped
6426 </t>
6427 <t>/ DB_INSTRUMENT SP DESCRIPTION SP db_path SP stringval_escaped
6428 </t>
6429 <t>/ ECHO SP boolean
6430 </t>
6431 <t>/ VOLUME SP volume_value
6432 </t>
6433 </list>
6434 </t>
6435 <t>create_instruction =
6436 <list>
6437 <t>AUDIO_OUTPUT_DEVICE SP string SP key_val_list
6438 </t>
6439 <t>/ AUDIO_OUTPUT_DEVICE SP string
6440 </t>
6441 <t>/ MIDI_INPUT_DEVICE SP string SP key_val_list
6442 </t>
6443 <t>/ MIDI_INPUT_DEVICE SP string
6444 </t>
6445 <t>/ FX_SEND SP sampler_channel SP midi_ctrl
6446 </t>
6447 <t>/ FX_SEND SP sampler_channel SP midi_ctrl SP fx_send_name
6448 </t>
6449 </list>
6450 </t>
6451 <t>reset_instruction =
6452 <list>
6453 <t>CHANNEL SP sampler_channel
6454 </t>
6455 </list>
6456 </t>
6457 <t>clear_instruction =
6458 <list>
6459 <t>MIDI_INSTRUMENTS SP midi_map
6460 </t>
6461 <t>/ MIDI_INSTRUMENTS SP ALL
6462 </t>
6463 </list>
6464 </t>
6465 <t>find_instruction =
6466 <list>
6467 <t>DB_INSTRUMENTS SP NON_RECURSIVE SP db_path SP query_val_list
6468 </t>
6469 <t>/ DB_INSTRUMENTS SP db_path SP query_val_list
6470 </t>
6471 <t>/ DB_INSTRUMENT_DIRECTORIES SP NON_RECURSIVE SP db_path SP query_val_list
6472 </t>
6473 <t>/ DB_INSTRUMENT_DIRECTORIES SP db_path SP query_val_list
6474 </t>
6475 </list>
6476 </t>
6477 <t>move_instruction =
6478 <list>
6479 <t>DB_INSTRUMENT_DIRECTORY SP db_path SP db_path
6480 </t>
6481 <t>/ DB_INSTRUMENT SP db_path SP db_path
6482 </t>
6483 </list>
6484 </t>
6485 <t>copy_instruction =
6486 <list>
6487 <t>DB_INSTRUMENT_DIRECTORY SP db_path SP db_path
6488 </t>
6489 <t>/ DB_INSTRUMENT SP db_path SP db_path
6490 </t>
6491 </list>
6492 </t>
6493 <t>destroy_instruction =
6494 <list>
6495 <t>AUDIO_OUTPUT_DEVICE SP number
6496 </t>
6497 <t>/ MIDI_INPUT_DEVICE SP number
6498 </t>
6499 <t>/ FX_SEND SP sampler_channel SP fx_send_id
6500 </t>
6501 </list>
6502 </t>
6503 <t>load_instruction =
6504 <list>
6505 <t>INSTRUMENT SP load_instr_args
6506 </t>
6507 <t>/ ENGINE SP load_engine_args
6508 </t>
6509 </list>
6510 </t>
6511 <t>set_chan_instruction =
6512 <list>
6513 <t>AUDIO_OUTPUT_DEVICE SP sampler_channel SP device_index
6514 </t>
6515 <t>/ AUDIO_OUTPUT_CHANNEL SP sampler_channel SP audio_channel_index SP audio_channel_index
6516 </t>
6517 <t>/ AUDIO_OUTPUT_TYPE SP sampler_channel SP audio_output_type_name
6518 </t>
6519 <t>/ MIDI_INPUT SP sampler_channel SP device_index SP midi_input_port_index SP midi_input_channel_index
6520 </t>
6521 <t>/ MIDI_INPUT_DEVICE SP sampler_channel SP device_index
6522 </t>
6523 <t>/ MIDI_INPUT_PORT SP sampler_channel SP midi_input_port_index
6524 </t>
6525 <t>/ MIDI_INPUT_CHANNEL SP sampler_channel SP midi_input_channel_index
6526 </t>
6527 <t>/ MIDI_INPUT_TYPE SP sampler_channel SP midi_input_type_name
6528 </t>
6529 <t>/ VOLUME SP sampler_channel SP volume_value
6530 </t>
6531 <t>/ MUTE SP sampler_channel SP boolean
6532 </t>
6533 <t>/ SOLO SP sampler_channel SP boolean
6534 </t>
6535 <t>/ MIDI_INSTRUMENT_MAP SP sampler_channel SP midi_map
6536 </t>
6537 <t>/ MIDI_INSTRUMENT_MAP SP sampler_channel SP NONE
6538 </t>
6539 <t>/ MIDI_INSTRUMENT_MAP SP sampler_channel SP DEFAULT
6540 </t>
6541 </list>
6542 </t>
6543 <t>edit_instruction =
6544 <list>
6545 <t>CHANNEL SP INSTRUMENT SP sampler_channel
6546 </t>
6547 </list>
6548 </t>
6549 <t>format_instruction =
6550 <list>
6551 <t>INSTRUMENTS_DB
6552 </t>
6553 </list>
6554 </t>
6555 <t>modal_arg =
6556 <list>
6557 <t>/* epsilon (empty argument) */
6558 </t>
6559 <t>/ NON_MODAL SP
6560 </t>
6561 </list>
6562 </t>
6563 <t>key_val_list =
6564 <list>
6565 <t>string '=' param_val_list
6566 </t>
6567 <t>/ key_val_list SP string '=' param_val_list
6568 </t>
6569 </list>
6570 </t>
6571 <t>buffer_size_type =
6572 <list>
6573 <t>BYTES
6574 </t>
6575 <t>/ PERCENTAGE
6576 </t>
6577 </list>
6578 </t>
6579 <t>list_instruction =
6580 <list>
6581 <t>AUDIO_OUTPUT_DEVICES
6582 </t>
6583 <t>/ MIDI_INPUT_DEVICES
6584 </t>
6585 <t>/ CHANNELS
6586 </t>
6587 <t>/ AVAILABLE_ENGINES
6588 </t>
6589 <t>/ AVAILABLE_MIDI_INPUT_DRIVERS
6590 </t>
6591 <t>/ AVAILABLE_AUDIO_OUTPUT_DRIVERS
6592 </t>
6593 <t>/ MIDI_INSTRUMENTS SP midi_map
6594 </t>
6595 <t>/ MIDI_INSTRUMENTS SP ALL
6596 </t>
6597 <t>/ MIDI_INSTRUMENT_MAPS
6598 </t>
6599 <t>/ FX_SENDS SP sampler_channel
6600 </t>
6601 <t>/ DB_INSTRUMENT_DIRECTORIES SP RECURSIVE SP db_path
6602 </t>
6603 <t>/ DB_INSTRUMENT_DIRECTORIES SP db_path
6604 </t>
6605 <t>/ DB_INSTRUMENTS SP RECURSIVE SP db_path
6606 </t>
6607 <t>/ DB_INSTRUMENTS SP db_path
6608 </t>
6609 </list>
6610 </t>
6611 <t>load_instr_args =
6612 <list>
6613 <t>filename SP instrument_index SP sampler_channel
6614 </t>
6615 <t>/ NON_MODAL SP filename SP instrument_index SP sampler_channel
6616 </t>
6617 </list>
6618 </t>
6619 <t>load_engine_args =
6620 <list>
6621 <t>engine_name SP sampler_channel
6622 </t>
6623 </list>
6624 </t>
6625 <t>instr_load_mode =
6626 <list>
6627 <t>ON_DEMAND
6628 </t>
6629 <t>/ ON_DEMAND_HOLD
6630 </t>
6631 <t>/ PERSISTENT
6632 </t>
6633 </list>
6634 </t>
6635 <t>device_index =
6636 <list>
6637 <t>number
6638 </t>
6639 </list>
6640 </t>
6641 <t>audio_channel_index =
6642 <list>
6643 <t>number
6644 </t>
6645 </list>
6646 </t>
6647 <t>audio_output_type_name =
6648 <list>
6649 <t>string
6650 </t>
6651 </list>
6652 </t>
6653 <t>midi_input_port_index =
6654 <list>
6655 <t>number
6656 </t>
6657 </list>
6658 </t>
6659 <t>midi_input_channel_index =
6660 <list>
6661 <t>number
6662 </t>
6663 <t>/ ALL
6664 </t>
6665 </list>
6666 </t>
6667 <t>midi_input_type_name =
6668 <list>
6669 <t>string
6670 </t>
6671 </list>
6672 </t>
6673 <t>midi_map =
6674 <list>
6675 <t>number
6676 </t>
6677 </list>
6678 </t>
6679 <t>midi_bank =
6680 <list>
6681 <t>number
6682 </t>
6683 </list>
6684 </t>
6685 <t>midi_prog =
6686 <list>
6687 <t>number
6688 </t>
6689 </list>
6690 </t>
6691 <t>midi_ctrl =
6692 <list>
6693 <t>number
6694 </t>
6695 </list>
6696 </t>
6697 <t>volume_value =
6698 <list>
6699 <t>dotnum
6700 </t>
6701 <t>/ number
6702 </t>
6703 </list>
6704 </t>
6705 <t>sampler_channel =
6706 <list>
6707 <t>number
6708 </t>
6709 </list>
6710 </t>
6711 <t>instrument_index =
6712 <list>
6713 <t>number
6714 </t>
6715 </list>
6716 </t>
6717 <t>fx_send_id =
6718 <list>
6719 <t>number
6720 </t>
6721 </list>
6722 </t>
6723 <t>engine_name =
6724 <list>
6725 <t>string
6726 </t>
6727 </list>
6728 </t>
6729 <t>filename =
6730 <list>
6731 <t>path
6732 </t>
6733 </list>
6734 </t>
6735 <t>db_path =
6736 <list>
6737 <t>path
6738 </t>
6739 </list>
6740 </t>
6741 <t>map_name =
6742 <list>
6743 <t>stringval_escaped
6744 </t>
6745 </list>
6746 </t>
6747 <t>entry_name =
6748 <list>
6749 <t>stringval_escaped
6750 </t>
6751 </list>
6752 </t>
6753 <t>fx_send_name =
6754 <list>
6755 <t>stringval_escaped
6756 </t>
6757 </list>
6758 </t>
6759 <t>param_val_list =
6760 <list>
6761 <t>param_val
6762 </t>
6763 <t>/ param_val_list','param_val
6764 </t>
6765 </list>
6766 </t>
6767
6768 <t>param_val =
6769 <list>
6770 <t>string
6771 </t>
6772 <t>/ stringval
6773 </t>
6774 <t>/ number
6775 </t>
6776 <t>/ dotnum
6777 </t>
6778 </list>
6779 </t>
6780 <t>query_val_list =
6781 <list>
6782 <t>string '=' query_val
6783 </t>
6784 <t>/ query_val_list SP string '=' query_val
6785 </t>
6786 </list>
6787 </t>
6788 <t>query_val =
6789 <list>
6790 <t>text_escaped
6791 </t>
6792 <t>/ stringval_escaped
6793 </t>
6794 </list>
6795 </t>
6796 <t>scan_mode =
6797 <list>
6798 <t>RECURSIVE
6799 </t>
6800 <t>/ NON_RECURSIVE
6801 </t>
6802 <t>/ FLAT
6803 </t>
6804 </list>
6805 </t>
6806
6807 <!-- GRAMMAR_BNF_END - do NOT delete or modify this line !!! -->
6808
6809 <section title="Character Set and Escape Sequences" anchor="character_set">
6810 <t>Older versions of this protocol up to and including v1.1 only
6811 supported the standard ASCII character set (ASCII code 0 - 127)
6812 <xref target="RFC20"/>, all younger versions of this protocol
6813 however support the Extended ASCII character set (ASCII code
6814 0 - 255). The same group of younger protocols also support
6815 escape sequences, but only for certain, explicitly declared
6816 parts of the protocol. The supported escape sequences are
6817 defined as follows:</t>
6818 <texttable>
6819 <ttcol>ASCII Character Sequence</ttcol>
6820 <ttcol>Translated into (Name)</ttcol>
6821 <c>\n</c> <c>new line</c>
6822 <c>\r</c> <c>carriage return</c>
6823 <c>\f</c> <c>form feed</c>
6824 <c>\t</c> <c>horizontal tab</c>
6825 <c>\v</c> <c>vertical tab</c>
6826 <c>\'</c> <c>apostrophe</c>
6827 <c>\"</c> <c>quotation mark</c>
6828 <c>\\</c> <c>backslash</c>
6829 <c>\OOO</c> <c>three digit octal ASCII code of the character</c>
6830 <c>\xHH</c> <c>two digit hex ASCII code of the character</c>
6831 </texttable>
6832 <t>Notice: due to the transition of certain parts of the
6833 protocol which now support escape sequences, a slight backward
6834 incompatibility to protocols version v1.1 and younger has been
6835 introduced. The only difference is that in parts of the protocol
6836 where escape characters are now supported, a backslash characters
6837 MUST be escaped as well (that is as double backslash), whereas
6838 in the old versions a single backslash was sufficient.</t>
6839
6840 <t>The following LSCP commands support escape sequences as part
6841 of their filename / path based arguments and / or may contain
6842 a filename / path with escape sequences in their response:
6843 <list>
6844 <t><xref target="LOAD INSTRUMENT">"LOAD INSTRUMENT"</xref></t>
6845 <t><xref target="GET CHANNEL INFO">"GET CHANNEL INFO"</xref></t>
6846 <t><xref target="MAP MIDI_INSTRUMENT">"MAP MIDI_INSTRUMENT"</xref></t>
6847 <t><xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref></t>
6848 <t><xref target="ADD DB_INSTRUMENT_DIRECTORY">"ADD DB_INSTRUMENT_DIRECTORY"</xref></t>
6849 <t><xref target="ADD DB_INSTRUMENTS">"ADD DB_INSTRUMENTS"</xref></t>
6850 <t><xref target="REMOVE DB_INSTRUMENT_DIRECTORY">"REMOVE DB_INSTRUMENT_DIRECTORY"</xref></t>
6851 <t><xref target="REMOVE DB_INSTRUMENT">"REMOVE DB_INSTRUMENT"</xref></t>
6852 <t><xref target="GET DB_INSTRUMENT_DIRECTORIES">"GET DB_INSTRUMENT_DIRECTORIES"</xref></t>
6853 <t><xref target="LIST DB_INSTRUMENT_DIRECTORIES">"LIST DB_INSTRUMENT_DIRECTORIES"</xref></t>
6854 <t><xref target="GET DB_INSTRUMENT_DIRECTORY INFO">"GET DB_INSTRUMENT_DIRECTORY INFO"</xref></t>
6855 <t><xref target="GET DB_INSTRUMENTS">"GET DB_INSTRUMENTS"</xref></t>
6856 <t><xref target="LIST DB_INSTRUMENTS">"LIST DB_INSTRUMENTS"</xref></t>
6857 <t><xref target="GET DB_INSTRUMENT INFO">"GET DB_INSTRUMENT INFO"</xref></t>
6858 <t><xref target="SET DB_INSTRUMENT_DIRECTORY NAME">"SET DB_INSTRUMENT_DIRECTORY NAME"</xref></t>
6859 <t><xref target="SET DB_INSTRUMENT_DIRECTORY DESCRIPTION">"SET DB_INSTRUMENT_DIRECTORY DESCRIPTION"</xref></t>
6860 <t><xref target="SET DB_INSTRUMENT NAME">"SET DB_INSTRUMENT NAME"</xref></t>
6861 <t><xref target="SET DB_INSTRUMENT DESCRIPTION">"SET DB_INSTRUMENT DESCRIPTION"</xref></t>
6862 <t><xref target="FIND DB_INSTRUMENTS">"FIND DB_INSTRUMENTS"</xref></t>
6863 <t><xref target="FIND DB_INSTRUMENT_DIRECTORIES">"FIND DB_INSTRUMENT_DIRECTORIES"</xref></t>
6864 <t><xref target="MOVE DB_INSTRUMENT">"MOVE DB_INSTRUMENT"</xref></t>
6865 <t><xref target="MOVE DB_INSTRUMENT_DIRECTORY">"MOVE DB_INSTRUMENT_DIRECTORY"</xref></t>
6866 <t><xref target="COPY DB_INSTRUMENT">"COPY DB_INSTRUMENT"</xref></t>
6867 <t><xref target="COPY DB_INSTRUMENT_DIRECTORY">"COPY DB_INSTRUMENT_DIRECTORY"</xref></t>
6868 </list>
6869 Note that the forward slash character ('/') has a special meaning in
6870 filename / path based arguments: it acts as separator of the nodes in
6871 the path, thus if a directory- or filename includes a forward slash
6872 (not intended as path node separator), you MUST escape that slash
6873 either with the respective hex escape sequence ("\x2f") or with the
6874 respective octal escape sequence ("\057").
6875 </t>
6876
6877 <t>
6878 The following LSCP commands even support escape sequences as
6879 part of at least one of their text-based arguments (i.e. entity name,
6880 description) and / or may contain escape sequences in at least one of
6881 their text-based fields in their response:
6882 <list>
6883 <t><xref target="GET SERVER INFO">"GET SERVER INFO"</xref></t>
6884 <t><xref target="GET ENGINE INFO">"GET ENGINE INFO"</xref></t>
6885 <t><xref target="GET CHANNEL INFO">"GET CHANNEL INFO"</xref></t>
6886 <t><xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref></t>
6887 <t><xref target="GET FX_SEND INFO">"GET FX_SEND INFO"</xref></t>
6888 <t><xref target="SET FX_SEND NAME">"SET FX_SEND NAME"</xref></t>
6889 <t><xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref></t>
6890 <t><xref target="GET MIDI_INSTRUMENT_MAP INFO">"GET MIDI_INSTRUMENT_MAP INFO"</xref></t>
6891 <t><xref target="ADD MIDI_INSTRUMENT_MAP">"ADD MIDI_INSTRUMENT_MAP"</xref></t>
6892 <t><xref target="MAP MIDI_INSTRUMENT">"MAP MIDI_INSTRUMENT"</xref></t>
6893 <t><xref target="SET MIDI_INSTRUMENT_MAP NAME">"SET MIDI_INSTRUMENT_MAP NAME"</xref></t>
6894 <t><xref target="GET DB_INSTRUMENT_DIRECTORY INFO">"GET DB_INSTRUMENT_DIRECTORY INFO"</xref></t>
6895 <t><xref target="SET DB_INSTRUMENT_DIRECTORY NAME">"SET DB_INSTRUMENT_DIRECTORY NAME"</xref></t>
6896 <t><xref target="SET DB_INSTRUMENT_DIRECTORY DESCRIPTION">"SET DB_INSTRUMENT_DIRECTORY DESCRIPTION"</xref></t>
6897 <t><xref target="FIND DB_INSTRUMENT_DIRECTORIES">"FIND DB_INSTRUMENT_DIRECTORIES"</xref></t>
6898 <t><xref target="GET DB_INSTRUMENT INFO">"GET DB_INSTRUMENT INFO"</xref></t>
6899 <t><xref target="SET DB_INSTRUMENT NAME">"SET DB_INSTRUMENT NAME"</xref></t>
6900 <t><xref target="SET DB_INSTRUMENT DESCRIPTION">"SET DB_INSTRUMENT DESCRIPTION"</xref></t>
6901 <t><xref target="FIND DB_INSTRUMENTS">"FIND DB_INSTRUMENTS"</xref></t>
6902 </list>
6903 Please note that these lists are manually maintained. If you
6904 find a command that also supports escape sequences we forgot to
6905 mention here, please report it!
6906 </t>
6907 </section>
6908 </section>
6909
6910 <section title="Events" anchor="events">
6911 <t>This chapter will describe all currently defined events supported by LinuxSampler.</t>
6912
6913 <section title="Number of audio output devices changed" anchor="SUBSCRIBE AUDIO_OUTPUT_DEVICE_COUNT">
6914 <t>Client may want to be notified when the total number of audio output devices on the
6915 back-end changes by issuing the following command:</t>
6916 <t>
6917 <list>
6918 <t>SUBSCRIBE AUDIO_OUTPUT_DEVICE_COUNT</t>
6919 </list>
6920 </t>
6921 <t>Server will start sending the following notification messages:</t>
6922 <t>
6923 <list>
6924 <t>"NOTIFY:AUDIO_OUTPUT_DEVICE_COUNT:&lt;devices&gt;"</t>
6925 </list>
6926 </t>
6927 <t>where &lt;devices&gt; will be replaced by the new number
6928 of audio output devices.</t>
6929 </section>
6930
6931 <section title="Audio output device's settings changed" anchor="SUBSCRIBE AUDIO_OUTPUT_DEVICE_INFO">
6932 <t>Client may want to be notified when changes were made to audio output devices on the
6933 back-end by issuing the following command:</t>
6934 <t>
6935 <list>
6936 <t>SUBSCRIBE AUDIO_OUTPUT_DEVICE_INFO</t>
6937 </list>
6938 </t>
6939 <t>Server will start sending the following notification messages:</t>
6940 <t>
6941 <list>
6942 <t>"NOTIFY:AUDIO_OUTPUT_DEVICE_INFO:&lt;device-id&gt;"</t>
6943 </list>
6944 </t>
6945 <t>where &lt;device-id&gt; will be replaced by the numerical ID of the audio output device,
6946 which settings has been changed. The front-end will have to send
6947 the respective command to actually get the audio output device info. Because these messages
6948 will be triggered by LSCP commands issued by other clients rather than real
6949 time events happening on the server, it is believed that an empty notification
6950 message is sufficient here.</t>
6951 </section>
6952
6953 <section title="Number of MIDI input devices changed" anchor="SUBSCRIBE MIDI_INPUT_DEVICE_COUNT">
6954 <t>Client may want to be notified when the total number of MIDI input devices on the
6955 back-end changes by issuing the following command:</t>
6956 <t>
6957 <list>
6958 <t>SUBSCRIBE MIDI_INPUT_DEVICE_COUNT</t>
6959 </list>
6960 </t>
6961 <t>Server will start sending the following notification messages:</t>
6962 <t>
6963 <list>
6964 <t>"NOTIFY:MIDI_INPUT_DEVICE_COUNT:&lt;devices&gt;"</t>
6965 </list>
6966 </t>
6967 <t>where &lt;devices&gt; will be replaced by the new number
6968 of MIDI input devices.</t>
6969 </section>
6970
6971 <section title="MIDI input device's settings changed" anchor="SUBSCRIBE MIDI_INPUT_DEVICE_INFO">
6972 <t>Client may want to be notified when changes were made to MIDI input devices on the
6973 back-end by issuing the following command:</t>
6974 <t>
6975 <list>
6976 <t>SUBSCRIBE MIDI_INPUT_DEVICE_INFO</t>
6977 </list>
6978 </t>
6979 <t>Server will start sending the following notification messages:</t>
6980 <t>
6981 <list>
6982 <t>"NOTIFY:MIDI_INPUT_DEVICE_INFO:&lt;device-id&gt;"</t>
6983 </list>
6984 </t>
6985 <t>where &lt;device-id&gt; will be replaced by the numerical ID of the MIDI input device,
6986 which settings has been changed. The front-end will have to send
6987 the respective command to actually get the MIDI input device info. Because these messages
6988 will be triggered by LSCP commands issued by other clients rather than real
6989 time events happening on the server, it is believed that an empty notification
6990 message is sufficient here.</t>
6991 </section>
6992
6993 <section title="Number of sampler channels changed" anchor="SUBSCRIBE CHANNEL_COUNT">
6994 <t>Client may want to be notified when the total number of channels on the
6995 back-end changes by issuing the following command:</t>
6996 <t>
6997 <list>
6998 <t>SUBSCRIBE CHANNEL_COUNT</t>
6999 </list>
7000 </t>
7001 <t>Server will start sending the following notification messages:</t>
7002 <t>
7003 <list>
7004 <t>"NOTIFY:CHANNEL_COUNT:&lt;channels&gt;"</t>
7005 </list>
7006 </t>
7007 <t>where &lt;channels&gt; will be replaced by the new number
7008 of sampler channels.</t>
7009 </section>
7010
7011 <section title="Number of active voices changed" anchor="SUBSCRIBE VOICE_COUNT">
7012 <t>Client may want to be notified when the number of voices on the
7013 back-end changes by issuing the following command:</t>
7014 <t>
7015 <list>
7016 <t>SUBSCRIBE VOICE_COUNT</t>
7017 </list>
7018 </t>
7019 <t>Server will start sending the following notification messages:</t>
7020 <t>
7021 <list>
7022 <t>"NOTIFY:VOICE_COUNT:&lt;sampler-channel&gt; &lt;voices&gt;"</t>
7023 </list>
7024 </t>
7025 <t>where &lt;sampler-channel&gt; will be replaced by the sampler channel the
7026 voice count change occurred and &lt;voices&gt; by the new number of
7027 active voices on that channel.</t>
7028 </section>
7029
7030 <section title="Number of active disk streams changed" anchor="SUBSCRIBE STREAM_COUNT">
7031 <t>Client may want to be notified when the number of streams on the back-end
7032 changes by issuing the following command: SUBSCRIBE STREAM_COUNT</t>
7033 <t>
7034 <list>
7035 <t>SUBSCRIBE STREAM_COUNT</t>
7036 </list>
7037 </t>
7038 <t>Server will start sending the following notification messages:</t>
7039 <t>
7040 <list>
7041 <t>"NOTIFY:STREAM_COUNT:&lt;sampler-channel&gt; &lt;streams&gt;"</t>
7042 </list>
7043 </t>
7044 <t>where &lt;sampler-channel&gt; will be replaced by the sampler channel the
7045 stream count change occurred and &lt;streams&gt; by the new number of
7046 active disk streams on that channel.</t>
7047 </section>
7048
7049 <section title="Disk stream buffer fill state changed" anchor="SUBSCRIBE BUFFER_FILL">
7050 <t>Client may want to be notified when the buffer fill state of a disk stream
7051 on the back-end changes by issuing the following command:</t>
7052 <t>
7053 <list>
7054 <t>SUBSCRIBE BUFFER_FILL</t>
7055 </list>
7056 </t>
7057 <t>Server will start sending the following notification messages:</t>
7058 <t>
7059 <list>
7060 <t>"NOTIFY:BUFFER_FILL:&lt;sampler-channel&gt; &lt;fill-data&gt;"</t>
7061 </list>
7062 </t>
7063 <t>where &lt;sampler-channel&gt; will be replaced by the sampler channel the
7064 buffer fill state change occurred on and &lt;fill-data&gt; will be replaced by the
7065 buffer fill data for this channel as described in <xref target="GET CHANNEL BUFFER_FILL" />
7066 as if the <xref target="GET CHANNEL BUFFER_FILL">
7067 "GET CHANNEL BUFFER_FILL PERCENTAGE"</xref> command was issued on this channel.</t>
7068 </section>
7069
7070 <section title="Channel information changed" anchor="SUBSCRIBE CHANNEL_INFO">
7071 <t>Client may want to be notified when changes were made to sampler channels on the
7072 back-end by issuing the following command:</t>
7073 <t>
7074 <list>
7075 <t>SUBSCRIBE CHANNEL_INFO</t>
7076 </list>
7077 </t>
7078 <t>Server will start sending the following notification messages:</t>
7079 <t>
7080 <list>
7081 <t>"NOTIFY:CHANNEL_INFO:&lt;sampler-channel&gt;"</t>
7082 </list>
7083 </t>
7084 <t>where &lt;sampler-channel&gt; will be replaced by the sampler channel the
7085 channel info change occurred. The front-end will have to send
7086 the respective command to actually get the channel info. Because these messages
7087 will be triggered by LSCP commands issued by other clients rather than real
7088 time events happening on the server, it is believed that an empty notification
7089 message is sufficient here.</t>
7090 </section>
7091
7092 <section title="Number of effect sends changed" anchor="SUBSCRIBE FX_SEND_COUNT">
7093 <t>Client may want to be notified when the number of effect sends on
7094 a particular sampler channel is changed by issuing the following command:</t>
7095 <t>
7096 <list>
7097 <t>SUBSCRIBE FX_SEND_COUNT</t>
7098 </list>
7099 </t>
7100 <t>Server will start sending the following notification messages:</t>
7101 <t>
7102 <list>
7103 <t>"NOTIFY:FX_SEND_COUNT:&lt;channel-id&gt; &lt;fx-sends&gt;"</t>
7104 </list>
7105 </t>
7106 <t>where &lt;channel-id&gt; will be replaced by the numerical ID of the sampler
7107 channel, on which the effect sends number is changed and &lt;fx-sends&gt; will
7108 be replaced by the new number of effect sends on that channel.</t>
7109 </section>
7110
7111 <section title="Effect send information changed" anchor="SUBSCRIBE FX_SEND_INFO">
7112 <t>Client may want to be notified when changes were made to effect sends on a
7113 a particular sampler channel by issuing the following command:</t>
7114 <t>
7115 <list>
7116 <t>SUBSCRIBE FX_SEND_INFO</t>
7117 </list>
7118 </t>
7119 <t>Server will start sending the following notification messages:</t>
7120 <t>
7121 <list>
7122 <t>"NOTIFY:FX_SEND_INFO:&lt;channel-id&gt; &lt;fx-send-id&gt;"</t>
7123 </list>
7124 </t>
7125 <t>where &lt;channel-id&gt; will be replaced by the numerical ID of the sampler
7126 channel, on which an effect send entity is changed and &lt;fx-send-id&gt; will
7127 be replaced by the numerical ID of the changed effect send.</t>
7128 </section>
7129
7130 <section title="Total number of active voices changed" anchor="SUBSCRIBE TOTAL_VOICE_COUNT">
7131 <t>Client may want to be notified when the total number of voices on the
7132 back-end changes by issuing the following command:</t>
7133 <t>
7134 <list>
7135 <t>SUBSCRIBE TOTAL_VOICE_COUNT</t>
7136 </list>
7137 </t>
7138 <t>Server will start sending the following notification messages:</t>
7139 <t>
7140 <list>
7141 <t>"NOTIFY:TOTAL_VOICE_COUNT:&lt;voices&gt;"</t>
7142 </list>
7143 </t>
7144 <t>where &lt;voices&gt; will be replaced by the new number of
7145 all currently active voices.</t>
7146 </section>
7147
7148 <section title="Number of MIDI instrument maps changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_MAP_COUNT">
7149 <t>Client may want to be notified when the number of MIDI instrument maps on the
7150 back-end changes by issuing the following command:</t>
7151 <t>
7152 <list>
7153 <t>SUBSCRIBE MIDI_INSTRUMENT_MAP_COUNT</t>
7154 </list>
7155 </t>
7156 <t>Server will start sending the following notification messages:</t>
7157 <t>
7158 <list>
7159 <t>"NOTIFY:MIDI_INSTRUMENT_MAP_COUNT:&lt;maps&gt;"</t>
7160 </list>
7161 </t>
7162 <t>where &lt;maps&gt; will be replaced by the new number
7163 of MIDI instrument maps.</t>
7164 </section>
7165
7166 <section title="MIDI instrument map information changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO">
7167 <t>Client may want to be notified when changes were made to MIDI instrument maps on the
7168 back-end by issuing the following command:</t>
7169 <t>
7170 <list>
7171 <t>SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO</t>
7172 </list>
7173 </t>
7174 <t>Server will start sending the following notification messages:</t>
7175 <t>
7176 <list>
7177 <t>"NOTIFY:MIDI_INSTRUMENT_MAP_INFO:&lt;map-id&gt;"</t>
7178 </list>
7179 </t>
7180 <t>where &lt;map-id&gt; will be replaced by the numerical ID of the MIDI instrument map,
7181 for which information changes occurred. The front-end will have to send
7182 the respective command to actually get the MIDI instrument map info. Because these messages
7183 will be triggered by LSCP commands issued by other clients rather than real
7184 time events happening on the server, it is believed that an empty notification
7185 message is sufficient here.</t>
7186 </section>
7187
7188 <section title="Number of MIDI instruments changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_COUNT">
7189 <t>Client may want to be notified when the number of MIDI instrument maps on the
7190 back-end changes by issuing the following command:</t>
7191 <t>
7192 <list>
7193 <t>SUBSCRIBE MIDI_INSTRUMENT_COUNT</t>
7194 </list>
7195 </t>
7196 <t>Server will start sending the following notification messages:</t>
7197 <t>
7198 <list>
7199 <t>"NOTIFY:MIDI_INSTRUMENT_COUNT:&lt;map-id&gt; &lt;instruments&gt;"</t>
7200 </list>
7201 </t>
7202 <t>where &lt;map-id&gt; is the numerical ID of the MIDI instrument map, in which
7203 the nuber of instruments has changed and &lt;instruments&gt; will be replaced by
7204 the new number of MIDI instruments in the specified map.</t>
7205 </section>
7206
7207 <section title="MIDI instrument information changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_INFO">
7208 <t>Client may want to be notified when changes were made to MIDI instruments on the
7209 back-end by issuing the following command:</t>
7210 <t>
7211 <list>
7212 <t>SUBSCRIBE MIDI_INSTRUMENT_INFO</t>
7213 </list>
7214 </t>
7215 <t>Server will start sending the following notification messages:</t>
7216 <t>
7217 <list>
7218 <t>"NOTIFY:MIDI_INSTRUMENT_INFO:&lt;map-id&gt; &lt;bank&gt; &lt;program&gt;"</t>
7219 </list>
7220 </t>
7221 <t>where &lt;map-id&gt; will be replaced by the numerical ID of the MIDI instrument map,
7222 in which a MIDI instrument is changed. &lt;bank&gt; and &lt;program&gt; specifies
7223 the location of the changed MIDI instrument in the map. The front-end will have to send
7224 the respective command to actually get the MIDI instrument info. Because these messages
7225 will be triggered by LSCP commands issued by other clients rather than real
7226 time events happening on the server, it is believed that an empty notification
7227 message is sufficient here.</t>
7228 </section>
7229
7230 <section title="Global settings changed" anchor="SUBSCRIBE GLOBAL_INFO">
7231 <t>Client may want to be notified when changes to the global settings
7232 of the sampler were made by issuing the following command:</t>
7233 <t>
7234 <list>
7235 <t>SUBSCRIBE GLOBAL_INFO</t>
7236 </list>
7237 </t>
7238 <t>Server will start sending the following types of notification messages:</t>
7239 <t>
7240 <list>
7241 <t>"NOTIFY:GLOBAL_INFO:VOLUME &lt;volume&gt;" - Notifies that the
7242 golbal volume of the sampler is changed, where &lt;volume&gt; will be
7243 replaced by the optional dotted floating point value, reflecting the
7244 new global volume parameter.</t>
7245 </list>
7246 </t>
7247 </section>
7248
7249 <section title="Number of database instrument directories changed" anchor="SUBSCRIBE DB_INSTRUMENT_DIRECTORY_COUNT">
7250 <t>Client may want to be notified when the number of instrument
7251 directories in a particular directory in the instruments database
7252 is changed by issuing the following command:</t>
7253 <t>
7254 <list>
7255 <t>SUBSCRIBE DB_INSTRUMENT_DIRECTORY_COUNT</t>
7256 </list>
7257 </t>
7258 <t>Server will start sending the following notification messages:</t>
7259 <t>
7260 <list>
7261 <t>"NOTIFY:DB_INSTRUMENT_DIRECTORY_COUNT:&lt;dir-path&gt;"</t>
7262 </list>
7263 </t>
7264 <t>where &lt;dir-path&gt; will be replaced by the absolute path
7265 name of the directory in the instruments database,
7266 in which the number of directories is changed.</t>
7267 <t>Note that when a non-empty directory is removed, this event
7268 is not sent for the subdirectories in that directory.</t>
7269 </section>
7270
7271 <section title="Database instrument directory information changed" anchor="SUBSCRIBE DB_INSTRUMENT_DIRECTORY_INFO">
7272 <t>Client may want to be notified when changes were made to directories
7273 in the instruments database by issuing the following command:</t>
7274 <t>
7275 <list>
7276 <t>SUBSCRIBE DB_INSTRUMENT_DIRECTORY_INFO</t>
7277 </list>
7278 </t>
7279 <t>Server will start sending the following notification messages:</t>
7280 <t>
7281 <list>
7282 <t>"NOTIFY:DB_INSTRUMENT_DIRECTORY_INFO:&lt;dir-path&gt;"</t>
7283 </list>
7284 </t>
7285 <t>where &lt;dir-path&gt; will be replaced by the absolute path name
7286 of the directory, for which information changes occurred. The front-end will have to send
7287 the respective command to actually get the updated directory info. Because these messages
7288 will be triggered by LSCP commands issued by other clients rather than real
7289 time events happening on the server, it is believed that an empty notification
7290 message is sufficient here.</t>
7291 <t>
7292 <list>
7293 <t>"NOTIFY:DB_INSTRUMENT_DIRECTORY_INFO:NAME &lt;old-dir-path&gt; &lt;new-name&gt;"</t>
7294 </list>
7295 </t>
7296 <t>where &lt;old-dir-path&gt; is the old absolute path name of the directory
7297 (encapsulated into apostrophes), which name is changes and &lt;new-name&gt; is
7298 the new name of the directory, encapsulated into apostrophes.</t>
7299 </section>
7300
7301 <section title="Number of database instruments changed" anchor="SUBSCRIBE DB_INSTRUMENT_COUNT">
7302 <t>Client may want to be notified when the number of instruments
7303 in a particular directory in the instruments database
7304 is changed by issuing the following command:</t>
7305 <t>
7306 <list>
7307 <t>SUBSCRIBE DB_INSTRUMENT_COUNT</t>
7308 </list>
7309 </t>
7310 <t>Server will start sending the following notification messages:</t>
7311 <t>
7312 <list>
7313 <t>"NOTIFY:DB_INSTRUMENT_COUNT:&lt;dir-path&gt;"</t>
7314 </list>
7315 </t>
7316 <t>where &lt;dir-path&gt; will be replaced by the absolute path
7317 name of the directory in the instruments database,
7318 in which the number of instruments is changed.</t>
7319 <t>Note that when a non-empty directory is removed, this event
7320 is not sent for the instruments in that directory.</t>
7321 </section>
7322
7323 <section title="Database instrument information changed" anchor="SUBSCRIBE DB_INSTRUMENT_INFO">
7324 <t>Client may want to be notified when changes were made to instruments
7325 in the instruments database by issuing the following command:</t>
7326 <t>
7327 <list>
7328 <t>SUBSCRIBE DB_INSTRUMENT_INFO</t>
7329 </list>
7330 </t>
7331 <t>Server will start sending the following notification messages:</t>
7332 <t>
7333 <list>
7334 <t>"NOTIFY:DB_INSTRUMENT_INFO:&lt;instr-path&gt;"</t>
7335 </list>
7336 </t>
7337 <t>where &lt;instr-path&gt; will be replaced by the absolute path name
7338 of the instrument, which settings are changed. The front-end will have to send
7339 the respective command to actually get the updated directory info. Because these messages
7340 will be triggered by LSCP commands issued by other clients rather than real
7341 time events happening on the server, it is believed that an empty notification
7342 message is sufficient here.</t>
7343 <t>
7344 <list>
7345 <t>"NOTIFY:DB_INSTRUMENT_INFO:NAME &lt;old-instr-path&gt; &lt;new-name&gt;"</t>
7346 </list>
7347 </t>
7348 <t>where &lt;old-instr-path&gt; is the old absolute path name of the instrument
7349 (encapsulated into apostrophes), which name is changes and &lt;new-name&gt; is
7350 the new name of the instrument, encapsulated into apostrophes.</t>
7351 </section>
7352
7353 <section title="Database job status information changed" anchor="SUBSCRIBE DB_INSTRUMENTS_JOB_INFO">
7354 <t>Client may want to be notified when the status of particular database
7355 instruments job is changed by issuing the following command:</t>
7356 <t>
7357 <list>
7358 <t>SUBSCRIBE DB_INSTRUMENTS_JOB_INFO</t>
7359 </list>
7360 </t>
7361 <t>Server will start sending the following notification messages:</t>
7362 <t>
7363 <list>
7364 <t>"NOTIFY:DB_INSTRUMENTS_JOB_INFO:&lt;job-id&gt;"</t>
7365 </list>
7366 </t>
7367 <t>where &lt;job-id&gt; will be replaced by the numerical ID of the job,
7368 which status is changed. The front-end will have to send the respective
7369 command to actually get the status info. Because these messages
7370 will be triggered by LSCP commands issued by other clients rather than real
7371 time events happening on the server, it is believed that an empty notification
7372 message is sufficient here.</t>
7373 </section>
7374
7375 <section title="Miscellaneous and debugging events" anchor="SUBSCRIBE MISCELLANEOUS">
7376 <t>Client may want to be notified of miscellaneous and debugging events occurring at
7377 the server by issuing the following command:</t>
7378 <t>
7379 <list>
7380 <t>SUBSCRIBE MISCELLANEOUS</t>
7381 </list>
7382 </t>
7383 <t>Server will start sending the following notification messages:</t>
7384 <t>
7385 <list>
7386 <t>"NOTIFY:MISCELLANEOUS:&lt;string&gt;"</t>
7387 </list>
7388 </t>
7389 <t>where &lt;string&gt; will be replaced by whatever data server
7390 wants to send to the client. Client MAY display this data to the
7391 user AS IS to facilitate debugging.</t>
7392 </section>
7393 </section>
7394
7395 <section title="Security Considerations">
7396 <t>As there is so far no method of authentication and authorization
7397 defined and so not required for a client applications to succeed to
7398 connect, running LinuxSampler might be a security risk for the host
7399 system the LinuxSampler instance is running on.</t>
7400 </section>
7401
7402 <section title="Acknowledgments">
7403 <t>This document has benefited greatly from the comments of the
7404 following people, discussed on the LinuxSampler developer's mailing
7405 list:</t>
7406 <t>
7407 <list>
7408 <t>Rui Nuno Capela</t>
7409 <t>Vladimir Senkov</t>
7410 <t>Mark Knecht</t>
7411 <t>Grigor Iliev</t>
7412 </list>
7413 </t>
7414 </section>
7415
7416 </middle>
7417
7418 <back>
7419 <references>
7420 <reference anchor="RFC2119">
7421 <front>
7422 <title>Key words for use in RFCs to Indicate Requirement Levels</title>
7423 <author initials="S." surname="Bradner" fullname="Scott Bradner">
7424 <organization>Harvard University</organization>
7425 </author>
7426 <date year="1997"></date>
7427 </front>
7428 <seriesInfo name="RFC" value="2119" />
7429 </reference>
7430 <reference anchor="RFC793">
7431 <front>
7432 <title>TRANSMISSION CONTROL PROTOCOL</title>
7433 <author>
7434 <organization>Defense Advanced Research Projects Agency</organization>
7435 </author>
7436 <date year="1981"></date>
7437 </front>
7438 <seriesInfo name="RFC" value="793" />
7439 </reference>
7440 <reference anchor="RFC2234">
7441 <front>
7442 <title>Augmented BNF for Syntax Specifications</title>
7443 <author initials="D.H." surname="Crocker" fullname="David H. Crocker">
7444 <organization>Internet Mail Consortium</organization>
7445 </author>
7446 <author initials="P." surname="Overell" fullname="Paul Overell">
7447 <organization>Demon Internet Ltd</organization>
7448 </author>
7449 <date year="1997"></date>
7450 </front>
7451 <seriesInfo name="RFC" value="2234" />
7452 </reference>
7453 <reference anchor="RFC20">
7454 <front>
7455 <title>ASCII format for Network Interchange</title>
7456 <author>
7457 <organization>UCLA</organization>
7458 </author>
7459 <date year="1969"></date>
7460 </front>
7461 <seriesInfo name="RFC" value="20" />
7462 </reference>
7463 </references>
7464 </back>
7465
7466 </rfc>

  ViewVC Help
Powered by ViewVC