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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1389 - (show annotations) (download) (as text)
Sun Oct 7 14:05:04 2007 UTC (13 years, 2 months ago) by schoenebeck
File MIME type: text/xml
File size: 375812 byte(s)
* the following LSCP commands now also support escape sequences for at
  least one of their text-based arguments (i.e. name, description):
  "ADD MIDI_INSTRUMENT_MAP", "SET MIDI_INSTRUMENT_MAP NAME",
  "SET FX_SEND NAME", "CREATE FX_SEND"
* the LSCP spec doc now lists all LSCP commands which support escape
  sequences as one of their arguments

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</t>
2447 </list>
2448 </t>
2449 <t>VERSION -
2450 <list>
2451 <t>arbitrary character string regarding the engine's version</t>
2452 </list>
2453 </t>
2454 </list>
2455 </t>
2456 </list>
2457 </t>
2458
2459 <t>The mentioned fields above don't have to be in particular order.</t>
2460
2461 <t>Example:</t>
2462 <t>
2463 <list>
2464 <t>C: "GET ENGINE INFO JoesCustomEngine"</t>
2465 <t>S: "DESCRIPTION: this is Joe's custom sampler engine"</t>
2466 <t>&nbsp;&nbsp;&nbsp;"VERSION: testing-1.0"</t>
2467 <t>&nbsp;&nbsp;&nbsp;"."</t>
2468 </list>
2469 </t>
2470 </section>
2471
2472 <section title="Getting sampler channel information" anchor="GET CHANNEL INFO">
2473 <t>The front-end can ask for the current settings of a sampler channel
2474 by sending the following command:</t>
2475 <t>
2476 <list>
2477 <t>GET CHANNEL INFO &lt;sampler-channel&gt;</t>
2478 </list>
2479 </t>
2480 <t>Where &lt;sampler-channel&gt; is the sampler channel number the front-end is interested in
2481 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2482 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t>
2483 <t>Possible Answers:</t>
2484 <t>
2485 <list>
2486 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
2487 Each answer line begins with the settings category name
2488 followed by a colon and then a space character &lt;SP&gt; and finally
2489 the info character string to that setting category. At the
2490 moment the following categories are defined:</t>
2491
2492 <t>
2493 <list>
2494 <t>ENGINE_NAME -
2495 <list>
2496 <t>name of the engine that is associated with the sampler
2497 channel, "NONE" if there's no engine associated yet for
2498 this sampler channel</t>
2499 </list>
2500 </t>
2501 <t>AUDIO_OUTPUT_DEVICE -
2502 <list>
2503 <t>numerical ID of the audio output device which is
2504 currently connected to this sampler channel to output
2505 the audio signal, "NONE" if there's no device
2506 connected to this sampler channel</t>
2507 </list>
2508 </t>
2509 <t>AUDIO_OUTPUT_CHANNELS -
2510 <list>
2511 <t>number of output channels the sampler channel offers
2512 (dependent to used sampler engine and loaded instrument)</t>
2513 </list>
2514 </t>
2515 <t>AUDIO_OUTPUT_ROUTING -
2516 <list>
2517 <t>comma separated list which reflects to which audio
2518 channel of the selected audio output device each
2519 sampler output channel is routed to, e.g. "0,3" would
2520 mean the engine's output channel 0 is routed to channel
2521 0 of the audio output device and the engine's output
2522 channel 1 is routed to the channel 3 of the audio
2523 output device</t>
2524 </list>
2525 </t>
2526 <t>INSTRUMENT_FILE -
2527 <list>
2528 <t>the file name of the loaded instrument, "NONE" if
2529 there's no instrument yet loaded for this sampler
2530 channel</t>
2531 </list>
2532 </t>
2533 <t>INSTRUMENT_NR -
2534 <list>
2535 <t>the instrument index number of the loaded instrument</t>
2536 </list>
2537 </t>
2538 <t>INSTRUMENT_NAME -
2539 <list>
2540 <t>the instrument name of the loaded instrument</t>
2541 </list>
2542 </t>
2543 <t>INSTRUMENT_STATUS -
2544 <list>
2545 <t>integer values 0 to 100 indicating loading progress percentage for the instrument. Negative
2546 value indicates a loading exception. Value of 100 indicates that the instrument is fully
2547 loaded.</t>
2548 </list>
2549 </t>
2550 <t>MIDI_INPUT_DEVICE -
2551 <list>
2552 <t>numerical ID of the MIDI input device which is
2553 currently connected to this sampler channel to deliver
2554 MIDI input commands, "NONE" if there's no device
2555 connected to this sampler channel</t>
2556 </list>
2557 </t>
2558 <t>MIDI_INPUT_PORT -
2559 <list>
2560 <t>port number of the MIDI input device</t>
2561 </list>
2562 </t>
2563 <t>MIDI_INPUT_CHANNEL -
2564 <list>
2565 <t>the MIDI input channel number this sampler channel
2566 should listen to or "ALL" to listen on all MIDI channels</t>
2567 </list>
2568 </t>
2569 <t>VOLUME -
2570 <list>
2571 <t>optionally dotted number for the channel volume factor
2572 (where a value &lt; 1.0 means attenuation and a value >
2573 1.0 means amplification)</t>
2574 </list>
2575 </t>
2576 <t>MUTE -
2577 <list>
2578 <t>Determines whether the channel is muted, "true" if the
2579 channel is muted, "false" if the channel is not muted, and
2580 "MUTED_BY_SOLO" if the channel is muted because of the
2581 presence of a solo channel and will be unmuted when
2582 there are no solo channels left</t>
2583 </list>
2584 </t>
2585 <t>SOLO -
2586 <list>
2587 <t>Determines whether this is a solo channel, "true" if
2588 the channel is a solo channel; "false" otherwise</t>
2589 </list>
2590 </t>
2591 <t>MIDI_INSTRUMENT_MAP -
2592 <list>
2593 <t>Determines to which MIDI instrument map this sampler
2594 channel is assigned to. Read chapter
2595 <xref target="SET CHANNEL MIDI_INSTRUMENT_MAP">"SET CHANNEL MIDI_INSTRUMENT_MAP"</xref>
2596 for a list of possible values.</t>
2597 </list>
2598 </t>
2599 </list>
2600 </t>
2601 </list>
2602 </t>
2603 <t>The mentioned fields above don't have to be in particular order.</t>
2604
2605 <t>Example:</t>
2606 <t>
2607 <list>
2608 <t>C: "GET CHANNEL INFO 34"</t>
2609 <t>S: "ENGINE_NAME: GigEngine"</t>
2610 <t>&nbsp;&nbsp;&nbsp;"VOLUME: 1.0"</t>
2611 <t>&nbsp;&nbsp;&nbsp;"AUDIO_OUTPUT_DEVICE: 0"</t>
2612 <t>&nbsp;&nbsp;&nbsp;"AUDIO_OUTPUT_CHANNELS: 2"</t>
2613 <t>&nbsp;&nbsp;&nbsp;"AUDIO_OUTPUT_ROUTING: 0,1"</t>
2614 <t>&nbsp;&nbsp;&nbsp;"INSTRUMENT_FILE: /home/joe/FazioliPiano.gig"</t>
2615 <t>&nbsp;&nbsp;&nbsp;"INSTRUMENT_NR: 0"</t>
2616 <t>&nbsp;&nbsp;&nbsp;"INSTRUMENT_NAME: Fazioli Piano"</t>
2617 <t>&nbsp;&nbsp;&nbsp;"INSTRUMENT_STATUS: 100"</t>
2618 <t>&nbsp;&nbsp;&nbsp;"MIDI_INPUT_DEVICE: 0"</t>
2619 <t>&nbsp;&nbsp;&nbsp;"MIDI_INPUT_PORT: 0"</t>
2620 <t>&nbsp;&nbsp;&nbsp;"MIDI_INPUT_CHANNEL: 5"</t>
2621 <t>&nbsp;&nbsp;&nbsp;"VOLUME: 1.0"</t>
2622 <t>&nbsp;&nbsp;&nbsp;"MUTE: false"</t>
2623 <t>&nbsp;&nbsp;&nbsp;"SOLO: false"</t>
2624 <t>&nbsp;&nbsp;&nbsp;"MIDI_INSTRUMENT_MAP: NONE"</t>
2625 <t>&nbsp;&nbsp;&nbsp;"."</t>
2626 </list>
2627 </t>
2628 </section>
2629
2630 <section title="Current number of active voices" anchor="GET CHANNEL VOICE_COUNT">
2631 <t>The front-end can ask for the current number of active voices on a
2632 sampler channel by sending the following command:</t>
2633 <t>
2634 <list>
2635 <t>GET CHANNEL VOICE_COUNT &lt;sampler-channel&gt;</t>
2636 </list>
2637 </t>
2638 <t>Where &lt;sampler-channel&gt; is the sampler channel number the front-end is interested in
2639 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2640 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t>
2641
2642 <t>Possible Answers:</t>
2643 <t>
2644 <list>
2645 <t>LinuxSampler will answer by returning the number of active
2646 voices on that channel.</t>
2647 </list>
2648 </t>
2649 <t>Example:</t>
2650 <t>
2651 <list>
2652 <t></t>
2653 </list>
2654 </t>
2655 </section>
2656
2657 <section title="Current number of active disk streams" anchor="GET CHANNEL STREAM_COUNT">
2658 <t>The front-end can ask for the current number of active disk streams
2659 on a sampler channel by sending the following command:</t>
2660 <t>
2661 <list>
2662 <t>GET CHANNEL STREAM_COUNT &lt;sampler-channel&gt;</t>
2663 </list>
2664 </t>
2665 <t>Where &lt;sampler-channel&gt; is the sampler channel number the front-end is interested in
2666 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2667 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t>
2668
2669 <t>Possible Answers:</t>
2670 <t>
2671 <list>
2672 <t>LinuxSampler will answer by returning the number of active
2673 disk streams on that channel in case the engine supports disk
2674 streaming, if the engine doesn't support disk streaming it will
2675 return "NA" for not available.</t>
2676 </list>
2677 </t>
2678 <t>Example:</t>
2679 <t>
2680 <list>
2681 <t></t>
2682 </list>
2683 </t>
2684 </section>
2685
2686 <section title="Current fill state of disk stream buffers" anchor="GET CHANNEL BUFFER_FILL">
2687 <t>The front-end can ask for the current fill state of all disk streams
2688 on a sampler channel by sending the following command:</t>
2689 <t>
2690 <list>
2691 <t>GET CHANNEL BUFFER_FILL BYTES &lt;sampler-channel&gt;</t>
2692 </list>
2693 </t>
2694 <t>to get the fill state in bytes or</t>
2695 <t>
2696 <list>
2697 <t>GET CHANNEL BUFFER_FILL PERCENTAGE &lt;sampler-channel&gt;</t>
2698 </list>
2699 </t>
2700 <t>to get the fill state in percent, where &lt;sampler-channel&gt; is the
2701 sampler channel number the front-end is interested in
2702 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2703 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t>
2704
2705 <t>Possible Answers:</t>
2706 <t>
2707 <list>
2708 <t>LinuxSampler will either answer by returning a comma separated
2709 string with the fill state of all disk stream buffers on that
2710 channel or an empty line if there are no active disk streams or
2711 "NA" for *not available* in case the engine which is deployed
2712 doesn't support disk streaming. Each entry in the answer list
2713 will begin with the stream's ID in brackets followed by the
2714 numerical representation of the fill size (either in bytes or
2715 percentage). Note: due to efficiency reasons the fill states in
2716 the response are not in particular order, thus the front-end has
2717 to sort them by itself if necessary.</t>
2718 </list>
2719 </t>
2720 <t>Examples:</t>
2721 <t>
2722 <list>
2723 <t>C: "GET CHANNEL BUFFER_FILL BYTES 4"</t>
2724 <t>S: "[115]420500,[116]510300,[75]110000,[120]230700"</t>
2725 </list>
2726
2727 <list>
2728 <t>C: "GET CHANNEL BUFFER_FILL PERCENTAGE 4"</t>
2729 <t>S: "[115]90%,[116]98%,[75]40%,[120]62%"</t>
2730 </list>
2731
2732 <list>
2733 <t>C: "GET CHANNEL BUFFER_FILL PERCENTAGE 4"</t>
2734 <t>S: ""</t>
2735 </list>
2736 </t>
2737 </section>
2738
2739 <section title="Setting audio output device" anchor="SET CHANNEL AUDIO_OUTPUT_DEVICE">
2740 <t>The front-end can set the audio output device on a specific sampler
2741 channel by sending the following command:</t>
2742 <t>
2743 <list>
2744 <t>SET CHANNEL AUDIO_OUTPUT_DEVICE &lt;sampler-channel&gt; &lt;audio-device-id&gt;</t>
2745 </list>
2746 </t>
2747 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
2748 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2749 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and
2750 &lt;audio-device-id&gt; is the numerical ID of the audio output device as given by the
2751 <xref target="CREATE AUDIO_OUTPUT_DEVICE">"CREATE AUDIO_OUTPUT_DEVICE"</xref>
2752 or <xref target="LIST AUDIO_OUTPUT_DEVICES">"LIST AUDIO_OUTPUT_DEVICES"</xref>
2753 command.</t>
2754
2755 <t>Possible Answers:</t>
2756 <t>
2757 <list>
2758 <t>"OK" -
2759 <list>
2760 <t>on success</t>
2761 </list>
2762 </t>
2763 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2764 <list>
2765 <t>if audio output device was set, but there are noteworthy
2766 issue(s) related, providing an appropriate warning code and
2767 warning message</t>
2768 </list>
2769 </t>
2770 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2771 <list>
2772 <t>in case it failed, providing an appropriate error code and error message</t>
2773 </list>
2774 </t>
2775 </list>
2776 </t>
2777 <t>Examples:</t>
2778 <t>
2779 <list>
2780 <t></t>
2781 </list>
2782 </t>
2783 </section>
2784
2785 <section title="Setting audio output type" anchor="SET CHANNEL AUDIO_OUTPUT_TYPE">
2786 <t>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!</t>
2787
2788 <t>The front-end can alter the audio output type on a specific sampler
2789 channel by sending the following command:</t>
2790 <t>
2791 <list>
2792 <t>SET CHANNEL AUDIO_OUTPUT_TYPE &lt;sampler-channel&gt; &lt;audio-output-type&gt;</t>
2793 </list>
2794 </t>
2795 <t>Where &lt;audio-output-type&gt; is currently either "ALSA" or "JACK" and
2796 &lt;sampler-channel&gt; is the respective sampler channel number.</t>
2797
2798 <t>Possible Answers:</t>
2799 <t>
2800 <list>
2801 <t>"OK" -
2802 <list>
2803 <t>on success</t>
2804 </list>
2805 </t>
2806 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2807 <list>
2808 <t>if audio output type was set, but there are noteworthy
2809 issue(s) related, providing an appropriate warning code and
2810 warning message</t>
2811 </list>
2812 </t>
2813 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2814 <list>
2815 <t>in case it failed, providing an appropriate error code and error message</t>
2816 </list>
2817 </t>
2818 </list>
2819 </t>
2820 <t>Examples:</t>
2821 <t>
2822 <list>
2823 <t></t>
2824 </list>
2825 </t>
2826 </section>
2827
2828 <section title="Setting audio output channel" anchor="SET CHANNEL AUDIO_OUTPUT_CHANNEL">
2829 <t>The front-end can alter the audio output channel on a specific
2830 sampler channel by sending the following command:</t>
2831 <t>
2832 <list>
2833 <t>SET CHANNEL AUDIO_OUTPUT_CHANNEL &lt;sampler-chan&gt; &lt;audio-out&gt; &lt;audio-in&gt;</t>
2834 </list>
2835 </t>
2836 <t>Where &lt;sampler-chan&gt; is the sampler channel number
2837 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2838 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, &lt;audio-out&gt; is the
2839 numerical ID of the sampler channel's audio output channel which should be
2840 rerouted and &lt;audio-in&gt; is the numerical ID of the audio channel of the selected audio
2841 output device where &lt;audio-out&gt; should be routed to.</t>
2842
2843 <t>Possible Answers:</t>
2844 <t>
2845 <list>
2846 <t>"OK" -
2847 <list>
2848 <t>on success</t>
2849 </list>
2850 </t>
2851 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2852 <list>
2853 <t>if audio output channel was set, but there are noteworthy
2854 issue(s) related, providing an appropriate warning code and
2855 warning message</t>
2856 </list>
2857 </t>
2858 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2859 <list>
2860 <t>in case it failed, providing an appropriate error code and error message</t>
2861 </list>
2862 </t>
2863 </list>
2864 </t>
2865 <t>Examples:</t>
2866 <t>
2867 <list>
2868 <t></t>
2869 </list>
2870 </t>
2871 </section>
2872
2873 <section title="Setting MIDI input device" anchor="SET CHANNEL MIDI_INPUT_DEVICE">
2874 <t>The front-end can set the MIDI input device on a specific sampler
2875 channel by sending the following command:</t>
2876 <t>
2877 <list>
2878 <t>SET CHANNEL MIDI_INPUT_DEVICE &lt;sampler-channel&gt; &lt;midi-device-id&gt;</t>
2879 </list>
2880 </t>
2881 <t>Where &lt;sampler-channel&gt; is the sampler channel number
2882 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
2883 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command
2884 and &lt;midi-device-id&gt; is the numerical ID of the MIDI input device as returned by the
2885 <xref target="CREATE MIDI_INPUT_DEVICE">"CREATE MIDI_INPUT_DEVICE"</xref>
2886 or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref> command.</t>
2887
2888 <t>Possible Answers:</t>
2889 <t>
2890 <list>
2891 <t>"OK" -
2892 <list>
2893 <t>on success</t>
2894 </list>
2895 </t>
2896 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2897 <list>
2898 <t>if MIDI input device was set, but there are noteworthy
2899 issue(s) related, providing an appropriate warning code and
2900 warning message</t>
2901 </list>
2902 </t>
2903 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2904 <list>
2905 <t>in case it failed, providing an appropriate error code and error message</t>
2906 </list>
2907 </t>
2908 </list>
2909 </t>
2910 <t>Examples:</t>
2911 <t>
2912 <list>
2913 <t></t>
2914 </list>
2915 </t>
2916 </section>
2917
2918 <section title="Setting MIDI input type" anchor="SET CHANNEL MIDI_INPUT_TYPE">
2919 <t>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!</t>
2920
2921 <t>The front-end can alter the MIDI input type on a specific sampler
2922 channel by sending the following command:</t>
2923 <t>
2924 <list>
2925 <t>SET CHANNEL MIDI_INPUT_TYPE &lt;sampler-channel&gt; &lt;midi-input-type&gt;</t>
2926 </list>
2927 </t>
2928 <t>Where &lt;midi-input-type&gt; is currently only "ALSA" and
2929 &lt;sampler-channel&gt; is the respective sampler channel number.</t>
2930
2931 <t>Possible Answers:</t>
2932 <t>
2933 <list>
2934 <t>"OK" -
2935 <list>
2936 <t>on success</t>
2937 </list>
2938 </t>
2939 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2940 <list>
2941 <t>if MIDI input type was set, but there are noteworthy
2942 issue(s) related, providing an appropriate warning code and
2943 warning message</t>
2944 </list>
2945 </t>
2946 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2947 <list>
2948 <t>in case it failed, providing an appropriate error code and error message</t>
2949 </list>
2950 </t>
2951 </list>
2952 </t>
2953 <t>Examples:</t>
2954 <t>
2955 <list>
2956 <t></t>
2957 </list>
2958 </t>
2959 </section>
2960
2961 <section title="Setting MIDI input port" anchor="SET CHANNEL MIDI_INPUT_PORT">
2962 <t>The front-end can alter the MIDI input port on a specific sampler
2963 channel by sending the following command:</t>
2964 <t>
2965 <list>
2966 <t>SET CHANNEL MIDI_INPUT_PORT &lt;sampler-channel&gt; &lt;midi-input-port&gt;</t>
2967 </list>
2968 </t>
2969 <t>Where &lt;midi-input-port&gt; is a MIDI input port number of the
2970 MIDI input device connected to the sampler channel given by
2971 &lt;sampler-channel&gt;.</t>
2972
2973 <t>Possible Answers:</t>
2974 <t>
2975 <list>
2976 <t>"OK" -
2977 <list>
2978 <t>on success</t>
2979 </list>
2980 </t>
2981 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
2982 <list>
2983 <t>if MIDI input port was set, but there are noteworthy
2984 issue(s) related, providing an appropriate warning code and
2985 warning message</t>
2986 </list>
2987 </t>
2988 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
2989 <list>
2990 <t>in case it failed, providing an appropriate error code and error message</t>
2991 </list>
2992 </t>
2993 </list>
2994 </t>
2995 <t>Examples:</t>
2996 <t>
2997 <list>
2998 <t></t>
2999 </list>
3000 </t>
3001 </section>
3002
3003 <section title="Setting MIDI input channel" anchor="SET CHANNEL MIDI_INPUT_CHANNEL">
3004 <t>The front-end can alter the MIDI channel a sampler channel should
3005 listen to by sending the following command:</t>
3006 <t>
3007 <list>
3008 <t>SET CHANNEL MIDI_INPUT_CHANNEL &lt;sampler-channel&gt; &lt;midi-input-chan&gt;</t>
3009 </list>
3010 </t>
3011 <t>Where &lt;midi-input-chan&gt; is the number of the new MIDI input channel where
3012 &lt;sampler-channel&gt; should listen to or "ALL" to listen on all 16 MIDI
3013 channels.</t>
3014
3015 <t>Possible Answers:</t>
3016 <t>
3017 <list>
3018 <t>"OK" -
3019 <list>
3020 <t>on success</t>
3021 </list>
3022 </t>
3023 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3024 <list>
3025 <t>if MIDI input channel was set, but there are noteworthy
3026 issue(s) related, providing an appropriate warning code and
3027 warning message</t>
3028 </list>
3029 </t>
3030 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3031 <list>
3032 <t>in case it failed, providing an appropriate error code and error message</t>
3033 </list>
3034 </t>
3035 </list>
3036 </t>
3037 <t>Examples:</t>
3038 <t>
3039 <list>
3040 <t></t>
3041 </list>
3042 </t>
3043 </section>
3044
3045 <section title="Setting channel volume" anchor="SET CHANNEL VOLUME">
3046 <t>The front-end can alter the volume of a sampler channel by sending
3047 the following command:</t>
3048 <t>
3049 <list>
3050 <t>SET CHANNEL VOLUME &lt;sampler-channel&gt; &lt;volume&gt;</t>
3051 </list>
3052 </t>
3053 <t>Where &lt;volume&gt; is an optionally dotted positive number (a value
3054 smaller than 1.0 means attenuation, whereas a value greater than
3055 1.0 means amplification) and &lt;sampler-channel&gt; defines the sampler
3056 channel where this volume factor should be set.</t>
3057
3058 <t>Possible Answers:</t>
3059 <t>
3060 <list>
3061 <t>"OK" -
3062 <list>
3063 <t>on success</t>
3064 </list>
3065 </t>
3066 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3067 <list>
3068 <t>if channel volume was set, but there are noteworthy
3069 issue(s) related, providing an appropriate warning code and
3070 warning message</t>
3071 </list>
3072 </t>
3073 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3074 <list>
3075 <t>in case it failed, providing an appropriate error code and error message</t>
3076 </list>
3077 </t>
3078 </list>
3079 </t>
3080 <t>Examples:</t>
3081 <t>
3082 <list>
3083 <t></t>
3084 </list>
3085 </t>
3086 </section>
3087
3088 <section title="Muting a sampler channel" anchor="SET CHANNEL MUTE">
3089 <t>The front-end can mute/unmute a specific sampler
3090 channel by sending the following command:</t>
3091 <t>
3092 <list>
3093 <t>SET CHANNEL MUTE &lt;sampler-channel&gt; &lt;mute&gt;</t>
3094 </list>
3095 </t>
3096 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3097 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3098 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and
3099 &lt;mute&gt; should be replaced either by "1" to mute the channel or "0"
3100 to unmute the channel.</t>
3101
3102 <t>Possible Answers:</t>
3103 <t>
3104 <list>
3105 <t>"OK" -
3106 <list>
3107 <t>on success</t>
3108 </list>
3109 </t>
3110 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3111 <list>
3112 <t>if the channel was muted/unmuted, but there are noteworthy
3113 issue(s) related, providing an appropriate warning code and
3114 warning message</t>
3115 </list>
3116 </t>
3117 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3118 <list>
3119 <t>in case it failed, providing an appropriate error code and error message</t>
3120 </list>
3121 </t>
3122 </list>
3123 </t>
3124 <t>Examples:</t>
3125 <t>
3126 <list>
3127 <t></t>
3128 </list>
3129 </t>
3130 </section>
3131
3132 <section title="Soloing a sampler channel" anchor="SET CHANNEL SOLO">
3133 <t>The front-end can solo/unsolo a specific sampler channel
3134 by sending the following command:</t>
3135 <t>
3136 <list>
3137 <t>SET CHANNEL SOLO &lt;sampler-channel&gt; &lt;solo&gt;</t>
3138 </list>
3139 </t>
3140 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3141 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3142 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and
3143 &lt;solo&gt; should be replaced either by "1" to solo the channel or "0"
3144 to unsolo the channel.</t>
3145
3146 <t>Possible Answers:</t>
3147 <t>
3148 <list>
3149 <t>"OK" -
3150 <list>
3151 <t>on success</t>
3152 </list>
3153 </t>
3154 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3155 <list>
3156 <t>if the channel was soloed/unsoloed, but there are noteworthy
3157 issue(s) related, providing an appropriate warning code and
3158 warning message</t>
3159 </list>
3160 </t>
3161 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3162 <list>
3163 <t>in case it failed, providing an appropriate error code and error message</t>
3164 </list>
3165 </t>
3166 </list>
3167 </t>
3168 <t>Examples:</t>
3169 <t>
3170 <list>
3171 <t></t>
3172 </list>
3173 </t>
3174 </section>
3175
3176 <section title="Assigning a MIDI instrument map to a sampler channel" anchor="SET CHANNEL MIDI_INSTRUMENT_MAP">
3177 <t>The front-end can assign a MIDI instrument map to a specific sampler channel
3178 by sending the following command:</t>
3179 <t>
3180 <list>
3181 <t>SET CHANNEL MIDI_INSTRUMENT_MAP &lt;sampler-channel&gt; &lt;map&gt;</t>
3182 </list>
3183 </t>
3184 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3185 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3186 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and
3187 &lt;map&gt; can have the following possibilites:</t>
3188 <t>
3189 <list>
3190 <t>"NONE" -
3191 <list>
3192 <t>This is the default setting. In this case
3193 the sampler channel is not assigned any MIDI
3194 instrument map and thus will ignore all MIDI
3195 program change messages.</t>
3196 </list>
3197 </t>
3198 <t>"DEFAULT" -
3199 <list>
3200 <t>The sampler channel will always use the
3201 default MIDI instrument map to handle MIDI
3202 program change messages.</t>
3203 </list>
3204 </t>
3205 <t>numeric ID -
3206 <list>
3207 <t>You can assign a specific MIDI instrument map
3208 by replacing &lt;map&gt; with the respective numeric
3209 ID of the MIDI instrument map as returned by the
3210 <xref target="LIST MIDI_INSTRUMENT_MAPS">"LIST MIDI_INSTRUMENT_MAPS"</xref>
3211 command. Once that map will be deleted, the sampler
3212 channel would fall back to "NONE".</t>
3213 </list>
3214 </t>
3215 </list>
3216 </t>
3217 <t>Read chapter <xref target="MIDI Instrument Mapping">"MIDI Instrument Mapping"</xref>
3218 for details regarding MIDI instrument mapping.</t>
3219
3220 <t>Possible Answers:</t>
3221 <t>
3222 <list>
3223 <t>"OK" -
3224 <list>
3225 <t>on success</t>
3226 </list>
3227 </t>
3228 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3229 <list>
3230 <t>in case it failed, providing an appropriate error code and error message</t>
3231 </list>
3232 </t>
3233 </list>
3234 </t>
3235
3236 <t>Examples:</t>
3237 <t>
3238 <list>
3239 <t></t>
3240 </list>
3241 </t>
3242 </section>
3243
3244 <section title="Adding an effect send to a sampler channel" anchor="CREATE FX_SEND">
3245 <t>The front-end can create an additional effect send on a specific sampler channel
3246 by sending the following command:</t>
3247 <t>
3248 <list>
3249 <t>CREATE FX_SEND &lt;sampler-channel&gt; &lt;midi-ctrl&gt; [&lt;name&gt;]</t>
3250 </list>
3251 </t>
3252 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3253 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3254 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, that is the
3255 sampler channel on which the effect send should be created on, &lt;midi-ctrl&gt;
3256 is a number between 0..127 defining the MIDI controller which can alter the
3257 effect send level and &lt;name&gt; is an optional argument defining a name
3258 for the effect send entity. The name does not have to be unique, but MUST be
3259 encapsulated into apostrophes and supports escape sequences as described in chapter
3260 "<xref target="character_set">Character Set and Escape Sequences</xref>".</t>
3261
3262 <t>By default, that is as initial routing, the effect send's audio channels
3263 are automatically routed to the last audio channels of the sampler channel's
3264 audio output device, that way you can i.e. first increase the amount of audio
3265 channels on the audio output device for having dedicated effect send output
3266 channels and when "CREATE FX_SEND" is called, those channels will automatically
3267 be picked. You can alter the destination channels however with
3268 <xref target="SET FX_SEND AUDIO_OUTPUT_CHANNEL">"SET FX_SEND AUDIO_OUTPUT_CHANNEL"</xref>.
3269 </t>
3270
3271 <t>Note: Create effect sends on a sampler channel only when needed, because having effect
3272 sends on a sampler channel will decrease runtime performance, because for implementing channel
3273 effect sends, separate (sampler channel local) audio buffers are needed to render and mix
3274 the voices and route the audio signal afterwards to the master outputs and effect send
3275 outputs (along with their respective effect send levels). A sampler channel without effect
3276 sends however can mix its voices directly into the audio output devices's audio buffers
3277 and is thus faster.
3278 </t>
3279
3280 <t>Possible Answers:</t>
3281 <t>
3282 <list>
3283 <t>"OK[&lt;fx-send-id&gt;]" -
3284 <list>
3285 <t>in case a new effect send could be added to the
3286 sampler channel, where &lt;fx-send-id&gt; reflects the
3287 unique ID of the newly created effect send entity</t>
3288 </list>
3289 </t>
3290 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3291 <list>
3292 <t>when a new effect send could not be added, i.e.
3293 due to invalid parameters</t>
3294 </list>
3295 </t>
3296 </list>
3297 </t>
3298
3299 <t>Examples:</t>
3300 <t>
3301 <list>
3302 <t>C: "CREATE FX_SEND 0 91 'Reverb Send'"</t>
3303 <t>S: "OK[0]"</t>
3304 </list>
3305 </t>
3306 <t>
3307 <list>
3308 <t>C: "CREATE FX_SEND 0 93"</t>
3309 <t>S: "OK[1]"</t>
3310 </list>
3311 </t>
3312 </section>
3313
3314 <section title="Removing an effect send from a sampler channel" anchor="DESTROY FX_SEND">
3315 <t>The front-end can remove an existing effect send on a specific sampler channel
3316 by sending the following command:</t>
3317 <t>
3318 <list>
3319 <t>DESTROY FX_SEND &lt;sampler-channel&gt; &lt;fx-send-id&gt;</t>
3320 </list>
3321 </t>
3322 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3323 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3324 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, that is the
3325 sampler channel from which the effect send should be removed from and
3326 &lt;fx-send-id&gt; is the respective effect send number as returned by the
3327 <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref>
3328 or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command.</t>
3329
3330 <t>Possible Answers:</t>
3331 <t>
3332 <list>
3333 <t>"OK" -
3334 <list>
3335 <t>on success</t>
3336 </list>
3337 </t>
3338 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3339 <list>
3340 <t>in case it failed, providing an appropriate error code and
3341 error message</t>
3342 </list>
3343 </t>
3344 </list>
3345 </t>
3346
3347 <t>Example:</t>
3348 <t>
3349 <list>
3350 <t>C: "DESTROY FX_SEND 0 0"</t>
3351 <t>S: "OK"</t>
3352 </list>
3353 </t>
3354 </section>
3355
3356 <section title="Getting amount of effect sends on a sampler channel" anchor="GET FX_SENDS">
3357 <t>The front-end can ask for the amount of effect sends on a specific sampler channel
3358 by sending the following command:</t>
3359 <t>
3360 <list>
3361 <t>GET FX_SENDS &lt;sampler-channel&gt;</t>
3362 </list>
3363 </t>
3364 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3365 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3366 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t>
3367
3368 <t>Possible Answers:</t>
3369 <t>
3370 <list>
3371 <t>The sampler will answer by returning the number of effect
3372 sends on the given sampler channel.</t>
3373 </list>
3374 </t>
3375
3376 <t>Example:</t>
3377 <t>
3378 <list>
3379 <t>C: "GET FX_SENDS 0"</t>
3380 <t>S: "2"</t>
3381 </list>
3382 </t>
3383 </section>
3384
3385 <section title="Listing all effect sends on a sampler channel" anchor="LIST FX_SENDS">
3386 <t>The front-end can ask for a list of effect sends on a specific sampler channel
3387 by sending the following command:</t>
3388 <t>
3389 <list>
3390 <t>LIST FX_SENDS &lt;sampler-channel&gt;</t>
3391 </list>
3392 </t>
3393 <t>Where &lt;sampler-channel&gt; is the respective sampler channel
3394 number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3395 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t>
3396
3397 <t>Possible Answers:</t>
3398 <t>
3399 <list>
3400 <t>The sampler will answer by returning a comma separated list
3401 with all effect sends' numerical IDs on the given sampler
3402 channel.</t>
3403 </list>
3404 </t>
3405
3406 <t>Examples:</t>
3407 <t>
3408 <list>
3409 <t>C: "LIST FX_SENDS 0"</t>
3410 <t>S: "0,1"</t>
3411 </list>
3412 </t>
3413 <t>
3414 <list>
3415 <t>C: "LIST FX_SENDS 1"</t>
3416 <t>S: ""</t>
3417 </list>
3418 </t>
3419 </section>
3420
3421 <section title="Getting effect send information" anchor="GET FX_SEND INFO">
3422 <t>The front-end can ask for the current settings of an effect send entity
3423 by sending the following command:</t>
3424 <t>
3425 <list>
3426 <t>GET FX_SEND INFO &lt;sampler-channel&gt; &lt;fx-send-id&gt;</t>
3427 </list>
3428 </t>
3429 <t>Where &lt;sampler-channel&gt; is the sampler channel number
3430 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3431 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and
3432 &lt;fx-send-id&gt; reflects the numerical ID of the effect send entity
3433 as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref>
3434 or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command.
3435 </t>
3436
3437 <t>Possible Answers:</t>
3438 <t>
3439 <list>
3440 <t>The sampler will answer by sending a &lt;CRLF&gt; separated list.
3441 Each answer line begins with the settings category name
3442 followed by a colon and then a space character &lt;SP&gt; and finally
3443 the info character string to that setting category. At the
3444 moment the following categories are defined:</t>
3445
3446 <t>
3447 <list>
3448 <t>NAME -
3449 <list>
3450 <t>name of the effect send entity</t>
3451 </list>
3452 </t>
3453 <t>MIDI_CONTROLLER -
3454 <list>
3455 <t>a value between 0 and 127 reflecting the MIDI controller
3456 which is able to modify the effect send's send level</t>
3457 </list>
3458 </t>
3459 <t>LEVEL -
3460 <list>
3461 <t>optionally dotted number reflecting the effect send's
3462 current send level (where a value &lt; 1.0 means attenuation
3463 and a value > 1.0 means amplification)</t>
3464 </list>
3465 </t>
3466 <t>AUDIO_OUTPUT_ROUTING -
3467 <list>
3468 <t>comma separated list which reflects to which audio
3469 channel of the selected audio output device each
3470 effect send output channel is routed to, e.g. "0,3" would
3471 mean the effect send's output channel 0 is routed to channel
3472 0 of the audio output device and the effect send's output
3473 channel 1 is routed to the channel 3 of the audio
3474 output device (see
3475 <xref target="SET FX_SEND AUDIO_OUTPUT_CHANNEL">"SET FX_SEND AUDIO_OUTPUT_CHANNEL"</xref>
3476 for details)</t>
3477 </list>
3478 </t>
3479 </list>
3480 </t>
3481 </list>
3482 </t>
3483 <t>The mentioned fields above don't have to be in particular order.</t>
3484
3485 <t>Example:</t>
3486 <t>
3487 <list>
3488 <t>C: "GET FX_SEND INFO 0 0"</t>
3489 <t>S: "NAME: Reverb Send"</t>
3490 <t>&nbsp;&nbsp;&nbsp;"MIDI_CONTROLLER: 91"</t>
3491 <t>&nbsp;&nbsp;&nbsp;"LEVEL: 0.3"</t>
3492 <t>&nbsp;&nbsp;&nbsp;"AUDIO_OUTPUT_ROUTING: 2,3"</t>
3493 <t>&nbsp;&nbsp;&nbsp;"."</t>
3494 </list>
3495 </t>
3496 </section>
3497
3498 <section title="Changing effect send's name" anchor="SET FX_SEND NAME">
3499 <t>The front-end can alter the current name of an effect
3500 send entity by sending the following command:</t>
3501 <t>
3502 <list>
3503 <t>SET FX_SEND NAME &lt;sampler-chan&gt; &lt;fx-send-id&gt; &lt;name&gt;</t>
3504 </list>
3505 </t>
3506 <t>Where &lt;sampler-chan&gt; is the sampler channel number
3507 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3508 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command,
3509 &lt;fx-send-id&gt; reflects the numerical ID of the effect send entity
3510 as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref>
3511 or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command and
3512 &lt;name&gt; is the new name of the effect send entity, which
3513 does not have to be unique (name MUST be encapsulated into apostrophes
3514 and supports escape sequences as described in chapter
3515 "<xref target="character_set">Character Set and Escape Sequences</xref>").
3516 </t>
3517
3518 <t>Possible Answers:</t>
3519 <t>
3520 <list>
3521 <t>"OK" -
3522 <list>
3523 <t>on success</t>
3524 </list>
3525 </t>
3526 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3527 <list>
3528 <t>in case it failed, providing an appropriate error code and error message</t>
3529 </list>
3530 </t>
3531 </list>
3532 </t>
3533 <t>Example:</t>
3534 <t>
3535 <list>
3536 <t>C: "SET FX_SEND NAME 0 0 'Fx Send 1'"</t>
3537 <t>S: "OK"</t>
3538 </list>
3539 </t>
3540 </section>
3541
3542 <section title="Altering effect send's audio routing" anchor="SET FX_SEND AUDIO_OUTPUT_CHANNEL">
3543 <t>The front-end can alter the destination of an effect send's audio channel on a specific
3544 sampler channel by sending the following command:</t>
3545 <t>
3546 <list>
3547 <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>
3548 </list>
3549 </t>
3550 <t>Where &lt;sampler-chan&gt; is the sampler channel number
3551 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3552 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command,
3553 &lt;fx-send-id&gt; reflects the numerical ID of the effect send entity
3554 as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref>
3555 or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command,
3556 &lt;audio-src&gt; is the numerical ID of the effect send's audio channel
3557 which should be rerouted and &lt;audio-dst&gt; is the numerical ID of
3558 the audio channel of the selected audio output device where &lt;audio-src&gt;
3559 should be routed to.</t>
3560
3561 <t>Note that effect sends can only route audio to the same audio output
3562 device as assigned to the effect send's sampler channel. Also note that an
3563 effect send entity does always have exactly as much audio channels as its
3564 sampler channel. So if the sampler channel is stereo, the effect send does
3565 have two audio channels as well. Also keep in mind that the amount of audio
3566 channels on a sampler channel might be dependant not only to the deployed
3567 sampler engine on the sampler channel, but also dependant to the instrument
3568 currently loaded. However you can (effectively) turn an i.e. stereo effect
3569 send into a mono one by simply altering its audio routing appropriately.</t>
3570
3571 <t>Possible Answers:</t>
3572 <t>
3573 <list>
3574 <t>"OK" -
3575 <list>
3576 <t>on success</t>
3577 </list>
3578 </t>
3579 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3580 <list>
3581 <t>if audio output channel was set, but there are noteworthy
3582 issue(s) related, providing an appropriate warning code and
3583 warning message</t>
3584 </list>
3585 </t>
3586 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3587 <list>
3588 <t>in case it failed, providing an appropriate error code and error message</t>
3589 </list>
3590 </t>
3591 </list>
3592 </t>
3593 <t>Example:</t>
3594 <t>
3595 <list>
3596 <t>C: "SET FX_SEND AUDIO_OUTPUT_CHANNEL 0 0 0 2"</t>
3597 <t>S: "OK"</t>
3598 </list>
3599 </t>
3600 </section>
3601
3602 <section title="Altering effect send's MIDI controller" anchor="SET FX_SEND MIDI_CONTROLLER">
3603 <t>The front-end can alter the MIDI controller of an effect
3604 send entity by sending the following command:</t>
3605 <t>
3606 <list>
3607 <t>SET FX_SEND MIDI_CONTROLLER &lt;sampler-chan&gt; &lt;fx-send-id&gt; &lt;midi-ctrl&gt;</t>
3608 </list>
3609 </t>
3610 <t>Where &lt;sampler-chan&gt; is the sampler channel number
3611 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3612 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command,
3613 &lt;fx-send-id&gt; reflects the numerical ID of the effect send entity
3614 as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref>
3615 or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command and
3616 &lt;midi-ctrl&gt; reflects the MIDI controller which shall be
3617 able to modify the effect send's send level.</t>
3618
3619 <t>Possible Answers:</t>
3620 <t>
3621 <list>
3622 <t>"OK" -
3623 <list>
3624 <t>on success</t>
3625 </list>
3626 </t>
3627 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3628 <list>
3629 <t>if MIDI controller was set, but there are noteworthy
3630 issue(s) related, providing an appropriate warning code and
3631 warning message</t>
3632 </list>
3633 </t>
3634 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3635 <list>
3636 <t>in case it failed, providing an appropriate error code and error message</t>
3637 </list>
3638 </t>
3639 </list>
3640 </t>
3641 <t>Example:</t>
3642 <t>
3643 <list>
3644 <t>C: "SET FX_SEND MIDI_CONTROLLER 0 0 91"</t>
3645 <t>S: "OK"</t>
3646 </list>
3647 </t>
3648 </section>
3649
3650 <section title="Altering effect send's send level" anchor="SET FX_SEND LEVEL">
3651 <t>The front-end can alter the current send level of an effect
3652 send entity by sending the following command:</t>
3653 <t>
3654 <list>
3655 <t>SET FX_SEND LEVEL &lt;sampler-chan&gt; &lt;fx-send-id&gt; &lt;volume&gt;</t>
3656 </list>
3657 </t>
3658 <t>Where &lt;sampler-chan&gt; is the sampler channel number
3659 as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref>
3660 or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command,
3661 &lt;fx-send-id&gt; reflects the numerical ID of the effect send entity
3662 as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref>
3663 or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command and
3664 &lt;volume&gt; is an optionally dotted positive number (a value
3665 smaller than 1.0 means attenuation, whereas a value greater than
3666 1.0 means amplification) reflecting the new send level.</t>
3667
3668 <t>Possible Answers:</t>
3669 <t>
3670 <list>
3671 <t>"OK" -
3672 <list>
3673 <t>on success</t>
3674 </list>
3675 </t>
3676 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3677 <list>
3678 <t>if new send level was set, but there are noteworthy
3679 issue(s) related, providing an appropriate warning code and
3680 warning message</t>
3681 </list>
3682 </t>
3683 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3684 <list>
3685 <t>in case it failed, providing an appropriate error code and error message</t>
3686 </list>
3687 </t>
3688 </list>
3689 </t>
3690 <t>Example:</t>
3691 <t>
3692 <list>
3693 <t>C: "SET FX_SEND LEVEL 0 0 0.15"</t>
3694 <t>S: "OK"</t>
3695 </list>
3696 </t>
3697 </section>
3698
3699 <section title="Resetting a sampler channel" anchor="RESET CHANNEL">
3700 <t>The front-end can reset a particular sampler channel by sending the following command:</t>
3701 <t>
3702 <list>
3703 <t>RESET CHANNEL &lt;sampler-channel&gt;</t>
3704 </list>
3705 </t>
3706 <t>
3707 Where &lt;sampler-channel&gt; defines the sampler channel to be reset.
3708 This will cause the engine on that sampler channel, its voices and
3709 eventually disk streams and all control and status variables to be
3710 reset.</t>
3711
3712 <t>Possible Answers:</t>
3713 <t>
3714 <list>
3715 <t>"OK" -
3716 <list>
3717 <t>on success</t>
3718 </list>
3719 </t>
3720 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3721 <list>
3722 <t>if channel was reset, but there are noteworthy issue(s)
3723 related, providing an appropriate warning code and warning
3724 message</t>
3725 </list>
3726 </t>
3727 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3728 <list>
3729 <t>in case it failed, providing an appropriate error code and
3730 error message</t>
3731 </list>
3732 </t>
3733 </list>
3734 </t>
3735 <t>Examples:</t>
3736 <t>
3737 <list>
3738 <t></t>
3739 </list>
3740 </t>
3741 </section>
3742 </section>
3743
3744 <section title="Controlling connection">
3745 <t>The following commands are used to control the connection to LinuxSampler.</t>
3746
3747 <section title="Register front-end for receiving event messages" anchor="SUBSCRIBE">
3748 <t>The front-end can register itself to the LinuxSampler application to
3749 be informed about noteworthy events by sending this command:</t>
3750 <t>
3751 <list>
3752 <t>SUBSCRIBE &lt;event-id&gt;</t>
3753 </list>
3754 </t>
3755 <t>where &lt;event-id&gt; will be replaced by the respective event that
3756 client wants to subscribe to.</t>
3757
3758 <t>Possible Answers:</t>
3759 <t>
3760 <list>
3761 <t>"OK" -
3762 <list>
3763 <t>on success</t>
3764 </list>
3765 </t>
3766 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3767 <list>
3768 <t>if registration succeeded, but there are noteworthy
3769 issue(s) related, providing an appropriate warning code and
3770 warning message</t>
3771 </list>
3772 </t>
3773 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3774 <list>
3775 <t>in case it failed, providing an appropriate error code and
3776 error message</t>
3777 </list>
3778 </t>
3779 </list>
3780 </t>
3781 <t>Examples:</t>
3782 <t>
3783 <list>
3784 <t></t>
3785 </list>
3786 </t>
3787 </section>
3788
3789 <section title="Unregister front-end for not receiving event messages" anchor="UNSUBSCRIBE">
3790 <t>The front-end can unregister itself if it doesn't want to receive event
3791 messages anymore by sending the following command:</t>
3792 <t>
3793 <list>
3794 <t>UNSUBSCRIBE &lt;event-id&gt;</t>
3795 </list>
3796 </t>
3797 <t>Where &lt;event-id&gt; will be replaced by the respective event that
3798 client doesn't want to receive anymore.</t>
3799
3800 <t>Possible Answers:</t>
3801 <t>
3802 <list>
3803 <t>"OK" -
3804 <list>
3805 <t>on success</t>
3806 </list>
3807 </t>
3808 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
3809 <list>
3810 <t>if unregistration succeeded, but there are noteworthy
3811 issue(s) related, providing an appropriate warning code and
3812 warning message</t>
3813 </list>
3814 </t>
3815 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3816 <list>
3817 <t>in case it failed, providing an appropriate error code and
3818 error message</t>
3819 </list>
3820 </t>
3821 </list>
3822 </t>
3823 <t>Examples:</t>
3824 <t>
3825 <list>
3826 <t></t>
3827 </list>
3828 </t>
3829 </section>
3830
3831 <section title="Enable or disable echo of commands" anchor="SET ECHO">
3832 <t>To enable or disable back sending of commands to the client the following command can be used:</t>
3833 <t>
3834 <list>
3835 <t>SET ECHO &lt;value&gt;</t>
3836 </list>
3837 </t>
3838 <t>Where &lt;value&gt; should be replaced either by "1" to enable echo mode
3839 or "0" to disable echo mode. When echo mode is enabled, all
3840 commands send to LinuxSampler will be immediately send back and
3841 after this echo the actual response to the command will be
3842 returned. Echo mode will only be altered for the client connection
3843 that issued the "SET ECHO" command, not globally for all client
3844 connections.</t>
3845
3846 <t>Possible Answers:</t>
3847 <t>
3848 <list>
3849 <t>"OK" -
3850 <list>
3851 <t>usually</t>
3852 </list>
3853 </t>
3854 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
3855 <list>
3856 <t>on syntax error, e.g. non boolean value</t>
3857 </list>
3858 </t>
3859 </list>
3860 </t>
3861 <t>Examples:</t>
3862 <t>
3863 <list>
3864 <t></t>
3865 </list>
3866 </t>
3867 </section>
3868
3869 <section title="Close client connection" anchor="QUIT">
3870 <t>The client can close its network connection to LinuxSampler by sending the following command:</t>
3871 <t>
3872 <list>
3873 <t>QUIT</t>
3874 </list>
3875 </t>
3876 <t>This is probably more interesting for manual telnet connections to
3877 LinuxSampler than really useful for a front-end implementation.</t>
3878 </section>
3879 </section>
3880
3881 <section title="Global commands">
3882 <t>The following commands have global impact on the sampler.</t>
3883
3884 <section title="Current number of active voices" anchor="GET TOTAL_VOICE_COUNT">
3885 <t>The front-end can ask for the current number of active voices on
3886 the sampler by sending the following command:</t>
3887 <t>
3888 <list>
3889 <t>GET TOTAL_VOICE_COUNT</t>
3890 </list>
3891 </t>
3892
3893 <t>Possible Answers:</t>
3894 <t>
3895 <list>
3896 <t>LinuxSampler will answer by returning the number of all active
3897 voices on the sampler.</t>
3898 </list>
3899 </t>
3900 </section>
3901
3902 <section title="Maximum amount of active voices" anchor="GET TOTAL_VOICE_COUNT_MAX">
3903 <t>The front-end can ask for the maximum number of active voices
3904 by sending the following command:</t>
3905 <t>
3906 <list>
3907 <t>GET TOTAL_VOICE_COUNT_MAX</t>
3908 </list>
3909 </t>
3910
3911 <t>Possible Answers:</t>
3912 <t>
3913 <list>
3914 <t>LinuxSampler will answer by returning the maximum number
3915 of active voices.</t>
3916 </list>
3917 </t>
3918 </section>
3919
3920 <section title="Reset sampler" anchor="RESET">
3921 <t>The front-end can reset the whole sampler by sending the following command:</t>
3922 <t>
3923 <list>
3924 <t>RESET</t>
3925 </list>
3926 </t>
3927
3928 <t>Possible Answers:</t>
3929 <t>
3930 <list>
3931 <t>"OK" -
3932 <list>
3933 <t>always</t>
3934 </list>
3935 </t>
3936 </list>
3937 </t>
3938 <t>Examples:</t>
3939 <t>
3940 <list>
3941 <t></t>
3942 </list>
3943 </t>
3944 </section>
3945
3946 <section title="General sampler informations" anchor="GET SERVER INFO">
3947 <t>The client can ask for general informations about the LinuxSampler
3948 instance by sending the following command:</t>
3949 <t>
3950 <list>
3951 <t>GET SERVER INFO</t>
3952 </list>
3953 </t>
3954 <t>Possible Answers:</t>
3955 <t>
3956 <list>
3957 <t>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
3958 Each answer line begins with the information category name
3959 followed by a colon and then a space character &lt;SP&gt; and finally
3960 the info character string to that information category. At the
3961 moment the following categories are defined:
3962 </t>
3963 <t>
3964 <list>
3965 <t>DESCRIPTION -
3966 <list>
3967 <t>arbitrary textual description about the sampler
3968 (note that the character string may contain
3969 <xref target="character_set">escape sequences</xref>)</t>
3970 </list>
3971 </t>
3972 <t>VERSION -
3973 <list>
3974 <t>version of the sampler</t>
3975 </list>
3976 </t>
3977 <t>PROTOCOL_VERSION -
3978 <list>
3979 <t>version of the LSCP specification the sampler
3980 complies with (see <xref target="LSCP versioning" /> for details)</t>
3981 </list>
3982 </t>
3983 <t>INSTRUMENTS_DB_SUPPORT -
3984 <list>
3985 <t>either yes or no, specifies whether the
3986 sampler is build with instruments database support.</t>
3987 </list>
3988 </t>
3989 </list>
3990 </t>
3991 </list>
3992 </t>
3993 <t>The mentioned fields above don't have to be in particular order.
3994 Other fields might be added in future.</t>
3995 </section>
3996
3997 <section title="Getting global volume attenuation" anchor="GET VOLUME">
3998 <t>The client can ask for the current global sampler-wide volume
3999 attenuation by sending the following command:</t>
4000 <t>
4001 <list>
4002 <t>GET VOLUME</t>
4003 </list>
4004 </t>
4005 <t>Possible Answers:</t>
4006 <t>
4007 <list>
4008 <t>The sampler will always answer by returning the optional
4009 dotted floating point coefficient, reflecting the current
4010 global volume attenuation.
4011 </t>
4012 </list>
4013 </t>
4014 <t>Note: it is up to the respective sampler engine whether to obey
4015 that global volume parameter or not, but in general all engines SHOULD
4016 use this parameter.</t>
4017 </section>
4018
4019 <section title="Setting global volume attenuation" anchor="SET VOLUME">
4020 <t>The client can alter the current global sampler-wide volume
4021 attenuation by sending the following command:</t>
4022 <t>
4023 <list>
4024 <t>SET VOLUME &lt;volume&gt;</t>
4025 </list>
4026 </t>
4027 <t>Where &lt;volume&gt; should be replaced by the optional dotted
4028 floating point value, reflecting the new global volume parameter.
4029 This value might usually be in the range between 0.0 and 1.0, that
4030 is for attenuating the overall volume.</t>
4031
4032 <t>Possible Answers:</t>
4033 <t>
4034 <list>
4035 <t>"OK" -
4036 <list>
4037 <t>on success</t>
4038 </list>
4039 </t>
4040 <t>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
4041 <list>
4042 <t>if the global volume was set, but there are noteworthy
4043 issue(s) related, providing an appropriate warning code and
4044 warning message</t>
4045 </list>
4046 </t>
4047 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
4048 <list>
4049 <t>in case it failed, providing an appropriate error code and error message</t>
4050 </list>
4051 </t>
4052 </list>
4053 </t>
4054 </section>
4055 </section>
4056
4057
4058 <section title="MIDI Instrument Mapping" anchor="MIDI Instrument Mapping">
4059 <t>The MIDI protocol provides a way to switch between instruments
4060 by sending so called MIDI bank select and MIDI program change
4061 messages which are essentially just numbers. The following commands
4062 allow to actually map arbitrary MIDI bank select / program change
4063 numbers with real instruments.</t>
4064 <t>The sampler allows to manage an arbitrary amount of MIDI
4065 instrument maps which define which instrument to load on
4066 which MIDI program change message.</t>
4067 <t>By default, that is when the sampler is launched, there is no
4068 map, thus the sampler will simply ignore all program change
4069 messages. The front-end has to explicitly create at least one
4070 map, add entries to the map and tell the respective sampler
4071 channel(s) which MIDI instrument map to use, so the sampler
4072 knows how to react on a given program change message on the
4073 respective sampler channel, that is by switching to the
4074 respectively defined engine type and loading the respective
4075 instrument. See command
4076 <xref target="SET CHANNEL MIDI_INSTRUMENT_MAP">"SET CHANNEL MIDI_INSTRUMENT_MAP"</xref>
4077 for how to assign a MIDI instrument map to a sampler channel.</t>
4078 <t>Also note per MIDI specification a bank select message does not
4079 cause to switch to another instrument. Instead when receiving a
4080 bank select message the bank value will be stored and a subsequent
4081 program change message (which may occur at any time) will finally
4082 cause the sampler to switch to the respective instrument as
4083 reflected by the current MIDI instrument map.</t>
4084
4085 <section title="Create a new MIDI instrument map" anchor="ADD MIDI_INSTRUMENT_MAP">
4086 <t>The front-end can add a new MIDI instrument map by sending
4087 the following command:</t>
4088 <t>
4089 <list>
4090 <t>ADD MIDI_INSTRUMENT_MAP [&lt;name&gt;]</t>
4091 </list>
4092 </t>
4093 <t>Where &lt;name&gt; is an optional argument allowing to
4094 assign a custom name to the new map. MIDI instrument Map
4095 names do not have to be unique, but MUST be encapsulated
4096 into apostrophes and support escape sequences as described
4097 in chapter "<xref target="character_set">Character Set and Escape Sequences</xref>".
4098 </t>
4099
4100 <t>Possible Answers:</t>
4101 <t>
4102 <list>
4103 <t>"OK[&lt;map&gt;]" -
4104 <list>
4105 <t>in case a new MIDI instrument map could
4106 be added, where &lt;map&gt; reflects the
4107 unique ID of the newly created MIDI
4108 instrument map</t>
4109 </list>
4110 </t>
4111 <t>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
4112 <list>
4113 <t>when a new map could not be created, which
4114 might never occur in practice</t>
4115 </list>
4116 </t>
4117 </list>
4118 </t>
4119
4120 <t>Examples:</t>
4121 <t>
4122 <list>
4123 <t>C: "ADD MIDI_INSTRUMENT_MAP 'Standard Map'"</t>
4124 <t>S: "OK[0]"</t>
4125 </list>
4126 </t>
4127 <t>
4128 <list>
4129 <t>C: "ADD MIDI_INSTRUMENT_MAP 'Standard Drumkit'"</t>
4130 <t>S: "OK[1]"</t>
4131 </list>
4132 </t>
4133 <t>
4134 <list>
4135 <t>C: "ADD MIDI_INSTRUMENT_MAP"</t>
4136 <t>S: "OK[5]"</t>
4137 </list>
4138 </t>
4139 </section>
4140
4141 <section title="Delete one particular or all MIDI instrument maps" anchor="REMOVE MIDI_INSTRUMENT_MAP">
4142 <t>The front-end can delete a particular MIDI instrument map
4143 by sending the following command:</t>
4144 <t>
4145 <list>
4146 <t>REMOVE MIDI_INSTRUMENT_MAP &lt;map&gt;</t>
4147 </list>
4148 </t>
4149 <t>Where &lt;map&gt; reflects the unique ID of the map to delete
4150 as returned by the <xref target="LIST MIDI_INSTRUMENT_MAPS">"LIST MIDI_INSTRUMENT_MAPS"</xref>
4151 command.</t>
4152 <t>The front-end can delete all MIDI instrument maps by
4153 sending the following command:</t>
4154 <t>
4155 <list>
4156 <t>REMOVE MIDI_INSTRUMENT_MAP ALL</t>
4157 </list>
4158 </t>
4159
4160 <t>Possible Answers:</t>
4161 <t>
4162 <list>