| 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.2"> |
| 20 |
<front> |
<front> |
| 21 |
<title>LinuxSampler Control Protocol</title> |
<title>LinuxSampler Control Protocol</title> |
| 22 |
<author initials='C.S.' surname="Schoenebeck" fullname='C. |
<author initials='C.S.' surname="Schoenebeck" fullname='C. |
| 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="Apr" year="2005"/> |
<date month="December" year="2006"/> |
| 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 |
|
|
| 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> |
| 2117 |
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 |
| 2118 |
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 |
| 2119 |
returns immediately and a background process is launched to load the instrument |
returns immediately and a background process is launched to load the instrument |
| 2120 |
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> |
| 2121 |
|
command can be used to obtain loading |
| 2122 |
progress from INSTRUMENT_STATUS field. LOAD command will perform sanity checks |
progress from INSTRUMENT_STATUS field. LOAD command will perform sanity checks |
| 2123 |
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 |
| 2124 |
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 |
| 2156 |
</t> |
</t> |
| 2157 |
</section> |
</section> |
| 2158 |
|
|
| 2159 |
<section title="Loading a sampler engine"> |
<section title="Loading a sampler engine" anchor="LOAD ENGINE"> |
| 2160 |
<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 |
| 2161 |
channel by the following command:</t> |
channel by the following command:</t> |
| 2162 |
<t> |
<t> |
| 2163 |
<list> |
<list> |
| 2166 |
</t> |
</t> |
| 2167 |
|
|
| 2168 |
<t>Where <engine-name> is an engine name as obtained by the |
<t>Where <engine-name> is an engine name as obtained by the |
| 2169 |
"GET AVAILABLE_ENGINES" command and <sampler-channel> the sampler channel the |
<xref target="LIST AVAILABLE_ENGINES"> |
| 2170 |
deployed engine should be assigned to. Even if the respective |
"LIST AVAILABLE_ENGINES"</xref> command and <sampler-channel> |
| 2171 |
sampler channel has already a deployed engine with that engine |
the sampler channel as returned by the |
| 2172 |
name, a new engine instance will be assigned to the sampler channel.</t> |
<xref target="ADD CHANNEL">"ADD CHANNEL"</xref> or |
| 2173 |
|
<xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command where |
| 2174 |
|
the engine type should be assigned to. This command should be issued |
| 2175 |
|
after adding a new sampler channel and before any other control |
| 2176 |
|
commands on the new sampler channel. It can also be used to change |
| 2177 |
|
the engine type of a sampler channel. This command has (currently) no |
| 2178 |
|
way to define or force if a new engine instance should be created and |
| 2179 |
|
assigned to the given sampler channel or if an already existing |
| 2180 |
|
instance of that engine type, shared with other sampler channels, |
| 2181 |
|
should be used.</t> |
| 2182 |
|
|
| 2183 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2184 |
<t> |
<t> |
| 2211 |
</t> |
</t> |
| 2212 |
</section> |
</section> |
| 2213 |
|
|
| 2214 |
<section title="Getting all created sampler channel count"> |
<section title="Getting all created sampler channel count" anchor="GET CHANNELS"> |
| 2215 |
<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 |
| 2216 |
current amount of sampler channels, the front-end can send the |
current amount of sampler channels, the front-end can send the |
| 2217 |
following command:</t> |
following command:</t> |
| 2235 |
</t> |
</t> |
| 2236 |
</section> |
</section> |
| 2237 |
|
|
| 2238 |
<section title="Getting all created sampler channel list"> |
<section title="Getting all created sampler channel list" anchor="LIST CHANNELS"> |
| 2239 |
<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 |
| 2240 |
current list of sampler channels, the front-end can send the |
current list of sampler channels, the front-end can send the |
| 2241 |
following command:</t> |
following command:</t> |
| 2260 |
</t> |
</t> |
| 2261 |
</section> |
</section> |
| 2262 |
|
|
| 2263 |
<section title="Adding a new sampler channel"> |
<section title="Adding a new sampler channel" anchor="ADD CHANNEL"> |
| 2264 |
<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 |
| 2265 |
channel list by sending the following command:</t> |
channel list by sending the following command:</t> |
| 2266 |
<t> |
<t> |
| 2284 |
<list> |
<list> |
| 2285 |
<t>in case a new sampler channel could be added, where |
<t>in case a new sampler channel could be added, where |
| 2286 |
<sampler-channel> reflects the channel number of the new |
<sampler-channel> reflects the channel number of the new |
| 2287 |
created sampler channel which should the be used to set up |
created sampler channel which should be used to set up |
| 2288 |
the sampler channel by sending subsequent intialization |
the sampler channel by sending subsequent initialization |
| 2289 |
commands</t> |
commands</t> |
| 2290 |
</list> |
</list> |
| 2291 |
</t> |
</t> |
| 2312 |
</t> |
</t> |
| 2313 |
</section> |
</section> |
| 2314 |
|
|
| 2315 |
<section title="Removing a sampler channel"> |
<section title="Removing a sampler channel" anchor="REMOVE CHANNEL"> |
| 2316 |
<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> |
| 2317 |
<t> |
<t> |
| 2318 |
<list> |
<list> |
| 2320 |
</list> |
</list> |
| 2321 |
</t> |
</t> |
| 2322 |
|
|
| 2323 |
<t>This will decrement the sampler channel count by one and also |
<t>Where <sampler-channel> should be replaced by the |
| 2324 |
decrement the channel numbers of all subsequent sampler channels by |
number of the sampler channel as given by the |
| 2325 |
one.</t> |
<xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2326 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> |
| 2327 |
|
command. The channel numbers of all subsequent sampler channels |
| 2328 |
|
remain the same.</t> |
| 2329 |
|
|
| 2330 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2331 |
<t> |
<t> |
| 2358 |
</t> |
</t> |
| 2359 |
</section> |
</section> |
| 2360 |
|
|
| 2361 |
<section title="Getting all available engines"> |
<section title="Getting amount of available engines" anchor="GET AVAILABLE_ENGINES"> |
| 2362 |
<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> |
| 2363 |
<t> |
<t> |
| 2364 |
<list> |
<list> |
| 2365 |
<t>GET AVAILABLE_ENGINES</t> |
<t>GET AVAILABLE_ENGINES</t> |
| 2368 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2369 |
<t> |
<t> |
| 2370 |
<list> |
<list> |
| 2371 |
<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> |
|
| 2372 |
</list> |
</list> |
| 2373 |
</t> |
</t> |
| 2374 |
<t>Example:</t> |
<t>Example:</t> |
| 2375 |
<t> |
<t> |
| 2376 |
<list> |
<list> |
| 2377 |
<t>C: "GET AVAILABLE_ENGINES"</t> |
<t>C: "GET AVAILABLE_ENGINES"</t> |
| 2378 |
<t>S: "GigEngine,AkaiEngine,DLSEngine,JoesCustomEngine"</t> |
<t>S: "4"</t> |
| 2379 |
</list> |
</list> |
| 2380 |
</t> |
</t> |
| 2381 |
</section> |
</section> |
| 2382 |
|
|
| 2383 |
<section title="Getting information about an engine"> |
<section title="Getting all available engines" anchor="LIST AVAILABLE_ENGINES"> |
| 2384 |
|
<t>The front-end can ask for a list of all available engines by sending the following command:</t> |
| 2385 |
|
<t> |
| 2386 |
|
<list> |
| 2387 |
|
<t>LIST AVAILABLE_ENGINES</t> |
| 2388 |
|
</list> |
| 2389 |
|
</t> |
| 2390 |
|
<t>Possible Answers:</t> |
| 2391 |
|
<t> |
| 2392 |
|
<list> |
| 2393 |
|
<t>LinuxSampler will answer by sending a comma separated list |
| 2394 |
|
of the engines' names encapsulated into apostrophes ('). |
| 2395 |
|
Engine names can consist of lower and upper cases, |
| 2396 |
|
digits and underlines ("_" character).</t> |
| 2397 |
|
</list> |
| 2398 |
|
</t> |
| 2399 |
|
<t>Example:</t> |
| 2400 |
|
<t> |
| 2401 |
|
<list> |
| 2402 |
|
<t>C: "LIST AVAILABLE_ENGINES"</t> |
| 2403 |
|
<t>S: "'GigEngine','AkaiEngine','DLSEngine','JoesCustomEngine'"</t> |
| 2404 |
|
</list> |
| 2405 |
|
</t> |
| 2406 |
|
</section> |
| 2407 |
|
|
| 2408 |
|
<section title="Getting information about an engine" anchor="GET ENGINE INFO"> |
| 2409 |
<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 |
| 2410 |
sending the following command:</t> |
sending the following command:</t> |
| 2411 |
<t> |
<t> |
| 2414 |
</list> |
</list> |
| 2415 |
</t> |
</t> |
| 2416 |
<t>Where <engine-name> is an engine name as obtained by the |
<t>Where <engine-name> is an engine name as obtained by the |
| 2417 |
"GET AVAILABLE_ENGINES" command.</t> |
<xref target="LIST AVAILABLE_ENGINES"> |
| 2418 |
|
"LIST AVAILABLE_ENGINES"</xref> command.</t> |
| 2419 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2420 |
<t> |
<t> |
| 2421 |
<list> |
<list> |
| 2455 |
</t> |
</t> |
| 2456 |
</section> |
</section> |
| 2457 |
|
|
| 2458 |
<section title="Getting sampler channel information"> |
<section title="Getting sampler channel information" anchor="GET CHANNEL INFO"> |
| 2459 |
<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 |
| 2460 |
by sending the following command:</t> |
by sending the following command:</t> |
| 2461 |
<t> |
<t> |
| 2463 |
<t>GET CHANNEL INFO <sampler-channel></t> |
<t>GET CHANNEL INFO <sampler-channel></t> |
| 2464 |
</list> |
</list> |
| 2465 |
</t> |
</t> |
| 2466 |
<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 |
| 2467 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2468 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 2469 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2470 |
<t> |
<t> |
| 2471 |
<list> |
<list> |
| 2479 |
<list> |
<list> |
| 2480 |
<t>ENGINE_NAME - |
<t>ENGINE_NAME - |
| 2481 |
<list> |
<list> |
| 2482 |
<t>name of the engine that is deployed on the sampler |
<t>name of the engine that is associated with the sampler |
| 2483 |
channel, "NONE" if there's no engine deployed yet for |
channel, "NONE" if there's no engine associated yet for |
| 2484 |
this sampler channel</t> |
this sampler channel</t> |
| 2485 |
</list> |
</list> |
| 2486 |
</t> |
</t> |
| 2559 |
1.0 means amplification)</t> |
1.0 means amplification)</t> |
| 2560 |
</list> |
</list> |
| 2561 |
</t> |
</t> |
| 2562 |
|
<t>MUTE - |
| 2563 |
|
<list> |
| 2564 |
|
<t>Determines whether the channel is muted, "true" if the |
| 2565 |
|
channel is muted, "false" if the channel is not muted, and |
| 2566 |
|
"MUTED_BY_SOLO" if the channel is muted because of the |
| 2567 |
|
presence of a solo channel and will be unmuted when |
| 2568 |
|
there are no solo channels left</t> |
| 2569 |
|
</list> |
| 2570 |
|
</t> |
| 2571 |
|
<t>SOLO - |
| 2572 |
|
<list> |
| 2573 |
|
<t>Determines whether this is a solo channel, "true" if |
| 2574 |
|
the channel is a solo channel; "false" otherwise</t> |
| 2575 |
|
</list> |
| 2576 |
|
</t> |
| 2577 |
|
<t>MIDI_INSTRUMENT_MAP - |
| 2578 |
|
<list> |
| 2579 |
|
<t>Determines to which MIDI instrument map this sampler |
| 2580 |
|
channel is assigned to. Read chapter |
| 2581 |
|
<xref target="SET CHANNEL MIDI_INSTRUMENT_MAP">"SET CHANNEL MIDI_INSTRUMENT_MAP"</xref> |
| 2582 |
|
for a list of possible values.</t> |
| 2583 |
|
</list> |
| 2584 |
|
</t> |
| 2585 |
</list> |
</list> |
| 2586 |
</t> |
</t> |
| 2587 |
</list> |
</list> |
| 2604 |
<t> "MIDI_INPUT_DEVICE: 0"</t> |
<t> "MIDI_INPUT_DEVICE: 0"</t> |
| 2605 |
<t> "MIDI_INPUT_PORT: 0"</t> |
<t> "MIDI_INPUT_PORT: 0"</t> |
| 2606 |
<t> "MIDI_INPUT_CHANNEL: 5"</t> |
<t> "MIDI_INPUT_CHANNEL: 5"</t> |
| 2607 |
|
<t> "VOLUME: 1.0"</t> |
| 2608 |
|
<t> "MUTE: false"</t> |
| 2609 |
|
<t> "SOLO: false"</t> |
| 2610 |
|
<t> "MIDI_INSTRUMENT_MAP: NONE"</t> |
| 2611 |
<t> "."</t> |
<t> "."</t> |
| 2612 |
</list> |
</list> |
| 2613 |
</t> |
</t> |
| 2614 |
</section> |
</section> |
| 2615 |
|
|
| 2616 |
<section title="Current number of active voices"> |
<section title="Current number of active voices" anchor="GET CHANNEL VOICE_COUNT"> |
| 2617 |
<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 |
| 2618 |
sampler channel by sending the following command:</t> |
sampler channel by sending the following command:</t> |
| 2619 |
<t> |
<t> |
| 2621 |
<t>GET CHANNEL VOICE_COUNT <sampler-channel></t> |
<t>GET CHANNEL VOICE_COUNT <sampler-channel></t> |
| 2622 |
</list> |
</list> |
| 2623 |
</t> |
</t> |
| 2624 |
<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 |
| 2625 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2626 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 2627 |
|
|
| 2628 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2629 |
<t> |
<t> |
| 2640 |
</t> |
</t> |
| 2641 |
</section> |
</section> |
| 2642 |
|
|
| 2643 |
<section title="Current number of active disk streams"> |
<section title="Current number of active disk streams" anchor="GET CHANNEL STREAM_COUNT"> |
| 2644 |
<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 |
| 2645 |
on a sampler channel by sending the following command:</t> |
on a sampler channel by sending the following command:</t> |
| 2646 |
<t> |
<t> |
| 2648 |
<t>GET CHANNEL STREAM_COUNT <sampler-channel></t> |
<t>GET CHANNEL STREAM_COUNT <sampler-channel></t> |
| 2649 |
</list> |
</list> |
| 2650 |
</t> |
</t> |
| 2651 |
<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 |
| 2652 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2653 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 2654 |
|
|
| 2655 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2656 |
<t> |
<t> |
| 2669 |
</t> |
</t> |
| 2670 |
</section> |
</section> |
| 2671 |
|
|
| 2672 |
<section title="Current fill state of disk stream buffers"> |
<section title="Current fill state of disk stream buffers" anchor="GET CHANNEL BUFFER_FILL"> |
| 2673 |
<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 |
| 2674 |
on a sampler channel by sending the following command:</t> |
on a sampler channel by sending the following command:</t> |
| 2675 |
<t> |
<t> |
| 2684 |
</list> |
</list> |
| 2685 |
</t> |
</t> |
| 2686 |
<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 |
| 2687 |
sampler channel number the front-end is interested in.</t> |
sampler channel number the front-end is interested in |
| 2688 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2689 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 2690 |
|
|
| 2691 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2692 |
<t> |
<t> |
| 2722 |
</t> |
</t> |
| 2723 |
</section> |
</section> |
| 2724 |
|
|
| 2725 |
<section title="Setting audio output device"> |
<section title="Setting audio output device" anchor="SET CHANNEL AUDIO_OUTPUT_DEVICE"> |
| 2726 |
<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 |
| 2727 |
channel by sending the following command:</t> |
channel by sending the following command:</t> |
| 2728 |
<t> |
<t> |
| 2730 |
<t>SET CHANNEL AUDIO_OUTPUT_DEVICE <sampler-channel> <audio-device-id></t> |
<t>SET CHANNEL AUDIO_OUTPUT_DEVICE <sampler-channel> <audio-device-id></t> |
| 2731 |
</list> |
</list> |
| 2732 |
</t> |
</t> |
| 2733 |
<t>Where <audio-device-id> is the numerical ID of the audio output |
<t>Where <sampler-channel> is the respective sampler channel |
| 2734 |
device and <sampler-channel> is the respective sampler channel |
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2735 |
number.</t> |
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and |
| 2736 |
|
<audio-device-id> is the numerical ID of the audio output device as given by the |
| 2737 |
|
<xref target="CREATE AUDIO_OUTPUT_DEVICE">"CREATE AUDIO_OUTPUT_DEVICE"</xref> |
| 2738 |
|
or <xref target="LIST AUDIO_OUTPUT_DEVICES">"LIST AUDIO_OUTPUT_DEVICES"</xref> |
| 2739 |
|
command.</t> |
| 2740 |
|
|
| 2741 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2742 |
<t> |
<t> |
| 2768 |
</t> |
</t> |
| 2769 |
</section> |
</section> |
| 2770 |
|
|
| 2771 |
<section title="Setting audio output type"> |
<section title="Setting audio output type" anchor="SET CHANNEL AUDIO_OUTPUT_TYPE"> |
| 2772 |
<t>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!</t> |
<t>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!</t> |
| 2773 |
|
|
| 2774 |
<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 |
| 2811 |
</t> |
</t> |
| 2812 |
</section> |
</section> |
| 2813 |
|
|
| 2814 |
<section title="Setting audio output channel"> |
<section title="Setting audio output channel" anchor="SET CHANNEL AUDIO_OUTPUT_CHANNEL"> |
| 2815 |
<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 |
| 2816 |
sampler channel by sending the following command:</t> |
sampler channel by sending the following command:</t> |
| 2817 |
<t> |
<t> |
| 2819 |
<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> |
| 2820 |
</list> |
</list> |
| 2821 |
</t> |
</t> |
| 2822 |
<t>Where <sampler-chan> is the sampler channel, <audio-out> is the |
<t>Where <sampler-chan> is the sampler channel number |
| 2823 |
sampler channel's audio output channel which should be |
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2824 |
rerouted and <audio-in> the audio channel of the selected audio |
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, <audio-out> is the |
| 2825 |
|
numerical ID of the sampler channel's audio output channel which should be |
| 2826 |
|
rerouted and <audio-in> is the numerical ID of the audio channel of the selected audio |
| 2827 |
output device where <audio-out> should be routed to.</t> |
output device where <audio-out> should be routed to.</t> |
| 2828 |
|
|
| 2829 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2856 |
</t> |
</t> |
| 2857 |
</section> |
</section> |
| 2858 |
|
|
| 2859 |
<section title="Setting MIDI input device"> |
<section title="Setting MIDI input device" anchor="SET CHANNEL MIDI_INPUT_DEVICE"> |
| 2860 |
<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 |
| 2861 |
channel by sending the following command:</t> |
channel by sending the following command:</t> |
| 2862 |
<t> |
<t> |
| 2864 |
<t>SET CHANNEL MIDI_INPUT_DEVICE <sampler-channel> <midi-device-id></t> |
<t>SET CHANNEL MIDI_INPUT_DEVICE <sampler-channel> <midi-device-id></t> |
| 2865 |
</list> |
</list> |
| 2866 |
</t> |
</t> |
| 2867 |
<t></t> |
<t>Where <sampler-channel> is the sampler channel number |
| 2868 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 2869 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command |
| 2870 |
|
and <midi-device-id> is the numerical ID of the MIDI input device as returned by the |
| 2871 |
|
<xref target="CREATE MIDI_INPUT_DEVICE">"CREATE MIDI_INPUT_DEVICE"</xref> |
| 2872 |
|
or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref> command.</t> |
| 2873 |
|
|
| 2874 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2875 |
<t> |
<t> |
| 2901 |
</t> |
</t> |
| 2902 |
</section> |
</section> |
| 2903 |
|
|
| 2904 |
<section title="Setting MIDI input type"> |
<section title="Setting MIDI input type" anchor="SET CHANNEL MIDI_INPUT_TYPE"> |
| 2905 |
<t>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!</t> |
<t>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!</t> |
| 2906 |
|
|
| 2907 |
<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 |
| 2944 |
</t> |
</t> |
| 2945 |
</section> |
</section> |
| 2946 |
|
|
| 2947 |
<section title="Setting MIDI input port"> |
<section title="Setting MIDI input port" anchor="SET CHANNEL MIDI_INPUT_PORT"> |
| 2948 |
<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 |
| 2949 |
channel by sending the following command:</t> |
channel by sending the following command:</t> |
| 2950 |
<t> |
<t> |
| 2951 |
<list> |
<list> |
| 2973 |
</t> |
</t> |
| 2974 |
<t>"ERR:<error-code>:<error-message>" - |
<t>"ERR:<error-code>:<error-message>" - |
| 2975 |
<list> |
<list> |
| 2976 |
<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> |
| 2977 |
</list> |
</list> |
| 2978 |
</t> |
</t> |
| 2979 |
</list> |
</list> |
| 2986 |
</t> |
</t> |
| 2987 |
</section> |
</section> |
| 2988 |
|
|
| 2989 |
<section title="Setting MIDI input channel"> |
<section title="Setting MIDI input channel" anchor="SET CHANNEL MIDI_INPUT_CHANNEL"> |
| 2990 |
<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 |
| 2991 |
listen to by sending the following command:</t> |
listen to by sending the following command:</t> |
| 2992 |
<t> |
<t> |
| 2994 |
<t>SET CHANNEL MIDI_INPUT_CHANNEL <sampler-channel> <midi-input-chan></t> |
<t>SET CHANNEL MIDI_INPUT_CHANNEL <sampler-channel> <midi-input-chan></t> |
| 2995 |
</list> |
</list> |
| 2996 |
</t> |
</t> |
| 2997 |
<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 |
| 2998 |
<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 |
| 2999 |
channels.</t> |
channels.</t> |
| 3000 |
|
|
| 3028 |
</t> |
</t> |
| 3029 |
</section> |
</section> |
| 3030 |
|
|
| 3031 |
<section title="Setting channel volume"> |
<section title="Setting channel volume" anchor="SET CHANNEL VOLUME"> |
| 3032 |
<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 |
| 3033 |
the following command:</t> |
the following command:</t> |
| 3034 |
<t> |
<t> |
| 3071 |
</t> |
</t> |
| 3072 |
</section> |
</section> |
| 3073 |
|
|
| 3074 |
<section title="Resetting a sampler channel"> |
<section title="Muting a sampler channel" anchor="SET CHANNEL MUTE"> |
| 3075 |
|
<t>The front-end can mute/unmute a specific sampler |
| 3076 |
|
channel by sending the following command:</t> |
| 3077 |
|
<t> |
| 3078 |
|
<list> |
| 3079 |
|
<t>SET CHANNEL MUTE <sampler-channel> <mute></t> |
| 3080 |
|
</list> |
| 3081 |
|
</t> |
| 3082 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3083 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3084 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and |
| 3085 |
|
<mute> should be replaced either by "1" to mute the channel or "0" |
| 3086 |
|
to unmute the channel.</t> |
| 3087 |
|
|
| 3088 |
|
<t>Possible Answers:</t> |
| 3089 |
|
<t> |
| 3090 |
|
<list> |
| 3091 |
|
<t>"OK" - |
| 3092 |
|
<list> |
| 3093 |
|
<t>on success</t> |
| 3094 |
|
</list> |
| 3095 |
|
</t> |
| 3096 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 3097 |
|
<list> |
| 3098 |
|
<t>if the channel was muted/unmuted, but there are noteworthy |
| 3099 |
|
issue(s) related, providing an appropriate warning code and |
| 3100 |
|
warning message</t> |
| 3101 |
|
</list> |
| 3102 |
|
</t> |
| 3103 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3104 |
|
<list> |
| 3105 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3106 |
|
</list> |
| 3107 |
|
</t> |
| 3108 |
|
</list> |
| 3109 |
|
</t> |
| 3110 |
|
<t>Examples:</t> |
| 3111 |
|
<t> |
| 3112 |
|
<list> |
| 3113 |
|
<t></t> |
| 3114 |
|
</list> |
| 3115 |
|
</t> |
| 3116 |
|
</section> |
| 3117 |
|
|
| 3118 |
|
<section title="Soloing a sampler channel" anchor="SET CHANNEL SOLO"> |
| 3119 |
|
<t>The front-end can solo/unsolo a specific sampler channel |
| 3120 |
|
by sending the following command:</t> |
| 3121 |
|
<t> |
| 3122 |
|
<list> |
| 3123 |
|
<t>SET CHANNEL SOLO <sampler-channel> <solo></t> |
| 3124 |
|
</list> |
| 3125 |
|
</t> |
| 3126 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3127 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3128 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and |
| 3129 |
|
<solo> should be replaced either by "1" to solo the channel or "0" |
| 3130 |
|
to unsolo the channel.</t> |
| 3131 |
|
|
| 3132 |
|
<t>Possible Answers:</t> |
| 3133 |
|
<t> |
| 3134 |
|
<list> |
| 3135 |
|
<t>"OK" - |
| 3136 |
|
<list> |
| 3137 |
|
<t>on success</t> |
| 3138 |
|
</list> |
| 3139 |
|
</t> |
| 3140 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 3141 |
|
<list> |
| 3142 |
|
<t>if the channel was soloed/unsoloed, but there are noteworthy |
| 3143 |
|
issue(s) related, providing an appropriate warning code and |
| 3144 |
|
warning message</t> |
| 3145 |
|
</list> |
| 3146 |
|
</t> |
| 3147 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3148 |
|
<list> |
| 3149 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3150 |
|
</list> |
| 3151 |
|
</t> |
| 3152 |
|
</list> |
| 3153 |
|
</t> |
| 3154 |
|
<t>Examples:</t> |
| 3155 |
|
<t> |
| 3156 |
|
<list> |
| 3157 |
|
<t></t> |
| 3158 |
|
</list> |
| 3159 |
|
</t> |
| 3160 |
|
</section> |
| 3161 |
|
|
| 3162 |
|
<section title="Assigning a MIDI instrument map to a sampler channel" anchor="SET CHANNEL MIDI_INSTRUMENT_MAP"> |
| 3163 |
|
<t>The front-end can assign a MIDI instrument map to a specific sampler channel |
| 3164 |
|
by sending the following command:</t> |
| 3165 |
|
<t> |
| 3166 |
|
<list> |
| 3167 |
|
<t>SET CHANNEL MIDI_INSTRUMENT_MAP <sampler-channel> <map></t> |
| 3168 |
|
</list> |
| 3169 |
|
</t> |
| 3170 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3171 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3172 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and |
| 3173 |
|
<map> can have the following possibilites:</t> |
| 3174 |
|
<t> |
| 3175 |
|
<list> |
| 3176 |
|
<t>"NONE" - |
| 3177 |
|
<list> |
| 3178 |
|
<t>This is the default setting. In this case |
| 3179 |
|
the sampler channel is not assigned any MIDI |
| 3180 |
|
instrument map and thus will ignore all MIDI |
| 3181 |
|
program change messages.</t> |
| 3182 |
|
</list> |
| 3183 |
|
</t> |
| 3184 |
|
<t>"DEFAULT" - |
| 3185 |
|
<list> |
| 3186 |
|
<t>The sampler channel will always use the |
| 3187 |
|
default MIDI instrument map to handle MIDI |
| 3188 |
|
program change messages.</t> |
| 3189 |
|
</list> |
| 3190 |
|
</t> |
| 3191 |
|
<t>numeric ID - |
| 3192 |
|
<list> |
| 3193 |
|
<t>You can assign a specific MIDI instrument map |
| 3194 |
|
by replacing <map> with the respective numeric |
| 3195 |
|
ID of the MIDI instrument map as returned by the |
| 3196 |
|
<xref target="LIST MIDI_INSTRUMENT_MAPS">"LIST MIDI_INSTRUMENT_MAPS"</xref> |
| 3197 |
|
command. Once that map will be deleted, the sampler |
| 3198 |
|
channel would fall back to "NONE".</t> |
| 3199 |
|
</list> |
| 3200 |
|
</t> |
| 3201 |
|
</list> |
| 3202 |
|
</t> |
| 3203 |
|
<t>Read chapter <xref target="MIDI Instrument Mapping">"MIDI Instrument Mapping"</xref> |
| 3204 |
|
for details regarding MIDI instrument mapping.</t> |
| 3205 |
|
|
| 3206 |
|
<t>Possible Answers:</t> |
| 3207 |
|
<t> |
| 3208 |
|
<list> |
| 3209 |
|
<t>"OK" - |
| 3210 |
|
<list> |
| 3211 |
|
<t>on success</t> |
| 3212 |
|
</list> |
| 3213 |
|
</t> |
| 3214 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3215 |
|
<list> |
| 3216 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3217 |
|
</list> |
| 3218 |
|
</t> |
| 3219 |
|
</list> |
| 3220 |
|
</t> |
| 3221 |
|
|
| 3222 |
|
<t>Examples:</t> |
| 3223 |
|
<t> |
| 3224 |
|
<list> |
| 3225 |
|
<t></t> |
| 3226 |
|
</list> |
| 3227 |
|
</t> |
| 3228 |
|
</section> |
| 3229 |
|
|
| 3230 |
|
<section title="Adding an effect send to a sampler channel" anchor="CREATE FX_SEND"> |
| 3231 |
|
<t>The front-end can create an additional effect send on a specific sampler channel |
| 3232 |
|
by sending the following command:</t> |
| 3233 |
|
<t> |
| 3234 |
|
<list> |
| 3235 |
|
<t>CREATE FX_SEND <sampler-channel> <midi-ctrl> [<name>]</t> |
| 3236 |
|
</list> |
| 3237 |
|
</t> |
| 3238 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3239 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3240 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, that is the |
| 3241 |
|
sampler channel on which the effect send should be created on, <midi-ctrl> |
| 3242 |
|
is a number between 0..127 defining the MIDI controller which can alter the |
| 3243 |
|
effect send level and <name> is an optional argument defining a name |
| 3244 |
|
for the effect send entity. The name does not have to be unique.</t> |
| 3245 |
|
|
| 3246 |
|
<t>By default, that is as initial routing, the effect send's audio channels |
| 3247 |
|
are automatically routed to the last audio channels of the sampler channel's |
| 3248 |
|
audio output device, that way you can i.e. first increase the amount of audio |
| 3249 |
|
channels on the audio output device for having dedicated effect send output |
| 3250 |
|
channels and when "CREATE FX_SEND" is called, those channels will automatically |
| 3251 |
|
be picked. You can alter the destination channels however with |
| 3252 |
|
<xref target="SET FX_SEND AUDIO_OUTPUT_CHANNEL">"SET FX_SEND AUDIO_OUTPUT_CHANNEL"</xref>. |
| 3253 |
|
</t> |
| 3254 |
|
|
| 3255 |
|
<t>Note: Create effect sends on a sampler channel only when needed, because having effect |
| 3256 |
|
sends on a sampler channel will decrease runtime performance, because for implementing channel |
| 3257 |
|
effect sends, separate (sampler channel local) audio buffers are needed to render and mix |
| 3258 |
|
the voices and route the audio signal afterwards to the master outputs and effect send |
| 3259 |
|
outputs (along with their respective effect send levels). A sampler channel without effect |
| 3260 |
|
sends however can mix its voices directly into the audio output devices's audio buffers |
| 3261 |
|
and is thus faster. |
| 3262 |
|
</t> |
| 3263 |
|
|
| 3264 |
|
<t>Possible Answers:</t> |
| 3265 |
|
<t> |
| 3266 |
|
<list> |
| 3267 |
|
<t>"OK[<fx-send-id>]" - |
| 3268 |
|
<list> |
| 3269 |
|
<t>in case a new effect send could be added to the |
| 3270 |
|
sampler channel, where <fx-send-id> reflects the |
| 3271 |
|
unique ID of the newly created effect send entity</t> |
| 3272 |
|
</list> |
| 3273 |
|
</t> |
| 3274 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3275 |
|
<list> |
| 3276 |
|
<t>when a new effect send could not be added, i.e. |
| 3277 |
|
due to invalid parameters</t> |
| 3278 |
|
</list> |
| 3279 |
|
</t> |
| 3280 |
|
</list> |
| 3281 |
|
</t> |
| 3282 |
|
|
| 3283 |
|
<t>Examples:</t> |
| 3284 |
|
<t> |
| 3285 |
|
<list> |
| 3286 |
|
<t>C: "CREATE FX_SEND 0 91 'Reverb Send'"</t> |
| 3287 |
|
<t>S: "OK[0]"</t> |
| 3288 |
|
</list> |
| 3289 |
|
</t> |
| 3290 |
|
<t> |
| 3291 |
|
<list> |
| 3292 |
|
<t>C: "CREATE FX_SEND 0 93"</t> |
| 3293 |
|
<t>S: "OK[1]"</t> |
| 3294 |
|
</list> |
| 3295 |
|
</t> |
| 3296 |
|
</section> |
| 3297 |
|
|
| 3298 |
|
<section title="Removing an effect send from a sampler channel" anchor="DESTROY FX_SEND"> |
| 3299 |
|
<t>The front-end can remove an existing effect send on a specific sampler channel |
| 3300 |
|
by sending the following command:</t> |
| 3301 |
|
<t> |
| 3302 |
|
<list> |
| 3303 |
|
<t>DESTROY FX_SEND <sampler-channel> <fx-send-id></t> |
| 3304 |
|
</list> |
| 3305 |
|
</t> |
| 3306 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3307 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3308 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, that is the |
| 3309 |
|
sampler channel from which the effect send should be removed from and |
| 3310 |
|
<fx-send-id> is the respective effect send number as returned by the |
| 3311 |
|
<xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3312 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command.</t> |
| 3313 |
|
|
| 3314 |
|
<t>Possible Answers:</t> |
| 3315 |
|
<t> |
| 3316 |
|
<list> |
| 3317 |
|
<t>"OK" - |
| 3318 |
|
<list> |
| 3319 |
|
<t>on success</t> |
| 3320 |
|
</list> |
| 3321 |
|
</t> |
| 3322 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3323 |
|
<list> |
| 3324 |
|
<t>in case it failed, providing an appropriate error code and |
| 3325 |
|
error message</t> |
| 3326 |
|
</list> |
| 3327 |
|
</t> |
| 3328 |
|
</list> |
| 3329 |
|
</t> |
| 3330 |
|
|
| 3331 |
|
<t>Example:</t> |
| 3332 |
|
<t> |
| 3333 |
|
<list> |
| 3334 |
|
<t>C: "DESTROY FX_SEND 0 0"</t> |
| 3335 |
|
<t>S: "OK"</t> |
| 3336 |
|
</list> |
| 3337 |
|
</t> |
| 3338 |
|
</section> |
| 3339 |
|
|
| 3340 |
|
<section title="Getting amount of effect sends on a sampler channel" anchor="GET FX_SENDS"> |
| 3341 |
|
<t>The front-end can ask for the amount of effect sends on a specific sampler channel |
| 3342 |
|
by sending the following command:</t> |
| 3343 |
|
<t> |
| 3344 |
|
<list> |
| 3345 |
|
<t>GET FX_SENDS <sampler-channel></t> |
| 3346 |
|
</list> |
| 3347 |
|
</t> |
| 3348 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3349 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3350 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 3351 |
|
|
| 3352 |
|
<t>Possible Answers:</t> |
| 3353 |
|
<t> |
| 3354 |
|
<list> |
| 3355 |
|
<t>The sampler will answer by returning the number of effect |
| 3356 |
|
sends on the given sampler channel.</t> |
| 3357 |
|
</list> |
| 3358 |
|
</t> |
| 3359 |
|
|
| 3360 |
|
<t>Example:</t> |
| 3361 |
|
<t> |
| 3362 |
|
<list> |
| 3363 |
|
<t>C: "GET FX_SENDS 0"</t> |
| 3364 |
|
<t>S: "2"</t> |
| 3365 |
|
</list> |
| 3366 |
|
</t> |
| 3367 |
|
</section> |
| 3368 |
|
|
| 3369 |
|
<section title="Listing all effect sends on a sampler channel" anchor="LIST FX_SENDS"> |
| 3370 |
|
<t>The front-end can ask for a list of effect sends on a specific sampler channel |
| 3371 |
|
by sending the following command:</t> |
| 3372 |
|
<t> |
| 3373 |
|
<list> |
| 3374 |
|
<t>LIST FX_SENDS <sampler-channel></t> |
| 3375 |
|
</list> |
| 3376 |
|
</t> |
| 3377 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3378 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3379 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 3380 |
|
|
| 3381 |
|
<t>Possible Answers:</t> |
| 3382 |
|
<t> |
| 3383 |
|
<list> |
| 3384 |
|
<t>The sampler will answer by returning a comma separated list |
| 3385 |
|
with all effect sends' numerical IDs on the given sampler |
| 3386 |
|
channel.</t> |
| 3387 |
|
</list> |
| 3388 |
|
</t> |
| 3389 |
|
|
| 3390 |
|
<t>Examples:</t> |
| 3391 |
|
<t> |
| 3392 |
|
<list> |
| 3393 |
|
<t>C: "LIST FX_SENDS 0"</t> |
| 3394 |
|
<t>S: "0,1"</t> |
| 3395 |
|
</list> |
| 3396 |
|
</t> |
| 3397 |
|
<t> |
| 3398 |
|
<list> |
| 3399 |
|
<t>C: "LIST FX_SENDS 1"</t> |
| 3400 |
|
<t>S: ""</t> |
| 3401 |
|
</list> |
| 3402 |
|
</t> |
| 3403 |
|
</section> |
| 3404 |
|
|
| 3405 |
|
<section title="Getting effect send information" anchor="GET FX_SEND INFO"> |
| 3406 |
|
<t>The front-end can ask for the current settings of an effect send entity |
| 3407 |
|
by sending the following command:</t> |
| 3408 |
|
<t> |
| 3409 |
|
<list> |
| 3410 |
|
<t>GET FX_SEND INFO <sampler-channel> <fx-send-id></t> |
| 3411 |
|
</list> |
| 3412 |
|
</t> |
| 3413 |
|
<t>Where <sampler-channel> is the sampler channel number |
| 3414 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3415 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and |
| 3416 |
|
<fx-send-id> reflects the numerical ID of the effect send entity |
| 3417 |
|
as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3418 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command. |
| 3419 |
|
</t> |
| 3420 |
|
|
| 3421 |
|
<t>Possible Answers:</t> |
| 3422 |
|
<t> |
| 3423 |
|
<list> |
| 3424 |
|
<t>The sampler will answer by sending a <CRLF> separated list. |
| 3425 |
|
Each answer line begins with the settings category name |
| 3426 |
|
followed by a colon and then a space character <SP> and finally |
| 3427 |
|
the info character string to that setting category. At the |
| 3428 |
|
moment the following categories are defined:</t> |
| 3429 |
|
|
| 3430 |
|
<t> |
| 3431 |
|
<list> |
| 3432 |
|
<t>NAME - |
| 3433 |
|
<list> |
| 3434 |
|
<t>name of the effect send entity</t> |
| 3435 |
|
</list> |
| 3436 |
|
</t> |
| 3437 |
|
<t>AUDIO_OUTPUT_ROUTING - |
| 3438 |
|
<list> |
| 3439 |
|
<t>comma separated list which reflects to which audio |
| 3440 |
|
channel of the selected audio output device each |
| 3441 |
|
effect send output channel is routed to, e.g. "0,3" would |
| 3442 |
|
mean the effect send's output channel 0 is routed to channel |
| 3443 |
|
0 of the audio output device and the effect send's output |
| 3444 |
|
channel 1 is routed to the channel 3 of the audio |
| 3445 |
|
output device (see |
| 3446 |
|
<xref target="SET FX_SEND AUDIO_OUTPUT_CHANNEL">"SET FX_SEND AUDIO_OUTPUT_CHANNEL"</xref> |
| 3447 |
|
for details)</t> |
| 3448 |
|
</list> |
| 3449 |
|
</t> |
| 3450 |
|
</list> |
| 3451 |
|
</t> |
| 3452 |
|
</list> |
| 3453 |
|
</t> |
| 3454 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 3455 |
|
|
| 3456 |
|
<t>Example:</t> |
| 3457 |
|
<t> |
| 3458 |
|
<list> |
| 3459 |
|
<t>C: "GET FX_SEND INFO 0 0"</t> |
| 3460 |
|
<t>S: "NAME: Reverb Send"</t> |
| 3461 |
|
<t> "AUDIO_OUTPUT_ROUTING: 2,3"</t> |
| 3462 |
|
<t> "."</t> |
| 3463 |
|
</list> |
| 3464 |
|
</t> |
| 3465 |
|
</section> |
| 3466 |
|
|
| 3467 |
|
<section title="Altering effect send's audio routing" anchor="SET FX_SEND AUDIO_OUTPUT_CHANNEL"> |
| 3468 |
|
<t>The front-end can alter the destination of an effect send's audio channel on a specific |
| 3469 |
|
sampler channel by sending the following command:</t> |
| 3470 |
|
<t> |
| 3471 |
|
<list> |
| 3472 |
|
<t>SET FX_SEND AUDIO_OUTPUT_CHANNEL <sampler-chan> <fx-send-id> <audio-src> <audio-dst></t> |
| 3473 |
|
</list> |
| 3474 |
|
</t> |
| 3475 |
|
<t>Where <sampler-chan> is the sampler channel number |
| 3476 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3477 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, |
| 3478 |
|
<fx-send-id> reflects the numerical ID of the effect send entity |
| 3479 |
|
as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3480 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command, |
| 3481 |
|
<audio-src> is the numerical ID of the effect send's audio channel |
| 3482 |
|
which should be rerouted and <audio-dst> is the numerical ID of |
| 3483 |
|
the audio channel of the selected audio output device where <audio-src> |
| 3484 |
|
should be routed to.</t> |
| 3485 |
|
|
| 3486 |
|
<t>Note that effect sends can only route audio to the same audio output |
| 3487 |
|
device as assigned to the effect send's sampler channel. Also note that an |
| 3488 |
|
effect send entity does always have exactly as much audio channels as its |
| 3489 |
|
sampler channel. So if the sampler channel is stereo, the effect send does |
| 3490 |
|
have two audio channels as well. Also keep in mind that the amount of audio |
| 3491 |
|
channels on a sampler channel might be dependant not only to the deployed |
| 3492 |
|
sampler engine on the sampler channel, but also dependant to the instrument |
| 3493 |
|
currently loaded. However you can (effectively) turn an i.e. stereo effect |
| 3494 |
|
send into a mono one by simply altering its audio routing appropriately.</t> |
| 3495 |
|
|
| 3496 |
|
<t>Possible Answers:</t> |
| 3497 |
|
<t> |
| 3498 |
|
<list> |
| 3499 |
|
<t>"OK" - |
| 3500 |
|
<list> |
| 3501 |
|
<t>on success</t> |
| 3502 |
|
</list> |
| 3503 |
|
</t> |
| 3504 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 3505 |
|
<list> |
| 3506 |
|
<t>if audio output channel was set, but there are noteworthy |
| 3507 |
|
issue(s) related, providing an appropriate warning code and |
| 3508 |
|
warning message</t> |
| 3509 |
|
</list> |
| 3510 |
|
</t> |
| 3511 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3512 |
|
<list> |
| 3513 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3514 |
|
</list> |
| 3515 |
|
</t> |
| 3516 |
|
</list> |
| 3517 |
|
</t> |
| 3518 |
|
<t>Example:</t> |
| 3519 |
|
<t> |
| 3520 |
|
<list> |
| 3521 |
|
<t>C: "SET FX_SEND AUDIO_OUTPUT_CHANNEL 0 0 0 2"</t> |
| 3522 |
|
<t>S: "OK"</t> |
| 3523 |
|
</list> |
| 3524 |
|
</t> |
| 3525 |
|
</section> |
| 3526 |
|
|
| 3527 |
|
|
| 3528 |
|
<section title="Resetting a sampler channel" anchor="RESET CHANNEL"> |
| 3529 |
<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> |
| 3530 |
<t> |
<t> |
| 3531 |
<list> |
<list> |
| 3573 |
<section title="Controlling connection"> |
<section title="Controlling connection"> |
| 3574 |
<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> |
| 3575 |
|
|
| 3576 |
<section title="Register front-end for receiving event messages"> |
<section title="Register front-end for receiving event messages" anchor="SUBSCRIBE"> |
| 3577 |
<t>The front-end can register itself to the LinuxSampler application to |
<t>The front-end can register itself to the LinuxSampler application to |
| 3578 |
be informed about noteworthy events by sending this command:</t> |
be informed about noteworthy events by sending this command:</t> |
| 3579 |
<t> |
<t> |
| 3615 |
</t> |
</t> |
| 3616 |
</section> |
</section> |
| 3617 |
|
|
| 3618 |
<section title="Unregister front-end for not receiving event messages"> |
<section title="Unregister front-end for not receiving event messages" anchor="UNSUBSCRIBE"> |
| 3619 |
<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 |
| 3620 |
messages anymore by sending the following command:</t> |
messages anymore by sending the following command:</t> |
| 3621 |
<t> |
<t> |
| 3657 |
</t> |
</t> |
| 3658 |
</section> |
</section> |
| 3659 |
|
|
| 3660 |
<section title="Enable or disable echo of commands"> |
<section title="Enable or disable echo of commands" anchor="SET ECHO"> |
| 3661 |
<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> |
| 3662 |
<t> |
<t> |
| 3663 |
<list> |
<list> |
| 3695 |
</t> |
</t> |
| 3696 |
</section> |
</section> |
| 3697 |
|
|
| 3698 |
<section title="Close client connection"> |
<section title="Close client connection" anchor="QUIT"> |
| 3699 |
<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> |
| 3700 |
<t> |
<t> |
| 3701 |
<list> |
<list> |
| 3710 |
<section title="Global commands"> |
<section title="Global commands"> |
| 3711 |
<t>The following commands have global impact on the sampler.</t> |
<t>The following commands have global impact on the sampler.</t> |
| 3712 |
|
|
| 3713 |
<section title="Reset sampler"> |
<section title="Current number of active voices" anchor="GET TOTAL_VOICE_COUNT"> |
| 3714 |
|
<t>The front-end can ask for the current number of active voices on |
| 3715 |
|
the sampler by sending the following command:</t> |
| 3716 |
|
<t> |
| 3717 |
|
<list> |
| 3718 |
|
<t>GET TOTAL_VOICE_COUNT</t> |
| 3719 |
|
</list> |
| 3720 |
|
</t> |
| 3721 |
|
|
| 3722 |
|
<t>Possible Answers:</t> |
| 3723 |
|
<t> |
| 3724 |
|
<list> |
| 3725 |
|
<t>LinuxSampler will answer by returning the number of all active |
| 3726 |
|
voices on the sampler.</t> |
| 3727 |
|
</list> |
| 3728 |
|
</t> |
| 3729 |
|
</section> |
| 3730 |
|
|
| 3731 |
|
<section title="Maximum amount of active voices" anchor="GET TOTAL_VOICE_COUNT_MAX"> |
| 3732 |
|
<t>The front-end can ask for the maximum number of active voices |
| 3733 |
|
by sending the following command:</t> |
| 3734 |
|
<t> |
| 3735 |
|
<list> |
| 3736 |
|
<t>GET TOTAL_VOICE_COUNT_MAX</t> |
| 3737 |
|
</list> |
| 3738 |
|
</t> |
| 3739 |
|
|
| 3740 |
|
<t>Possible Answers:</t> |
| 3741 |
|
<t> |
| 3742 |
|
<list> |
| 3743 |
|
<t>LinuxSampler will answer by returning the maximum number |
| 3744 |
|
of active voices.</t> |
| 3745 |
|
</list> |
| 3746 |
|
</t> |
| 3747 |
|
</section> |
| 3748 |
|
|
| 3749 |
|
<section title="Reset sampler" anchor="RESET"> |
| 3750 |
<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> |
| 3751 |
<t> |
<t> |
| 3752 |
<list> |
<list> |
| 3771 |
</list> |
</list> |
| 3772 |
</t> |
</t> |
| 3773 |
</section> |
</section> |
| 3774 |
|
|
| 3775 |
|
<section title="General sampler informations" anchor="GET SERVER INFO"> |
| 3776 |
|
<t>The client can ask for general informations about the LinuxSampler |
| 3777 |
|
instance by sending the following command:</t> |
| 3778 |
|
<t> |
| 3779 |
|
<list> |
| 3780 |
|
<t>GET SERVER INFO</t> |
| 3781 |
|
</list> |
| 3782 |
|
</t> |
| 3783 |
|
<t>Possible Answers:</t> |
| 3784 |
|
<t> |
| 3785 |
|
<list> |
| 3786 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
| 3787 |
|
Each answer line begins with the information category name |
| 3788 |
|
followed by a colon and then a space character <SP> and finally |
| 3789 |
|
the info character string to that information category. At the |
| 3790 |
|
moment the following categories are defined: |
| 3791 |
|
</t> |
| 3792 |
|
<t> |
| 3793 |
|
<list> |
| 3794 |
|
<t>DESCRIPTION - |
| 3795 |
|
<list> |
| 3796 |
|
<t>arbitrary textual description about the sampler</t> |
| 3797 |
|
</list> |
| 3798 |
|
</t> |
| 3799 |
|
<t>VERSION - |
| 3800 |
|
<list> |
| 3801 |
|
<t>version of the sampler</t> |
| 3802 |
|
</list> |
| 3803 |
|
</t> |
| 3804 |
|
<t>PROTOCOL_VERSION - |
| 3805 |
|
<list> |
| 3806 |
|
<t>version of the LSCP specification the sampler |
| 3807 |
|
complies with (see <xref target="LSCP versioning" /> for details)</t> |
| 3808 |
|
</list> |
| 3809 |
|
</t> |
| 3810 |
|
</list> |
| 3811 |
|
</t> |
| 3812 |
|
</list> |
| 3813 |
|
</t> |
| 3814 |
|
<t>The mentioned fields above don't have to be in particular order. |
| 3815 |
|
Other fields might be added in future.</t> |
| 3816 |
|
</section> |
| 3817 |
|
</section> |
| 3818 |
|
|
| 3819 |
|
|
| 3820 |
|
<section title="MIDI Instrument Mapping" anchor="MIDI Instrument Mapping"> |
| 3821 |
|
<t>The MIDI protocol provides a way to switch between instruments |
| 3822 |
|
by sending so called MIDI bank select and MIDI program change |
| 3823 |
|
messages which are essentially just numbers. The following commands |
| 3824 |
|
allow to actually map arbitrary MIDI bank select / program change |
| 3825 |
|
numbers with real instruments.</t> |
| 3826 |
|
<t>The sampler allows to manage an arbitrary amount of MIDI |
| 3827 |
|
instrument maps which define which instrument to load on |
| 3828 |
|
which MIDI program change message.</t> |
| 3829 |
|
<t>By default, that is when the sampler is launched, there is no |
| 3830 |
|
map, thus the sampler will simply ignore all program change |
| 3831 |
|
messages. The front-end has to explicitly create at least one |
| 3832 |
|
map, add entries to the map and tell the respective sampler |
| 3833 |
|
channel(s) which MIDI instrument map to use, so the sampler |
| 3834 |
|
knows how to react on a given program change message on the |
| 3835 |
|
respective sampler channel, that is by switching to the |
| 3836 |
|
respectively defined engine type and loading the respective |
| 3837 |
|
instrument. See command |
| 3838 |
|
<xref target="SET CHANNEL MIDI_INSTRUMENT_MAP">"SET CHANNEL MIDI_INSTRUMENT_MAP"</xref> |
| 3839 |
|
for how to assign a MIDI instrument map to a sampler channel.</t> |
| 3840 |
|
<t>Also note per MIDI specification a bank select message does not |
| 3841 |
|
cause to switch to another instrument. Instead when receiving a |
| 3842 |
|
bank select message the bank value will be stored and a subsequent |
| 3843 |
|
program change message (which may occur at any time) will finally |
| 3844 |
|
cause the sampler to switch to the respective instrument as |
| 3845 |
|
reflected by the current MIDI instrument map.</t> |
| 3846 |
|
|
| 3847 |
|
<section title="Create a new MIDI instrument map" anchor="ADD MIDI_INSTRUMENT MAP"> |
| 3848 |
|
<t>The front-end can add a new MIDI instrument map by sending |
| 3849 |
|
the following command:</t> |
| 3850 |
|
<t> |
| 3851 |
|
<list> |
| 3852 |
|
<t>ADD MIDI_INSTRUMENT_MAP [<name>]</t> |
| 3853 |
|
</list> |
| 3854 |
|
</t> |
| 3855 |
|
<t>Where <name> is an optional argument allowing to |
| 3856 |
|
assign a custom name to the new map. MIDI instrument Map |
| 3857 |
|
names do not have to be unique.</t> |
| 3858 |
|
|
| 3859 |
|
<t>Possible Answers:</t> |
| 3860 |
|
<t> |
| 3861 |
|
<list> |
| 3862 |
|
<t>"OK[<map>]" - |
| 3863 |
|
<list> |
| 3864 |
|
<t>in case a new MIDI instrument map could |
| 3865 |
|
be added, where <map> reflects the |
| 3866 |
|
unique ID of the newly created MIDI |
| 3867 |
|
instrument map</t> |
| 3868 |
|
</list> |
| 3869 |
|
</t> |
| 3870 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3871 |
|
<list> |
| 3872 |
|
<t>when a new map could not be created, which |
| 3873 |
|
might never occur in practice</t> |
| 3874 |
|
</list> |
| 3875 |
|
</t> |
| 3876 |
|
</list> |
| 3877 |
|
</t> |
| 3878 |
|
|
| 3879 |
|
<t>Examples:</t> |
| 3880 |
|
<t> |
| 3881 |
|
<list> |
| 3882 |
|
<t>C: "ADD MIDI_INSTRUMENT_MAP 'Standard Map'"</t> |
| 3883 |
|
<t>S: "OK[0]"</t> |
| 3884 |
|
</list> |
| 3885 |
|
</t> |
| 3886 |
|
<t> |
| 3887 |
|
<list> |
| 3888 |
|
<t>C: "ADD MIDI_INSTRUMENT_MAP 'Standard Drumkit'"</t> |
| 3889 |
|
<t>S: "OK[1]"</t> |
| 3890 |
|
</list> |
| 3891 |
|
</t> |
| 3892 |
|
<t> |
| 3893 |
|
<list> |
| 3894 |
|
<t>C: "ADD MIDI_INSTRUMENT_MAP"</t> |
| 3895 |
|
<t>S: "OK[5]"</t> |
| 3896 |
|
</list> |
| 3897 |
|
</t> |
| 3898 |
|
</section> |
| 3899 |
|
|
| 3900 |
|
<section title="Delete one particular or all MIDI instrument maps" anchor="REMOVE MIDI_INSTRUMENT_MAP"> |
| 3901 |
|
<t>The front-end can delete a particular MIDI instrument map |
| 3902 |
|
by sending the following command:</t> |
| 3903 |
|
<t> |
| 3904 |
|
<list> |
| 3905 |
|
<t>REMOVE MIDI_INSTRUMENT_MAP <map></t> |
| 3906 |
|
</list> |
| 3907 |
|
</t> |
| 3908 |
|
<t>Where <map> reflects the unique ID of the map to delete |
| 3909 |
|
as returned by the <xref target="LIST MIDI_INSTRUMENT_MAPS">"LIST MIDI_INSTRUMENT_MAPS"</xref> |
| 3910 |
|
command.</t> |
| 3911 |
|
<t>The front-end can delete all MIDI instrument maps by |
| 3912 |
|
sending the following command:</t> |
| 3913 |
|
<t> |
| 3914 |
|
<list> |
| 3915 |
|
<t>REMOVE MIDI_INSTRUMENT_MAP ALL</t> |
| 3916 |
|
</list> |
| 3917 |
|
</t> |
| 3918 |
|
|
| 3919 |
|
<t>Possible Answers:</t> |
| 3920 |
|
<t> |
| 3921 |
|
<list> |
| 3922 |
|
<t>"OK" - |
| 3923 |
|
<list> |
| 3924 |
|
<t>in case the map(s) could be deleted</t> |
| 3925 |
|
</list> |
| 3926 |
|
</t> |
| 3927 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3928 |
|
<list> |
| 3929 |
|
<t>when the given map does not exist</t> |
| 3930 |
|
</list> |
| 3931 |
|
</t> |
| 3932 |
|
</list> |
| 3933 |
|
</t> |
| 3934 |
|
|
| 3935 |
|
<t>Examples:</t> |
| 3936 |
|
<t> |
| 3937 |
|
<list> |
| 3938 |
|
<t>C: "REMOVE MIDI_INSTRUMENT_MAP 0"</t> |
| 3939 |
|
<t>S: "OK"</t> |
| 3940 |
|
</list> |
| 3941 |
|
</t> |
| 3942 |
|
<t> |
| 3943 |
|
<list> |
| 3944 |
|
<t>C: "REMOVE MIDI_INSTRUMENT_MAP ALL"</t> |
| 3945 |
|
<t>S: "OK"</t> |
| 3946 |
|
</list> |
| 3947 |
|
</t> |
| 3948 |
|
</section> |
| 3949 |
|
|
| 3950 |
|
<section title="Get amount of existing MIDI instrument maps" anchor="GET MIDI_INSTRUMENT_MAPS"> |
| 3951 |
|
<t>The front-end can retrieve the current amount of MIDI |
| 3952 |
|
instrument maps by sending the following command:</t> |
| 3953 |
|
<t> |
| 3954 |
|
<list> |
| 3955 |
|
<t>GET MIDI_INSTRUMENT_MAPS</t> |
| 3956 |
|
</list> |
| 3957 |
|
</t> |
| 3958 |
|
|
| 3959 |
|
<t>Possible Answers:</t> |
| 3960 |
|
<t> |
| 3961 |
|
<list> |
| 3962 |
|
<t>The sampler will answer by returning the current |
| 3963 |
|
number of MIDI instrument maps.</t> |
| 3964 |
|
</list> |
| 3965 |
|
</t> |
| 3966 |
|
|
| 3967 |
|
<t>Example:</t> |
| 3968 |
|
<t> |
| 3969 |
|
<list> |
| 3970 |
|
<t>C: "GET MIDI_INSTRUMENT_MAPS"</t> |
| 3971 |
|
<t>S: "2"</t> |
| 3972 |
|
</list> |
| 3973 |
|
</t> |
| 3974 |
|
</section> |
| 3975 |
|
|
| 3976 |
|
<section title="Getting all created MIDI instrument maps" anchor="LIST MIDI_INSTRUMENT_MAPS"> |
| 3977 |
|
<t>The number of MIDI instrument maps can change on runtime. To get the |
| 3978 |
|
current list of MIDI instrument maps, the front-end can send the |
| 3979 |
|
following command:</t> |
| 3980 |
|
<t> |
| 3981 |
|
<list> |
| 3982 |
|
<t>LIST MIDI_INSTRUMENT_MAPS</t> |
| 3983 |
|
</list> |
| 3984 |
|
</t> |
| 3985 |
|
<t>Possible Answers:</t> |
| 3986 |
|
<t> |
| 3987 |
|
<list> |
| 3988 |
|
<t>The sampler will answer by returning a comma separated list |
| 3989 |
|
with all MIDI instrument maps' numerical IDs.</t> |
| 3990 |
|
</list> |
| 3991 |
|
</t> |
| 3992 |
|
<t>Example:</t> |
| 3993 |
|
<t> |
| 3994 |
|
<list> |
| 3995 |
|
<t>C: "LIST MIDI_INSTRUMENT_MAPS"</t> |
| 3996 |
|
<t>S: "0,1,5,12"</t> |
| 3997 |
|
</list> |
| 3998 |
|
</t> |
| 3999 |
|
</section> |
| 4000 |
|
|
| 4001 |
|
<section title="Getting MIDI instrument map information" anchor="GET MIDI_INSTRUMENT_MAP INFO"> |
| 4002 |
|
<t>The front-end can ask for the current settings of a MIDI |
| 4003 |
|
instrument map by sending the following command:</t> |
| 4004 |
|
<t> |
| 4005 |
|
<list> |
| 4006 |
|
<t>GET MIDI_INSTRUMENT_MAP INFO <map></t> |
| 4007 |
|
</list> |
| 4008 |
|
</t> |
| 4009 |
|
<t>Where <map> is the numerical ID of the map the |
| 4010 |
|
front-end is interested in as returned by the |
| 4011 |
|
<xref target="LIST MIDI_INSTRUMENT_MAPS">"LIST MIDI_INSTRUMENT_MAPS"</xref> |
| 4012 |
|
command.</t> |
| 4013 |
|
|
| 4014 |
|
<t>Possible Answers:</t> |
| 4015 |
|
<t> |
| 4016 |
|
<list> |
| 4017 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
| 4018 |
|
Each answer line begins with the settings category name |
| 4019 |
|
followed by a colon and then a space character <SP> and finally |
| 4020 |
|
the info character string to that setting category. At the |
| 4021 |
|
moment the following categories are defined:</t> |
| 4022 |
|
|
| 4023 |
|
<t> |
| 4024 |
|
<list> |
| 4025 |
|
<t>NAME - |
| 4026 |
|
<list> |
| 4027 |
|
<t>custom name of the given map, |
| 4028 |
|
which does not have to be unique</t> |
| 4029 |
|
</list> |
| 4030 |
|
</t> |
| 4031 |
|
</list> |
| 4032 |
|
</t> |
| 4033 |
|
</list> |
| 4034 |
|
</t> |
| 4035 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 4036 |
|
|
| 4037 |
|
<t>Example:</t> |
| 4038 |
|
<t> |
| 4039 |
|
<list> |
| 4040 |
|
<t>C: "GET MIDI_INSTRUMENT_MAP INFO 0"</t> |
| 4041 |
|
<t>S: "NAME: Standard Map"</t> |
| 4042 |
|
<t> "."</t> |
| 4043 |
|
</list> |
| 4044 |
|
</t> |
| 4045 |
|
</section> |
| 4046 |
|
|
| 4047 |
|
<section title="Renaming a MIDI instrument map" anchor="SET MIDI_INSTRUMENT_MAP NAME"> |
| 4048 |
|
<t>The front-end can alter the custom name of a MIDI |
| 4049 |
|
instrument map by sending the following command:</t> |
| 4050 |
|
<t> |
| 4051 |
|
<list> |
| 4052 |
|
<t>SET MIDI_INSTRUMENT_MAP NAME <map> <name></t> |
| 4053 |
|
</list> |
| 4054 |
|
</t> |
| 4055 |
|
<t>Where <map> is the numerical ID of the map and |
| 4056 |
|
<name> the new custom name of the map, which does not |
| 4057 |
|
have to be unique.</t> |
| 4058 |
|
|
| 4059 |
|
<t>Possible Answers:</t> |
| 4060 |
|
<t> |
| 4061 |
|
<list> |
| 4062 |
|
<t>"OK" - |
| 4063 |
|
<list> |
| 4064 |
|
<t>on success</t> |
| 4065 |
|
</list> |
| 4066 |
|
</t> |
| 4067 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4068 |
|
<list> |
| 4069 |
|
<t>in case the given map does not exist</t> |
| 4070 |
|
</list> |
| 4071 |
|
</t> |
| 4072 |
|
</list> |
| 4073 |
|
</t> |
| 4074 |
|
|
| 4075 |
|
<t>Example:</t> |
| 4076 |
|
<t> |
| 4077 |
|
<list> |
| 4078 |
|
<t>C: "SET MIDI_INSTRUMENT_MAP NAME 0 'Foo instruments'"</t> |
| 4079 |
|
<t>S: "OK"</t> |
| 4080 |
|
</list> |
| 4081 |
|
</t> |
| 4082 |
|
</section> |
| 4083 |
|
|
| 4084 |
|
<section title="Create or replace a MIDI instrument map entry" anchor="MAP MIDI_INSTRUMENT"> |
| 4085 |
|
<t>The front-end can create a new or replace an existing entry |
| 4086 |
|
in a sampler's MIDI instrument map by sending the following |
| 4087 |
|
command:</t> |
| 4088 |
|
<t> |
| 4089 |
|
<list> |
| 4090 |
|
<t>MAP MIDI_INSTRUMENT <map> |
| 4091 |
|
<midi_bank> <midi_prog> <engine_name> |
| 4092 |
|
<filename> <instrument_index> <volume_value> |
| 4093 |
|
[<instr_load_mode>] [<name>]</t> |
| 4094 |
|
</list> |
| 4095 |
|
</t> |
| 4096 |
|
<t>Where <map> is the numeric ID of the map to alter, |
| 4097 |
|
<midi_bank> is an integer value between |
| 4098 |
|
0..16383 reflecting the MIDI bank select index, |
| 4099 |
|
<midi_prog> an |
| 4100 |
|
integer value between 0..127 reflecting the MIDI program change |
| 4101 |
|
index, <engine_name> a sampler engine name as returned by |
| 4102 |
|
the <xref target="LIST AVAILABLE_ENGINES">"LIST AVAILABLE_ENGINES"</xref> |
| 4103 |
|
command (not encapsulated into apostrophes), <filename> the name |
| 4104 |
|
of the instrument's file to be deployed (encapsulated into apostrophes), |
| 4105 |
|
<instrument_index> the index (integer value) of the instrument |
| 4106 |
|
within the given file, <volume_value> reflects the master |
| 4107 |
|
volume of the instrument as optionally dotted number (where a |
| 4108 |
|
value < 1.0 means attenuation and a value > 1.0 means |
| 4109 |
|
amplification). This parameter easily allows to adjust the |
| 4110 |
|
volume of all intruments within a custom instrument map |
| 4111 |
|
without having to adjust their instrument files. The |
| 4112 |
|
OPTIONAL <instr_load_mode> argument defines the life |
| 4113 |
|
time of the instrument, that is when the instrument should |
| 4114 |
|
be loaded, when freed and has exactly the following |
| 4115 |
|
possibilities:</t> |
| 4116 |
|
<t> |
| 4117 |
|
<list> |
| 4118 |
|
<t>"ON_DEMAND" - |
| 4119 |
|
<list> |
| 4120 |
|
<t>The instrument will be loaded when needed, |
| 4121 |
|
that is when demanded by at least one sampler |
| 4122 |
|
channel. It will immediately be freed from memory |
| 4123 |
|
when not needed by any sampler channel anymore.</t> |
| 4124 |
|
</list> |
| 4125 |
|
</t> |
| 4126 |
|
<t>"ON_DEMAND_HOLD" - |
| 4127 |
|
<list> |
| 4128 |
|
<t>The instrument will be loaded when needed, |
| 4129 |
|
that is when demanded by at least one sampler |
| 4130 |
|
channel. It will be kept in memory even when |
| 4131 |
|
not needed by any sampler channel anymore. |
| 4132 |
|
Instruments with this mode are only freed |
| 4133 |
|
when the sampler is reset or all mapping |
| 4134 |
|
entries with this mode (and respective |
| 4135 |
|
instrument) are explicitly changed to |
| 4136 |
|
"ON_DEMAND" and no sampler channel is using |
| 4137 |
|
the instrument anymore.</t> |
| 4138 |
|
</list> |
| 4139 |
|
</t> |
| 4140 |
|
<t>"PERSISTENT" - |
| 4141 |
|
<list> |
| 4142 |
|
<t>The instrument will immediately be loaded |
| 4143 |
|
into memory in the background when this mapping |
| 4144 |
|
command is sent and the instrument is kept all |
| 4145 |
|
the time. Instruments with this mode are |
| 4146 |
|
only freed when the sampler is reset or all |
| 4147 |
|
mapping entries with this mode (and |
| 4148 |
|
respective instrument) are explicitly |
| 4149 |
|
changed to "ON_DEMAND" and no sampler |
| 4150 |
|
channel is using the instrument anymore.</t> |
| 4151 |
|
</list> |
| 4152 |
|
</t> |
| 4153 |
|
<t>not supplied - |
| 4154 |
|
<list> |
| 4155 |
|
<t>In case there is no <instr_load_mode> |
| 4156 |
|
argument given, it will be up to the |
| 4157 |
|
InstrumentManager to decide which mode to use. |
| 4158 |
|
Usually it will use "ON_DEMAND" if an entry |
| 4159 |
|
for the given instrument does not exist in |
| 4160 |
|
the InstrumentManager's list yet, otherwise |
| 4161 |
|
if an entry already exists, it will simply |
| 4162 |
|
stick with the mode currently reflected by |
| 4163 |
|
the already existing entry, that is it will |
| 4164 |
|
not change the mode.</t> |
| 4165 |
|
</list> |
| 4166 |
|
</t> |
| 4167 |
|
</list> |
| 4168 |
|
</t> |
| 4169 |
|
<t> |
| 4170 |
|
The <instr_load_mode> argument thus allows to define an |
| 4171 |
|
appropriate strategy (low memory consumption vs. fast |
| 4172 |
|
instrument switching) for each instrument individually. Note, the |
| 4173 |
|
following restrictions apply to this argument: "ON_DEMAND_HOLD" and |
| 4174 |
|
"PERSISTENT" have to be supported by the respective sampler engine |
| 4175 |
|
(which is technically the case when the engine provides an |
| 4176 |
|
InstrumentManager for its format). If this is not the case the |
| 4177 |
|
argument will automatically fall back to the default value |
| 4178 |
|
"ON_DEMAND". Also the load mode of one instrument may |
| 4179 |
|
automatically change the laod mode of other instrument(s), i.e. |
| 4180 |
|
because the instruments are part of the same file and the |
| 4181 |
|
engine does not allow a way to manage load modes for them |
| 4182 |
|
individually. Due to this, in case the frontend shows the |
| 4183 |
|
load modes of entries, the frontend should retrieve the actual |
| 4184 |
|
mode by i.e. sending |
| 4185 |
|
<xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref> |
| 4186 |
|
command(s). Finally the OPTIONAL <name> argument allows to |
| 4187 |
|
set a custom name (encapsulated into apostrophes) for the mapping |
| 4188 |
|
entry, useful for frontends for displaying an appropriate name for |
| 4189 |
|
mapped instruments (using |
| 4190 |
|
<xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref>). |
| 4191 |
|
</t> |
| 4192 |
|
<t> |
| 4193 |
|
The "MAP MIDI_INSTRUMENT" command |
| 4194 |
|
will immediately return, thus it will not block when an |
| 4195 |
|
instrument is to be loaded due to a "PERSISTENT" type |
| 4196 |
|
entry as instruments are loaded in the background. As a |
| 4197 |
|
consequence this command may not necessarily return an error |
| 4198 |
|
i.e. when the given instrument file does not exist or may |
| 4199 |
|
turn out to be corrupt. |
| 4200 |
|
</t> |
| 4201 |
|
|
| 4202 |
|
<t>Possible Answers:</t> |
| 4203 |
|
<t> |
| 4204 |
|
<list> |
| 4205 |
|
<t>"OK" - |
| 4206 |
|
<list> |
| 4207 |
|
<t>usually</t> |
| 4208 |
|
</list> |
| 4209 |
|
</t> |
| 4210 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4211 |
|
<list> |
| 4212 |
|
<t>when the given map or engine does not exist or a value |
| 4213 |
|
is out of range</t> |
| 4214 |
|
</list> |
| 4215 |
|
</t> |
| 4216 |
|
</list> |
| 4217 |
|
</t> |
| 4218 |
|
|
| 4219 |
|
<t>Examples:</t> |
| 4220 |
|
<t> |
| 4221 |
|
<list> |
| 4222 |
|
<t>C: "MAP MIDI_INSTRUMENT 0 3 0 gig '/usr/share/Steinway D.gig' 0 0.8 PERSISTENT"</t> |
| 4223 |
|
<t>S: "OK"</t> |
| 4224 |
|
</list> |
| 4225 |
|
</t> |
| 4226 |
|
<t> |
| 4227 |
|
<list> |
| 4228 |
|
<t>C: "MAP MIDI_INSTRUMENT 0 4 50 gig '/home/john/foostrings.gig' 7 1.0"</t> |
| 4229 |
|
<t>S: "OK"</t> |
| 4230 |
|
</list> |
| 4231 |
|
</t> |
| 4232 |
|
<t> |
| 4233 |
|
<list> |
| 4234 |
|
<t>C: "MAP MIDI_INSTRUMENT 0 0 0 gig '/usr/share/piano.gig' 0 1.0 'Normal Piano'"</t> |
| 4235 |
|
<t>S: "OK"</t> |
| 4236 |
|
<t>C: "MAP MIDI_INSTRUMENT 0 1 0 gig '/usr/share/piano.gig' 0 0.25 'Silent Piano'"</t> |
| 4237 |
|
<t>S: "OK"</t> |
| 4238 |
|
</list> |
| 4239 |
|
</t> |
| 4240 |
|
<t> |
| 4241 |
|
<list> |
| 4242 |
|
<t>C: "MAP MIDI_INSTRUMENT 1 8 120 gig '/home/joe/foodrums.gig' 0 1.0 PERSISTENT 'Foo Drumkit'"</t> |
| 4243 |
|
<t>S: "OK"</t> |
| 4244 |
|
</list> |
| 4245 |
|
</t> |
| 4246 |
|
</section> |
| 4247 |
|
|
| 4248 |
|
<section title="Getting ammount of MIDI instrument map entries" anchor="GET MIDI_INSTRUMENTS"> |
| 4249 |
|
<t>The front-end can query the amount of currently existing |
| 4250 |
|
entries in a MIDI instrument map by sending the following |
| 4251 |
|
command:</t> |
| 4252 |
|
<t> |
| 4253 |
|
<list> |
| 4254 |
|
<t>GET MIDI_INSTRUMENTS <map></t> |
| 4255 |
|
</list> |
| 4256 |
|
</t> |
| 4257 |
|
<t>The front-end can query the amount of currently existing |
| 4258 |
|
entries in all MIDI instrument maps by sending the following |
| 4259 |
|
command:</t> |
| 4260 |
|
<t> |
| 4261 |
|
<list> |
| 4262 |
|
<t>GET MIDI_INSTRUMENTS ALL</t> |
| 4263 |
|
</list> |
| 4264 |
|
</t> |
| 4265 |
|
<t>Possible Answers:</t> |
| 4266 |
|
<t> |
| 4267 |
|
<list> |
| 4268 |
|
<t>The sampler will answer by sending the current number of |
| 4269 |
|
entries in the MIDI instrument map(s).</t> |
| 4270 |
|
</list> |
| 4271 |
|
</t> |
| 4272 |
|
|
| 4273 |
|
<t>Example:</t> |
| 4274 |
|
<t> |
| 4275 |
|
<list> |
| 4276 |
|
<t>C: "GET MIDI_INSTRUMENTS 0"</t> |
| 4277 |
|
<t>S: "234"</t> |
| 4278 |
|
</list> |
| 4279 |
|
</t> |
| 4280 |
|
<t> |
| 4281 |
|
<list> |
| 4282 |
|
<t>C: "GET MIDI_INSTRUMENTS ALL"</t> |
| 4283 |
|
<t>S: "954"</t> |
| 4284 |
|
</list> |
| 4285 |
|
</t> |
| 4286 |
|
</section> |
| 4287 |
|
|
| 4288 |
|
<section title="Getting indeces of all entries of a MIDI instrument map" anchor="LIST MIDI_INSTRUMENTS"> |
| 4289 |
|
<t>The front-end can query a list of all currently existing |
| 4290 |
|
entries in a certain MIDI instrument map by sending the following |
| 4291 |
|
command:</t> |
| 4292 |
|
<t> |
| 4293 |
|
<list> |
| 4294 |
|
<t>LIST MIDI_INSTRUMENTS <map></t> |
| 4295 |
|
</list> |
| 4296 |
|
</t> |
| 4297 |
|
<t>Where <map> is the numeric ID of the MIDI instrument map.</t> |
| 4298 |
|
<t>The front-end can query a list of all currently existing |
| 4299 |
|
entries of all MIDI instrument maps by sending the following |
| 4300 |
|
command:</t> |
| 4301 |
|
<t> |
| 4302 |
|
<list> |
| 4303 |
|
<t>LIST MIDI_INSTRUMENTS ALL</t> |
| 4304 |
|
</list> |
| 4305 |
|
</t> |
| 4306 |
|
|
| 4307 |
|
<t>Possible Answers:</t> |
| 4308 |
|
<t> |
| 4309 |
|
<list> |
| 4310 |
|
<t>The sampler will answer by sending a comma separated |
| 4311 |
|
list of map ID - MIDI bank - MIDI program triples, where |
| 4312 |
|
each triple is encapsulated into curly braces. The |
| 4313 |
|
list is returned in one single line. Each triple |
| 4314 |
|
just reflects the key of the respective map entry, |
| 4315 |
|
thus subsequent |
| 4316 |
|
<xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref> |
| 4317 |
|
command(s) are necessary to retrieve detailed informations |
| 4318 |
|
about each entry.</t> |
| 4319 |
|
</list> |
| 4320 |
|
</t> |
| 4321 |
|
|
| 4322 |
|
<t>Example:</t> |
| 4323 |
|
<t> |
| 4324 |
|
<list> |
| 4325 |
|
<t>C: "LIST MIDI_INSTRUMENTS 0"</t> |
| 4326 |
|
<t>S: "{0,0,0},{0,0,1},{0,0,3},{0,1,4},{1,127,127}"</t> |
| 4327 |
|
</list> |
| 4328 |
|
</t> |
| 4329 |
|
</section> |
| 4330 |
|
|
| 4331 |
|
<section title="Remove an entry from the MIDI instrument map" anchor="UNMAP MIDI_INSTRUMENT"> |
| 4332 |
|
<t>The front-end can delete an entry from a MIDI instrument |
| 4333 |
|
map by sending the following command:</t> |
| 4334 |
|
<t> |
| 4335 |
|
<list> |
| 4336 |
|
<t>UNMAP MIDI_INSTRUMENT <map> <midi_bank> <midi_prog></t> |
| 4337 |
|
</list> |
| 4338 |
|
</t> |
| 4339 |
|
<t> |
| 4340 |
|
Where <map> is the numeric ID of the MIDI instrument map, |
| 4341 |
|
<midi_bank> is an integer value between 0..16383 |
| 4342 |
|
reflecting the MIDI bank value and |
| 4343 |
|
<midi_prog> an integer value between |
| 4344 |
|
0..127 reflecting the MIDI program value of the map's entrie's key |
| 4345 |
|
index triple. |
| 4346 |
|
</t> |
| 4347 |
|
|
| 4348 |
|
<t>Possible Answers:</t> |
| 4349 |
|
<t> |
| 4350 |
|
<list> |
| 4351 |
|
<t>"OK" - |
| 4352 |
|
<list> |
| 4353 |
|
<t>usually</t> |
| 4354 |
|
</list> |
| 4355 |
|
</t> |
| 4356 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4357 |
|
<list> |
| 4358 |
|
<t>when index out of bounds</t> |
| 4359 |
|
</list> |
| 4360 |
|
</t> |
| 4361 |
|
</list> |
| 4362 |
|
</t> |
| 4363 |
|
|
| 4364 |
|
<t>Example:</t> |
| 4365 |
|
<t> |
| 4366 |
|
<list> |
| 4367 |
|
<t>C: "UNMAP MIDI_INSTRUMENT 0 2 127"</t> |
| 4368 |
|
<t>S: "OK"</t> |
| 4369 |
|
</list> |
| 4370 |
|
</t> |
| 4371 |
|
</section> |
| 4372 |
|
|
| 4373 |
|
<section title="Get current settings of MIDI instrument map entry" anchor="GET MIDI_INSTRUMENT INFO"> |
| 4374 |
|
<t>The front-end can retrieve the current settings of a certain |
| 4375 |
|
instrument map entry by sending the following command:</t> |
| 4376 |
|
<t> |
| 4377 |
|
<list> |
| 4378 |
|
<t>GET MIDI_INSTRUMENT INFO <map> <midi_bank> <midi_prog></t> |
| 4379 |
|
</list> |
| 4380 |
|
</t> |
| 4381 |
|
<t> |
| 4382 |
|
Where <map> is the numeric ID of the MIDI instrument map, |
| 4383 |
|
<midi_bank> is an integer value between 0..16383 |
| 4384 |
|
reflecting the MIDI bank value, <midi_bank> |
| 4385 |
|
and <midi_prog> an integer value between |
| 4386 |
|
0..127 reflecting the MIDI program value of the map's entrie's key |
| 4387 |
|
index triple. |
| 4388 |
|
</t> |
| 4389 |
|
|
| 4390 |
|
<t>Possible Answers:</t> |
| 4391 |
|
<t> |
| 4392 |
|
<list> |
| 4393 |
|
<t>LinuxSampler will answer by sending a <CRLF> |
| 4394 |
|
separated list. Each answer line begins with the |
| 4395 |
|
information category name followed by a colon and then |
| 4396 |
|
a space character <SP> and finally the info |
| 4397 |
|
character string to that info category. At the moment |
| 4398 |
|
the following categories are defined:</t> |
| 4399 |
|
<t>"NAME" - |
| 4400 |
|
<list> |
| 4401 |
|
<t>Name for this MIDI instrument map entry (if defined). |
| 4402 |
|
This name shall be used by frontends for displaying a |
| 4403 |
|
name for this mapped instrument. It can be set and |
| 4404 |
|
changed with the |
| 4405 |
|
<xref target="MAP MIDI_INSTRUMENT">"MAP MIDI_INSTRUMENT"</xref> |
| 4406 |
|
command and does not have to be unique.</t> |
| 4407 |
|
</list> |
| 4408 |
|
</t> |
| 4409 |
|
<t>"ENGINE_NAME" - |
| 4410 |
|
<list> |
| 4411 |
|
<t>Name of the engine to be deployed for this |
| 4412 |
|
instrument.</t> |
| 4413 |
|
</list> |
| 4414 |
|
</t> |
| 4415 |
|
<t>"INSTRUMENT_FILE" - |
| 4416 |
|
<list> |
| 4417 |
|
<t>File name of the instrument.</t> |
| 4418 |
|
</list> |
| 4419 |
|
</t> |
| 4420 |
|
<t>"INSTRUMENT_NR" - |
| 4421 |
|
<list> |
| 4422 |
|
<t>Index of the instrument within the file.</t> |
| 4423 |
|
</list> |
| 4424 |
|
</t> |
| 4425 |
|
<t>"INSTRUMENT_NAME" - |
| 4426 |
|
<list> |
| 4427 |
|
<t>Name of the loaded instrument as reflected by its file. |
| 4428 |
|
In contrast to the "NAME" field, the "INSTRUMENT_NAME" field |
| 4429 |
|
cannot be changed.</t> |
| 4430 |
|
</list> |
| 4431 |
|
</t> |
| 4432 |
|
<t>"LOAD_MODE" - |
| 4433 |
|
<list> |
| 4434 |
|
<t>Life time of instrument |
| 4435 |
|
(see <xref target="MAP MIDI_INSTRUMENT">"MAP MIDI_INSTRUMENT"</xref> for details about this setting).</t> |
| 4436 |
|
</list> |
| 4437 |
|
</t> |
| 4438 |
|
<t>"VOLUME" - |
| 4439 |
|
<list> |
| 4440 |
|
<t>master volume of the instrument as optionally |
| 4441 |
|
dotted number (where a value < 1.0 means attenuation |
| 4442 |
|
and a value > 1.0 means amplification)</t> |
| 4443 |
|
</list> |
| 4444 |
|
</t> |
| 4445 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 4446 |
|
</list> |
| 4447 |
|
</t> |
| 4448 |
|
|
| 4449 |
|
<t>Example:</t> |
| 4450 |
|
<t> |
| 4451 |
|
<list> |
| 4452 |
|
<t>C: "GET MIDI_INSTRUMENT INFO 1 45 120"</t> |
| 4453 |
|
<t>S: "NAME: Drums for Foo Song"</t> |
| 4454 |
|
<t> "ENGINE_NAME: GigEngine"</t> |
| 4455 |
|
<t> "INSTRUMENT_FILE: /usr/share/joesdrumkit.gig"</t> |
| 4456 |
|
<t> "INSTRUMENT_NR: 0"</t> |
| 4457 |
|
<t> "INSTRUMENT_NAME: Joe's Drumkit"</t> |
| 4458 |
|
<t> "LOAD_MODE: PERSISTENT"</t> |
| 4459 |
|
<t> "VOLUME: 1.0"</t> |
| 4460 |
|
<t> "."</t> |
| 4461 |
|
</list> |
| 4462 |
|
</t> |
| 4463 |
|
</section> |
| 4464 |
|
|
| 4465 |
|
<section title="Clear MIDI instrument map" anchor="CLEAR MIDI_INSTRUMENTS"> |
| 4466 |
|
<t>The front-end can clear a whole MIDI instrument map, that |
| 4467 |
|
is delete all its entries by sending the following command:</t> |
| 4468 |
|
<t> |
| 4469 |
|
<list> |
| 4470 |
|
<t>CLEAR MIDI_INSTRUMENTS <map></t> |
| 4471 |
|
</list> |
| 4472 |
|
</t> |
| 4473 |
|
<t>Where <map> is the numeric ID of the map to clear.</t> |
| 4474 |
|
<t>The front-end can clear all MIDI instrument maps, that |
| 4475 |
|
is delete all entries of all maps by sending the following |
| 4476 |
|
command:</t> |
| 4477 |
|
<t> |
| 4478 |
|
<list> |
| 4479 |
|
<t>CLEAR MIDI_INSTRUMENTS ALL</t> |
| 4480 |
|
</list> |
| 4481 |
|
</t> |
| 4482 |
|
<t>The command "CLEAR MIDI_INSTRUMENTS ALL" does not delete the |
| 4483 |
|
maps, only their entries, thus the map's settings like |
| 4484 |
|
custom name will be preservevd.</t> |
| 4485 |
|
|
| 4486 |
|
<t>Possible Answers:</t> |
| 4487 |
|
<t> |
| 4488 |
|
<list> |
| 4489 |
|
<t>"OK" - |
| 4490 |
|
<list> |
| 4491 |
|
<t>always</t> |
| 4492 |
|
</list> |
| 4493 |
|
</t> |
| 4494 |
|
</list> |
| 4495 |
|
</t> |
| 4496 |
|
|
| 4497 |
|
<t>Examples:</t> |
| 4498 |
|
<t> |
| 4499 |
|
<list> |
| 4500 |
|
<t>C: "CLEAR MIDI_INSTRUMENTS 0"</t> |
| 4501 |
|
<t>S: "OK"</t> |
| 4502 |
|
</list> |
| 4503 |
|
</t> |
| 4504 |
|
<t> |
| 4505 |
|
<list> |
| 4506 |
|
<t>C: "CLEAR MIDI_INSTRUMENTS ALL"</t> |
| 4507 |
|
<t>S: "OK"</t> |
| 4508 |
|
</list> |
| 4509 |
|
</t> |
| 4510 |
|
</section> |
| 4511 |
</section> |
</section> |
| 4512 |
|
|
| 4513 |
</section> |
</section> |
| 4514 |
|
|
| 4515 |
<section title="Command Syntax"> |
|
| 4516 |
<t>TODO: will soon automatically included from src/network/lscp.y, |
<section title="Command Syntax" anchor="command_syntax"> |
| 4517 |
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"/> |
| 4518 |
the command syntax.</t> |
is defined below using Backus-Naur Form (BNF as described in <xref target="RFC2234"/>) |
| 4519 |
|
where applicable. |
| 4520 |
|
</t> |
| 4521 |
|
<!-- |
| 4522 |
|
This section is automatically generated by scripts/update_grammar.pl |
| 4523 |
|
from src/network/lscp.y (yacc input file). Do not modify this section |
| 4524 |
|
manually ! |
| 4525 |
|
--> |
| 4526 |
|
<!-- GRAMMAR_BNF_BEGIN - do NOT delete or modify this line !!! --> |
| 4527 |
|
|
| 4528 |
|
<t>input = |
| 4529 |
|
<list> |
| 4530 |
|
<t>line LF |
| 4531 |
|
</t> |
| 4532 |
|
<t>/ line CR LF |
| 4533 |
|
</t> |
| 4534 |
|
</list> |
| 4535 |
|
</t> |
| 4536 |
|
<t>line = |
| 4537 |
|
<list> |
| 4538 |
|
<t>/* epsilon (empty line ignored) */ |
| 4539 |
|
</t> |
| 4540 |
|
<t>/ comment |
| 4541 |
|
</t> |
| 4542 |
|
<t>/ command |
| 4543 |
|
</t> |
| 4544 |
|
<t>/ error |
| 4545 |
|
</t> |
| 4546 |
|
</list> |
| 4547 |
|
</t> |
| 4548 |
|
<t>comment = |
| 4549 |
|
<list> |
| 4550 |
|
<t>'#' |
| 4551 |
|
</t> |
| 4552 |
|
<t>/ comment '#' |
| 4553 |
|
</t> |
| 4554 |
|
<t>/ comment SP |
| 4555 |
|
</t> |
| 4556 |
|
<t>/ comment number |
| 4557 |
|
</t> |
| 4558 |
|
<t>/ comment string |
| 4559 |
|
</t> |
| 4560 |
|
</list> |
| 4561 |
|
</t> |
| 4562 |
|
<t>command = |
| 4563 |
|
<list> |
| 4564 |
|
<t>ADD SP add_instruction |
| 4565 |
|
</t> |
| 4566 |
|
<t>/ MAP SP map_instruction |
| 4567 |
|
</t> |
| 4568 |
|
<t>/ UNMAP SP unmap_instruction |
| 4569 |
|
</t> |
| 4570 |
|
<t>/ GET SP get_instruction |
| 4571 |
|
</t> |
| 4572 |
|
<t>/ CREATE SP create_instruction |
| 4573 |
|
</t> |
| 4574 |
|
<t>/ DESTROY SP destroy_instruction |
| 4575 |
|
</t> |
| 4576 |
|
<t>/ LIST SP list_instruction |
| 4577 |
|
</t> |
| 4578 |
|
<t>/ LOAD SP load_instruction |
| 4579 |
|
</t> |
| 4580 |
|
<t>/ REMOVE SP remove_instruction |
| 4581 |
|
</t> |
| 4582 |
|
<t>/ SET SP set_instruction |
| 4583 |
|
</t> |
| 4584 |
|
<t>/ SUBSCRIBE SP subscribe_event |
| 4585 |
|
</t> |
| 4586 |
|
<t>/ UNSUBSCRIBE SP unsubscribe_event |
| 4587 |
|
</t> |
| 4588 |
|
<t>/ SELECT SP text |
| 4589 |
|
</t> |
| 4590 |
|
<t>/ RESET SP reset_instruction |
| 4591 |
|
</t> |
| 4592 |
|
<t>/ CLEAR SP clear_instruction |
| 4593 |
|
</t> |
| 4594 |
|
<t>/ RESET |
| 4595 |
|
</t> |
| 4596 |
|
<t>/ QUIT |
| 4597 |
|
</t> |
| 4598 |
|
</list> |
| 4599 |
|
</t> |
| 4600 |
|
<t>add_instruction = |
| 4601 |
|
<list> |
| 4602 |
|
<t>CHANNEL |
| 4603 |
|
</t> |
| 4604 |
|
<t>/ MIDI_INSTRUMENT_MAP |
| 4605 |
|
</t> |
| 4606 |
|
<t>/ MIDI_INSTRUMENT_MAP SP map_name |
| 4607 |
|
</t> |
| 4608 |
|
</list> |
| 4609 |
|
</t> |
| 4610 |
|
<t>subscribe_event = |
| 4611 |
|
<list> |
| 4612 |
|
<t>AUDIO_OUTPUT_DEVICE_COUNT |
| 4613 |
|
</t> |
| 4614 |
|
<t>/ AUDIO_OUTPUT_DEVICE_INFO |
| 4615 |
|
</t> |
| 4616 |
|
<t>/ MIDI_INPUT_DEVICE_COUNT |
| 4617 |
|
</t> |
| 4618 |
|
<t>/ MIDI_INPUT_DEVICE_INFO |
| 4619 |
|
</t> |
| 4620 |
|
<t>/ CHANNEL_COUNT |
| 4621 |
|
</t> |
| 4622 |
|
<t>/ VOICE_COUNT |
| 4623 |
|
</t> |
| 4624 |
|
<t>/ STREAM_COUNT |
| 4625 |
|
</t> |
| 4626 |
|
<t>/ BUFFER_FILL |
| 4627 |
|
</t> |
| 4628 |
|
<t>/ CHANNEL_INFO |
| 4629 |
|
</t> |
| 4630 |
|
<t>/ MIDI_INSTRUMENT_MAP_COUNT |
| 4631 |
|
</t> |
| 4632 |
|
<t>/ MIDI_INSTRUMENT_MAP_INFO |
| 4633 |
|
</t> |
| 4634 |
|
<t>/ MIDI_INSTRUMENT_COUNT |
| 4635 |
|
</t> |
| 4636 |
|
<t>/ MIDI_INSTRUMENT_INFO |
| 4637 |
|
</t> |
| 4638 |
|
<t>/ MISCELLANEOUS |
| 4639 |
|
</t> |
| 4640 |
|
<t>/ TOTAL_VOICE_COUNT |
| 4641 |
|
</t> |
| 4642 |
|
</list> |
| 4643 |
|
</t> |
| 4644 |
|
<t>unsubscribe_event = |
| 4645 |
|
<list> |
| 4646 |
|
<t>AUDIO_OUTPUT_DEVICE_COUNT |
| 4647 |
|
</t> |
| 4648 |
|
<t>/ AUDIO_OUTPUT_DEVICE_INFO |
| 4649 |
|
</t> |
| 4650 |
|
<t>/ MIDI_INPUT_DEVICE_COUNT |
| 4651 |
|
</t> |
| 4652 |
|
<t>/ MIDI_INPUT_DEVICE_INFO |
| 4653 |
|
</t> |
| 4654 |
|
<t>/ CHANNEL_COUNT |
| 4655 |
|
</t> |
| 4656 |
|
<t>/ VOICE_COUNT |
| 4657 |
|
</t> |
| 4658 |
|
<t>/ STREAM_COUNT |
| 4659 |
|
</t> |
| 4660 |
|
<t>/ BUFFER_FILL |
| 4661 |
|
</t> |
| 4662 |
|
<t>/ CHANNEL_INFO |
| 4663 |
|
</t> |
| 4664 |
|
<t>/ MIDI_INSTRUMENT_MAP_COUNT |
| 4665 |
|
</t> |
| 4666 |
|
<t>/ MIDI_INSTRUMENT_MAP_INFO |
| 4667 |
|
</t> |
| 4668 |
|
<t>/ MIDI_INSTRUMENT_COUNT |
| 4669 |
|
</t> |
| 4670 |
|
<t>/ MIDI_INSTRUMENT_INFO |
| 4671 |
|
</t> |
| 4672 |
|
<t>/ MISCELLANEOUS |
| 4673 |
|
</t> |
| 4674 |
|
<t>/ TOTAL_VOICE_COUNT |
| 4675 |
|
</t> |
| 4676 |
|
</list> |
| 4677 |
|
</t> |
| 4678 |
|
<t>map_instruction = |
| 4679 |
|
<list> |
| 4680 |
|
<t>MIDI_INSTRUMENT SP midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value |
| 4681 |
|
</t> |
| 4682 |
|
<t>/ MIDI_INSTRUMENT SP midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP instr_load_mode |
| 4683 |
|
</t> |
| 4684 |
|
<t>/ MIDI_INSTRUMENT SP midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP entry_name |
| 4685 |
|
</t> |
| 4686 |
|
<t>/ MIDI_INSTRUMENT SP 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 |
| 4687 |
|
</t> |
| 4688 |
|
</list> |
| 4689 |
|
</t> |
| 4690 |
|
<t>unmap_instruction = |
| 4691 |
|
<list> |
| 4692 |
|
<t>MIDI_INSTRUMENT SP midi_map SP midi_bank SP midi_prog |
| 4693 |
|
</t> |
| 4694 |
|
</list> |
| 4695 |
|
</t> |
| 4696 |
|
<t>remove_instruction = |
| 4697 |
|
<list> |
| 4698 |
|
<t>CHANNEL SP sampler_channel |
| 4699 |
|
</t> |
| 4700 |
|
<t>/ MIDI_INSTRUMENT_MAP SP midi_map |
| 4701 |
|
</t> |
| 4702 |
|
<t>/ MIDI_INSTRUMENT_MAP SP ALL |
| 4703 |
|
</t> |
| 4704 |
|
</list> |
| 4705 |
|
</t> |
| 4706 |
|
<t>get_instruction = |
| 4707 |
|
<list> |
| 4708 |
|
<t>AVAILABLE_ENGINES |
| 4709 |
|
</t> |
| 4710 |
|
<t>/ AVAILABLE_MIDI_INPUT_DRIVERS |
| 4711 |
|
</t> |
| 4712 |
|
<t>/ MIDI_INPUT_DRIVER SP INFO SP string |
| 4713 |
|
</t> |
| 4714 |
|
<t>/ MIDI_INPUT_DRIVER_PARAMETER SP INFO SP string SP string |
| 4715 |
|
</t> |
| 4716 |
|
<t>/ MIDI_INPUT_DRIVER_PARAMETER SP INFO SP string SP string SP key_val_list |
| 4717 |
|
</t> |
| 4718 |
|
<t>/ AVAILABLE_AUDIO_OUTPUT_DRIVERS |
| 4719 |
|
</t> |
| 4720 |
|
<t>/ AUDIO_OUTPUT_DRIVER SP INFO SP string |
| 4721 |
|
</t> |
| 4722 |
|
<t>/ AUDIO_OUTPUT_DRIVER_PARAMETER SP INFO SP string SP string |
| 4723 |
|
</t> |
| 4724 |
|
<t>/ AUDIO_OUTPUT_DRIVER_PARAMETER SP INFO SP string SP string SP key_val_list |
| 4725 |
|
</t> |
| 4726 |
|
<t>/ AUDIO_OUTPUT_DEVICES |
| 4727 |
|
</t> |
| 4728 |
|
<t>/ MIDI_INPUT_DEVICES |
| 4729 |
|
</t> |
| 4730 |
|
<t>/ AUDIO_OUTPUT_DEVICE SP INFO SP number |
| 4731 |
|
</t> |
| 4732 |
|
<t>/ MIDI_INPUT_DEVICE SP INFO SP number |
| 4733 |
|
</t> |
| 4734 |
|
<t>/ MIDI_INPUT_PORT SP INFO SP number SP number |
| 4735 |
|
</t> |
| 4736 |
|
<t>/ MIDI_INPUT_PORT_PARAMETER SP INFO SP number SP number SP string |
| 4737 |
|
</t> |
| 4738 |
|
<t>/ AUDIO_OUTPUT_CHANNEL SP INFO SP number SP number |
| 4739 |
|
</t> |
| 4740 |
|
<t>/ AUDIO_OUTPUT_CHANNEL_PARAMETER SP INFO SP number SP number SP string |
| 4741 |
|
</t> |
| 4742 |
|
<t>/ CHANNELS |
| 4743 |
|
</t> |
| 4744 |
|
<t>/ CHANNEL SP INFO SP sampler_channel |
| 4745 |
|
</t> |
| 4746 |
|
<t>/ CHANNEL SP BUFFER_FILL SP buffer_size_type SP sampler_channel |
| 4747 |
|
</t> |
| 4748 |
|
<t>/ CHANNEL SP STREAM_COUNT SP sampler_channel |
| 4749 |
|
</t> |
| 4750 |
|
<t>/ CHANNEL SP VOICE_COUNT SP sampler_channel |
| 4751 |
|
</t> |
| 4752 |
|
<t>/ ENGINE SP INFO SP engine_name |
| 4753 |
|
</t> |
| 4754 |
|
<t>/ SERVER SP INFO |
| 4755 |
|
</t> |
| 4756 |
|
<t>/ TOTAL_VOICE_COUNT |
| 4757 |
|
</t> |
| 4758 |
|
<t>/ TOTAL_VOICE_COUNT_MAX |
| 4759 |
|
</t> |
| 4760 |
|
<t>/ MIDI_INSTRUMENTS SP midi_map |
| 4761 |
|
</t> |
| 4762 |
|
<t>/ MIDI_INSTRUMENTS SP ALL |
| 4763 |
|
</t> |
| 4764 |
|
<t>/ MIDI_INSTRUMENT SP INFO SP midi_map SP midi_bank SP midi_prog |
| 4765 |
|
</t> |
| 4766 |
|
<t>/ MIDI_INSTRUMENT_MAPS |
| 4767 |
|
</t> |
| 4768 |
|
<t>/ MIDI_INSTRUMENT_MAP SP INFO SP midi_map |
| 4769 |
|
</t> |
| 4770 |
|
<t>/ FX_SENDS SP sampler_channel |
| 4771 |
|
</t> |
| 4772 |
|
<t>/ FX_SEND SP INFO SP sampler_channel SP fx_send_id |
| 4773 |
|
</t> |
| 4774 |
|
</list> |
| 4775 |
|
</t> |
| 4776 |
|
<t>set_instruction = |
| 4777 |
|
<list> |
| 4778 |
|
<t>AUDIO_OUTPUT_DEVICE_PARAMETER SP number SP string '=' param_val_list |
| 4779 |
|
</t> |
| 4780 |
|
<t>/ AUDIO_OUTPUT_CHANNEL_PARAMETER SP number SP number SP string '=' param_val_list |
| 4781 |
|
</t> |
| 4782 |
|
<t>/ MIDI_INPUT_DEVICE_PARAMETER SP number SP string '=' param_val_list |
| 4783 |
|
</t> |
| 4784 |
|
<t>/ MIDI_INPUT_PORT_PARAMETER SP number SP number SP string '=' param_val_list |
| 4785 |
|
</t> |
| 4786 |
|
<t>/ CHANNEL SP set_chan_instruction |
| 4787 |
|
</t> |
| 4788 |
|
<t>/ MIDI_INSTRUMENT_MAP SP NAME SP midi_map SP map_name |
| 4789 |
|
</t> |
| 4790 |
|
<t>/ FX_SEND SP AUDIO_OUTPUT_CHANNEL SP sampler_channel SP fx_send_id SP audio_channel_index SP audio_channel_index |
| 4791 |
|
</t> |
| 4792 |
|
<t>/ ECHO SP boolean |
| 4793 |
|
</t> |
| 4794 |
|
</list> |
| 4795 |
|
</t> |
| 4796 |
|
<t>create_instruction = |
| 4797 |
|
<list> |
| 4798 |
|
<t>AUDIO_OUTPUT_DEVICE SP string SP key_val_list |
| 4799 |
|
</t> |
| 4800 |
|
<t>/ AUDIO_OUTPUT_DEVICE SP string |
| 4801 |
|
</t> |
| 4802 |
|
<t>/ MIDI_INPUT_DEVICE SP string SP key_val_list |
| 4803 |
|
</t> |
| 4804 |
|
<t>/ MIDI_INPUT_DEVICE SP string |
| 4805 |
|
</t> |
| 4806 |
|
<t>/ FX_SEND SP sampler_channel SP midi_ctrl |
| 4807 |
|
</t> |
| 4808 |
|
<t>/ FX_SEND SP sampler_channel SP midi_ctrl SP fx_send_name |
| 4809 |
|
</t> |
| 4810 |
|
</list> |
| 4811 |
|
</t> |
| 4812 |
|
<t>reset_instruction = |
| 4813 |
|
<list> |
| 4814 |
|
<t>CHANNEL SP sampler_channel |
| 4815 |
|
</t> |
| 4816 |
|
</list> |
| 4817 |
|
</t> |
| 4818 |
|
<t>clear_instruction = |
| 4819 |
|
<list> |
| 4820 |
|
<t>MIDI_INSTRUMENTS SP midi_map |
| 4821 |
|
</t> |
| 4822 |
|
<t>/ MIDI_INSTRUMENTS SP ALL |
| 4823 |
|
</t> |
| 4824 |
|
</list> |
| 4825 |
|
</t> |
| 4826 |
|
<t>destroy_instruction = |
| 4827 |
|
<list> |
| 4828 |
|
<t>AUDIO_OUTPUT_DEVICE SP number |
| 4829 |
|
</t> |
| 4830 |
|
<t>/ MIDI_INPUT_DEVICE SP number |
| 4831 |
|
</t> |
| 4832 |
|
<t>/ FX_SEND SP sampler_channel SP fx_send_id |
| 4833 |
|
</t> |
| 4834 |
|
</list> |
| 4835 |
|
</t> |
| 4836 |
|
<t>load_instruction = |
| 4837 |
|
<list> |
| 4838 |
|
<t>INSTRUMENT SP load_instr_args |
| 4839 |
|
</t> |
| 4840 |
|
<t>/ ENGINE SP load_engine_args |
| 4841 |
|
</t> |
| 4842 |
|
</list> |
| 4843 |
|
</t> |
| 4844 |
|
<t>set_chan_instruction = |
| 4845 |
|
<list> |
| 4846 |
|
<t>AUDIO_OUTPUT_DEVICE SP sampler_channel SP device_index |
| 4847 |
|
</t> |
| 4848 |
|
<t>/ AUDIO_OUTPUT_CHANNEL SP sampler_channel SP audio_channel_index SP audio_channel_index |
| 4849 |
|
</t> |
| 4850 |
|
<t>/ AUDIO_OUTPUT_TYPE SP sampler_channel SP audio_output_type_name |
| 4851 |
|
</t> |
| 4852 |
|
<t>/ MIDI_INPUT SP sampler_channel SP device_index SP midi_input_port_index SP midi_input_channel_index |
| 4853 |
|
</t> |
| 4854 |
|
<t>/ MIDI_INPUT_DEVICE SP sampler_channel SP device_index |
| 4855 |
|
</t> |
| 4856 |
|
<t>/ MIDI_INPUT_PORT SP sampler_channel SP midi_input_port_index |
| 4857 |
|
</t> |
| 4858 |
|
<t>/ MIDI_INPUT_CHANNEL SP sampler_channel SP midi_input_channel_index |
| 4859 |
|
</t> |
| 4860 |
|
<t>/ MIDI_INPUT_TYPE SP sampler_channel SP midi_input_type_name |
| 4861 |
|
</t> |
| 4862 |
|
<t>/ VOLUME SP sampler_channel SP volume_value |
| 4863 |
|
</t> |
| 4864 |
|
<t>/ MUTE SP sampler_channel SP boolean |
| 4865 |
|
</t> |
| 4866 |
|
<t>/ SOLO SP sampler_channel SP boolean |
| 4867 |
|
</t> |
| 4868 |
|
<t>/ MIDI_INSTRUMENT_MAP SP sampler_channel SP midi_map |
| 4869 |
|
</t> |
| 4870 |
|
<t>/ MIDI_INSTRUMENT_MAP SP sampler_channel SP NONE |
| 4871 |
|
</t> |
| 4872 |
|
<t>/ MIDI_INSTRUMENT_MAP SP sampler_channel SP DEFAULT |
| 4873 |
|
</t> |
| 4874 |
|
</list> |
| 4875 |
|
</t> |
| 4876 |
|
<t>key_val_list = |
| 4877 |
|
<list> |
| 4878 |
|
<t>string '=' param_val_list |
| 4879 |
|
</t> |
| 4880 |
|
<t>/ key_val_list SP string '=' param_val_list |
| 4881 |
|
</t> |
| 4882 |
|
</list> |
| 4883 |
|
</t> |
| 4884 |
|
<t>buffer_size_type = |
| 4885 |
|
<list> |
| 4886 |
|
<t>BYTES |
| 4887 |
|
</t> |
| 4888 |
|
<t>/ PERCENTAGE |
| 4889 |
|
</t> |
| 4890 |
|
</list> |
| 4891 |
|
</t> |
| 4892 |
|
<t>list_instruction = |
| 4893 |
|
<list> |
| 4894 |
|
<t>AUDIO_OUTPUT_DEVICES |
| 4895 |
|
</t> |
| 4896 |
|
<t>/ MIDI_INPUT_DEVICES |
| 4897 |
|
</t> |
| 4898 |
|
<t>/ CHANNELS |
| 4899 |
|
</t> |
| 4900 |
|
<t>/ AVAILABLE_ENGINES |
| 4901 |
|
</t> |
| 4902 |
|
<t>/ AVAILABLE_MIDI_INPUT_DRIVERS |
| 4903 |
|
</t> |
| 4904 |
|
<t>/ AVAILABLE_AUDIO_OUTPUT_DRIVERS |
| 4905 |
|
</t> |
| 4906 |
|
<t>/ MIDI_INSTRUMENTS SP midi_map |
| 4907 |
|
</t> |
| 4908 |
|
<t>/ MIDI_INSTRUMENTS SP ALL |
| 4909 |
|
</t> |
| 4910 |
|
<t>/ MIDI_INSTRUMENT_MAPS |
| 4911 |
|
</t> |
| 4912 |
|
<t>/ FX_SENDS SP sampler_channel |
| 4913 |
|
</t> |
| 4914 |
|
</list> |
| 4915 |
|
</t> |
| 4916 |
|
<t>load_instr_args = |
| 4917 |
|
<list> |
| 4918 |
|
<t>filename SP instrument_index SP sampler_channel |
| 4919 |
|
</t> |
| 4920 |
|
<t>/ NON_MODAL SP filename SP instrument_index SP sampler_channel |
| 4921 |
|
</t> |
| 4922 |
|
</list> |
| 4923 |
|
</t> |
| 4924 |
|
<t>load_engine_args = |
| 4925 |
|
<list> |
| 4926 |
|
<t>engine_name SP sampler_channel |
| 4927 |
|
</t> |
| 4928 |
|
</list> |
| 4929 |
|
</t> |
| 4930 |
|
<t>instr_load_mode = |
| 4931 |
|
<list> |
| 4932 |
|
<t>ON_DEMAND |
| 4933 |
|
</t> |
| 4934 |
|
<t>/ ON_DEMAND_HOLD |
| 4935 |
|
</t> |
| 4936 |
|
<t>/ PERSISTENT |
| 4937 |
|
</t> |
| 4938 |
|
</list> |
| 4939 |
|
</t> |
| 4940 |
|
<t>device_index = |
| 4941 |
|
<list> |
| 4942 |
|
<t>number |
| 4943 |
|
</t> |
| 4944 |
|
</list> |
| 4945 |
|
</t> |
| 4946 |
|
<t>audio_channel_index = |
| 4947 |
|
<list> |
| 4948 |
|
<t>number |
| 4949 |
|
</t> |
| 4950 |
|
</list> |
| 4951 |
|
</t> |
| 4952 |
|
<t>audio_output_type_name = |
| 4953 |
|
<list> |
| 4954 |
|
<t>string |
| 4955 |
|
</t> |
| 4956 |
|
</list> |
| 4957 |
|
</t> |
| 4958 |
|
<t>midi_input_port_index = |
| 4959 |
|
<list> |
| 4960 |
|
<t>number |
| 4961 |
|
</t> |
| 4962 |
|
</list> |
| 4963 |
|
</t> |
| 4964 |
|
<t>midi_input_channel_index = |
| 4965 |
|
<list> |
| 4966 |
|
<t>number |
| 4967 |
|
</t> |
| 4968 |
|
<t>/ ALL |
| 4969 |
|
</t> |
| 4970 |
|
</list> |
| 4971 |
|
</t> |
| 4972 |
|
<t>midi_input_type_name = |
| 4973 |
|
<list> |
| 4974 |
|
<t>string |
| 4975 |
|
</t> |
| 4976 |
|
</list> |
| 4977 |
|
</t> |
| 4978 |
|
<t>midi_map = |
| 4979 |
|
<list> |
| 4980 |
|
<t>number |
| 4981 |
|
</t> |
| 4982 |
|
</list> |
| 4983 |
|
</t> |
| 4984 |
|
<t>midi_bank = |
| 4985 |
|
<list> |
| 4986 |
|
<t>number |
| 4987 |
|
</t> |
| 4988 |
|
</list> |
| 4989 |
|
</t> |
| 4990 |
|
<t>midi_prog = |
| 4991 |
|
<list> |
| 4992 |
|
<t>number |
| 4993 |
|
</t> |
| 4994 |
|
</list> |
| 4995 |
|
</t> |
| 4996 |
|
<t>midi_ctrl = |
| 4997 |
|
<list> |
| 4998 |
|
<t>number |
| 4999 |
|
</t> |
| 5000 |
|
</list> |
| 5001 |
|
</t> |
| 5002 |
|
<t>volume_value = |
| 5003 |
|
<list> |
| 5004 |
|
<t>dotnum |
| 5005 |
|
</t> |
| 5006 |
|
<t>/ number |
| 5007 |
|
</t> |
| 5008 |
|
</list> |
| 5009 |
|
</t> |
| 5010 |
|
<t>sampler_channel = |
| 5011 |
|
<list> |
| 5012 |
|
<t>number |
| 5013 |
|
</t> |
| 5014 |
|
</list> |
| 5015 |
|
</t> |
| 5016 |
|
<t>instrument_index = |
| 5017 |
|
<list> |
| 5018 |
|
<t>number |
| 5019 |
|
</t> |
| 5020 |
|
</list> |
| 5021 |
|
</t> |
| 5022 |
|
<t>fx_send_id = |
| 5023 |
|
<list> |
| 5024 |
|
<t>number |
| 5025 |
|
</t> |
| 5026 |
|
</list> |
| 5027 |
|
</t> |
| 5028 |
|
<t>engine_name = |
| 5029 |
|
<list> |
| 5030 |
|
<t>string |
| 5031 |
|
</t> |
| 5032 |
|
</list> |
| 5033 |
|
</t> |
| 5034 |
|
<t>filename = |
| 5035 |
|
<list> |
| 5036 |
|
<t>stringval |
| 5037 |
|
</t> |
| 5038 |
|
</list> |
| 5039 |
|
</t> |
| 5040 |
|
<t>map_name = |
| 5041 |
|
<list> |
| 5042 |
|
<t>stringval |
| 5043 |
|
</t> |
| 5044 |
|
</list> |
| 5045 |
|
</t> |
| 5046 |
|
<t>entry_name = |
| 5047 |
|
<list> |
| 5048 |
|
<t>stringval |
| 5049 |
|
</t> |
| 5050 |
|
</list> |
| 5051 |
|
</t> |
| 5052 |
|
<t>fx_send_name = |
| 5053 |
|
<list> |
| 5054 |
|
<t>stringval |
| 5055 |
|
</t> |
| 5056 |
|
</list> |
| 5057 |
|
</t> |
| 5058 |
|
<t>param_val_list = |
| 5059 |
|
<list> |
| 5060 |
|
<t>param_val |
| 5061 |
|
</t> |
| 5062 |
|
<t>/ param_val_list','param_val |
| 5063 |
|
</t> |
| 5064 |
|
</list> |
| 5065 |
|
</t> |
| 5066 |
|
<t>param_val = |
| 5067 |
|
<list> |
| 5068 |
|
<t>string |
| 5069 |
|
</t> |
| 5070 |
|
<t>/ stringval |
| 5071 |
|
</t> |
| 5072 |
|
<t>/ number |
| 5073 |
|
</t> |
| 5074 |
|
<t>/ dotnum |
| 5075 |
|
</t> |
| 5076 |
|
</list> |
| 5077 |
|
</t> |
| 5078 |
|
|
| 5079 |
|
<!-- GRAMMAR_BNF_END - do NOT delete or modify this line !!! --> |
| 5080 |
</section> |
</section> |
| 5081 |
|
|
| 5082 |
<section title="Events"> |
<section title="Events" anchor="events"> |
| 5083 |
<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> |
| 5084 |
|
|
| 5085 |
<section title="Number of sampler channels changed"> |
<section title="Number of audio output devices changed" anchor="SUBSCRIBE AUDIO_OUTPUT_DEVICE_COUNT"> |
| 5086 |
|
<t>Client may want to be notified when the total number of audio output devices on the |
| 5087 |
|
back-end changes by issuing the following command:</t> |
| 5088 |
|
<t> |
| 5089 |
|
<list> |
| 5090 |
|
<t>SUBSCRIBE AUDIO_OUTPUT_DEVICE_COUNT</t> |
| 5091 |
|
</list> |
| 5092 |
|
</t> |
| 5093 |
|
<t>Server will start sending the following notification messages:</t> |
| 5094 |
|
<t> |
| 5095 |
|
<list> |
| 5096 |
|
<t>"NOTIFY:AUDIO_OUTPUT_DEVICE_COUNT:<devices>"</t> |
| 5097 |
|
</list> |
| 5098 |
|
</t> |
| 5099 |
|
<t>where <devices> will be replaced by the new number |
| 5100 |
|
of audio output devices.</t> |
| 5101 |
|
</section> |
| 5102 |
|
|
| 5103 |
|
<section title="Audio output device's settings changed" anchor="SUBSCRIBE AUDIO_OUTPUT_DEVICE_INFO"> |
| 5104 |
|
<t>Client may want to be notified when changes were made to audio output devices on the |
| 5105 |
|
back-end by issuing the following command:</t> |
| 5106 |
|
<t> |
| 5107 |
|
<list> |
| 5108 |
|
<t>SUBSCRIBE AUDIO_OUTPUT_DEVICE_INFO</t> |
| 5109 |
|
</list> |
| 5110 |
|
</t> |
| 5111 |
|
<t>Server will start sending the following notification messages:</t> |
| 5112 |
|
<t> |
| 5113 |
|
<list> |
| 5114 |
|
<t>"NOTIFY:AUDIO_OUTPUT_DEVICE_INFO:<device-id>"</t> |
| 5115 |
|
</list> |
| 5116 |
|
</t> |
| 5117 |
|
<t>where <device-id> will be replaced by the numerical ID of the audio output device, |
| 5118 |
|
which settings has been changed. The front-end will have to send |
| 5119 |
|
the respective command to actually get the audio output device info. Because these messages |
| 5120 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 5121 |
|
time events happening on the server, it is believed that an empty notification |
| 5122 |
|
message is sufficient here.</t> |
| 5123 |
|
</section> |
| 5124 |
|
|
| 5125 |
|
<section title="Number of MIDI input devices changed" anchor="SUBSCRIBE MIDI_INPUT_DEVICE_COUNT"> |
| 5126 |
|
<t>Client may want to be notified when the total number of MIDI input devices on the |
| 5127 |
|
back-end changes by issuing the following command:</t> |
| 5128 |
|
<t> |
| 5129 |
|
<list> |
| 5130 |
|
<t>SUBSCRIBE MIDI_INPUT_DEVICE_COUNT</t> |
| 5131 |
|
</list> |
| 5132 |
|
</t> |
| 5133 |
|
<t>Server will start sending the following notification messages:</t> |
| 5134 |
|
<t> |
| 5135 |
|
<list> |
| 5136 |
|
<t>"NOTIFY:MIDI_INPUT_DEVICE_COUNT:<devices>"</t> |
| 5137 |
|
</list> |
| 5138 |
|
</t> |
| 5139 |
|
<t>where <devices> will be replaced by the new number |
| 5140 |
|
of MIDI input devices.</t> |
| 5141 |
|
</section> |
| 5142 |
|
|
| 5143 |
|
<section title="MIDI input device's settings changed" anchor="SUBSCRIBE MIDI_INPUT_DEVICE_INFO"> |
| 5144 |
|
<t>Client may want to be notified when changes were made to MIDI input devices on the |
| 5145 |
|
back-end by issuing the following command:</t> |
| 5146 |
|
<t> |
| 5147 |
|
<list> |
| 5148 |
|
<t>SUBSCRIBE MIDI_INPUT_DEVICE_INFO</t> |
| 5149 |
|
</list> |
| 5150 |
|
</t> |
| 5151 |
|
<t>Server will start sending the following notification messages:</t> |
| 5152 |
|
<t> |
| 5153 |
|
<list> |
| 5154 |
|
<t>"NOTIFY:MIDI_INPUT_DEVICE_INFO:<device-id>"</t> |
| 5155 |
|
</list> |
| 5156 |
|
</t> |
| 5157 |
|
<t>where <device-id> will be replaced by the numerical ID of the MIDI input device, |
| 5158 |
|
which settings has been changed. The front-end will have to send |
| 5159 |
|
the respective command to actually get the MIDI input device info. Because these messages |
| 5160 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 5161 |
|
time events happening on the server, it is believed that an empty notification |
| 5162 |
|
message is sufficient here.</t> |
| 5163 |
|
</section> |
| 5164 |
|
|
| 5165 |
|
<section title="Number of sampler channels changed" anchor="SUBSCRIBE CHANNEL_COUNT"> |
| 5166 |
<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 |
| 5167 |
back-end changes by issuing the following command:</t> |
back-end changes by issuing the following command:</t> |
| 5168 |
<t> |
<t> |
| 5169 |
<list> |
<list> |
| 5170 |
<t>SUBSCRIBE CHANNELS</t> |
<t>SUBSCRIBE CHANNEL_COUNT</t> |
| 5171 |
</list> |
</list> |
| 5172 |
</t> |
</t> |
| 5173 |
<t>Server will start sending the following notification messages:</t> |
<t>Server will start sending the following notification messages:</t> |
| 5174 |
<t> |
<t> |
| 5175 |
<list> |
<list> |
| 5176 |
<t>"NOTIFY:CHANNELS:<channels>"</t> |
<t>"NOTIFY:CHANNEL_COUNT:<channels>"</t> |
| 5177 |
</list> |
</list> |
| 5178 |
</t> |
</t> |
| 5179 |
<t>where <channels> will be replaced by the new number |
<t>where <channels> will be replaced by the new number |
| 5180 |
of sampler channels.</t> |
of sampler channels.</t> |
| 5181 |
</section> |
</section> |
| 5182 |
|
|
| 5183 |
<section title="Number of active voices changed"> |
<section title="Number of active voices changed" anchor="SUBSCRIBE VOICE_COUNT"> |
| 5184 |
<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 |
| 5185 |
back-end changes by issuing the following command:</t> |
back-end changes by issuing the following command:</t> |
| 5186 |
<t> |
<t> |
| 5191 |
<t>Server will start sending the following notification messages:</t> |
<t>Server will start sending the following notification messages:</t> |
| 5192 |
<t> |
<t> |
| 5193 |
<list> |
<list> |
| 5194 |
<t>"NOTIFY:VOICE_COUNT:<sampler-channel> <voices>></t> |
<t>"NOTIFY:VOICE_COUNT:<sampler-channel> <voices></t> |
| 5195 |
</list> |
</list> |
| 5196 |
</t> |
</t> |
| 5197 |
<t>where <sampler-channel> will be replaced by the sampler channel the |
<t>where <sampler-channel> will be replaced by the sampler channel the |
| 5198 |
voice count change occurred and <voices>> by the new number of |
voice count change occurred and <voices> by the new number of |
| 5199 |
active voices on that channel.</t> |
active voices on that channel.</t> |
| 5200 |
</section> |
</section> |
| 5201 |
|
|
| 5202 |
<section title="Number of active disk streams changed"> |
<section title="Number of active disk streams changed" anchor="SUBSCRIBE STREAM_COUNT"> |
| 5203 |
<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 |
| 5204 |
changes by issuing the following command: SUBSCRIBE STREAM_COUNT</t> |
changes by issuing the following command: SUBSCRIBE STREAM_COUNT</t> |
| 5205 |
<t> |
<t> |
| 5218 |
active disk streams on that channel.</t> |
active disk streams on that channel.</t> |
| 5219 |
</section> |
</section> |
| 5220 |
|
|
| 5221 |
<section title="Disk stream buffer fill state changed"> |
<section title="Disk stream buffer fill state changed" anchor="SUBSCRIBE BUFFER_FILL"> |
| 5222 |
<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 |
| 5223 |
changes by issuing the following command:</t> |
on the back-end changes by issuing the following command:</t> |
| 5224 |
<t> |
<t> |
| 5225 |
<list> |
<list> |
| 5226 |
<t>SUBSCRIBE BUFFER_FILL</t> |
<t>SUBSCRIBE BUFFER_FILL</t> |
| 5233 |
</list> |
</list> |
| 5234 |
</t> |
</t> |
| 5235 |
<t>where <sampler-channel> will be replaced by the sampler channel the |
<t>where <sampler-channel> will be replaced by the sampler channel the |
| 5236 |
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 |
| 5237 |
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" /> |
| 5238 |
"GET CHANNEL BUFFER_FILL PERCENTAGE" was issued on this channel.</t> |
as if the <xref target="GET CHANNEL BUFFER_FILL"> |
| 5239 |
|
"GET CHANNEL BUFFER_FILL PERCENTAGE"</xref> command was issued on this channel.</t> |
| 5240 |
</section> |
</section> |
| 5241 |
|
|
| 5242 |
<section title="Channel information changed"> |
<section title="Channel information changed" anchor="SUBSCRIBE CHANNEL_INFO"> |
| 5243 |
<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 |
| 5244 |
back-end changes by issuing the following command:</t> |
back-end by issuing the following command:</t> |
| 5245 |
<t> |
<t> |
| 5246 |
<list> |
<list> |
| 5247 |
<t>SUBSCRIBE INFO</t> |
<t>SUBSCRIBE CHANNEL_INFO</t> |
| 5248 |
</list> |
</list> |
| 5249 |
</t> |
</t> |
| 5250 |
<t>Server will start sending the following notification messages:</t> |
<t>Server will start sending the following notification messages:</t> |
| 5251 |
<t> |
<t> |
| 5252 |
<list> |
<list> |
| 5253 |
<t>"NOTIFY:INFO:<sampler-channel>"</t> |
<t>"NOTIFY:CHANNEL_INFO:<sampler-channel>"</t> |
| 5254 |
</list> |
</list> |
| 5255 |
</t> |
</t> |
| 5256 |
<t>where <sampler-channel> will be replaced by the sampler channel the |
<t>where <sampler-channel> will be replaced by the sampler channel the |
| 5261 |
message is sufficient here.</t> |
message is sufficient here.</t> |
| 5262 |
</section> |
</section> |
| 5263 |
|
|
| 5264 |
<section title="Miscellaneous and debugging events"> |
<section title="Total number of active voices changed" anchor="SUBSCRIBE TOTAL_VOICE_COUNT"> |
| 5265 |
|
<t>Client may want to be notified when the total number of voices on the |
| 5266 |
|
back-end changes by issuing the following command:</t> |
| 5267 |
|
<t> |
| 5268 |
|
<list> |
| 5269 |
|
<t>SUBSCRIBE TOTAL_VOICE_COUNT</t> |
| 5270 |
|
</list> |
| 5271 |
|
</t> |
| 5272 |
|
<t>Server will start sending the following notification messages:</t> |
| 5273 |
|
<t> |
| 5274 |
|
<list> |
| 5275 |
|
<t>"NOTIFY:TOTAL_VOICE_COUNT:<voices></t> |
| 5276 |
|
</list> |
| 5277 |
|
</t> |
| 5278 |
|
<t>where <voices> will be replaced by the new number of |
| 5279 |
|
all currently active voices.</t> |
| 5280 |
|
</section> |
| 5281 |
|
|
| 5282 |
|
<section title="Number of MIDI instrument maps changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_MAP_COUNT"> |
| 5283 |
|
<t>Client may want to be notified when the number of MIDI instrument maps on the |
| 5284 |
|
back-end changes by issuing the following command:</t> |
| 5285 |
|
<t> |
| 5286 |
|
<list> |
| 5287 |
|
<t>SUBSCRIBE MIDI_INSTRUMENT_MAP_COUNT</t> |
| 5288 |
|
</list> |
| 5289 |
|
</t> |
| 5290 |
|
<t>Server will start sending the following notification messages:</t> |
| 5291 |
|
<t> |
| 5292 |
|
<list> |
| 5293 |
|
<t>"NOTIFY:MIDI_INSTRUMENT_MAP_COUNT:<maps>"</t> |
| 5294 |
|
</list> |
| 5295 |
|
</t> |
| 5296 |
|
<t>where <maps> will be replaced by the new number |
| 5297 |
|
of MIDI instrument maps.</t> |
| 5298 |
|
</section> |
| 5299 |
|
|
| 5300 |
|
<section title="MIDI instrument map information changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO"> |
| 5301 |
|
<t>Client may want to be notified when changes were made to MIDI instrument maps on the |
| 5302 |
|
back-end by issuing the following command:</t> |
| 5303 |
|
<t> |
| 5304 |
|
<list> |
| 5305 |
|
<t>SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO</t> |
| 5306 |
|
</list> |
| 5307 |
|
</t> |
| 5308 |
|
<t>Server will start sending the following notification messages:</t> |
| 5309 |
|
<t> |
| 5310 |
|
<list> |
| 5311 |
|
<t>"NOTIFY:MIDI_INSTRUMENT_MAP_INFO:<map-id>"</t> |
| 5312 |
|
</list> |
| 5313 |
|
</t> |
| 5314 |
|
<t>where <map-id> will be replaced by the numerical ID of the MIDI instrument map, |
| 5315 |
|
for which information changes occurred. The front-end will have to send |
| 5316 |
|
the respective command to actually get the MIDI instrument map info. Because these messages |
| 5317 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 5318 |
|
time events happening on the server, it is believed that an empty notification |
| 5319 |
|
message is sufficient here.</t> |
| 5320 |
|
</section> |
| 5321 |
|
|
| 5322 |
|
<section title="Number of MIDI instruments changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_COUNT"> |
| 5323 |
|
<t>Client may want to be notified when the number of MIDI instrument maps on the |
| 5324 |
|
back-end changes by issuing the following command:</t> |
| 5325 |
|
<t> |
| 5326 |
|
<list> |
| 5327 |
|
<t>SUBSCRIBE MIDI_INSTRUMENT_COUNT</t> |
| 5328 |
|
</list> |
| 5329 |
|
</t> |
| 5330 |
|
<t>Server will start sending the following notification messages:</t> |
| 5331 |
|
<t> |
| 5332 |
|
<list> |
| 5333 |
|
<t>"NOTIFY:MIDI_INSTRUMENT_COUNT:<map-id> <instruments>"</t> |
| 5334 |
|
</list> |
| 5335 |
|
</t> |
| 5336 |
|
<t>where <map-id> is the numerical ID of the MIDI instrument map, in which |
| 5337 |
|
the nuber of instruments has changed and <instruments> will be replaced by |
| 5338 |
|
the new number of MIDI instruments in the specified map.</t> |
| 5339 |
|
</section> |
| 5340 |
|
|
| 5341 |
|
<section title="MIDI instrument information changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_INFO"> |
| 5342 |
|
<t>Client may want to be notified when changes were made to MIDI instruments on the |
| 5343 |
|
back-end by issuing the following command:</t> |
| 5344 |
|
<t> |
| 5345 |
|
<list> |
| 5346 |
|
<t>SUBSCRIBE MIDI_INSTRUMENT_INFO</t> |
| 5347 |
|
</list> |
| 5348 |
|
</t> |
| 5349 |
|
<t>Server will start sending the following notification messages:</t> |
| 5350 |
|
<t> |
| 5351 |
|
<list> |
| 5352 |
|
<t>"NOTIFY:MIDI_INSTRUMENT_INFO:<map-id> <bank> <program>"</t> |
| 5353 |
|
</list> |
| 5354 |
|
</t> |
| 5355 |
|
<t>where <map-id> will be replaced by the numerical ID of the MIDI instrument map, |
| 5356 |
|
in which a MIDI instrument is changed. <bank> and <program> specifies |
| 5357 |
|
the location of the changed MIDI instrument in the map. The front-end will have to send |
| 5358 |
|
the respective command to actually get the MIDI instrument info. Because these messages |
| 5359 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 5360 |
|
time events happening on the server, it is believed that an empty notification |
| 5361 |
|
message is sufficient here.</t> |
| 5362 |
|
</section> |
| 5363 |
|
|
| 5364 |
|
<section title="Miscellaneous and debugging events" anchor="SUBSCRIBE MISCELLANEOUS"> |
| 5365 |
<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 |
| 5366 |
the server by issuing the following command:</t> |
the server by issuing the following command:</t> |
| 5367 |
<t> |
<t> |
| 5397 |
<t>Rui Nuno Capela</t> |
<t>Rui Nuno Capela</t> |
| 5398 |
<t>Vladimir Senkov</t> |
<t>Vladimir Senkov</t> |
| 5399 |
<t>Mark Knecht</t> |
<t>Mark Knecht</t> |
| 5400 |
|
<t>Grigor Iliev</t> |
| 5401 |
</list> |
</list> |
| 5402 |
</t> |
</t> |
| 5403 |
</section> |
</section> |
| 5405 |
</middle> |
</middle> |
| 5406 |
|
|
| 5407 |
<back> |
<back> |
| 5408 |
<references>&rfc2119;</references> |
<references> |
| 5409 |
|
<reference anchor="RFC2119"> |
| 5410 |
|
<front> |
| 5411 |
|
<title>Key words for use in RFCs to Indicate Requirement Levels</title> |
| 5412 |
|
<author initials="S." surname="Bradner" fullname="Scott Bradner"> |
| 5413 |
|
<organization>Harvard University</organization> |
| 5414 |
|
</author> |
| 5415 |
|
<date year="1997"></date> |
| 5416 |
|
</front> |
| 5417 |
|
<seriesInfo name="RFC" value="2119" /> |
| 5418 |
|
</reference> |
| 5419 |
|
<reference anchor="RFC793"> |
| 5420 |
|
<front> |
| 5421 |
|
<title>TRANSMISSION CONTROL PROTOCOL</title> |
| 5422 |
|
<author> |
| 5423 |
|
<organization>Defense Advanced Research Projects Agency</organization> |
| 5424 |
|
</author> |
| 5425 |
|
<date year="1981"></date> |
| 5426 |
|
</front> |
| 5427 |
|
<seriesInfo name="RFC" value="793" /> |
| 5428 |
|
</reference> |
| 5429 |
|
<reference anchor="RFC2234"> |
| 5430 |
|
<front> |
| 5431 |
|
<title>Augmented BNF for Syntax Specifications</title> |
| 5432 |
|
<author initials="D.H." surname="Crocker" fullname="David H. Crocker"> |
| 5433 |
|
<organization>Internet Mail Consortium</organization> |
| 5434 |
|
</author> |
| 5435 |
|
<author initials="P." surname="Overell" fullname="Paul Overell"> |
| 5436 |
|
<organization>Demon Internet Ltd</organization> |
| 5437 |
|
</author> |
| 5438 |
|
<date year="1997"></date> |
| 5439 |
|
</front> |
| 5440 |
|
<seriesInfo name="RFC" value="2234" /> |
| 5441 |
|
</reference> |
| 5442 |
|
</references> |
| 5443 |
</back> |
</back> |
| 5444 |
|
|
| 5445 |
</rfc> |
</rfc> |
Parent Directory
| 
Revision Log
| 
Patch