16 |
to an annoying "missing Normative/Informative References" error message --> |
to an annoying "missing Normative/Informative References" error message --> |
17 |
<?rfc strict="no" ?> |
<?rfc strict="no" ?> |
18 |
|
|
19 |
<rfc category="std" ipr="full3978" docName="LSCP 1.2"> |
<rfc category="std" ipr="full3978" docName="LSCP 1.2cvs"> |
20 |
<front> |
<front> |
21 |
<title>LinuxSampler Control Protocol</title> |
<title>LinuxSampler Control Protocol (draft)</title> |
22 |
<author initials='C.S.' surname="Schoenebeck" fullname='C. |
<author initials='C.S.' surname="Schoenebeck" fullname='C. |
23 |
Schoenebeck'> |
Schoenebeck'> |
24 |
<organization> |
<organization> |
34 |
<email>schoenebeck at software minus engineering dot org</email> |
<email>schoenebeck at software minus engineering dot org</email> |
35 |
</address> |
</address> |
36 |
</author> |
</author> |
37 |
<date month="March" year="2007"/> |
<date month="June" year="2007"/> |
38 |
<workgroup>LinuxSampler Developers</workgroup> |
<workgroup>LinuxSampler Developers</workgroup> |
39 |
<keyword>LSCP</keyword> |
<keyword>LSCP</keyword> |
40 |
<abstract> |
<abstract> |
61 |
(front-end) and server (LinuxSampler) respectively. Lines in |
(front-end) and server (LinuxSampler) respectively. Lines in |
62 |
examples must be interpreted as every line being CRLF |
examples must be interpreted as every line being CRLF |
63 |
terminated (carriage return character followed by line feed |
terminated (carriage return character followed by line feed |
64 |
character as defined in the ASCII standard), thus the following |
character as defined in the ASCII standard <xref target="RFC20"/>), |
65 |
example:</t> |
thus the following example:</t> |
66 |
|
|
67 |
<t> |
<t> |
68 |
<list> |
<list> |
2061 |
or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref> |
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 |
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 (encapsulated into apostrophes) or NONE (not encapsulated into apostrophes) |
2065 |
|
for specifying no value for parameters allowing a list of values.</t> |
2066 |
|
|
2067 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
2068 |
<t> |
<t> |
2089 |
<t>Example:</t> |
<t>Example:</t> |
2090 |
<t> |
<t> |
2091 |
<list> |
<list> |
2092 |
<t></t> |
<t>C: "SET MIDI_INPUT_PORT_PARAMETER 0 0 ALSA_SEQ_BINDINGS='20:0'"</t> |
2093 |
|
<t>S: "OK"</t> |
2094 |
|
</list> |
2095 |
|
</t> |
2096 |
|
<t> |
2097 |
|
<list> |
2098 |
|
<t>C: "SET MIDI_INPUT_PORT_PARAMETER 0 0 ALSA_SEQ_BINDINGS=NONE"</t> |
2099 |
|
<t>S: "OK"</t> |
2100 |
</list> |
</list> |
2101 |
</t> |
</t> |
2102 |
</section> |
</section> |
2121 |
number of the sampler channel the instrument should be assigned to. |
number of the sampler channel the instrument should be assigned to. |
2122 |
Each sampler channel can only have one instrument.</t> |
Each sampler channel can only have one instrument.</t> |
2123 |
|
|
2124 |
|
<t>Notice: since LSCP 1.2 the <filename> argument supports |
2125 |
|
escape characters for special characters (see chapter |
2126 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>" |
2127 |
|
for details) and accordingly backslash characters in the filename |
2128 |
|
MUST now be escaped as well!</t> |
2129 |
|
|
2130 |
<t>The difference between regular and NON_MODAL versions of the command |
<t>The difference between regular and NON_MODAL versions of the command |
2131 |
is that the regular command returns OK only after the instrument has been |
is that the regular command returns OK only after the instrument has been |
2132 |
fully loaded and the channel is ready to be used while NON_MODAL version |
fully loaded and the channel is ready to be used while NON_MODAL version |
3973 |
complies with (see <xref target="LSCP versioning" /> for details)</t> |
complies with (see <xref target="LSCP versioning" /> for details)</t> |
3974 |
</list> |
</list> |
3975 |
</t> |
</t> |
3976 |
|
<t>INSTRUMENTS_DB_SUPPORT - |
3977 |
|
<list> |
3978 |
|
<t>either yes or no, specifies whether the |
3979 |
|
sampler is build with instruments database support.</t> |
3980 |
|
</list> |
3981 |
|
</t> |
3982 |
</list> |
</list> |
3983 |
</t> |
</t> |
3984 |
</list> |
</list> |
4276 |
<list> |
<list> |
4277 |
<t>C: "GET MIDI_INSTRUMENT_MAP INFO 0"</t> |
<t>C: "GET MIDI_INSTRUMENT_MAP INFO 0"</t> |
4278 |
<t>S: "NAME: Standard Map"</t> |
<t>S: "NAME: Standard Map"</t> |
4279 |
|
<t> "DEFAULT: true"</t> |
4280 |
<t> "."</t> |
<t> "."</t> |
4281 |
</list> |
</list> |
4282 |
</t> |
</t> |
4339 |
index, <engine_name> a sampler engine name as returned by |
index, <engine_name> a sampler engine name as returned by |
4340 |
the <xref target="LIST AVAILABLE_ENGINES">"LIST AVAILABLE_ENGINES"</xref> |
the <xref target="LIST AVAILABLE_ENGINES">"LIST AVAILABLE_ENGINES"</xref> |
4341 |
command (not encapsulated into apostrophes), <filename> the name |
command (not encapsulated into apostrophes), <filename> the name |
4342 |
of the instrument's file to be deployed (encapsulated into apostrophes), |
of the instrument's file to be deployed (encapsulated into apostrophes, |
4343 |
|
supporting escape sequences as described in chapter |
4344 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>"), |
4345 |
<instrument_index> the index (integer value) of the instrument |
<instrument_index> the index (integer value) of the instrument |
4346 |
within the given file, <volume_value> reflects the master |
within the given file, <volume_value> reflects the master |
4347 |
volume of the instrument as optionally dotted number (where a |
volume of the instrument as optionally dotted number (where a |
4756 |
</section> |
</section> |
4757 |
</section> |
</section> |
4758 |
|
|
4759 |
|
|
4760 |
|
<section title="Managing Instruments Database" anchor="Managing Instruments Database"> |
4761 |
|
<t>The following commands describe how to use and manage |
4762 |
|
the instruments database.</t> |
4763 |
|
|
4764 |
|
<section title="Creating a new instrument directory" anchor="ADD DB_INSTRUMENT_DIRECTORY"> |
4765 |
|
<t>The front-end can add a new instrument directory to the |
4766 |
|
instruments database by sending the following command:</t> |
4767 |
|
<t> |
4768 |
|
<list> |
4769 |
|
<t>ADD DB_INSTRUMENT_DIRECTORY <dir></t> |
4770 |
|
</list> |
4771 |
|
</t> |
4772 |
|
<t>Where <dir> is the absolute path name of the directory |
4773 |
|
to be created (encapsulated into apostrophes).</t> |
4774 |
|
|
4775 |
|
<t>Possible Answers:</t> |
4776 |
|
<t> |
4777 |
|
<list> |
4778 |
|
<t>"OK" - |
4779 |
|
<list> |
4780 |
|
<t>on success</t> |
4781 |
|
</list> |
4782 |
|
</t> |
4783 |
|
<t>"ERR:<error-code>:<error-message>" - |
4784 |
|
<list> |
4785 |
|
<t>when the directory could not be created, which |
4786 |
|
can happen if the directory already exists or the |
4787 |
|
name contains not allowed symbols</t> |
4788 |
|
</list> |
4789 |
|
</t> |
4790 |
|
</list> |
4791 |
|
</t> |
4792 |
|
|
4793 |
|
<t>Examples:</t> |
4794 |
|
<t> |
4795 |
|
<list> |
4796 |
|
<t>C: "ADD DB_INSTRUMENT_DIRECTORY '/Piano Collection'"</t> |
4797 |
|
<t>S: "OK"</t> |
4798 |
|
</list> |
4799 |
|
</t> |
4800 |
|
</section> |
4801 |
|
|
4802 |
|
<section title="Deleting an instrument directory" anchor="REMOVE DB_INSTRUMENT_DIRECTORY"> |
4803 |
|
<t>The front-end can delete a particular instrument directory |
4804 |
|
from the instruments database by sending the following command:</t> |
4805 |
|
<t> |
4806 |
|
<list> |
4807 |
|
<t>REMOVE DB_INSTRUMENT_DIRECTORY [FORCE] <dir></t> |
4808 |
|
</list> |
4809 |
|
</t> |
4810 |
|
<t>Where <dir> is the absolute path name of the directory |
4811 |
|
to delete. The optional FORCE argument can be used to |
4812 |
|
force the deletion of a non-empty directory and all its content.</t> |
4813 |
|
|
4814 |
|
<t>Possible Answers:</t> |
4815 |
|
<t> |
4816 |
|
<list> |
4817 |
|
<t>"OK" - |
4818 |
|
<list> |
4819 |
|
<t>if the directory is deleted successfully</t> |
4820 |
|
</list> |
4821 |
|
</t> |
4822 |
|
<t>"ERR:<error-code>:<error-message>" - |
4823 |
|
<list> |
4824 |
|
<t>if the given directory does not exist, or |
4825 |
|
if trying to delete a non-empty directory, |
4826 |
|
without using the FORCE argument.</t> |
4827 |
|
</list> |
4828 |
|
</t> |
4829 |
|
</list> |
4830 |
|
</t> |
4831 |
|
|
4832 |
|
<t>Examples:</t> |
4833 |
|
<t> |
4834 |
|
<list> |
4835 |
|
<t>C: "REMOVE DB_INSTRUMENT_DIRECTORY FORCE '/Piano Collection'"</t> |
4836 |
|
<t>S: "OK"</t> |
4837 |
|
</list> |
4838 |
|
</t> |
4839 |
|
</section> |
4840 |
|
|
4841 |
|
<section title="Getting amount of instrument directories" anchor="GET DB_INSTRUMENT_DIRECTORIES"> |
4842 |
|
<t>The front-end can retrieve the current amount of |
4843 |
|
directories in a specific directory by sending the following command:</t> |
4844 |
|
<t> |
4845 |
|
<list> |
4846 |
|
<t>GET DB_INSTRUMENT_DIRECTORIES [RECURSIVE] <dir></t> |
4847 |
|
</list> |
4848 |
|
</t> |
4849 |
|
<t>Where <dir> should be replaced by the absolute path |
4850 |
|
name of the directory. If RECURSIVE is specified, the number of |
4851 |
|
all directories, including those located in subdirectories of the |
4852 |
|
specified directory, will be returned.</t> |
4853 |
|
|
4854 |
|
<t>Possible Answers:</t> |
4855 |
|
<t> |
4856 |
|
<list> |
4857 |
|
<t>The current number of instrument directories |
4858 |
|
in the specified directory.</t> |
4859 |
|
<t>"ERR:<error-code>:<error-message>" - |
4860 |
|
<list> |
4861 |
|
<t>if the given directory does not exist.</t> |
4862 |
|
</list> |
4863 |
|
</t> |
4864 |
|
</list> |
4865 |
|
</t> |
4866 |
|
|
4867 |
|
<t>Example:</t> |
4868 |
|
<t> |
4869 |
|
<list> |
4870 |
|
<t>C: "GET DB_INSTRUMENT_DIRECTORIES '/'"</t> |
4871 |
|
<t>S: "2"</t> |
4872 |
|
</list> |
4873 |
|
</t> |
4874 |
|
</section> |
4875 |
|
|
4876 |
|
<section title="Listing all directories in specific directory" anchor="LIST DB_INSTRUMENT_DIRECTORIES"> |
4877 |
|
<t>The front-end can retrieve the current list of directories |
4878 |
|
in specific directory by sending the following command:</t> |
4879 |
|
<t> |
4880 |
|
<list> |
4881 |
|
<t>LIST DB_INSTRUMENT_DIRECTORIES [RECURSIVE] <dir></t> |
4882 |
|
</list> |
4883 |
|
</t> |
4884 |
|
<t>Where <dir> should be replaced by the absolute path |
4885 |
|
name of the directory. If RECURSIVE is specified, the absolute path names |
4886 |
|
of all directories, including those located in subdirectories of the |
4887 |
|
specified directory, will be returned.</t> |
4888 |
|
|
4889 |
|
<t>Possible Answers:</t> |
4890 |
|
<t> |
4891 |
|
<list> |
4892 |
|
<t>A comma separated list of all instrument directories |
4893 |
|
(encapsulated into apostrophes) in the specified directory.</t> |
4894 |
|
<t>"ERR:<error-code>:<error-message>" - |
4895 |
|
<list> |
4896 |
|
<t>if the given directory does not exist.</t> |
4897 |
|
</list> |
4898 |
|
</t> |
4899 |
|
</list> |
4900 |
|
</t> |
4901 |
|
<t>Example:</t> |
4902 |
|
<t> |
4903 |
|
<list> |
4904 |
|
<t>C: "LIST DB_INSTRUMENT_DIRECTORIES '/'"</t> |
4905 |
|
<t>S: "'Piano Collection','Percussion Collection'"</t> |
4906 |
|
</list> |
4907 |
|
</t> |
4908 |
|
<t> |
4909 |
|
<list> |
4910 |
|
<t>C: "LIST DB_INSTRUMENT_DIRECTORIES RECURSIVE '/'"</t> |
4911 |
|
<t>S: "'/Piano Collection','/Piano Collection/Acoustic','/Piano Collection/Acoustic/New','/Percussion Collection'"</t> |
4912 |
|
</list> |
4913 |
|
</t> |
4914 |
|
</section> |
4915 |
|
|
4916 |
|
<section title="Getting instrument directory information" anchor="GET DB_INSTRUMENT_DIRECTORY INFO"> |
4917 |
|
<t>The front-end can ask for the current settings of an |
4918 |
|
instrument directory by sending the following command:</t> |
4919 |
|
<t> |
4920 |
|
<list> |
4921 |
|
<t>GET DB_INSTRUMENT_DIRECTORY INFO <dir></t> |
4922 |
|
</list> |
4923 |
|
</t> |
4924 |
|
<t>Where <dir> should be replaced by the absolute path |
4925 |
|
name of the directory the front-end is interested in.</t> |
4926 |
|
|
4927 |
|
<t>Possible Answers:</t> |
4928 |
|
<t> |
4929 |
|
<list> |
4930 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
4931 |
|
Each answer line begins with the settings category name |
4932 |
|
followed by a colon and then a space character <SP> and finally |
4933 |
|
the info character string to that setting category. At the |
4934 |
|
moment the following categories are defined:</t> |
4935 |
|
|
4936 |
|
<t> |
4937 |
|
<list> |
4938 |
|
<t>DESCRIPTION - |
4939 |
|
<list> |
4940 |
|
<t>A brief description of the directory content</t> |
4941 |
|
</list> |
4942 |
|
</t> |
4943 |
|
<t>CREATED - |
4944 |
|
<list> |
4945 |
|
<t>The creation date and time of the directory, |
4946 |
|
represented in "YYYY-MM-DD HH:MM:SS" format</t> |
4947 |
|
</list> |
4948 |
|
</t> |
4949 |
|
<t>MODIFIED - |
4950 |
|
<list> |
4951 |
|
<t>The date and time of the last modification of the |
4952 |
|
directory, represented in "YYYY-MM-DD HH:MM:SS" format</t> |
4953 |
|
</list> |
4954 |
|
</t> |
4955 |
|
</list> |
4956 |
|
</t> |
4957 |
|
</list> |
4958 |
|
</t> |
4959 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
4960 |
|
|
4961 |
|
<t>Example:</t> |
4962 |
|
<t> |
4963 |
|
<list> |
4964 |
|
<t>C: "GET DB_INSTRUMENT_DIRECTORY INFO '/Piano Collection'"</t> |
4965 |
|
<t>S: "DESCRIPTION: Piano collection of instruments in GigaSampler format."</t> |
4966 |
|
<t> "CREATED: 2007-02-05 10:23:12"</t> |
4967 |
|
<t> "MODIFIED: 2007-04-07 12:50:21"</t> |
4968 |
|
<t> "."</t> |
4969 |
|
</list> |
4970 |
|
</t> |
4971 |
|
</section> |
4972 |
|
|
4973 |
|
<section title="Renaming an instrument directory" anchor="SET DB_INSTRUMENT_DIRECTORY NAME"> |
4974 |
|
<t>The front-end can alter the name of a specific |
4975 |
|
instrument directory by sending the following command:</t> |
4976 |
|
<t> |
4977 |
|
<list> |
4978 |
|
<t>SET DB_INSTRUMENT_DIRECTORY NAME <dir> <name></t> |
4979 |
|
</list> |
4980 |
|
</t> |
4981 |
|
<t>Where <dir> is the absolute path name of the directory and |
4982 |
|
<name> is the new name for that directory.</t> |
4983 |
|
|
4984 |
|
<t>Possible Answers:</t> |
4985 |
|
<t> |
4986 |
|
<list> |
4987 |
|
<t>"OK" - |
4988 |
|
<list> |
4989 |
|
<t>on success</t> |
4990 |
|
</list> |
4991 |
|
</t> |
4992 |
|
<t>"ERR:<error-code>:<error-message>" - |
4993 |
|
<list> |
4994 |
|
<t>in case the given directory does not exists, |
4995 |
|
or if a directory with name equal to the new |
4996 |
|
name already exists.</t> |
4997 |
|
</list> |
4998 |
|
</t> |
4999 |
|
</list> |
5000 |
|
</t> |
5001 |
|
|
5002 |
|
<t>Example:</t> |
5003 |
|
<t> |
5004 |
|
<list> |
5005 |
|
<t>C: "SET DB_INSTRUMENT_DIRECTORY NAME '/Piano Collection/Acustic' 'Acoustic'"</t> |
5006 |
|
<t>S: "OK"</t> |
5007 |
|
</list> |
5008 |
|
</t> |
5009 |
|
</section> |
5010 |
|
|
5011 |
|
<section title="Moving an instrument directory" anchor="MOVE DB_INSTRUMENT_DIRECTORY"> |
5012 |
|
<t>The front-end can move a specific |
5013 |
|
instrument directory by sending the following command:</t> |
5014 |
|
<t> |
5015 |
|
<list> |
5016 |
|
<t>MOVE DB_INSTRUMENT_DIRECTORY <dir> <dst></t> |
5017 |
|
</list> |
5018 |
|
</t> |
5019 |
|
<t>Where <dir> is the absolute path name of the directory |
5020 |
|
to move and <dst> is the location where the directory will |
5021 |
|
be moved to.</t> |
5022 |
|
|
5023 |
|
<t>Possible Answers:</t> |
5024 |
|
<t> |
5025 |
|
<list> |
5026 |
|
<t>"OK" - |
5027 |
|
<list> |
5028 |
|
<t>on success</t> |
5029 |
|
</list> |
5030 |
|
</t> |
5031 |
|
<t>"ERR:<error-code>:<error-message>" - |
5032 |
|
<list> |
5033 |
|
<t>in case a given directory does not exists, |
5034 |
|
or if a directory with name equal to the name |
5035 |
|
of the specified directory already exists in |
5036 |
|
the destination directory. Error is also thrown |
5037 |
|
when trying to move a directory to a subdirectory |
5038 |
|
of itself.</t> |
5039 |
|
</list> |
5040 |
|
</t> |
5041 |
|
</list> |
5042 |
|
</t> |
5043 |
|
|
5044 |
|
<t>Example:</t> |
5045 |
|
<t> |
5046 |
|
<list> |
5047 |
|
<t>C: "MOVE DB_INSTRUMENT_DIRECTORY '/Acoustic' '/Piano Collection/Acoustic'"</t> |
5048 |
|
<t>S: "OK"</t> |
5049 |
|
</list> |
5050 |
|
</t> |
5051 |
|
</section> |
5052 |
|
|
5053 |
|
<section title="Copying instrument directories" anchor="COPY DB_INSTRUMENT_DIRECTORY"> |
5054 |
|
<t>The front-end can copy a specific |
5055 |
|
instrument directory by sending the following command:</t> |
5056 |
|
<t> |
5057 |
|
<list> |
5058 |
|
<t>COPY DB_INSTRUMENT_DIRECTORY <dir> <dst></t> |
5059 |
|
</list> |
5060 |
|
</t> |
5061 |
|
<t>Where <dir> is the absolute path name of the directory |
5062 |
|
to copy and <dst> is the location where the directory will |
5063 |
|
be copied to.</t> |
5064 |
|
|
5065 |
|
<t>Possible Answers:</t> |
5066 |
|
<t> |
5067 |
|
<list> |
5068 |
|
<t>"OK" - |
5069 |
|
<list> |
5070 |
|
<t>on success</t> |
5071 |
|
</list> |
5072 |
|
</t> |
5073 |
|
<t>"ERR:<error-code>:<error-message>" - |
5074 |
|
<list> |
5075 |
|
<t>in case a given directory does not exists, |
5076 |
|
or if a directory with name equal to the name |
5077 |
|
of the specified directory already exists in |
5078 |
|
the destination directory. Error is also thrown |
5079 |
|
when trying to copy a directory to a subdirectory |
5080 |
|
of itself.</t> |
5081 |
|
</list> |
5082 |
|
</t> |
5083 |
|
</list> |
5084 |
|
</t> |
5085 |
|
|
5086 |
|
<t>Example:</t> |
5087 |
|
<t> |
5088 |
|
<list> |
5089 |
|
<t>C: "COPY DB_INSTRUMENT_DIRECTORY '/Piano Collection/Acoustic' '/Acoustic/Pianos'"</t> |
5090 |
|
<t>S: "OK"</t> |
5091 |
|
</list> |
5092 |
|
</t> |
5093 |
|
</section> |
5094 |
|
|
5095 |
|
<section title="Changing the description of directory" anchor="SET DB_INSTRUMENT_DIRECTORY DESCRIPTION"> |
5096 |
|
<t>The front-end can alter the description of a specific |
5097 |
|
instrument directory by sending the following command:</t> |
5098 |
|
<t> |
5099 |
|
<list> |
5100 |
|
<t>SET DB_INSTRUMENT_DIRECTORY DESCRIPTION <dir> <desc></t> |
5101 |
|
</list> |
5102 |
|
</t> |
5103 |
|
<t>Where <dir> is the absolute path name of the directory and |
5104 |
|
<desc> is the new description for the directory.</t> |
5105 |
|
|
5106 |
|
<t>Possible Answers:</t> |
5107 |
|
<t> |
5108 |
|
<list> |
5109 |
|
<t>"OK" - |
5110 |
|
<list> |
5111 |
|
<t>on success</t> |
5112 |
|
</list> |
5113 |
|
</t> |
5114 |
|
<t>"ERR:<error-code>:<error-message>" - |
5115 |
|
<list> |
5116 |
|
<t>in case the given directory does not exists.</t> |
5117 |
|
</list> |
5118 |
|
</t> |
5119 |
|
</list> |
5120 |
|
</t> |
5121 |
|
|
5122 |
|
<t>Example:</t> |
5123 |
|
<t> |
5124 |
|
<list> |
5125 |
|
<t>C: "SET DB_INSTRUMENT_DIRECTORY DESCRIPTION '/Piano Collection' 'A collection of piano instruments in various format.'"</t> |
5126 |
|
<t>S: "OK"</t> |
5127 |
|
</list> |
5128 |
|
</t> |
5129 |
|
</section> |
5130 |
|
|
5131 |
|
<section title="Finding directories" anchor="FIND DB_INSTRUMENT_DIRECTORIES"> |
5132 |
|
<t>The front-end can search for directories |
5133 |
|
in specific directory by sending the following command:</t> |
5134 |
|
<t> |
5135 |
|
<list> |
5136 |
|
<t>FIND DB_INSTRUMENT_DIRECTORIES [NON_RECURSIVE] <dir> <criteria-list></t> |
5137 |
|
</list> |
5138 |
|
</t> |
5139 |
|
<t>Where <dir> should be replaced by the absolute path |
5140 |
|
name of the directory to search in. If NON_RECURSIVE is specified, the |
5141 |
|
directories located in subdirectories of the specified directory will not |
5142 |
|
be searched. <criteria-list> is a list of search criterias |
5143 |
|
in form of "key1=val1 key2=val2 ...". The following criterias are |
5144 |
|
allowed:</t> |
5145 |
|
<t> |
5146 |
|
<t>NAME='<search-string>' |
5147 |
|
<list> |
5148 |
|
<t>Restricts the search to directories, which names |
5149 |
|
satisfy the supplied search string.</t> |
5150 |
|
</list> |
5151 |
|
</t> |
5152 |
|
|
5153 |
|
<t>CREATED='[<date-after>]..[<date-before>]' |
5154 |
|
<list> |
5155 |
|
<t>Restricts the search to directories, which creation |
5156 |
|
date satisfies the specified period, where <date-after> |
5157 |
|
and <date-before> are in "YYYY-MM-DD HH:MM:SS" format. |
5158 |
|
If <date-after> is omitted the search is restricted to |
5159 |
|
directories created before <date-before>. If |
5160 |
|
<date-before> is omitted, the search is restricted |
5161 |
|
to directories created after <date-after>.</t> |
5162 |
|
</list> |
5163 |
|
</t> |
5164 |
|
|
5165 |
|
<t>MODIFIED='[<date-after>]..[<date-before>]' |
5166 |
|
<list> |
5167 |
|
<t>Restricts the search to directories, which |
5168 |
|
date of last modification satisfies the specified period, where |
5169 |
|
<date-after> and <date-before> are in "YYYY-MM-DD HH:MM:SS" |
5170 |
|
format. If <date-after> is omitted the search is restricted to |
5171 |
|
directories, which are last modified before <date-before>. If |
5172 |
|
<date-before> is omitted, the search is restricted to directories, |
5173 |
|
which are last modified after <date-after>.</t> |
5174 |
|
</list> |
5175 |
|
</t> |
5176 |
|
|
5177 |
|
<t>DESCRIPTION='<search-string>' |
5178 |
|
<list> |
5179 |
|
<t>Restricts the search to directories with description |
5180 |
|
that satisfies the supplied search string.</t> |
5181 |
|
</list> |
5182 |
|
</t> |
5183 |
|
</t> |
5184 |
|
|
5185 |
|
<t>Where <search-string> is either a regular expression, or a |
5186 |
|
word list separated with spaces for OR search and with '+' for AND search.</t> |
5187 |
|
|
5188 |
|
<t>Possible Answers:</t> |
5189 |
|
<t> |
5190 |
|
<list> |
5191 |
|
<t>A comma separated list with the absolute path names (encapsulated into |
5192 |
|
apostrophes) of all directories in the specified directory that satisfy |
5193 |
|
the supplied search criterias.</t> |
5194 |
|
<t>"ERR:<error-code>:<error-message>" - |
5195 |
|
<list> |
5196 |
|
<t>if the given directory does not exist.</t> |
5197 |
|
</list> |
5198 |
|
</t> |
5199 |
|
</list> |
5200 |
|
</t> |
5201 |
|
<t>Example:</t> |
5202 |
|
<t> |
5203 |
|
<list> |
5204 |
|
<t>C: "FIND DB_INSTRUMENT_DIRECTORIES '/' NAME='Piano'"</t> |
5205 |
|
<t>S: "'/Piano Collection'"</t> |
5206 |
|
</list> |
5207 |
|
</t> |
5208 |
|
<t> |
5209 |
|
<list> |
5210 |
|
<t>C: "FIND DB_INSTRUMENT_DIRECTORIES '/' CREATED='..2007-04-01 09:30:13'"</t> |
5211 |
|
<t>S: "'/Piano Collection','/Percussions'"</t> |
5212 |
|
</list> |
5213 |
|
</t> |
5214 |
|
</section> |
5215 |
|
|
5216 |
|
<section title="Adding instruments to the instruments database" anchor="ADD DB_INSTRUMENTS"> |
5217 |
|
<t>The front-end can add one or more instruments |
5218 |
|
to the instruments database by sending the following command:</t> |
5219 |
|
<t> |
5220 |
|
<list> |
5221 |
|
<t>ADD DB_INSTRUMENTS [NON_MODAL] [<mode>] <db_dir> <file_path> [<instr_index>]</t> |
5222 |
|
</list> |
5223 |
|
</t> |
5224 |
|
<t>Where <db_dir> is the absolute path name of a directory |
5225 |
|
(encapsulated into apostrophes) in the instruments database in which |
5226 |
|
only the new instruments (that are not already in the database) will |
5227 |
|
be added, <file_path> is the absolute path name of a file or |
5228 |
|
directory in the file system (encapsulated into apostrophes). In case |
5229 |
|
an instrument file is supplied, only the instruments in the specified |
5230 |
|
file will be added to the instruments database. If the optional |
5231 |
|
<instr_index> (the index of the instrument within the given file) |
5232 |
|
is supplied too, then only the specified instrument will be added. |
5233 |
|
In case a directory is supplied, the instruments in that directory |
5234 |
|
will be added. The OPTIONAL <mode> argument is only applied |
5235 |
|
when a directory is provided as <file_path> and specifies how the |
5236 |
|
scanning will be done and has exactly the following possibilities:</t> |
5237 |
|
<t> |
5238 |
|
<list> |
5239 |
|
<t>"RECURSIVE" - |
5240 |
|
<list> |
5241 |
|
<t>All instruments will be processed, including those |
5242 |
|
in the subdirectories, and the respective subdirectory |
5243 |
|
tree structure will be recreated in the instruments |
5244 |
|
database</t> |
5245 |
|
</list> |
5246 |
|
</t> |
5247 |
|
<t>"NON_RECURSIVE" - |
5248 |
|
<list> |
5249 |
|
<t>Only the instruments in the specified directory |
5250 |
|
will be added, the instruments in the subdirectories |
5251 |
|
will not be processed.</t> |
5252 |
|
</list> |
5253 |
|
</t> |
5254 |
|
<t>"FLAT" - |
5255 |
|
<list> |
5256 |
|
<t>All instruments will be processed, including those |
5257 |
|
in the subdirectories, but the respective subdirectory |
5258 |
|
structure will not be recreated in the instruments |
5259 |
|
database. All instruments will be added directly in |
5260 |
|
the specified database directory.</t> |
5261 |
|
</list> |
5262 |
|
</t> |
5263 |
|
</list> |
5264 |
|
</t> |
5265 |
|
|
5266 |
|
<t>The difference between regular and NON_MODAL versions of the command |
5267 |
|
is that the regular command returns when the scanning is finished |
5268 |
|
while NON_MODAL version returns immediately and a background process is launched. |
5269 |
|
The <xref target="GET DB_INSTRUMENTS_JOB INFO">GET DB_INSTRUMENTS_JOB INFO</xref> |
5270 |
|
command can be used to monitor the scanning progress.</t> |
5271 |
|
|
5272 |
|
<t>Possible Answers:</t> |
5273 |
|
<t> |
5274 |
|
<list> |
5275 |
|
<t>"OK" - |
5276 |
|
<list> |
5277 |
|
<t>on success when NON_MODAL is not supplied</t> |
5278 |
|
</list> |
5279 |
|
</t> |
5280 |
|
<t>"OK[<job-id>]" - |
5281 |
|
<list> |
5282 |
|
<t>on success when NON_MODAL is supplied, where <job-id> |
5283 |
|
is a numerical ID used to obtain status information about the job progress. |
5284 |
|
See <xref target="GET DB_INSTRUMENTS_JOB INFO">GET DB_INSTRUMENTS_JOB INFO</xref> |
5285 |
|
</t> |
5286 |
|
</list> |
5287 |
|
</t> |
5288 |
|
<t>"ERR:<error-code>:<error-message>" - |
5289 |
|
<list> |
5290 |
|
<t>if an invalid path is specified.</t> |
5291 |
|
</list> |
5292 |
|
</t> |
5293 |
|
</list> |
5294 |
|
</t> |
5295 |
|
|
5296 |
|
<t>Examples:</t> |
5297 |
|
<t> |
5298 |
|
<list> |
5299 |
|
<t>C: "ADD DB_INSTRUMENTS '/Piano Collection' '/home/me/gigs/PMI Bosendorfer 290.gig' 0"</t> |
5300 |
|
<t>S: "OK"</t> |
5301 |
|
</list> |
5302 |
|
</t> |
5303 |
|
</section> |
5304 |
|
|
5305 |
|
<section title="Removing an instrument" anchor="REMOVE DB_INSTRUMENT"> |
5306 |
|
<t>The front-end can remove a particular instrument |
5307 |
|
from the instruments database by sending the following command:</t> |
5308 |
|
<t> |
5309 |
|
<list> |
5310 |
|
<t>REMOVE DB_INSTRUMENT <instr_path></t> |
5311 |
|
</list> |
5312 |
|
</t> |
5313 |
|
<t>Where <instr_path> is the absolute path name |
5314 |
|
(in the instruments database) of the instrument to remove.</t> |
5315 |
|
|
5316 |
|
<t>Possible Answers:</t> |
5317 |
|
<t> |
5318 |
|
<list> |
5319 |
|
<t>"OK" - |
5320 |
|
<list> |
5321 |
|
<t>if the instrument is removed successfully</t> |
5322 |
|
</list> |
5323 |
|
</t> |
5324 |
|
<t>"ERR:<error-code>:<error-message>" - |
5325 |
|
<list> |
5326 |
|
<t>if the given path does not exist or |
5327 |
|
is a directory.</t> |
5328 |
|
</list> |
5329 |
|
</t> |
5330 |
|
</list> |
5331 |
|
</t> |
5332 |
|
|
5333 |
|
<t>Examples:</t> |
5334 |
|
<t> |
5335 |
|
<list> |
5336 |
|
<t>C: "REMOVE DB_INSTRUMENT '/Piano Collection/Bosendorfer 290'"</t> |
5337 |
|
<t>S: "OK"</t> |
5338 |
|
</list> |
5339 |
|
</t> |
5340 |
|
</section> |
5341 |
|
|
5342 |
|
<section title="Getting amount of instruments" anchor="GET DB_INSTRUMENTS"> |
5343 |
|
<t>The front-end can retrieve the current amount of |
5344 |
|
instruments in a specific directory by sending the following command:</t> |
5345 |
|
<t> |
5346 |
|
<list> |
5347 |
|
<t>GET DB_INSTRUMENTS [RECURSIVE] <dir></t> |
5348 |
|
</list> |
5349 |
|
</t> |
5350 |
|
<t>Where <dir> should be replaced by the absolute path name |
5351 |
|
of the directory. If RECURSIVE is specified, the number of all |
5352 |
|
instruments, including those located in subdirectories of the |
5353 |
|
specified directory, will be returned.</t> |
5354 |
|
|
5355 |
|
<t>Possible Answers:</t> |
5356 |
|
<t> |
5357 |
|
<list> |
5358 |
|
<t>The current number of instruments |
5359 |
|
in the specified directory.</t> |
5360 |
|
<t>"ERR:<error-code>:<error-message>" - |
5361 |
|
<list> |
5362 |
|
<t>if the given directory does not exist.</t> |
5363 |
|
</list> |
5364 |
|
</t> |
5365 |
|
</list> |
5366 |
|
</t> |
5367 |
|
|
5368 |
|
<t>Example:</t> |
5369 |
|
<t> |
5370 |
|
<list> |
5371 |
|
<t>C: "GET DB_INSTRUMENTS '/Piano Collection'"</t> |
5372 |
|
<t>S: "2"</t> |
5373 |
|
</list> |
5374 |
|
</t> |
5375 |
|
</section> |
5376 |
|
|
5377 |
|
<section title="Listing all instruments in specific directory" anchor="LIST DB_INSTRUMENTS"> |
5378 |
|
<t>The front-end can retrieve the current list of instruments |
5379 |
|
in specific directory by sending the following command:</t> |
5380 |
|
<t> |
5381 |
|
<list> |
5382 |
|
<t>LIST DB_INSTRUMENTS [RECURSIVE] <dir></t> |
5383 |
|
</list> |
5384 |
|
</t> |
5385 |
|
<t>Where <dir> should be replaced by the absolute path |
5386 |
|
name of the directory. If RECURSIVE is specified, the absolute path |
5387 |
|
names of all instruments, including those located in subdirectories |
5388 |
|
of the specified directory, will be returned.</t> |
5389 |
|
|
5390 |
|
<t>Possible Answers:</t> |
5391 |
|
<t> |
5392 |
|
<list> |
5393 |
|
<t>A comma separated list of all instruments |
5394 |
|
(encapsulated into apostrophes) in the specified directory.</t> |
5395 |
|
<t>"ERR:<error-code>:<error-message>" - |
5396 |
|
<list> |
5397 |
|
<t>if the given directory does not exist.</t> |
5398 |
|
</list> |
5399 |
|
</t> |
5400 |
|
</list> |
5401 |
|
</t> |
5402 |
|
<t>Example:</t> |
5403 |
|
<t> |
5404 |
|
<list> |
5405 |
|
<t>C: "LIST DB_INSTRUMENTS '/Piano Collection'"</t> |
5406 |
|
<t>S: "'Bosendorfer 290','Steinway D'"</t> |
5407 |
|
</list> |
5408 |
|
</t> |
5409 |
|
<t> |
5410 |
|
<list> |
5411 |
|
<t>C: "LIST DB_INSTRUMENTS RECURSIVE '/Piano Collection'"</t> |
5412 |
|
<t>S: "'/Piano Collection/Bosendorfer 290','/Piano Collection/Steinway D','/Piano Collection/Lite/Free Piano'"</t> |
5413 |
|
</list> |
5414 |
|
</t> |
5415 |
|
</section> |
5416 |
|
|
5417 |
|
<section title="Getting instrument information" anchor="GET DB_INSTRUMENT INFO"> |
5418 |
|
<t>The front-end can ask for the current settings of an |
5419 |
|
instrument by sending the following command:</t> |
5420 |
|
<t> |
5421 |
|
<list> |
5422 |
|
<t>GET DB_INSTRUMENT INFO <instr_path></t> |
5423 |
|
</list> |
5424 |
|
</t> |
5425 |
|
<t>Where <instr_path> should be replaced by the absolute path |
5426 |
|
name of the instrument the front-end is interested in.</t> |
5427 |
|
|
5428 |
|
<t>Possible Answers:</t> |
5429 |
|
<t> |
5430 |
|
<list> |
5431 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
5432 |
|
Each answer line begins with the settings category name |
5433 |
|
followed by a colon and then a space character <SP> and finally |
5434 |
|
the info character string to that setting category. At the |
5435 |
|
moment the following categories are defined:</t> |
5436 |
|
|
5437 |
|
<t> |
5438 |
|
<list> |
5439 |
|
<t>INSTRUMENT_FILE - |
5440 |
|
<list> |
5441 |
|
<t>File name of the instrument.</t> |
5442 |
|
</list> |
5443 |
|
</t> |
5444 |
|
<t>INSTRUMENT_NR - |
5445 |
|
<list> |
5446 |
|
<t>Index of the instrument within the file.</t> |
5447 |
|
</list> |
5448 |
|
</t> |
5449 |
|
<t>FORMAT_FAMILY - |
5450 |
|
<list> |
5451 |
|
<t>The format family of the instrument.</t> |
5452 |
|
</list> |
5453 |
|
</t> |
5454 |
|
<t>FORMAT_VERSION - |
5455 |
|
<list> |
5456 |
|
<t>The format version of the instrument.</t> |
5457 |
|
</list> |
5458 |
|
</t> |
5459 |
|
<t>SIZE - |
5460 |
|
<list> |
5461 |
|
<t>The size of the instrument in bytes.</t> |
5462 |
|
</list> |
5463 |
|
</t> |
5464 |
|
<t>CREATED - |
5465 |
|
<list> |
5466 |
|
<t>The date and time when the instrument is added |
5467 |
|
in the instruments database, represented in |
5468 |
|
"YYYY-MM-DD HH:MM:SS" format</t> |
5469 |
|
</list> |
5470 |
|
</t> |
5471 |
|
<t>MODIFIED - |
5472 |
|
<list> |
5473 |
|
<t>The date and time of the last modification of the |
5474 |
|
instrument's database settings, represented in |
5475 |
|
"YYYY-MM-DD HH:MM:SS" format</t> |
5476 |
|
</list> |
5477 |
|
</t> |
5478 |
|
<t>DESCRIPTION - |
5479 |
|
<list> |
5480 |
|
<t>A brief description of the instrument</t> |
5481 |
|
</list> |
5482 |
|
</t> |
5483 |
|
<t>IS_DRUM - |
5484 |
|
<list> |
5485 |
|
<t>either true or false, determines whether the |
5486 |
|
instrument is a drumkit or a chromatic instrument</t> |
5487 |
|
</list> |
5488 |
|
</t> |
5489 |
|
<t>PRODUCT - |
5490 |
|
<list> |
5491 |
|
<t>The product title of the instrument</t> |
5492 |
|
</list> |
5493 |
|
</t> |
5494 |
|
<t>ARTISTS - |
5495 |
|
<list> |
5496 |
|
<t>Lists the artist names</t> |
5497 |
|
</list> |
5498 |
|
</t> |
5499 |
|
<t>KEYWORDS - |
5500 |
|
<list> |
5501 |
|
<t>Provides a list of keywords that refer to the instrument. |
5502 |
|
Keywords are separated with semicolon and blank.</t> |
5503 |
|
</list> |
5504 |
|
</t> |
5505 |
|
</list> |
5506 |
|
</t> |
5507 |
|
</list> |
5508 |
|
</t> |
5509 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
5510 |
|
|
5511 |
|
<t>Example:</t> |
5512 |
|
<t> |
5513 |
|
<list> |
5514 |
|
<t>C: "GET DB_INSTRUMENT INFO '/Piano Collection/Bosendorfer 290'"</t> |
5515 |
|
<t>S: "INSTRUMENT_FILE: /home/me/gigs/Bosendorfer 290.gig"</t> |
5516 |
|
<t> "INSTRUMENT_NR: 0"</t> |
5517 |
|
<t> "FORMAT_FAMILY: GIG"</t> |
5518 |
|
<t> "FORMAT_VERSION: 2"</t> |
5519 |
|
<t> "SIZE: 2050871870"</t> |
5520 |
|
<t> "CREATED: 2007-02-05 10:23:12"</t> |
5521 |
|
<t> "MODIFIED: 2007-04-07 12:50:21"</t> |
5522 |
|
<t> "DESCRIPTION: "</t> |
5523 |
|
<t> "IS_DRUM: false"</t> |
5524 |
|
<t> "PRODUCT: GRANDIOSO Bosendorfer 290"</t> |
5525 |
|
<t> "ARTISTS: Post Musical Instruments"</t> |
5526 |
|
<t> "KEYWORDS: Bosendorfer"</t> |
5527 |
|
<t> "."</t> |
5528 |
|
</list> |
5529 |
|
</t> |
5530 |
|
</section> |
5531 |
|
|
5532 |
|
<section title="Renaming an instrument" anchor="SET DB_INSTRUMENT NAME"> |
5533 |
|
<t>The front-end can alter the name of a specific |
5534 |
|
instrument by sending the following command:</t> |
5535 |
|
<t> |
5536 |
|
<list> |
5537 |
|
<t>SET DB_INSTRUMENT NAME <instr> <name></t> |
5538 |
|
</list> |
5539 |
|
</t> |
5540 |
|
<t>Where <instr> is the absolute path name of the instrument and |
5541 |
|
<name> is the new name for that instrument.</t> |
5542 |
|
|
5543 |
|
<t>Possible Answers:</t> |
5544 |
|
<t> |
5545 |
|
<list> |
5546 |
|
<t>"OK" - |
5547 |
|
<list> |
5548 |
|
<t>on success</t> |
5549 |
|
</list> |
5550 |
|
</t> |
5551 |
|
<t>"ERR:<error-code>:<error-message>" - |
5552 |
|
<list> |
5553 |
|
<t>in case the given instrument does not exists, |
5554 |
|
or if an instrument with name equal to the new |
5555 |
|
name already exists.</t> |
5556 |
|
</list> |
5557 |
|
</t> |
5558 |
|
</list> |
5559 |
|
</t> |
5560 |
|
|
5561 |
|
<t>Example:</t> |
5562 |
|
<t> |
5563 |
|
<list> |
5564 |
|
<t>C: "SET DB_INSTRUMENT NAME '/Piano Collection/Bosendorfer' 'Bosendorfer 290'"</t> |
5565 |
|
<t>S: "OK"</t> |
5566 |
|
</list> |
5567 |
|
</t> |
5568 |
|
</section> |
5569 |
|
|
5570 |
|
<section title="Moving an instrument" anchor="MOVE DB_INSTRUMENT"> |
5571 |
|
<t>The front-end can move a specific instrument to another directory by |
5572 |
|
sending the following command:</t> |
5573 |
|
<t> |
5574 |
|
<list> |
5575 |
|
<t>MOVE DB_INSTRUMENT <instr> <dst></t> |
5576 |
|
</list> |
5577 |
|
</t> |
5578 |
|
<t>Where <instr> is the absolute path name of the instrument |
5579 |
|
to move and <dst> is the directory where the instrument will |
5580 |
|
be moved to.</t> |
5581 |
|
|
5582 |
|
<t>Possible Answers:</t> |
5583 |
|
<t> |
5584 |
|
<list> |
5585 |
|
<t>"OK" - |
5586 |
|
<list> |
5587 |
|
<t>on success</t> |
5588 |
|
</list> |
5589 |
|
</t> |
5590 |
|
<t>"ERR:<error-code>:<error-message>" - |
5591 |
|
<list> |
5592 |
|
<t>in case the given instrument does not exists, |
5593 |
|
or if an instrument with name equal to the name of the |
5594 |
|
specified instrument already exists in the destination |
5595 |
|
directory.</t> |
5596 |
|
</list> |
5597 |
|
</t> |
5598 |
|
</list> |
5599 |
|
</t> |
5600 |
|
|
5601 |
|
<t>Example:</t> |
5602 |
|
<t> |
5603 |
|
<list> |
5604 |
|
<t>C: "MOVE DB_INSTRUMENT '/Piano Collection/Bosendorfer 290' '/Piano Collection/Acoustic'"</t> |
5605 |
|
<t>S: "OK"</t> |
5606 |
|
</list> |
5607 |
|
</t> |
5608 |
|
</section> |
5609 |
|
|
5610 |
|
<section title="Copying instruments" anchor="COPY DB_INSTRUMENT"> |
5611 |
|
<t>The front-end can copy a specific instrument to another directory by |
5612 |
|
sending the following command:</t> |
5613 |
|
<t> |
5614 |
|
<list> |
5615 |
|
<t>COPY DB_INSTRUMENT <instr> <dst></t> |
5616 |
|
</list> |
5617 |
|
</t> |
5618 |
|
<t>Where <instr> is the absolute path name of the instrument |
5619 |
|
to copy and <dst> is the directory where the instrument will |
5620 |
|
be copied to.</t> |
5621 |
|
|
5622 |
|
<t>Possible Answers:</t> |
5623 |
|
<t> |
5624 |
|
<list> |
5625 |
|
<t>"OK" - |
5626 |
|
<list> |
5627 |
|
<t>on success</t> |
5628 |
|
</list> |
5629 |
|
</t> |
5630 |
|
<t>"ERR:<error-code>:<error-message>" - |
5631 |
|
<list> |
5632 |
|
<t>in case the given instrument does not exists, |
5633 |
|
or if an instrument with name equal to the name of the |
5634 |
|
specified instrument already exists in the destination |
5635 |
|
directory.</t> |
5636 |
|
</list> |
5637 |
|
</t> |
5638 |
|
</list> |
5639 |
|
</t> |
5640 |
|
|
5641 |
|
<t>Example:</t> |
5642 |
|
<t> |
5643 |
|
<list> |
5644 |
|
<t>C: "COPY DB_INSTRUMENT '/Piano Collection/Bosendorfer 290' '/Acoustic/Pianos/'"</t> |
5645 |
|
<t>S: "OK"</t> |
5646 |
|
</list> |
5647 |
|
</t> |
5648 |
|
</section> |
5649 |
|
|
5650 |
|
<section title="Changing the description of instrument" anchor="SET DB_INSTRUMENT DESCRIPTION"> |
5651 |
|
<t>The front-end can alter the description of a specific |
5652 |
|
instrument by sending the following command:</t> |
5653 |
|
<t> |
5654 |
|
<list> |
5655 |
|
<t>SET DB_INSTRUMENT DESCRIPTION <instr> <desc></t> |
5656 |
|
</list> |
5657 |
|
</t> |
5658 |
|
<t>Where <instr> is the absolute path name of the instrument and |
5659 |
|
<desc> is the new description for the instrument.</t> |
5660 |
|
|
5661 |
|
<t>Possible Answers:</t> |
5662 |
|
<t> |
5663 |
|
<list> |
5664 |
|
<t>"OK" - |
5665 |
|
<list> |
5666 |
|
<t>on success</t> |
5667 |
|
</list> |
5668 |
|
</t> |
5669 |
|
<t>"ERR:<error-code>:<error-message>" - |
5670 |
|
<list> |
5671 |
|
<t>in case the given instrument does not exists.</t> |
5672 |
|
</list> |
5673 |
|
</t> |
5674 |
|
</list> |
5675 |
|
</t> |
5676 |
|
|
5677 |
|
<t>Example:</t> |
5678 |
|
<t> |
5679 |
|
<list> |
5680 |
|
<t>C: "SET DB_INSTRUMENT DESCRIPTION '/Piano Collection/Acoustic/Bosendorfer 290' 'No comment :)'"</t> |
5681 |
|
<t>S: "OK"</t> |
5682 |
|
</list> |
5683 |
|
</t> |
5684 |
|
</section> |
5685 |
|
|
5686 |
|
<section title="Finding instruments" anchor="FIND DB_INSTRUMENTS"> |
5687 |
|
<t>The front-end can search for instruments |
5688 |
|
in specific directory by sending the following command:</t> |
5689 |
|
<t> |
5690 |
|
<list> |
5691 |
|
<t>FIND DB_INSTRUMENTS [NON_RECURSIVE] <dir> <criteria-list></t> |
5692 |
|
</list> |
5693 |
|
</t> |
5694 |
|
<t>Where <dir> should be replaced by the absolute path |
5695 |
|
name of the directory to search in. If NON_RECURSIVE is specified, the |
5696 |
|
directories located in subdirectories of the specified directory will not |
5697 |
|
be searched. <criteria-list> is a list of search criterias |
5698 |
|
in form of "key1=val1 key2=val2 ...". The following criterias are |
5699 |
|
allowed:</t> |
5700 |
|
<t> |
5701 |
|
<t>NAME='<search-string>' |
5702 |
|
<list> |
5703 |
|
<t>Restricts the search to instruments, which names |
5704 |
|
satisfy the supplied search string.</t> |
5705 |
|
</list> |
5706 |
|
</t> |
5707 |
|
|
5708 |
|
<t>SIZE=[<min>]..[<max>] |
5709 |
|
<list> |
5710 |
|
<t>Restricts the search to instruments, which |
5711 |
|
size is in the specified range. If <min> is omitted, |
5712 |
|
the search results are restricted to instruments with size less then |
5713 |
|
or equal to <max>. If <max> is omitted, the |
5714 |
|
search is restricted to instruments with size greater then |
5715 |
|
or equal to <min>.</t> |
5716 |
|
</list> |
5717 |
|
</t> |
5718 |
|
|
5719 |
|
<t>CREATED='[<date-after>]..[<date-before>]' |
5720 |
|
<list> |
5721 |
|
<t>Restricts the search to instruments, which creation |
5722 |
|
date satisfies the specified period, where <date-after> |
5723 |
|
and <date-before> are in "YYYY-MM-DD HH:MM:SS" format. |
5724 |
|
If <date-after> is omitted the search is restricted to |
5725 |
|
instruments created before <date-before>. If |
5726 |
|
<date-before> is omitted, the search is restricted |
5727 |
|
to instruments created after <date-after>.</t> |
5728 |
|
</list> |
5729 |
|
</t> |
5730 |
|
|
5731 |
|
<t>MODIFIED='[<date-after>]..[<date-before>]' |
5732 |
|
<list> |
5733 |
|
<t>Restricts the search to instruments, which |
5734 |
|
date of last modification satisfies the specified period, where |
5735 |
|
<date-after> and <date-before> are in "YYYY-MM-DD HH:MM:SS" |
5736 |
|
format. If <date-after> is omitted the search is restricted to |
5737 |
|
instruments, which are last modified before <date-before>. If |
5738 |
|
<date-before> is omitted, the search is restricted to instruments, |
5739 |
|
which are last modified after <date-after>.</t> |
5740 |
|
</list> |
5741 |
|
</t> |
5742 |
|
|
5743 |
|
<t>DESCRIPTION='<search-string>' |
5744 |
|
<list> |
5745 |
|
<t>Restricts the search to instruments with description |
5746 |
|
that satisfies the supplied search string.</t> |
5747 |
|
</list> |
5748 |
|
</t> |
5749 |
|
|
5750 |
|
<t>PRODUCT='<search-string>' |
5751 |
|
<list> |
5752 |
|
<t>Restricts the search to instruments with product info |
5753 |
|
that satisfies the supplied search string.</t> |
5754 |
|
</list> |
5755 |
|
</t> |
5756 |
|
|
5757 |
|
<t>ARTISTS='<search-string>' |
5758 |
|
<list> |
5759 |
|
<t>Restricts the search to instruments with artists info |
5760 |
|
that satisfies the supplied search string.</t> |
5761 |
|
</list> |
5762 |
|
</t> |
5763 |
|
|
5764 |
|
<t>KEYWORDS='<search-string>' |
5765 |
|
<list> |
5766 |
|
<t>Restricts the search to instruments with keyword list |
5767 |
|
that satisfies the supplied search string.</t> |
5768 |
|
</list> |
5769 |
|
</t> |
5770 |
|
|
5771 |
|
<t>IS_DRUM=true | false |
5772 |
|
<list> |
5773 |
|
<t>Either true or false. Restricts the search to |
5774 |
|
drum kits or chromatic instruments.</t> |
5775 |
|
</list> |
5776 |
|
</t> |
5777 |
|
|
5778 |
|
<t>FORMAT_FAMILIES='<format-list>' |
5779 |
|
<list> |
5780 |
|
<t>Restricts the search to instruments of the supplied format families, |
5781 |
|
where <format-list> is a comma separated list of format families.</t> |
5782 |
|
</list> |
5783 |
|
</t> |
5784 |
|
</t> |
5785 |
|
|
5786 |
|
<t>Where <search-string> is either a regular expression, or a |
5787 |
|
word list separated with spaces for OR search and with '+' for AND search.</t> |
5788 |
|
|
5789 |
|
<t>Possible Answers:</t> |
5790 |
|
<t> |
5791 |
|
<list> |
5792 |
|
<t>A comma separated list with the absolute path names (encapsulated into |
5793 |
|
apostrophes) of all instruments in the specified directory that satisfy |
5794 |
|
the supplied search criterias.</t> |
5795 |
|
<t>"ERR:<error-code>:<error-message>" - |
5796 |
|
<list> |
5797 |
|
<t>if the given directory does not exist.</t> |
5798 |
|
</list> |
5799 |
|
</t> |
5800 |
|
</list> |
5801 |
|
</t> |
5802 |
|
<t>Example:</t> |
5803 |
|
<t> |
5804 |
|
<list> |
5805 |
|
<t>C: "FIND DB_INSTRUMENTS '/Piano Collection' NAME='bosendorfer+290'"</t> |
5806 |
|
<t>S: "'/Piano Collection/Bosendorfer 290'"</t> |
5807 |
|
</list> |
5808 |
|
</t> |
5809 |
|
<t> |
5810 |
|
<list> |
5811 |
|
<t>C: "FIND DB_INSTRUMENTS '/Piano Collection' CREATED='2007-04-01 09:30:13..'"</t> |
5812 |
|
<t>S: "'/Piano Collection/Bosendorfer 290','/Piano Collection/Steinway D'"</t> |
5813 |
|
</list> |
5814 |
|
</t> |
5815 |
|
</section> |
5816 |
|
|
5817 |
|
<section title="Getting job status information" anchor="GET DB_INSTRUMENTS_JOB INFO"> |
5818 |
|
<t>The front-end can ask for the current status of a |
5819 |
|
particular database instruments job by sending the following command:</t> |
5820 |
|
<t> |
5821 |
|
<list> |
5822 |
|
<t>GET DB_INSTRUMENTS_JOB INFO <job-id></t> |
5823 |
|
</list> |
5824 |
|
</t> |
5825 |
|
<t>Where <job-id> should be replaced by the numerical ID |
5826 |
|
of the job the front-end is interested in.</t> |
5827 |
|
|
5828 |
|
<t>Possible Answers:</t> |
5829 |
|
<t> |
5830 |
|
<list> |
5831 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
5832 |
|
Each answer line begins with the settings category name |
5833 |
|
followed by a colon and then a space character <SP> and finally |
5834 |
|
the info character string to that setting category. At the |
5835 |
|
moment the following categories are defined:</t> |
5836 |
|
|
5837 |
|
<t> |
5838 |
|
<list> |
5839 |
|
<t>FILES_TOTAL - |
5840 |
|
<list> |
5841 |
|
<t>The total number of files scheduled for scanning</t> |
5842 |
|
</list> |
5843 |
|
</t> |
5844 |
|
<t>FILES_SCANNED - |
5845 |
|
<list> |
5846 |
|
<t>The current number of scanned files</t> |
5847 |
|
</list> |
5848 |
|
</t> |
5849 |
|
<t>SCANNING - |
5850 |
|
<list> |
5851 |
|
<t>The absolute path name of the file which is currently |
5852 |
|
being scanned</t> |
5853 |
|
</list> |
5854 |
|
</t> |
5855 |
|
<t>STATUS - |
5856 |
|
<list> |
5857 |
|
<t>An integer value between 0 and 100 indicating the |
5858 |
|
scanning progress percentage of the file which is |
5859 |
|
currently being scanned</t> |
5860 |
|
</list> |
5861 |
|
</t> |
5862 |
|
</list> |
5863 |
|
</t> |
5864 |
|
</list> |
5865 |
|
</t> |
5866 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
5867 |
|
|
5868 |
|
<t>Example:</t> |
5869 |
|
<t> |
5870 |
|
<list> |
5871 |
|
<t>C: "GET DB_INSTRUMENTS_JOB INFO 2"</t> |
5872 |
|
<t>S: "FILES_TOTAL: 12"</t> |
5873 |
|
<t> "FILES_SCANNED: 7"</t> |
5874 |
|
<t> "SCANNING: /home/me/gigs/Bosendorfer 290.gig"</t> |
5875 |
|
<t> "STATUS: 42"</t> |
5876 |
|
<t> "."</t> |
5877 |
|
</list> |
5878 |
|
</t> |
5879 |
|
</section> |
5880 |
|
|
5881 |
|
</section> |
5882 |
|
|
5883 |
</section> |
</section> |
5884 |
|
|
5885 |
|
|
5955 |
</t> |
</t> |
5956 |
<t>/ UNSUBSCRIBE SP unsubscribe_event |
<t>/ UNSUBSCRIBE SP unsubscribe_event |
5957 |
</t> |
</t> |
|
<t>/ SELECT SP text |
|
|
</t> |
|
5958 |
<t>/ RESET SP reset_instruction |
<t>/ RESET SP reset_instruction |
5959 |
</t> |
</t> |
5960 |
<t>/ CLEAR SP clear_instruction |
<t>/ CLEAR SP clear_instruction |
5961 |
</t> |
</t> |
5962 |
|
<t>/ FIND SP find_instruction |
5963 |
|
</t> |
5964 |
|
<t>/ MOVE SP move_instruction |
5965 |
|
</t> |
5966 |
|
<t>/ COPY SP copy_instruction |
5967 |
|
</t> |
5968 |
|
<t>/ EDIT SP edit_instruction |
5969 |
|
</t> |
5970 |
<t>/ RESET |
<t>/ RESET |
5971 |
</t> |
</t> |
5972 |
<t>/ QUIT |
<t>/ QUIT |
5977 |
<list> |
<list> |
5978 |
<t>CHANNEL |
<t>CHANNEL |
5979 |
</t> |
</t> |
5980 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP pathname |
5981 |
|
</t> |
5982 |
|
<t>/ DB_INSTRUMENTS SP NON_MODAL SP scan_mode SP pathname SP pathname |
5983 |
|
</t> |
5984 |
|
<t>/ DB_INSTRUMENTS SP scan_mode SP pathname SP pathname |
5985 |
|
</t> |
5986 |
|
<t>/ DB_INSTRUMENTS SP NON_MODAL SP pathname SP pathname |
5987 |
|
</t> |
5988 |
|
<t>/ DB_INSTRUMENTS SP NON_MODAL SP pathname SP pathname SP instrument_index |
5989 |
|
</t> |
5990 |
|
<t>/ DB_INSTRUMENTS SP pathname SP pathname |
5991 |
|
</t> |
5992 |
|
<t>/ DB_INSTRUMENTS SP pathname SP pathname SP instrument_index |
5993 |
|
</t> |
5994 |
<t>/ MIDI_INSTRUMENT_MAP |
<t>/ MIDI_INSTRUMENT_MAP |
5995 |
</t> |
</t> |
5996 |
<t>/ MIDI_INSTRUMENT_MAP SP map_name |
<t>/ MIDI_INSTRUMENT_MAP SP map_name |
6029 |
</t> |
</t> |
6030 |
<t>/ MIDI_INSTRUMENT_INFO |
<t>/ MIDI_INSTRUMENT_INFO |
6031 |
</t> |
</t> |
6032 |
|
<t>/ DB_INSTRUMENT_DIRECTORY_COUNT |
6033 |
|
</t> |
6034 |
|
<t>/ DB_INSTRUMENT_DIRECTORY_INFO |
6035 |
|
</t> |
6036 |
|
<t>/ DB_INSTRUMENT_COUNT |
6037 |
|
</t> |
6038 |
|
<t>/ DB_INSTRUMENT_INFO |
6039 |
|
</t> |
6040 |
|
<t>/ DB_INSTRUMENTS_JOB_INFO |
6041 |
|
</t> |
6042 |
<t>/ MISCELLANEOUS |
<t>/ MISCELLANEOUS |
6043 |
</t> |
</t> |
6044 |
<t>/ TOTAL_VOICE_COUNT |
<t>/ TOTAL_VOICE_COUNT |
6079 |
</t> |
</t> |
6080 |
<t>/ MIDI_INSTRUMENT_INFO |
<t>/ MIDI_INSTRUMENT_INFO |
6081 |
</t> |
</t> |
6082 |
|
<t>/ DB_INSTRUMENT_DIRECTORY_COUNT |
6083 |
|
</t> |
6084 |
|
<t>/ DB_INSTRUMENT_DIRECTORY_INFO |
6085 |
|
</t> |
6086 |
|
<t>/ DB_INSTRUMENT_COUNT |
6087 |
|
</t> |
6088 |
|
<t>/ DB_INSTRUMENT_INFO |
6089 |
|
</t> |
6090 |
|
<t>/ DB_INSTRUMENTS_JOB_INFO |
6091 |
|
</t> |
6092 |
<t>/ MISCELLANEOUS |
<t>/ MISCELLANEOUS |
6093 |
</t> |
</t> |
6094 |
<t>/ TOTAL_VOICE_COUNT |
<t>/ TOTAL_VOICE_COUNT |
6123 |
</t> |
</t> |
6124 |
<t>/ MIDI_INSTRUMENT_MAP SP ALL |
<t>/ MIDI_INSTRUMENT_MAP SP ALL |
6125 |
</t> |
</t> |
6126 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP FORCE SP pathname |
6127 |
|
</t> |
6128 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP pathname |
6129 |
|
</t> |
6130 |
|
<t>/ DB_INSTRUMENT SP pathname |
6131 |
|
</t> |
6132 |
</list> |
</list> |
6133 |
</t> |
</t> |
6134 |
<t>get_instruction = |
<t>get_instruction = |
6199 |
</t> |
</t> |
6200 |
<t>/ FX_SEND SP INFO SP sampler_channel SP fx_send_id |
<t>/ FX_SEND SP INFO SP sampler_channel SP fx_send_id |
6201 |
</t> |
</t> |
6202 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP RECURSIVE SP pathname |
6203 |
|
</t> |
6204 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP pathname |
6205 |
|
</t> |
6206 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP INFO SP pathname |
6207 |
|
</t> |
6208 |
|
<t>/ DB_INSTRUMENTS SP RECURSIVE SP pathname |
6209 |
|
</t> |
6210 |
|
<t>/ DB_INSTRUMENTS SP pathname |
6211 |
|
</t> |
6212 |
|
<t>/ DB_INSTRUMENT SP INFO SP pathname |
6213 |
|
</t> |
6214 |
|
<t>/ DB_INSTRUMENTS_JOB SP INFO SP number |
6215 |
|
</t> |
6216 |
<t>/ VOLUME |
<t>/ VOLUME |
6217 |
</t> |
</t> |
6218 |
</list> |
</list> |
6225 |
</t> |
</t> |
6226 |
<t>/ MIDI_INPUT_DEVICE_PARAMETER SP number SP string '=' param_val_list |
<t>/ MIDI_INPUT_DEVICE_PARAMETER SP number SP string '=' param_val_list |
6227 |
</t> |
</t> |
6228 |
|
<t>/ MIDI_INPUT_PORT_PARAMETER SP number SP number SP string '=' NONE |
6229 |
|
</t> |
6230 |
<t>/ MIDI_INPUT_PORT_PARAMETER SP number SP number SP string '=' param_val_list |
<t>/ MIDI_INPUT_PORT_PARAMETER SP number SP number SP string '=' param_val_list |
6231 |
</t> |
</t> |
6232 |
<t>/ CHANNEL SP set_chan_instruction |
<t>/ CHANNEL SP set_chan_instruction |
6241 |
</t> |
</t> |
6242 |
<t>/ FX_SEND SP LEVEL SP sampler_channel SP fx_send_id SP volume_value |
<t>/ FX_SEND SP LEVEL SP sampler_channel SP fx_send_id SP volume_value |
6243 |
</t> |
</t> |
6244 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP NAME SP pathname SP dirname |
6245 |
|
</t> |
6246 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP DESCRIPTION SP pathname SP stringval |
6247 |
|
</t> |
6248 |
|
<t>/ DB_INSTRUMENT SP NAME SP pathname SP dirname |
6249 |
|
</t> |
6250 |
|
<t>/ DB_INSTRUMENT SP DESCRIPTION SP pathname SP stringval |
6251 |
|
</t> |
6252 |
<t>/ ECHO SP boolean |
<t>/ ECHO SP boolean |
6253 |
</t> |
</t> |
6254 |
<t>/ VOLUME SP volume_value |
<t>/ VOLUME SP volume_value |
6285 |
</t> |
</t> |
6286 |
</list> |
</list> |
6287 |
</t> |
</t> |
6288 |
|
<t>find_instruction = |
6289 |
|
<list> |
6290 |
|
<t>DB_INSTRUMENTS SP NON_RECURSIVE SP pathname SP query_val_list |
6291 |
|
</t> |
6292 |
|
<t>/ DB_INSTRUMENTS SP pathname SP query_val_list |
6293 |
|
</t> |
6294 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP NON_RECURSIVE SP pathname SP query_val_list |
6295 |
|
</t> |
6296 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP pathname SP query_val_list |
6297 |
|
</t> |
6298 |
|
</list> |
6299 |
|
</t> |
6300 |
|
<t>move_instruction = |
6301 |
|
<list> |
6302 |
|
<t>DB_INSTRUMENT_DIRECTORY SP pathname SP pathname |
6303 |
|
</t> |
6304 |
|
<t>/ DB_INSTRUMENT SP pathname SP pathname |
6305 |
|
</t> |
6306 |
|
</list> |
6307 |
|
</t> |
6308 |
|
<t>copy_instruction = |
6309 |
|
<list> |
6310 |
|
<t>DB_INSTRUMENT_DIRECTORY SP pathname SP pathname |
6311 |
|
</t> |
6312 |
|
<t>/ DB_INSTRUMENT SP pathname SP pathname |
6313 |
|
</t> |
6314 |
|
</list> |
6315 |
|
</t> |
6316 |
<t>destroy_instruction = |
<t>destroy_instruction = |
6317 |
<list> |
<list> |
6318 |
<t>AUDIO_OUTPUT_DEVICE SP number |
<t>AUDIO_OUTPUT_DEVICE SP number |
6363 |
</t> |
</t> |
6364 |
</list> |
</list> |
6365 |
</t> |
</t> |
6366 |
|
<t>edit_instruction = |
6367 |
|
<list> |
6368 |
|
<t>INSTRUMENT SP sampler_channel |
6369 |
|
</t> |
6370 |
|
</list> |
6371 |
|
</t> |
6372 |
<t>modal_arg = |
<t>modal_arg = |
6373 |
<list> |
<list> |
6374 |
<t>/* epsilon (empty argument) */ |
<t>/* epsilon (empty argument) */ |
6415 |
</t> |
</t> |
6416 |
<t>/ FX_SENDS SP sampler_channel |
<t>/ FX_SENDS SP sampler_channel |
6417 |
</t> |
</t> |
6418 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP RECURSIVE SP pathname |
6419 |
|
</t> |
6420 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP pathname |
6421 |
|
</t> |
6422 |
|
<t>/ DB_INSTRUMENTS SP RECURSIVE SP pathname |
6423 |
|
</t> |
6424 |
|
<t>/ DB_INSTRUMENTS SP pathname |
6425 |
|
</t> |
6426 |
</list> |
</list> |
6427 |
</t> |
</t> |
6428 |
<t>load_instr_args = |
<t>load_instr_args = |
6543 |
</t> |
</t> |
6544 |
</list> |
</list> |
6545 |
</t> |
</t> |
6546 |
<t>filename = |
<t>pathname = |
6547 |
|
<list> |
6548 |
|
<t>stringval |
6549 |
|
</t> |
6550 |
|
</list> |
6551 |
|
</t> |
6552 |
|
<t>dirname = |
6553 |
<list> |
<list> |
6554 |
<t>stringval |
<t>stringval |
6555 |
</t> |
</t> |
6556 |
</list> |
</list> |
6557 |
</t> |
</t> |
6558 |
|
<t>filename = |
6559 |
|
<list> |
6560 |
|
<t>stringval_escaped |
6561 |
|
</t> |
6562 |
|
</list> |
6563 |
|
</t> |
6564 |
<t>map_name = |
<t>map_name = |
6565 |
<list> |
<list> |
6566 |
<t>stringval |
<t>stringval |
6599 |
</t> |
</t> |
6600 |
</list> |
</list> |
6601 |
</t> |
</t> |
6602 |
|
<t>query_val_list = |
6603 |
|
<list> |
6604 |
|
<t>string '=' query_val |
6605 |
|
</t> |
6606 |
|
<t>/ query_val_list SP string '=' query_val |
6607 |
|
</t> |
6608 |
|
</list> |
6609 |
|
</t> |
6610 |
|
<t>query_val = |
6611 |
|
<list> |
6612 |
|
<t>string |
6613 |
|
</t> |
6614 |
|
<t>/ stringval |
6615 |
|
</t> |
6616 |
|
</list> |
6617 |
|
</t> |
6618 |
|
<t>scan_mode = |
6619 |
|
<list> |
6620 |
|
<t>RECURSIVE |
6621 |
|
</t> |
6622 |
|
<t>/ NON_RECURSIVE |
6623 |
|
</t> |
6624 |
|
<t>/ FLAT |
6625 |
|
</t> |
6626 |
|
</list> |
6627 |
|
</t> |
6628 |
|
|
6629 |
<!-- GRAMMAR_BNF_END - do NOT delete or modify this line !!! --> |
<!-- GRAMMAR_BNF_END - do NOT delete or modify this line !!! --> |
6630 |
|
|
6631 |
|
<section title="Character Set and Escape Sequences" anchor="character_set"> |
6632 |
|
<t>Older versions of this protocol up to and including v1.1 only |
6633 |
|
supported the standard ASCII character set (ASCII code 0 - 127) |
6634 |
|
<xref target="RFC20"/>, all younger versions of this protocol |
6635 |
|
however support the Extended ASCII character set (ASCII code |
6636 |
|
0 - 255). The same group of younger protocols also support |
6637 |
|
escape sequences, but only for certain, explicitly declared |
6638 |
|
parts of the protocol. The supported escape sequences are |
6639 |
|
defined as follows:</t> |
6640 |
|
<texttable> |
6641 |
|
<ttcol>ASCII Character Sequence</ttcol> |
6642 |
|
<ttcol>Translated into (Name)</ttcol> |
6643 |
|
<c>\n</c> <c>new line</c> |
6644 |
|
<c>\r</c> <c>carriage return</c> |
6645 |
|
<c>\f</c> <c>form feed</c> |
6646 |
|
<c>\t</c> <c>horizontal tab</c> |
6647 |
|
<c>\v</c> <c>vertical tab</c> |
6648 |
|
<c>\'</c> <c>apostrophe</c> |
6649 |
|
<c>\"</c> <c>quotation mark</c> |
6650 |
|
<c>\\</c> <c>backslash</c> |
6651 |
|
<c>\OOO</c> <c>three digit octal ASCII code of the character</c> |
6652 |
|
<c>\xHH</c> <c>two digit hex ASCII code of the character</c> |
6653 |
|
</texttable> |
6654 |
|
<t>Notice: due to the transition of certain parts of the |
6655 |
|
protocol which now support escape sequences, a slight backward |
6656 |
|
incompatibility to protocols version v1.1 and younger has been |
6657 |
|
introduced. The only difference is that in parts of the protocol |
6658 |
|
where escape characters are now supported, a backslash characters |
6659 |
|
MUST be escaped as well (that is as double backslash), whereas |
6660 |
|
in the old versions a single backslash was sufficient.</t> |
6661 |
|
</section> |
6662 |
</section> |
</section> |
6663 |
|
|
6664 |
<section title="Events" anchor="events"> |
<section title="Events" anchor="events"> |
6844 |
</section> |
</section> |
6845 |
|
|
6846 |
<section title="Number of effect sends changed" anchor="SUBSCRIBE FX_SEND_COUNT"> |
<section title="Number of effect sends changed" anchor="SUBSCRIBE FX_SEND_COUNT"> |
6847 |
<t>Client may want to be notified when the number of effect sends on |
<t>Client may want to be notified when the number of effect sends on |
6848 |
a particular sampler channel is changed by issuing the following command:</t> |
a particular sampler channel is changed by issuing the following command:</t> |
6849 |
<t> |
<t> |
6850 |
<list> |
<list> |
7000 |
</t> |
</t> |
7001 |
</section> |
</section> |
7002 |
|
|
7003 |
|
<section title="Number of database instrument directories changed" anchor="SUBSCRIBE DB_INSTRUMENT_DIRECTORY_COUNT"> |
7004 |
|
<t>Client may want to be notified when the number of instrument |
7005 |
|
directories in a particular directory in the instruments database |
7006 |
|
is changed by issuing the following command:</t> |
7007 |
|
<t> |
7008 |
|
<list> |
7009 |
|
<t>SUBSCRIBE DB_INSTRUMENT_DIRECTORY_COUNT</t> |
7010 |
|
</list> |
7011 |
|
</t> |
7012 |
|
<t>Server will start sending the following notification messages:</t> |
7013 |
|
<t> |
7014 |
|
<list> |
7015 |
|
<t>"NOTIFY:DB_INSTRUMENT_DIRECTORY_COUNT:<dir-path>"</t> |
7016 |
|
</list> |
7017 |
|
</t> |
7018 |
|
<t>where <dir-path> will be replaced by the absolute path |
7019 |
|
name of the directory in the instruments database, |
7020 |
|
in which the number of directories is changed.</t> |
7021 |
|
<t>Note that when a non-empty directory is removed, this event |
7022 |
|
is not sent for the subdirectories in that directory.</t> |
7023 |
|
</section> |
7024 |
|
|
7025 |
|
<section title="Database instrument directory information changed" anchor="SUBSCRIBE DB_INSTRUMENT_DIRECTORY_INFO"> |
7026 |
|
<t>Client may want to be notified when changes were made to directories |
7027 |
|
in the instruments database by issuing the following command:</t> |
7028 |
|
<t> |
7029 |
|
<list> |
7030 |
|
<t>SUBSCRIBE DB_INSTRUMENT_DIRECTORY_INFO</t> |
7031 |
|
</list> |
7032 |
|
</t> |
7033 |
|
<t>Server will start sending the following notification messages:</t> |
7034 |
|
<t> |
7035 |
|
<list> |
7036 |
|
<t>"NOTIFY:DB_INSTRUMENT_DIRECTORY_INFO:<dir-path>"</t> |
7037 |
|
</list> |
7038 |
|
</t> |
7039 |
|
<t>where <dir-path> will be replaced by the absolute path name |
7040 |
|
of the directory, for which information changes occurred. The front-end will have to send |
7041 |
|
the respective command to actually get the updated directory info. Because these messages |
7042 |
|
will be triggered by LSCP commands issued by other clients rather than real |
7043 |
|
time events happening on the server, it is believed that an empty notification |
7044 |
|
message is sufficient here.</t> |
7045 |
|
<t> |
7046 |
|
<list> |
7047 |
|
<t>"NOTIFY:DB_INSTRUMENT_DIRECTORY_INFO:NAME <old-dir-path> <new-name>"</t> |
7048 |
|
</list> |
7049 |
|
</t> |
7050 |
|
<t>where <old-dir-path> is the old absolute path name of the directory |
7051 |
|
(encapsulated into apostrophes), which name is changes and <new-name> is |
7052 |
|
the new name of the directory, encapsulated into apostrophes.</t> |
7053 |
|
</section> |
7054 |
|
|
7055 |
|
<section title="Number of database instruments changed" anchor="SUBSCRIBE DB_INSTRUMENT_COUNT"> |
7056 |
|
<t>Client may want to be notified when the number of instruments |
7057 |
|
in a particular directory in the instruments database |
7058 |
|
is changed by issuing the following command:</t> |
7059 |
|
<t> |
7060 |
|
<list> |
7061 |
|
<t>SUBSCRIBE DB_INSTRUMENT_COUNT</t> |
7062 |
|
</list> |
7063 |
|
</t> |
7064 |
|
<t>Server will start sending the following notification messages:</t> |
7065 |
|
<t> |
7066 |
|
<list> |
7067 |
|
<t>"NOTIFY:DB_INSTRUMENT_COUNT:<dir-path>"</t> |
7068 |
|
</list> |
7069 |
|
</t> |
7070 |
|
<t>where <dir-path> will be replaced by the absolute path |
7071 |
|
name of the directory in the instruments database, |
7072 |
|
in which the number of instruments is changed.</t> |
7073 |
|
<t>Note that when a non-empty directory is removed, this event |
7074 |
|
is not sent for the instruments in that directory.</t> |
7075 |
|
</section> |
7076 |
|
|
7077 |
|
<section title="Database instrument information changed" anchor="SUBSCRIBE DB_INSTRUMENT_INFO"> |
7078 |
|
<t>Client may want to be notified when changes were made to instruments |
7079 |
|
in the instruments database by issuing the following command:</t> |
7080 |
|
<t> |
7081 |
|
<list> |
7082 |
|
<t>SUBSCRIBE DB_INSTRUMENT_INFO</t> |
7083 |
|
</list> |
7084 |
|
</t> |
7085 |
|
<t>Server will start sending the following notification messages:</t> |
7086 |
|
<t> |
7087 |
|
<list> |
7088 |
|
<t>"NOTIFY:DB_INSTRUMENT_INFO:<instr-path>"</t> |
7089 |
|
</list> |
7090 |
|
</t> |
7091 |
|
<t>where <instr-path> will be replaced by the absolute path name |
7092 |
|
of the instrument, which settings are changed. The front-end will have to send |
7093 |
|
the respective command to actually get the updated directory info. Because these messages |
7094 |
|
will be triggered by LSCP commands issued by other clients rather than real |
7095 |
|
time events happening on the server, it is believed that an empty notification |
7096 |
|
message is sufficient here.</t> |
7097 |
|
<t> |
7098 |
|
<list> |
7099 |
|
<t>"NOTIFY:DB_INSTRUMENT_INFO:NAME <old-instr-path> <new-name>"</t> |
7100 |
|
</list> |
7101 |
|
</t> |
7102 |
|
<t>where <old-instr-path> is the old absolute path name of the instrument |
7103 |
|
(encapsulated into apostrophes), which name is changes and <new-name> is |
7104 |
|
the new name of the instrument, encapsulated into apostrophes.</t> |
7105 |
|
</section> |
7106 |
|
|
7107 |
|
<section title="Database job status information changed" anchor="SUBSCRIBE DB_INSTRUMENTS_JOB_INFO"> |
7108 |
|
<t>Client may want to be notified when the status of particular database |
7109 |
|
instruments job is changed by issuing the following command:</t> |
7110 |
|
<t> |
7111 |
|
<list> |
7112 |
|
<t>SUBSCRIBE DB_INSTRUMENTS_JOB_INFO</t> |
7113 |
|
</list> |
7114 |
|
</t> |
7115 |
|
<t>Server will start sending the following notification messages:</t> |
7116 |
|
<t> |
7117 |
|
<list> |
7118 |
|
<t>"NOTIFY:DB_INSTRUMENTS_JOB_INFO:<job-id>"</t> |
7119 |
|
</list> |
7120 |
|
</t> |
7121 |
|
<t>where <job-id> will be replaced by the numerical ID of the job, |
7122 |
|
which status is changed. The front-end will have to send the respective |
7123 |
|
command to actually get the status info. Because these messages |
7124 |
|
will be triggered by LSCP commands issued by other clients rather than real |
7125 |
|
time events happening on the server, it is believed that an empty notification |
7126 |
|
message is sufficient here.</t> |
7127 |
|
</section> |
7128 |
|
|
7129 |
<section title="Miscellaneous and debugging events" anchor="SUBSCRIBE MISCELLANEOUS"> |
<section title="Miscellaneous and debugging events" anchor="SUBSCRIBE MISCELLANEOUS"> |
7130 |
<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 |
7131 |
the server by issuing the following command:</t> |
the server by issuing the following command:</t> |
7204 |
</front> |
</front> |
7205 |
<seriesInfo name="RFC" value="2234" /> |
<seriesInfo name="RFC" value="2234" /> |
7206 |
</reference> |
</reference> |
7207 |
|
<reference anchor="RFC20"> |
7208 |
|
<front> |
7209 |
|
<title>ASCII format for Network Interchange</title> |
7210 |
|
<author> |
7211 |
|
<organization>UCLA</organization> |
7212 |
|
</author> |
7213 |
|
<date year="1969"></date> |
7214 |
|
</front> |
7215 |
|
<seriesInfo name="RFC" value="20" /> |
7216 |
|
</reference> |
7217 |
</references> |
</references> |
7218 |
</back> |
</back> |
7219 |
|
|