| 11 |
<?rfc symrefs="yes" ?> |
<?rfc symrefs="yes" ?> |
| 12 |
<?rfc sortrefs="yes"?> |
<?rfc sortrefs="yes"?> |
| 13 |
<?rfc iprnotified="no" ?> |
<?rfc iprnotified="no" ?> |
|
<?rfc strict="yes" ?> |
|
| 14 |
|
|
| 15 |
<rfc category="std" ipr="full2026" docName="lscp.txt"> |
<!-- 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> |
<front> |
| 21 |
<title>LinuxSampler Control Protocol</title> |
<title>LinuxSampler Control Protocol (draft)</title> |
| 22 |
<author initials='C.S.' surname="Schoenebeck" fullname='C. |
<author initials='C.S.' surname="Schoenebeck" fullname='C. |
| 23 |
Schoenebeck'> |
Schoenebeck'> |
| 24 |
<organization> |
<organization> |
| 34 |
<email>schoenebeck at software minus engineering dot org</email> |
<email>schoenebeck at software minus engineering dot org</email> |
| 35 |
</address> |
</address> |
| 36 |
</author> |
</author> |
| 37 |
<date month="Jan" year="2005"/> |
<date month="June" year="2007"/> |
| 38 |
<workgroup>LinuxSampler Developers</workgroup> |
<workgroup>LinuxSampler Developers</workgroup> |
| 39 |
<keyword>LSCP</keyword> |
<keyword>LSCP</keyword> |
| 40 |
<abstract> |
<abstract> |
| 41 |
<t>The LinuxSampler Control Protocol (LSCP) is an |
<t>The LinuxSampler Control Protocol (LSCP) is an |
| 42 |
application-level protocol primarily intended for local and |
application-level protocol primarily intended for local and |
| 43 |
remote controlling the LinuxSampler main application, which is a |
remote controlling the LinuxSampler backend application, which is a |
| 44 |
sophisticated console application essentially playing back audio |
sophisticated server-like console application essentially playing |
| 45 |
samples and manipulating the samples in real time to certain |
back audio samples and manipulating the samples in real time to |
| 46 |
extent.</t> |
certain extent.</t> |
| 47 |
</abstract> |
</abstract> |
| 48 |
</front> |
</front> |
| 49 |
|
|
| 61 |
(front-end) and server (LinuxSampler) respectively. Lines in |
(front-end) and server (LinuxSampler) respectively. Lines in |
| 62 |
examples must be interpreted as every line being CRLF |
examples must be interpreted as every line being CRLF |
| 63 |
terminated (carriage return character followed by line feed |
terminated (carriage return character followed by line feed |
| 64 |
character as defined in the ASCII standard), thus the following |
character as defined in the ASCII standard <xref target="RFC20"/>), |
| 65 |
example:</t> |
thus the following example:</t> |
| 66 |
|
|
| 67 |
<t> |
<t> |
| 68 |
<list> |
<list> |
| 115 |
return and line feed characters respectively.</t> |
return and line feed characters respectively.</t> |
| 116 |
</section> |
</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"> |
<section title="Introduction"> |
| 156 |
<t>LinuxSampler is a so called software sampler application |
<t>LinuxSampler is a so called software sampler application |
| 157 |
capable to playback audio samples from a computer's Random |
capable to playback audio samples from a computer's Random |
| 164 |
arbitrary MIDI input method and arbitrary MIDI channel (e.g. |
arbitrary MIDI input method and arbitrary MIDI channel (e.g. |
| 165 |
sampler channel 17 could be connected to an ALSA sequencer |
sampler channel 17 could be connected to an ALSA sequencer |
| 166 |
device 64:0 and listening to MIDI channel 1 there). Each sampler |
device 64:0 and listening to MIDI channel 1 there). Each sampler |
| 167 |
engine will be assigned an own instance of one of the available |
channel will be associated with an instance of one of the available |
| 168 |
sampler engines (e.g. GigEngine, DLSEngine). The audio output of |
sampler engines (e.g. GigEngine, DLSEngine). The audio output of |
| 169 |
each sampler channel can be routed to an arbitrary audio output |
each sampler channel can be routed to an arbitrary audio output |
| 170 |
method (ALSA / JACK) and an arbitrary audio output channel |
method (ALSA / JACK) and an arbitrary audio output channel |
| 194 |
methods will be described next.</t> |
methods will be described next.</t> |
| 195 |
|
|
| 196 |
<section title="Request/response communication method"> |
<section title="Request/response communication method"> |
| 197 |
<t>This simple communication method is based on TCP. The |
<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 |
front-end application establishes a TCP connection to the |
| 200 |
LinuxSampler instance on a certain host system. Then the |
LinuxSampler instance on a certain host system. Then the |
| 201 |
front-end application will send certain ASCII based commands |
front-end application will send certain ASCII based commands |
| 275 |
<t>C: "GET AUDIO_OUTPUT_DEVICE INFO 123456"</t> |
<t>C: "GET AUDIO_OUTPUT_DEVICE INFO 123456"</t> |
| 276 |
<t>S: "ERR:9:There is no audio output device with index 123456."</t> |
<t>S: "ERR:9:There is no audio output device with index 123456."</t> |
| 277 |
</list> |
</list> |
| 278 |
</t> |
</t> |
| 279 |
<t>Normal result sets could be:</t> |
<t>Normal result sets could be:</t> |
| 280 |
<t> |
<t> |
| 281 |
<list style="numbers"> |
<list style="numbers"> |
| 420 |
|
|
| 421 |
<t>where <event-id> will be replace by the respective |
<t>where <event-id> will be replace by the respective |
| 422 |
event that client is no longer interested in receiving. For |
event that client is no longer interested in receiving. For |
| 423 |
a list of supported events see chapter 6.</t> |
a list of supported events see <xref target="events" />.</t> |
| 424 |
|
|
| 425 |
<t>Example: the fill states of disk stream buffers have |
<t>Example: the fill states of disk stream buffers have |
| 426 |
changed on sampler channel 4 and the LinuxSampler instance |
changed on sampler channel 4 and the LinuxSampler instance |
| 466 |
</section> |
</section> |
| 467 |
</section> |
</section> |
| 468 |
|
|
| 469 |
<section title="Description for control commands"> |
<section title="Description for control commands" anchor="control_commands"> |
| 470 |
<t>This chapter will describe the available control commands |
<t>This chapter will describe the available control commands |
| 471 |
that can be sent on the TCP connection in detail. Some certain |
that can be sent on the TCP connection in detail. Some certain |
| 472 |
commands (e.g. "GET CHANNEL INFO" or "GET ENGINE INFO") lead to |
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 |
multiple-line responses. In this case LinuxSampler signals the |
| 475 |
end of the response by a "." (single dot) line.</t> |
end of the response by a "." (single dot) line.</t> |
| 476 |
|
|
| 514 |
what parameters drivers are offering, how to retrieve their |
what parameters drivers are offering, how to retrieve their |
| 515 |
possible values, etc.</t> |
possible values, etc.</t> |
| 516 |
|
|
| 517 |
<section title="Getting all available audio output drivers"> |
<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 |
<t>Use the following command to list all audio output |
| 544 |
drivers currently available for the LinuxSampler |
drivers currently available for the LinuxSampler |
| 545 |
instance:</t> |
instance:</t> |
| 546 |
<t> |
<t> |
| 547 |
<list> |
<list> |
| 548 |
<t>GET AVAILABLE_AUDIO_OUTPUT_DRIVERS</t> |
<t>LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS</t> |
| 549 |
</list> |
</list> |
| 550 |
</t> |
</t> |
| 551 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 559 |
<t>Example:</t> |
<t>Example:</t> |
| 560 |
<t> |
<t> |
| 561 |
<list> |
<list> |
| 562 |
<t>C: "GET AVAILABLE_AUDIO_OUTPUT_DRIVERS"</t> |
<t>C: "LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS"</t> |
| 563 |
<t>S: "ALSA,JACK"</t> |
<t>S: "ALSA,JACK"</t> |
| 564 |
</list> |
</list> |
| 565 |
</t> |
</t> |
| 566 |
</section> |
</section> |
| 567 |
|
|
| 568 |
<section title="Getting information about a specific audio |
<section title="Getting information about a specific audio |
| 569 |
output driver"> |
output driver" anchor="GET AUDIO_OUTPUT_DRIVER INFO"> |
| 570 |
<t>Use the following command to get detailed information |
<t>Use the following command to get detailed information |
| 571 |
about a specific audio output driver:</t> |
about a specific audio output driver:</t> |
| 572 |
<t> |
<t> |
| 576 |
</list> |
</list> |
| 577 |
</t> |
</t> |
| 578 |
<t>Where <audio-output-driver> is the name of the |
<t>Where <audio-output-driver> is the name of the |
| 579 |
audio output driver, returned by the "GET |
audio output driver, returned by the |
| 580 |
AVAILABLE_AUDIO_OUTPUT_DRIVERS" command.</t> |
<xref target="LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS">"LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS"</xref> command.</t> |
| 581 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 582 |
<t> |
<t> |
| 583 |
<list> |
<list> |
| 639 |
</section> |
</section> |
| 640 |
|
|
| 641 |
<section title="Getting information about specific audio |
<section title="Getting information about specific audio |
| 642 |
output driver parameter"> |
output driver parameter" anchor="GET AUDIO_OUTPUT_DRIVER_PARAMETER INFO"> |
| 643 |
<t>Use the following command to get detailed information |
<t>Use the following command to get detailed information |
| 644 |
about a specific audio output driver parameter:</t> |
about a specific audio output driver parameter:</t> |
| 645 |
<t> |
<t> |
| 648 |
</list> |
</list> |
| 649 |
</t> |
</t> |
| 650 |
<t>Where <audio> is the name of the audio output |
<t>Where <audio> is the name of the audio output |
| 651 |
driver as returned by the "GET AVAILABLE_AUDIO_OUTPUT_DRIVERS" command, |
driver as returned by the <xref target="LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS"> |
| 652 |
|
"LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS"</xref> command, |
| 653 |
<prm> a specific parameter name for which information should be |
<prm> a specific parameter name for which information should be |
| 654 |
obtained (as returned by the "GET AUDIO_OUTPUT_DRIVER INFO" command) and |
obtained (as returned by the |
| 655 |
|
<xref target="GET AUDIO_OUTPUT_DRIVER INFO">"GET AUDIO_OUTPUT_DRIVER INFO"</xref> command) and |
| 656 |
<deplist> is an optional list of parameters on which the sought |
<deplist> is an optional list of parameters on which the sought |
| 657 |
parameter <prm> depends on, <deplist> is a list of key-value |
parameter <prm> depends on, <deplist> is a list of key-value |
| 658 |
pairs in form of "key1=val1 key2=val2 ...", where character string values |
pairs in form of "key1=val1 key2=val2 ...", where character string values |
| 699 |
<list> |
<list> |
| 700 |
<t>either true or false, defines if this parameter must be |
<t>either true or false, defines if this parameter must be |
| 701 |
given when the device is to be created with the |
given when the device is to be created with the |
| 702 |
'CREATE AUDIO_OUTPUT_DEVICE' command |
<xref target="CREATE AUDIO_OUTPUT_DEVICE">'CREATE AUDIO_OUTPUT_DEVICE'</xref> |
| 703 |
(always returned, no matter which driver parameter)</t> |
command (always returned, no matter which driver parameter)</t> |
| 704 |
</list> |
</list> |
| 705 |
</t> |
</t> |
| 706 |
|
|
| 708 |
<list> |
<list> |
| 709 |
<t>either true or false, if false then this parameter can |
<t>either true or false, if false then this parameter can |
| 710 |
be changed at any time, once the device is created by |
be changed at any time, once the device is created by |
| 711 |
the 'CREATE AUDIO_OUTPUT_DEVICE' command |
the <xref target="CREATE AUDIO_OUTPUT_DEVICE">'CREATE AUDIO_OUTPUT_DEVICE'</xref> |
| 712 |
(always returned, no matter which driver parameter)</t> |
command (always returned, no matter which driver parameter)</t> |
| 713 |
</list> |
</list> |
| 714 |
</t> |
</t> |
| 715 |
|
|
| 724 |
|
|
| 725 |
<t>DEPENDS - |
<t>DEPENDS - |
| 726 |
<list> |
<list> |
| 727 |
<t>comma separated list of paramters this parameter depends |
<t>comma separated list of parameters this parameter depends |
| 728 |
on, means the values for fields 'DEFAULT', 'RANGE_MIN', |
on, means the values for fields 'DEFAULT', 'RANGE_MIN', |
| 729 |
'RANGE_MAX' and 'POSSIBILITIES' might depend on these |
'RANGE_MAX' and 'POSSIBILITIES' might depend on these |
| 730 |
listed parameters, for example assuming that an audio |
listed parameters, for example assuming that an audio |
| 741 |
<list> |
<list> |
| 742 |
<t>reflects the default value for this parameter which is |
<t>reflects the default value for this parameter which is |
| 743 |
used when the device is created and not explicitly |
used when the device is created and not explicitly |
| 744 |
given with the 'CREATE AUDIO_OUTPUT_DEVICE' command, |
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 |
in case of MULTIPLCITY=true, this is a comma separated |
| 747 |
list, that's why character strings are encapsulated into |
list, that's why character strings are encapsulated into |
| 748 |
apostrophes (') |
apostrophes (') |
| 827 |
</t> |
</t> |
| 828 |
</section> |
</section> |
| 829 |
|
|
| 830 |
<section title="Creating an audio output device"> |
<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> |
<t>Use the following command to create a new audio output device for the desired audio output system:</t> |
| 832 |
|
|
| 833 |
<t> |
<t> |
| 837 |
</t> |
</t> |
| 838 |
|
|
| 839 |
<t>Where <audio-output-driver> should be replaced by the desired audio |
<t>Where <audio-output-driver> should be replaced by the desired audio |
| 840 |
output system and <param-list> by an optional list of driver |
output system as returned by the |
| 841 |
|
<xref target="LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS">"LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS"</xref> |
| 842 |
|
command and <param-list> by an optional list of driver |
| 843 |
specific parameters in form of "key1=val1 key2=val2 ...", where |
specific parameters in form of "key1=val1 key2=val2 ...", where |
| 844 |
character string values should be encapsulated into apostrophes ('). |
character string values should be encapsulated into apostrophes ('). |
| 845 |
Note that there might be drivers which require parameter(s) to be |
Note that there might be drivers which require parameter(s) to be |
| 887 |
</t> |
</t> |
| 888 |
</section> |
</section> |
| 889 |
|
|
| 890 |
<section title="Destroying an audio output device"> |
<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> |
<t>Use the following command to destroy a created output device:</t> |
| 892 |
<t> |
<t> |
| 893 |
<list> |
<list> |
| 895 |
</list> |
</list> |
| 896 |
</t> |
</t> |
| 897 |
<t>Where <device-id> should be replaced by the numerical ID of the |
<t>Where <device-id> should be replaced by the numerical ID of the |
| 898 |
audio output device as given by the "CREATE AUDIO_OUTPUT_DEVICE" or |
audio output device as given by the |
| 899 |
"GET AUDIO_OUTPUT_DEVICES" command.</t> |
<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> |
<t>Possible Answers:</t> |
| 903 |
<t> |
<t> |
| 904 |
<list> |
<list> |
| 933 |
</t> |
</t> |
| 934 |
</section> |
</section> |
| 935 |
|
|
| 936 |
<section title="Getting all created audio output device count"> |
<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> |
<t>Use the following command to count all created audio output devices:</t> |
| 938 |
<t> |
<t> |
| 939 |
<list> |
<list> |
| 956 |
</t> |
</t> |
| 957 |
</section> |
</section> |
| 958 |
|
|
| 959 |
<section title="Getting all created audio output device list"> |
<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> |
<t>Use the following command to list all created audio output devices:</t> |
| 961 |
<t> |
<t> |
| 962 |
<list> |
<list> |
| 979 |
</t> |
</t> |
| 980 |
</section> |
</section> |
| 981 |
|
|
| 982 |
<section title="Getting current settings of an audio output device"> |
<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> |
<t>Use the following command to get current settings of a specific, created audio output device:</t> |
| 984 |
<t> |
<t> |
| 985 |
<list> |
<list> |
| 988 |
</t> |
</t> |
| 989 |
<t>Where <device-id> should be replaced by numerical ID |
<t>Where <device-id> should be replaced by numerical ID |
| 990 |
of the audio output device as e.g. returned by the |
of the audio output device as e.g. returned by the |
| 991 |
"LIST AUDIO_OUTPUT_DEVICES" command.</t> |
<xref target="LIST AUDIO_OUTPUT_DEVICES">"LIST AUDIO_OUTPUT_DEVICES"</xref> command.</t> |
| 992 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 993 |
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
| 994 |
Each answer line begins with the information category name |
Each answer line begins with the information category name |
| 1002 |
<t>DRIVER - |
<t>DRIVER - |
| 1003 |
<list> |
<list> |
| 1004 |
<t>identifier of the used audio output driver, as also |
<t>identifier of the used audio output driver, as also |
| 1005 |
returned by the "GET AVAILABLE_AUDIO_OUTPUT_DRIVERS" |
returned by the |
| 1006 |
|
<xref target="LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS"> |
| 1007 |
|
"LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS"</xref> |
| 1008 |
command</t> |
command</t> |
| 1009 |
</list> |
</list> |
| 1010 |
</t> |
</t> |
| 1033 |
order. The fields above are only those fields which are |
order. The fields above are only those fields which are |
| 1034 |
returned by all audio output devices. Every audio output driver |
returned by all audio output devices. Every audio output driver |
| 1035 |
might have its own, additional driver specific parameters (see |
might have its own, additional driver specific parameters (see |
| 1036 |
"GET AUDIO_OUTPUT_DRIVER INFO" command) which are also returned |
<xref target="GET AUDIO_OUTPUT_DRIVER INFO" />) |
| 1037 |
by this command.</t> |
which are also returned by this command.</t> |
| 1038 |
<t>Example:</t> |
<t>Example:</t> |
| 1039 |
<t> |
<t> |
| 1040 |
<list> |
<list> |
| 1052 |
</section> |
</section> |
| 1053 |
|
|
| 1054 |
|
|
| 1055 |
<section title="Changing settings of audio output devices"> |
<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> |
<t>Use the following command to alter a specific setting of a created audio output device:</t> |
| 1057 |
<t> |
<t> |
| 1058 |
<list> |
<list> |
| 1060 |
</list> |
</list> |
| 1061 |
</t> |
</t> |
| 1062 |
<t>Where <device-id> should be replaced by the numerical ID of the |
<t>Where <device-id> should be replaced by the numerical ID of the |
| 1063 |
audio output device, <key> by the name of the parameter to change |
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, <key> by the name of the parameter to change |
| 1067 |
and <value> by the new value for this parameter.</t> |
and <value> by the new value for this parameter.</t> |
| 1068 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 1069 |
<t> |
<t> |
| 1097 |
</t> |
</t> |
| 1098 |
</section> |
</section> |
| 1099 |
|
|
| 1100 |
<section title="Getting information about an audio channel"> |
<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> |
<t>Use the following command to get information about an audio channel:</t> |
| 1102 |
<t> |
<t> |
| 1103 |
<list> |
<list> |
| 1104 |
<t>GET AUDIO_OUTPUT_CHANNEL INFO <device-id> <audio-chan></t> |
<t>GET AUDIO_OUTPUT_CHANNEL INFO <device-id> <audio-chan></t> |
| 1105 |
</list> |
</list> |
| 1106 |
</t> |
</t> |
| 1107 |
<t>Where <device-id> is the numerical ID of the audio output device |
<t>Where <device-id> is the numerical ID of the audio output device as given by the |
| 1108 |
and <audio-chan> the audio channel number.</t> |
<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 <audio-chan> the audio channel number.</t> |
| 1111 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 1112 |
<t> |
<t> |
| 1113 |
<list> |
<list> |
| 1197 |
</t> |
</t> |
| 1198 |
</section> |
</section> |
| 1199 |
|
|
| 1200 |
<section title="Getting information about specific audio channel parameter"> |
<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> |
<t>Use the following command to get detailed information about specific audio channel parameter:</t> |
| 1202 |
|
|
| 1203 |
<t> |
<t> |
| 1206 |
</list> |
</list> |
| 1207 |
</t> |
</t> |
| 1208 |
|
|
| 1209 |
<t>Where <dev-id> is the numerical ID of the audio output device as returned |
<t>Where <dev-id> is the numerical ID of the audio output device as returned by the |
| 1210 |
by the "GET AUDIO_OUTPUT_DEVICES" command, <chan> the audio channel number |
<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, <chan> the audio channel number |
| 1213 |
and <param> a specific channel parameter name for which information should |
and <param> a specific channel parameter name for which information should |
| 1214 |
be obtained (as returned by the "GET AUDIO_OUTPUT_CHANNEL INFO" command).</t> |
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> |
<t>Possible Answers:</t> |
| 1217 |
|
|
| 1218 |
<t> |
<t> |
| 1303 |
</t> |
</t> |
| 1304 |
</section> |
</section> |
| 1305 |
|
|
| 1306 |
<section title="Changing settings of audio output channels"> |
<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> |
<t>Use the following command to alter a specific setting of an audio output channel:</t> |
| 1308 |
<t> |
<t> |
| 1309 |
<list> |
<list> |
| 1310 |
<t>SET AUDIO_OUTPUT_CHANNEL_PARAMETER <dev-id> <chn> <key>=<value></t> |
<t>SET AUDIO_OUTPUT_CHANNEL_PARAMETER <dev-id> <chn> <key>=<value></t> |
| 1311 |
</list> |
</list> |
| 1312 |
</t> |
</t> |
| 1313 |
<t>Where <dev-id> should be replaced by the numerical ID of the audio |
<t>Where <dev-id> should be replaced by the numerical ID of the audio output device as returned by the |
| 1314 |
device, <chn> by the audio channel number, <key> by the name of the |
<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, <chn> by the audio channel number, <key> by the name of the |
| 1317 |
parameter to change and <value> by the new value for this parameter.</t> |
parameter to change and <value> by the new value for this parameter.</t> |
| 1318 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 1319 |
<t> |
<t> |
| 1381 |
showing how to retrieve what parameters drivers are offering, how to retrieve their |
showing how to retrieve what parameters drivers are offering, how to retrieve their |
| 1382 |
possible values, etc.</t> |
possible values, etc.</t> |
| 1383 |
|
|
| 1384 |
<section title="Getting all available MIDI input drivers"> |
<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 |
<t>Use the following command to list all MIDI input drivers currently available |
| 1411 |
for the LinuxSampler instance:</t> |
for the LinuxSampler instance:</t> |
| 1412 |
<t> |
<t> |
| 1413 |
<list> |
<list> |
| 1414 |
<t>GET AVAILABLE_MIDI_INPUT_DRIVERS</t> |
<t>LIST AVAILABLE_MIDI_INPUT_DRIVERS</t> |
| 1415 |
</list> |
</list> |
| 1416 |
</t> |
</t> |
| 1417 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 1424 |
<t>Example:</t> |
<t>Example:</t> |
| 1425 |
<t> |
<t> |
| 1426 |
<list> |
<list> |
| 1427 |
<t>C: "GET AVAILABLE_MIDI_INPUT_DRIVERS"</t> |
<t>C: "LIST AVAILABLE_MIDI_INPUT_DRIVERS"</t> |
| 1428 |
<t>S: "ALSA,JACK"</t> |
<t>S: "ALSA,JACK"</t> |
| 1429 |
</list> |
</list> |
| 1430 |
</t> |
</t> |
| 1431 |
</section> |
</section> |
| 1432 |
|
|
| 1433 |
<section title="Getting information about a specific MIDI input driver"> |
<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> |
<t>Use the following command to get detailed information about a specific MIDI input driver:</t> |
| 1435 |
<t> |
<t> |
| 1436 |
<list> |
<list> |
| 1437 |
<t>GET MIDI_INPUT_DRIVER INFO <midi-input-driver></t> |
<t>GET MIDI_INPUT_DRIVER INFO <midi-input-driver></t> |
| 1438 |
</list> |
</list> |
| 1439 |
</t> |
</t> |
| 1440 |
<t>Where <midi-input-driver> is the name of the MIDI input driver.</t> |
<t>Where <midi-input-driver> 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> |
<t>Possible Answers:</t> |
| 1444 |
<t> |
<t> |
| 1445 |
<list> |
<list> |
| 1486 |
</t> |
</t> |
| 1487 |
</section> |
</section> |
| 1488 |
|
|
| 1489 |
<section title="Getting information about specific MIDI input driver parameter"> |
<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> |
<t>Use the following command to get detailed information about a specific parameter of a specific MIDI input driver:</t> |
| 1491 |
<t> |
<t> |
| 1492 |
<list> |
<list> |
| 1494 |
</list> |
</list> |
| 1495 |
</t> |
</t> |
| 1496 |
|
|
| 1497 |
<t>Where <midi-t> is the name of the MIDI input driver as returned |
<t>Where <midit> is the name of the MIDI input driver as returned |
| 1498 |
by the "GET AVAILABLE_MIDI_INPUT_DRIVERS" command, <param> a specific |
by the <xref target="LIST AVAILABLE_MIDI_INPUT_DRIVERS"> |
| 1499 |
|
"LIST AVAILABLE_MIDI_INPUT_DRIVERS"</xref> command, <param> a specific |
| 1500 |
parameter name for which information should be obtained (as returned by the |
parameter name for which information should be obtained (as returned by the |
| 1501 |
"GET MIDI_INPUT_DRIVER INFO" command) and <deplist> is an optional list |
<xref target="GET MIDI_INPUT_DRIVER INFO"> |
| 1502 |
|
"GET MIDI_INPUT_DRIVER INFO"</xref> command) and <deplist> is an optional list |
| 1503 |
of parameters on which the sought parameter <param> depends on, |
of parameters on which the sought parameter <param> depends on, |
| 1504 |
<deplist> is a key-value pair list in form of "key1=val1 key2=val2 ...", |
<deplist> is a key-value pair list in form of "key1=val1 key2=val2 ...", |
| 1505 |
where character string values are encapsulated into apostrophes ('). Arguments |
where character string values are encapsulated into apostrophes ('). Arguments |
| 1540 |
<list> |
<list> |
| 1541 |
<t>either true or false, defines if this parameter must be |
<t>either true or false, defines if this parameter must be |
| 1542 |
given when the device is to be created with the |
given when the device is to be created with the |
| 1543 |
'CREATE MIDI_INPUT_DEVICE' command |
<xref target="CREATE MIDI_INPUT_DEVICE"> |
| 1544 |
|
'CREATE MIDI_INPUT_DEVICE'</xref> command |
| 1545 |
(always returned, no matter which driver parameter)</t> |
(always returned, no matter which driver parameter)</t> |
| 1546 |
</list> |
</list> |
| 1547 |
</t> |
</t> |
| 1550 |
<list> |
<list> |
| 1551 |
<t>either true or false, if false then this parameter can |
<t>either true or false, if false then this parameter can |
| 1552 |
be changed at any time, once the device is created by |
be changed at any time, once the device is created by |
| 1553 |
the 'CREATE MIDI_INPUT_DEVICE' command |
the <xref target="CREATE MIDI_INPUT_DEVICE"> |
| 1554 |
|
'CREATE MIDI_INPUT_DEVICE'</xref> command |
| 1555 |
(always returned, no matter which driver parameter)</t> |
(always returned, no matter which driver parameter)</t> |
| 1556 |
</list> |
</list> |
| 1557 |
</t> |
</t> |
| 1567 |
|
|
| 1568 |
<t>DEPENDS - |
<t>DEPENDS - |
| 1569 |
<list> |
<list> |
| 1570 |
<t>comma separated list of paramters this parameter depends |
<t>comma separated list of parameters this parameter depends |
| 1571 |
on, means the values for fields 'DEFAULT', 'RANGE_MIN', |
on, means the values for fields 'DEFAULT', 'RANGE_MIN', |
| 1572 |
'RANGE_MAX' and 'POSSIBILITIES' might depend on these |
'RANGE_MAX' and 'POSSIBILITIES' might depend on these |
| 1573 |
listed parameters, for example assuming that an audio |
listed parameters, for example assuming that an audio |
| 1584 |
<list> |
<list> |
| 1585 |
<t>reflects the default value for this parameter which is |
<t>reflects the default value for this parameter which is |
| 1586 |
used when the device is created and not explicitly |
used when the device is created and not explicitly |
| 1587 |
given with the 'CREATE MIDI_INPUT_DEVICE' command, |
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 |
in case of MULTIPLCITY=true, this is a comma separated |
| 1590 |
list, that's why character strings are encapsulated into |
list, that's why character strings are encapsulated into |
| 1591 |
apostrophes (') |
apostrophes (') |
| 1641 |
</t> |
</t> |
| 1642 |
</section> |
</section> |
| 1643 |
|
|
| 1644 |
<section title="Creating a MIDI input device"> |
<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> |
<t>Use the following command to create a new MIDI input device for the desired MIDI input system:</t> |
| 1646 |
<t> |
<t> |
| 1647 |
<list> |
<list> |
| 1649 |
</list> |
</list> |
| 1650 |
</t> |
</t> |
| 1651 |
|
|
| 1652 |
<t>Where <midi-input-driver> should be replaced by the desired MIDI input system and <param-list> by an |
<t>Where <midi-input-driver> 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 <param-list> by an |
| 1655 |
optional list of driver specific parameters in form of "key1=val1 key2=val2 ...", where |
optional list of driver specific parameters in form of "key1=val1 key2=val2 ...", where |
| 1656 |
character string values should be encapsulated into apostrophes ('). |
character string values should be encapsulated into apostrophes ('). |
| 1657 |
Note that there might be drivers which require parameter(s) to be |
Note that there might be drivers which require parameter(s) to be |
| 1691 |
</t> |
</t> |
| 1692 |
</section> |
</section> |
| 1693 |
|
|
| 1694 |
<section title="Destroying a MIDI input device"> |
<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> |
<t>Use the following command to destroy a created MIDI input device:</t> |
| 1696 |
<t> |
<t> |
| 1697 |
<list> |
<list> |
| 1698 |
<t>DESTROY MIDI_INPUT_DEVICE <device-id></t> |
<t>DESTROY MIDI_INPUT_DEVICE <device-id></t> |
| 1699 |
</list> |
</list> |
| 1700 |
</t> |
</t> |
| 1701 |
<t>Where <device-id> should be replaced by the device's numerical ID.</t> |
<t>Where <device-id> 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> |
<t>Possible Answers:</t> |
| 1706 |
<t> |
<t> |
| 1707 |
<list> |
<list> |
| 1733 |
</t> |
</t> |
| 1734 |
</section> |
</section> |
| 1735 |
|
|
| 1736 |
<section title="Getting all created MIDI input device count"> |
<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> |
<t>Use the following command to count all created MIDI input devices:</t> |
| 1738 |
<t> |
<t> |
| 1739 |
<list> |
<list> |
| 1757 |
</section> |
</section> |
| 1758 |
|
|
| 1759 |
|
|
| 1760 |
<section title="Getting all created MIDI input device list"> |
<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> |
<t>Use the following command to list all created MIDI input devices:</t> |
| 1762 |
<t> |
<t> |
| 1763 |
<list> |
<list> |
| 1786 |
</t> |
</t> |
| 1787 |
</section> |
</section> |
| 1788 |
|
|
| 1789 |
<section title="Getting current settings of a MIDI input device"> |
<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> |
<t>Use the following command to get current settings of a specific, created MIDI input device:</t> |
| 1791 |
<t> |
<t> |
| 1792 |
<list> |
<list> |
| 1793 |
<t>GET MIDI_INPUT_DEVICE INFO <device-id></t> |
<t>GET MIDI_INPUT_DEVICE INFO <device-id></t> |
| 1794 |
</list> |
</list> |
| 1795 |
</t> |
</t> |
| 1796 |
<t>Where <device-id> is the numerical ID of the MIDI input device.</t> |
<t>Where <device-id> 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> |
<t>Possible Answers:</t> |
| 1801 |
<t> |
<t> |
| 1802 |
<list> |
<list> |
| 1813 |
<t>DRIVER - |
<t>DRIVER - |
| 1814 |
<list> |
<list> |
| 1815 |
<t>identifier of the used MIDI input driver, as e.g. |
<t>identifier of the used MIDI input driver, as e.g. |
| 1816 |
returned by the "GET AVAILABLE_MIDI_INPUT_DRIVERS" |
returned by the <xref target="LIST AVAILABLE_MIDI_INPUT_DRIVERS"> |
| 1817 |
|
"LIST AVAILABLE_MIDI_INPUT_DRIVERS"</xref> |
| 1818 |
command</t> |
command</t> |
| 1819 |
</list> |
</list> |
| 1820 |
</t> |
</t> |
| 1837 |
order. The fields above are only those fields which are |
order. The fields above are only those fields which are |
| 1838 |
returned by all MIDI input devices. Every MIDI input driver |
returned by all MIDI input devices. Every MIDI input driver |
| 1839 |
might have its own, additional driver specific parameters (see |
might have its own, additional driver specific parameters (see |
| 1840 |
"GET MIDI_INPUT_DRIVER INFO" command) which are also returned |
<xref target="GET MIDI_INPUT_DRIVER INFO"> |
| 1841 |
|
"GET MIDI_INPUT_DRIVER INFO"</xref> command) which are also returned |
| 1842 |
by this command.</t> |
by this command.</t> |
| 1843 |
|
|
| 1844 |
<t>Example:</t> |
<t>Example:</t> |
| 1852 |
</t> |
</t> |
| 1853 |
</section> |
</section> |
| 1854 |
|
|
| 1855 |
<section title="Changing settings of MIDI input devices"> |
<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> |
<t>Use the following command to alter a specific setting of a created MIDI input device:</t> |
| 1857 |
<t> |
<t> |
| 1858 |
<list> |
<list> |
| 1861 |
</t> |
</t> |
| 1862 |
|
|
| 1863 |
<t>Where <device-id> should be replaced by the numerical ID of the |
<t>Where <device-id> should be replaced by the numerical ID of the |
| 1864 |
MIDI input device, <key> by the name of the parameter to change and |
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, <key> by the name of the parameter to change and |
| 1868 |
<value> by the new value for this parameter.</t> |
<value> by the new value for this parameter.</t> |
| 1869 |
|
|
| 1870 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 1898 |
</t> |
</t> |
| 1899 |
</section> |
</section> |
| 1900 |
|
|
| 1901 |
<section title="Getting information about a MIDI port"> |
<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> |
<t>Use the following command to get information about a MIDI port:</t> |
| 1903 |
<t> |
<t> |
| 1904 |
<list> |
<list> |
| 1905 |
<t>GET MIDI_INPUT_PORT INFO <device-id> <midi-port></t> |
<t>GET MIDI_INPUT_PORT INFO <device-id> <midi-port></t> |
| 1906 |
</list> |
</list> |
| 1907 |
</t> |
</t> |
| 1908 |
<t>Where <device-id> is the numerical ID of the MIDI input device |
<t>Where <device-id> is the numerical ID of the MIDI input device as returned by the |
| 1909 |
and <midi-port> the MIDI input port number.</t> |
<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 <midi-port> the MIDI input port number.</t> |
| 1912 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 1913 |
<t> |
<t> |
| 1914 |
<list> |
<list> |
| 1942 |
</t> |
</t> |
| 1943 |
</section> |
</section> |
| 1944 |
|
|
| 1945 |
<section title="Getting information about specific MIDI port parameter"> |
<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> |
<t>Use the following command to get detailed information about specific MIDI port parameter:</t> |
| 1947 |
<t> |
<t> |
| 1948 |
<list> |
<list> |
| 1950 |
</list> |
</list> |
| 1951 |
</t> |
</t> |
| 1952 |
|
|
| 1953 |
<t>Where <dev-id> is the numerical ID of the MIDI input device as returned |
<t>Where <dev-id> is the numerical ID of the MIDI input device as returned by the |
| 1954 |
by the "LIST MIDI_INPUT_DEVICES" command, <port> the MIDI port number and |
<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, <port> the MIDI port number and |
| 1957 |
<param> a specific port parameter name for which information should be |
<param> a specific port parameter name for which information should be |
| 1958 |
obtained (as returned by the "GET MIDI_INPUT_PORT INFO" command).</t> |
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> |
<t>Possible Answers:</t> |
| 1962 |
<t> |
<t> |
| 2047 |
</t> |
</t> |
| 2048 |
</section> |
</section> |
| 2049 |
|
|
| 2050 |
<section title="Changing settings of MIDI input ports"> |
<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> |
<t>Use the following command to alter a specific setting of a MIDI input port:</t> |
| 2052 |
<t> |
<t> |
| 2053 |
<list> |
<list> |
| 2056 |
</t> |
</t> |
| 2057 |
|
|
| 2058 |
<t>Where <device-id> should be replaced by the numerical ID of the |
<t>Where <device-id> should be replaced by the numerical ID of the |
| 2059 |
MIDI device, <port> by the MIDI port number, <key> by the name of |
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, <port> by the MIDI port number, <key> by the name of |
| 2063 |
the parameter to change and <value> by the new value for this |
the parameter to change and <value> by the new value for this |
| 2064 |
parameter.</t> |
parameter.</t> |
| 2065 |
|
|
| 2095 |
</section> |
</section> |
| 2096 |
|
|
| 2097 |
<section title="Configuring sampler channels"> |
<section title="Configuring sampler channels"> |
| 2098 |
<t>The following commands describe how to add and remove sampler channels, deploy |
<t>The following commands describe how to add and remove sampler channels, associate a |
| 2099 |
sampler engines, load instruments and connect sampler channels to MIDI and audio devices.</t> |
sampler channel with a sampler engine, load instruments and connect sampler channels to |
| 2100 |
|
MIDI and audio devices.</t> |
| 2101 |
|
|
| 2102 |
<section title="Loading an instrument"> |
<section title="Loading an instrument" anchor="LOAD INSTRUMENT"> |
| 2103 |
<t>An instrument file can be loaded and assigned to a sampler channel by one of the following commands:</t> |
<t>An instrument file can be loaded and assigned to a sampler channel by one of the following commands:</t> |
| 2104 |
<t> |
<t> |
| 2105 |
<list> |
<list> |
| 2113 |
number of the sampler channel the instrument should be assigned to. |
number of the sampler channel the instrument should be assigned to. |
| 2114 |
Each sampler channel can only have one instrument.</t> |
Each sampler channel can only have one instrument.</t> |
| 2115 |
|
|
| 2116 |
|
<t>Notice: since LSCP 1.2 the <filename> argument supports |
| 2117 |
|
escape characters for special characters (see chapter |
| 2118 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>" |
| 2119 |
|
for details) and accordingly backslash characters in the filename |
| 2120 |
|
MUST now be escaped as well!</t> |
| 2121 |
|
|
| 2122 |
<t>The difference between regular and NON_MODAL versions of the command |
<t>The difference between regular and NON_MODAL versions of the command |
| 2123 |
is that the regular command returns OK only after the instrument has been |
is that the regular command returns OK only after the instrument has been |
| 2124 |
fully loaded and the channel is ready to be used while NON_MODAL version |
fully loaded and the channel is ready to be used while NON_MODAL version |
| 2125 |
returns immediately and a background process is launched to load the instrument |
returns immediately and a background process is launched to load the instrument |
| 2126 |
on the channel. GET CHANNEL INFO command can be used to obtain loading |
on the channel. The <xref target="GET CHANNEL INFO">GET CHANNEL INFO</xref> |
| 2127 |
|
command can be used to obtain loading |
| 2128 |
progress from INSTRUMENT_STATUS field. LOAD command will perform sanity checks |
progress from INSTRUMENT_STATUS field. LOAD command will perform sanity checks |
| 2129 |
such as making sure that the file could be read and it is of a proper format |
such as making sure that the file could be read and it is of a proper format |
| 2130 |
and SHOULD return ERR and SHOULD not launch the background process should any |
and SHOULD return ERR and SHOULD not launch the background process should any |
| 2162 |
</t> |
</t> |
| 2163 |
</section> |
</section> |
| 2164 |
|
|
| 2165 |
<section title="Loading a sampler engine"> |
<section title="Loading a sampler engine" anchor="LOAD ENGINE"> |
| 2166 |
<t>A sample engine can be deployed and assigned to a specific sampler |
<t>A sampler engine type can be associated to a specific sampler |
| 2167 |
channel by the following command:</t> |
channel by the following command:</t> |
| 2168 |
<t> |
<t> |
| 2169 |
<list> |
<list> |
| 2172 |
</t> |
</t> |
| 2173 |
|
|
| 2174 |
<t>Where <engine-name> is an engine name as obtained by the |
<t>Where <engine-name> is an engine name as obtained by the |
| 2175 |
"GET AVAILABLE_ENGINES" command and <sampler-channel> the sampler channel the |
<xref target="LIST AVAILABLE_ENGINES"> |
| 2176 |
deployed engine should be assigned to. Even if the respective |
"LIST AVAILABLE_ENGINES"</xref> command and <sampler-channel> |
| 2177 |
sampler channel has already a deployed engine with that engine |
the sampler channel as returned by the |
| 2178 |
name, a new engine instance will be assigned to the sampler channel.</t> |
<xref target="ADD CHANNEL">"ADD CHANNEL"</xref> or |
| 2179 |
|
<xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command where |
| 2180 |
|
the engine type should be assigned to. This command should be issued |
| 2181 |
|
after adding a new sampler channel and before any other control |
| 2182 |
|
commands on the new sampler channel. It can also be used to change |
| 2183 |
|
the engine type of a sampler channel. This command has (currently) no |
| 2184 |
|
way to define or force if a new engine instance should be created and |
| 2185 |
|
assigned to the given sampler channel or if an already existing |
| 2186 |
|
instance of that engine type, shared with other sampler channels, |
| 2187 |
|
should be used.</t> |
| 2188 |
|
|
| 2189 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2190 |
<t> |
<t> |
| 2217 |
</t> |
</t> |
| 2218 |
</section> |
</section> |
| 2219 |
|
|
| 2220 |
<section title="Getting all created sampler channel count"> |
<section title="Getting all created sampler channel count" anchor="GET CHANNELS"> |
| 2221 |
<t>The number of sampler channels can change on runtime. To get the |
<t>The number of sampler channels can change on runtime. To get the |
| 2222 |
current amount of sampler channels, the front-end can send the |
current amount of sampler channels, the front-end can send the |
| 2223 |
following command:</t> |
following command:</t> |
| 2241 |
</t> |
</t> |
| 2242 |
</section> |
</section> |
| 2243 |
|
|
| 2244 |
<section title="Getting all created sampler channel list"> |
<section title="Getting all created sampler channel list" anchor="LIST CHANNELS"> |
| 2245 |
<t>The number of sampler channels can change on runtime. To get the |
<t>The number of sampler channels can change on runtime. To get the |
| 2246 |
current list of sampler channels, the front-end can send the |
current list of sampler channels, the front-end can send the |
| 2247 |
following command:</t> |
following command:</t> |
| 2266 |
</t> |
</t> |
| 2267 |
</section> |
</section> |
| 2268 |
|
|
| 2269 |
<section title="Adding a new sampler channel"> |
<section title="Adding a new sampler channel" anchor="ADD CHANNEL"> |
| 2270 |
<t>A new sampler channel can be added to the end of the sampler |
<t>A new sampler channel can be added to the end of the sampler |
| 2271 |
channel list by sending the following command:</t> |
channel list by sending the following command:</t> |
| 2272 |
<t> |
<t> |
| 2290 |
<list> |
<list> |
| 2291 |
<t>in case a new sampler channel could be added, where |
<t>in case a new sampler channel could be added, where |
| 2292 |
<sampler-channel> reflects the channel number of the new |
<sampler-channel> reflects the channel number of the new |
| 2293 |
created sampler channel which should the be used to set up |
created sampler channel which should be used to set up |
| 2294 |
the sampler channel by sending subsequent intialization |
the sampler channel by sending subsequent initialization |
| 2295 |
commands</t> |
commands</t> |
| 2296 |
</list> |
</list> |
| 2297 |
</t> |
</t> |
| 2318 |
</t> |
</t> |
| 2319 |
</section> |
</section> |
| 2320 |
|
|
| 2321 |
<section title="Removing a sampler channel"> |
<section title="Removing a sampler channel" anchor="REMOVE CHANNEL"> |
| 2322 |
<t>A sampler channel can be removed by sending the following command:</t> |
<t>A sampler channel can be removed by sending the following command:</t> |
| 2323 |
<t> |
<t> |
| 2324 |
<list> |
<list> |
| 2326 |
</list> |
</list> |
| 2327 |
</t> |
</t> |
| 2328 |
|
|
| 2329 |
<t>This will decrement the sampler channel count by one and also |
<t>Where <sampler-channel> should be replaced by the |
| 2330 |
decrement the channel numbers of all subsequent sampler channels by |
number of the sampler channel as given by the |
| 2331 |
one.</t> |
<xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2332 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> |
| 2333 |
|
command. The channel numbers of all subsequent sampler channels |
| 2334 |
|
remain the same.</t> |
| 2335 |
|
|
| 2336 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2337 |
<t> |
<t> |
| 2364 |
</t> |
</t> |
| 2365 |
</section> |
</section> |
| 2366 |
|
|
| 2367 |
<section title="Getting all available engines"> |
<section title="Getting amount of available engines" anchor="GET AVAILABLE_ENGINES"> |
| 2368 |
<t>The front-end can ask for all available engines by sending the following command:</t> |
<t>The front-end can ask for the number of available engines by sending the following command:</t> |
| 2369 |
<t> |
<t> |
| 2370 |
<list> |
<list> |
| 2371 |
<t>GET AVAILABLE_ENGINES</t> |
<t>GET AVAILABLE_ENGINES</t> |
| 2374 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2375 |
<t> |
<t> |
| 2376 |
<list> |
<list> |
| 2377 |
<t>LinuxSampler will answer by sending a comma separated character |
<t>LinuxSampler will answer by sending the number of available engines.</t> |
|
string of the engines' names. Engine names can consist of lower and |
|
|
upper cases, digits and underlines ("_" character).</t> |
|
| 2378 |
</list> |
</list> |
| 2379 |
</t> |
</t> |
| 2380 |
<t>Example:</t> |
<t>Example:</t> |
| 2381 |
<t> |
<t> |
| 2382 |
<list> |
<list> |
| 2383 |
<t>C: "GET AVAILABLE_ENGINES"</t> |
<t>C: "GET AVAILABLE_ENGINES"</t> |
| 2384 |
<t>S: "GigEngine,AkaiEngine,DLSEngine,JoesCustomEngine"</t> |
<t>S: "4"</t> |
| 2385 |
</list> |
</list> |
| 2386 |
</t> |
</t> |
| 2387 |
</section> |
</section> |
| 2388 |
|
|
| 2389 |
<section title="Getting information about an engine"> |
<section title="Getting all available engines" anchor="LIST AVAILABLE_ENGINES"> |
| 2390 |
|
<t>The front-end can ask for a list of all available engines by sending the following command:</t> |
| 2391 |
|
<t> |
| 2392 |
|
<list> |
| 2393 |
|
<t>LIST AVAILABLE_ENGINES</t> |
| 2394 |
|
</list> |
| 2395 |
|
</t> |
| 2396 |
|
<t>Possible Answers:</t> |
| 2397 |
|
<t> |
| 2398 |
|
<list> |
| 2399 |
|
<t>LinuxSampler will answer by sending a comma separated list |
| 2400 |
|
of the engines' names encapsulated into apostrophes ('). |
| 2401 |
|
Engine names can consist of lower and upper cases, |
| 2402 |
|
digits and underlines ("_" character).</t> |
| 2403 |
|
</list> |
| 2404 |
|
</t> |
| 2405 |
|
<t>Example:</t> |
| 2406 |
|
<t> |
| 2407 |
|
<list> |
| 2408 |
|
<t>C: "LIST AVAILABLE_ENGINES"</t> |
| 2409 |
|
<t>S: "'GigEngine','AkaiEngine','DLSEngine','JoesCustomEngine'"</t> |
| 2410 |
|
</list> |
| 2411 |
|
</t> |
| 2412 |
|
</section> |
| 2413 |
|
|
| 2414 |
|
<section title="Getting information about an engine" anchor="GET ENGINE INFO"> |
| 2415 |
<t>The front-end can ask for information about a specific engine by |
<t>The front-end can ask for information about a specific engine by |
| 2416 |
sending the following command:</t> |
sending the following command:</t> |
| 2417 |
<t> |
<t> |
| 2420 |
</list> |
</list> |
| 2421 |
</t> |
</t> |
| 2422 |
<t>Where <engine-name> is an engine name as obtained by the |
<t>Where <engine-name> is an engine name as obtained by the |
| 2423 |
"GET AVAILABLE_ENGINES" command.</t> |
<xref target="LIST AVAILABLE_ENGINES"> |
| 2424 |
|
"LIST AVAILABLE_ENGINES"</xref> command.</t> |
| 2425 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2426 |
<t> |
<t> |
| 2427 |
<list> |
<list> |
| 2461 |
</t> |
</t> |
| 2462 |
</section> |
</section> |
| 2463 |
|
|
| 2464 |
<section title="Getting sampler channel information"> |
<section title="Getting sampler channel information" anchor="GET CHANNEL INFO"> |
| 2465 |
<t>The front-end can ask for the current settings of a sampler channel |
<t>The front-end can ask for the current settings of a sampler channel |
| 2466 |
by sending the following command:</t> |
by sending the following command:</t> |
| 2467 |
<t> |
<t> |
| 2469 |
<t>GET CHANNEL INFO <sampler-channel></t> |
<t>GET CHANNEL INFO <sampler-channel></t> |
| 2470 |
</list> |
</list> |
| 2471 |
</t> |
</t> |
| 2472 |
<t>Where <sampler-channel> is the sampler channel number the front-end is interested in.</t> |
<t>Where <sampler-channel> is the sampler channel number the front-end is interested in |
| 2473 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2474 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 2475 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2476 |
<t> |
<t> |
| 2477 |
<list> |
<list> |
| 2485 |
<list> |
<list> |
| 2486 |
<t>ENGINE_NAME - |
<t>ENGINE_NAME - |
| 2487 |
<list> |
<list> |
| 2488 |
<t>name of the engine that is deployed on the sampler |
<t>name of the engine that is associated with the sampler |
| 2489 |
channel, "NONE" if there's no engine deployed yet for |
channel, "NONE" if there's no engine associated yet for |
| 2490 |
this sampler channel</t> |
this sampler channel</t> |
| 2491 |
</list> |
</list> |
| 2492 |
</t> |
</t> |
| 2561 |
<t>VOLUME - |
<t>VOLUME - |
| 2562 |
<list> |
<list> |
| 2563 |
<t>optionally dotted number for the channel volume factor |
<t>optionally dotted number for the channel volume factor |
| 2564 |
(where a value < 1.0 means attenuation and a value > |
(where a value < 1.0 means attenuation and a value > |
| 2565 |
1.0 means amplification)</t> |
1.0 means amplification)</t> |
| 2566 |
</list> |
</list> |
| 2567 |
</t> |
</t> |
| 2568 |
|
<t>MUTE - |
| 2569 |
|
<list> |
| 2570 |
|
<t>Determines whether the channel is muted, "true" if the |
| 2571 |
|
channel is muted, "false" if the channel is not muted, and |
| 2572 |
|
"MUTED_BY_SOLO" if the channel is muted because of the |
| 2573 |
|
presence of a solo channel and will be unmuted when |
| 2574 |
|
there are no solo channels left</t> |
| 2575 |
|
</list> |
| 2576 |
|
</t> |
| 2577 |
|
<t>SOLO - |
| 2578 |
|
<list> |
| 2579 |
|
<t>Determines whether this is a solo channel, "true" if |
| 2580 |
|
the channel is a solo channel; "false" otherwise</t> |
| 2581 |
|
</list> |
| 2582 |
|
</t> |
| 2583 |
|
<t>MIDI_INSTRUMENT_MAP - |
| 2584 |
|
<list> |
| 2585 |
|
<t>Determines to which MIDI instrument map this sampler |
| 2586 |
|
channel is assigned to. Read chapter |
| 2587 |
|
<xref target="SET CHANNEL MIDI_INSTRUMENT_MAP">"SET CHANNEL MIDI_INSTRUMENT_MAP"</xref> |
| 2588 |
|
for a list of possible values.</t> |
| 2589 |
|
</list> |
| 2590 |
|
</t> |
| 2591 |
</list> |
</list> |
| 2592 |
</t> |
</t> |
| 2593 |
</list> |
</list> |
| 2610 |
<t> "MIDI_INPUT_DEVICE: 0"</t> |
<t> "MIDI_INPUT_DEVICE: 0"</t> |
| 2611 |
<t> "MIDI_INPUT_PORT: 0"</t> |
<t> "MIDI_INPUT_PORT: 0"</t> |
| 2612 |
<t> "MIDI_INPUT_CHANNEL: 5"</t> |
<t> "MIDI_INPUT_CHANNEL: 5"</t> |
| 2613 |
|
<t> "VOLUME: 1.0"</t> |
| 2614 |
|
<t> "MUTE: false"</t> |
| 2615 |
|
<t> "SOLO: false"</t> |
| 2616 |
|
<t> "MIDI_INSTRUMENT_MAP: NONE"</t> |
| 2617 |
<t> "."</t> |
<t> "."</t> |
| 2618 |
</list> |
</list> |
| 2619 |
</t> |
</t> |
| 2620 |
</section> |
</section> |
| 2621 |
|
|
| 2622 |
<section title="Current number of active voices"> |
<section title="Current number of active voices" anchor="GET CHANNEL VOICE_COUNT"> |
| 2623 |
<t>The front-end can ask for the current number of active voices on a |
<t>The front-end can ask for the current number of active voices on a |
| 2624 |
sampler channel by sending the following command:</t> |
sampler channel by sending the following command:</t> |
| 2625 |
<t> |
<t> |
| 2627 |
<t>GET CHANNEL VOICE_COUNT <sampler-channel></t> |
<t>GET CHANNEL VOICE_COUNT <sampler-channel></t> |
| 2628 |
</list> |
</list> |
| 2629 |
</t> |
</t> |
| 2630 |
<t>Where <sampler-channel> is the sampler channel number the front-end is interested in.</t> |
<t>Where <sampler-channel> is the sampler channel number the front-end is interested in |
| 2631 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2632 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 2633 |
|
|
| 2634 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2635 |
<t> |
<t> |
| 2646 |
</t> |
</t> |
| 2647 |
</section> |
</section> |
| 2648 |
|
|
| 2649 |
<section title="Current number of active disk streams"> |
<section title="Current number of active disk streams" anchor="GET CHANNEL STREAM_COUNT"> |
| 2650 |
<t>The front-end can ask for the current number of active disk streams |
<t>The front-end can ask for the current number of active disk streams |
| 2651 |
on a sampler channel by sending the following command:</t> |
on a sampler channel by sending the following command:</t> |
| 2652 |
<t> |
<t> |
| 2654 |
<t>GET CHANNEL STREAM_COUNT <sampler-channel></t> |
<t>GET CHANNEL STREAM_COUNT <sampler-channel></t> |
| 2655 |
</list> |
</list> |
| 2656 |
</t> |
</t> |
| 2657 |
<t>Where <sampler-channel> is the sampler channel number the front-end is interested in.</t> |
<t>Where <sampler-channel> is the sampler channel number the front-end is interested in |
| 2658 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2659 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 2660 |
|
|
| 2661 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2662 |
<t> |
<t> |
| 2675 |
</t> |
</t> |
| 2676 |
</section> |
</section> |
| 2677 |
|
|
| 2678 |
<section title="Current fill state of disk stream buffers"> |
<section title="Current fill state of disk stream buffers" anchor="GET CHANNEL BUFFER_FILL"> |
| 2679 |
<t>The front-end can ask for the current fill state of all disk streams |
<t>The front-end can ask for the current fill state of all disk streams |
| 2680 |
on a sampler channel by sending the following command:</t> |
on a sampler channel by sending the following command:</t> |
| 2681 |
<t> |
<t> |
| 2690 |
</list> |
</list> |
| 2691 |
</t> |
</t> |
| 2692 |
<t>to get the fill state in percent, where <sampler-channel> is the |
<t>to get the fill state in percent, where <sampler-channel> is the |
| 2693 |
sampler channel number the front-end is interested in.</t> |
sampler channel number the front-end is interested in |
| 2694 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2695 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 2696 |
|
|
| 2697 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2698 |
<t> |
<t> |
| 2728 |
</t> |
</t> |
| 2729 |
</section> |
</section> |
| 2730 |
|
|
| 2731 |
<section title="Setting audio output device"> |
<section title="Setting audio output device" anchor="SET CHANNEL AUDIO_OUTPUT_DEVICE"> |
| 2732 |
<t>The front-end can set the audio output device on a specific sampler |
<t>The front-end can set the audio output device on a specific sampler |
| 2733 |
channel by sending the following command:</t> |
channel by sending the following command:</t> |
| 2734 |
<t> |
<t> |
| 2736 |
<t>SET CHANNEL AUDIO_OUTPUT_DEVICE <sampler-channel> <audio-device-id></t> |
<t>SET CHANNEL AUDIO_OUTPUT_DEVICE <sampler-channel> <audio-device-id></t> |
| 2737 |
</list> |
</list> |
| 2738 |
</t> |
</t> |
| 2739 |
<t>Where <audio-device-id> is the numerical ID of the audio output |
<t>Where <sampler-channel> is the respective sampler channel |
| 2740 |
device and <sampler-channel> is the respective sampler channel |
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2741 |
number.</t> |
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and |
| 2742 |
|
<audio-device-id> is the numerical ID of the audio output device as given by the |
| 2743 |
|
<xref target="CREATE AUDIO_OUTPUT_DEVICE">"CREATE AUDIO_OUTPUT_DEVICE"</xref> |
| 2744 |
|
or <xref target="LIST AUDIO_OUTPUT_DEVICES">"LIST AUDIO_OUTPUT_DEVICES"</xref> |
| 2745 |
|
command.</t> |
| 2746 |
|
|
| 2747 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2748 |
<t> |
<t> |
| 2774 |
</t> |
</t> |
| 2775 |
</section> |
</section> |
| 2776 |
|
|
| 2777 |
<section title="Setting audio output type"> |
<section title="Setting audio output type" anchor="SET CHANNEL AUDIO_OUTPUT_TYPE"> |
| 2778 |
<t>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!</t> |
<t>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!</t> |
| 2779 |
|
|
| 2780 |
<t>The front-end can alter the audio output type on a specific sampler |
<t>The front-end can alter the audio output type on a specific sampler |
| 2817 |
</t> |
</t> |
| 2818 |
</section> |
</section> |
| 2819 |
|
|
| 2820 |
<section title="Setting audio output channel"> |
<section title="Setting audio output channel" anchor="SET CHANNEL AUDIO_OUTPUT_CHANNEL"> |
| 2821 |
<t>The front-end can alter the audio output channel on a specific |
<t>The front-end can alter the audio output channel on a specific |
| 2822 |
sampler channel by sending the following command:</t> |
sampler channel by sending the following command:</t> |
| 2823 |
<t> |
<t> |
| 2825 |
<t>SET CHANNEL AUDIO_OUTPUT_CHANNEL <sampler-chan> <audio-out> <audio-in></t> |
<t>SET CHANNEL AUDIO_OUTPUT_CHANNEL <sampler-chan> <audio-out> <audio-in></t> |
| 2826 |
</list> |
</list> |
| 2827 |
</t> |
</t> |
| 2828 |
<t>Where <sampler-chan> is the sampler channel, <audio-out> is the |
<t>Where <sampler-chan> is the sampler channel number |
| 2829 |
sampler channel's audio output channel which should be |
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2830 |
rerouted and <audio-in> the audio channel of the selected audio |
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, <audio-out> is the |
| 2831 |
|
numerical ID of the sampler channel's audio output channel which should be |
| 2832 |
|
rerouted and <audio-in> is the numerical ID of the audio channel of the selected audio |
| 2833 |
output device where <audio-out> should be routed to.</t> |
output device where <audio-out> should be routed to.</t> |
| 2834 |
|
|
| 2835 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2862 |
</t> |
</t> |
| 2863 |
</section> |
</section> |
| 2864 |
|
|
| 2865 |
<section title="Setting MIDI input device"> |
<section title="Setting MIDI input device" anchor="SET CHANNEL MIDI_INPUT_DEVICE"> |
| 2866 |
<t>The front-end can set the MIDI input device on a specific sampler |
<t>The front-end can set the MIDI input device on a specific sampler |
| 2867 |
channel by sending the following command:</t> |
channel by sending the following command:</t> |
| 2868 |
<t> |
<t> |
| 2870 |
<t>SET CHANNEL MIDI_INPUT_DEVICE <sampler-channel> <midi-device-id></t> |
<t>SET CHANNEL MIDI_INPUT_DEVICE <sampler-channel> <midi-device-id></t> |
| 2871 |
</list> |
</list> |
| 2872 |
</t> |
</t> |
| 2873 |
<t></t> |
<t>Where <sampler-channel> is the sampler channel number |
| 2874 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2875 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command |
| 2876 |
|
and <midi-device-id> is the numerical ID of the MIDI input device as returned by the |
| 2877 |
|
<xref target="CREATE MIDI_INPUT_DEVICE">"CREATE MIDI_INPUT_DEVICE"</xref> |
| 2878 |
|
or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref> command.</t> |
| 2879 |
|
|
| 2880 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2881 |
<t> |
<t> |
| 2907 |
</t> |
</t> |
| 2908 |
</section> |
</section> |
| 2909 |
|
|
| 2910 |
<section title="Setting MIDI input type"> |
<section title="Setting MIDI input type" anchor="SET CHANNEL MIDI_INPUT_TYPE"> |
| 2911 |
<t>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!</t> |
<t>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!</t> |
| 2912 |
|
|
| 2913 |
<t>The front-end can alter the MIDI input type on a specific sampler |
<t>The front-end can alter the MIDI input type on a specific sampler |
| 2950 |
</t> |
</t> |
| 2951 |
</section> |
</section> |
| 2952 |
|
|
| 2953 |
<section title="Setting MIDI input port"> |
<section title="Setting MIDI input port" anchor="SET CHANNEL MIDI_INPUT_PORT"> |
| 2954 |
<t>The front-end can alter the input MIDI port on a specific sampler |
<t>The front-end can alter the MIDI input port on a specific sampler |
| 2955 |
channel by sending the following command:</t> |
channel by sending the following command:</t> |
| 2956 |
<t> |
<t> |
| 2957 |
<list> |
<list> |
| 2979 |
</t> |
</t> |
| 2980 |
<t>"ERR:<error-code>:<error-message>" - |
<t>"ERR:<error-code>:<error-message>" - |
| 2981 |
<list> |
<list> |
| 2982 |
<t>in case it failed, providing an appropriate error code and error messag</t> |
<t>in case it failed, providing an appropriate error code and error message</t> |
| 2983 |
</list> |
</list> |
| 2984 |
</t> |
</t> |
| 2985 |
</list> |
</list> |
| 2992 |
</t> |
</t> |
| 2993 |
</section> |
</section> |
| 2994 |
|
|
| 2995 |
<section title="Setting MIDI input channel"> |
<section title="Setting MIDI input channel" anchor="SET CHANNEL MIDI_INPUT_CHANNEL"> |
| 2996 |
<t>The front-end can alter the MIDI channel a sampler channel should |
<t>The front-end can alter the MIDI channel a sampler channel should |
| 2997 |
listen to by sending the following command:</t> |
listen to by sending the following command:</t> |
| 2998 |
<t> |
<t> |
| 3000 |
<t>SET CHANNEL MIDI_INPUT_CHANNEL <sampler-channel> <midi-input-chan></t> |
<t>SET CHANNEL MIDI_INPUT_CHANNEL <sampler-channel> <midi-input-chan></t> |
| 3001 |
</list> |
</list> |
| 3002 |
</t> |
</t> |
| 3003 |
<t>Where <midi-input-chan> is the new MIDI input channel where |
<t>Where <midi-input-chan> is the number of the new MIDI input channel where |
| 3004 |
<sampler-channel> should listen to or "ALL" to listen on all 16 MIDI |
<sampler-channel> should listen to or "ALL" to listen on all 16 MIDI |
| 3005 |
channels.</t> |
channels.</t> |
| 3006 |
|
|
| 3034 |
</t> |
</t> |
| 3035 |
</section> |
</section> |
| 3036 |
|
|
| 3037 |
<section title="Setting channel volume"> |
<section title="Setting channel volume" anchor="SET CHANNEL VOLUME"> |
| 3038 |
<t>The front-end can alter the volume of a sampler channel by sending |
<t>The front-end can alter the volume of a sampler channel by sending |
| 3039 |
the following command:</t> |
the following command:</t> |
| 3040 |
<t> |
<t> |
| 3077 |
</t> |
</t> |
| 3078 |
</section> |
</section> |
| 3079 |
|
|
| 3080 |
<section title="Resetting a sampler channel"> |
<section title="Muting a sampler channel" anchor="SET CHANNEL MUTE"> |
| 3081 |
|
<t>The front-end can mute/unmute a specific sampler |
| 3082 |
|
channel by sending the following command:</t> |
| 3083 |
|
<t> |
| 3084 |
|
<list> |
| 3085 |
|
<t>SET CHANNEL MUTE <sampler-channel> <mute></t> |
| 3086 |
|
</list> |
| 3087 |
|
</t> |
| 3088 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3089 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3090 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and |
| 3091 |
|
<mute> should be replaced either by "1" to mute the channel or "0" |
| 3092 |
|
to unmute the channel.</t> |
| 3093 |
|
|
| 3094 |
|
<t>Possible Answers:</t> |
| 3095 |
|
<t> |
| 3096 |
|
<list> |
| 3097 |
|
<t>"OK" - |
| 3098 |
|
<list> |
| 3099 |
|
<t>on success</t> |
| 3100 |
|
</list> |
| 3101 |
|
</t> |
| 3102 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 3103 |
|
<list> |
| 3104 |
|
<t>if the channel was muted/unmuted, but there are noteworthy |
| 3105 |
|
issue(s) related, providing an appropriate warning code and |
| 3106 |
|
warning message</t> |
| 3107 |
|
</list> |
| 3108 |
|
</t> |
| 3109 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3110 |
|
<list> |
| 3111 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3112 |
|
</list> |
| 3113 |
|
</t> |
| 3114 |
|
</list> |
| 3115 |
|
</t> |
| 3116 |
|
<t>Examples:</t> |
| 3117 |
|
<t> |
| 3118 |
|
<list> |
| 3119 |
|
<t></t> |
| 3120 |
|
</list> |
| 3121 |
|
</t> |
| 3122 |
|
</section> |
| 3123 |
|
|
| 3124 |
|
<section title="Soloing a sampler channel" anchor="SET CHANNEL SOLO"> |
| 3125 |
|
<t>The front-end can solo/unsolo a specific sampler channel |
| 3126 |
|
by sending the following command:</t> |
| 3127 |
|
<t> |
| 3128 |
|
<list> |
| 3129 |
|
<t>SET CHANNEL SOLO <sampler-channel> <solo></t> |
| 3130 |
|
</list> |
| 3131 |
|
</t> |
| 3132 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3133 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3134 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and |
| 3135 |
|
<solo> should be replaced either by "1" to solo the channel or "0" |
| 3136 |
|
to unsolo the channel.</t> |
| 3137 |
|
|
| 3138 |
|
<t>Possible Answers:</t> |
| 3139 |
|
<t> |
| 3140 |
|
<list> |
| 3141 |
|
<t>"OK" - |
| 3142 |
|
<list> |
| 3143 |
|
<t>on success</t> |
| 3144 |
|
</list> |
| 3145 |
|
</t> |
| 3146 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 3147 |
|
<list> |
| 3148 |
|
<t>if the channel was soloed/unsoloed, but there are noteworthy |
| 3149 |
|
issue(s) related, providing an appropriate warning code and |
| 3150 |
|
warning message</t> |
| 3151 |
|
</list> |
| 3152 |
|
</t> |
| 3153 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3154 |
|
<list> |
| 3155 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3156 |
|
</list> |
| 3157 |
|
</t> |
| 3158 |
|
</list> |
| 3159 |
|
</t> |
| 3160 |
|
<t>Examples:</t> |
| 3161 |
|
<t> |
| 3162 |
|
<list> |
| 3163 |
|
<t></t> |
| 3164 |
|
</list> |
| 3165 |
|
</t> |
| 3166 |
|
</section> |
| 3167 |
|
|
| 3168 |
|
<section title="Assigning a MIDI instrument map to a sampler channel" anchor="SET CHANNEL MIDI_INSTRUMENT_MAP"> |
| 3169 |
|
<t>The front-end can assign a MIDI instrument map to a specific sampler channel |
| 3170 |
|
by sending the following command:</t> |
| 3171 |
|
<t> |
| 3172 |
|
<list> |
| 3173 |
|
<t>SET CHANNEL MIDI_INSTRUMENT_MAP <sampler-channel> <map></t> |
| 3174 |
|
</list> |
| 3175 |
|
</t> |
| 3176 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3177 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3178 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and |
| 3179 |
|
<map> can have the following possibilites:</t> |
| 3180 |
|
<t> |
| 3181 |
|
<list> |
| 3182 |
|
<t>"NONE" - |
| 3183 |
|
<list> |
| 3184 |
|
<t>This is the default setting. In this case |
| 3185 |
|
the sampler channel is not assigned any MIDI |
| 3186 |
|
instrument map and thus will ignore all MIDI |
| 3187 |
|
program change messages.</t> |
| 3188 |
|
</list> |
| 3189 |
|
</t> |
| 3190 |
|
<t>"DEFAULT" - |
| 3191 |
|
<list> |
| 3192 |
|
<t>The sampler channel will always use the |
| 3193 |
|
default MIDI instrument map to handle MIDI |
| 3194 |
|
program change messages.</t> |
| 3195 |
|
</list> |
| 3196 |
|
</t> |
| 3197 |
|
<t>numeric ID - |
| 3198 |
|
<list> |
| 3199 |
|
<t>You can assign a specific MIDI instrument map |
| 3200 |
|
by replacing <map> with the respective numeric |
| 3201 |
|
ID of the MIDI instrument map as returned by the |
| 3202 |
|
<xref target="LIST MIDI_INSTRUMENT_MAPS">"LIST MIDI_INSTRUMENT_MAPS"</xref> |
| 3203 |
|
command. Once that map will be deleted, the sampler |
| 3204 |
|
channel would fall back to "NONE".</t> |
| 3205 |
|
</list> |
| 3206 |
|
</t> |
| 3207 |
|
</list> |
| 3208 |
|
</t> |
| 3209 |
|
<t>Read chapter <xref target="MIDI Instrument Mapping">"MIDI Instrument Mapping"</xref> |
| 3210 |
|
for details regarding MIDI instrument mapping.</t> |
| 3211 |
|
|
| 3212 |
|
<t>Possible Answers:</t> |
| 3213 |
|
<t> |
| 3214 |
|
<list> |
| 3215 |
|
<t>"OK" - |
| 3216 |
|
<list> |
| 3217 |
|
<t>on success</t> |
| 3218 |
|
</list> |
| 3219 |
|
</t> |
| 3220 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3221 |
|
<list> |
| 3222 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3223 |
|
</list> |
| 3224 |
|
</t> |
| 3225 |
|
</list> |
| 3226 |
|
</t> |
| 3227 |
|
|
| 3228 |
|
<t>Examples:</t> |
| 3229 |
|
<t> |
| 3230 |
|
<list> |
| 3231 |
|
<t></t> |
| 3232 |
|
</list> |
| 3233 |
|
</t> |
| 3234 |
|
</section> |
| 3235 |
|
|
| 3236 |
|
<section title="Adding an effect send to a sampler channel" anchor="CREATE FX_SEND"> |
| 3237 |
|
<t>The front-end can create an additional effect send on a specific sampler channel |
| 3238 |
|
by sending the following command:</t> |
| 3239 |
|
<t> |
| 3240 |
|
<list> |
| 3241 |
|
<t>CREATE FX_SEND <sampler-channel> <midi-ctrl> [<name>]</t> |
| 3242 |
|
</list> |
| 3243 |
|
</t> |
| 3244 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3245 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3246 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, that is the |
| 3247 |
|
sampler channel on which the effect send should be created on, <midi-ctrl> |
| 3248 |
|
is a number between 0..127 defining the MIDI controller which can alter the |
| 3249 |
|
effect send level and <name> is an optional argument defining a name |
| 3250 |
|
for the effect send entity. The name does not have to be unique.</t> |
| 3251 |
|
|
| 3252 |
|
<t>By default, that is as initial routing, the effect send's audio channels |
| 3253 |
|
are automatically routed to the last audio channels of the sampler channel's |
| 3254 |
|
audio output device, that way you can i.e. first increase the amount of audio |
| 3255 |
|
channels on the audio output device for having dedicated effect send output |
| 3256 |
|
channels and when "CREATE FX_SEND" is called, those channels will automatically |
| 3257 |
|
be picked. You can alter the destination channels however with |
| 3258 |
|
<xref target="SET FX_SEND AUDIO_OUTPUT_CHANNEL">"SET FX_SEND AUDIO_OUTPUT_CHANNEL"</xref>. |
| 3259 |
|
</t> |
| 3260 |
|
|
| 3261 |
|
<t>Note: Create effect sends on a sampler channel only when needed, because having effect |
| 3262 |
|
sends on a sampler channel will decrease runtime performance, because for implementing channel |
| 3263 |
|
effect sends, separate (sampler channel local) audio buffers are needed to render and mix |
| 3264 |
|
the voices and route the audio signal afterwards to the master outputs and effect send |
| 3265 |
|
outputs (along with their respective effect send levels). A sampler channel without effect |
| 3266 |
|
sends however can mix its voices directly into the audio output devices's audio buffers |
| 3267 |
|
and is thus faster. |
| 3268 |
|
</t> |
| 3269 |
|
|
| 3270 |
|
<t>Possible Answers:</t> |
| 3271 |
|
<t> |
| 3272 |
|
<list> |
| 3273 |
|
<t>"OK[<fx-send-id>]" - |
| 3274 |
|
<list> |
| 3275 |
|
<t>in case a new effect send could be added to the |
| 3276 |
|
sampler channel, where <fx-send-id> reflects the |
| 3277 |
|
unique ID of the newly created effect send entity</t> |
| 3278 |
|
</list> |
| 3279 |
|
</t> |
| 3280 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3281 |
|
<list> |
| 3282 |
|
<t>when a new effect send could not be added, i.e. |
| 3283 |
|
due to invalid parameters</t> |
| 3284 |
|
</list> |
| 3285 |
|
</t> |
| 3286 |
|
</list> |
| 3287 |
|
</t> |
| 3288 |
|
|
| 3289 |
|
<t>Examples:</t> |
| 3290 |
|
<t> |
| 3291 |
|
<list> |
| 3292 |
|
<t>C: "CREATE FX_SEND 0 91 'Reverb Send'"</t> |
| 3293 |
|
<t>S: "OK[0]"</t> |
| 3294 |
|
</list> |
| 3295 |
|
</t> |
| 3296 |
|
<t> |
| 3297 |
|
<list> |
| 3298 |
|
<t>C: "CREATE FX_SEND 0 93"</t> |
| 3299 |
|
<t>S: "OK[1]"</t> |
| 3300 |
|
</list> |
| 3301 |
|
</t> |
| 3302 |
|
</section> |
| 3303 |
|
|
| 3304 |
|
<section title="Removing an effect send from a sampler channel" anchor="DESTROY FX_SEND"> |
| 3305 |
|
<t>The front-end can remove an existing effect send on a specific sampler channel |
| 3306 |
|
by sending the following command:</t> |
| 3307 |
|
<t> |
| 3308 |
|
<list> |
| 3309 |
|
<t>DESTROY FX_SEND <sampler-channel> <fx-send-id></t> |
| 3310 |
|
</list> |
| 3311 |
|
</t> |
| 3312 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3313 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3314 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, that is the |
| 3315 |
|
sampler channel from which the effect send should be removed from and |
| 3316 |
|
<fx-send-id> is the respective effect send number as returned by the |
| 3317 |
|
<xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3318 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command.</t> |
| 3319 |
|
|
| 3320 |
|
<t>Possible Answers:</t> |
| 3321 |
|
<t> |
| 3322 |
|
<list> |
| 3323 |
|
<t>"OK" - |
| 3324 |
|
<list> |
| 3325 |
|
<t>on success</t> |
| 3326 |
|
</list> |
| 3327 |
|
</t> |
| 3328 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3329 |
|
<list> |
| 3330 |
|
<t>in case it failed, providing an appropriate error code and |
| 3331 |
|
error message</t> |
| 3332 |
|
</list> |
| 3333 |
|
</t> |
| 3334 |
|
</list> |
| 3335 |
|
</t> |
| 3336 |
|
|
| 3337 |
|
<t>Example:</t> |
| 3338 |
|
<t> |
| 3339 |
|
<list> |
| 3340 |
|
<t>C: "DESTROY FX_SEND 0 0"</t> |
| 3341 |
|
<t>S: "OK"</t> |
| 3342 |
|
</list> |
| 3343 |
|
</t> |
| 3344 |
|
</section> |
| 3345 |
|
|
| 3346 |
|
<section title="Getting amount of effect sends on a sampler channel" anchor="GET FX_SENDS"> |
| 3347 |
|
<t>The front-end can ask for the amount of effect sends on a specific sampler channel |
| 3348 |
|
by sending the following command:</t> |
| 3349 |
|
<t> |
| 3350 |
|
<list> |
| 3351 |
|
<t>GET FX_SENDS <sampler-channel></t> |
| 3352 |
|
</list> |
| 3353 |
|
</t> |
| 3354 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3355 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3356 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 3357 |
|
|
| 3358 |
|
<t>Possible Answers:</t> |
| 3359 |
|
<t> |
| 3360 |
|
<list> |
| 3361 |
|
<t>The sampler will answer by returning the number of effect |
| 3362 |
|
sends on the given sampler channel.</t> |
| 3363 |
|
</list> |
| 3364 |
|
</t> |
| 3365 |
|
|
| 3366 |
|
<t>Example:</t> |
| 3367 |
|
<t> |
| 3368 |
|
<list> |
| 3369 |
|
<t>C: "GET FX_SENDS 0"</t> |
| 3370 |
|
<t>S: "2"</t> |
| 3371 |
|
</list> |
| 3372 |
|
</t> |
| 3373 |
|
</section> |
| 3374 |
|
|
| 3375 |
|
<section title="Listing all effect sends on a sampler channel" anchor="LIST FX_SENDS"> |
| 3376 |
|
<t>The front-end can ask for a list of effect sends on a specific sampler channel |
| 3377 |
|
by sending the following command:</t> |
| 3378 |
|
<t> |
| 3379 |
|
<list> |
| 3380 |
|
<t>LIST FX_SENDS <sampler-channel></t> |
| 3381 |
|
</list> |
| 3382 |
|
</t> |
| 3383 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3384 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3385 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 3386 |
|
|
| 3387 |
|
<t>Possible Answers:</t> |
| 3388 |
|
<t> |
| 3389 |
|
<list> |
| 3390 |
|
<t>The sampler will answer by returning a comma separated list |
| 3391 |
|
with all effect sends' numerical IDs on the given sampler |
| 3392 |
|
channel.</t> |
| 3393 |
|
</list> |
| 3394 |
|
</t> |
| 3395 |
|
|
| 3396 |
|
<t>Examples:</t> |
| 3397 |
|
<t> |
| 3398 |
|
<list> |
| 3399 |
|
<t>C: "LIST FX_SENDS 0"</t> |
| 3400 |
|
<t>S: "0,1"</t> |
| 3401 |
|
</list> |
| 3402 |
|
</t> |
| 3403 |
|
<t> |
| 3404 |
|
<list> |
| 3405 |
|
<t>C: "LIST FX_SENDS 1"</t> |
| 3406 |
|
<t>S: ""</t> |
| 3407 |
|
</list> |
| 3408 |
|
</t> |
| 3409 |
|
</section> |
| 3410 |
|
|
| 3411 |
|
<section title="Getting effect send information" anchor="GET FX_SEND INFO"> |
| 3412 |
|
<t>The front-end can ask for the current settings of an effect send entity |
| 3413 |
|
by sending the following command:</t> |
| 3414 |
|
<t> |
| 3415 |
|
<list> |
| 3416 |
|
<t>GET FX_SEND INFO <sampler-channel> <fx-send-id></t> |
| 3417 |
|
</list> |
| 3418 |
|
</t> |
| 3419 |
|
<t>Where <sampler-channel> is the sampler channel number |
| 3420 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3421 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and |
| 3422 |
|
<fx-send-id> reflects the numerical ID of the effect send entity |
| 3423 |
|
as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3424 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command. |
| 3425 |
|
</t> |
| 3426 |
|
|
| 3427 |
|
<t>Possible Answers:</t> |
| 3428 |
|
<t> |
| 3429 |
|
<list> |
| 3430 |
|
<t>The sampler will answer by sending a <CRLF> separated list. |
| 3431 |
|
Each answer line begins with the settings category name |
| 3432 |
|
followed by a colon and then a space character <SP> and finally |
| 3433 |
|
the info character string to that setting category. At the |
| 3434 |
|
moment the following categories are defined:</t> |
| 3435 |
|
|
| 3436 |
|
<t> |
| 3437 |
|
<list> |
| 3438 |
|
<t>NAME - |
| 3439 |
|
<list> |
| 3440 |
|
<t>name of the effect send entity</t> |
| 3441 |
|
</list> |
| 3442 |
|
</t> |
| 3443 |
|
<t>MIDI_CONTROLLER - |
| 3444 |
|
<list> |
| 3445 |
|
<t>a value between 0 and 127 reflecting the MIDI controller |
| 3446 |
|
which is able to modify the effect send's send level</t> |
| 3447 |
|
</list> |
| 3448 |
|
</t> |
| 3449 |
|
<t>LEVEL - |
| 3450 |
|
<list> |
| 3451 |
|
<t>optionally dotted number reflecting the effect send's |
| 3452 |
|
current send level (where a value < 1.0 means attenuation |
| 3453 |
|
and a value > 1.0 means amplification)</t> |
| 3454 |
|
</list> |
| 3455 |
|
</t> |
| 3456 |
|
<t>AUDIO_OUTPUT_ROUTING - |
| 3457 |
|
<list> |
| 3458 |
|
<t>comma separated list which reflects to which audio |
| 3459 |
|
channel of the selected audio output device each |
| 3460 |
|
effect send output channel is routed to, e.g. "0,3" would |
| 3461 |
|
mean the effect send's output channel 0 is routed to channel |
| 3462 |
|
0 of the audio output device and the effect send's output |
| 3463 |
|
channel 1 is routed to the channel 3 of the audio |
| 3464 |
|
output device (see |
| 3465 |
|
<xref target="SET FX_SEND AUDIO_OUTPUT_CHANNEL">"SET FX_SEND AUDIO_OUTPUT_CHANNEL"</xref> |
| 3466 |
|
for details)</t> |
| 3467 |
|
</list> |
| 3468 |
|
</t> |
| 3469 |
|
</list> |
| 3470 |
|
</t> |
| 3471 |
|
</list> |
| 3472 |
|
</t> |
| 3473 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 3474 |
|
|
| 3475 |
|
<t>Example:</t> |
| 3476 |
|
<t> |
| 3477 |
|
<list> |
| 3478 |
|
<t>C: "GET FX_SEND INFO 0 0"</t> |
| 3479 |
|
<t>S: "NAME: Reverb Send"</t> |
| 3480 |
|
<t> "MIDI_CONTROLLER: 91"</t> |
| 3481 |
|
<t> "LEVEL: 0.3"</t> |
| 3482 |
|
<t> "AUDIO_OUTPUT_ROUTING: 2,3"</t> |
| 3483 |
|
<t> "."</t> |
| 3484 |
|
</list> |
| 3485 |
|
</t> |
| 3486 |
|
</section> |
| 3487 |
|
|
| 3488 |
|
<section title="Changing effect send's name" anchor="SET FX_SEND NAME"> |
| 3489 |
|
<t>The front-end can alter the current name of an effect |
| 3490 |
|
send entity by sending the following command:</t> |
| 3491 |
|
<t> |
| 3492 |
|
<list> |
| 3493 |
|
<t>SET FX_SEND NAME <sampler-chan> <fx-send-id> <name></t> |
| 3494 |
|
</list> |
| 3495 |
|
</t> |
| 3496 |
|
<t>Where <sampler-chan> is the sampler channel number |
| 3497 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3498 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, |
| 3499 |
|
<fx-send-id> reflects the numerical ID of the effect send entity |
| 3500 |
|
as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3501 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command and |
| 3502 |
|
<name> is the new name of the effect send entity, which |
| 3503 |
|
does not have to be unique.</t> |
| 3504 |
|
|
| 3505 |
|
<t>Possible Answers:</t> |
| 3506 |
|
<t> |
| 3507 |
|
<list> |
| 3508 |
|
<t>"OK" - |
| 3509 |
|
<list> |
| 3510 |
|
<t>on success</t> |
| 3511 |
|
</list> |
| 3512 |
|
</t> |
| 3513 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3514 |
|
<list> |
| 3515 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3516 |
|
</list> |
| 3517 |
|
</t> |
| 3518 |
|
</list> |
| 3519 |
|
</t> |
| 3520 |
|
<t>Example:</t> |
| 3521 |
|
<t> |
| 3522 |
|
<list> |
| 3523 |
|
<t>C: "SET FX_SEND NAME 0 0 'Fx Send 1'"</t> |
| 3524 |
|
<t>S: "OK"</t> |
| 3525 |
|
</list> |
| 3526 |
|
</t> |
| 3527 |
|
</section> |
| 3528 |
|
|
| 3529 |
|
<section title="Altering effect send's audio routing" anchor="SET FX_SEND AUDIO_OUTPUT_CHANNEL"> |
| 3530 |
|
<t>The front-end can alter the destination of an effect send's audio channel on a specific |
| 3531 |
|
sampler channel by sending the following command:</t> |
| 3532 |
|
<t> |
| 3533 |
|
<list> |
| 3534 |
|
<t>SET FX_SEND AUDIO_OUTPUT_CHANNEL <sampler-chan> <fx-send-id> <audio-src> <audio-dst></t> |
| 3535 |
|
</list> |
| 3536 |
|
</t> |
| 3537 |
|
<t>Where <sampler-chan> is the sampler channel number |
| 3538 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3539 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, |
| 3540 |
|
<fx-send-id> reflects the numerical ID of the effect send entity |
| 3541 |
|
as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3542 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command, |
| 3543 |
|
<audio-src> is the numerical ID of the effect send's audio channel |
| 3544 |
|
which should be rerouted and <audio-dst> is the numerical ID of |
| 3545 |
|
the audio channel of the selected audio output device where <audio-src> |
| 3546 |
|
should be routed to.</t> |
| 3547 |
|
|
| 3548 |
|
<t>Note that effect sends can only route audio to the same audio output |
| 3549 |
|
device as assigned to the effect send's sampler channel. Also note that an |
| 3550 |
|
effect send entity does always have exactly as much audio channels as its |
| 3551 |
|
sampler channel. So if the sampler channel is stereo, the effect send does |
| 3552 |
|
have two audio channels as well. Also keep in mind that the amount of audio |
| 3553 |
|
channels on a sampler channel might be dependant not only to the deployed |
| 3554 |
|
sampler engine on the sampler channel, but also dependant to the instrument |
| 3555 |
|
currently loaded. However you can (effectively) turn an i.e. stereo effect |
| 3556 |
|
send into a mono one by simply altering its audio routing appropriately.</t> |
| 3557 |
|
|
| 3558 |
|
<t>Possible Answers:</t> |
| 3559 |
|
<t> |
| 3560 |
|
<list> |
| 3561 |
|
<t>"OK" - |
| 3562 |
|
<list> |
| 3563 |
|
<t>on success</t> |
| 3564 |
|
</list> |
| 3565 |
|
</t> |
| 3566 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 3567 |
|
<list> |
| 3568 |
|
<t>if audio output channel was set, but there are noteworthy |
| 3569 |
|
issue(s) related, providing an appropriate warning code and |
| 3570 |
|
warning message</t> |
| 3571 |
|
</list> |
| 3572 |
|
</t> |
| 3573 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3574 |
|
<list> |
| 3575 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3576 |
|
</list> |
| 3577 |
|
</t> |
| 3578 |
|
</list> |
| 3579 |
|
</t> |
| 3580 |
|
<t>Example:</t> |
| 3581 |
|
<t> |
| 3582 |
|
<list> |
| 3583 |
|
<t>C: "SET FX_SEND AUDIO_OUTPUT_CHANNEL 0 0 0 2"</t> |
| 3584 |
|
<t>S: "OK"</t> |
| 3585 |
|
</list> |
| 3586 |
|
</t> |
| 3587 |
|
</section> |
| 3588 |
|
|
| 3589 |
|
<section title="Altering effect send's MIDI controller" anchor="SET FX_SEND MIDI_CONTROLLER"> |
| 3590 |
|
<t>The front-end can alter the MIDI controller of an effect |
| 3591 |
|
send entity by sending the following command:</t> |
| 3592 |
|
<t> |
| 3593 |
|
<list> |
| 3594 |
|
<t>SET FX_SEND MIDI_CONTROLLER <sampler-chan> <fx-send-id> <midi-ctrl></t> |
| 3595 |
|
</list> |
| 3596 |
|
</t> |
| 3597 |
|
<t>Where <sampler-chan> is the sampler channel number |
| 3598 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3599 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, |
| 3600 |
|
<fx-send-id> reflects the numerical ID of the effect send entity |
| 3601 |
|
as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3602 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command and |
| 3603 |
|
<midi-ctrl> reflects the MIDI controller which shall be |
| 3604 |
|
able to modify the effect send's send level.</t> |
| 3605 |
|
|
| 3606 |
|
<t>Possible Answers:</t> |
| 3607 |
|
<t> |
| 3608 |
|
<list> |
| 3609 |
|
<t>"OK" - |
| 3610 |
|
<list> |
| 3611 |
|
<t>on success</t> |
| 3612 |
|
</list> |
| 3613 |
|
</t> |
| 3614 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 3615 |
|
<list> |
| 3616 |
|
<t>if MIDI controller was set, but there are noteworthy |
| 3617 |
|
issue(s) related, providing an appropriate warning code and |
| 3618 |
|
warning message</t> |
| 3619 |
|
</list> |
| 3620 |
|
</t> |
| 3621 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3622 |
|
<list> |
| 3623 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3624 |
|
</list> |
| 3625 |
|
</t> |
| 3626 |
|
</list> |
| 3627 |
|
</t> |
| 3628 |
|
<t>Example:</t> |
| 3629 |
|
<t> |
| 3630 |
|
<list> |
| 3631 |
|
<t>C: "SET FX_SEND MIDI_CONTROLLER 0 0 91"</t> |
| 3632 |
|
<t>S: "OK"</t> |
| 3633 |
|
</list> |
| 3634 |
|
</t> |
| 3635 |
|
</section> |
| 3636 |
|
|
| 3637 |
|
<section title="Altering effect send's send level" anchor="SET FX_SEND LEVEL"> |
| 3638 |
|
<t>The front-end can alter the current send level of an effect |
| 3639 |
|
send entity by sending the following command:</t> |
| 3640 |
|
<t> |
| 3641 |
|
<list> |
| 3642 |
|
<t>SET FX_SEND LEVEL <sampler-chan> <fx-send-id> <volume></t> |
| 3643 |
|
</list> |
| 3644 |
|
</t> |
| 3645 |
|
<t>Where <sampler-chan> is the sampler channel number |
| 3646 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3647 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, |
| 3648 |
|
<fx-send-id> reflects the numerical ID of the effect send entity |
| 3649 |
|
as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3650 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command and |
| 3651 |
|
<volume> is an optionally dotted positive number (a value |
| 3652 |
|
smaller than 1.0 means attenuation, whereas a value greater than |
| 3653 |
|
1.0 means amplification) reflecting the new send level.</t> |
| 3654 |
|
|
| 3655 |
|
<t>Possible Answers:</t> |
| 3656 |
|
<t> |
| 3657 |
|
<list> |
| 3658 |
|
<t>"OK" - |
| 3659 |
|
<list> |
| 3660 |
|
<t>on success</t> |
| 3661 |
|
</list> |
| 3662 |
|
</t> |
| 3663 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 3664 |
|
<list> |
| 3665 |
|
<t>if new send level was set, but there are noteworthy |
| 3666 |
|
issue(s) related, providing an appropriate warning code and |
| 3667 |
|
warning message</t> |
| 3668 |
|
</list> |
| 3669 |
|
</t> |
| 3670 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3671 |
|
<list> |
| 3672 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3673 |
|
</list> |
| 3674 |
|
</t> |
| 3675 |
|
</list> |
| 3676 |
|
</t> |
| 3677 |
|
<t>Example:</t> |
| 3678 |
|
<t> |
| 3679 |
|
<list> |
| 3680 |
|
<t>C: "SET FX_SEND LEVEL 0 0 0.15"</t> |
| 3681 |
|
<t>S: "OK"</t> |
| 3682 |
|
</list> |
| 3683 |
|
</t> |
| 3684 |
|
</section> |
| 3685 |
|
|
| 3686 |
|
<section title="Resetting a sampler channel" anchor="RESET CHANNEL"> |
| 3687 |
<t>The front-end can reset a particular sampler channel by sending the following command:</t> |
<t>The front-end can reset a particular sampler channel by sending the following command:</t> |
| 3688 |
<t> |
<t> |
| 3689 |
<list> |
<list> |
| 3731 |
<section title="Controlling connection"> |
<section title="Controlling connection"> |
| 3732 |
<t>The following commands are used to control the connection to LinuxSampler.</t> |
<t>The following commands are used to control the connection to LinuxSampler.</t> |
| 3733 |
|
|
| 3734 |
<section title="Register front-end for receiving event messages"> |
<section title="Register front-end for receiving event messages" anchor="SUBSCRIBE"> |
| 3735 |
<t>The front-end can register itself to the LinuxSampler application to |
<t>The front-end can register itself to the LinuxSampler application to |
| 3736 |
be informed about noteworthy events by sending this command:</t> |
be informed about noteworthy events by sending this command:</t> |
| 3737 |
<t> |
<t> |
| 3773 |
</t> |
</t> |
| 3774 |
</section> |
</section> |
| 3775 |
|
|
| 3776 |
<section title="Unregister front-end for not receiving event messages"> |
<section title="Unregister front-end for not receiving event messages" anchor="UNSUBSCRIBE"> |
| 3777 |
<t>The front-end can unregister itself if it doesn't want to receive event |
<t>The front-end can unregister itself if it doesn't want to receive event |
| 3778 |
messages anymore by sending the following command:</t> |
messages anymore by sending the following command:</t> |
| 3779 |
<t> |
<t> |
| 3815 |
</t> |
</t> |
| 3816 |
</section> |
</section> |
| 3817 |
|
|
| 3818 |
<section title="Enable or disable echo of commands"> |
<section title="Enable or disable echo of commands" anchor="SET ECHO"> |
| 3819 |
<t>To enable or disable back sending of commands to the client the following command can be used:</t> |
<t>To enable or disable back sending of commands to the client the following command can be used:</t> |
| 3820 |
<t> |
<t> |
| 3821 |
<list> |
<list> |
| 3853 |
</t> |
</t> |
| 3854 |
</section> |
</section> |
| 3855 |
|
|
| 3856 |
<section title="Close client connection"> |
<section title="Close client connection" anchor="QUIT"> |
| 3857 |
<t>The client can close its network connection to LinuxSampler by sending the following command:</t> |
<t>The client can close its network connection to LinuxSampler by sending the following command:</t> |
| 3858 |
<t> |
<t> |
| 3859 |
<list> |
<list> |
| 3868 |
<section title="Global commands"> |
<section title="Global commands"> |
| 3869 |
<t>The following commands have global impact on the sampler.</t> |
<t>The following commands have global impact on the sampler.</t> |
| 3870 |
|
|
| 3871 |
<section title="Reset sampler"> |
<section title="Current number of active voices" anchor="GET TOTAL_VOICE_COUNT"> |
| 3872 |
|
<t>The front-end can ask for the current number of active voices on |
| 3873 |
|
the sampler by sending the following command:</t> |
| 3874 |
|
<t> |
| 3875 |
|
<list> |
| 3876 |
|
<t>GET TOTAL_VOICE_COUNT</t> |
| 3877 |
|
</list> |
| 3878 |
|
</t> |
| 3879 |
|
|
| 3880 |
|
<t>Possible Answers:</t> |
| 3881 |
|
<t> |
| 3882 |
|
<list> |
| 3883 |
|
<t>LinuxSampler will answer by returning the number of all active |
| 3884 |
|
voices on the sampler.</t> |
| 3885 |
|
</list> |
| 3886 |
|
</t> |
| 3887 |
|
</section> |
| 3888 |
|
|
| 3889 |
|
<section title="Maximum amount of active voices" anchor="GET TOTAL_VOICE_COUNT_MAX"> |
| 3890 |
|
<t>The front-end can ask for the maximum number of active voices |
| 3891 |
|
by sending the following command:</t> |
| 3892 |
|
<t> |
| 3893 |
|
<list> |
| 3894 |
|
<t>GET TOTAL_VOICE_COUNT_MAX</t> |
| 3895 |
|
</list> |
| 3896 |
|
</t> |
| 3897 |
|
|
| 3898 |
|
<t>Possible Answers:</t> |
| 3899 |
|
<t> |
| 3900 |
|
<list> |
| 3901 |
|
<t>LinuxSampler will answer by returning the maximum number |
| 3902 |
|
of active voices.</t> |
| 3903 |
|
</list> |
| 3904 |
|
</t> |
| 3905 |
|
</section> |
| 3906 |
|
|
| 3907 |
|
<section title="Reset sampler" anchor="RESET"> |
| 3908 |
<t>The front-end can reset the whole sampler by sending the following command:</t> |
<t>The front-end can reset the whole sampler by sending the following command:</t> |
| 3909 |
<t> |
<t> |
| 3910 |
<list> |
<list> |
| 3929 |
</list> |
</list> |
| 3930 |
</t> |
</t> |
| 3931 |
</section> |
</section> |
| 3932 |
|
|
| 3933 |
|
<section title="General sampler informations" anchor="GET SERVER INFO"> |
| 3934 |
|
<t>The client can ask for general informations about the LinuxSampler |
| 3935 |
|
instance by sending the following command:</t> |
| 3936 |
|
<t> |
| 3937 |
|
<list> |
| 3938 |
|
<t>GET SERVER INFO</t> |
| 3939 |
|
</list> |
| 3940 |
|
</t> |
| 3941 |
|
<t>Possible Answers:</t> |
| 3942 |
|
<t> |
| 3943 |
|
<list> |
| 3944 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
| 3945 |
|
Each answer line begins with the information category name |
| 3946 |
|
followed by a colon and then a space character <SP> and finally |
| 3947 |
|
the info character string to that information category. At the |
| 3948 |
|
moment the following categories are defined: |
| 3949 |
|
</t> |
| 3950 |
|
<t> |
| 3951 |
|
<list> |
| 3952 |
|
<t>DESCRIPTION - |
| 3953 |
|
<list> |
| 3954 |
|
<t>arbitrary textual description about the sampler</t> |
| 3955 |
|
</list> |
| 3956 |
|
</t> |
| 3957 |
|
<t>VERSION - |
| 3958 |
|
<list> |
| 3959 |
|
<t>version of the sampler</t> |
| 3960 |
|
</list> |
| 3961 |
|
</t> |
| 3962 |
|
<t>PROTOCOL_VERSION - |
| 3963 |
|
<list> |
| 3964 |
|
<t>version of the LSCP specification the sampler |
| 3965 |
|
complies with (see <xref target="LSCP versioning" /> for details)</t> |
| 3966 |
|
</list> |
| 3967 |
|
</t> |
| 3968 |
|
<t>INSTRUMENTS_DB_SUPPORT - |
| 3969 |
|
<list> |
| 3970 |
|
<t>either yes or no, specifies whether the |
| 3971 |
|
sampler is build with instruments database support.</t> |
| 3972 |
|
</list> |
| 3973 |
|
</t> |
| 3974 |
|
</list> |
| 3975 |
|
</t> |
| 3976 |
|
</list> |
| 3977 |
|
</t> |
| 3978 |
|
<t>The mentioned fields above don't have to be in particular order. |
| 3979 |
|
Other fields might be added in future.</t> |
| 3980 |
|
</section> |
| 3981 |
|
|
| 3982 |
|
<section title="Getting global volume attenuation" anchor="GET VOLUME"> |
| 3983 |
|
<t>The client can ask for the current global sampler-wide volume |
| 3984 |
|
attenuation by sending the following command:</t> |
| 3985 |
|
<t> |
| 3986 |
|
<list> |
| 3987 |
|
<t>GET VOLUME</t> |
| 3988 |
|
</list> |
| 3989 |
|
</t> |
| 3990 |
|
<t>Possible Answers:</t> |
| 3991 |
|
<t> |
| 3992 |
|
<list> |
| 3993 |
|
<t>The sampler will always answer by returning the optional |
| 3994 |
|
dotted floating point coefficient, reflecting the current |
| 3995 |
|
global volume attenuation. |
| 3996 |
|
</t> |
| 3997 |
|
</list> |
| 3998 |
|
</t> |
| 3999 |
|
<t>Note: it is up to the respective sampler engine whether to obey |
| 4000 |
|
that global volume parameter or not, but in general all engines SHOULD |
| 4001 |
|
use this parameter.</t> |
| 4002 |
|
</section> |
| 4003 |
|
|
| 4004 |
|
<section title="Setting global volume attenuation" anchor="SET VOLUME"> |
| 4005 |
|
<t>The client can alter the current global sampler-wide volume |
| 4006 |
|
attenuation by sending the following command:</t> |
| 4007 |
|
<t> |
| 4008 |
|
<list> |
| 4009 |
|
<t>SET VOLUME <volume></t> |
| 4010 |
|
</list> |
| 4011 |
|
</t> |
| 4012 |
|
<t>Where <volume> should be replaced by the optional dotted |
| 4013 |
|
floating point value, reflecting the new global volume parameter. |
| 4014 |
|
This value might usually be in the range between 0.0 and 1.0, that |
| 4015 |
|
is for attenuating the overall volume.</t> |
| 4016 |
|
|
| 4017 |
|
<t>Possible Answers:</t> |
| 4018 |
|
<t> |
| 4019 |
|
<list> |
| 4020 |
|
<t>"OK" - |
| 4021 |
|
<list> |
| 4022 |
|
<t>on success</t> |
| 4023 |
|
</list> |
| 4024 |
|
</t> |
| 4025 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 4026 |
|
<list> |
| 4027 |
|
<t>if the global volume was set, but there are noteworthy |
| 4028 |
|
issue(s) related, providing an appropriate warning code and |
| 4029 |
|
warning message</t> |
| 4030 |
|
</list> |
| 4031 |
|
</t> |
| 4032 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4033 |
|
<list> |
| 4034 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 4035 |
|
</list> |
| 4036 |
|
</t> |
| 4037 |
|
</list> |
| 4038 |
|
</t> |
| 4039 |
|
</section> |
| 4040 |
|
</section> |
| 4041 |
|
|
| 4042 |
|
|
| 4043 |
|
<section title="MIDI Instrument Mapping" anchor="MIDI Instrument Mapping"> |
| 4044 |
|
<t>The MIDI protocol provides a way to switch between instruments |
| 4045 |
|
by sending so called MIDI bank select and MIDI program change |
| 4046 |
|
messages which are essentially just numbers. The following commands |
| 4047 |
|
allow to actually map arbitrary MIDI bank select / program change |
| 4048 |
|
numbers with real instruments.</t> |
| 4049 |
|
<t>The sampler allows to manage an arbitrary amount of MIDI |
| 4050 |
|
instrument maps which define which instrument to load on |
| 4051 |
|
which MIDI program change message.</t> |
| 4052 |
|
<t>By default, that is when the sampler is launched, there is no |
| 4053 |
|
map, thus the sampler will simply ignore all program change |
| 4054 |
|
messages. The front-end has to explicitly create at least one |
| 4055 |
|
map, add entries to the map and tell the respective sampler |
| 4056 |
|
channel(s) which MIDI instrument map to use, so the sampler |
| 4057 |
|
knows how to react on a given program change message on the |
| 4058 |
|
respective sampler channel, that is by switching to the |
| 4059 |
|
respectively defined engine type and loading the respective |
| 4060 |
|
instrument. See command |
| 4061 |
|
<xref target="SET CHANNEL MIDI_INSTRUMENT_MAP">"SET CHANNEL MIDI_INSTRUMENT_MAP"</xref> |
| 4062 |
|
for how to assign a MIDI instrument map to a sampler channel.</t> |
| 4063 |
|
<t>Also note per MIDI specification a bank select message does not |
| 4064 |
|
cause to switch to another instrument. Instead when receiving a |
| 4065 |
|
bank select message the bank value will be stored and a subsequent |
| 4066 |
|
program change message (which may occur at any time) will finally |
| 4067 |
|
cause the sampler to switch to the respective instrument as |
| 4068 |
|
reflected by the current MIDI instrument map.</t> |
| 4069 |
|
|
| 4070 |
|
<section title="Create a new MIDI instrument map" anchor="ADD MIDI_INSTRUMENT MAP"> |
| 4071 |
|
<t>The front-end can add a new MIDI instrument map by sending |
| 4072 |
|
the following command:</t> |
| 4073 |
|
<t> |
| 4074 |
|
<list> |
| 4075 |
|
<t>ADD MIDI_INSTRUMENT_MAP [<name>]</t> |
| 4076 |
|
</list> |
| 4077 |
|
</t> |
| 4078 |
|
<t>Where <name> is an optional argument allowing to |
| 4079 |
|
assign a custom name to the new map. MIDI instrument Map |
| 4080 |
|
names do not have to be unique.</t> |
| 4081 |
|
|
| 4082 |
|
<t>Possible Answers:</t> |
| 4083 |
|
<t> |
| 4084 |
|
<list> |
| 4085 |
|
<t>"OK[<map>]" - |
| 4086 |
|
<list> |
| 4087 |
|
<t>in case a new MIDI instrument map could |
| 4088 |
|
be added, where <map> reflects the |
| 4089 |
|
unique ID of the newly created MIDI |
| 4090 |
|
instrument map</t> |
| 4091 |
|
</list> |
| 4092 |
|
</t> |
| 4093 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4094 |
|
<list> |
| 4095 |
|
<t>when a new map could not be created, which |
| 4096 |
|
might never occur in practice</t> |
| 4097 |
|
</list> |
| 4098 |
|
</t> |
| 4099 |
|
</list> |
| 4100 |
|
</t> |
| 4101 |
|
|
| 4102 |
|
<t>Examples:</t> |
| 4103 |
|
<t> |
| 4104 |
|
<list> |
| 4105 |
|
<t>C: "ADD MIDI_INSTRUMENT_MAP 'Standard Map'"</t> |
| 4106 |
|
<t>S: "OK[0]"</t> |
| 4107 |
|
</list> |
| 4108 |
|
</t> |
| 4109 |
|
<t> |
| 4110 |
|
<list> |
| 4111 |
|
<t>C: "ADD MIDI_INSTRUMENT_MAP 'Standard Drumkit'"</t> |
| 4112 |
|
<t>S: "OK[1]"</t> |
| 4113 |
|
</list> |
| 4114 |
|
</t> |
| 4115 |
|
<t> |
| 4116 |
|
<list> |
| 4117 |
|
<t>C: "ADD MIDI_INSTRUMENT_MAP"</t> |
| 4118 |
|
<t>S: "OK[5]"</t> |
| 4119 |
|
</list> |
| 4120 |
|
</t> |
| 4121 |
|
</section> |
| 4122 |
|
|
| 4123 |
|
<section title="Delete one particular or all MIDI instrument maps" anchor="REMOVE MIDI_INSTRUMENT_MAP"> |
| 4124 |
|
<t>The front-end can delete a particular MIDI instrument map |
| 4125 |
|
by sending the following command:</t> |
| 4126 |
|
<t> |
| 4127 |
|
<list> |
| 4128 |
|
<t>REMOVE MIDI_INSTRUMENT_MAP <map></t> |
| 4129 |
|
</list> |
| 4130 |
|
</t> |
| 4131 |
|
<t>Where <map> reflects the unique ID of the map to delete |
| 4132 |
|
as returned by the <xref target="LIST MIDI_INSTRUMENT_MAPS">"LIST MIDI_INSTRUMENT_MAPS"</xref> |
| 4133 |
|
command.</t> |
| 4134 |
|
<t>The front-end can delete all MIDI instrument maps by |
| 4135 |
|
sending the following command:</t> |
| 4136 |
|
<t> |
| 4137 |
|
<list> |
| 4138 |
|
<t>REMOVE MIDI_INSTRUMENT_MAP ALL</t> |
| 4139 |
|
</list> |
| 4140 |
|
</t> |
| 4141 |
|
|
| 4142 |
|
<t>Possible Answers:</t> |
| 4143 |
|
<t> |
| 4144 |
|
<list> |
| 4145 |
|
<t>"OK" - |
| 4146 |
|
<list> |
| 4147 |
|
<t>in case the map(s) could be deleted</t> |
| 4148 |
|
</list> |
| 4149 |
|
</t> |
| 4150 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4151 |
|
<list> |
| 4152 |
|
<t>when the given map does not exist</t> |
| 4153 |
|
</list> |
| 4154 |
|
</t> |
| 4155 |
|
</list> |
| 4156 |
|
</t> |
| 4157 |
|
|
| 4158 |
|
<t>Examples:</t> |
| 4159 |
|
<t> |
| 4160 |
|
<list> |
| 4161 |
|
<t>C: "REMOVE MIDI_INSTRUMENT_MAP 0"</t> |
| 4162 |
|
<t>S: "OK"</t> |
| 4163 |
|
</list> |
| 4164 |
|
</t> |
| 4165 |
|
<t> |
| 4166 |
|
<list> |
| 4167 |
|
<t>C: "REMOVE MIDI_INSTRUMENT_MAP ALL"</t> |
| 4168 |
|
<t>S: "OK"</t> |
| 4169 |
|
</list> |
| 4170 |
|
</t> |
| 4171 |
|
</section> |
| 4172 |
|
|
| 4173 |
|
<section title="Get amount of existing MIDI instrument maps" anchor="GET MIDI_INSTRUMENT_MAPS"> |
| 4174 |
|
<t>The front-end can retrieve the current amount of MIDI |
| 4175 |
|
instrument maps by sending the following command:</t> |
| 4176 |
|
<t> |
| 4177 |
|
<list> |
| 4178 |
|
<t>GET MIDI_INSTRUMENT_MAPS</t> |
| 4179 |
|
</list> |
| 4180 |
|
</t> |
| 4181 |
|
|
| 4182 |
|
<t>Possible Answers:</t> |
| 4183 |
|
<t> |
| 4184 |
|
<list> |
| 4185 |
|
<t>The sampler will answer by returning the current |
| 4186 |
|
number of MIDI instrument maps.</t> |
| 4187 |
|
</list> |
| 4188 |
|
</t> |
| 4189 |
|
|
| 4190 |
|
<t>Example:</t> |
| 4191 |
|
<t> |
| 4192 |
|
<list> |
| 4193 |
|
<t>C: "GET MIDI_INSTRUMENT_MAPS"</t> |
| 4194 |
|
<t>S: "2"</t> |
| 4195 |
|
</list> |
| 4196 |
|
</t> |
| 4197 |
|
</section> |
| 4198 |
|
|
| 4199 |
|
<section title="Getting all created MIDI instrument maps" anchor="LIST MIDI_INSTRUMENT_MAPS"> |
| 4200 |
|
<t>The number of MIDI instrument maps can change on runtime. To get the |
| 4201 |
|
current list of MIDI instrument maps, the front-end can send the |
| 4202 |
|
following command:</t> |
| 4203 |
|
<t> |
| 4204 |
|
<list> |
| 4205 |
|
<t>LIST MIDI_INSTRUMENT_MAPS</t> |
| 4206 |
|
</list> |
| 4207 |
|
</t> |
| 4208 |
|
<t>Possible Answers:</t> |
| 4209 |
|
<t> |
| 4210 |
|
<list> |
| 4211 |
|
<t>The sampler will answer by returning a comma separated list |
| 4212 |
|
with all MIDI instrument maps' numerical IDs.</t> |
| 4213 |
|
</list> |
| 4214 |
|
</t> |
| 4215 |
|
<t>Example:</t> |
| 4216 |
|
<t> |
| 4217 |
|
<list> |
| 4218 |
|
<t>C: "LIST MIDI_INSTRUMENT_MAPS"</t> |
| 4219 |
|
<t>S: "0,1,5,12"</t> |
| 4220 |
|
</list> |
| 4221 |
|
</t> |
| 4222 |
|
</section> |
| 4223 |
|
|
| 4224 |
|
<section title="Getting MIDI instrument map information" anchor="GET MIDI_INSTRUMENT_MAP INFO"> |
| 4225 |
|
<t>The front-end can ask for the current settings of a MIDI |
| 4226 |
|
instrument map by sending the following command:</t> |
| 4227 |
|
<t> |
| 4228 |
|
<list> |
| 4229 |
|
<t>GET MIDI_INSTRUMENT_MAP INFO <map></t> |
| 4230 |
|
</list> |
| 4231 |
|
</t> |
| 4232 |
|
<t>Where <map> is the numerical ID of the map the |
| 4233 |
|
front-end is interested in as returned by the |
| 4234 |
|
<xref target="LIST MIDI_INSTRUMENT_MAPS">"LIST MIDI_INSTRUMENT_MAPS"</xref> |
| 4235 |
|
command.</t> |
| 4236 |
|
|
| 4237 |
|
<t>Possible Answers:</t> |
| 4238 |
|
<t> |
| 4239 |
|
<list> |
| 4240 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
| 4241 |
|
Each answer line begins with the settings category name |
| 4242 |
|
followed by a colon and then a space character <SP> and finally |
| 4243 |
|
the info character string to that setting category. At the |
| 4244 |
|
moment the following categories are defined:</t> |
| 4245 |
|
|
| 4246 |
|
<t> |
| 4247 |
|
<list> |
| 4248 |
|
<t>NAME - |
| 4249 |
|
<list> |
| 4250 |
|
<t>custom name of the given map, |
| 4251 |
|
which does not have to be unique</t> |
| 4252 |
|
</list> |
| 4253 |
|
</t> |
| 4254 |
|
<t>DEFAULT - |
| 4255 |
|
<list> |
| 4256 |
|
<t>either true or false, |
| 4257 |
|
defines whether this map is the default map</t> |
| 4258 |
|
</list> |
| 4259 |
|
</t> |
| 4260 |
|
</list> |
| 4261 |
|
</t> |
| 4262 |
|
</list> |
| 4263 |
|
</t> |
| 4264 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 4265 |
|
|
| 4266 |
|
<t>Example:</t> |
| 4267 |
|
<t> |
| 4268 |
|
<list> |
| 4269 |
|
<t>C: "GET MIDI_INSTRUMENT_MAP INFO 0"</t> |
| 4270 |
|
<t>S: "NAME: Standard Map"</t> |
| 4271 |
|
<t> "DEFAULT: true"</t> |
| 4272 |
|
<t> "."</t> |
| 4273 |
|
</list> |
| 4274 |
|
</t> |
| 4275 |
|
</section> |
| 4276 |
|
|
| 4277 |
|
<section title="Renaming a MIDI instrument map" anchor="SET MIDI_INSTRUMENT_MAP NAME"> |
| 4278 |
|
<t>The front-end can alter the custom name of a MIDI |
| 4279 |
|
instrument map by sending the following command:</t> |
| 4280 |
|
<t> |
| 4281 |
|
<list> |
| 4282 |
|
<t>SET MIDI_INSTRUMENT_MAP NAME <map> <name></t> |
| 4283 |
|
</list> |
| 4284 |
|
</t> |
| 4285 |
|
<t>Where <map> is the numerical ID of the map and |
| 4286 |
|
<name> the new custom name of the map, which does not |
| 4287 |
|
have to be unique.</t> |
| 4288 |
|
|
| 4289 |
|
<t>Possible Answers:</t> |
| 4290 |
|
<t> |
| 4291 |
|
<list> |
| 4292 |
|
<t>"OK" - |
| 4293 |
|
<list> |
| 4294 |
|
<t>on success</t> |
| 4295 |
|
</list> |
| 4296 |
|
</t> |
| 4297 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4298 |
|
<list> |
| 4299 |
|
<t>in case the given map does not exist</t> |
| 4300 |
|
</list> |
| 4301 |
|
</t> |
| 4302 |
|
</list> |
| 4303 |
|
</t> |
| 4304 |
|
|
| 4305 |
|
<t>Example:</t> |
| 4306 |
|
<t> |
| 4307 |
|
<list> |
| 4308 |
|
<t>C: "SET MIDI_INSTRUMENT_MAP NAME 0 'Foo instruments'"</t> |
| 4309 |
|
<t>S: "OK"</t> |
| 4310 |
|
</list> |
| 4311 |
|
</t> |
| 4312 |
|
</section> |
| 4313 |
|
|
| 4314 |
|
<section title="Create or replace a MIDI instrument map entry" anchor="MAP MIDI_INSTRUMENT"> |
| 4315 |
|
<t>The front-end can create a new or replace an existing entry |
| 4316 |
|
in a sampler's MIDI instrument map by sending the following |
| 4317 |
|
command:</t> |
| 4318 |
|
<t> |
| 4319 |
|
<list> |
| 4320 |
|
<t>MAP MIDI_INSTRUMENT [NON_MODAL] <map> |
| 4321 |
|
<midi_bank> <midi_prog> <engine_name> |
| 4322 |
|
<filename> <instrument_index> <volume_value> |
| 4323 |
|
[<instr_load_mode>] [<name>]</t> |
| 4324 |
|
</list> |
| 4325 |
|
</t> |
| 4326 |
|
<t>Where <map> is the numeric ID of the map to alter, |
| 4327 |
|
<midi_bank> is an integer value between |
| 4328 |
|
0..16383 reflecting the MIDI bank select index, |
| 4329 |
|
<midi_prog> an |
| 4330 |
|
integer value between 0..127 reflecting the MIDI program change |
| 4331 |
|
index, <engine_name> a sampler engine name as returned by |
| 4332 |
|
the <xref target="LIST AVAILABLE_ENGINES">"LIST AVAILABLE_ENGINES"</xref> |
| 4333 |
|
command (not encapsulated into apostrophes), <filename> the name |
| 4334 |
|
of the instrument's file to be deployed (encapsulated into apostrophes, |
| 4335 |
|
supporting escape sequences as described in chapter |
| 4336 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>"), |
| 4337 |
|
<instrument_index> the index (integer value) of the instrument |
| 4338 |
|
within the given file, <volume_value> reflects the master |
| 4339 |
|
volume of the instrument as optionally dotted number (where a |
| 4340 |
|
value < 1.0 means attenuation and a value > 1.0 means |
| 4341 |
|
amplification). This parameter easily allows to adjust the |
| 4342 |
|
volume of all intruments within a custom instrument map |
| 4343 |
|
without having to adjust their instrument files. The |
| 4344 |
|
OPTIONAL <instr_load_mode> argument defines the life |
| 4345 |
|
time of the instrument, that is when the instrument should |
| 4346 |
|
be loaded, when freed and has exactly the following |
| 4347 |
|
possibilities:</t> |
| 4348 |
|
<t> |
| 4349 |
|
<list> |
| 4350 |
|
<t>"ON_DEMAND" - |
| 4351 |
|
<list> |
| 4352 |
|
<t>The instrument will be loaded when needed, |
| 4353 |
|
that is when demanded by at least one sampler |
| 4354 |
|
channel. It will immediately be freed from memory |
| 4355 |
|
when not needed by any sampler channel anymore.</t> |
| 4356 |
|
</list> |
| 4357 |
|
</t> |
| 4358 |
|
<t>"ON_DEMAND_HOLD" - |
| 4359 |
|
<list> |
| 4360 |
|
<t>The instrument will be loaded when needed, |
| 4361 |
|
that is when demanded by at least one sampler |
| 4362 |
|
channel. It will be kept in memory even when |
| 4363 |
|
not needed by any sampler channel anymore. |
| 4364 |
|
Instruments with this mode are only freed |
| 4365 |
|
when the sampler is reset or all mapping |
| 4366 |
|
entries with this mode (and respective |
| 4367 |
|
instrument) are explicitly changed to |
| 4368 |
|
"ON_DEMAND" and no sampler channel is using |
| 4369 |
|
the instrument anymore.</t> |
| 4370 |
|
</list> |
| 4371 |
|
</t> |
| 4372 |
|
<t>"PERSISTENT" - |
| 4373 |
|
<list> |
| 4374 |
|
<t>The instrument will immediately be loaded |
| 4375 |
|
into memory when this mapping |
| 4376 |
|
command is sent and the instrument is kept all |
| 4377 |
|
the time. Instruments with this mode are |
| 4378 |
|
only freed when the sampler is reset or all |
| 4379 |
|
mapping entries with this mode (and |
| 4380 |
|
respective instrument) are explicitly |
| 4381 |
|
changed to "ON_DEMAND" and no sampler |
| 4382 |
|
channel is using the instrument anymore.</t> |
| 4383 |
|
</list> |
| 4384 |
|
</t> |
| 4385 |
|
<t>not supplied - |
| 4386 |
|
<list> |
| 4387 |
|
<t>In case there is no <instr_load_mode> |
| 4388 |
|
argument given, it will be up to the |
| 4389 |
|
InstrumentManager to decide which mode to use. |
| 4390 |
|
Usually it will use "ON_DEMAND" if an entry |
| 4391 |
|
for the given instrument does not exist in |
| 4392 |
|
the InstrumentManager's list yet, otherwise |
| 4393 |
|
if an entry already exists, it will simply |
| 4394 |
|
stick with the mode currently reflected by |
| 4395 |
|
the already existing entry, that is it will |
| 4396 |
|
not change the mode.</t> |
| 4397 |
|
</list> |
| 4398 |
|
</t> |
| 4399 |
|
</list> |
| 4400 |
|
</t> |
| 4401 |
|
<t> |
| 4402 |
|
The <instr_load_mode> argument thus allows to define an |
| 4403 |
|
appropriate strategy (low memory consumption vs. fast |
| 4404 |
|
instrument switching) for each instrument individually. Note, the |
| 4405 |
|
following restrictions apply to this argument: "ON_DEMAND_HOLD" and |
| 4406 |
|
"PERSISTENT" have to be supported by the respective sampler engine |
| 4407 |
|
(which is technically the case when the engine provides an |
| 4408 |
|
InstrumentManager for its format). If this is not the case the |
| 4409 |
|
argument will automatically fall back to the default value |
| 4410 |
|
"ON_DEMAND". Also the load mode of one instrument may |
| 4411 |
|
automatically change the laod mode of other instrument(s), i.e. |
| 4412 |
|
because the instruments are part of the same file and the |
| 4413 |
|
engine does not allow a way to manage load modes for them |
| 4414 |
|
individually. Due to this, in case the frontend shows the |
| 4415 |
|
load modes of entries, the frontend should retrieve the actual |
| 4416 |
|
mode by i.e. sending |
| 4417 |
|
<xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref> |
| 4418 |
|
command(s). Finally the OPTIONAL <name> argument allows to |
| 4419 |
|
set a custom name (encapsulated into apostrophes) for the mapping |
| 4420 |
|
entry, useful for frontends for displaying an appropriate name for |
| 4421 |
|
mapped instruments (using |
| 4422 |
|
<xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref>). |
| 4423 |
|
</t> |
| 4424 |
|
<t> |
| 4425 |
|
By default, "MAP MIDI_INSTRUMENT" commands block until the mapping is |
| 4426 |
|
completely established in the sampler. The OPTIONAL "NON_MODAL" argument |
| 4427 |
|
however causes the respective "MAP MIDI_INSTRUMENT" command to return |
| 4428 |
|
immediately, that is to let the sampler establish the mapping in the |
| 4429 |
|
background. So this argument might be especially useful for mappings with |
| 4430 |
|
a "PERSISTENT" type, because these have to load the respective instruments |
| 4431 |
|
immediately and might thus block for a very long time. It is recommended |
| 4432 |
|
however to use the OPTIONAL "NON_MODAL" argument only if really necessary, |
| 4433 |
|
because it has the following drawbacks: as "NON_MODAL" instructions return |
| 4434 |
|
immediately, they may not necessarily return an error i.e. when the given |
| 4435 |
|
instrument file turns out to be corrupt, beside that subsequent commands |
| 4436 |
|
in a LSCP instruction sequence might fail, because mandatory mappings are |
| 4437 |
|
not yet completed. |
| 4438 |
|
</t> |
| 4439 |
|
|
| 4440 |
|
<t>Possible Answers:</t> |
| 4441 |
|
<t> |
| 4442 |
|
<list> |
| 4443 |
|
<t>"OK" - |
| 4444 |
|
<list> |
| 4445 |
|
<t>usually</t> |
| 4446 |
|
</list> |
| 4447 |
|
</t> |
| 4448 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4449 |
|
<list> |
| 4450 |
|
<t>when the given map or engine does not exist or a value |
| 4451 |
|
is out of range</t> |
| 4452 |
|
</list> |
| 4453 |
|
</t> |
| 4454 |
|
</list> |
| 4455 |
|
</t> |
| 4456 |
|
|
| 4457 |
|
<t>Examples:</t> |
| 4458 |
|
<t> |
| 4459 |
|
<list> |
| 4460 |
|
<t>C: "MAP MIDI_INSTRUMENT 0 3 0 gig '/usr/share/Steinway D.gig' 0 0.8 PERSISTENT"</t> |
| 4461 |
|
<t>S: "OK"</t> |
| 4462 |
|
</list> |
| 4463 |
|
</t> |
| 4464 |
|
<t> |
| 4465 |
|
<list> |
| 4466 |
|
<t>C: "MAP MIDI_INSTRUMENT 0 4 50 gig '/home/john/foostrings.gig' 7 1.0"</t> |
| 4467 |
|
<t>S: "OK"</t> |
| 4468 |
|
</list> |
| 4469 |
|
</t> |
| 4470 |
|
<t> |
| 4471 |
|
<list> |
| 4472 |
|
<t>C: "MAP MIDI_INSTRUMENT 0 0 0 gig '/usr/share/piano.gig' 0 1.0 'Normal Piano'"</t> |
| 4473 |
|
<t>S: "OK"</t> |
| 4474 |
|
<t>C: "MAP MIDI_INSTRUMENT 0 1 0 gig '/usr/share/piano.gig' 0 0.25 'Silent Piano'"</t> |
| 4475 |
|
<t>S: "OK"</t> |
| 4476 |
|
</list> |
| 4477 |
|
</t> |
| 4478 |
|
<t> |
| 4479 |
|
<list> |
| 4480 |
|
<t>C: "MAP MIDI_INSTRUMENT NON_MODAL 1 8 120 gig '/home/joe/foodrums.gig' 0 1.0 PERSISTENT 'Foo Drumkit'"</t> |
| 4481 |
|
<t>S: "OK"</t> |
| 4482 |
|
</list> |
| 4483 |
|
</t> |
| 4484 |
|
</section> |
| 4485 |
|
|
| 4486 |
|
<section title="Getting ammount of MIDI instrument map entries" anchor="GET MIDI_INSTRUMENTS"> |
| 4487 |
|
<t>The front-end can query the amount of currently existing |
| 4488 |
|
entries in a MIDI instrument map by sending the following |
| 4489 |
|
command:</t> |
| 4490 |
|
<t> |
| 4491 |
|
<list> |
| 4492 |
|
<t>GET MIDI_INSTRUMENTS <map></t> |
| 4493 |
|
</list> |
| 4494 |
|
</t> |
| 4495 |
|
<t>The front-end can query the amount of currently existing |
| 4496 |
|
entries in all MIDI instrument maps by sending the following |
| 4497 |
|
command:</t> |
| 4498 |
|
<t> |
| 4499 |
|
<list> |
| 4500 |
|
<t>GET MIDI_INSTRUMENTS ALL</t> |
| 4501 |
|
</list> |
| 4502 |
|
</t> |
| 4503 |
|
<t>Possible Answers:</t> |
| 4504 |
|
<t> |
| 4505 |
|
<list> |
| 4506 |
|
<t>The sampler will answer by sending the current number of |
| 4507 |
|
entries in the MIDI instrument map(s).</t> |
| 4508 |
|
</list> |
| 4509 |
|
</t> |
| 4510 |
|
|
| 4511 |
|
<t>Example:</t> |
| 4512 |
|
<t> |
| 4513 |
|
<list> |
| 4514 |
|
<t>C: "GET MIDI_INSTRUMENTS 0"</t> |
| 4515 |
|
<t>S: "234"</t> |
| 4516 |
|
</list> |
| 4517 |
|
</t> |
| 4518 |
|
<t> |
| 4519 |
|
<list> |
| 4520 |
|
<t>C: "GET MIDI_INSTRUMENTS ALL"</t> |
| 4521 |
|
<t>S: "954"</t> |
| 4522 |
|
</list> |
| 4523 |
|
</t> |
| 4524 |
|
</section> |
| 4525 |
|
|
| 4526 |
|
<section title="Getting indeces of all entries of a MIDI instrument map" anchor="LIST MIDI_INSTRUMENTS"> |
| 4527 |
|
<t>The front-end can query a list of all currently existing |
| 4528 |
|
entries in a certain MIDI instrument map by sending the following |
| 4529 |
|
command:</t> |
| 4530 |
|
<t> |
| 4531 |
|
<list> |
| 4532 |
|
<t>LIST MIDI_INSTRUMENTS <map></t> |
| 4533 |
|
</list> |
| 4534 |
|
</t> |
| 4535 |
|
<t>Where <map> is the numeric ID of the MIDI instrument map.</t> |
| 4536 |
|
<t>The front-end can query a list of all currently existing |
| 4537 |
|
entries of all MIDI instrument maps by sending the following |
| 4538 |
|
command:</t> |
| 4539 |
|
<t> |
| 4540 |
|
<list> |
| 4541 |
|
<t>LIST MIDI_INSTRUMENTS ALL</t> |
| 4542 |
|
</list> |
| 4543 |
|
</t> |
| 4544 |
|
|
| 4545 |
|
<t>Possible Answers:</t> |
| 4546 |
|
<t> |
| 4547 |
|
<list> |
| 4548 |
|
<t>The sampler will answer by sending a comma separated |
| 4549 |
|
list of map ID - MIDI bank - MIDI program triples, where |
| 4550 |
|
each triple is encapsulated into curly braces. The |
| 4551 |
|
list is returned in one single line. Each triple |
| 4552 |
|
just reflects the key of the respective map entry, |
| 4553 |
|
thus subsequent |
| 4554 |
|
<xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref> |
| 4555 |
|
command(s) are necessary to retrieve detailed informations |
| 4556 |
|
about each entry.</t> |
| 4557 |
|
</list> |
| 4558 |
|
</t> |
| 4559 |
|
|
| 4560 |
|
<t>Example:</t> |
| 4561 |
|
<t> |
| 4562 |
|
<list> |
| 4563 |
|
<t>C: "LIST MIDI_INSTRUMENTS 0"</t> |
| 4564 |
|
<t>S: "{0,0,0},{0,0,1},{0,0,3},{0,1,4},{1,127,127}"</t> |
| 4565 |
|
</list> |
| 4566 |
|
</t> |
| 4567 |
|
</section> |
| 4568 |
|
|
| 4569 |
|
<section title="Remove an entry from the MIDI instrument map" anchor="UNMAP MIDI_INSTRUMENT"> |
| 4570 |
|
<t>The front-end can delete an entry from a MIDI instrument |
| 4571 |
|
map by sending the following command:</t> |
| 4572 |
|
<t> |
| 4573 |
|
<list> |
| 4574 |
|
<t>UNMAP MIDI_INSTRUMENT <map> <midi_bank> <midi_prog></t> |
| 4575 |
|
</list> |
| 4576 |
|
</t> |
| 4577 |
|
<t> |
| 4578 |
|
Where <map> is the numeric ID of the MIDI instrument map, |
| 4579 |
|
<midi_bank> is an integer value between 0..16383 |
| 4580 |
|
reflecting the MIDI bank value and |
| 4581 |
|
<midi_prog> an integer value between |
| 4582 |
|
0..127 reflecting the MIDI program value of the map's entrie's key |
| 4583 |
|
index triple. |
| 4584 |
|
</t> |
| 4585 |
|
|
| 4586 |
|
<t>Possible Answers:</t> |
| 4587 |
|
<t> |
| 4588 |
|
<list> |
| 4589 |
|
<t>"OK" - |
| 4590 |
|
<list> |
| 4591 |
|
<t>usually</t> |
| 4592 |
|
</list> |
| 4593 |
|
</t> |
| 4594 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4595 |
|
<list> |
| 4596 |
|
<t>when index out of bounds</t> |
| 4597 |
|
</list> |
| 4598 |
|
</t> |
| 4599 |
|
</list> |
| 4600 |
|
</t> |
| 4601 |
|
|
| 4602 |
|
<t>Example:</t> |
| 4603 |
|
<t> |
| 4604 |
|
<list> |
| 4605 |
|
<t>C: "UNMAP MIDI_INSTRUMENT 0 2 127"</t> |
| 4606 |
|
<t>S: "OK"</t> |
| 4607 |
|
</list> |
| 4608 |
|
</t> |
| 4609 |
|
</section> |
| 4610 |
|
|
| 4611 |
|
<section title="Get current settings of MIDI instrument map entry" anchor="GET MIDI_INSTRUMENT INFO"> |
| 4612 |
|
<t>The front-end can retrieve the current settings of a certain |
| 4613 |
|
instrument map entry by sending the following command:</t> |
| 4614 |
|
<t> |
| 4615 |
|
<list> |
| 4616 |
|
<t>GET MIDI_INSTRUMENT INFO <map> <midi_bank> <midi_prog></t> |
| 4617 |
|
</list> |
| 4618 |
|
</t> |
| 4619 |
|
<t> |
| 4620 |
|
Where <map> is the numeric ID of the MIDI instrument map, |
| 4621 |
|
<midi_bank> is an integer value between 0..16383 |
| 4622 |
|
reflecting the MIDI bank value, <midi_bank> |
| 4623 |
|
and <midi_prog> an integer value between |
| 4624 |
|
0..127 reflecting the MIDI program value of the map's entrie's key |
| 4625 |
|
index triple. |
| 4626 |
|
</t> |
| 4627 |
|
|
| 4628 |
|
<t>Possible Answers:</t> |
| 4629 |
|
<t> |
| 4630 |
|
<list> |
| 4631 |
|
<t>LinuxSampler will answer by sending a <CRLF> |
| 4632 |
|
separated list. Each answer line begins with the |
| 4633 |
|
information category name followed by a colon and then |
| 4634 |
|
a space character <SP> and finally the info |
| 4635 |
|
character string to that info category. At the moment |
| 4636 |
|
the following categories are defined:</t> |
| 4637 |
|
<t>"NAME" - |
| 4638 |
|
<list> |
| 4639 |
|
<t>Name for this MIDI instrument map entry (if defined). |
| 4640 |
|
This name shall be used by frontends for displaying a |
| 4641 |
|
name for this mapped instrument. It can be set and |
| 4642 |
|
changed with the |
| 4643 |
|
<xref target="MAP MIDI_INSTRUMENT">"MAP MIDI_INSTRUMENT"</xref> |
| 4644 |
|
command and does not have to be unique.</t> |
| 4645 |
|
</list> |
| 4646 |
|
</t> |
| 4647 |
|
<t>"ENGINE_NAME" - |
| 4648 |
|
<list> |
| 4649 |
|
<t>Name of the engine to be deployed for this |
| 4650 |
|
instrument.</t> |
| 4651 |
|
</list> |
| 4652 |
|
</t> |
| 4653 |
|
<t>"INSTRUMENT_FILE" - |
| 4654 |
|
<list> |
| 4655 |
|
<t>File name of the instrument.</t> |
| 4656 |
|
</list> |
| 4657 |
|
</t> |
| 4658 |
|
<t>"INSTRUMENT_NR" - |
| 4659 |
|
<list> |
| 4660 |
|
<t>Index of the instrument within the file.</t> |
| 4661 |
|
</list> |
| 4662 |
|
</t> |
| 4663 |
|
<t>"INSTRUMENT_NAME" - |
| 4664 |
|
<list> |
| 4665 |
|
<t>Name of the loaded instrument as reflected by its file. |
| 4666 |
|
In contrast to the "NAME" field, the "INSTRUMENT_NAME" field |
| 4667 |
|
cannot be changed.</t> |
| 4668 |
|
</list> |
| 4669 |
|
</t> |
| 4670 |
|
<t>"LOAD_MODE" - |
| 4671 |
|
<list> |
| 4672 |
|
<t>Life time of instrument |
| 4673 |
|
(see <xref target="MAP MIDI_INSTRUMENT">"MAP MIDI_INSTRUMENT"</xref> for details about this setting).</t> |
| 4674 |
|
</list> |
| 4675 |
|
</t> |
| 4676 |
|
<t>"VOLUME" - |
| 4677 |
|
<list> |
| 4678 |
|
<t>master volume of the instrument as optionally |
| 4679 |
|
dotted number (where a value < 1.0 means attenuation |
| 4680 |
|
and a value > 1.0 means amplification)</t> |
| 4681 |
|
</list> |
| 4682 |
|
</t> |
| 4683 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 4684 |
|
</list> |
| 4685 |
|
</t> |
| 4686 |
|
|
| 4687 |
|
<t>Example:</t> |
| 4688 |
|
<t> |
| 4689 |
|
<list> |
| 4690 |
|
<t>C: "GET MIDI_INSTRUMENT INFO 1 45 120"</t> |
| 4691 |
|
<t>S: "NAME: Drums for Foo Song"</t> |
| 4692 |
|
<t> "ENGINE_NAME: GigEngine"</t> |
| 4693 |
|
<t> "INSTRUMENT_FILE: /usr/share/joesdrumkit.gig"</t> |
| 4694 |
|
<t> "INSTRUMENT_NR: 0"</t> |
| 4695 |
|
<t> "INSTRUMENT_NAME: Joe's Drumkit"</t> |
| 4696 |
|
<t> "LOAD_MODE: PERSISTENT"</t> |
| 4697 |
|
<t> "VOLUME: 1.0"</t> |
| 4698 |
|
<t> "."</t> |
| 4699 |
|
</list> |
| 4700 |
|
</t> |
| 4701 |
|
</section> |
| 4702 |
|
|
| 4703 |
|
<section title="Clear MIDI instrument map" anchor="CLEAR MIDI_INSTRUMENTS"> |
| 4704 |
|
<t>The front-end can clear a whole MIDI instrument map, that |
| 4705 |
|
is delete all its entries by sending the following command:</t> |
| 4706 |
|
<t> |
| 4707 |
|
<list> |
| 4708 |
|
<t>CLEAR MIDI_INSTRUMENTS <map></t> |
| 4709 |
|
</list> |
| 4710 |
|
</t> |
| 4711 |
|
<t>Where <map> is the numeric ID of the map to clear.</t> |
| 4712 |
|
<t>The front-end can clear all MIDI instrument maps, that |
| 4713 |
|
is delete all entries of all maps by sending the following |
| 4714 |
|
command:</t> |
| 4715 |
|
<t> |
| 4716 |
|
<list> |
| 4717 |
|
<t>CLEAR MIDI_INSTRUMENTS ALL</t> |
| 4718 |
|
</list> |
| 4719 |
|
</t> |
| 4720 |
|
<t>The command "CLEAR MIDI_INSTRUMENTS ALL" does not delete the |
| 4721 |
|
maps, only their entries, thus the map's settings like |
| 4722 |
|
custom name will be preservevd.</t> |
| 4723 |
|
|
| 4724 |
|
<t>Possible Answers:</t> |
| 4725 |
|
<t> |
| 4726 |
|
<list> |
| 4727 |
|
<t>"OK" - |
| 4728 |
|
<list> |
| 4729 |
|
<t>always</t> |
| 4730 |
|
</list> |
| 4731 |
|
</t> |
| 4732 |
|
</list> |
| 4733 |
|
</t> |
| 4734 |
|
|
| 4735 |
|
<t>Examples:</t> |
| 4736 |
|
<t> |
| 4737 |
|
<list> |
| 4738 |
|
<t>C: "CLEAR MIDI_INSTRUMENTS 0"</t> |
| 4739 |
|
<t>S: "OK"</t> |
| 4740 |
|
</list> |
| 4741 |
|
</t> |
| 4742 |
|
<t> |
| 4743 |
|
<list> |
| 4744 |
|
<t>C: "CLEAR MIDI_INSTRUMENTS ALL"</t> |
| 4745 |
|
<t>S: "OK"</t> |
| 4746 |
|
</list> |
| 4747 |
|
</t> |
| 4748 |
|
</section> |
| 4749 |
|
</section> |
| 4750 |
|
|
| 4751 |
|
|
| 4752 |
|
<section title="Managing Instruments Database" anchor="Managing Instruments Database"> |
| 4753 |
|
<t>The following commands describe how to use and manage |
| 4754 |
|
the instruments database.</t> |
| 4755 |
|
|
| 4756 |
|
<section title="Creating a new instrument directory" anchor="ADD DB_INSTRUMENT_DIRECTORY"> |
| 4757 |
|
<t>The front-end can add a new instrument directory to the |
| 4758 |
|
instruments database by sending the following command:</t> |
| 4759 |
|
<t> |
| 4760 |
|
<list> |
| 4761 |
|
<t>ADD DB_INSTRUMENT_DIRECTORY <dir></t> |
| 4762 |
|
</list> |
| 4763 |
|
</t> |
| 4764 |
|
<t>Where <dir> is the absolute path name of the directory |
| 4765 |
|
to be created (encapsulated into apostrophes).</t> |
| 4766 |
|
|
| 4767 |
|
<t>Possible Answers:</t> |
| 4768 |
|
<t> |
| 4769 |
|
<list> |
| 4770 |
|
<t>"OK" - |
| 4771 |
|
<list> |
| 4772 |
|
<t>on success</t> |
| 4773 |
|
</list> |
| 4774 |
|
</t> |
| 4775 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4776 |
|
<list> |
| 4777 |
|
<t>when the directory could not be created, which |
| 4778 |
|
can happen if the directory already exists or the |
| 4779 |
|
name contains not allowed symbols</t> |
| 4780 |
|
</list> |
| 4781 |
|
</t> |
| 4782 |
|
</list> |
| 4783 |
|
</t> |
| 4784 |
|
|
| 4785 |
|
<t>Examples:</t> |
| 4786 |
|
<t> |
| 4787 |
|
<list> |
| 4788 |
|
<t>C: "ADD DB_INSTRUMENT_DIRECTORY '/Piano Collection'"</t> |
| 4789 |
|
<t>S: "OK"</t> |
| 4790 |
|
</list> |
| 4791 |
|
</t> |
| 4792 |
|
</section> |
| 4793 |
|
|
| 4794 |
|
<section title="Deleting an instrument directory" anchor="REMOVE DB_INSTRUMENT_DIRECTORY"> |
| 4795 |
|
<t>The front-end can delete a particular instrument directory |
| 4796 |
|
from the instruments database by sending the following command:</t> |
| 4797 |
|
<t> |
| 4798 |
|
<list> |
| 4799 |
|
<t>REMOVE DB_INSTRUMENT_DIRECTORY [FORCE] <dir></t> |
| 4800 |
|
</list> |
| 4801 |
|
</t> |
| 4802 |
|
<t>Where <dir> is the absolute path name of the directory |
| 4803 |
|
to delete. The optional FORCE argument can be used to |
| 4804 |
|
force the deletion of a non-empty directory and all its content.</t> |
| 4805 |
|
|
| 4806 |
|
<t>Possible Answers:</t> |
| 4807 |
|
<t> |
| 4808 |
|
<list> |
| 4809 |
|
<t>"OK" - |
| 4810 |
|
<list> |
| 4811 |
|
<t>if the directory is deleted successfully</t> |
| 4812 |
|
</list> |
| 4813 |
|
</t> |
| 4814 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4815 |
|
<list> |
| 4816 |
|
<t>if the given directory does not exist, or |
| 4817 |
|
if trying to delete a non-empty directory, |
| 4818 |
|
without using the FORCE argument.</t> |
| 4819 |
|
</list> |
| 4820 |
|
</t> |
| 4821 |
|
</list> |
| 4822 |
|
</t> |
| 4823 |
|
|
| 4824 |
|
<t>Examples:</t> |
| 4825 |
|
<t> |
| 4826 |
|
<list> |
| 4827 |
|
<t>C: "REMOVE DB_INSTRUMENT_DIRECTORY FORCE '/Piano Collection'"</t> |
| 4828 |
|
<t>S: "OK"</t> |
| 4829 |
|
</list> |
| 4830 |
|
</t> |
| 4831 |
|
</section> |
| 4832 |
|
|
| 4833 |
|
<section title="Getting amount of instrument directories" anchor="GET DB_INSTRUMENT_DIRECTORIES"> |
| 4834 |
|
<t>The front-end can retrieve the current amount of |
| 4835 |
|
directories in a specific directory by sending the following command:</t> |
| 4836 |
|
<t> |
| 4837 |
|
<list> |
| 4838 |
|
<t>GET DB_INSTRUMENT_DIRECTORIES [RECURSIVE] <dir></t> |
| 4839 |
|
</list> |
| 4840 |
|
</t> |
| 4841 |
|
<t>Where <dir> should be replaced by the absolute path |
| 4842 |
|
name of the directory. If RECURSIVE is specified, the number of |
| 4843 |
|
all directories, including those located in subdirectories of the |
| 4844 |
|
specified directory, will be returned.</t> |
| 4845 |
|
|
| 4846 |
|
<t>Possible Answers:</t> |
| 4847 |
|
<t> |
| 4848 |
|
<list> |
| 4849 |
|
<t>The current number of instrument directories |
| 4850 |
|
in the specified directory.</t> |
| 4851 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4852 |
|
<list> |
| 4853 |
|
<t>if the given directory does not exist.</t> |
| 4854 |
|
</list> |
| 4855 |
|
</t> |
| 4856 |
|
</list> |
| 4857 |
|
</t> |
| 4858 |
|
|
| 4859 |
|
<t>Example:</t> |
| 4860 |
|
<t> |
| 4861 |
|
<list> |
| 4862 |
|
<t>C: "GET DB_INSTRUMENT_DIRECTORIES '/'"</t> |
| 4863 |
|
<t>S: "2"</t> |
| 4864 |
|
</list> |
| 4865 |
|
</t> |
| 4866 |
|
</section> |
| 4867 |
|
|
| 4868 |
|
<section title="Listing all directories in specific directory" anchor="LIST DB_INSTRUMENT_DIRECTORIES"> |
| 4869 |
|
<t>The front-end can retrieve the current list of directories |
| 4870 |
|
in specific directory by sending the following command:</t> |
| 4871 |
|
<t> |
| 4872 |
|
<list> |
| 4873 |
|
<t>LIST DB_INSTRUMENT_DIRECTORIES [RECURSIVE] <dir></t> |
| 4874 |
|
</list> |
| 4875 |
|
</t> |
| 4876 |
|
<t>Where <dir> should be replaced by the absolute path |
| 4877 |
|
name of the directory. If RECURSIVE is specified, the absolute path names |
| 4878 |
|
of all directories, including those located in subdirectories of the |
| 4879 |
|
specified directory, will be returned.</t> |
| 4880 |
|
|
| 4881 |
|
<t>Possible Answers:</t> |
| 4882 |
|
<t> |
| 4883 |
|
<list> |
| 4884 |
|
<t>A comma separated list of all instrument directories |
| 4885 |
|
(encapsulated into apostrophes) in the specified directory.</t> |
| 4886 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4887 |
|
<list> |
| 4888 |
|
<t>if the given directory does not exist.</t> |
| 4889 |
|
</list> |
| 4890 |
|
</t> |
| 4891 |
|
</list> |
| 4892 |
|
</t> |
| 4893 |
|
<t>Example:</t> |
| 4894 |
|
<t> |
| 4895 |
|
<list> |
| 4896 |
|
<t>C: "LIST DB_INSTRUMENT_DIRECTORIES '/'"</t> |
| 4897 |
|
<t>S: "'Piano Collection','Percussion Collection'"</t> |
| 4898 |
|
</list> |
| 4899 |
|
</t> |
| 4900 |
|
<t> |
| 4901 |
|
<list> |
| 4902 |
|
<t>C: "LIST DB_INSTRUMENT_DIRECTORIES RECURSIVE '/'"</t> |
| 4903 |
|
<t>S: "'/Piano Collection','/Piano Collection/Acoustic','/Piano Collection/Acoustic/New','/Percussion Collection'"</t> |
| 4904 |
|
</list> |
| 4905 |
|
</t> |
| 4906 |
|
</section> |
| 4907 |
|
|
| 4908 |
|
<section title="Getting instrument directory information" anchor="GET DB_INSTRUMENT_DIRECTORY INFO"> |
| 4909 |
|
<t>The front-end can ask for the current settings of an |
| 4910 |
|
instrument directory by sending the following command:</t> |
| 4911 |
|
<t> |
| 4912 |
|
<list> |
| 4913 |
|
<t>GET DB_INSTRUMENT_DIRECTORY INFO <dir></t> |
| 4914 |
|
</list> |
| 4915 |
|
</t> |
| 4916 |
|
<t>Where <dir> should be replaced by the absolute path |
| 4917 |
|
name of the directory the front-end is interested in.</t> |
| 4918 |
|
|
| 4919 |
|
<t>Possible Answers:</t> |
| 4920 |
|
<t> |
| 4921 |
|
<list> |
| 4922 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
| 4923 |
|
Each answer line begins with the settings category name |
| 4924 |
|
followed by a colon and then a space character <SP> and finally |
| 4925 |
|
the info character string to that setting category. At the |
| 4926 |
|
moment the following categories are defined:</t> |
| 4927 |
|
|
| 4928 |
|
<t> |
| 4929 |
|
<list> |
| 4930 |
|
<t>DESCRIPTION - |
| 4931 |
|
<list> |
| 4932 |
|
<t>A brief description of the directory content</t> |
| 4933 |
|
</list> |
| 4934 |
|
</t> |
| 4935 |
|
<t>CREATED - |
| 4936 |
|
<list> |
| 4937 |
|
<t>The creation date and time of the directory, |
| 4938 |
|
represented in "YYYY-MM-DD HH:MM:SS" format</t> |
| 4939 |
|
</list> |
| 4940 |
|
</t> |
| 4941 |
|
<t>MODIFIED - |
| 4942 |
|
<list> |
| 4943 |
|
<t>The date and time of the last modification of the |
| 4944 |
|
directory, represented in "YYYY-MM-DD HH:MM:SS" format</t> |
| 4945 |
|
</list> |
| 4946 |
|
</t> |
| 4947 |
|
</list> |
| 4948 |
|
</t> |
| 4949 |
|
</list> |
| 4950 |
|
</t> |
| 4951 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 4952 |
|
|
| 4953 |
|
<t>Example:</t> |
| 4954 |
|
<t> |
| 4955 |
|
<list> |
| 4956 |
|
<t>C: "GET DB_INSTRUMENT_DIRECTORY INFO '/Piano Collection'"</t> |
| 4957 |
|
<t>S: "DESCRIPTION: Piano collection of instruments in GigaSampler format."</t> |
| 4958 |
|
<t> "CREATED: 2007-02-05 10:23:12"</t> |
| 4959 |
|
<t> "MODIFIED: 2007-04-07 12:50:21"</t> |
| 4960 |
|
<t> "."</t> |
| 4961 |
|
</list> |
| 4962 |
|
</t> |
| 4963 |
|
</section> |
| 4964 |
|
|
| 4965 |
|
<section title="Renaming an instrument directory" anchor="SET DB_INSTRUMENT_DIRECTORY NAME"> |
| 4966 |
|
<t>The front-end can alter the name of a specific |
| 4967 |
|
instrument directory by sending the following command:</t> |
| 4968 |
|
<t> |
| 4969 |
|
<list> |
| 4970 |
|
<t>SET DB_INSTRUMENT_DIRECTORY NAME <dir> <name></t> |
| 4971 |
|
</list> |
| 4972 |
|
</t> |
| 4973 |
|
<t>Where <dir> is the absolute path name of the directory and |
| 4974 |
|
<name> is the new name for that directory.</t> |
| 4975 |
|
|
| 4976 |
|
<t>Possible Answers:</t> |
| 4977 |
|
<t> |
| 4978 |
|
<list> |
| 4979 |
|
<t>"OK" - |
| 4980 |
|
<list> |
| 4981 |
|
<t>on success</t> |
| 4982 |
|
</list> |
| 4983 |
|
</t> |
| 4984 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4985 |
|
<list> |
| 4986 |
|
<t>in case the given directory does not exists, |
| 4987 |
|
or if a directory with name equal to the new |
| 4988 |
|
name already exists.</t> |
| 4989 |
|
</list> |
| 4990 |
|
</t> |
| 4991 |
|
</list> |
| 4992 |
|
</t> |
| 4993 |
|
|
| 4994 |
|
<t>Example:</t> |
| 4995 |
|
<t> |
| 4996 |
|
<list> |
| 4997 |
|
<t>C: "SET DB_INSTRUMENT_DIRECTORY NAME '/Piano Collection/Acustic' 'Acoustic'"</t> |
| 4998 |
|
<t>S: "OK"</t> |
| 4999 |
|
</list> |
| 5000 |
|
</t> |
| 5001 |
|
</section> |
| 5002 |
|
|
| 5003 |
|
<section title="Moving an instrument directory" anchor="MOVE DB_INSTRUMENT_DIRECTORY"> |
| 5004 |
|
<t>The front-end can move a specific |
| 5005 |
|
instrument directory by sending the following command:</t> |
| 5006 |
|
<t> |
| 5007 |
|
<list> |
| 5008 |
|
<t>MOVE DB_INSTRUMENT_DIRECTORY <dir> <dst></t> |
| 5009 |
|
</list> |
| 5010 |
|
</t> |
| 5011 |
|
<t>Where <dir> is the absolute path name of the directory |
| 5012 |
|
to move and <dst> is the location where the directory will |
| 5013 |
|
be moved to.</t> |
| 5014 |
|
|
| 5015 |
|
<t>Possible Answers:</t> |
| 5016 |
|
<t> |
| 5017 |
|
<list> |
| 5018 |
|
<t>"OK" - |
| 5019 |
|
<list> |
| 5020 |
|
<t>on success</t> |
| 5021 |
|
</list> |
| 5022 |
|
</t> |
| 5023 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5024 |
|
<list> |
| 5025 |
|
<t>in case a given directory does not exists, |
| 5026 |
|
or if a directory with name equal to the name |
| 5027 |
|
of the specified directory already exists in |
| 5028 |
|
the destination directory. Error is also thrown |
| 5029 |
|
when trying to move a directory to a subdirectory |
| 5030 |
|
of itself.</t> |
| 5031 |
|
</list> |
| 5032 |
|
</t> |
| 5033 |
|
</list> |
| 5034 |
|
</t> |
| 5035 |
|
|
| 5036 |
|
<t>Example:</t> |
| 5037 |
|
<t> |
| 5038 |
|
<list> |
| 5039 |
|
<t>C: "MOVE DB_INSTRUMENT_DIRECTORY '/Acoustic' '/Piano Collection/Acoustic'"</t> |
| 5040 |
|
<t>S: "OK"</t> |
| 5041 |
|
</list> |
| 5042 |
|
</t> |
| 5043 |
|
</section> |
| 5044 |
|
|
| 5045 |
|
<section title="Copying instrument directories" anchor="COPY DB_INSTRUMENT_DIRECTORY"> |
| 5046 |
|
<t>The front-end can copy a specific |
| 5047 |
|
instrument directory by sending the following command:</t> |
| 5048 |
|
<t> |
| 5049 |
|
<list> |
| 5050 |
|
<t>COPY DB_INSTRUMENT_DIRECTORY <dir> <dst></t> |
| 5051 |
|
</list> |
| 5052 |
|
</t> |
| 5053 |
|
<t>Where <dir> is the absolute path name of the directory |
| 5054 |
|
to copy and <dst> is the location where the directory will |
| 5055 |
|
be copied to.</t> |
| 5056 |
|
|
| 5057 |
|
<t>Possible Answers:</t> |
| 5058 |
|
<t> |
| 5059 |
|
<list> |
| 5060 |
|
<t>"OK" - |
| 5061 |
|
<list> |
| 5062 |
|
<t>on success</t> |
| 5063 |
|
</list> |
| 5064 |
|
</t> |
| 5065 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5066 |
|
<list> |
| 5067 |
|
<t>in case a given directory does not exists, |
| 5068 |
|
or if a directory with name equal to the name |
| 5069 |
|
of the specified directory already exists in |
| 5070 |
|
the destination directory. Error is also thrown |
| 5071 |
|
when trying to copy a directory to a subdirectory |
| 5072 |
|
of itself.</t> |
| 5073 |
|
</list> |
| 5074 |
|
</t> |
| 5075 |
|
</list> |
| 5076 |
|
</t> |
| 5077 |
|
|
| 5078 |
|
<t>Example:</t> |
| 5079 |
|
<t> |
| 5080 |
|
<list> |
| 5081 |
|
<t>C: "COPY DB_INSTRUMENT_DIRECTORY '/Piano Collection/Acoustic' '/Acoustic/Pianos'"</t> |
| 5082 |
|
<t>S: "OK"</t> |
| 5083 |
|
</list> |
| 5084 |
|
</t> |
| 5085 |
|
</section> |
| 5086 |
|
|
| 5087 |
|
<section title="Changing the description of directory" anchor="SET DB_INSTRUMENT_DIRECTORY DESCRIPTION"> |
| 5088 |
|
<t>The front-end can alter the description of a specific |
| 5089 |
|
instrument directory by sending the following command:</t> |
| 5090 |
|
<t> |
| 5091 |
|
<list> |
| 5092 |
|
<t>SET DB_INSTRUMENT_DIRECTORY DESCRIPTION <dir> <desc></t> |
| 5093 |
|
</list> |
| 5094 |
|
</t> |
| 5095 |
|
<t>Where <dir> is the absolute path name of the directory and |
| 5096 |
|
<desc> is the new description for the directory.</t> |
| 5097 |
|
|
| 5098 |
|
<t>Possible Answers:</t> |
| 5099 |
|
<t> |
| 5100 |
|
<list> |
| 5101 |
|
<t>"OK" - |
| 5102 |
|
<list> |
| 5103 |
|
<t>on success</t> |
| 5104 |
|
</list> |
| 5105 |
|
</t> |
| 5106 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5107 |
|
<list> |
| 5108 |
|
<t>in case the given directory does not exists.</t> |
| 5109 |
|
</list> |
| 5110 |
|
</t> |
| 5111 |
|
</list> |
| 5112 |
|
</t> |
| 5113 |
|
|
| 5114 |
|
<t>Example:</t> |
| 5115 |
|
<t> |
| 5116 |
|
<list> |
| 5117 |
|
<t>C: "SET DB_INSTRUMENT_DIRECTORY DESCRIPTION '/Piano Collection' 'A collection of piano instruments in various format.'"</t> |
| 5118 |
|
<t>S: "OK"</t> |
| 5119 |
|
</list> |
| 5120 |
|
</t> |
| 5121 |
|
</section> |
| 5122 |
|
|
| 5123 |
|
<section title="Finding directories" anchor="FIND DB_INSTRUMENT_DIRECTORIES"> |
| 5124 |
|
<t>The front-end can search for directories |
| 5125 |
|
in specific directory by sending the following command:</t> |
| 5126 |
|
<t> |
| 5127 |
|
<list> |
| 5128 |
|
<t>FIND DB_INSTRUMENT_DIRECTORIES [NON_RECURSIVE] <dir> <criteria-list></t> |
| 5129 |
|
</list> |
| 5130 |
|
</t> |
| 5131 |
|
<t>Where <dir> should be replaced by the absolute path |
| 5132 |
|
name of the directory to search in. If NON_RECURSIVE is specified, the |
| 5133 |
|
directories located in subdirectories of the specified directory will not |
| 5134 |
|
be searched. <criteria-list> is a list of search criterias |
| 5135 |
|
in form of "key1=val1 key2=val2 ...". The following criterias are |
| 5136 |
|
allowed:</t> |
| 5137 |
|
<t> |
| 5138 |
|
<t>NAME='<search-string>' |
| 5139 |
|
<list> |
| 5140 |
|
<t>Restricts the search to directories, which names |
| 5141 |
|
satisfy the supplied search string.</t> |
| 5142 |
|
</list> |
| 5143 |
|
</t> |
| 5144 |
|
|
| 5145 |
|
<t>CREATED='[<date-after>]..[<date-before>]' |
| 5146 |
|
<list> |
| 5147 |
|
<t>Restricts the search to directories, which creation |
| 5148 |
|
date satisfies the specified period, where <date-after> |
| 5149 |
|
and <date-before> are in "YYYY-MM-DD HH:MM:SS" format. |
| 5150 |
|
If <date-after> is omitted the search is restricted to |
| 5151 |
|
directories created before <date-before>. If |
| 5152 |
|
<date-before> is omitted, the search is restricted |
| 5153 |
|
to directories created after <date-after>.</t> |
| 5154 |
|
</list> |
| 5155 |
|
</t> |
| 5156 |
|
|
| 5157 |
|
<t>MODIFIED='[<date-after>]..[<date-before>]' |
| 5158 |
|
<list> |
| 5159 |
|
<t>Restricts the search to directories, which |
| 5160 |
|
date of last modification satisfies the specified period, where |
| 5161 |
|
<date-after> and <date-before> are in "YYYY-MM-DD HH:MM:SS" |
| 5162 |
|
format. If <date-after> is omitted the search is restricted to |
| 5163 |
|
directories, which are last modified before <date-before>. If |
| 5164 |
|
<date-before> is omitted, the search is restricted to directories, |
| 5165 |
|
which are last modified after <date-after>.</t> |
| 5166 |
|
</list> |
| 5167 |
|
</t> |
| 5168 |
|
|
| 5169 |
|
<t>DESCRIPTION='<search-string>' |
| 5170 |
|
<list> |
| 5171 |
|
<t>Restricts the search to directories with description |
| 5172 |
|
that satisfies the supplied search string.</t> |
| 5173 |
|
</list> |
| 5174 |
|
</t> |
| 5175 |
|
</t> |
| 5176 |
|
|
| 5177 |
|
<t>Where <search-string> is either a regular expression, or a |
| 5178 |
|
word list separated with spaces for OR search and with '+' for AND search.</t> |
| 5179 |
|
|
| 5180 |
|
<t>Possible Answers:</t> |
| 5181 |
|
<t> |
| 5182 |
|
<list> |
| 5183 |
|
<t>A comma separated list with the absolute path names (encapsulated into |
| 5184 |
|
apostrophes) of all directories in the specified directory that satisfy |
| 5185 |
|
the supplied search criterias.</t> |
| 5186 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5187 |
|
<list> |
| 5188 |
|
<t>if the given directory does not exist.</t> |
| 5189 |
|
</list> |
| 5190 |
|
</t> |
| 5191 |
|
</list> |
| 5192 |
|
</t> |
| 5193 |
|
<t>Example:</t> |
| 5194 |
|
<t> |
| 5195 |
|
<list> |
| 5196 |
|
<t>C: "FIND DB_INSTRUMENT_DIRECTORIES '/' NAME='Piano'"</t> |
| 5197 |
|
<t>S: "'/Piano Collection'"</t> |
| 5198 |
|
</list> |
| 5199 |
|
</t> |
| 5200 |
|
<t> |
| 5201 |
|
<list> |
| 5202 |
|
<t>C: "FIND DB_INSTRUMENT_DIRECTORIES '/' CREATED='..2007-04-01 09:30:13'"</t> |
| 5203 |
|
<t>S: "'/Piano Collection','/Percussions'"</t> |
| 5204 |
|
</list> |
| 5205 |
|
</t> |
| 5206 |
|
</section> |
| 5207 |
|
|
| 5208 |
|
<section title="Adding instruments to the instruments database" anchor="ADD DB_INSTRUMENTS"> |
| 5209 |
|
<t>The front-end can add one or more instruments |
| 5210 |
|
to the instruments database by sending the following command:</t> |
| 5211 |
|
<t> |
| 5212 |
|
<list> |
| 5213 |
|
<t>ADD DB_INSTRUMENTS [NON_MODAL] [<mode>] <db_dir> <file_path> [<instr_index>]</t> |
| 5214 |
|
</list> |
| 5215 |
|
</t> |
| 5216 |
|
<t>Where <db_dir> is the absolute path name of a directory |
| 5217 |
|
(encapsulated into apostrophes) in the instruments database in which |
| 5218 |
|
only the new instruments (that are not already in the database) will |
| 5219 |
|
be added, <file_path> is the absolute path name of a file or |
| 5220 |
|
directory in the file system (encapsulated into apostrophes). In case |
| 5221 |
|
an instrument file is supplied, only the instruments in the specified |
| 5222 |
|
file will be added to the instruments database. If the optional |
| 5223 |
|
<instr_index> (the index of the instrument within the given file) |
| 5224 |
|
is supplied too, then only the specified instrument will be added. |
| 5225 |
|
In case a directory is supplied, the instruments in that directory |
| 5226 |
|
will be added. The OPTIONAL <mode> argument is only applied |
| 5227 |
|
when a directory is provided as <file_path> and specifies how the |
| 5228 |
|
scanning will be done and has exactly the following possibilities:</t> |
| 5229 |
|
<t> |
| 5230 |
|
<list> |
| 5231 |
|
<t>"RECURSIVE" - |
| 5232 |
|
<list> |
| 5233 |
|
<t>All instruments will be processed, including those |
| 5234 |
|
in the subdirectories, and the respective subdirectory |
| 5235 |
|
tree structure will be recreated in the instruments |
| 5236 |
|
database</t> |
| 5237 |
|
</list> |
| 5238 |
|
</t> |
| 5239 |
|
<t>"NON_RECURSIVE" - |
| 5240 |
|
<list> |
| 5241 |
|
<t>Only the instruments in the specified directory |
| 5242 |
|
will be added, the instruments in the subdirectories |
| 5243 |
|
will not be processed.</t> |
| 5244 |
|
</list> |
| 5245 |
|
</t> |
| 5246 |
|
<t>"FLAT" - |
| 5247 |
|
<list> |
| 5248 |
|
<t>All instruments will be processed, including those |
| 5249 |
|
in the subdirectories, but the respective subdirectory |
| 5250 |
|
structure will not be recreated in the instruments |
| 5251 |
|
database. All instruments will be added directly in |
| 5252 |
|
the specified database directory.</t> |
| 5253 |
|
</list> |
| 5254 |
|
</t> |
| 5255 |
|
</list> |
| 5256 |
|
</t> |
| 5257 |
|
|
| 5258 |
|
<t>The difference between regular and NON_MODAL versions of the command |
| 5259 |
|
is that the regular command returns when the scanning is finished |
| 5260 |
|
while NON_MODAL version returns immediately and a background process is launched. |
| 5261 |
|
The <xref target="GET DB_INSTRUMENTS_JOB INFO">GET DB_INSTRUMENTS_JOB INFO</xref> |
| 5262 |
|
command can be used to monitor the scanning progress.</t> |
| 5263 |
|
|
| 5264 |
|
<t>Possible Answers:</t> |
| 5265 |
|
<t> |
| 5266 |
|
<list> |
| 5267 |
|
<t>"OK" - |
| 5268 |
|
<list> |
| 5269 |
|
<t>on success when NON_MODAL is not supplied</t> |
| 5270 |
|
</list> |
| 5271 |
|
</t> |
| 5272 |
|
<t>"OK[<job-id>]" - |
| 5273 |
|
<list> |
| 5274 |
|
<t>on success when NON_MODAL is supplied, where <job-id> |
| 5275 |
|
is a numerical ID used to obtain status information about the job progress. |
| 5276 |
|
See <xref target="GET DB_INSTRUMENTS_JOB INFO">GET DB_INSTRUMENTS_JOB INFO</xref> |
| 5277 |
|
</t> |
| 5278 |
|
</list> |
| 5279 |
|
</t> |
| 5280 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5281 |
|
<list> |
| 5282 |
|
<t>if an invalid path is specified.</t> |
| 5283 |
|
</list> |
| 5284 |
|
</t> |
| 5285 |
|
</list> |
| 5286 |
|
</t> |
| 5287 |
|
|
| 5288 |
|
<t>Examples:</t> |
| 5289 |
|
<t> |
| 5290 |
|
<list> |
| 5291 |
|
<t>C: "ADD DB_INSTRUMENTS '/Piano Collection' '/home/me/gigs/PMI Bosendorfer 290.gig' 0"</t> |
| 5292 |
|
<t>S: "OK"</t> |
| 5293 |
|
</list> |
| 5294 |
|
</t> |
| 5295 |
|
</section> |
| 5296 |
|
|
| 5297 |
|
<section title="Removing an instrument" anchor="REMOVE DB_INSTRUMENT"> |
| 5298 |
|
<t>The front-end can remove a particular instrument |
| 5299 |
|
from the instruments database by sending the following command:</t> |
| 5300 |
|
<t> |
| 5301 |
|
<list> |
| 5302 |
|
<t>REMOVE DB_INSTRUMENT <instr_path></t> |
| 5303 |
|
</list> |
| 5304 |
|
</t> |
| 5305 |
|
<t>Where <instr_path> is the absolute path name |
| 5306 |
|
(in the instruments database) of the instrument to remove.</t> |
| 5307 |
|
|
| 5308 |
|
<t>Possible Answers:</t> |
| 5309 |
|
<t> |
| 5310 |
|
<list> |
| 5311 |
|
<t>"OK" - |
| 5312 |
|
<list> |
| 5313 |
|
<t>if the instrument is removed successfully</t> |
| 5314 |
|
</list> |
| 5315 |
|
</t> |
| 5316 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5317 |
|
<list> |
| 5318 |
|
<t>if the given path does not exist or |
| 5319 |
|
is a directory.</t> |
| 5320 |
|
</list> |
| 5321 |
|
</t> |
| 5322 |
|
</list> |
| 5323 |
|
</t> |
| 5324 |
|
|
| 5325 |
|
<t>Examples:</t> |
| 5326 |
|
<t> |
| 5327 |
|
<list> |
| 5328 |
|
<t>C: "REMOVE DB_INSTRUMENT '/Piano Collection/Bosendorfer 290'"</t> |
| 5329 |
|
<t>S: "OK"</t> |
| 5330 |
|
</list> |
| 5331 |
|
</t> |
| 5332 |
|
</section> |
| 5333 |
|
|
| 5334 |
|
<section title="Getting amount of instruments" anchor="GET DB_INSTRUMENTS"> |
| 5335 |
|
<t>The front-end can retrieve the current amount of |
| 5336 |
|
instruments in a specific directory by sending the following command:</t> |
| 5337 |
|
<t> |
| 5338 |
|
<list> |
| 5339 |
|
<t>GET DB_INSTRUMENTS [RECURSIVE] <dir></t> |
| 5340 |
|
</list> |
| 5341 |
|
</t> |
| 5342 |
|
<t>Where <dir> should be replaced by the absolute path name |
| 5343 |
|
of the directory. If RECURSIVE is specified, the number of all |
| 5344 |
|
instruments, including those located in subdirectories of the |
| 5345 |
|
specified directory, will be returned.</t> |
| 5346 |
|
|
| 5347 |
|
<t>Possible Answers:</t> |
| 5348 |
|
<t> |
| 5349 |
|
<list> |
| 5350 |
|
<t>The current number of instruments |
| 5351 |
|
in the specified directory.</t> |
| 5352 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5353 |
|
<list> |
| 5354 |
|
<t>if the given directory does not exist.</t> |
| 5355 |
|
</list> |
| 5356 |
|
</t> |
| 5357 |
|
</list> |
| 5358 |
|
</t> |
| 5359 |
|
|
| 5360 |
|
<t>Example:</t> |
| 5361 |
|
<t> |
| 5362 |
|
<list> |
| 5363 |
|
<t>C: "GET DB_INSTRUMENTS '/Piano Collection'"</t> |
| 5364 |
|
<t>S: "2"</t> |
| 5365 |
|
</list> |
| 5366 |
|
</t> |
| 5367 |
|
</section> |
| 5368 |
|
|
| 5369 |
|
<section title="Listing all instruments in specific directory" anchor="LIST DB_INSTRUMENTS"> |
| 5370 |
|
<t>The front-end can retrieve the current list of instruments |
| 5371 |
|
in specific directory by sending the following command:</t> |
| 5372 |
|
<t> |
| 5373 |
|
<list> |
| 5374 |
|
<t>LIST DB_INSTRUMENTS [RECURSIVE] <dir></t> |
| 5375 |
|
</list> |
| 5376 |
|
</t> |
| 5377 |
|
<t>Where <dir> should be replaced by the absolute path |
| 5378 |
|
name of the directory. If RECURSIVE is specified, the absolute path |
| 5379 |
|
names of all instruments, including those located in subdirectories |
| 5380 |
|
of the specified directory, will be returned.</t> |
| 5381 |
|
|
| 5382 |
|
<t>Possible Answers:</t> |
| 5383 |
|
<t> |
| 5384 |
|
<list> |
| 5385 |
|
<t>A comma separated list of all instruments |
| 5386 |
|
(encapsulated into apostrophes) in the specified directory.</t> |
| 5387 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5388 |
|
<list> |
| 5389 |
|
<t>if the given directory does not exist.</t> |
| 5390 |
|
</list> |
| 5391 |
|
</t> |
| 5392 |
|
</list> |
| 5393 |
|
</t> |
| 5394 |
|
<t>Example:</t> |
| 5395 |
|
<t> |
| 5396 |
|
<list> |
| 5397 |
|
<t>C: "LIST DB_INSTRUMENTS '/Piano Collection'"</t> |
| 5398 |
|
<t>S: "'Bosendorfer 290','Steinway D'"</t> |
| 5399 |
|
</list> |
| 5400 |
|
</t> |
| 5401 |
|
<t> |
| 5402 |
|
<list> |
| 5403 |
|
<t>C: "LIST DB_INSTRUMENTS RECURSIVE '/Piano Collection'"</t> |
| 5404 |
|
<t>S: "'/Piano Collection/Bosendorfer 290','/Piano Collection/Steinway D','/Piano Collection/Lite/Free Piano'"</t> |
| 5405 |
|
</list> |
| 5406 |
|
</t> |
| 5407 |
|
</section> |
| 5408 |
|
|
| 5409 |
|
<section title="Getting instrument information" anchor="GET DB_INSTRUMENT INFO"> |
| 5410 |
|
<t>The front-end can ask for the current settings of an |
| 5411 |
|
instrument by sending the following command:</t> |
| 5412 |
|
<t> |
| 5413 |
|
<list> |
| 5414 |
|
<t>GET DB_INSTRUMENT INFO <instr_path></t> |
| 5415 |
|
</list> |
| 5416 |
|
</t> |
| 5417 |
|
<t>Where <instr_path> should be replaced by the absolute path |
| 5418 |
|
name of the instrument the front-end is interested in.</t> |
| 5419 |
|
|
| 5420 |
|
<t>Possible Answers:</t> |
| 5421 |
|
<t> |
| 5422 |
|
<list> |
| 5423 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
| 5424 |
|
Each answer line begins with the settings category name |
| 5425 |
|
followed by a colon and then a space character <SP> and finally |
| 5426 |
|
the info character string to that setting category. At the |
| 5427 |
|
moment the following categories are defined:</t> |
| 5428 |
|
|
| 5429 |
|
<t> |
| 5430 |
|
<list> |
| 5431 |
|
<t>INSTRUMENT_FILE - |
| 5432 |
|
<list> |
| 5433 |
|
<t>File name of the instrument.</t> |
| 5434 |
|
</list> |
| 5435 |
|
</t> |
| 5436 |
|
<t>INSTRUMENT_NR - |
| 5437 |
|
<list> |
| 5438 |
|
<t>Index of the instrument within the file.</t> |
| 5439 |
|
</list> |
| 5440 |
|
</t> |
| 5441 |
|
<t>FORMAT_FAMILY - |
| 5442 |
|
<list> |
| 5443 |
|
<t>The format family of the instrument.</t> |
| 5444 |
|
</list> |
| 5445 |
|
</t> |
| 5446 |
|
<t>FORMAT_VERSION - |
| 5447 |
|
<list> |
| 5448 |
|
<t>The format version of the instrument.</t> |
| 5449 |
|
</list> |
| 5450 |
|
</t> |
| 5451 |
|
<t>SIZE - |
| 5452 |
|
<list> |
| 5453 |
|
<t>The size of the instrument in bytes.</t> |
| 5454 |
|
</list> |
| 5455 |
|
</t> |
| 5456 |
|
<t>CREATED - |
| 5457 |
|
<list> |
| 5458 |
|
<t>The date and time when the instrument is added |
| 5459 |
|
in the instruments database, represented in |
| 5460 |
|
"YYYY-MM-DD HH:MM:SS" format</t> |
| 5461 |
|
</list> |
| 5462 |
|
</t> |
| 5463 |
|
<t>MODIFIED - |
| 5464 |
|
<list> |
| 5465 |
|
<t>The date and time of the last modification of the |
| 5466 |
|
instrument's database settings, represented in |
| 5467 |
|
"YYYY-MM-DD HH:MM:SS" format</t> |
| 5468 |
|
</list> |
| 5469 |
|
</t> |
| 5470 |
|
<t>DESCRIPTION - |
| 5471 |
|
<list> |
| 5472 |
|
<t>A brief description of the instrument</t> |
| 5473 |
|
</list> |
| 5474 |
|
</t> |
| 5475 |
|
<t>IS_DRUM - |
| 5476 |
|
<list> |
| 5477 |
|
<t>either true or false, determines whether the |
| 5478 |
|
instrument is a drumkit or a chromatic instrument</t> |
| 5479 |
|
</list> |
| 5480 |
|
</t> |
| 5481 |
|
<t>PRODUCT - |
| 5482 |
|
<list> |
| 5483 |
|
<t>The product title of the instrument</t> |
| 5484 |
|
</list> |
| 5485 |
|
</t> |
| 5486 |
|
<t>ARTISTS - |
| 5487 |
|
<list> |
| 5488 |
|
<t>Lists the artist names</t> |
| 5489 |
|
</list> |
| 5490 |
|
</t> |
| 5491 |
|
<t>KEYWORDS - |
| 5492 |
|
<list> |
| 5493 |
|
<t>Provides a list of keywords that refer to the instrument. |
| 5494 |
|
Keywords are separated with semicolon and blank.</t> |
| 5495 |
|
</list> |
| 5496 |
|
</t> |
| 5497 |
|
</list> |
| 5498 |
|
</t> |
| 5499 |
|
</list> |
| 5500 |
|
</t> |
| 5501 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 5502 |
|
|
| 5503 |
|
<t>Example:</t> |
| 5504 |
|
<t> |
| 5505 |
|
<list> |
| 5506 |
|
<t>C: "GET DB_INSTRUMENT INFO '/Piano Collection/Bosendorfer 290'"</t> |
| 5507 |
|
<t>S: "INSTRUMENT_FILE: /home/me/gigs/Bosendorfer 290.gig"</t> |
| 5508 |
|
<t> "INSTRUMENT_NR: 0"</t> |
| 5509 |
|
<t> "FORMAT_FAMILY: GIG"</t> |
| 5510 |
|
<t> "FORMAT_VERSION: 2"</t> |
| 5511 |
|
<t> "SIZE: 2050871870"</t> |
| 5512 |
|
<t> "CREATED: 2007-02-05 10:23:12"</t> |
| 5513 |
|
<t> "MODIFIED: 2007-04-07 12:50:21"</t> |
| 5514 |
|
<t> "DESCRIPTION: "</t> |
| 5515 |
|
<t> "IS_DRUM: false"</t> |
| 5516 |
|
<t> "PRODUCT: GRANDIOSO Bosendorfer 290"</t> |
| 5517 |
|
<t> "ARTISTS: Post Musical Instruments"</t> |
| 5518 |
|
<t> "KEYWORDS: Bosendorfer"</t> |
| 5519 |
|
<t> "."</t> |
| 5520 |
|
</list> |
| 5521 |
|
</t> |
| 5522 |
|
</section> |
| 5523 |
|
|
| 5524 |
|
<section title="Renaming an instrument" anchor="SET DB_INSTRUMENT NAME"> |
| 5525 |
|
<t>The front-end can alter the name of a specific |
| 5526 |
|
instrument by sending the following command:</t> |
| 5527 |
|
<t> |
| 5528 |
|
<list> |
| 5529 |
|
<t>SET DB_INSTRUMENT NAME <instr> <name></t> |
| 5530 |
|
</list> |
| 5531 |
|
</t> |
| 5532 |
|
<t>Where <instr> is the absolute path name of the instrument and |
| 5533 |
|
<name> is the new name for that instrument.</t> |
| 5534 |
|
|
| 5535 |
|
<t>Possible Answers:</t> |
| 5536 |
|
<t> |
| 5537 |
|
<list> |
| 5538 |
|
<t>"OK" - |
| 5539 |
|
<list> |
| 5540 |
|
<t>on success</t> |
| 5541 |
|
</list> |
| 5542 |
|
</t> |
| 5543 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5544 |
|
<list> |
| 5545 |
|
<t>in case the given instrument does not exists, |
| 5546 |
|
or if an instrument with name equal to the new |
| 5547 |
|
name already exists.</t> |
| 5548 |
|
</list> |
| 5549 |
|
</t> |
| 5550 |
|
</list> |
| 5551 |
|
</t> |
| 5552 |
|
|
| 5553 |
|
<t>Example:</t> |
| 5554 |
|
<t> |
| 5555 |
|
<list> |
| 5556 |
|
<t>C: "SET DB_INSTRUMENT NAME '/Piano Collection/Bosendorfer' 'Bosendorfer 290'"</t> |
| 5557 |
|
<t>S: "OK"</t> |
| 5558 |
|
</list> |
| 5559 |
|
</t> |
| 5560 |
|
</section> |
| 5561 |
|
|
| 5562 |
|
<section title="Moving an instrument" anchor="MOVE DB_INSTRUMENT"> |
| 5563 |
|
<t>The front-end can move a specific instrument to another directory by |
| 5564 |
|
sending the following command:</t> |
| 5565 |
|
<t> |
| 5566 |
|
<list> |
| 5567 |
|
<t>MOVE DB_INSTRUMENT <instr> <dst></t> |
| 5568 |
|
</list> |
| 5569 |
|
</t> |
| 5570 |
|
<t>Where <instr> is the absolute path name of the instrument |
| 5571 |
|
to move and <dst> is the directory where the instrument will |
| 5572 |
|
be moved to.</t> |
| 5573 |
|
|
| 5574 |
|
<t>Possible Answers:</t> |
| 5575 |
|
<t> |
| 5576 |
|
<list> |
| 5577 |
|
<t>"OK" - |
| 5578 |
|
<list> |
| 5579 |
|
<t>on success</t> |
| 5580 |
|
</list> |
| 5581 |
|
</t> |
| 5582 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5583 |
|
<list> |
| 5584 |
|
<t>in case the given instrument does not exists, |
| 5585 |
|
or if an instrument with name equal to the name of the |
| 5586 |
|
specified instrument already exists in the destination |
| 5587 |
|
directory.</t> |
| 5588 |
|
</list> |
| 5589 |
|
</t> |
| 5590 |
|
</list> |
| 5591 |
|
</t> |
| 5592 |
|
|
| 5593 |
|
<t>Example:</t> |
| 5594 |
|
<t> |
| 5595 |
|
<list> |
| 5596 |
|
<t>C: "MOVE DB_INSTRUMENT '/Piano Collection/Bosendorfer 290' '/Piano Collection/Acoustic'"</t> |
| 5597 |
|
<t>S: "OK"</t> |
| 5598 |
|
</list> |
| 5599 |
|
</t> |
| 5600 |
|
</section> |
| 5601 |
|
|
| 5602 |
|
<section title="Copying instruments" anchor="COPY DB_INSTRUMENT"> |
| 5603 |
|
<t>The front-end can copy a specific instrument to another directory by |
| 5604 |
|
sending the following command:</t> |
| 5605 |
|
<t> |
| 5606 |
|
<list> |
| 5607 |
|
<t>COPY DB_INSTRUMENT <instr> <dst></t> |
| 5608 |
|
</list> |
| 5609 |
|
</t> |
| 5610 |
|
<t>Where <instr> is the absolute path name of the instrument |
| 5611 |
|
to copy and <dst> is the directory where the instrument will |
| 5612 |
|
be copied to.</t> |
| 5613 |
|
|
| 5614 |
|
<t>Possible Answers:</t> |
| 5615 |
|
<t> |
| 5616 |
|
<list> |
| 5617 |
|
<t>"OK" - |
| 5618 |
|
<list> |
| 5619 |
|
<t>on success</t> |
| 5620 |
|
</list> |
| 5621 |
|
</t> |
| 5622 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5623 |
|
<list> |
| 5624 |
|
<t>in case the given instrument does not exists, |
| 5625 |
|
or if an instrument with name equal to the name of the |
| 5626 |
|
specified instrument already exists in the destination |
| 5627 |
|
directory.</t> |
| 5628 |
|
</list> |
| 5629 |
|
</t> |
| 5630 |
|
</list> |
| 5631 |
|
</t> |
| 5632 |
|
|
| 5633 |
|
<t>Example:</t> |
| 5634 |
|
<t> |
| 5635 |
|
<list> |
| 5636 |
|
<t>C: "COPY DB_INSTRUMENT '/Piano Collection/Bosendorfer 290' '/Acoustic/Pianos/'"</t> |
| 5637 |
|
<t>S: "OK"</t> |
| 5638 |
|
</list> |
| 5639 |
|
</t> |
| 5640 |
|
</section> |
| 5641 |
|
|
| 5642 |
|
<section title="Changing the description of instrument" anchor="SET DB_INSTRUMENT DESCRIPTION"> |
| 5643 |
|
<t>The front-end can alter the description of a specific |
| 5644 |
|
instrument by sending the following command:</t> |
| 5645 |
|
<t> |
| 5646 |
|
<list> |
| 5647 |
|
<t>SET DB_INSTRUMENT DESCRIPTION <instr> <desc></t> |
| 5648 |
|
</list> |
| 5649 |
|
</t> |
| 5650 |
|
<t>Where <instr> is the absolute path name of the instrument and |
| 5651 |
|
<desc> is the new description for the instrument.</t> |
| 5652 |
|
|
| 5653 |
|
<t>Possible Answers:</t> |
| 5654 |
|
<t> |
| 5655 |
|
<list> |
| 5656 |
|
<t>"OK" - |
| 5657 |
|
<list> |
| 5658 |
|
<t>on success</t> |
| 5659 |
|
</list> |
| 5660 |
|
</t> |
| 5661 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5662 |
|
<list> |
| 5663 |
|
<t>in case the given instrument does not exists.</t> |
| 5664 |
|
</list> |
| 5665 |
|
</t> |
| 5666 |
|
</list> |
| 5667 |
|
</t> |
| 5668 |
|
|
| 5669 |
|
<t>Example:</t> |
| 5670 |
|
<t> |
| 5671 |
|
<list> |
| 5672 |
|
<t>C: "SET DB_INSTRUMENT DESCRIPTION '/Piano Collection/Acoustic/Bosendorfer 290' 'No comment :)'"</t> |
| 5673 |
|
<t>S: "OK"</t> |
| 5674 |
|
</list> |
| 5675 |
|
</t> |
| 5676 |
|
</section> |
| 5677 |
|
|
| 5678 |
|
<section title="Finding instruments" anchor="FIND DB_INSTRUMENTS"> |
| 5679 |
|
<t>The front-end can search for instruments |
| 5680 |
|
in specific directory by sending the following command:</t> |
| 5681 |
|
<t> |
| 5682 |
|
<list> |
| 5683 |
|
<t>FIND DB_INSTRUMENTS [NON_RECURSIVE] <dir> <criteria-list></t> |
| 5684 |
|
</list> |
| 5685 |
|
</t> |
| 5686 |
|
<t>Where <dir> should be replaced by the absolute path |
| 5687 |
|
name of the directory to search in. If NON_RECURSIVE is specified, the |
| 5688 |
|
directories located in subdirectories of the specified directory will not |
| 5689 |
|
be searched. <criteria-list> is a list of search criterias |
| 5690 |
|
in form of "key1=val1 key2=val2 ...". The following criterias are |
| 5691 |
|
allowed:</t> |
| 5692 |
|
<t> |
| 5693 |
|
<t>NAME='<search-string>' |
| 5694 |
|
<list> |
| 5695 |
|
<t>Restricts the search to instruments, which names |
| 5696 |
|
satisfy the supplied search string.</t> |
| 5697 |
|
</list> |
| 5698 |
|
</t> |
| 5699 |
|
|
| 5700 |
|
<t>SIZE=[<min>]..[<max>] |
| 5701 |
|
<list> |
| 5702 |
|
<t>Restricts the search to instruments, which |
| 5703 |
|
size is in the specified range. If <min> is omitted, |
| 5704 |
|
the search results are restricted to instruments with size less then |
| 5705 |
|
or equal to <max>. If <max> is omitted, the |
| 5706 |
|
search is restricted to instruments with size greater then |
| 5707 |
|
or equal to <min>.</t> |
| 5708 |
|
</list> |
| 5709 |
|
</t> |
| 5710 |
|
|
| 5711 |
|
<t>CREATED='[<date-after>]..[<date-before>]' |
| 5712 |
|
<list> |
| 5713 |
|
<t>Restricts the search to instruments, which creation |
| 5714 |
|
date satisfies the specified period, where <date-after> |
| 5715 |
|
and <date-before> are in "YYYY-MM-DD HH:MM:SS" format. |
| 5716 |
|
If <date-after> is omitted the search is restricted to |
| 5717 |
|
instruments created before <date-before>. If |
| 5718 |
|
<date-before> is omitted, the search is restricted |
| 5719 |
|
to instruments created after <date-after>.</t> |
| 5720 |
|
</list> |
| 5721 |
|
</t> |
| 5722 |
|
|
| 5723 |
|
<t>MODIFIED='[<date-after>]..[<date-before>]' |
| 5724 |
|
<list> |
| 5725 |
|
<t>Restricts the search to instruments, which |
| 5726 |
|
date of last modification satisfies the specified period, where |
| 5727 |
|
<date-after> and <date-before> are in "YYYY-MM-DD HH:MM:SS" |
| 5728 |
|
format. If <date-after> is omitted the search is restricted to |
| 5729 |
|
instruments, which are last modified before <date-before>. If |
| 5730 |
|
<date-before> is omitted, the search is restricted to instruments, |
| 5731 |
|
which are last modified after <date-after>.</t> |
| 5732 |
|
</list> |
| 5733 |
|
</t> |
| 5734 |
|
|
| 5735 |
|
<t>DESCRIPTION='<search-string>' |
| 5736 |
|
<list> |
| 5737 |
|
<t>Restricts the search to instruments with description |
| 5738 |
|
that satisfies the supplied search string.</t> |
| 5739 |
|
</list> |
| 5740 |
|
</t> |
| 5741 |
|
|
| 5742 |
|
<t>PRODUCT='<search-string>' |
| 5743 |
|
<list> |
| 5744 |
|
<t>Restricts the search to instruments with product info |
| 5745 |
|
that satisfies the supplied search string.</t> |
| 5746 |
|
</list> |
| 5747 |
|
</t> |
| 5748 |
|
|
| 5749 |
|
<t>ARTISTS='<search-string>' |
| 5750 |
|
<list> |
| 5751 |
|
<t>Restricts the search to instruments with artists info |
| 5752 |
|
that satisfies the supplied search string.</t> |
| 5753 |
|
</list> |
| 5754 |
|
</t> |
| 5755 |
|
|
| 5756 |
|
<t>KEYWORDS='<search-string>' |
| 5757 |
|
<list> |
| 5758 |
|
<t>Restricts the search to instruments with keyword list |
| 5759 |
|
that satisfies the supplied search string.</t> |
| 5760 |
|
</list> |
| 5761 |
|
</t> |
| 5762 |
|
|
| 5763 |
|
<t>IS_DRUM=true | false |
| 5764 |
|
<list> |
| 5765 |
|
<t>Either true or false. Restricts the search to |
| 5766 |
|
drum kits or chromatic instruments.</t> |
| 5767 |
|
</list> |
| 5768 |
|
</t> |
| 5769 |
|
|
| 5770 |
|
<t>FORMAT_FAMILIES='<format-list>' |
| 5771 |
|
<list> |
| 5772 |
|
<t>Restricts the search to instruments of the supplied format families, |
| 5773 |
|
where <format-list> is a comma separated list of format families.</t> |
| 5774 |
|
</list> |
| 5775 |
|
</t> |
| 5776 |
|
</t> |
| 5777 |
|
|
| 5778 |
|
<t>Where <search-string> is either a regular expression, or a |
| 5779 |
|
word list separated with spaces for OR search and with '+' for AND search.</t> |
| 5780 |
|
|
| 5781 |
|
<t>Possible Answers:</t> |
| 5782 |
|
<t> |
| 5783 |
|
<list> |
| 5784 |
|
<t>A comma separated list with the absolute path names (encapsulated into |
| 5785 |
|
apostrophes) of all instruments in the specified directory that satisfy |
| 5786 |
|
the supplied search criterias.</t> |
| 5787 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5788 |
|
<list> |
| 5789 |
|
<t>if the given directory does not exist.</t> |
| 5790 |
|
</list> |
| 5791 |
|
</t> |
| 5792 |
|
</list> |
| 5793 |
|
</t> |
| 5794 |
|
<t>Example:</t> |
| 5795 |
|
<t> |
| 5796 |
|
<list> |
| 5797 |
|
<t>C: "FIND DB_INSTRUMENTS '/Piano Collection' NAME='bosendorfer+290'"</t> |
| 5798 |
|
<t>S: "'/Piano Collection/Bosendorfer 290'"</t> |
| 5799 |
|
</list> |
| 5800 |
|
</t> |
| 5801 |
|
<t> |
| 5802 |
|
<list> |
| 5803 |
|
<t>C: "FIND DB_INSTRUMENTS '/Piano Collection' CREATED='2007-04-01 09:30:13..'"</t> |
| 5804 |
|
<t>S: "'/Piano Collection/Bosendorfer 290','/Piano Collection/Steinway D'"</t> |
| 5805 |
|
</list> |
| 5806 |
|
</t> |
| 5807 |
|
</section> |
| 5808 |
|
|
| 5809 |
|
<section title="Getting job status information" anchor="GET DB_INSTRUMENTS_JOB INFO"> |
| 5810 |
|
<t>The front-end can ask for the current status of a |
| 5811 |
|
particular database instruments job by sending the following command:</t> |
| 5812 |
|
<t> |
| 5813 |
|
<list> |
| 5814 |
|
<t>GET DB_INSTRUMENTS_JOB INFO <job-id></t> |
| 5815 |
|
</list> |
| 5816 |
|
</t> |
| 5817 |
|
<t>Where <job-id> should be replaced by the numerical ID |
| 5818 |
|
of the job the front-end is interested in.</t> |
| 5819 |
|
|
| 5820 |
|
<t>Possible Answers:</t> |
| 5821 |
|
<t> |
| 5822 |
|
<list> |
| 5823 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
| 5824 |
|
Each answer line begins with the settings category name |
| 5825 |
|
followed by a colon and then a space character <SP> and finally |
| 5826 |
|
the info character string to that setting category. At the |
| 5827 |
|
moment the following categories are defined:</t> |
| 5828 |
|
|
| 5829 |
|
<t> |
| 5830 |
|
<list> |
| 5831 |
|
<t>FILES_TOTAL - |
| 5832 |
|
<list> |
| 5833 |
|
<t>The total number of files scheduled for scanning</t> |
| 5834 |
|
</list> |
| 5835 |
|
</t> |
| 5836 |
|
<t>FILES_SCANNED - |
| 5837 |
|
<list> |
| 5838 |
|
<t>The current number of scanned files</t> |
| 5839 |
|
</list> |
| 5840 |
|
</t> |
| 5841 |
|
<t>SCANNING - |
| 5842 |
|
<list> |
| 5843 |
|
<t>The absolute path name of the file which is currently |
| 5844 |
|
being scanned</t> |
| 5845 |
|
</list> |
| 5846 |
|
</t> |
| 5847 |
|
<t>STATUS - |
| 5848 |
|
<list> |
| 5849 |
|
<t>An integer value between 0 and 100 indicating the |
| 5850 |
|
scanning progress percentage of the file which is |
| 5851 |
|
currently being scanned</t> |
| 5852 |
|
</list> |
| 5853 |
|
</t> |
| 5854 |
|
</list> |
| 5855 |
|
</t> |
| 5856 |
|
</list> |
| 5857 |
|
</t> |
| 5858 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 5859 |
|
|
| 5860 |
|
<t>Example:</t> |
| 5861 |
|
<t> |
| 5862 |
|
<list> |
| 5863 |
|
<t>C: "GET DB_INSTRUMENTS_JOB INFO 2"</t> |
| 5864 |
|
<t>S: "FILES_TOTAL: 12"</t> |
| 5865 |
|
<t> "FILES_SCANNED: 7"</t> |
| 5866 |
|
<t> "SCANNING: /home/me/gigs/Bosendorfer 290.gig"</t> |
| 5867 |
|
<t> "STATUS: 42"</t> |
| 5868 |
|
<t> "."</t> |
| 5869 |
|
</list> |
| 5870 |
|
</t> |
| 5871 |
|
</section> |
| 5872 |
|
|
| 5873 |
</section> |
</section> |
| 5874 |
|
|
| 5875 |
</section> |
</section> |
| 5876 |
|
|
| 5877 |
<section title="Command Syntax"> |
|
| 5878 |
<t>TODO: will soon automatically included from src/network/lscp.y, |
<section title="Command Syntax" anchor="command_syntax"> |
| 5879 |
meanwhile have a look at that file to get the exact definition of |
<t>The grammar of the control protocol as descibed in <xref target="control_commands"/> |
| 5880 |
the command syntax.</t> |
is defined below using Backus-Naur Form (BNF as described in <xref target="RFC2234"/>) |
| 5881 |
|
where applicable. |
| 5882 |
|
</t> |
| 5883 |
|
<!-- |
| 5884 |
|
This section is automatically generated by scripts/update_grammar.pl |
| 5885 |
|
from src/network/lscp.y (yacc input file). Do not modify this section |
| 5886 |
|
manually ! |
| 5887 |
|
--> |
| 5888 |
|
<!-- GRAMMAR_BNF_BEGIN - do NOT delete or modify this line !!! --> |
| 5889 |
|
|
| 5890 |
|
<t>input = |
| 5891 |
|
<list> |
| 5892 |
|
<t>line LF |
| 5893 |
|
</t> |
| 5894 |
|
<t>/ line CR LF |
| 5895 |
|
</t> |
| 5896 |
|
</list> |
| 5897 |
|
</t> |
| 5898 |
|
<t>line = |
| 5899 |
|
<list> |
| 5900 |
|
<t>/* epsilon (empty line ignored) */ |
| 5901 |
|
</t> |
| 5902 |
|
<t>/ comment |
| 5903 |
|
</t> |
| 5904 |
|
<t>/ command |
| 5905 |
|
</t> |
| 5906 |
|
<t>/ error |
| 5907 |
|
</t> |
| 5908 |
|
</list> |
| 5909 |
|
</t> |
| 5910 |
|
<t>comment = |
| 5911 |
|
<list> |
| 5912 |
|
<t>'#' |
| 5913 |
|
</t> |
| 5914 |
|
<t>/ comment '#' |
| 5915 |
|
</t> |
| 5916 |
|
<t>/ comment SP |
| 5917 |
|
</t> |
| 5918 |
|
<t>/ comment number |
| 5919 |
|
</t> |
| 5920 |
|
<t>/ comment string |
| 5921 |
|
</t> |
| 5922 |
|
</list> |
| 5923 |
|
</t> |
| 5924 |
|
<t>command = |
| 5925 |
|
<list> |
| 5926 |
|
<t>ADD SP add_instruction |
| 5927 |
|
</t> |
| 5928 |
|
<t>/ MAP SP map_instruction |
| 5929 |
|
</t> |
| 5930 |
|
<t>/ UNMAP SP unmap_instruction |
| 5931 |
|
</t> |
| 5932 |
|
<t>/ GET SP get_instruction |
| 5933 |
|
</t> |
| 5934 |
|
<t>/ CREATE SP create_instruction |
| 5935 |
|
</t> |
| 5936 |
|
<t>/ DESTROY SP destroy_instruction |
| 5937 |
|
</t> |
| 5938 |
|
<t>/ LIST SP list_instruction |
| 5939 |
|
</t> |
| 5940 |
|
<t>/ LOAD SP load_instruction |
| 5941 |
|
</t> |
| 5942 |
|
<t>/ REMOVE SP remove_instruction |
| 5943 |
|
</t> |
| 5944 |
|
<t>/ SET SP set_instruction |
| 5945 |
|
</t> |
| 5946 |
|
<t>/ SUBSCRIBE SP subscribe_event |
| 5947 |
|
</t> |
| 5948 |
|
<t>/ UNSUBSCRIBE SP unsubscribe_event |
| 5949 |
|
</t> |
| 5950 |
|
<t>/ RESET SP reset_instruction |
| 5951 |
|
</t> |
| 5952 |
|
<t>/ CLEAR SP clear_instruction |
| 5953 |
|
</t> |
| 5954 |
|
<t>/ FIND SP find_instruction |
| 5955 |
|
</t> |
| 5956 |
|
<t>/ MOVE SP move_instruction |
| 5957 |
|
</t> |
| 5958 |
|
<t>/ COPY SP copy_instruction |
| 5959 |
|
</t> |
| 5960 |
|
<t>/ EDIT SP edit_instruction |
| 5961 |
|
</t> |
| 5962 |
|
<t>/ RESET |
| 5963 |
|
</t> |
| 5964 |
|
<t>/ QUIT |
| 5965 |
|
</t> |
| 5966 |
|
</list> |
| 5967 |
|
</t> |
| 5968 |
|
<t>add_instruction = |
| 5969 |
|
<list> |
| 5970 |
|
<t>CHANNEL |
| 5971 |
|
</t> |
| 5972 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP pathname |
| 5973 |
|
</t> |
| 5974 |
|
<t>/ DB_INSTRUMENTS SP NON_MODAL SP scan_mode SP pathname SP pathname |
| 5975 |
|
</t> |
| 5976 |
|
<t>/ DB_INSTRUMENTS SP scan_mode SP pathname SP pathname |
| 5977 |
|
</t> |
| 5978 |
|
<t>/ DB_INSTRUMENTS SP NON_MODAL SP pathname SP pathname |
| 5979 |
|
</t> |
| 5980 |
|
<t>/ DB_INSTRUMENTS SP NON_MODAL SP pathname SP pathname SP instrument_index |
| 5981 |
|
</t> |
| 5982 |
|
<t>/ DB_INSTRUMENTS SP pathname SP pathname |
| 5983 |
|
</t> |
| 5984 |
|
<t>/ DB_INSTRUMENTS SP pathname SP pathname SP instrument_index |
| 5985 |
|
</t> |
| 5986 |
|
<t>/ MIDI_INSTRUMENT_MAP |
| 5987 |
|
</t> |
| 5988 |
|
<t>/ MIDI_INSTRUMENT_MAP SP map_name |
| 5989 |
|
</t> |
| 5990 |
|
</list> |
| 5991 |
|
</t> |
| 5992 |
|
<t>subscribe_event = |
| 5993 |
|
<list> |
| 5994 |
|
<t>AUDIO_OUTPUT_DEVICE_COUNT |
| 5995 |
|
</t> |
| 5996 |
|
<t>/ AUDIO_OUTPUT_DEVICE_INFO |
| 5997 |
|
</t> |
| 5998 |
|
<t>/ MIDI_INPUT_DEVICE_COUNT |
| 5999 |
|
</t> |
| 6000 |
|
<t>/ MIDI_INPUT_DEVICE_INFO |
| 6001 |
|
</t> |
| 6002 |
|
<t>/ CHANNEL_COUNT |
| 6003 |
|
</t> |
| 6004 |
|
<t>/ VOICE_COUNT |
| 6005 |
|
</t> |
| 6006 |
|
<t>/ STREAM_COUNT |
| 6007 |
|
</t> |
| 6008 |
|
<t>/ BUFFER_FILL |
| 6009 |
|
</t> |
| 6010 |
|
<t>/ CHANNEL_INFO |
| 6011 |
|
</t> |
| 6012 |
|
<t>/ FX_SEND_COUNT |
| 6013 |
|
</t> |
| 6014 |
|
<t>/ FX_SEND_INFO |
| 6015 |
|
</t> |
| 6016 |
|
<t>/ MIDI_INSTRUMENT_MAP_COUNT |
| 6017 |
|
</t> |
| 6018 |
|
<t>/ MIDI_INSTRUMENT_MAP_INFO |
| 6019 |
|
</t> |
| 6020 |
|
<t>/ MIDI_INSTRUMENT_COUNT |
| 6021 |
|
</t> |
| 6022 |
|
<t>/ MIDI_INSTRUMENT_INFO |
| 6023 |
|
</t> |
| 6024 |
|
<t>/ DB_INSTRUMENT_DIRECTORY_COUNT |
| 6025 |
|
</t> |
| 6026 |
|
<t>/ DB_INSTRUMENT_DIRECTORY_INFO |
| 6027 |
|
</t> |
| 6028 |
|
<t>/ DB_INSTRUMENT_COUNT |
| 6029 |
|
</t> |
| 6030 |
|
<t>/ DB_INSTRUMENT_INFO |
| 6031 |
|
</t> |
| 6032 |
|
<t>/ DB_INSTRUMENTS_JOB_INFO |
| 6033 |
|
</t> |
| 6034 |
|
<t>/ MISCELLANEOUS |
| 6035 |
|
</t> |
| 6036 |
|
<t>/ TOTAL_VOICE_COUNT |
| 6037 |
|
</t> |
| 6038 |
|
<t>/ GLOBAL_INFO |
| 6039 |
|
</t> |
| 6040 |
|
</list> |
| 6041 |
|
</t> |
| 6042 |
|
<t>unsubscribe_event = |
| 6043 |
|
<list> |
| 6044 |
|
<t>AUDIO_OUTPUT_DEVICE_COUNT |
| 6045 |
|
</t> |
| 6046 |
|
<t>/ AUDIO_OUTPUT_DEVICE_INFO |
| 6047 |
|
</t> |
| 6048 |
|
<t>/ MIDI_INPUT_DEVICE_COUNT |
| 6049 |
|
</t> |
| 6050 |
|
<t>/ MIDI_INPUT_DEVICE_INFO |
| 6051 |
|
</t> |
| 6052 |
|
<t>/ CHANNEL_COUNT |
| 6053 |
|
</t> |
| 6054 |
|
<t>/ VOICE_COUNT |
| 6055 |
|
</t> |
| 6056 |
|
<t>/ STREAM_COUNT |
| 6057 |
|
</t> |
| 6058 |
|
<t>/ BUFFER_FILL |
| 6059 |
|
</t> |
| 6060 |
|
<t>/ CHANNEL_INFO |
| 6061 |
|
</t> |
| 6062 |
|
<t>/ FX_SEND_COUNT |
| 6063 |
|
</t> |
| 6064 |
|
<t>/ FX_SEND_INFO |
| 6065 |
|
</t> |
| 6066 |
|
<t>/ MIDI_INSTRUMENT_MAP_COUNT |
| 6067 |
|
</t> |
| 6068 |
|
<t>/ MIDI_INSTRUMENT_MAP_INFO |
| 6069 |
|
</t> |
| 6070 |
|
<t>/ MIDI_INSTRUMENT_COUNT |
| 6071 |
|
</t> |
| 6072 |
|
<t>/ MIDI_INSTRUMENT_INFO |
| 6073 |
|
</t> |
| 6074 |
|
<t>/ DB_INSTRUMENT_DIRECTORY_COUNT |
| 6075 |
|
</t> |
| 6076 |
|
<t>/ DB_INSTRUMENT_DIRECTORY_INFO |
| 6077 |
|
</t> |
| 6078 |
|
<t>/ DB_INSTRUMENT_COUNT |
| 6079 |
|
</t> |
| 6080 |
|
<t>/ DB_INSTRUMENT_INFO |
| 6081 |
|
</t> |
| 6082 |
|
<t>/ DB_INSTRUMENTS_JOB_INFO |
| 6083 |
|
</t> |
| 6084 |
|
<t>/ MISCELLANEOUS |
| 6085 |
|
</t> |
| 6086 |
|
<t>/ TOTAL_VOICE_COUNT |
| 6087 |
|
</t> |
| 6088 |
|
<t>/ GLOBAL_INFO |
| 6089 |
|
</t> |
| 6090 |
|
</list> |
| 6091 |
|
</t> |
| 6092 |
|
<t>map_instruction = |
| 6093 |
|
<list> |
| 6094 |
|
<t>MIDI_INSTRUMENT SP modal_arg midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value |
| 6095 |
|
</t> |
| 6096 |
|
<t>/ MIDI_INSTRUMENT SP modal_arg midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP instr_load_mode |
| 6097 |
|
</t> |
| 6098 |
|
<t>/ MIDI_INSTRUMENT SP modal_arg midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP entry_name |
| 6099 |
|
</t> |
| 6100 |
|
<t>/ MIDI_INSTRUMENT SP modal_arg midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP instr_load_mode SP entry_name |
| 6101 |
|
</t> |
| 6102 |
|
</list> |
| 6103 |
|
</t> |
| 6104 |
|
<t>unmap_instruction = |
| 6105 |
|
<list> |
| 6106 |
|
<t>MIDI_INSTRUMENT SP midi_map SP midi_bank SP midi_prog |
| 6107 |
|
</t> |
| 6108 |
|
</list> |
| 6109 |
|
</t> |
| 6110 |
|
<t>remove_instruction = |
| 6111 |
|
<list> |
| 6112 |
|
<t>CHANNEL SP sampler_channel |
| 6113 |
|
</t> |
| 6114 |
|
<t>/ MIDI_INSTRUMENT_MAP SP midi_map |
| 6115 |
|
</t> |
| 6116 |
|
<t>/ MIDI_INSTRUMENT_MAP SP ALL |
| 6117 |
|
</t> |
| 6118 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP FORCE SP pathname |
| 6119 |
|
</t> |
| 6120 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP pathname |
| 6121 |
|
</t> |
| 6122 |
|
<t>/ DB_INSTRUMENT SP pathname |
| 6123 |
|
</t> |
| 6124 |
|
</list> |
| 6125 |
|
</t> |
| 6126 |
|
<t>get_instruction = |
| 6127 |
|
<list> |
| 6128 |
|
<t>AVAILABLE_ENGINES |
| 6129 |
|
</t> |
| 6130 |
|
<t>/ AVAILABLE_MIDI_INPUT_DRIVERS |
| 6131 |
|
</t> |
| 6132 |
|
<t>/ MIDI_INPUT_DRIVER SP INFO SP string |
| 6133 |
|
</t> |
| 6134 |
|
<t>/ MIDI_INPUT_DRIVER_PARAMETER SP INFO SP string SP string |
| 6135 |
|
</t> |
| 6136 |
|
<t>/ MIDI_INPUT_DRIVER_PARAMETER SP INFO SP string SP string SP key_val_list |
| 6137 |
|
</t> |
| 6138 |
|
<t>/ AVAILABLE_AUDIO_OUTPUT_DRIVERS |
| 6139 |
|
</t> |
| 6140 |
|
<t>/ AUDIO_OUTPUT_DRIVER SP INFO SP string |
| 6141 |
|
</t> |
| 6142 |
|
<t>/ AUDIO_OUTPUT_DRIVER_PARAMETER SP INFO SP string SP string |
| 6143 |
|
</t> |
| 6144 |
|
<t>/ AUDIO_OUTPUT_DRIVER_PARAMETER SP INFO SP string SP string SP key_val_list |
| 6145 |
|
</t> |
| 6146 |
|
<t>/ AUDIO_OUTPUT_DEVICES |
| 6147 |
|
</t> |
| 6148 |
|
<t>/ MIDI_INPUT_DEVICES |
| 6149 |
|
</t> |
| 6150 |
|
<t>/ AUDIO_OUTPUT_DEVICE SP INFO SP number |
| 6151 |
|
</t> |
| 6152 |
|
<t>/ MIDI_INPUT_DEVICE SP INFO SP number |
| 6153 |
|
</t> |
| 6154 |
|
<t>/ MIDI_INPUT_PORT SP INFO SP number SP number |
| 6155 |
|
</t> |
| 6156 |
|
<t>/ MIDI_INPUT_PORT_PARAMETER SP INFO SP number SP number SP string |
| 6157 |
|
</t> |
| 6158 |
|
<t>/ AUDIO_OUTPUT_CHANNEL SP INFO SP number SP number |
| 6159 |
|
</t> |
| 6160 |
|
<t>/ AUDIO_OUTPUT_CHANNEL_PARAMETER SP INFO SP number SP number SP string |
| 6161 |
|
</t> |
| 6162 |
|
<t>/ CHANNELS |
| 6163 |
|
</t> |
| 6164 |
|
<t>/ CHANNEL SP INFO SP sampler_channel |
| 6165 |
|
</t> |
| 6166 |
|
<t>/ CHANNEL SP BUFFER_FILL SP buffer_size_type SP sampler_channel |
| 6167 |
|
</t> |
| 6168 |
|
<t>/ CHANNEL SP STREAM_COUNT SP sampler_channel |
| 6169 |
|
</t> |
| 6170 |
|
<t>/ CHANNEL SP VOICE_COUNT SP sampler_channel |
| 6171 |
|
</t> |
| 6172 |
|
<t>/ ENGINE SP INFO SP engine_name |
| 6173 |
|
</t> |
| 6174 |
|
<t>/ SERVER SP INFO |
| 6175 |
|
</t> |
| 6176 |
|
<t>/ TOTAL_VOICE_COUNT |
| 6177 |
|
</t> |
| 6178 |
|
<t>/ TOTAL_VOICE_COUNT_MAX |
| 6179 |
|
</t> |
| 6180 |
|
<t>/ MIDI_INSTRUMENTS SP midi_map |
| 6181 |
|
</t> |
| 6182 |
|
<t>/ MIDI_INSTRUMENTS SP ALL |
| 6183 |
|
</t> |
| 6184 |
|
<t>/ MIDI_INSTRUMENT SP INFO SP midi_map SP midi_bank SP midi_prog |
| 6185 |
|
</t> |
| 6186 |
|
<t>/ MIDI_INSTRUMENT_MAPS |
| 6187 |
|
</t> |
| 6188 |
|
<t>/ MIDI_INSTRUMENT_MAP SP INFO SP midi_map |
| 6189 |
|
</t> |
| 6190 |
|
<t>/ FX_SENDS SP sampler_channel |
| 6191 |
|
</t> |
| 6192 |
|
<t>/ FX_SEND SP INFO SP sampler_channel SP fx_send_id |
| 6193 |
|
</t> |
| 6194 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP RECURSIVE SP pathname |
| 6195 |
|
</t> |
| 6196 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP pathname |
| 6197 |
|
</t> |
| 6198 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP INFO SP pathname |
| 6199 |
|
</t> |
| 6200 |
|
<t>/ DB_INSTRUMENTS SP RECURSIVE SP pathname |
| 6201 |
|
</t> |
| 6202 |
|
<t>/ DB_INSTRUMENTS SP pathname |
| 6203 |
|
</t> |
| 6204 |
|
<t>/ DB_INSTRUMENT SP INFO SP pathname |
| 6205 |
|
</t> |
| 6206 |
|
<t>/ DB_INSTRUMENTS_JOB SP INFO SP number |
| 6207 |
|
</t> |
| 6208 |
|
<t>/ VOLUME |
| 6209 |
|
</t> |
| 6210 |
|
</list> |
| 6211 |
|
</t> |
| 6212 |
|
<t>set_instruction = |
| 6213 |
|
<list> |
| 6214 |
|
<t>AUDIO_OUTPUT_DEVICE_PARAMETER SP number SP string '=' param_val_list |
| 6215 |
|
</t> |
| 6216 |
|
<t>/ AUDIO_OUTPUT_CHANNEL_PARAMETER SP number SP number SP string '=' param_val_list |
| 6217 |
|
</t> |
| 6218 |
|
<t>/ MIDI_INPUT_DEVICE_PARAMETER SP number SP string '=' param_val_list |
| 6219 |
|
</t> |
| 6220 |
|
<t>/ MIDI_INPUT_PORT_PARAMETER SP number SP number SP string '=' param_val_list |
| 6221 |
|
</t> |
| 6222 |
|
<t>/ CHANNEL SP set_chan_instruction |
| 6223 |
|
</t> |
| 6224 |
|
<t>/ MIDI_INSTRUMENT_MAP SP NAME SP midi_map SP map_name |
| 6225 |
|
</t> |
| 6226 |
|
<t>/ FX_SEND SP NAME SP sampler_channel SP fx_send_id SP fx_send_name |
| 6227 |
|
</t> |
| 6228 |
|
<t>/ FX_SEND SP AUDIO_OUTPUT_CHANNEL SP sampler_channel SP fx_send_id SP audio_channel_index SP audio_channel_index |
| 6229 |
|
</t> |
| 6230 |
|
<t>/ FX_SEND SP MIDI_CONTROLLER SP sampler_channel SP fx_send_id SP midi_ctrl |
| 6231 |
|
</t> |
| 6232 |
|
<t>/ FX_SEND SP LEVEL SP sampler_channel SP fx_send_id SP volume_value |
| 6233 |
|
</t> |
| 6234 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP NAME SP pathname SP dirname |
| 6235 |
|
</t> |
| 6236 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP DESCRIPTION SP pathname SP stringval |
| 6237 |
|
</t> |
| 6238 |
|
<t>/ DB_INSTRUMENT SP NAME SP pathname SP dirname |
| 6239 |
|
</t> |
| 6240 |
|
<t>/ DB_INSTRUMENT SP DESCRIPTION SP pathname SP stringval |
| 6241 |
|
</t> |
| 6242 |
|
<t>/ ECHO SP boolean |
| 6243 |
|
</t> |
| 6244 |
|
<t>/ VOLUME SP volume_value |
| 6245 |
|
</t> |
| 6246 |
|
</list> |
| 6247 |
|
</t> |
| 6248 |
|
<t>create_instruction = |
| 6249 |
|
<list> |
| 6250 |
|
<t>AUDIO_OUTPUT_DEVICE SP string SP key_val_list |
| 6251 |
|
</t> |
| 6252 |
|
<t>/ AUDIO_OUTPUT_DEVICE SP string |
| 6253 |
|
</t> |
| 6254 |
|
<t>/ MIDI_INPUT_DEVICE SP string SP key_val_list |
| 6255 |
|
</t> |
| 6256 |
|
<t>/ MIDI_INPUT_DEVICE SP string |
| 6257 |
|
</t> |
| 6258 |
|
<t>/ FX_SEND SP sampler_channel SP midi_ctrl |
| 6259 |
|
</t> |
| 6260 |
|
<t>/ FX_SEND SP sampler_channel SP midi_ctrl SP fx_send_name |
| 6261 |
|
</t> |
| 6262 |
|
</list> |
| 6263 |
|
</t> |
| 6264 |
|
<t>reset_instruction = |
| 6265 |
|
<list> |
| 6266 |
|
<t>CHANNEL SP sampler_channel |
| 6267 |
|
</t> |
| 6268 |
|
</list> |
| 6269 |
|
</t> |
| 6270 |
|
<t>clear_instruction = |
| 6271 |
|
<list> |
| 6272 |
|
<t>MIDI_INSTRUMENTS SP midi_map |
| 6273 |
|
</t> |
| 6274 |
|
<t>/ MIDI_INSTRUMENTS SP ALL |
| 6275 |
|
</t> |
| 6276 |
|
</list> |
| 6277 |
|
</t> |
| 6278 |
|
<t>find_instruction = |
| 6279 |
|
<list> |
| 6280 |
|
<t>DB_INSTRUMENTS SP NON_RECURSIVE SP pathname SP query_val_list |
| 6281 |
|
</t> |
| 6282 |
|
<t>/ DB_INSTRUMENTS SP pathname SP query_val_list |
| 6283 |
|
</t> |
| 6284 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP NON_RECURSIVE SP pathname SP query_val_list |
| 6285 |
|
</t> |
| 6286 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP pathname SP query_val_list |
| 6287 |
|
</t> |
| 6288 |
|
</list> |
| 6289 |
|
</t> |
| 6290 |
|
<t>move_instruction = |
| 6291 |
|
<list> |
| 6292 |
|
<t>DB_INSTRUMENT_DIRECTORY SP pathname SP pathname |
| 6293 |
|
</t> |
| 6294 |
|
<t>/ DB_INSTRUMENT SP pathname SP pathname |
| 6295 |
|
</t> |
| 6296 |
|
</list> |
| 6297 |
|
</t> |
| 6298 |
|
<t>copy_instruction = |
| 6299 |
|
<list> |
| 6300 |
|
<t>DB_INSTRUMENT_DIRECTORY SP pathname SP pathname |
| 6301 |
|
</t> |
| 6302 |
|
<t>/ DB_INSTRUMENT SP pathname SP pathname |
| 6303 |
|
</t> |
| 6304 |
|
</list> |
| 6305 |
|
</t> |
| 6306 |
|
<t>destroy_instruction = |
| 6307 |
|
<list> |
| 6308 |
|
<t>AUDIO_OUTPUT_DEVICE SP number |
| 6309 |
|
</t> |
| 6310 |
|
<t>/ MIDI_INPUT_DEVICE SP number |
| 6311 |
|
</t> |
| 6312 |
|
<t>/ FX_SEND SP sampler_channel SP fx_send_id |
| 6313 |
|
</t> |
| 6314 |
|
</list> |
| 6315 |
|
</t> |
| 6316 |
|
<t>load_instruction = |
| 6317 |
|
<list> |
| 6318 |
|
<t>INSTRUMENT SP load_instr_args |
| 6319 |
|
</t> |
| 6320 |
|
<t>/ ENGINE SP load_engine_args |
| 6321 |
|
</t> |
| 6322 |
|
</list> |
| 6323 |
|
</t> |
| 6324 |
|
<t>set_chan_instruction = |
| 6325 |
|
<list> |
| 6326 |
|
<t>AUDIO_OUTPUT_DEVICE SP sampler_channel SP device_index |
| 6327 |
|
</t> |
| 6328 |
|
<t>/ AUDIO_OUTPUT_CHANNEL SP sampler_channel SP audio_channel_index SP audio_channel_index |
| 6329 |
|
</t> |
| 6330 |
|
<t>/ AUDIO_OUTPUT_TYPE SP sampler_channel SP audio_output_type_name |
| 6331 |
|
</t> |
| 6332 |
|
<t>/ MIDI_INPUT SP sampler_channel SP device_index SP midi_input_port_index SP midi_input_channel_index |
| 6333 |
|
</t> |
| 6334 |
|
<t>/ MIDI_INPUT_DEVICE SP sampler_channel SP device_index |
| 6335 |
|
</t> |
| 6336 |
|
<t>/ MIDI_INPUT_PORT SP sampler_channel SP midi_input_port_index |
| 6337 |
|
</t> |
| 6338 |
|
<t>/ MIDI_INPUT_CHANNEL SP sampler_channel SP midi_input_channel_index |
| 6339 |
|
</t> |
| 6340 |
|
<t>/ MIDI_INPUT_TYPE SP sampler_channel SP midi_input_type_name |
| 6341 |
|
</t> |
| 6342 |
|
<t>/ VOLUME SP sampler_channel SP volume_value |
| 6343 |
|
</t> |
| 6344 |
|
<t>/ MUTE SP sampler_channel SP boolean |
| 6345 |
|
</t> |
| 6346 |
|
<t>/ SOLO SP sampler_channel SP boolean |
| 6347 |
|
</t> |
| 6348 |
|
<t>/ MIDI_INSTRUMENT_MAP SP sampler_channel SP midi_map |
| 6349 |
|
</t> |
| 6350 |
|
<t>/ MIDI_INSTRUMENT_MAP SP sampler_channel SP NONE |
| 6351 |
|
</t> |
| 6352 |
|
<t>/ MIDI_INSTRUMENT_MAP SP sampler_channel SP DEFAULT |
| 6353 |
|
</t> |
| 6354 |
|
</list> |
| 6355 |
|
</t> |
| 6356 |
|
<t>edit_instruction = |
| 6357 |
|
<list> |
| 6358 |
|
<t>INSTRUMENT SP sampler_channel |
| 6359 |
|
</t> |
| 6360 |
|
</list> |
| 6361 |
|
</t> |
| 6362 |
|
<t>modal_arg = |
| 6363 |
|
<list> |
| 6364 |
|
<t>/* epsilon (empty argument) */ |
| 6365 |
|
</t> |
| 6366 |
|
<t>/ NON_MODAL SP |
| 6367 |
|
</t> |
| 6368 |
|
</list> |
| 6369 |
|
</t> |
| 6370 |
|
<t>key_val_list = |
| 6371 |
|
<list> |
| 6372 |
|
<t>string '=' param_val_list |
| 6373 |
|
</t> |
| 6374 |
|
<t>/ key_val_list SP string '=' param_val_list |
| 6375 |
|
</t> |
| 6376 |
|
</list> |
| 6377 |
|
</t> |
| 6378 |
|
<t>buffer_size_type = |
| 6379 |
|
<list> |
| 6380 |
|
<t>BYTES |
| 6381 |
|
</t> |
| 6382 |
|
<t>/ PERCENTAGE |
| 6383 |
|
</t> |
| 6384 |
|
</list> |
| 6385 |
|
</t> |
| 6386 |
|
<t>list_instruction = |
| 6387 |
|
<list> |
| 6388 |
|
<t>AUDIO_OUTPUT_DEVICES |
| 6389 |
|
</t> |
| 6390 |
|
<t>/ MIDI_INPUT_DEVICES |
| 6391 |
|
</t> |
| 6392 |
|
<t>/ CHANNELS |
| 6393 |
|
</t> |
| 6394 |
|
<t>/ AVAILABLE_ENGINES |
| 6395 |
|
</t> |
| 6396 |
|
<t>/ AVAILABLE_MIDI_INPUT_DRIVERS |
| 6397 |
|
</t> |
| 6398 |
|
<t>/ AVAILABLE_AUDIO_OUTPUT_DRIVERS |
| 6399 |
|
</t> |
| 6400 |
|
<t>/ MIDI_INSTRUMENTS SP midi_map |
| 6401 |
|
</t> |
| 6402 |
|
<t>/ MIDI_INSTRUMENTS SP ALL |
| 6403 |
|
</t> |
| 6404 |
|
<t>/ MIDI_INSTRUMENT_MAPS |
| 6405 |
|
</t> |
| 6406 |
|
<t>/ FX_SENDS SP sampler_channel |
| 6407 |
|
</t> |
| 6408 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP RECURSIVE SP pathname |
| 6409 |
|
</t> |
| 6410 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP pathname |
| 6411 |
|
</t> |
| 6412 |
|
<t>/ DB_INSTRUMENTS SP RECURSIVE SP pathname |
| 6413 |
|
</t> |
| 6414 |
|
<t>/ DB_INSTRUMENTS SP pathname |
| 6415 |
|
</t> |
| 6416 |
|
</list> |
| 6417 |
|
</t> |
| 6418 |
|
<t>load_instr_args = |
| 6419 |
|
<list> |
| 6420 |
|
<t>filename SP instrument_index SP sampler_channel |
| 6421 |
|
</t> |
| 6422 |
|
<t>/ NON_MODAL SP filename SP instrument_index SP sampler_channel |
| 6423 |
|
</t> |
| 6424 |
|
</list> |
| 6425 |
|
</t> |
| 6426 |
|
<t>load_engine_args = |
| 6427 |
|
<list> |
| 6428 |
|
<t>engine_name SP sampler_channel |
| 6429 |
|
</t> |
| 6430 |
|
</list> |
| 6431 |
|
</t> |
| 6432 |
|
<t>instr_load_mode = |
| 6433 |
|
<list> |
| 6434 |
|
<t>ON_DEMAND |
| 6435 |
|
</t> |
| 6436 |
|
<t>/ ON_DEMAND_HOLD |
| 6437 |
|
</t> |
| 6438 |
|
<t>/ PERSISTENT |
| 6439 |
|
</t> |
| 6440 |
|
</list> |
| 6441 |
|
</t> |
| 6442 |
|
<t>device_index = |
| 6443 |
|
<list> |
| 6444 |
|
<t>number |
| 6445 |
|
</t> |
| 6446 |
|
</list> |
| 6447 |
|
</t> |
| 6448 |
|
<t>audio_channel_index = |
| 6449 |
|
<list> |
| 6450 |
|
<t>number |
| 6451 |
|
</t> |
| 6452 |
|
</list> |
| 6453 |
|
</t> |
| 6454 |
|
<t>audio_output_type_name = |
| 6455 |
|
<list> |
| 6456 |
|
<t>string |
| 6457 |
|
</t> |
| 6458 |
|
</list> |
| 6459 |
|
</t> |
| 6460 |
|
<t>midi_input_port_index = |
| 6461 |
|
<list> |
| 6462 |
|
<t>number |
| 6463 |
|
</t> |
| 6464 |
|
</list> |
| 6465 |
|
</t> |
| 6466 |
|
<t>midi_input_channel_index = |
| 6467 |
|
<list> |
| 6468 |
|
<t>number |
| 6469 |
|
</t> |
| 6470 |
|
<t>/ ALL |
| 6471 |
|
</t> |
| 6472 |
|
</list> |
| 6473 |
|
</t> |
| 6474 |
|
<t>midi_input_type_name = |
| 6475 |
|
<list> |
| 6476 |
|
<t>string |
| 6477 |
|
</t> |
| 6478 |
|
</list> |
| 6479 |
|
</t> |
| 6480 |
|
<t>midi_map = |
| 6481 |
|
<list> |
| 6482 |
|
<t>number |
| 6483 |
|
</t> |
| 6484 |
|
</list> |
| 6485 |
|
</t> |
| 6486 |
|
<t>midi_bank = |
| 6487 |
|
<list> |
| 6488 |
|
<t>number |
| 6489 |
|
</t> |
| 6490 |
|
</list> |
| 6491 |
|
</t> |
| 6492 |
|
<t>midi_prog = |
| 6493 |
|
<list> |
| 6494 |
|
<t>number |
| 6495 |
|
</t> |
| 6496 |
|
</list> |
| 6497 |
|
</t> |
| 6498 |
|
<t>midi_ctrl = |
| 6499 |
|
<list> |
| 6500 |
|
<t>number |
| 6501 |
|
</t> |
| 6502 |
|
</list> |
| 6503 |
|
</t> |
| 6504 |
|
<t>volume_value = |
| 6505 |
|
<list> |
| 6506 |
|
<t>dotnum |
| 6507 |
|
</t> |
| 6508 |
|
<t>/ number |
| 6509 |
|
</t> |
| 6510 |
|
</list> |
| 6511 |
|
</t> |
| 6512 |
|
<t>sampler_channel = |
| 6513 |
|
<list> |
| 6514 |
|
<t>number |
| 6515 |
|
</t> |
| 6516 |
|
</list> |
| 6517 |
|
</t> |
| 6518 |
|
<t>instrument_index = |
| 6519 |
|
<list> |
| 6520 |
|
<t>number |
| 6521 |
|
</t> |
| 6522 |
|
</list> |
| 6523 |
|
</t> |
| 6524 |
|
<t>fx_send_id = |
| 6525 |
|
<list> |
| 6526 |
|
<t>number |
| 6527 |
|
</t> |
| 6528 |
|
</list> |
| 6529 |
|
</t> |
| 6530 |
|
<t>engine_name = |
| 6531 |
|
<list> |
| 6532 |
|
<t>string |
| 6533 |
|
</t> |
| 6534 |
|
</list> |
| 6535 |
|
</t> |
| 6536 |
|
<t>pathname = |
| 6537 |
|
<list> |
| 6538 |
|
<t>stringval |
| 6539 |
|
</t> |
| 6540 |
|
</list> |
| 6541 |
|
</t> |
| 6542 |
|
<t>dirname = |
| 6543 |
|
<list> |
| 6544 |
|
<t>stringval |
| 6545 |
|
</t> |
| 6546 |
|
</list> |
| 6547 |
|
</t> |
| 6548 |
|
<t>filename = |
| 6549 |
|
<list> |
| 6550 |
|
<t>stringval_escaped |
| 6551 |
|
</t> |
| 6552 |
|
</list> |
| 6553 |
|
</t> |
| 6554 |
|
<t>map_name = |
| 6555 |
|
<list> |
| 6556 |
|
<t>stringval |
| 6557 |
|
</t> |
| 6558 |
|
</list> |
| 6559 |
|
</t> |
| 6560 |
|
<t>entry_name = |
| 6561 |
|
<list> |
| 6562 |
|
<t>stringval |
| 6563 |
|
</t> |
| 6564 |
|
</list> |
| 6565 |
|
</t> |
| 6566 |
|
<t>fx_send_name = |
| 6567 |
|
<list> |
| 6568 |
|
<t>stringval |
| 6569 |
|
</t> |
| 6570 |
|
</list> |
| 6571 |
|
</t> |
| 6572 |
|
<t>param_val_list = |
| 6573 |
|
<list> |
| 6574 |
|
<t>param_val |
| 6575 |
|
</t> |
| 6576 |
|
<t>/ param_val_list','param_val |
| 6577 |
|
</t> |
| 6578 |
|
</list> |
| 6579 |
|
</t> |
| 6580 |
|
<t>param_val = |
| 6581 |
|
<list> |
| 6582 |
|
<t>string |
| 6583 |
|
</t> |
| 6584 |
|
<t>/ stringval |
| 6585 |
|
</t> |
| 6586 |
|
<t>/ number |
| 6587 |
|
</t> |
| 6588 |
|
<t>/ dotnum |
| 6589 |
|
</t> |
| 6590 |
|
</list> |
| 6591 |
|
</t> |
| 6592 |
|
<t>query_val_list = |
| 6593 |
|
<list> |
| 6594 |
|
<t>string '=' query_val |
| 6595 |
|
</t> |
| 6596 |
|
<t>/ query_val_list SP string '=' query_val |
| 6597 |
|
</t> |
| 6598 |
|
</list> |
| 6599 |
|
</t> |
| 6600 |
|
<t>query_val = |
| 6601 |
|
<list> |
| 6602 |
|
<t>string |
| 6603 |
|
</t> |
| 6604 |
|
<t>/ stringval |
| 6605 |
|
</t> |
| 6606 |
|
</list> |
| 6607 |
|
</t> |
| 6608 |
|
<t>scan_mode = |
| 6609 |
|
<list> |
| 6610 |
|
<t>RECURSIVE |
| 6611 |
|
</t> |
| 6612 |
|
<t>/ NON_RECURSIVE |
| 6613 |
|
</t> |
| 6614 |
|
<t>/ FLAT |
| 6615 |
|
</t> |
| 6616 |
|
</list> |
| 6617 |
|
</t> |
| 6618 |
|
|
| 6619 |
|
<!-- GRAMMAR_BNF_END - do NOT delete or modify this line !!! --> |
| 6620 |
|
|
| 6621 |
|
<section title="Character Set and Escape Sequences" anchor="character_set"> |
| 6622 |
|
<t>Older versions of this protocol up to and including v1.1 only |
| 6623 |
|
supported the standard ASCII character set (ASCII code 0 - 127) |
| 6624 |
|
<xref target="RFC20"/>, all younger versions of this protocol |
| 6625 |
|
however support the Extended ASCII character set (ASCII code |
| 6626 |
|
0 - 255). The same group of younger protocols also support |
| 6627 |
|
escape sequences, but only for certain, explicitly declared |
| 6628 |
|
parts of the protocol. The supported escape sequences are |
| 6629 |
|
defined as follows:</t> |
| 6630 |
|
<texttable> |
| 6631 |
|
<ttcol>ASCII Character Sequence</ttcol> |
| 6632 |
|
<ttcol>Translated into (Name)</ttcol> |
| 6633 |
|
<c>\n</c> <c>new line</c> |
| 6634 |
|
<c>\r</c> <c>carriage return</c> |
| 6635 |
|
<c>\f</c> <c>form feed</c> |
| 6636 |
|
<c>\t</c> <c>horizontal tab</c> |
| 6637 |
|
<c>\v</c> <c>vertical tab</c> |
| 6638 |
|
<c>\'</c> <c>apostrophe</c> |
| 6639 |
|
<c>\"</c> <c>quotation mark</c> |
| 6640 |
|
<c>\\</c> <c>backslash</c> |
| 6641 |
|
<c>\OOO</c> <c>three digit octal ASCII code of the character</c> |
| 6642 |
|
<c>\xHH</c> <c>two digit hex ASCII code of the character</c> |
| 6643 |
|
</texttable> |
| 6644 |
|
<t>Notice: due to the transition of certain parts of the |
| 6645 |
|
protocol which now support escape sequences, a slight backward |
| 6646 |
|
incompatibility to protocols version v1.1 and younger has been |
| 6647 |
|
introduced. The only difference is that in parts of the protocol |
| 6648 |
|
where escape characters are now supported, a backslash characters |
| 6649 |
|
MUST be escaped as well (that is as double backslash), whereas |
| 6650 |
|
in the old versions a single backslash was sufficient.</t> |
| 6651 |
|
</section> |
| 6652 |
</section> |
</section> |
| 6653 |
|
|
| 6654 |
<section title="Events"> |
<section title="Events" anchor="events"> |
| 6655 |
<t>This chapter will describe all currently defined events supported by LinuxSampler.</t> |
<t>This chapter will describe all currently defined events supported by LinuxSampler.</t> |
| 6656 |
|
|
| 6657 |
<section title="Number of sampler channels changed"> |
<section title="Number of audio output devices changed" anchor="SUBSCRIBE AUDIO_OUTPUT_DEVICE_COUNT"> |
| 6658 |
|
<t>Client may want to be notified when the total number of audio output devices on the |
| 6659 |
|
back-end changes by issuing the following command:</t> |
| 6660 |
|
<t> |
| 6661 |
|
<list> |
| 6662 |
|
<t>SUBSCRIBE AUDIO_OUTPUT_DEVICE_COUNT</t> |
| 6663 |
|
</list> |
| 6664 |
|
</t> |
| 6665 |
|
<t>Server will start sending the following notification messages:</t> |
| 6666 |
|
<t> |
| 6667 |
|
<list> |
| 6668 |
|
<t>"NOTIFY:AUDIO_OUTPUT_DEVICE_COUNT:<devices>"</t> |
| 6669 |
|
</list> |
| 6670 |
|
</t> |
| 6671 |
|
<t>where <devices> will be replaced by the new number |
| 6672 |
|
of audio output devices.</t> |
| 6673 |
|
</section> |
| 6674 |
|
|
| 6675 |
|
<section title="Audio output device's settings changed" anchor="SUBSCRIBE AUDIO_OUTPUT_DEVICE_INFO"> |
| 6676 |
|
<t>Client may want to be notified when changes were made to audio output devices on the |
| 6677 |
|
back-end by issuing the following command:</t> |
| 6678 |
|
<t> |
| 6679 |
|
<list> |
| 6680 |
|
<t>SUBSCRIBE AUDIO_OUTPUT_DEVICE_INFO</t> |
| 6681 |
|
</list> |
| 6682 |
|
</t> |
| 6683 |
|
<t>Server will start sending the following notification messages:</t> |
| 6684 |
|
<t> |
| 6685 |
|
<list> |
| 6686 |
|
<t>"NOTIFY:AUDIO_OUTPUT_DEVICE_INFO:<device-id>"</t> |
| 6687 |
|
</list> |
| 6688 |
|
</t> |
| 6689 |
|
<t>where <device-id> will be replaced by the numerical ID of the audio output device, |
| 6690 |
|
which settings has been changed. The front-end will have to send |
| 6691 |
|
the respective command to actually get the audio output device info. Because these messages |
| 6692 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 6693 |
|
time events happening on the server, it is believed that an empty notification |
| 6694 |
|
message is sufficient here.</t> |
| 6695 |
|
</section> |
| 6696 |
|
|
| 6697 |
|
<section title="Number of MIDI input devices changed" anchor="SUBSCRIBE MIDI_INPUT_DEVICE_COUNT"> |
| 6698 |
|
<t>Client may want to be notified when the total number of MIDI input devices on the |
| 6699 |
|
back-end changes by issuing the following command:</t> |
| 6700 |
|
<t> |
| 6701 |
|
<list> |
| 6702 |
|
<t>SUBSCRIBE MIDI_INPUT_DEVICE_COUNT</t> |
| 6703 |
|
</list> |
| 6704 |
|
</t> |
| 6705 |
|
<t>Server will start sending the following notification messages:</t> |
| 6706 |
|
<t> |
| 6707 |
|
<list> |
| 6708 |
|
<t>"NOTIFY:MIDI_INPUT_DEVICE_COUNT:<devices>"</t> |
| 6709 |
|
</list> |
| 6710 |
|
</t> |
| 6711 |
|
<t>where <devices> will be replaced by the new number |
| 6712 |
|
of MIDI input devices.</t> |
| 6713 |
|
</section> |
| 6714 |
|
|
| 6715 |
|
<section title="MIDI input device's settings changed" anchor="SUBSCRIBE MIDI_INPUT_DEVICE_INFO"> |
| 6716 |
|
<t>Client may want to be notified when changes were made to MIDI input devices on the |
| 6717 |
|
back-end by issuing the following command:</t> |
| 6718 |
|
<t> |
| 6719 |
|
<list> |
| 6720 |
|
<t>SUBSCRIBE MIDI_INPUT_DEVICE_INFO</t> |
| 6721 |
|
</list> |
| 6722 |
|
</t> |
| 6723 |
|
<t>Server will start sending the following notification messages:</t> |
| 6724 |
|
<t> |
| 6725 |
|
<list> |
| 6726 |
|
<t>"NOTIFY:MIDI_INPUT_DEVICE_INFO:<device-id>"</t> |
| 6727 |
|
</list> |
| 6728 |
|
</t> |
| 6729 |
|
<t>where <device-id> will be replaced by the numerical ID of the MIDI input device, |
| 6730 |
|
which settings has been changed. The front-end will have to send |
| 6731 |
|
the respective command to actually get the MIDI input device info. Because these messages |
| 6732 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 6733 |
|
time events happening on the server, it is believed that an empty notification |
| 6734 |
|
message is sufficient here.</t> |
| 6735 |
|
</section> |
| 6736 |
|
|
| 6737 |
|
<section title="Number of sampler channels changed" anchor="SUBSCRIBE CHANNEL_COUNT"> |
| 6738 |
<t>Client may want to be notified when the total number of channels on the |
<t>Client may want to be notified when the total number of channels on the |
| 6739 |
back-end changes by issuing the following command:</t> |
back-end changes by issuing the following command:</t> |
| 6740 |
<t> |
<t> |
| 6741 |
<list> |
<list> |
| 6742 |
<t>SUBSCRIBE CHANNELS</t> |
<t>SUBSCRIBE CHANNEL_COUNT</t> |
| 6743 |
</list> |
</list> |
| 6744 |
</t> |
</t> |
| 6745 |
<t>Server will start sending the following notification messages:</t> |
<t>Server will start sending the following notification messages:</t> |
| 6746 |
<t> |
<t> |
| 6747 |
<list> |
<list> |
| 6748 |
<t>"NOTIFY:CHANNELS:<channels>"</t> |
<t>"NOTIFY:CHANNEL_COUNT:<channels>"</t> |
| 6749 |
</list> |
</list> |
| 6750 |
</t> |
</t> |
| 6751 |
<t>where <channels> will be replaced by the new number |
<t>where <channels> will be replaced by the new number |
| 6752 |
of sampler channels.</t> |
of sampler channels.</t> |
| 6753 |
</section> |
</section> |
| 6754 |
|
|
| 6755 |
<section title="Number of active voices changed"> |
<section title="Number of active voices changed" anchor="SUBSCRIBE VOICE_COUNT"> |
| 6756 |
<t>Client may want to be notified when the number of voices on the |
<t>Client may want to be notified when the number of voices on the |
| 6757 |
back-end changes by issuing the following command:</t> |
back-end changes by issuing the following command:</t> |
| 6758 |
<t> |
<t> |
| 6763 |
<t>Server will start sending the following notification messages:</t> |
<t>Server will start sending the following notification messages:</t> |
| 6764 |
<t> |
<t> |
| 6765 |
<list> |
<list> |
| 6766 |
<t>"NOTIFY:VOICE_COUNT:<sampler-channel> <voices>></t> |
<t>"NOTIFY:VOICE_COUNT:<sampler-channel> <voices>"</t> |
| 6767 |
</list> |
</list> |
| 6768 |
</t> |
</t> |
| 6769 |
<t>where <sampler-channel> will be replaced by the sampler channel the |
<t>where <sampler-channel> will be replaced by the sampler channel the |
| 6770 |
voice count change occurred and <voices>> by the new number of |
voice count change occurred and <voices> by the new number of |
| 6771 |
active voices on that channel.</t> |
active voices on that channel.</t> |
| 6772 |
</section> |
</section> |
| 6773 |
|
|
| 6774 |
<section title="Number of active disk streams changed"> |
<section title="Number of active disk streams changed" anchor="SUBSCRIBE STREAM_COUNT"> |
| 6775 |
<t>Client may want to be notified when the number of streams on the back-end |
<t>Client may want to be notified when the number of streams on the back-end |
| 6776 |
changes by issuing the following command: SUBSCRIBE STREAM_COUNT</t> |
changes by issuing the following command: SUBSCRIBE STREAM_COUNT</t> |
| 6777 |
<t> |
<t> |
| 6790 |
active disk streams on that channel.</t> |
active disk streams on that channel.</t> |
| 6791 |
</section> |
</section> |
| 6792 |
|
|
| 6793 |
<section title="Disk stream buffer fill state changed"> |
<section title="Disk stream buffer fill state changed" anchor="SUBSCRIBE BUFFER_FILL"> |
| 6794 |
<t>Client may want to be notified when the number of streams on the back-end |
<t>Client may want to be notified when the buffer fill state of a disk stream |
| 6795 |
changes by issuing the following command:</t> |
on the back-end changes by issuing the following command:</t> |
| 6796 |
<t> |
<t> |
| 6797 |
<list> |
<list> |
| 6798 |
<t>SUBSCRIBE BUFFER_FILL</t> |
<t>SUBSCRIBE BUFFER_FILL</t> |
| 6805 |
</list> |
</list> |
| 6806 |
</t> |
</t> |
| 6807 |
<t>where <sampler-channel> will be replaced by the sampler channel the |
<t>where <sampler-channel> will be replaced by the sampler channel the |
| 6808 |
buffer fill state change occurred and <fill-data> will be replaced by the |
buffer fill state change occurred on and <fill-data> will be replaced by the |
| 6809 |
buffer fill data for this channel as described in 4.4.12 as if the |
buffer fill data for this channel as described in <xref target="GET CHANNEL BUFFER_FILL" /> |
| 6810 |
"GET CHANNEL BUFFER_FILL PERCENTAGE" was issued on this channel.</t> |
as if the <xref target="GET CHANNEL BUFFER_FILL"> |
| 6811 |
|
"GET CHANNEL BUFFER_FILL PERCENTAGE"</xref> command was issued on this channel.</t> |
| 6812 |
</section> |
</section> |
| 6813 |
|
|
| 6814 |
<section title="Channel information changed"> |
<section title="Channel information changed" anchor="SUBSCRIBE CHANNEL_INFO"> |
| 6815 |
<t>Client may want to be notified when changes were made to sampler channels on the |
<t>Client may want to be notified when changes were made to sampler channels on the |
| 6816 |
back-end changes by issuing the following command:</t> |
back-end by issuing the following command:</t> |
| 6817 |
<t> |
<t> |
| 6818 |
<list> |
<list> |
| 6819 |
<t>SUBSCRIBE INFO</t> |
<t>SUBSCRIBE CHANNEL_INFO</t> |
| 6820 |
</list> |
</list> |
| 6821 |
</t> |
</t> |
| 6822 |
<t>Server will start sending the following notification messages:</t> |
<t>Server will start sending the following notification messages:</t> |
| 6823 |
<t> |
<t> |
| 6824 |
<list> |
<list> |
| 6825 |
<t>"NOTIFY:INFO:<sampler-channel>"</t> |
<t>"NOTIFY:CHANNEL_INFO:<sampler-channel>"</t> |
| 6826 |
</list> |
</list> |
| 6827 |
</t> |
</t> |
| 6828 |
<t>where <sampler-channel> will be replaced by the sampler channel the |
<t>where <sampler-channel> will be replaced by the sampler channel the |
| 6833 |
message is sufficient here.</t> |
message is sufficient here.</t> |
| 6834 |
</section> |
</section> |
| 6835 |
|
|
| 6836 |
<section title="Miscellaneous and debugging events"> |
<section title="Number of effect sends changed" anchor="SUBSCRIBE FX_SEND_COUNT"> |
| 6837 |
|
<t>Client may want to be notified when the number of effect sends on |
| 6838 |
|
a particular sampler channel is changed by issuing the following command:</t> |
| 6839 |
|
<t> |
| 6840 |
|
<list> |
| 6841 |
|
<t>SUBSCRIBE FX_SEND_COUNT</t> |
| 6842 |
|
</list> |
| 6843 |
|
</t> |
| 6844 |
|
<t>Server will start sending the following notification messages:</t> |
| 6845 |
|
<t> |
| 6846 |
|
<list> |
| 6847 |
|
<t>"NOTIFY:FX_SEND_COUNT:<channel-id> <fx-sends>"</t> |
| 6848 |
|
</list> |
| 6849 |
|
</t> |
| 6850 |
|
<t>where <channel-id> will be replaced by the numerical ID of the sampler |
| 6851 |
|
channel, on which the effect sends number is changed and <fx-sends> will |
| 6852 |
|
be replaced by the new number of effect sends on that channel.</t> |
| 6853 |
|
</section> |
| 6854 |
|
|
| 6855 |
|
<section title="Effect send information changed" anchor="SUBSCRIBE FX_SEND_INFO"> |
| 6856 |
|
<t>Client may want to be notified when changes were made to effect sends on a |
| 6857 |
|
a particular sampler channel by issuing the following command:</t> |
| 6858 |
|
<t> |
| 6859 |
|
<list> |
| 6860 |
|
<t>SUBSCRIBE FX_SEND_INFO</t> |
| 6861 |
|
</list> |
| 6862 |
|
</t> |
| 6863 |
|
<t>Server will start sending the following notification messages:</t> |
| 6864 |
|
<t> |
| 6865 |
|
<list> |
| 6866 |
|
<t>"NOTIFY:FX_SEND_INFO:<channel-id> <fx-send-id>"</t> |
| 6867 |
|
</list> |
| 6868 |
|
</t> |
| 6869 |
|
<t>where <channel-id> will be replaced by the numerical ID of the sampler |
| 6870 |
|
channel, on which an effect send entity is changed and <fx-send-id> will |
| 6871 |
|
be replaced by the numerical ID of the changed effect send.</t> |
| 6872 |
|
</section> |
| 6873 |
|
|
| 6874 |
|
<section title="Total number of active voices changed" anchor="SUBSCRIBE TOTAL_VOICE_COUNT"> |
| 6875 |
|
<t>Client may want to be notified when the total number of voices on the |
| 6876 |
|
back-end changes by issuing the following command:</t> |
| 6877 |
|
<t> |
| 6878 |
|
<list> |
| 6879 |
|
<t>SUBSCRIBE TOTAL_VOICE_COUNT</t> |
| 6880 |
|
</list> |
| 6881 |
|
</t> |
| 6882 |
|
<t>Server will start sending the following notification messages:</t> |
| 6883 |
|
<t> |
| 6884 |
|
<list> |
| 6885 |
|
<t>"NOTIFY:TOTAL_VOICE_COUNT:<voices>"</t> |
| 6886 |
|
</list> |
| 6887 |
|
</t> |
| 6888 |
|
<t>where <voices> will be replaced by the new number of |
| 6889 |
|
all currently active voices.</t> |
| 6890 |
|
</section> |
| 6891 |
|
|
| 6892 |
|
<section title="Number of MIDI instrument maps changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_MAP_COUNT"> |
| 6893 |
|
<t>Client may want to be notified when the number of MIDI instrument maps on the |
| 6894 |
|
back-end changes by issuing the following command:</t> |
| 6895 |
|
<t> |
| 6896 |
|
<list> |
| 6897 |
|
<t>SUBSCRIBE MIDI_INSTRUMENT_MAP_COUNT</t> |
| 6898 |
|
</list> |
| 6899 |
|
</t> |
| 6900 |
|
<t>Server will start sending the following notification messages:</t> |
| 6901 |
|
<t> |
| 6902 |
|
<list> |
| 6903 |
|
<t>"NOTIFY:MIDI_INSTRUMENT_MAP_COUNT:<maps>"</t> |
| 6904 |
|
</list> |
| 6905 |
|
</t> |
| 6906 |
|
<t>where <maps> will be replaced by the new number |
| 6907 |
|
of MIDI instrument maps.</t> |
| 6908 |
|
</section> |
| 6909 |
|
|
| 6910 |
|
<section title="MIDI instrument map information changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO"> |
| 6911 |
|
<t>Client may want to be notified when changes were made to MIDI instrument maps on the |
| 6912 |
|
back-end by issuing the following command:</t> |
| 6913 |
|
<t> |
| 6914 |
|
<list> |
| 6915 |
|
<t>SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO</t> |
| 6916 |
|
</list> |
| 6917 |
|
</t> |
| 6918 |
|
<t>Server will start sending the following notification messages:</t> |
| 6919 |
|
<t> |
| 6920 |
|
<list> |
| 6921 |
|
<t>"NOTIFY:MIDI_INSTRUMENT_MAP_INFO:<map-id>"</t> |
| 6922 |
|
</list> |
| 6923 |
|
</t> |
| 6924 |
|
<t>where <map-id> will be replaced by the numerical ID of the MIDI instrument map, |
| 6925 |
|
for which information changes occurred. The front-end will have to send |
| 6926 |
|
the respective command to actually get the MIDI instrument map info. Because these messages |
| 6927 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 6928 |
|
time events happening on the server, it is believed that an empty notification |
| 6929 |
|
message is sufficient here.</t> |
| 6930 |
|
</section> |
| 6931 |
|
|
| 6932 |
|
<section title="Number of MIDI instruments changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_COUNT"> |
| 6933 |
|
<t>Client may want to be notified when the number of MIDI instrument maps on the |
| 6934 |
|
back-end changes by issuing the following command:</t> |
| 6935 |
|
<t> |
| 6936 |
|
<list> |
| 6937 |
|
<t>SUBSCRIBE MIDI_INSTRUMENT_COUNT</t> |
| 6938 |
|
</list> |
| 6939 |
|
</t> |
| 6940 |
|
<t>Server will start sending the following notification messages:</t> |
| 6941 |
|
<t> |
| 6942 |
|
<list> |
| 6943 |
|
<t>"NOTIFY:MIDI_INSTRUMENT_COUNT:<map-id> <instruments>"</t> |
| 6944 |
|
</list> |
| 6945 |
|
</t> |
| 6946 |
|
<t>where <map-id> is the numerical ID of the MIDI instrument map, in which |
| 6947 |
|
the nuber of instruments has changed and <instruments> will be replaced by |
| 6948 |
|
the new number of MIDI instruments in the specified map.</t> |
| 6949 |
|
</section> |
| 6950 |
|
|
| 6951 |
|
<section title="MIDI instrument information changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_INFO"> |
| 6952 |
|
<t>Client may want to be notified when changes were made to MIDI instruments on the |
| 6953 |
|
back-end by issuing the following command:</t> |
| 6954 |
|
<t> |
| 6955 |
|
<list> |
| 6956 |
|
<t>SUBSCRIBE MIDI_INSTRUMENT_INFO</t> |
| 6957 |
|
</list> |
| 6958 |
|
</t> |
| 6959 |
|
<t>Server will start sending the following notification messages:</t> |
| 6960 |
|
<t> |
| 6961 |
|
<list> |
| 6962 |
|
<t>"NOTIFY:MIDI_INSTRUMENT_INFO:<map-id> <bank> <program>"</t> |
| 6963 |
|
</list> |
| 6964 |
|
</t> |
| 6965 |
|
<t>where <map-id> will be replaced by the numerical ID of the MIDI instrument map, |
| 6966 |
|
in which a MIDI instrument is changed. <bank> and <program> specifies |
| 6967 |
|
the location of the changed MIDI instrument in the map. The front-end will have to send |
| 6968 |
|
the respective command to actually get the MIDI instrument info. Because these messages |
| 6969 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 6970 |
|
time events happening on the server, it is believed that an empty notification |
| 6971 |
|
message is sufficient here.</t> |
| 6972 |
|
</section> |
| 6973 |
|
|
| 6974 |
|
<section title="Global settings changed" anchor="SUBSCRIBE GLOBAL_INFO"> |
| 6975 |
|
<t>Client may want to be notified when changes to the global settings |
| 6976 |
|
of the sampler were made by issuing the following command:</t> |
| 6977 |
|
<t> |
| 6978 |
|
<list> |
| 6979 |
|
<t>SUBSCRIBE GLOBAL_INFO</t> |
| 6980 |
|
</list> |
| 6981 |
|
</t> |
| 6982 |
|
<t>Server will start sending the following types of notification messages:</t> |
| 6983 |
|
<t> |
| 6984 |
|
<list> |
| 6985 |
|
<t>"NOTIFY:GLOBAL_INFO:VOLUME <volume>" - Notifies that the |
| 6986 |
|
golbal volume of the sampler is changed, where <volume> will be |
| 6987 |
|
replaced by the optional dotted floating point value, reflecting the |
| 6988 |
|
new global volume parameter.</t> |
| 6989 |
|
</list> |
| 6990 |
|
</t> |
| 6991 |
|
</section> |
| 6992 |
|
|
| 6993 |
|
<section title="Number of database instrument directories changed" anchor="SUBSCRIBE DB_INSTRUMENT_DIRECTORY_COUNT"> |
| 6994 |
|
<t>Client may want to be notified when the number of instrument |
| 6995 |
|
directories in a particular directory in the instruments database |
| 6996 |
|
is changed by issuing the following command:</t> |
| 6997 |
|
<t> |
| 6998 |
|
<list> |
| 6999 |
|
<t>SUBSCRIBE DB_INSTRUMENT_DIRECTORY_COUNT</t> |
| 7000 |
|
</list> |
| 7001 |
|
</t> |
| 7002 |
|
<t>Server will start sending the following notification messages:</t> |
| 7003 |
|
<t> |
| 7004 |
|
<list> |
| 7005 |
|
<t>"NOTIFY:DB_INSTRUMENT_DIRECTORY_COUNT:<dir-path>"</t> |
| 7006 |
|
</list> |
| 7007 |
|
</t> |
| 7008 |
|
<t>where <dir-path> will be replaced by the absolute path |
| 7009 |
|
name of the directory in the instruments database, |
| 7010 |
|
in which the number of directories is changed.</t> |
| 7011 |
|
<t>Note that when a non-empty directory is removed, this event |
| 7012 |
|
is not sent for the subdirectories in that directory.</t> |
| 7013 |
|
</section> |
| 7014 |
|
|
| 7015 |
|
<section title="Database instrument directory information changed" anchor="SUBSCRIBE DB_INSTRUMENT_DIRECTORY_INFO"> |
| 7016 |
|
<t>Client may want to be notified when changes were made to directories |
| 7017 |
|
in the instruments database by issuing the following command:</t> |
| 7018 |
|
<t> |
| 7019 |
|
<list> |
| 7020 |
|
<t>SUBSCRIBE DB_INSTRUMENT_DIRECTORY_INFO</t> |
| 7021 |
|
</list> |
| 7022 |
|
</t> |
| 7023 |
|
<t>Server will start sending the following notification messages:</t> |
| 7024 |
|
<t> |
| 7025 |
|
<list> |
| 7026 |
|
<t>"NOTIFY:DB_INSTRUMENT_DIRECTORY_INFO:<dir-path>"</t> |
| 7027 |
|
</list> |
| 7028 |
|
</t> |
| 7029 |
|
<t>where <dir-path> will be replaced by the absolute path name |
| 7030 |
|
of the directory, for which information changes occurred. The front-end will have to send |
| 7031 |
|
the respective command to actually get the updated directory info. Because these messages |
| 7032 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 7033 |
|
time events happening on the server, it is believed that an empty notification |
| 7034 |
|
message is sufficient here.</t> |
| 7035 |
|
<t> |
| 7036 |
|
<list> |
| 7037 |
|
<t>"NOTIFY:DB_INSTRUMENT_DIRECTORY_INFO:NAME <old-dir-path> <new-name>"</t> |
| 7038 |
|
</list> |
| 7039 |
|
</t> |
| 7040 |
|
<t>where <old-dir-path> is the old absolute path name of the directory |
| 7041 |
|
(encapsulated into apostrophes), which name is changes and <new-name> is |
| 7042 |
|
the new name of the directory, encapsulated into apostrophes.</t> |
| 7043 |
|
</section> |
| 7044 |
|
|
| 7045 |
|
<section title="Number of database instruments changed" anchor="SUBSCRIBE DB_INSTRUMENT_COUNT"> |
| 7046 |
|
<t>Client may want to be notified when the number of instruments |
| 7047 |
|
in a particular directory in the instruments database |
| 7048 |
|
is changed by issuing the following command:</t> |
| 7049 |
|
<t> |
| 7050 |
|
<list> |
| 7051 |
|
<t>SUBSCRIBE DB_INSTRUMENT_COUNT</t> |
| 7052 |
|
</list> |
| 7053 |
|
</t> |
| 7054 |
|
<t>Server will start sending the following notification messages:</t> |
| 7055 |
|
<t> |
| 7056 |
|
<list> |
| 7057 |
|
<t>"NOTIFY:DB_INSTRUMENT_COUNT:<dir-path>"</t> |
| 7058 |
|
</list> |
| 7059 |
|
</t> |
| 7060 |
|
<t>where <dir-path> will be replaced by the absolute path |
| 7061 |
|
name of the directory in the instruments database, |
| 7062 |
|
in which the number of instruments is changed.</t> |
| 7063 |
|
<t>Note that when a non-empty directory is removed, this event |
| 7064 |
|
is not sent for the instruments in that directory.</t> |
| 7065 |
|
</section> |
| 7066 |
|
|
| 7067 |
|
<section title="Database instrument information changed" anchor="SUBSCRIBE DB_INSTRUMENT_INFO"> |
| 7068 |
|
<t>Client may want to be notified when changes were made to instruments |
| 7069 |
|
in the instruments database by issuing the following command:</t> |
| 7070 |
|
<t> |
| 7071 |
|
<list> |
| 7072 |
|
<t>SUBSCRIBE DB_INSTRUMENT_INFO</t> |
| 7073 |
|
</list> |
| 7074 |
|
</t> |
| 7075 |
|
<t>Server will start sending the following notification messages:</t> |
| 7076 |
|
<t> |
| 7077 |
|
<list> |
| 7078 |
|
<t>"NOTIFY:DB_INSTRUMENT_INFO:<instr-path>"</t> |
| 7079 |
|
</list> |
| 7080 |
|
</t> |
| 7081 |
|
<t>where <instr-path> will be replaced by the absolute path name |
| 7082 |
|
of the instrument, which settings are changed. The front-end will have to send |
| 7083 |
|
the respective command to actually get the updated directory info. Because these messages |
| 7084 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 7085 |
|
time events happening on the server, it is believed that an empty notification |
| 7086 |
|
message is sufficient here.</t> |
| 7087 |
|
<t> |
| 7088 |
|
<list> |
| 7089 |
|
<t>"NOTIFY:DB_INSTRUMENT_INFO:NAME <old-instr-path> <new-name>"</t> |
| 7090 |
|
</list> |
| 7091 |
|
</t> |
| 7092 |
|
<t>where <old-instr-path> is the old absolute path name of the instrument |
| 7093 |
|
(encapsulated into apostrophes), which name is changes and <new-name> is |
| 7094 |
|
the new name of the instrument, encapsulated into apostrophes.</t> |
| 7095 |
|
</section> |
| 7096 |
|
|
| 7097 |
|
<section title="Database job status information changed" anchor="SUBSCRIBE DB_INSTRUMENTS_JOB_INFO"> |
| 7098 |
|
<t>Client may want to be notified when the status of particular database |
| 7099 |
|
instruments job is changed by issuing the following command:</t> |
| 7100 |
|
<t> |
| 7101 |
|
<list> |
| 7102 |
|
<t>SUBSCRIBE DB_INSTRUMENTS_JOB_INFO</t> |
| 7103 |
|
</list> |
| 7104 |
|
</t> |
| 7105 |
|
<t>Server will start sending the following notification messages:</t> |
| 7106 |
|
<t> |
| 7107 |
|
<list> |
| 7108 |
|
<t>"NOTIFY:DB_INSTRUMENTS_JOB_INFO:<job-id>"</t> |
| 7109 |
|
</list> |
| 7110 |
|
</t> |
| 7111 |
|
<t>where <job-id> will be replaced by the numerical ID of the job, |
| 7112 |
|
which status is changed. The front-end will have to send the respective |
| 7113 |
|
command to actually get the status info. Because these messages |
| 7114 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 7115 |
|
time events happening on the server, it is believed that an empty notification |
| 7116 |
|
message is sufficient here.</t> |
| 7117 |
|
</section> |
| 7118 |
|
|
| 7119 |
|
<section title="Miscellaneous and debugging events" anchor="SUBSCRIBE MISCELLANEOUS"> |
| 7120 |
<t>Client may want to be notified of miscellaneous and debugging events occurring at |
<t>Client may want to be notified of miscellaneous and debugging events occurring at |
| 7121 |
the server by issuing the following command:</t> |
the server by issuing the following command:</t> |
| 7122 |
<t> |
<t> |
| 7152 |
<t>Rui Nuno Capela</t> |
<t>Rui Nuno Capela</t> |
| 7153 |
<t>Vladimir Senkov</t> |
<t>Vladimir Senkov</t> |
| 7154 |
<t>Mark Knecht</t> |
<t>Mark Knecht</t> |
| 7155 |
|
<t>Grigor Iliev</t> |
| 7156 |
</list> |
</list> |
| 7157 |
</t> |
</t> |
| 7158 |
</section> |
</section> |
| 7160 |
</middle> |
</middle> |
| 7161 |
|
|
| 7162 |
<back> |
<back> |
| 7163 |
<references>&rfc2119;</references> |
<references> |
| 7164 |
|
<reference anchor="RFC2119"> |
| 7165 |
|
<front> |
| 7166 |
|
<title>Key words for use in RFCs to Indicate Requirement Levels</title> |
| 7167 |
|
<author initials="S." surname="Bradner" fullname="Scott Bradner"> |
| 7168 |
|
<organization>Harvard University</organization> |
| 7169 |
|
</author> |
| 7170 |
|
<date year="1997"></date> |
| 7171 |
|
</front> |
| 7172 |
|
<seriesInfo name="RFC" value="2119" /> |
| 7173 |
|
</reference> |
| 7174 |
|
<reference anchor="RFC793"> |
| 7175 |
|
<front> |
| 7176 |
|
<title>TRANSMISSION CONTROL PROTOCOL</title> |
| 7177 |
|
<author> |
| 7178 |
|
<organization>Defense Advanced Research Projects Agency</organization> |
| 7179 |
|
</author> |
| 7180 |
|
<date year="1981"></date> |
| 7181 |
|
</front> |
| 7182 |
|
<seriesInfo name="RFC" value="793" /> |
| 7183 |
|
</reference> |
| 7184 |
|
<reference anchor="RFC2234"> |
| 7185 |
|
<front> |
| 7186 |
|
<title>Augmented BNF for Syntax Specifications</title> |
| 7187 |
|
<author initials="D.H." surname="Crocker" fullname="David H. Crocker"> |
| 7188 |
|
<organization>Internet Mail Consortium</organization> |
| 7189 |
|
</author> |
| 7190 |
|
<author initials="P." surname="Overell" fullname="Paul Overell"> |
| 7191 |
|
<organization>Demon Internet Ltd</organization> |
| 7192 |
|
</author> |
| 7193 |
|
<date year="1997"></date> |
| 7194 |
|
</front> |
| 7195 |
|
<seriesInfo name="RFC" value="2234" /> |
| 7196 |
|
</reference> |
| 7197 |
|
<reference anchor="RFC20"> |
| 7198 |
|
<front> |
| 7199 |
|
<title>ASCII format for Network Interchange</title> |
| 7200 |
|
<author> |
| 7201 |
|
<organization>UCLA</organization> |
| 7202 |
|
</author> |
| 7203 |
|
<date year="1969"></date> |
| 7204 |
|
</front> |
| 7205 |
|
<seriesInfo name="RFC" value="20" /> |
| 7206 |
|
</reference> |
| 7207 |
|
</references> |
| 7208 |
</back> |
</back> |
| 7209 |
|
|
| 7210 |
</rfc> |
</rfc> |
Parent Directory
| 
Revision Log
| 
Patch