1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> |
2 |
<html lang="en"><head><title>LinuxSampler Control Protocol</title> |
<html lang="en"><head><title>LinuxSampler Control Protocol (draft)</title> |
3 |
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> |
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> |
4 |
<meta name="description" content="LinuxSampler Control Protocol"> |
<meta name="description" content="LinuxSampler Control Protocol (draft)"> |
5 |
<meta name="keywords" content="LSCP"> |
<meta name="keywords" content="LSCP"> |
6 |
<meta name="generator" content="xml2rfc v1.32 (http://xml.resource.org/)"> |
<meta name="generator" content="xml2rfc v1.32 (http://xml.resource.org/)"> |
7 |
<style type='text/css'><!-- |
<style type='text/css'><!-- |
145 |
<tr><td class="header">LinuxSampler Developers</td><td class="header">C. Schoenebeck</td></tr> |
<tr><td class="header">LinuxSampler Developers</td><td class="header">C. Schoenebeck</td></tr> |
146 |
<tr><td class="header">Internet-Draft</td><td class="header">Interessengemeinschaft Software</td></tr> |
<tr><td class="header">Internet-Draft</td><td class="header">Interessengemeinschaft Software</td></tr> |
147 |
<tr><td class="header">Intended status: Standards Track</td><td class="header">Engineering e. V.</td></tr> |
<tr><td class="header">Intended status: Standards Track</td><td class="header">Engineering e. V.</td></tr> |
148 |
<tr><td class="header">Expires: November 17, 2007</td><td class="header">May 16, 2007</td></tr> |
<tr><td class="header">Expires: December 24, 2007</td><td class="header">June 22, 2007</td></tr> |
149 |
</table></td></tr></table> |
</table></td></tr></table> |
150 |
<h1><br />LinuxSampler Control Protocol<br />LSCP 1.2</h1> |
<h1><br />LinuxSampler Control Protocol (draft)<br />LSCP 1.2cvs</h1> |
151 |
|
|
152 |
<h3>Status of this Memo</h3> |
<h3>Status of this Memo</h3> |
153 |
<p> |
<p> |
173 |
The list of Internet-Draft Shadow Directories can be accessed at |
The list of Internet-Draft Shadow Directories can be accessed at |
174 |
<a href='http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html</a>.</p> |
<a href='http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html</a>.</p> |
175 |
<p> |
<p> |
176 |
This Internet-Draft will expire on November 17, 2007.</p> |
This Internet-Draft will expire on December 24, 2007.</p> |
177 |
|
|
178 |
<h3>Copyright Notice</h3> |
<h3>Copyright Notice</h3> |
179 |
<p> |
<p> |
430 |
Changing the description of instrument<br /> |
Changing the description of instrument<br /> |
431 |
<a href="#FIND DB_INSTRUMENTS">6.8.20.</a> |
<a href="#FIND DB_INSTRUMENTS">6.8.20.</a> |
432 |
Finding instruments<br /> |
Finding instruments<br /> |
433 |
|
<a href="#GET DB_INSTRUMENTS_JOB INFO">6.8.21.</a> |
434 |
|
Getting job status information<br /> |
435 |
<a href="#command_syntax">7.</a> |
<a href="#command_syntax">7.</a> |
436 |
Command Syntax<br /> |
Command Syntax<br /> |
437 |
|
<a href="#character_set">7.1.</a> |
438 |
|
Character Set and Escape Sequences<br /> |
439 |
<a href="#events">8.</a> |
<a href="#events">8.</a> |
440 |
Events<br /> |
Events<br /> |
441 |
<a href="#SUBSCRIBE AUDIO_OUTPUT_DEVICE_COUNT">8.1.</a> |
<a href="#SUBSCRIBE AUDIO_OUTPUT_DEVICE_COUNT">8.1.</a> |
480 |
Number of database instruments changed<br /> |
Number of database instruments changed<br /> |
481 |
<a href="#SUBSCRIBE DB_INSTRUMENT_INFO">8.21.</a> |
<a href="#SUBSCRIBE DB_INSTRUMENT_INFO">8.21.</a> |
482 |
Database instrument information changed<br /> |
Database instrument information changed<br /> |
483 |
<a href="#SUBSCRIBE MISCELLANEOUS">8.22.</a> |
<a href="#SUBSCRIBE DB_INSTRUMENTS_JOB_INFO">8.22.</a> |
484 |
|
Database job status information changed<br /> |
485 |
|
<a href="#SUBSCRIBE MISCELLANEOUS">8.23.</a> |
486 |
Miscellaneous and debugging events<br /> |
Miscellaneous and debugging events<br /> |
487 |
<a href="#anchor14">9.</a> |
<a href="#anchor14">9.</a> |
488 |
Security Considerations<br /> |
Security Considerations<br /> |
514 |
(front-end) and server (LinuxSampler) respectively. Lines in |
(front-end) and server (LinuxSampler) respectively. Lines in |
515 |
examples must be interpreted as every line being CRLF |
examples must be interpreted as every line being CRLF |
516 |
terminated (carriage return character followed by line feed |
terminated (carriage return character followed by line feed |
517 |
character as defined in the ASCII standard), thus the following |
character as defined in the ASCII standard <a class='info' href='#RFC20'>[RFC20]<span> (</span><span class='info'>UCLA, “ASCII format for Network Interchange,” 1969.</span><span>)</span></a>), |
518 |
example: |
thus the following example: |
519 |
</p> |
</p> |
520 |
<p> |
<p> |
521 |
</p> |
</p> |
3377 |
number of the sampler channel the instrument should be assigned to. |
number of the sampler channel the instrument should be assigned to. |
3378 |
Each sampler channel can only have one instrument. |
Each sampler channel can only have one instrument. |
3379 |
</p> |
</p> |
3380 |
|
<p>Notice: since LSCP 1.2 the <filename> argument supports |
3381 |
|
escape characters for special characters (see chapter |
3382 |
|
"<a class='info' href='#character_set'>Character Set and Escape Sequences<span> (</span><span class='info'>Character Set and Escape Sequences</span><span>)</span></a>" |
3383 |
|
for details) and accordingly backslash characters in the filename |
3384 |
|
MUST now be escaped as well! |
3385 |
|
</p> |
3386 |
<p>The difference between regular and NON_MODAL versions of the command |
<p>The difference between regular and NON_MODAL versions of the command |
3387 |
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 |
3388 |
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 |
6655 |
index, <engine_name> a sampler engine name as returned by |
index, <engine_name> a sampler engine name as returned by |
6656 |
the <a class='info' href='#LIST AVAILABLE_ENGINES'>"LIST AVAILABLE_ENGINES"<span> (</span><span class='info'>Getting all available engines</span><span>)</span></a> |
the <a class='info' href='#LIST AVAILABLE_ENGINES'>"LIST AVAILABLE_ENGINES"<span> (</span><span class='info'>Getting all available engines</span><span>)</span></a> |
6657 |
command (not encapsulated into apostrophes), <filename> the name |
command (not encapsulated into apostrophes), <filename> the name |
6658 |
of the instrument's file to be deployed (encapsulated into apostrophes), |
of the instrument's file to be deployed (encapsulated into apostrophes, |
6659 |
|
supporting escape sequences as described in chapter |
6660 |
|
"<a class='info' href='#character_set'>Character Set and Escape Sequences<span> (</span><span class='info'>Character Set and Escape Sequences</span><span>)</span></a>"), |
6661 |
<instrument_index> the index (integer value) of the instrument |
<instrument_index> the index (integer value) of the instrument |
6662 |
within the given file, <volume_value> reflects the master |
within the given file, <volume_value> reflects the master |
6663 |
volume of the instrument as optionally dotted number (where a |
volume of the instrument as optionally dotted number (where a |
7930 |
<p> |
<p> |
7931 |
</p> |
</p> |
7932 |
<blockquote class="text"> |
<blockquote class="text"> |
7933 |
<p>ADD DB_INSTRUMENTS [<mode>] <db_dir> <file_path> [<instr_index>] |
<p>ADD DB_INSTRUMENTS [NON_MODAL] [<mode>] <db_dir> <file_path> [<instr_index>] |
7934 |
</p> |
</p> |
7935 |
</blockquote><p> |
</blockquote><p> |
7936 |
|
|
7952 |
<p> |
<p> |
7953 |
</p> |
</p> |
7954 |
<blockquote class="text"> |
<blockquote class="text"> |
7955 |
|
<p>"RECURSIVE" - |
7956 |
|
</p> |
7957 |
|
<blockquote class="text"> |
7958 |
|
<p>All instruments will be processed, including those |
7959 |
|
in the subdirectories, and the respective subdirectory |
7960 |
|
tree structure will be recreated in the instruments |
7961 |
|
database |
7962 |
|
</p> |
7963 |
|
</blockquote> |
7964 |
|
|
7965 |
|
|
7966 |
<p>"NON_RECURSIVE" - |
<p>"NON_RECURSIVE" - |
7967 |
</p> |
</p> |
7968 |
<blockquote class="text"> |
<blockquote class="text"> |
7985 |
</blockquote> |
</blockquote> |
7986 |
|
|
7987 |
|
|
|
<p>not supplied - |
|
|
</p> |
|
|
<blockquote class="text"> |
|
|
<p>The subdirectory tree structure will be recreated |
|
|
in the instruments database and all instruments will be |
|
|
processed and added to the respective subdirectory |
|
|
in the instruments database. |
|
|
</p> |
|
|
</blockquote> |
|
|
|
|
|
|
|
7988 |
</blockquote><p> |
</blockquote><p> |
7989 |
|
|
7990 |
</p> |
</p> |
7991 |
|
<p>The difference between regular and NON_MODAL versions of the command |
7992 |
|
is that the regular command returns when the scanning is finished |
7993 |
|
while NON_MODAL version returns immediately and a background process is launched. |
7994 |
|
The <a class='info' href='#GET DB_INSTRUMENTS_JOB INFO'>GET DB_INSTRUMENTS_JOB INFO<span> (</span><span class='info'>Getting job status information</span><span>)</span></a> |
7995 |
|
command can be used to monitor the scanning progress. |
7996 |
|
</p> |
7997 |
<p>Possible Answers: |
<p>Possible Answers: |
7998 |
</p> |
</p> |
7999 |
<p> |
<p> |
8002 |
<p>"OK" - |
<p>"OK" - |
8003 |
</p> |
</p> |
8004 |
<blockquote class="text"> |
<blockquote class="text"> |
8005 |
<p>on success |
<p>on success when NON_MODAL is not supplied |
8006 |
|
</p> |
8007 |
|
</blockquote> |
8008 |
|
|
8009 |
|
|
8010 |
|
<p>"OK[<job-id>]" - |
8011 |
|
</p> |
8012 |
|
<blockquote class="text"> |
8013 |
|
<p>on success when NON_MODAL is supplied, where <job-id> |
8014 |
|
is a numerical ID used to obtain status information about the job progress. |
8015 |
|
See <a class='info' href='#GET DB_INSTRUMENTS_JOB INFO'>GET DB_INSTRUMENTS_JOB INFO<span> (</span><span class='info'>Getting job status information</span><span>)</span></a> |
8016 |
|
|
8017 |
</p> |
</p> |
8018 |
</blockquote> |
</blockquote> |
8019 |
|
|
8659 |
<p>SIZE=[<min>]..[<max>] |
<p>SIZE=[<min>]..[<max>] |
8660 |
</p> |
</p> |
8661 |
<blockquote class="text"> |
<blockquote class="text"> |
8662 |
<p>Restricts the search to instruments, which |
<p>Restricts the search to instruments, which |
8663 |
size is in the specified range. If <min> is omitted, |
size is in the specified range. If <min> is omitted, |
8664 |
the search results are restricted to instruments with size less then |
the search results are restricted to instruments with size less then |
8665 |
or equal to <max>. If <max> is omitted, the |
or equal to <max>. If <max> is omitted, the |
8750 |
<p>IS_DRUM=true | false |
<p>IS_DRUM=true | false |
8751 |
</p> |
</p> |
8752 |
<blockquote class="text"> |
<blockquote class="text"> |
8753 |
<p>Either true or false. Restricts the search to |
<p>Either true or false. Restricts the search to |
8754 |
drum kits or chromatic instruments. |
drum kits or chromatic instruments. |
8755 |
</p> |
</p> |
8756 |
</blockquote><p> |
</blockquote><p> |
8814 |
</blockquote><p> |
</blockquote><p> |
8815 |
|
|
8816 |
</p> |
</p> |
8817 |
|
<a name="GET DB_INSTRUMENTS_JOB INFO"></a><br /><hr /> |
8818 |
|
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> |
8819 |
|
<a name="rfc.section.6.8.21"></a><h3>6.8.21. |
8820 |
|
Getting job status information</h3> |
8821 |
|
|
8822 |
|
<p>The front-end can ask for the current status of a |
8823 |
|
particular database instruments job by sending the following command: |
8824 |
|
</p> |
8825 |
|
<p> |
8826 |
|
</p> |
8827 |
|
<blockquote class="text"> |
8828 |
|
<p>GET DB_INSTRUMENTS_JOB INFO <job-id> |
8829 |
|
</p> |
8830 |
|
</blockquote><p> |
8831 |
|
|
8832 |
|
</p> |
8833 |
|
<p>Where <job-id> should be replaced by the numerical ID |
8834 |
|
of the job the front-end is interested in. |
8835 |
|
</p> |
8836 |
|
<p>Possible Answers: |
8837 |
|
</p> |
8838 |
|
<p> |
8839 |
|
</p> |
8840 |
|
<blockquote class="text"> |
8841 |
|
<p>LinuxSampler will answer by sending a <CRLF> separated list. |
8842 |
|
Each answer line begins with the settings category name |
8843 |
|
followed by a colon and then a space character <SP> and finally |
8844 |
|
the info character string to that setting category. At the |
8845 |
|
moment the following categories are defined: |
8846 |
|
</p> |
8847 |
|
<p> |
8848 |
|
</p> |
8849 |
|
<blockquote class="text"> |
8850 |
|
<p>FILES_TOTAL - |
8851 |
|
</p> |
8852 |
|
<blockquote class="text"> |
8853 |
|
<p>The total number of files scheduled for scanning |
8854 |
|
</p> |
8855 |
|
</blockquote> |
8856 |
|
|
8857 |
|
|
8858 |
|
<p>FILES_SCANNED - |
8859 |
|
</p> |
8860 |
|
<blockquote class="text"> |
8861 |
|
<p>The current number of scanned files |
8862 |
|
</p> |
8863 |
|
</blockquote> |
8864 |
|
|
8865 |
|
|
8866 |
|
<p>SCANNING - |
8867 |
|
</p> |
8868 |
|
<blockquote class="text"> |
8869 |
|
<p>The absolute path name of the file which is currently |
8870 |
|
being scanned |
8871 |
|
</p> |
8872 |
|
</blockquote> |
8873 |
|
|
8874 |
|
|
8875 |
|
<p>STATUS - |
8876 |
|
</p> |
8877 |
|
<blockquote class="text"> |
8878 |
|
<p>An integer value between 0 and 100 indicating the |
8879 |
|
scanning progress percentage of the file which is |
8880 |
|
currently being scanned |
8881 |
|
</p> |
8882 |
|
</blockquote> |
8883 |
|
|
8884 |
|
|
8885 |
|
</blockquote> |
8886 |
|
|
8887 |
|
|
8888 |
|
</blockquote><p> |
8889 |
|
|
8890 |
|
</p> |
8891 |
|
<p>The mentioned fields above don't have to be in particular order. |
8892 |
|
</p> |
8893 |
|
<p>Example: |
8894 |
|
</p> |
8895 |
|
<p> |
8896 |
|
</p> |
8897 |
|
<blockquote class="text"> |
8898 |
|
<p>C: "GET DB_INSTRUMENTS_JOB INFO 2" |
8899 |
|
</p> |
8900 |
|
<p>S: "FILES_TOTAL: 12" |
8901 |
|
</p> |
8902 |
|
<p> "FILES_SCANNED: 7" |
8903 |
|
</p> |
8904 |
|
<p> "SCANNING: /home/me/gigs/Bosendorfer 290.gig" |
8905 |
|
</p> |
8906 |
|
<p> "STATUS: 42" |
8907 |
|
</p> |
8908 |
|
<p> "." |
8909 |
|
</p> |
8910 |
|
</blockquote><p> |
8911 |
|
|
8912 |
|
</p> |
8913 |
<a name="command_syntax"></a><br /><hr /> |
<a name="command_syntax"></a><br /><hr /> |
8914 |
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> |
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> |
8915 |
<a name="rfc.section.7"></a><h3>7. |
<a name="rfc.section.7"></a><h3>7. |
9025 |
<p>/ COPY SP copy_instruction |
<p>/ COPY SP copy_instruction |
9026 |
|
|
9027 |
</p> |
</p> |
9028 |
|
<p>/ EDIT SP edit_instruction |
9029 |
|
|
9030 |
|
</p> |
9031 |
<p>/ RESET |
<p>/ RESET |
9032 |
|
|
9033 |
</p> |
</p> |
9046 |
<p>/ DB_INSTRUMENT_DIRECTORY SP pathname |
<p>/ DB_INSTRUMENT_DIRECTORY SP pathname |
9047 |
|
|
9048 |
</p> |
</p> |
9049 |
<p>/ DB_INSTRUMENTS SP FLAT SP pathname SP pathname |
<p>/ DB_INSTRUMENTS SP NON_MODAL SP scan_mode SP pathname SP pathname |
9050 |
|
|
9051 |
|
</p> |
9052 |
|
<p>/ DB_INSTRUMENTS SP scan_mode SP pathname SP pathname |
9053 |
|
|
9054 |
|
</p> |
9055 |
|
<p>/ DB_INSTRUMENTS SP NON_MODAL SP pathname SP pathname |
9056 |
|
|
9057 |
</p> |
</p> |
9058 |
<p>/ DB_INSTRUMENTS SP NON_RECURSIVE SP pathname SP pathname |
<p>/ DB_INSTRUMENTS SP NON_MODAL SP pathname SP pathname SP instrument_index |
9059 |
|
|
9060 |
</p> |
</p> |
9061 |
<p>/ DB_INSTRUMENTS SP pathname SP pathname |
<p>/ DB_INSTRUMENTS SP pathname SP pathname |
9133 |
<p>/ DB_INSTRUMENT_INFO |
<p>/ DB_INSTRUMENT_INFO |
9134 |
|
|
9135 |
</p> |
</p> |
9136 |
|
<p>/ DB_INSTRUMENTS_JOB_INFO |
9137 |
|
|
9138 |
|
</p> |
9139 |
<p>/ MISCELLANEOUS |
<p>/ MISCELLANEOUS |
9140 |
|
|
9141 |
</p> |
</p> |
9208 |
<p>/ DB_INSTRUMENT_INFO |
<p>/ DB_INSTRUMENT_INFO |
9209 |
|
|
9210 |
</p> |
</p> |
9211 |
|
<p>/ DB_INSTRUMENTS_JOB_INFO |
9212 |
|
|
9213 |
|
</p> |
9214 |
<p>/ MISCELLANEOUS |
<p>/ MISCELLANEOUS |
9215 |
|
|
9216 |
</p> |
</p> |
9394 |
<p>/ DB_INSTRUMENT SP INFO SP pathname |
<p>/ DB_INSTRUMENT SP INFO SP pathname |
9395 |
|
|
9396 |
</p> |
</p> |
9397 |
|
<p>/ DB_INSTRUMENTS_JOB SP INFO SP number |
9398 |
|
|
9399 |
|
</p> |
9400 |
<p>/ VOLUME |
<p>/ VOLUME |
9401 |
|
|
9402 |
</p> |
</p> |
9619 |
</blockquote><p> |
</blockquote><p> |
9620 |
|
|
9621 |
</p> |
</p> |
9622 |
|
<p>edit_instruction = |
9623 |
|
</p> |
9624 |
|
<blockquote class="text"> |
9625 |
|
<p>INSTRUMENT SP sampler_channel |
9626 |
|
|
9627 |
|
</p> |
9628 |
|
</blockquote><p> |
9629 |
|
|
9630 |
|
</p> |
9631 |
<p>modal_arg = |
<p>modal_arg = |
9632 |
</p> |
</p> |
9633 |
<blockquote class="text"> |
<blockquote class="text"> |
9910 |
<p>filename = |
<p>filename = |
9911 |
</p> |
</p> |
9912 |
<blockquote class="text"> |
<blockquote class="text"> |
9913 |
<p>stringval |
<p>stringval_escaped |
9914 |
|
|
9915 |
</p> |
</p> |
9916 |
</blockquote><p> |
</blockquote><p> |
9997 |
</blockquote><p> |
</blockquote><p> |
9998 |
|
|
9999 |
</p> |
</p> |
10000 |
|
<p>scan_mode = |
10001 |
|
</p> |
10002 |
|
<blockquote class="text"> |
10003 |
|
<p>RECURSIVE |
10004 |
|
|
10005 |
|
</p> |
10006 |
|
<p>/ NON_RECURSIVE |
10007 |
|
|
10008 |
|
</p> |
10009 |
|
<p>/ FLAT |
10010 |
|
|
10011 |
|
</p> |
10012 |
|
</blockquote><p> |
10013 |
|
|
10014 |
|
</p> |
10015 |
|
<a name="character_set"></a><br /><hr /> |
10016 |
|
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> |
10017 |
|
<a name="rfc.section.7.1"></a><h3>7.1. |
10018 |
|
Character Set and Escape Sequences</h3> |
10019 |
|
|
10020 |
|
<p>Older versions of this protocol up to and including v1.1 only |
10021 |
|
supported the standard ASCII character set (ASCII code 0 - 127) |
10022 |
|
<a class='info' href='#RFC20'>[RFC20]<span> (</span><span class='info'>UCLA, “ASCII format for Network Interchange,” 1969.</span><span>)</span></a>, all younger versions of this protocol |
10023 |
|
however support the Extended ASCII character set (ASCII code |
10024 |
|
0 - 255). The same group of younger protocols also support |
10025 |
|
escape sequences, but only for certain, explicitly declared |
10026 |
|
parts of the protocol. The supported escape sequences are |
10027 |
|
defined as follows: |
10028 |
|
</p><table class="full" align="center" border="0" cellpadding="2" cellspacing="2"> |
10029 |
|
<col align="left"><col align="left"> |
10030 |
|
<tr><th align="left">ASCII Character Sequence</th><th align="left">Translated into (Name)</th></tr> |
10031 |
|
<tr> |
10032 |
|
<td align="left">\n</td> |
10033 |
|
<td align="left">new line</td> |
10034 |
|
</tr> |
10035 |
|
<tr> |
10036 |
|
<td align="left">\r</td> |
10037 |
|
<td align="left">carriage return</td> |
10038 |
|
</tr> |
10039 |
|
<tr> |
10040 |
|
<td align="left">\f</td> |
10041 |
|
<td align="left">form feed</td> |
10042 |
|
</tr> |
10043 |
|
<tr> |
10044 |
|
<td align="left">\t</td> |
10045 |
|
<td align="left">horizontal tab</td> |
10046 |
|
</tr> |
10047 |
|
<tr> |
10048 |
|
<td align="left">\v</td> |
10049 |
|
<td align="left">vertical tab</td> |
10050 |
|
</tr> |
10051 |
|
<tr> |
10052 |
|
<td align="left">\'</td> |
10053 |
|
<td align="left">apostrophe</td> |
10054 |
|
</tr> |
10055 |
|
<tr> |
10056 |
|
<td align="left">\"</td> |
10057 |
|
<td align="left">quotation mark</td> |
10058 |
|
</tr> |
10059 |
|
<tr> |
10060 |
|
<td align="left">\\</td> |
10061 |
|
<td align="left">backslash</td> |
10062 |
|
</tr> |
10063 |
|
<tr> |
10064 |
|
<td align="left">\OOO</td> |
10065 |
|
<td align="left">three digit octal ASCII code of the character</td> |
10066 |
|
</tr> |
10067 |
|
<tr> |
10068 |
|
<td align="left">\xHH</td> |
10069 |
|
<td align="left">two digit hex ASCII code of the character</td> |
10070 |
|
</tr> |
10071 |
|
</table> |
10072 |
|
|
10073 |
|
<p>Notice: due to the transition of certain parts of the |
10074 |
|
protocol which now support escape sequences, a slight backward |
10075 |
|
incompatibility to protocols version v1.1 and younger has been |
10076 |
|
introduced. The only difference is that in parts of the protocol |
10077 |
|
where escape characters are now supported, a backslash characters |
10078 |
|
MUST be escaped as well (that is as double backslash), whereas |
10079 |
|
in the old versions a single backslash was sufficient. |
10080 |
|
</p> |
10081 |
<a name="events"></a><br /><hr /> |
<a name="events"></a><br /><hr /> |
10082 |
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> |
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> |
10083 |
<a name="rfc.section.8"></a><h3>8. |
<a name="rfc.section.8"></a><h3>8. |
10367 |
<a name="rfc.section.8.10"></a><h3>8.10. |
<a name="rfc.section.8.10"></a><h3>8.10. |
10368 |
Number of effect sends changed</h3> |
Number of effect sends changed</h3> |
10369 |
|
|
10370 |
<p>Client may want to be notified when the number of effect sends on |
<p>Client may want to be notified when the number of effect sends on |
10371 |
a particular sampler channel is changed by issuing the following command: |
a particular sampler channel is changed by issuing the following command: |
10372 |
</p> |
</p> |
10373 |
<p> |
<p> |
10764 |
(encapsulated into apostrophes), which name is changes and <new-name> is |
(encapsulated into apostrophes), which name is changes and <new-name> is |
10765 |
the new name of the instrument, encapsulated into apostrophes. |
the new name of the instrument, encapsulated into apostrophes. |
10766 |
</p> |
</p> |
10767 |
<a name="SUBSCRIBE MISCELLANEOUS"></a><br /><hr /> |
<a name="SUBSCRIBE DB_INSTRUMENTS_JOB_INFO"></a><br /><hr /> |
10768 |
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> |
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> |
10769 |
<a name="rfc.section.8.22"></a><h3>8.22. |
<a name="rfc.section.8.22"></a><h3>8.22. |
10770 |
|
Database job status information changed</h3> |
10771 |
|
|
10772 |
|
<p>Client may want to be notified when the status of particular database |
10773 |
|
instruments job is changed by issuing the following command: |
10774 |
|
</p> |
10775 |
|
<p> |
10776 |
|
</p> |
10777 |
|
<blockquote class="text"> |
10778 |
|
<p>SUBSCRIBE DB_INSTRUMENTS_JOB_INFO |
10779 |
|
</p> |
10780 |
|
</blockquote><p> |
10781 |
|
|
10782 |
|
</p> |
10783 |
|
<p>Server will start sending the following notification messages: |
10784 |
|
</p> |
10785 |
|
<p> |
10786 |
|
</p> |
10787 |
|
<blockquote class="text"> |
10788 |
|
<p>"NOTIFY:DB_INSTRUMENTS_JOB_INFO:<job-id>" |
10789 |
|
</p> |
10790 |
|
</blockquote><p> |
10791 |
|
|
10792 |
|
</p> |
10793 |
|
<p>where <job-id> will be replaced by the numerical ID of the job, |
10794 |
|
which status is changed. The front-end will have to send the respective |
10795 |
|
command to actually get the status info. Because these messages |
10796 |
|
will be triggered by LSCP commands issued by other clients rather than real |
10797 |
|
time events happening on the server, it is believed that an empty notification |
10798 |
|
message is sufficient here. |
10799 |
|
</p> |
10800 |
|
<a name="SUBSCRIBE MISCELLANEOUS"></a><br /><hr /> |
10801 |
|
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> |
10802 |
|
<a name="rfc.section.8.23"></a><h3>8.23. |
10803 |
Miscellaneous and debugging events</h3> |
Miscellaneous and debugging events</h3> |
10804 |
|
|
10805 |
<p>Client may want to be notified of miscellaneous and debugging events occurring at |
<p>Client may want to be notified of miscellaneous and debugging events occurring at |
10864 |
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> |
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> |
10865 |
<h3>11. References</h3> |
<h3>11. References</h3> |
10866 |
<table width="99%" border="0"> |
<table width="99%" border="0"> |
10867 |
|
<tr><td class="author-text" valign="top"><a name="RFC20">[RFC20]</a></td> |
10868 |
|
<td class="author-text">UCLA, “<a href="ftp://ftp.isi.edu/in-notes/rfc20.txt">ASCII format for Network Interchange</a>,” RFC 20, 1969.</td></tr> |
10869 |
<tr><td class="author-text" valign="top"><a name="RFC2119">[RFC2119]</a></td> |
<tr><td class="author-text" valign="top"><a name="RFC2119">[RFC2119]</a></td> |
10870 |
<td class="author-text">Bradner, S., “<a href="ftp://ftp.isi.edu/in-notes/rfc2119.txt">Key words for use in RFCs to Indicate Requirement Levels</a>,” RFC 2119, 1997.</td></tr> |
<td class="author-text">Bradner, S., “<a href="ftp://ftp.isi.edu/in-notes/rfc2119.txt">Key words for use in RFCs to Indicate Requirement Levels</a>,” RFC 2119, 1997.</td></tr> |
10871 |
<tr><td class="author-text" valign="top"><a name="RFC2234">[RFC2234]</a></td> |
<tr><td class="author-text" valign="top"><a name="RFC2234">[RFC2234]</a></td> |