--- web/trunk/www.linuxsampler.org/api/draft-linuxsampler-protocol.html	2007/10/07 14:07:48	1390
+++ web/trunk/www.linuxsampler.org/api/draft-linuxsampler-protocol.html	2008/12/10 22:10:17	1805
@@ -1,9 +1,9 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html lang="en"><head><title>LinuxSampler Control Protocol (draft)</title>
+<html lang="en"><head><title>LinuxSampler Control Protocol</title>
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<meta name="description" content="LinuxSampler Control Protocol (draft)">
+<meta name="description" content="LinuxSampler Control Protocol">
 <meta name="keywords" content="LSCP">
-<meta name="generator" content="xml2rfc v1.32 (http://xml.resource.org/)">
+<meta name="generator" content="xml2rfc v1.33 (http://xml.resource.org/)">
 <style type='text/css'><!--
         body {
                 font-family: verdana, charcoal, helvetica, arial, sans-serif;
@@ -145,9 +145,9 @@
 <tr><td class="header">LinuxSampler Developers</td><td class="header">C. Schoenebeck</td></tr>
 <tr><td class="header">Internet-Draft</td><td class="header">Interessengemeinschaft Software</td></tr>
 <tr><td class="header">Intended status: Standards Track</td><td class="header">Engineering e. V.</td></tr>
-<tr><td class="header">Expires: April 9, 2008</td><td class="header">October 7, 2007</td></tr>
+<tr><td class="header">Expires: June 13, 2009</td><td class="header">December 10, 2008</td></tr>
 </table></td></tr></table>
-<h1><br />LinuxSampler Control Protocol (draft)<br />LSCP 1.2cvs</h1>
+<h1><br />LinuxSampler Control Protocol<br />LSCP 1.4</h1>
 
 <h3>Status of this Memo</h3>
 <p>
@@ -173,11 +173,7 @@
 The list of Internet-Draft Shadow Directories can be accessed at
 <a href='http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html</a>.</p>
 <p>
-This Internet-Draft will expire on April 9, 2008.</p>
-
-<h3>Copyright Notice</h3>
-<p>
-Copyright &copy; The IETF Trust (2007).</p>
+This Internet-Draft will expire on June 13, 2009.</p>
 
 <h3>Abstract</h3>
 
@@ -336,7 +332,9 @@
 Altering effect send's MIDI controller<br />
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET FX_SEND LEVEL">6.4.33.</a>&nbsp;
 Altering effect send's send level<br />
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#RESET CHANNEL">6.4.34.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SEND CHANNEL MIDI_DATA">6.4.34.</a>&nbsp;
+Sending MIDI messages to sampler channel<br />
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#RESET CHANNEL">6.4.35.</a>&nbsp;
 Resetting a sampler channel<br />
 &nbsp;&nbsp;&nbsp;&nbsp;<a href="#anchor12">6.5.</a>&nbsp;
 Controlling connection<br />
@@ -354,14 +352,24 @@
 Current number of active voices<br />
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET TOTAL_VOICE_COUNT_MAX">6.6.2.</a>&nbsp;
 Maximum amount of active voices<br />
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#RESET">6.6.3.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET TOTAL_STREAM_COUNT">6.6.3.</a>&nbsp;
+Current number of active disk streams<br />
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#RESET">6.6.4.</a>&nbsp;
 Reset sampler<br />
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET SERVER INFO">6.6.4.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET SERVER INFO">6.6.5.</a>&nbsp;
 General sampler informations<br />
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET VOLUME">6.6.5.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET VOLUME">6.6.6.</a>&nbsp;
 Getting global volume attenuation<br />
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET VOLUME">6.6.6.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET VOLUME">6.6.7.</a>&nbsp;
 Setting global volume attenuation<br />
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET VOICES">6.6.8.</a>&nbsp;
+Getting global voice limit<br />
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET VOICES">6.6.9.</a>&nbsp;
+Setting global voice limit<br />
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET STREAMS">6.6.10.</a>&nbsp;
+Getting global disk stream limit<br />
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET STREAMS">6.6.11.</a>&nbsp;
+Setting global disk stream limit<br />
 &nbsp;&nbsp;&nbsp;&nbsp;<a href="#MIDI Instrument Mapping">6.7.</a>&nbsp;
 MIDI Instrument Mapping<br />
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#ADD MIDI_INSTRUMENT_MAP">6.7.1.</a>&nbsp;
@@ -434,10 +442,22 @@
 Getting job status information<br />
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#FORMAT INSTRUMENTS_DB">6.8.22.</a>&nbsp;
 Formatting the instruments database<br />
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#FIND LOST DB_INSTRUMENT_FILES">6.8.23.</a>&nbsp;
+Checking for lost instrument files<br />
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET DB_INSTRUMENT FILE_PATH">6.8.24.</a>&nbsp;
+Replacing an instrument file<br />
 &nbsp;&nbsp;&nbsp;&nbsp;<a href="#editing_instruments">6.9.</a>&nbsp;
 Editing Instruments<br />
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#EDIT INSTRUMENT">6.9.1.</a>&nbsp;
 Opening an appropriate instrument editor application<br />
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#file_management">6.10.</a>&nbsp;
+Managing Files<br />
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET FILE INSTRUMENTS">6.10.1.</a>&nbsp;
+Retrieving amount of instruments of a file<br />
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#LIST FILE INSTRUMENTS">6.10.2.</a>&nbsp;
+Retrieving all instruments of a file<br />
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET FILE INSTRUMENT INFO">6.10.3.</a>&nbsp;
+Retrieving informations about one instrument in a file<br />
 <a href="#command_syntax">7.</a>&nbsp;
 Command Syntax<br />
 &nbsp;&nbsp;&nbsp;&nbsp;<a href="#character_set">7.1.</a>&nbsp;
@@ -454,41 +474,47 @@
 MIDI input device's settings changed<br />
 &nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE CHANNEL_COUNT">8.5.</a>&nbsp;
 Number of sampler channels changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE VOICE_COUNT">8.6.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE CHANNEL_MIDI">8.6.</a>&nbsp;
+MIDI data on a sampler channel arrived<br />
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE DEVICE_MIDI">8.7.</a>&nbsp;
+MIDI data on a MIDI input device arrived<br />
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE VOICE_COUNT">8.8.</a>&nbsp;
 Number of active voices changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE STREAM_COUNT">8.7.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE STREAM_COUNT">8.9.</a>&nbsp;
 Number of active disk streams changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE BUFFER_FILL">8.8.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE BUFFER_FILL">8.10.</a>&nbsp;
 Disk stream buffer fill state changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE CHANNEL_INFO">8.9.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE CHANNEL_INFO">8.11.</a>&nbsp;
 Channel information changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE FX_SEND_COUNT">8.10.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE FX_SEND_COUNT">8.12.</a>&nbsp;
 Number of effect sends changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE FX_SEND_INFO">8.11.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE FX_SEND_INFO">8.13.</a>&nbsp;
 Effect send information changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE TOTAL_VOICE_COUNT">8.12.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE TOTAL_VOICE_COUNT">8.14.</a>&nbsp;
 Total number of active voices changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE MIDI_INSTRUMENT_MAP_COUNT">8.13.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE TOTAL_STREAM_COUNT">8.15.</a>&nbsp;
+Total number of active disk streams changed<br />
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE MIDI_INSTRUMENT_MAP_COUNT">8.16.</a>&nbsp;
 Number of MIDI instrument maps changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO">8.14.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO">8.17.</a>&nbsp;
 MIDI instrument map information changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE MIDI_INSTRUMENT_COUNT">8.15.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE MIDI_INSTRUMENT_COUNT">8.18.</a>&nbsp;
 Number of MIDI instruments changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE MIDI_INSTRUMENT_INFO">8.16.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE MIDI_INSTRUMENT_INFO">8.19.</a>&nbsp;
 MIDI instrument information changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE GLOBAL_INFO">8.17.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE GLOBAL_INFO">8.20.</a>&nbsp;
 Global settings changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE DB_INSTRUMENT_DIRECTORY_COUNT">8.18.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE DB_INSTRUMENT_DIRECTORY_COUNT">8.21.</a>&nbsp;
 Number of database instrument directories changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE DB_INSTRUMENT_DIRECTORY_INFO">8.19.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE DB_INSTRUMENT_DIRECTORY_INFO">8.22.</a>&nbsp;
 Database instrument directory information changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE DB_INSTRUMENT_COUNT">8.20.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE DB_INSTRUMENT_COUNT">8.23.</a>&nbsp;
 Number of database instruments changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE DB_INSTRUMENT_INFO">8.21.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE DB_INSTRUMENT_INFO">8.24.</a>&nbsp;
 Database instrument information changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE DB_INSTRUMENTS_JOB_INFO">8.22.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE DB_INSTRUMENTS_JOB_INFO">8.25.</a>&nbsp;
 Database job status information changed<br />
-&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE MISCELLANEOUS">8.23.</a>&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE MISCELLANEOUS">8.26.</a>&nbsp;
 Miscellaneous and debugging events<br />
 <a href="#anchor14">9.</a>&nbsp;
 Security Considerations<br />
@@ -3449,12 +3475,26 @@
 </blockquote><p>
                     
 </p>
-<p>Example:
+<p>Example (Unix):
 </p>
 <p>
                         </p>
 <blockquote class="text">
+<p>C: LOAD INSTRUMENT '/home/joe/gigs/cello.gig' 0 0
+</p>
+<p>S: OK
+</p>
+</blockquote><p>
+                    
+</p>
+<p>Example (Windows):
+</p>
 <p>
+                        </p>
+<blockquote class="text">
+<p>C: LOAD INSTRUMENT 'D:/MySounds/cello.gig' 0 0
+</p>
+<p>S: OK
 </p>
 </blockquote><p>
                     
@@ -3869,6 +3909,8 @@
                                         </p>
 <blockquote class="text">
 <p>arbitrary description text about the engine
+                                            (note that the character string may contain
+                                            <a class='info' href='#character_set'>escape sequences<span> (</span><span class='info'>Character Set and Escape Sequences</span><span>)</span></a>)
 </p>
 </blockquote>
                                     
@@ -3954,7 +3996,7 @@
 <blockquote class="text">
 <p>numerical ID of the audio output device which is
                                             currently connected to this sampler channel to output
-                                            the audio signal, "NONE" if there's no device
+                                            the audio signal, "-1" if there's no device
                                             connected to this sampler channel
 </p>
 </blockquote>
@@ -3988,7 +4030,8 @@
 <blockquote class="text">
 <p>the file name of the loaded instrument, "NONE" if
                                             there's no instrument yet loaded for this sampler
-                                            channel
+                                            channel (note: since LSCP 1.2 this path may contain
+                                            <a class='info' href='#character_set'>escape sequences<span> (</span><span class='info'>Character Set and Escape Sequences</span><span>)</span></a>)
 </p>
 </blockquote>
                                     
@@ -3996,7 +4039,9 @@
 <p>INSTRUMENT_NR -
                                         </p>
 <blockquote class="text">
-<p>the instrument index number of the loaded instrument
+<p>the instrument index number of the loaded instrument,
+                                            "-1" if there's no instrument loaded for this sampler
+                                            channel
 </p>
 </blockquote>
                                     
@@ -4005,6 +4050,8 @@
                                         </p>
 <blockquote class="text">
 <p>the instrument name of the loaded instrument
+                                            (note: since LSCP 1.2 this character string may contain
+                                            <a class='info' href='#character_set'>escape sequences<span> (</span><span class='info'>Character Set and Escape Sequences</span><span>)</span></a>)
 </p>
 </blockquote>
                                     
@@ -4012,8 +4059,11 @@
 <p>INSTRUMENT_STATUS -
                                         </p>
 <blockquote class="text">
-<p>integer values 0 to 100 indicating loading progress percentage for the instrument. Negative
-                                            value indicates a loading exception. Value of 100 indicates that the instrument is fully
+<p>Integer values 0 to 100 indicating loading progress
+                                            percentage for the instrument. Negative
+                                            value indicates a loading exception (also returns "-1" in case no
+                                            instrument was yet to be loaded on the sampler channel).
+                                            Value of 100 indicates that the instrument is fully
                                             loaded.
 </p>
 </blockquote>
@@ -4024,7 +4074,7 @@
 <blockquote class="text">
 <p>numerical ID of the MIDI input device which is
                                             currently connected to this sampler channel to deliver
-                                            MIDI input commands, "NONE" if there's no device
+                                            MIDI input commands, "-1" if there's no device
                                             connected to this sampler channel
 </p>
 </blockquote>
@@ -4033,7 +4083,9 @@
 <p>MIDI_INPUT_PORT -
                                         </p>
 <blockquote class="text">
-<p>port number of the MIDI input device
+<p>port number of the MIDI input device (in case a
+                                            MIDI device was already assigned to the sampler
+                                            channel)
 </p>
 </blockquote>
                                     
@@ -5351,6 +5403,8 @@
                                         </p>
 <blockquote class="text">
 <p>name of the effect send entity
+                                            (note that this character string may contain
+                                             <a class='info' href='#character_set'>escape sequences<span> (</span><span class='info'>Character Set and Escape Sequences</span><span>)</span></a>)
 </p>
 </blockquote>
                                     
@@ -5708,9 +5762,96 @@
 </blockquote><p>
                     
 </p>
-<a name="RESET CHANNEL"></a><br /><hr />
+<a name="SEND CHANNEL MIDI_DATA"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
 <a name="rfc.section.6.4.34"></a><h3>6.4.34.&nbsp;
+Sending MIDI messages to sampler channel</h3>
+
+<p>The front-end can send MIDI events to specific sampler channel
+                    by sending the following command:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>SEND CHANNEL MIDI_DATA &lt;midi-msg&gt; &lt;sampler-chan&gt; &lt;arg1&gt; &lt;arg2&gt;
+</p>
+</blockquote><p>
+                    
+</p>
+<p>Where &lt;sampler-chan&gt; is the sampler channel number
+                    as returned by the <a class='info' href='#ADD CHANNEL'>"ADD CHANNEL"<span> (</span><span class='info'>Adding a new sampler channel</span><span>)</span></a>
+                    or <a class='info' href='#LIST CHANNELS'>"LIST CHANNELS"<span> (</span><span class='info'>Getting all created sampler channel list</span><span>)</span></a> command,
+                    &lt;arg1&gt; and &lt;arg2&gt; arguments depend on the &lt;midi-msg&gt; argument, which
+                    specifies the MIDI message type. Currently, the following MIDI messages are supported:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>"NOTE_ON" -
+                                </p>
+<blockquote class="text">
+<p>For turning on MIDI notes, where &lt;arg1&gt;
+                                    specifies the key number and &lt;arg2&gt; the velocity
+                                    as described in the MIDI specification.
+</p>
+</blockquote>
+                            
+
+<p>"NOTE_OFF" -
+                                </p>
+<blockquote class="text">
+<p>For turning a currently playing MIDI note off, where &lt;arg1&gt;
+                                    specifies the key number and &lt;arg2&gt; the velocity
+                                    as described in the MIDI specification.
+</p>
+</blockquote>
+                            
+
+</blockquote><p>
+                    
+</p>
+<p>CAUTION: This command is provided for implementations of virtual MIDI keyboards
+                    and no realtime guarantee whatsoever will be made!
+</p>
+<p>Possible Answers:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>"OK" -
+                                </p>
+<blockquote class="text">
+<p>on success
+</p>
+</blockquote>
+                            
+
+<p>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
+                                </p>
+<blockquote class="text">
+<p>in case it failed, providing an appropriate error code and error message
+</p>
+</blockquote>
+                            
+
+</blockquote><p>
+                    
+</p>
+<p>Example:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>C: "SEND CHANNEL MIDI_DATA NOTE_ON 0 56 112"
+</p>
+<p>S: "OK"
+</p>
+</blockquote><p>
+                    
+</p>
+<a name="RESET CHANNEL"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.6.4.35"></a><h3>6.4.35.&nbsp;
 Resetting a sampler channel</h3>
 
 <p>The front-end can reset a particular sampler channel by sending the following command:
@@ -6045,9 +6186,36 @@
 </blockquote><p>
                     
 </p>
-<a name="RESET"></a><br /><hr />
+<a name="GET TOTAL_STREAM_COUNT"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
 <a name="rfc.section.6.6.3"></a><h3>6.6.3.&nbsp;
+Current number of active disk streams</h3>
+
+<p>The front-end can ask for the current number of active disk streams on
+                    the sampler by sending the following command:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>GET TOTAL_STREAM_COUNT
+</p>
+</blockquote><p>
+                    
+</p>
+<p>Possible Answers:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>LinuxSampler will answer by returning the number of all active
+                            disk streams on the sampler.
+</p>
+</blockquote><p>
+                    
+</p>
+<a name="RESET"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.6.6.4"></a><h3>6.6.4.&nbsp;
 Reset sampler</h3>
 
 <p>The front-end can reset the whole sampler by sending the following command:
@@ -6088,7 +6256,7 @@
 </p>
 <a name="GET SERVER INFO"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.6.6.4"></a><h3>6.6.4.&nbsp;
+<a name="rfc.section.6.6.5"></a><h3>6.6.5.&nbsp;
 General sampler informations</h3>
 
 <p>The client can ask for general informations about the LinuxSampler
@@ -6164,7 +6332,7 @@
 </p>
 <a name="GET VOLUME"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.6.6.5"></a><h3>6.6.5.&nbsp;
+<a name="rfc.section.6.6.6"></a><h3>6.6.6.&nbsp;
 Getting global volume attenuation</h3>
 
 <p>The client can ask for the current global sampler-wide volume
@@ -6197,7 +6365,7 @@
 </p>
 <a name="SET VOLUME"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.6.6.6"></a><h3>6.6.6.&nbsp;
+<a name="rfc.section.6.6.7"></a><h3>6.6.7.&nbsp;
 Setting global volume attenuation</h3>
 
 <p>The client can alter the current global sampler-wide volume
@@ -6250,6 +6418,198 @@
 </blockquote><p>
                     
 </p>
+<a name="GET VOICES"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.6.6.8"></a><h3>6.6.8.&nbsp;
+Getting global voice limit</h3>
+
+<p>The client can ask for the current global sampler-wide limit
+                       for maximum voices by sending the following command:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>GET VOICES
+</p>
+</blockquote><p>
+                    
+</p>
+<p>Possible Answers:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>LinuxSampler will answer by returning the number for
+                               the current limit of maximum voices.
+</p>
+</blockquote><p>
+                    
+</p>
+<p>The voice limit setting defines how many voices should maximum
+                       be processed by the sampler at the same time. If the user
+                       triggers new notes which would exceed that voice limit, the
+                       sampler engine will react by stealing old voices for those
+                       newly triggered notes. Note that the amount of voices triggered
+                       by a new note can be larger than one and is dependent to the
+                       respective instrument and probably further criterias.
+</p>
+<a name="SET VOICES"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.6.6.9"></a><h3>6.6.9.&nbsp;
+Setting global voice limit</h3>
+
+<p>The client can alter the current global sampler-wide limit
+                    for maximum voices by sending the following command:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>SET VOICES &lt;max-voices&gt;
+</p>
+</blockquote><p>
+                    
+</p>
+<p>Where &lt;max-voices&gt; should be replaced by the integer
+                   value, reflecting the new global amount limit of maximum voices.
+                   This value has to be larger than 0.
+</p>
+<p>Possible Answers:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>"OK" -
+                                </p>
+<blockquote class="text">
+<p>on success
+</p>
+</blockquote>
+                            
+
+<p>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
+                                </p>
+<blockquote class="text">
+<p>if the voice limit was set, but there are noteworthy
+                                    issue(s) related, providing an appropriate warning code and
+                                    warning message
+</p>
+</blockquote>
+                            
+
+<p>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
+                                </p>
+<blockquote class="text">
+<p>in case it failed, providing an appropriate error code and error message
+</p>
+</blockquote>
+                            
+
+</blockquote><p>
+                    
+</p>
+<p>Note: the given value will be passed to all sampler engine instances.
+                       The total amount of maximum voices on the running system might thus
+                       be as big as the given value multiplied by the current amount of engine
+                       instances.
+</p>
+<p>Caution: when adjusting the voice limit, you SHOULD also
+                        adjust the disk stream limit respectively and vice versa.
+</p>
+<a name="GET STREAMS"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.6.6.10"></a><h3>6.6.10.&nbsp;
+Getting global disk stream limit</h3>
+
+<p>The client can ask for the current global sampler-wide limit
+                       for maximum disk streams by sending the following command:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>GET STREAMS
+</p>
+</blockquote><p>
+                    
+</p>
+<p>Possible Answers:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>LinuxSampler will answer by returning the number for
+                               the current limit of maximum disk streams.
+</p>
+</blockquote><p>
+                    
+</p>
+<p>The disk stream limit setting defines how many disk streams should
+                       maximum be processed by a sampler engine at the same time. The
+                       higher this value, the more memory (RAM) will be occupied, since
+                       every disk streams allocates a certain buffer size for being able
+                       to perform its streaming operations.
+</p>
+<a name="SET STREAMS"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.6.6.11"></a><h3>6.6.11.&nbsp;
+Setting global disk stream limit</h3>
+
+<p>The client can alter the current global sampler-wide limit
+                    for maximum disk streams by sending the following command:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>SET STREAMS &lt;max-streams&gt;
+</p>
+</blockquote><p>
+                    
+</p>
+<p>Where &lt;max-streams&gt; should be replaced by the integer
+                   value, reflecting the new global amount limit of maximum disk streams.
+                   This value has to be positive.
+</p>
+<p>Possible Answers:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>"OK" -
+                                </p>
+<blockquote class="text">
+<p>on success
+</p>
+</blockquote>
+                            
+
+<p>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
+                                </p>
+<blockquote class="text">
+<p>if the disk stream limit was set, but there are noteworthy
+                                    issue(s) related, providing an appropriate warning code and
+                                    warning message
+</p>
+</blockquote>
+                            
+
+<p>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
+                                </p>
+<blockquote class="text">
+<p>in case it failed, providing an appropriate error code and error message
+</p>
+</blockquote>
+                            
+
+</blockquote><p>
+                    
+</p>
+<p>Note: the given value will be passed to all sampler engine instances.
+                       The total amount of maximum disk streams on the running system might
+                       thus be as big as the given value multiplied by the current amount of
+                       engine instances.
+</p>
+<p>Caution: when adjusting the disk stream limit, you SHOULD also
+                        adjust the voice limit respectively and vice versa.
+</p>
 <a name="MIDI Instrument Mapping"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
 <a name="rfc.section.6.7"></a><h3>6.7.&nbsp;
@@ -6563,6 +6923,8 @@
 <blockquote class="text">
 <p>custom name of the given map,
                                             which does not have to be unique
+                                            (note that this character string may contain
+                                             <a class='info' href='#character_set'>escape sequences<span> (</span><span class='info'>Character Set and Escape Sequences</span><span>)</span></a>)
 </p>
 </blockquote>
                                     
@@ -7111,6 +7473,8 @@
                                     changed with the
                                     <a class='info' href='#MAP MIDI_INSTRUMENT'>"MAP MIDI_INSTRUMENT"<span> (</span><span class='info'>Create or replace a MIDI instrument map entry</span><span>)</span></a>
                                     command and does not have to be unique.
+                                    (note that this character string may contain
+                                    <a class='info' href='#character_set'>escape sequences<span> (</span><span class='info'>Character Set and Escape Sequences</span><span>)</span></a>)
 </p>
 </blockquote>
                             
@@ -7127,7 +7491,9 @@
 <p>"INSTRUMENT_FILE" -
                                 </p>
 <blockquote class="text">
-<p>File name of the instrument.
+<p>File name of the instrument
+                                    (note that this path may contain
+                                    <a class='info' href='#character_set'>escape sequences<span> (</span><span class='info'>Character Set and Escape Sequences</span><span>)</span></a>).
 </p>
 </blockquote>
                             
@@ -7145,7 +7511,8 @@
 <blockquote class="text">
 <p>Name of the loaded instrument as reflected by its file.
                                     In contrast to the "NAME" field, the "INSTRUMENT_NAME" field
-                                    cannot be changed.
+                                    cannot be changed (note that this character string may contain
+                                    <a class='info' href='#character_set'>escape sequences<span> (</span><span class='info'>Character Set and Escape Sequences</span><span>)</span></a>).
 </p>
 </blockquote>
                             
@@ -7989,7 +8356,7 @@
 <p>
                         </p>
 <blockquote class="text">
-<p>ADD DB_INSTRUMENTS [NON_MODAL] [&lt;mode&gt;] &lt;db_dir&gt; &lt;file_path&gt; [&lt;instr_index&gt;]
+<p>ADD DB_INSTRUMENTS [NON_MODAL] [&lt;mode&gt;[ FILE_AS_DIR]] &lt;db_dir&gt; &lt;file_path&gt; [&lt;instr_index&gt;]
 </p>
 </blockquote><p>
                     
@@ -8047,6 +8414,11 @@
 </blockquote><p>
                     
 </p>
+<p> If FILE_AS_DIR argument is supplied, all instruments in an instrument
+		 file will be added to a separate directory in the instruments database, which
+		 name will be the name of the instrument file with the file extension stripped off.
+                 
+</p>
 <p>The difference between regular and NON_MODAL versions of the command
                     is that the regular command returns when the scanning is finished
                     while NON_MODAL version returns immediately and a background process is launched.
@@ -8651,7 +9023,7 @@
                     
 </p>
 <p>Where &lt;instr&gt; is the absolute path name of the instrument and
-                    &lt;desc&gt; is the new description for the instrument 
+                    &lt;desc&gt; is the new description for the instrument
                     (encapsulated into apostrophes, supporting escape sequences as described in chapter
                     "<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>").
 </p>
@@ -9033,6 +9405,108 @@
 </blockquote><p>
                     
 </p>
+<a name="FIND LOST DB_INSTRUMENT_FILES"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.6.8.23"></a><h3>6.8.23.&nbsp;
+Checking for lost instrument files</h3>
+
+<p>The front-end can retrieve the list of all instrument files in the instruments database
+                    that don't exist in the filesystem by sending the following command:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>FIND LOST DB_INSTRUMENT_FILES
+</p>
+</blockquote><p>
+                    
+</p>
+<p>Possible Answers:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>A comma separated list with the absolute path names
+                            (encapsulated into apostrophes) of all lost instrument files.
+</p>
+<p>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
+                                </p>
+<blockquote class="text">
+<p>in case it failed, providing an appropriate error code and error message.
+</p>
+</blockquote>
+                            
+
+</blockquote><p>
+                    
+</p>
+<p>Example:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>C: "FIND LOST DB_INSTRUMENT_FILES"
+</p>
+<p>S: "'/gigs/Bosendorfer 290.gig','/gigs/Steinway D.gig','/gigs/Free Piano.gig'"
+</p>
+</blockquote><p>
+                    
+</p>
+<a name="SET DB_INSTRUMENT FILE_PATH"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.6.8.24"></a><h3>6.8.24.&nbsp;
+Replacing an instrument file</h3>
+
+<p>The front-end can substitute all occurrences of an instrument file
+                    in the instruments database with a new one by sending the following command:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>SET DB_INSTRUMENT FILE_PATH &lt;old_path&gt; &lt;new_path&gt;
+</p>
+</blockquote><p>
+                    
+</p>
+<p>Where &lt;old_path&gt; is the absolute path name of the instrument file
+                    to substitute with &lt;new_path&gt;.
+</p>
+<p>Possible Answers:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>"OK" -
+                                </p>
+<blockquote class="text">
+<p>on success
+</p>
+</blockquote>
+                            
+
+<p>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
+                                </p>
+<blockquote class="text">
+<p>in case it failed, providing an appropriate error code and error message.
+</p>
+</blockquote>
+                            
+
+</blockquote><p>
+                    
+</p>
+<p>Example:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>C: "SET DB_INSTRUMENT FILE_PATH '/gigs/Bosendorfer 290.gig' '/gigs/pianos/Bosendorfer 290.gig'"
+</p>
+<p>S: "OK"
+</p>
+</blockquote><p>
+                    
+</p>
 <a name="editing_instruments"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
 <a name="rfc.section.6.9"></a><h3>6.9.&nbsp;
@@ -9060,7 +9534,7 @@
 <p>
                         </p>
 <blockquote class="text">
-<p>EDIT INSTRUMENT &lt;sampler-channel&gt;
+<p>EDIT CHANNEL INSTRUMENT &lt;sampler-channel&gt;
 </p>
 </blockquote><p>
                     
@@ -9127,13 +9601,285 @@
 <p>
                         </p>
 <blockquote class="text">
-<p>C: "EDIT INSTRUMENT 0"
+<p>C: "EDIT CHANNEL INSTRUMENT 0"
 </p>
 <p>S: "OK"
 </p>
 </blockquote><p>
                     
 </p>
+<a name="file_management"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.6.10"></a><h3>6.10.&nbsp;
+Managing Files</h3>
+
+<p>You can query detailed informations about files located
+                at the same system where the sampler instance is running on.
+                Using this command set allows to retrieve file informations
+                even remotely from another machine.
+</p>
+<a name="GET FILE INSTRUMENTS"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.6.10.1"></a><h3>6.10.1.&nbsp;
+Retrieving amount of instruments of a file</h3>
+
+<p>The front-end can retrieve the amount of instruments
+                    within a given instrument file by sending the
+                    following command:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>GET FILE INSTRUMENTS &lt;filename&gt;
+</p>
+</blockquote><p>
+                    
+</p>
+<p>Where &lt;filename&gt; is the name of the instrument
+                    file (encapsulated into apostrophes, supporting escape
+                    sequences as described in chapter
+                    "<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>").
+</p>
+<p>The sampler will try to ask all sampler engines,
+                    whether they support the given file and ask the first
+                    engine with a positive answer for the amount of
+                    instruments.
+</p>
+<p>Possible Answers:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>On success, the sampler will answer by
+                               returning the amount of instruments.
+                            
+</p>
+<p>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
+                                </p>
+<blockquote class="text">
+<p>if the file could not be handled
+</p>
+</blockquote>
+                            
+
+</blockquote><p>
+                    
+</p>
+<p>Examples:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>C: "GET FILE INSTRUMENTS 'D:/Sounds/Foo.gig'"
+</p>
+<p>S: "10"
+</p>
+</blockquote><p>
+                    
+</p>
+<a name="LIST FILE INSTRUMENTS"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.6.10.2"></a><h3>6.10.2.&nbsp;
+Retrieving all instruments of a file</h3>
+
+<p>The front-end can retrieve a list of all instruments
+                    within a given instrument file by sending the
+                    following command:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>LIST FILE INSTRUMENTS &lt;filename&gt;
+</p>
+</blockquote><p>
+                    
+</p>
+<p>Where &lt;filename&gt; is the name of the instrument
+                    file (encapsulated into apostrophes, supporting escape
+                    sequences as described in chapter
+                    "<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>").
+</p>
+<p>The sampler will try to ask all sampler engines,
+                    whether they support the given file and ask the first
+                    engine with a positive answer for a list of IDs for the
+                    instruments in the given file.
+</p>
+<p>Possible Answers:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>On success, the sampler will answer by
+                               returning a comma separated list of
+                               instrument IDs.
+                            
+</p>
+<p>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
+                                </p>
+<blockquote class="text">
+<p>if the file could not be handled
+</p>
+</blockquote>
+                            
+
+</blockquote><p>
+                    
+</p>
+<p>Examples:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>C: "LIST FILE INSTRUMENTS 'D:/Sounds/Foo.gig'"
+</p>
+<p>S: "0,1,2,3,4,5,6,7,8,9"
+</p>
+</blockquote><p>
+                    
+</p>
+<a name="GET FILE INSTRUMENT INFO"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.6.10.3"></a><h3>6.10.3.&nbsp;
+Retrieving informations about one instrument in a file</h3>
+
+<p>The front-end can retrieve detailed informations
+                    about a specific instrument within a given instrument
+                    file by sending the following command:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>GET FILE INSTRUMENT INFO &lt;filename&gt;
+                            &lt;instr-id&gt;
+</p>
+</blockquote><p>
+                    
+</p>
+<p>Where &lt;filename&gt; is the name of the instrument
+                    file (encapsulated into apostrophes, supporting escape
+                    sequences as described in chapter
+                    "<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>") and &lt;instr-id&gt; is the numeric
+                    instrument ID as returned by the
+                    <a class='info' href='#LIST FILE INSTRUMENTS'>"LIST FILE INSTRUMENTS"<span> (</span><span class='info'>Retrieving all instruments of a file</span><span>)</span></a> command.
+</p>
+<p>The sampler will try to ask all sampler engines,
+                    whether they support the given file and ask the first
+                    engine with a positive answer for informations about the
+                    specific instrument in the given file.
+</p>
+<p>Possible Answers:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>LinuxSampler will answer by sending a &lt;CRLF&gt; separated list.
+                            Each answer line begins with the settings category name
+                            followed by a colon and then a space character &lt;SP&gt; and finally
+                            the info character string to that setting category. At the
+                            moment the following categories are defined:
+</p>
+<p>
+                                </p>
+<blockquote class="text">
+<p>NAME -
+                                        </p>
+<blockquote class="text">
+<p>name of the instrument as
+                                            stored in the instrument file
+</p>
+</blockquote>
+                                    
+
+<p>FORMAT_FAMILY -
+                                        </p>
+<blockquote class="text">
+<p>name of the sampler format
+                                            of the given instrument
+</p>
+</blockquote>
+                                    
+
+<p>FORMAT_VERSION -
+                                        </p>
+<blockquote class="text">
+<p>version of the sampler format
+                                            the instrumen is stored as
+</p>
+</blockquote>
+                                    
+
+<p>PRODUCT -
+                                        </p>
+<blockquote class="text">
+<p>official product name of the
+                                            instrument as stored in the file
+                                            
+</p>
+</blockquote>
+                                    
+
+<p>ARTISTS -
+                                        </p>
+<blockquote class="text">
+<p>artists / sample library
+                                            vendor of the instrument
+</p>
+</blockquote>
+                                    
+
+<p>KEY_BINDINGS -
+                                        </p>
+<blockquote class="text">
+<p>comma separated list of integer values representing
+                                               the instrument's key mapping in the range between 0 .. 127,
+                                               reflecting the analog meaning of the MIDI specification.
+</p>
+</blockquote>
+                                    
+
+<p>KEYSWITCH_BINDINGS -
+                                        </p>
+<blockquote class="text">
+<p>comma separated list of integer values representing
+                                               the instrument's keyswitch mapping in the range between 0 .. 127,
+                                               reflecting the analog meaning of the MIDI specification.
+</p>
+</blockquote>
+                                    
+
+</blockquote>
+                            
+
+</blockquote><p>
+                    
+</p>
+<p>The mentioned fields above don't have to be in particular order.
+</p>
+<p>Example:
+</p>
+<p>
+                        </p>
+<blockquote class="text">
+<p>C: "GET FILE INSTRUMENT INFO 'D:/Sounds/Foo.gig' 0"
+</p>
+<p>S: "NAME: Lunatic Loops"
+</p>
+<p>&nbsp;&nbsp;&nbsp;"FORMAT_FAMILY: GIG"
+</p>
+<p>&nbsp;&nbsp;&nbsp;"FORMAT_VERSION: 3"
+</p>
+<p>&nbsp;&nbsp;&nbsp;"PRODUCT: The Backbone Bongo Beats"
+</p>
+<p>&nbsp;&nbsp;&nbsp;"ARTISTS: Jimmy the Fish"
+</p>
+<p>&nbsp;&nbsp;&nbsp;"."
+</p>
+</blockquote><p>
+                    
+</p>
 <a name="command_syntax"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
 <a name="rfc.section.7"></a><h3>7.&nbsp;
@@ -9255,6 +10001,9 @@
 <p>/ FORMAT SP format_instruction
 		
 </p>
+<p>/ SEND SP send_instruction
+		
+</p>
 <p>/ RESET
 		
 </p>
@@ -9276,9 +10025,15 @@
 <p>/ DB_INSTRUMENTS SP NON_MODAL SP scan_mode SP db_path SP filename
 		
 </p>
+<p>/ DB_INSTRUMENTS SP NON_MODAL SP scan_mode SP FILE_AS_DIR SP db_path SP filename
+		
+</p>
 <p>/ DB_INSTRUMENTS SP scan_mode SP db_path SP filename
 		
 </p>
+<p>/ DB_INSTRUMENTS SP scan_mode SP FILE_AS_DIR SP db_path SP filename
+		
+</p>
 <p>/ DB_INSTRUMENTS SP NON_MODAL SP db_path SP filename
 		
 </p>
@@ -9318,6 +10073,12 @@
 <p>/ CHANNEL_COUNT
 		
 </p>
+<p>/ CHANNEL_MIDI
+		
+</p>
+<p>/ DEVICE_MIDI
+		
+</p>
 <p>/ VOICE_COUNT
 		
 </p>
@@ -9366,6 +10127,9 @@
 <p>/ MISCELLANEOUS
 		
 </p>
+<p>/ TOTAL_STREAM_COUNT
+		
+</p>
 <p>/ TOTAL_VOICE_COUNT
 		
 </p>
@@ -9393,6 +10157,12 @@
 <p>/ CHANNEL_COUNT
 		
 </p>
+<p>/ CHANNEL_MIDI
+		
+</p>
+<p>/ DEVICE_MIDI
+		
+</p>
 <p>/ VOICE_COUNT
 		
 </p>
@@ -9441,6 +10211,9 @@
 <p>/ MISCELLANEOUS
 		
 </p>
+<p>/ TOTAL_STREAM_COUNT
+		
+</p>
 <p>/ TOTAL_VOICE_COUNT
 		
 </p>
@@ -9576,6 +10349,9 @@
 <p>/ SERVER SP INFO
 		
 </p>
+<p>/ TOTAL_STREAM_COUNT
+		
+</p>
 <p>/ TOTAL_VOICE_COUNT
 		
 </p>
@@ -9627,6 +10403,18 @@
 <p>/ VOLUME
 		
 </p>
+<p>/ VOICES
+		
+</p>
+<p>/ STREAMS
+		
+</p>
+<p>/ FILE SP INSTRUMENTS SP filename
+		
+</p>
+<p>/ FILE SP INSTRUMENT SP INFO SP filename SP instrument_index
+		
+</p>
 </blockquote><p>
 
 </p>
@@ -9678,12 +10466,21 @@
 <p>/ DB_INSTRUMENT SP DESCRIPTION SP db_path SP stringval_escaped
 		
 </p>
+<p>/ DB_INSTRUMENT SP FILE_PATH SP filename SP filename
+		
+</p>
 <p>/ ECHO SP boolean
 		
 </p>
 <p>/ VOLUME SP volume_value
 		
 </p>
+<p>/ VOICES SP number
+		
+</p>
+<p>/ STREAMS SP number
+		
+</p>
 </blockquote><p>
 
 </p>
@@ -9747,6 +10544,9 @@
 <p>/ DB_INSTRUMENT_DIRECTORIES SP db_path SP query_val_list
 		
 </p>
+<p>/ LOST SP DB_INSTRUMENT_FILES
+		
+</p>
 </blockquote><p>
 
 </p>
@@ -9852,7 +10652,7 @@
 <p>edit_instruction =
 	</p>
 <blockquote class="text">
-<p>INSTRUMENT SP sampler_channel
+<p>CHANNEL SP INSTRUMENT SP sampler_channel
 		
 </p>
 </blockquote><p>
@@ -9948,6 +10748,18 @@
 <p>/ DB_INSTRUMENTS SP db_path
 		
 </p>
+<p>/ FILE SP INSTRUMENTS SP filename
+		
+</p>
+</blockquote><p>
+
+</p>
+<p>send_instruction =
+	</p>
+<blockquote class="text">
+<p>CHANNEL SP MIDI_DATA SP string SP sampler_channel SP number SP number
+		
+</p>
 </blockquote><p>
 
 </p>
@@ -10299,6 +11111,7 @@
 <td align="left">two digit hex ASCII code of the character</td>
 </tr>
 </table>
+<br clear="all" />
 
 <p>Notice: due to the transition of certain parts of the
                 protocol which now support escape sequences, a slight backward
@@ -10309,13 +11122,18 @@
                 in the old versions a single backslash was sufficient.
 </p>
 <p>The following LSCP commands support escape sequences as part
-                of their filename / path based arguments:
+                of their filename / path based arguments and / or may contain
+                a filename / path with escape sequences in their response:
                 </p>
 <blockquote class="text">
 <p><a class='info' href='#LOAD INSTRUMENT'>"LOAD INSTRUMENT"<span> (</span><span class='info'>Loading an instrument</span><span>)</span></a>
 </p>
+<p><a class='info' href='#GET CHANNEL INFO'>"GET CHANNEL INFO"<span> (</span><span class='info'>Getting sampler channel information</span><span>)</span></a>
+</p>
 <p><a class='info' href='#MAP MIDI_INSTRUMENT'>"MAP MIDI_INSTRUMENT"<span> (</span><span class='info'>Create or replace a MIDI instrument map entry</span><span>)</span></a>
 </p>
+<p><a class='info' href='#GET MIDI_INSTRUMENT INFO'>"GET MIDI_INSTRUMENT INFO"<span> (</span><span class='info'>Get current settings of MIDI instrument map entry</span><span>)</span></a>
+</p>
 <p><a class='info' href='#ADD DB_INSTRUMENT_DIRECTORY'>"ADD DB_INSTRUMENT_DIRECTORY"<span> (</span><span class='info'>Creating a new instrument directory</span><span>)</span></a>
 </p>
 <p><a class='info' href='#ADD DB_INSTRUMENTS'>"ADD DB_INSTRUMENTS"<span> (</span><span class='info'>Adding instruments to the instruments database</span><span>)</span></a>
@@ -10356,6 +11174,16 @@
 </p>
 <p><a class='info' href='#COPY DB_INSTRUMENT_DIRECTORY'>"COPY DB_INSTRUMENT_DIRECTORY"<span> (</span><span class='info'>Copying instrument directories</span><span>)</span></a>
 </p>
+<p><a class='info' href='#FIND LOST DB_INSTRUMENT_FILES'>"FIND LOST DB_INSTRUMENT_FILES"<span> (</span><span class='info'>Checking for lost instrument files</span><span>)</span></a>
+</p>
+<p><a class='info' href='#SET DB_INSTRUMENT FILE_PATH'>"SET DB_INSTRUMENT FILE_PATH"<span> (</span><span class='info'>Replacing an instrument file</span><span>)</span></a>
+</p>
+<p><a class='info' href='#GET FILE INSTRUMENTS'>"GET FILE INSTRUMENTS"<span> (</span><span class='info'>Retrieving amount of instruments of a file</span><span>)</span></a>
+</p>
+<p><a class='info' href='#LIST FILE INSTRUMENTS'>"LIST FILE INSTRUMENTS"<span> (</span><span class='info'>Retrieving all instruments of a file</span><span>)</span></a>
+</p>
+<p><a class='info' href='#GET FILE INSTRUMENT INFO'>"GET FILE INSTRUMENT INFO"<span> (</span><span class='info'>Retrieving informations about one instrument in a file</span><span>)</span></a>
+</p>
 </blockquote><p>
                 Note that the forward slash character ('/') has a special meaning in
                 filename / path based arguments: it acts as separator of the nodes in
@@ -10366,26 +11194,59 @@
                 
 </p>
 <p>
+                Note for Windows: file path arguments in LSCP are expected
+                to use forward slashes as directory node separator similar
+                to Unix based operating systems. In contrast to Unix however
+                a Windows typical drive character is expected to be
+                prefixed to the path. That is an original Windows file path
+                like "D:\Sounds\My.gig" would become in LSCP:
+                "D:/Sounds/My.gig".
+                
+</p>
+<p>
                 The following LSCP commands even support escape sequences as
                 part of at least one of their text-based arguments (i.e. entity name,
-                description):
+                description) and / or may contain escape sequences in at least one of
+                their text-based fields in their response:
                 </p>
 <blockquote class="text">
+<p><a class='info' href='#GET SERVER INFO'>"GET SERVER INFO"<span> (</span><span class='info'>General sampler informations</span><span>)</span></a>
+</p>
+<p><a class='info' href='#GET ENGINE INFO'>"GET ENGINE INFO"<span> (</span><span class='info'>Getting information about an engine</span><span>)</span></a>
+</p>
+<p><a class='info' href='#GET CHANNEL INFO'>"GET CHANNEL INFO"<span> (</span><span class='info'>Getting sampler channel information</span><span>)</span></a>
+</p>
+<p><a class='info' href='#CREATE FX_SEND'>"CREATE FX_SEND"<span> (</span><span class='info'>Adding an effect send to a sampler channel</span><span>)</span></a>
+</p>
+<p><a class='info' href='#GET FX_SEND INFO'>"GET FX_SEND INFO"<span> (</span><span class='info'>Getting effect send information</span><span>)</span></a>
+</p>
+<p><a class='info' href='#SET FX_SEND NAME'>"SET FX_SEND NAME"<span> (</span><span class='info'>Changing effect send's name</span><span>)</span></a>
+</p>
+<p><a class='info' href='#GET MIDI_INSTRUMENT INFO'>"GET MIDI_INSTRUMENT INFO"<span> (</span><span class='info'>Get current settings of MIDI instrument map entry</span><span>)</span></a>
+</p>
+<p><a class='info' href='#GET MIDI_INSTRUMENT_MAP INFO'>"GET MIDI_INSTRUMENT_MAP INFO"<span> (</span><span class='info'>Getting MIDI instrument map information</span><span>)</span></a>
+</p>
 <p><a class='info' href='#ADD MIDI_INSTRUMENT_MAP'>"ADD MIDI_INSTRUMENT_MAP"<span> (</span><span class='info'>Create a new MIDI instrument map</span><span>)</span></a>
 </p>
 <p><a class='info' href='#MAP MIDI_INSTRUMENT'>"MAP MIDI_INSTRUMENT"<span> (</span><span class='info'>Create or replace a MIDI instrument map entry</span><span>)</span></a>
 </p>
 <p><a class='info' href='#SET MIDI_INSTRUMENT_MAP NAME'>"SET MIDI_INSTRUMENT_MAP NAME"<span> (</span><span class='info'>Renaming a MIDI instrument map</span><span>)</span></a>
 </p>
+<p><a class='info' href='#GET DB_INSTRUMENT_DIRECTORY INFO'>"GET DB_INSTRUMENT_DIRECTORY INFO"<span> (</span><span class='info'>Getting instrument directory information</span><span>)</span></a>
+</p>
 <p><a class='info' href='#SET DB_INSTRUMENT_DIRECTORY NAME'>"SET DB_INSTRUMENT_DIRECTORY NAME"<span> (</span><span class='info'>Renaming an instrument directory</span><span>)</span></a>
 </p>
 <p><a class='info' href='#SET DB_INSTRUMENT_DIRECTORY DESCRIPTION'>"SET DB_INSTRUMENT_DIRECTORY DESCRIPTION"<span> (</span><span class='info'>Changing the description of directory</span><span>)</span></a>
 </p>
+<p><a class='info' href='#FIND DB_INSTRUMENT_DIRECTORIES'>"FIND DB_INSTRUMENT_DIRECTORIES"<span> (</span><span class='info'>Finding directories</span><span>)</span></a>
+</p>
+<p><a class='info' href='#GET DB_INSTRUMENT INFO'>"GET DB_INSTRUMENT INFO"<span> (</span><span class='info'>Getting instrument information</span><span>)</span></a>
+</p>
 <p><a class='info' href='#SET DB_INSTRUMENT NAME'>"SET DB_INSTRUMENT NAME"<span> (</span><span class='info'>Renaming an instrument</span><span>)</span></a>
 </p>
 <p><a class='info' href='#SET DB_INSTRUMENT DESCRIPTION'>"SET DB_INSTRUMENT DESCRIPTION"<span> (</span><span class='info'>Changing the description of instrument</span><span>)</span></a>
 </p>
-<p><a class='info' href='#FIND DB_INSTRUMENT_DIRECTORIES'>"FIND DB_INSTRUMENT_DIRECTORIES"<span> (</span><span class='info'>Finding directories</span><span>)</span></a>
+<p><a class='info' href='#FIND DB_INSTRUMENTS'>"FIND DB_INSTRUMENTS"<span> (</span><span class='info'>Finding instruments</span><span>)</span></a>
 </p>
 </blockquote><p>
                 Please note that these lists are manually maintained. If you
@@ -10553,9 +11414,85 @@
 <p>where &lt;channels&gt; will be replaced by the new number
                 of sampler channels.
 </p>
-<a name="SUBSCRIBE VOICE_COUNT"></a><br /><hr />
+<a name="SUBSCRIBE CHANNEL_MIDI"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
 <a name="rfc.section.8.6"></a><h3>8.6.&nbsp;
+MIDI data on a sampler channel arrived</h3>
+
+<p>Client may want to be notified when MIDI data arrive on sampler channels on
+                back-end side, by issuing the following command:
+</p>
+<p>
+                    </p>
+<blockquote class="text">
+<p>SUBSCRIBE CHANNEL_MIDI
+</p>
+</blockquote><p>
+                
+</p>
+<p>Server will start sending one of the the following notification messages:
+</p>
+<p>
+                    </p>
+<blockquote class="text">
+<p>"NOTIFY:CHANNEL_MIDI:&lt;channel-id&gt; NOTE_ON  &lt;note&gt; &lt;velocity&gt;"
+</p>
+<p>"NOTIFY:CHANNEL_MIDI:&lt;channel-id&gt; NOTE_OFF &lt;note&gt; &lt;velocity&gt;"
+</p>
+</blockquote><p>
+                
+</p>
+<p>where &lt;channel-id&gt; will be replaced by the ID of the sampler channel where the MIDI
+                data arrived. &lt;note&gt; and &lt;velocity&gt; are integer values in the range between
+                0 .. 127, reflecting the analog meaning of the MIDI specification.
+                
+</p>
+<p>CAUTION: no guarantee whatsoever will be made that MIDI events are actually all
+                delivered by this mechanism! With other words: events could be lost at any time!
+                This restriction was made to keep the RT-safeness of the backend's MIDI and audio
+                thread unaffected by this feature.
+</p>
+<a name="SUBSCRIBE DEVICE_MIDI"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.8.7"></a><h3>8.7.&nbsp;
+MIDI data on a MIDI input device arrived</h3>
+
+<p>Client may want to be notified when MIDI data arrive on MIDI input devices by issuing the following command:
+</p>
+<p>
+			    </p>
+<blockquote class="text">
+<p>SUBSCRIBE DEVICE_MIDI
+</p>
+</blockquote><p>
+		    
+</p>
+<p>Server will start sending one of the the following notification messages:
+</p>
+<p>
+			    </p>
+<blockquote class="text">
+<p>"NOTIFY:DEVICE_MIDI:&lt;device-id&gt; &lt;port-id&gt; NOTE_ON &lt;note&gt; &lt;velocity&gt;"
+</p>
+<p>"NOTIFY:DEVICE_MIDI:&lt;device-id&gt; &lt;port-id&gt; NOTE_OFF &lt;note&gt; &lt;velocity&gt;"
+</p>
+</blockquote><p>
+		    
+</p>
+<p>where &lt;device-id&gt; &lt;port-id&gt; will be replaced
+		       by the IDs of the respective MIDI input device and the device's MIDI port where the MIDI
+		       data arrived. &lt;note&gt; and &lt;velocity&gt; are integer values in the range between
+		       0 .. 127, reflecting the analog meaning of the MIDI specification.
+		    
+</p>
+<p>CAUTION: no guarantee whatsoever will be made that MIDI events are actually all
+		       delivered by this mechanism! With other words: events could be lost at any time!
+		       This restriction was made to keep the RT-safeness of the backend's MIDI and audio
+		       thread unaffected by this feature.
+</p>
+<a name="SUBSCRIBE VOICE_COUNT"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.8.8"></a><h3>8.8.&nbsp;
 Number of active voices changed</h3>
 
 <p>Client may want to be notified when the number of voices on the
@@ -10585,7 +11522,7 @@
 </p>
 <a name="SUBSCRIBE STREAM_COUNT"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.7"></a><h3>8.7.&nbsp;
+<a name="rfc.section.8.9"></a><h3>8.9.&nbsp;
 Number of active disk streams changed</h3>
 
 <p>Client may want to be notified when the number of streams on the back-end
@@ -10615,7 +11552,7 @@
 </p>
 <a name="SUBSCRIBE BUFFER_FILL"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.8"></a><h3>8.8.&nbsp;
+<a name="rfc.section.8.10"></a><h3>8.10.&nbsp;
 Disk stream buffer fill state changed</h3>
 
 <p>Client may want to be notified when the buffer fill state of a disk stream
@@ -10646,7 +11583,7 @@
 </p>
 <a name="SUBSCRIBE CHANNEL_INFO"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.9"></a><h3>8.9.&nbsp;
+<a name="rfc.section.8.11"></a><h3>8.11.&nbsp;
 Channel information changed</h3>
 
 <p>Client may want to be notified when changes were made to sampler channels on the
@@ -10679,7 +11616,7 @@
 </p>
 <a name="SUBSCRIBE FX_SEND_COUNT"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.10"></a><h3>8.10.&nbsp;
+<a name="rfc.section.8.12"></a><h3>8.12.&nbsp;
 Number of effect sends changed</h3>
 
 <p>Client may want to be notified when the number of effect sends on
@@ -10709,7 +11646,7 @@
 </p>
 <a name="SUBSCRIBE FX_SEND_INFO"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.11"></a><h3>8.11.&nbsp;
+<a name="rfc.section.8.13"></a><h3>8.13.&nbsp;
 Effect send information changed</h3>
 
 <p>Client may want to be notified when changes were made to effect sends on a
@@ -10739,7 +11676,7 @@
 </p>
 <a name="SUBSCRIBE TOTAL_VOICE_COUNT"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.12"></a><h3>8.12.&nbsp;
+<a name="rfc.section.8.14"></a><h3>8.14.&nbsp;
 Total number of active voices changed</h3>
 
 <p>Client may want to be notified when the total number of voices on the
@@ -10766,9 +11703,38 @@
 <p>where &lt;voices&gt; will be replaced by the new number of
                 all currently active voices.
 </p>
+<a name="SUBSCRIBE TOTAL_STREAM_COUNT"></a><br /><hr />
+<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
+<a name="rfc.section.8.15"></a><h3>8.15.&nbsp;
+Total number of active disk streams changed</h3>
+
+<p>Client may want to be notified when the total number of disk streams on the
+                back-end changes by issuing the following command:
+</p>
+<p>
+                    </p>
+<blockquote class="text">
+<p>SUBSCRIBE TOTAL_STREAM_COUNT
+</p>
+</blockquote><p>
+                
+</p>
+<p>Server will start sending the following notification messages:
+</p>
+<p>
+                    </p>
+<blockquote class="text">
+<p>"NOTIFY:TOTAL_STREAM_COUNT:&lt;streams&gt;"
+</p>
+</blockquote><p>
+                
+</p>
+<p>where &lt;streams&gt; will be replaced by the new number of
+                all currently active disk streams.
+</p>
 <a name="SUBSCRIBE MIDI_INSTRUMENT_MAP_COUNT"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.13"></a><h3>8.13.&nbsp;
+<a name="rfc.section.8.16"></a><h3>8.16.&nbsp;
 Number of MIDI instrument maps changed</h3>
 
 <p>Client may want to be notified when the number of MIDI instrument maps on the
@@ -10797,7 +11763,7 @@
 </p>
 <a name="SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.14"></a><h3>8.14.&nbsp;
+<a name="rfc.section.8.17"></a><h3>8.17.&nbsp;
 MIDI instrument map information changed</h3>
 
 <p>Client may want to be notified when changes were made to MIDI instrument maps on the
@@ -10830,7 +11796,7 @@
 </p>
 <a name="SUBSCRIBE MIDI_INSTRUMENT_COUNT"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.15"></a><h3>8.15.&nbsp;
+<a name="rfc.section.8.18"></a><h3>8.18.&nbsp;
 Number of MIDI instruments changed</h3>
 
 <p>Client may want to be notified when the number of MIDI instrument maps on the
@@ -10860,7 +11826,7 @@
 </p>
 <a name="SUBSCRIBE MIDI_INSTRUMENT_INFO"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.16"></a><h3>8.16.&nbsp;
+<a name="rfc.section.8.19"></a><h3>8.19.&nbsp;
 MIDI instrument information changed</h3>
 
 <p>Client may want to be notified when changes were made to MIDI instruments on the
@@ -10894,7 +11860,7 @@
 </p>
 <a name="SUBSCRIBE GLOBAL_INFO"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.17"></a><h3>8.17.&nbsp;
+<a name="rfc.section.8.20"></a><h3>8.20.&nbsp;
 Global settings changed</h3>
 
 <p>Client may want to be notified when changes to the global settings
@@ -10919,11 +11885,27 @@
                         new global volume parameter.
 </p>
 </blockquote><p>
+                    </p>
+<blockquote class="text">
+<p>"NOTIFY:GLOBAL_INFO:VOICES &lt;max-voices&gt;" - Notifies that the
+                        golbal limit of the sampler for maximum voices is changed, where
+                        &lt;max-voices&gt; will be an integer value, reflecting the
+                        new global voice limit parameter.
+</p>
+</blockquote><p>
+                    </p>
+<blockquote class="text">
+<p>"NOTIFY:GLOBAL_INFO:STREAMS &lt;max-streams&gt;" - Notifies that the
+                        golbal limit of the sampler for maximum disk streams is changed, where
+                        &lt;max-streams&gt; will be an integer value, reflecting the
+                        new global disk streams limit parameter.
+</p>
+</blockquote><p>
                 
 </p>
 <a name="SUBSCRIBE DB_INSTRUMENT_DIRECTORY_COUNT"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.18"></a><h3>8.18.&nbsp;
+<a name="rfc.section.8.21"></a><h3>8.21.&nbsp;
 Number of database instrument directories changed</h3>
 
 <p>Client may want to be notified when the number of instrument
@@ -10957,7 +11939,7 @@
 </p>
 <a name="SUBSCRIBE DB_INSTRUMENT_DIRECTORY_INFO"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.19"></a><h3>8.19.&nbsp;
+<a name="rfc.section.8.22"></a><h3>8.22.&nbsp;
 Database instrument directory information changed</h3>
 
 <p>Client may want to be notified when changes were made to directories
@@ -11002,7 +11984,7 @@
 </p>
 <a name="SUBSCRIBE DB_INSTRUMENT_COUNT"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.20"></a><h3>8.20.&nbsp;
+<a name="rfc.section.8.23"></a><h3>8.23.&nbsp;
 Number of database instruments changed</h3>
 
 <p>Client may want to be notified when the number of instruments
@@ -11036,7 +12018,7 @@
 </p>
 <a name="SUBSCRIBE DB_INSTRUMENT_INFO"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.21"></a><h3>8.21.&nbsp;
+<a name="rfc.section.8.24"></a><h3>8.24.&nbsp;
 Database instrument information changed</h3>
 
 <p>Client may want to be notified when changes were made to instruments
@@ -11081,7 +12063,7 @@
 </p>
 <a name="SUBSCRIBE DB_INSTRUMENTS_JOB_INFO"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.22"></a><h3>8.22.&nbsp;
+<a name="rfc.section.8.25"></a><h3>8.25.&nbsp;
 Database job status information changed</h3>
 
 <p>Client may want to be notified when the status of particular database
@@ -11114,7 +12096,7 @@
 </p>
 <a name="SUBSCRIBE MISCELLANEOUS"></a><br /><hr />
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
-<a name="rfc.section.8.23"></a><h3>8.23.&nbsp;
+<a name="rfc.section.8.26"></a><h3>8.26.&nbsp;
 Miscellaneous and debugging events</h3>
 
 <p>Client may want to be notified of miscellaneous and debugging events occurring at
@@ -11180,13 +12162,13 @@
 <h3>11.&nbsp;References</h3>
 <table width="99%" border="0">
 <tr><td class="author-text" valign="top"><a name="RFC20">[RFC20]</a></td>
-<td class="author-text">UCLA, &ldquo;<a href="ftp://ftp.isi.edu/in-notes/rfc20.txt">ASCII format for Network Interchange</a>,&rdquo; RFC&nbsp;20, 1969.</td></tr>
+<td class="author-text">UCLA, &ldquo;<a href="http://tools.ietf.org/html/rfc20">ASCII format for Network Interchange</a>,&rdquo; RFC&nbsp;20, 1969.</td></tr>
 <tr><td class="author-text" valign="top"><a name="RFC2119">[RFC2119]</a></td>
-<td class="author-text">Bradner, S., &ldquo;<a href="ftp://ftp.isi.edu/in-notes/rfc2119.txt">Key words for use in RFCs to Indicate Requirement Levels</a>,&rdquo; RFC&nbsp;2119, 1997.</td></tr>
+<td class="author-text">Bradner, S., &ldquo;<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>,&rdquo; RFC&nbsp;2119, 1997.</td></tr>
 <tr><td class="author-text" valign="top"><a name="RFC2234">[RFC2234]</a></td>
-<td class="author-text">Crocker, D. and P. Overell, &ldquo;<a href="ftp://ftp.isi.edu/in-notes/rfc2234.txt">Augmented BNF for Syntax Specifications</a>,&rdquo; RFC&nbsp;2234, 1997.</td></tr>
+<td class="author-text">Crocker, D. and P. Overell, &ldquo;<a href="http://tools.ietf.org/html/rfc2234">Augmented BNF for Syntax Specifications</a>,&rdquo; RFC&nbsp;2234, 1997.</td></tr>
 <tr><td class="author-text" valign="top"><a name="RFC793">[RFC793]</a></td>
-<td class="author-text">Defense Advanced Research Projects Agency, &ldquo;<a href="ftp://ftp.isi.edu/in-notes/rfc793.txt">TRANSMISSION CONTROL PROTOCOL</a>,&rdquo; RFC&nbsp;793, 1981.</td></tr>
+<td class="author-text">Defense Advanced Research Projects Agency, &ldquo;<a href="http://tools.ietf.org/html/rfc793">TRANSMISSION CONTROL PROTOCOL</a>,&rdquo; RFC&nbsp;793, 1981.</td></tr>
 </table>
 
 <a name="rfc.authors"></a><br /><hr />
@@ -11211,7 +12193,7 @@
 <table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc">&nbsp;TOC&nbsp;</a></td></tr></table>
 <h3>Full Copyright Statement</h3>
 <p class='copyright'>
-Copyright &copy; The IETF Trust (2007).</p>
+Copyright &copy; The IETF Trust (2008).</p>
 <p class='copyright'>
 This document is subject to the rights,
 licenses and restrictions contained in BCP&nbsp;78,
@@ -11253,9 +12235,5 @@
 proprietary rights that may cover technology that may be required
 to implement this standard.
 Please address the information to the IETF at <a href='mailto:ietf-ipr@ietf.org'>ietf-ipr@ietf.org</a>.</p>
-<h3>Acknowledgment</h3>
-<p class='copyright'>
-Funding for the RFC Editor function is provided by
-the IETF Administrative Support Activity (IASA).</p>
 </body></html>
 
