/[svn]/web/trunk/www.linuxsampler.org/api/draft-linuxsampler-protocol.html

Diff of /web/trunk/www.linuxsampler.org/api/draft-linuxsampler-protocol.html

Parent Directory | Revision Log | View Patch Patch

-revision 1773 by iliev,
Wed Sep 10 15:14:31 2008 UTC
+revision 2498 by schoenebeck,
Thu Jan  9 22:05:21 2014 UTC
 Line 3
  <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  <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.35 (http://xml.resource.org/)">
  <style type='text/css'><!--
          body {
                  font-family: verdana, charcoal, helvetica, arial, sans-serif;
 Line 143
  <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>
  <table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
  <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">Internet-Draft</td><td class="header">LinuxSampler.org</td></tr>
- <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">January 9, 2014</td></tr>
- <tr><td class="header">Expires: March 14, 2009</td><td class="header">September 10, 2008</td></tr>
+ <tr><td class="header">Expires: July 13, 2014</td><td class="header">&nbsp;</td></tr>
  </table></td></tr></table>
- <h1><br />LinuxSampler Control Protocol<br />LSCP 1.4</h1>
+ <h1><br />LinuxSampler Control Protocol<br />LSCP 1.6</h1>
+ <h3>Abstract</h3>
+ <p>The LinuxSampler Control Protocol (LSCP) is an
+             application-level protocol primarily intended for local and
+             remote controlling the LinuxSampler backend application, which is a
+             sophisticated server-like console application essentially playing
+             back audio samples and manipulating the samples in real time to
+             certain extent.
+ </p>
  <h3>Status of this Memo</h3>
  <p>
  By submitting this Internet-Draft,
-Line 158 
 and any of which he or she becomes aware
+Line 167 
 and any of which he or she becomes aware
  in accordance with Section&nbsp;6 of BCP&nbsp;79.</p>
  <p>
  Internet-Drafts are working documents of the Internet Engineering
- Task Force (IETF), its areas, and its working groups.
+ Task Force (IETF).  Note that other groups may also distribute
- Note that other groups may also distribute working documents as
+ working documents as Internet-Drafts.  The list of current
- Internet-Drafts.</p>
+ Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.</p>
  <p>
  Internet-Drafts are draft documents valid for a maximum of six months
  and may be updated, replaced, or obsoleted by other documents at any time.
  It is inappropriate to use Internet-Drafts as reference material or to cite
  them other than as &ldquo;work in progress.&rdquo;</p>
  <p>
- The list of current Internet-Drafts can be accessed at
+ This Internet-Draft will expire on July 13, 2014.</p>
- <a href='http://www.ietf.org/ietf/1id-abstracts.txt'>http://www.ietf.org/ietf/1id-abstracts.txt</a>.</p>
+ <a name="toc"></a><br /><hr />
- <p>
- 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 March 14, 2009.</p>
- <h3>Copyright Notice</h3>
- <p>
- Copyright &copy; The IETF Trust (2008).</p>
- <h3>Abstract</h3>
- <p>The LinuxSampler Control Protocol (LSCP) is an
-             application-level protocol primarily intended for local and
-             remote controlling the LinuxSampler backend application, which is a
-             sophisticated server-like console application essentially playing
-             back audio samples and manipulating the samples in real time to
-             certain extent.
- </p><a name="toc"></a><br /><hr />
  <h3>Table of Contents</h3>
  <p class="toc">
  <a href="#anchor1">1.</a>&nbsp;
-Line 302 
 Setting audio output device<br />
+Line 292 
 Setting audio output device<br />
  Setting audio output type<br />
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL AUDIO_OUTPUT_CHANNEL">6.4.16.</a>&nbsp;
  Setting audio output channel<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL MIDI_INPUT_DEVICE">6.4.17.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#ADD CHANNEL MIDI_INPUT">6.4.17.</a>&nbsp;
+ Add MIDI input to sampler channel<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#REMOVE CHANNEL MIDI_INPUT">6.4.18.</a>&nbsp;
+ Remove MIDI input(s) from sampler channel<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#LIST CHANNEL MIDI_INPUTS">6.4.19.</a>&nbsp;
+ Getting all MIDI inputs of a sampler channel<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL MIDI_INPUT_DEVICE">6.4.20.</a>&nbsp;
  Setting MIDI input device<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL MIDI_INPUT_TYPE">6.4.18.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL MIDI_INPUT_TYPE">6.4.21.</a>&nbsp;
  Setting MIDI input type<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL MIDI_INPUT_PORT">6.4.19.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL MIDI_INPUT_PORT">6.4.22.</a>&nbsp;
  Setting MIDI input port<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL MIDI_INPUT_CHANNEL">6.4.20.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL MIDI_INPUT_CHANNEL">6.4.23.</a>&nbsp;
  Setting MIDI input channel<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL VOLUME">6.4.21.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL VOLUME">6.4.24.</a>&nbsp;
  Setting channel volume<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL MUTE">6.4.22.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL MUTE">6.4.25.</a>&nbsp;
  Muting a sampler channel<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL SOLO">6.4.23.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL SOLO">6.4.26.</a>&nbsp;
  Soloing a sampler channel<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL MIDI_INSTRUMENT_MAP">6.4.24.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET CHANNEL MIDI_INSTRUMENT_MAP">6.4.27.</a>&nbsp;
  Assigning a MIDI instrument map to a sampler channel<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#CREATE FX_SEND">6.4.25.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#CREATE FX_SEND">6.4.28.</a>&nbsp;
  Adding an effect send to a sampler channel<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#DESTROY FX_SEND">6.4.26.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#DESTROY FX_SEND">6.4.29.</a>&nbsp;
  Removing an effect send from a sampler channel<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET FX_SENDS">6.4.27.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET FX_SENDS">6.4.30.</a>&nbsp;
  Getting amount of effect sends on a sampler channel<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#LIST FX_SENDS">6.4.28.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#LIST FX_SENDS">6.4.31.</a>&nbsp;
  Listing all effect sends on a sampler channel<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET FX_SEND INFO">6.4.29.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET FX_SEND INFO">6.4.32.</a>&nbsp;
  Getting effect send information<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET FX_SEND NAME">6.4.30.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET FX_SEND NAME">6.4.33.</a>&nbsp;
  Changing effect send's name<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET FX_SEND AUDIO_OUTPUT_CHANNEL">6.4.31.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET FX_SEND AUDIO_OUTPUT_CHANNEL">6.4.34.</a>&nbsp;
  Altering effect send's audio routing<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET FX_SEND MIDI_CONTROLLER">6.4.32.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET FX_SEND EFFECT">6.4.35.</a>&nbsp;
+ Assigning destination effect to an effect send<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#REMOVE FX_SEND EFFECT">6.4.36.</a>&nbsp;
+ Removing destination effect from an effect send<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET FX_SEND MIDI_CONTROLLER">6.4.37.</a>&nbsp;
  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;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET FX_SEND LEVEL">6.4.38.</a>&nbsp;
  Altering effect send's send level<br />
- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SEND CHANNEL MIDI_DATA">6.4.34.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SEND CHANNEL MIDI_DATA">6.4.39.</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;
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#RESET CHANNEL">6.4.40.</a>&nbsp;
  Resetting a sampler channel<br />
  &nbsp;&nbsp;&nbsp;&nbsp;<a href="#anchor12">6.5.</a>&nbsp;
  Controlling connection<br />
 Line 366 
 General sampler informations<br />
  Getting global volume attenuation<br />
  &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;
-Line 383 
 Renaming a MIDI instrument map<br />
+Line 391 
 Renaming a MIDI instrument map<br />
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#MAP MIDI_INSTRUMENT">6.7.7.</a>&nbsp;
  Create or replace a MIDI instrument map entry<br />
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET MIDI_INSTRUMENTS">6.7.8.</a>&nbsp;
- Getting ammount of MIDI instrument map entries<br />
+ Getting amount of MIDI instrument map entries<br />
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#LIST MIDI_INSTRUMENTS">6.7.9.</a>&nbsp;
  Getting indeces of all entries of a MIDI instrument map<br />
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#UNMAP MIDI_INSTRUMENT">6.7.10.</a>&nbsp;
-Line 454 
 Retrieving amount of instruments of a fi
+Line 462 
 Retrieving amount of instruments of a fi
  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 />
+ &nbsp;&nbsp;&nbsp;&nbsp;<a href="#effects">6.11.</a>&nbsp;
+ Managing Effects<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET AVAILABLE_EFFECTS">6.11.1.</a>&nbsp;
+ Retrieve amount of available effects<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#LIST AVAILABLE_EFFECTS">6.11.2.</a>&nbsp;
+ Get list of available effects<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET EFFECT INFO">6.11.3.</a>&nbsp;
+ Retrieving general information about an effect<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#CREATE EFFECT_INSTANCE">6.11.4.</a>&nbsp;
+ Creating an instance of an effect by its portable ID<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#CREATE EFFECT_INSTANCE (non-portable)">6.11.5.</a>&nbsp;
+ Creating an instance of an effect by its numerical ID<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#DESTROY EFFECT_INSTANCE">6.11.6.</a>&nbsp;
+ Destroy an effect instance<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET EFFECT_INSTANCES">6.11.7.</a>&nbsp;
+ Retrieve amount of effect instances<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#LIST EFFECT_INSTANCES">6.11.8.</a>&nbsp;
+ Get list of effect instances<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET EFFECT_INSTANCE INFO">6.11.9.</a>&nbsp;
+ Retrieving current information about an effect instance<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET EFFECT_INSTANCE_INPUT_CONTROL INFO">6.11.10.</a>&nbsp;
+ Retrieving information about an effect parameter<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#SET EFFECT_INSTANCE_INPUT_CONTROL VALUE">6.11.11.</a>&nbsp;
+ Altering an effect parameter<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET SEND_EFFECT_CHAINS">6.11.12.</a>&nbsp;
+ Retrieve amount of send effect chains<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#LIST SEND_EFFECT_CHAINS">6.11.13.</a>&nbsp;
+ Retrieve list of send effect chains<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#ADD SEND_EFFECT_CHAIN">6.11.14.</a>&nbsp;
+ Add send effect chain<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#REMOVE SEND_EFFECT_CHAIN">6.11.15.</a>&nbsp;
+ Remove send effect chain<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#GET SEND_EFFECT_CHAIN INFO">6.11.16.</a>&nbsp;
+ Retrieving information about a send effect chain<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#APPEND SEND_EFFECT_CHAIN EFFECT">6.11.17.</a>&nbsp;
+ Append effect instance to a send effect chain<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#INSERT SEND_EFFECT_CHAIN EFFECT">6.11.18.</a>&nbsp;
+ Insert effect instance to a send effect chain<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="#REMOVE SEND_EFFECT_CHAIN EFFECT">6.11.19.</a>&nbsp;
+ Remove effect instance from send effect chain<br />
  <a href="#command_syntax">7.</a>&nbsp;
  Command Syntax<br />
  &nbsp;&nbsp;&nbsp;&nbsp;<a href="#character_set">7.1.</a>&nbsp;
-Line 510 
 Number of database instruments changed<b
+Line 558 
 Number of database instruments changed<b
  Database instrument information changed<br />
  &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.26.</a>&nbsp;
+ &nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE EFFECT_INSTANCE_COUNT">8.26.</a>&nbsp;
+ Number of effect instances changed<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE EFFECT_INSTANCE_INFO">8.27.</a>&nbsp;
+ Effect instance information changed<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE SEND_EFFECT_CHAIN_COUNT">8.28.</a>&nbsp;
+ Number of send effect chains changed<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE SEND_EFFECT_CHAIN_INFO">8.29.</a>&nbsp;
+ Send effect chain information changed<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;<a href="#SUBSCRIBE MISCELLANEOUS">8.30.</a>&nbsp;
  Miscellaneous and debugging events<br />
  <a href="#anchor14">9.</a>&nbsp;
  Security Considerations<br />
-Line 3863 
 Getting all available engines</h3>
+Line 3919 
 Getting all available engines</h3>
  <blockquote class="text">
  <p>C: "LIST AVAILABLE_ENGINES"
  </p>
- <p>S: "'GigEngine','AkaiEngine','DLSEngine','JoesCustomEngine'"
+ <p>S: "'gig','sfz','sf2'"
  </p>
  </blockquote><p>
-Line 3927 
 Getting information about an engine</h3>
+Line 3983 
 Getting information about an engine</h3>
  </p>
  <p>The mentioned fields above don't have to be in particular order.
  </p>
- <p>Example:
+ <p>Examples:
  </p>
  <p>
                          </p>
  <blockquote class="text">
- <p>C: "GET ENGINE INFO JoesCustomEngine"
+ <p>C: "GET ENGINE INFO gig"
+ </p>
+ <p>S: "DESCRIPTION: GigaSampler Format Engine"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"VERSION: 1.110"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"."
+ </p>
+ <p>C: "GET ENGINE INFO sf2"
  </p>
- <p>S: "DESCRIPTION: this is Joe's custom sampler engine"
+ <p>S: "DESCRIPTION: SoundFont Format Engine"
  </p>
- <p>&nbsp;&nbsp;&nbsp;"VERSION: testing-1.0"
+ <p>&nbsp;&nbsp;&nbsp;"VERSION: 1.4"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"."
+ </p>
+ <p>C: "GET ENGINE INFO sfz"
+ </p>
+ <p>S: "DESCRIPTION: SFZ Format Engine"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"VERSION: 1.11"
  </p>
  <p>&nbsp;&nbsp;&nbsp;"."
  </p>
-Line 3992 
 Getting sampler channel information</h3>
+Line 4064 
 Getting sampler channel information</h3>
  <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>
-Line 4035 
 Getting sampler channel information</h3>
+Line 4107 
 Getting sampler channel information</h3>
  <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>
-Line 4053 
 Getting sampler channel information</h3>
+Line 4127 
 Getting sampler channel information</h3>
  <p>INSTRUMENT_STATUS -
                                          </p>
  <blockquote class="text">
- <p>integer values 0 to 100 indicating loading progress percentage for the instrument. Negative
+ <p>Integer values 0 to 100 indicating loading progress
-                                             value indicates a loading exception. Value of 100 indicates that the instrument is fully
+                                             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>
-Line 4065 
 Getting sampler channel information</h3>
+Line 4142 
 Getting sampler channel information</h3>
  <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>
-Line 4074 
 Getting sampler channel information</h3>
+Line 4151 
 Getting sampler channel information</h3>
  <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>
-Line 4145 
 Getting sampler channel information</h3>
+Line 4224 
 Getting sampler channel information</h3>
  <blockquote class="text">
  <p>C: "GET CHANNEL INFO 34"
  </p>
- <p>S: "ENGINE_NAME: GigEngine"
+ <p>S: "ENGINE_NAME: gig"
  </p>
  <p>&nbsp;&nbsp;&nbsp;"VOLUME: 1.0"
  </p>
-Line 4417 
 Setting audio output device</h3>
+Line 4496 
 Setting audio output device</h3>
  <a name="rfc.section.6.4.15"></a><h3>6.4.15.&nbsp;
  Setting audio output type</h3>
- <p>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!
+ <p>DEPRECATED: THIS COMMAND WILL DISAPPEAR!
  </p>
  <p>The front-end can alter the audio output type on a specific sampler
                      channel by sending the following command:
-Line 4477 
 Setting audio output type</h3>
+Line 4556 
 Setting audio output type</h3>
  </blockquote><p>
  </p>
+ <p>Deprecated:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>Should not be used anymore. This command is currently only preserved for backward compatibility.
+ </p>
+ <p>This command is a relict from times where there was no sophisticated driver management yet. Use <a class='info' href='#CREATE AUDIO_OUTPUT_DEVICE'>"CREATE AUDIO_OUTPUT_DEVICE"<span> (</span><span class='info'>Creating an audio output device</span><span>)</span></a> and <a class='info' href='#SET CHANNEL AUDIO_OUTPUT_DEVICE'>"SET CHANNEL AUDIO_OUTPUT_DEVICE"<span> (</span><span class='info'>Setting audio output device</span><span>)</span></a> instead.
+ </p>
+ </blockquote><p>
+ </p>
  <a name="SET CHANNEL AUDIO_OUTPUT_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.16"></a><h3>6.4.16.&nbsp;
-Line 4544 
 Setting audio output channel</h3>
+Line 4635 
 Setting audio output channel</h3>
  </blockquote><p>
  </p>
- <a name="SET CHANNEL MIDI_INPUT_DEVICE"></a><br /><hr />
+ <a name="ADD CHANNEL MIDI_INPUT"></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.17"></a><h3>6.4.17.&nbsp;
+ Add MIDI input to sampler channel</h3>
+ <p>The front-end can add a MIDI input on a specific sampler
+                     channel by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>ADD CHANNEL MIDI_INPUT &lt;sampler-channel&gt; &lt;midi-device-id&gt; [&lt;midi-input-port&gt;]
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;sampler-channel&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
+                     and &lt;midi-device-id&gt; is the numerical ID of the MIDI input
+                     device as returned by the
+                     <a class='info' href='#CREATE MIDI_INPUT_DEVICE'>"CREATE MIDI_INPUT_DEVICE"<span> (</span><span class='info'>Creating a MIDI input device</span><span>)</span></a>
+                     or <a class='info' href='#LIST MIDI_INPUT_DEVICES'>"LIST MIDI_INPUT_DEVICES"<span> (</span><span class='info'>Getting all created MIDI input device list</span><span>)</span></a> command,
+                     and &lt;midi-input-port&gt; is an optional MIDI input port number of that
+                     MIDI input device. If &lt;midi-input-port&gt; is omitted,
+                     then the MIDI input device's first port (port number 0) is
+                     used.
+ </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 MIDI input port was connected, 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>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "ADD CHANNEL MIDI_INPUT 0 0"
+ </p>
+ <p>S: "OK"
+ </p>
+ <p>C: "ADD CHANNEL MIDI_INPUT 1 0"
+ </p>
+ <p>S: "OK"
+ </p>
+ <p>C: "ADD CHANNEL MIDI_INPUT 1 1 1"
+ </p>
+ <p>S: "OK"
+ </p>
+ <p>C: "ADD CHANNEL MIDI_INPUT 1 2 0"
+ </p>
+ <p>S: "OK"
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Since:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>Introduced with LSCP v1.6
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="REMOVE CHANNEL MIDI_INPUT"></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.18"></a><h3>6.4.18.&nbsp;
+ Remove MIDI input(s) from sampler channel</h3>
+ <p>The front-end can remove one ore more MIDI input(s) on a
+                     specific sampler channel by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>REMOVE CHANNEL MIDI_INPUT &lt;sampler-channel&gt; [&lt;midi-device-id&gt; [&lt;midi-input-port&gt;]]
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;sampler-channel&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
+                     and &lt;midi-device-id&gt; and &lt;midi-input-port&gt; are
+                     optional numerical IDs defining the MIDI input device and
+                     one of its MIDI ports as returned by the
+                     <a class='info' href='#LIST CHANNEL MIDI_INPUTS'>"LIST CHANNEL MIDI_INPUTS"<span> (</span><span class='info'>Getting all MIDI inputs of a sampler channel</span><span>)</span></a> command.
+ </p>
+ <p>
+                     If &lt;midi-input-port&gt; is omitted, then all MIDI input
+                     ports of &lt;midi-device-id&gt; are disconnected from this
+                     sampler channel.
+ </p>
+ <p>
+                     If both, &lt;midi-device-id&gt; and &lt;midi-input-port&gt;
+                     are omitted, then all MIDI input ports currently connected
+                     to this sampler channel are disconnected from this sampler
+                     channel.
+ </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 MIDI input porst were disconnected, 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>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "REMOVE CHANNEL MIDI_INPUT 0"
+ </p>
+ <p>S: "OK"
+ </p>
+ <p>C: "REMOVE CHANNEL MIDI_INPUT 1"
+ </p>
+ <p>S: "OK"
+ </p>
+ <p>C: "REMOVE CHANNEL MIDI_INPUT 1 2 0"
+ </p>
+ <p>S: "OK"
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Since:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>Introduced with LSCP v1.6
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="LIST CHANNEL MIDI_INPUTS"></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.19"></a><h3>6.4.19.&nbsp;
+ Getting all MIDI inputs of a sampler channel</h3>
+ <p>The front-end can query a list of all currently connected
+                     MIDI inputs of a certain sampler channel by sending the following
+                     command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>LIST CHANNEL MIDI_INPUTS &lt;sampler-channel&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;sampler-channel&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.
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>The sampler will answer by sending a comma separated
+                             list of MIDI input device ID - MIDI input port number pairs, where
+                             each pair is encapsulated into curly braces. The
+                             list is returned in one single line. The MIDI input
+                             device ID corresponds to the number returned by
+                             <a class='info' href='#LIST MIDI_INPUT_DEVICES'>"LIST MIDI_INPUT_DEVICES"<span> (</span><span class='info'>Getting all created MIDI input device list</span><span>)</span></a>
+                             and the port number is the index of the respective MIDI
+                             port of that MIDI input device.
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Example:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "LIST CHANNEL MIDI_INPUTS 0"
+ </p>
+ <p>S: "{0,0},{1,3},{2,0}"
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Since:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>Introduced with LSCP v1.6
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="SET CHANNEL MIDI_INPUT_DEVICE"></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.20"></a><h3>6.4.20.&nbsp;
  Setting MIDI input device</h3>
+ <p>DEPRECATED: THIS COMMAND WILL DISAPPEAR!
+ </p>
  <p>The front-end can set the MIDI input device on a specific sampler
                      channel by sending the following command:
  </p>
-Line 4567 
 Setting MIDI input device</h3>
+Line 4920 
 Setting MIDI input device</h3>
                      <a class='info' href='#CREATE MIDI_INPUT_DEVICE'>"CREATE MIDI_INPUT_DEVICE"<span> (</span><span class='info'>Creating a MIDI input device</span><span>)</span></a>
                      or <a class='info' href='#LIST MIDI_INPUT_DEVICES'>"LIST MIDI_INPUT_DEVICES"<span> (</span><span class='info'>Getting all created MIDI input device list</span><span>)</span></a> command.
  </p>
+ <p>
+                     If more than 1 MIDI inputs are currently connected to this
+                     sampler channel: Sending this command will disconnect ALL
+                     currently connected MIDI input ports connected to this
+                     sampler channel before establishing the new MIDI input
+                     connection. So this command does NOT add the connection,
+                     it replaces all existing ones instead. This behavior is due
+                     to preserving full behavior backward compatibility.
+ </p>
  <p>Possible Answers:
  </p>
  <p>
-Line 4611 
 Setting MIDI input device</h3>
+Line 4974 
 Setting MIDI input device</h3>
  </blockquote><p>
  </p>
+ <p>Deprecated:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>Should not be used anymore as of LSCP v1.6 and younger. This command is currently only preserved for backward compatibility.
+ </p>
+ <p>This command is a relict from times where only one MIDI input per sampler channel was allowed. Use <a class='info' href='#ADD CHANNEL MIDI_INPUT'>"ADD CHANNEL MIDI_INPUT"<span> (</span><span class='info'>Add MIDI input to sampler channel</span><span>)</span></a> and <a class='info' href='#REMOVE CHANNEL MIDI_INPUT'>"REMOVE CHANNEL MIDI_INPUT"<span> (</span><span class='info'>Remove MIDI input(s) from sampler channel</span><span>)</span></a> instead.
+ </p>
+ </blockquote><p>
+ </p>
  <a name="SET CHANNEL MIDI_INPUT_TYPE"></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.18"></a><h3>6.4.18.&nbsp;
+ <a name="rfc.section.6.4.21"></a><h3>6.4.21.&nbsp;
  Setting MIDI input type</h3>
- <p>DEPRECATED: THIS COMMAND WILL DISAPPEAR SOON!
+ <p>DEPRECATED: THIS COMMAND WILL DISAPPEAR!
  </p>
  <p>The front-end can alter the MIDI input type on a specific sampler
                      channel by sending the following command:
-Line 4632 
 Setting MIDI input type</h3>
+Line 5007 
 Setting MIDI input type</h3>
  <p>Where &lt;midi-input-type&gt; is currently only "ALSA" and
                      &lt;sampler-channel&gt; is the respective sampler channel number.
  </p>
+ <p>
+                     If more than 1 MIDI inputs are currently connected to this
+                     sampler channel: Sending this command will disconnect ALL
+                     currently connected MIDI input ports connected to this
+                     sampler channel before establishing the new MIDI input
+                     connection. So this command does NOT add the connection,
+                     it replaces all existing ones instead. This behavior is due
+                     to preserving full behavior backward compatibility.
+ </p>
  <p>Possible Answers:
  </p>
  <p>
-Line 4676 
 Setting MIDI input type</h3>
+Line 5061 
 Setting MIDI input type</h3>
  </blockquote><p>
  </p>
+ <p>Deprecated:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>Should not be used anymore. This command is currently only preserved for backward compatibility.
+ </p>
+ <p>This command is a relict from times where only 1 MIDI input per sampler channels was allowed and where no sophisticated driver management existed yet. Use <a class='info' href='#ADD CHANNEL MIDI_INPUT'>"ADD CHANNEL MIDI_INPUT"<span> (</span><span class='info'>Add MIDI input to sampler channel</span><span>)</span></a> and <a class='info' href='#REMOVE CHANNEL MIDI_INPUT'>"REMOVE CHANNEL MIDI_INPUT"<span> (</span><span class='info'>Remove MIDI input(s) from sampler channel</span><span>)</span></a> instead.
+ </p>
+ </blockquote><p>
+ </p>
  <a name="SET CHANNEL MIDI_INPUT_PORT"></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.19"></a><h3>6.4.19.&nbsp;
+ <a name="rfc.section.6.4.22"></a><h3>6.4.22.&nbsp;
  Setting MIDI input port</h3>
+ <p>DEPRECATED: THIS COMMAND WILL DISAPPEAR!
+ </p>
  <p>The front-end can alter the MIDI input port on a specific sampler
                      channel by sending the following command:
  </p>
-Line 4696 
 Setting MIDI input port</h3>
+Line 5095 
 Setting MIDI input port</h3>
                      MIDI input device connected to the sampler channel given by
                      &lt;sampler-channel&gt;.
  </p>
+ <p>
+                     If more than 1 MIDI inputs are currently connected to this
+                     sampler channel: Sending this command will switch the
+                     connection of the first (and only the first) MIDI input port
+                     currently being connected to this sampler channel, to
+                     another port of the same MIDI input device. Or in other
+                     words: the first MIDI input port currently connected to
+                     this sampler channel will be disconnected, and the requested
+                     other port of its MIDI input device will be connected to
+                     this sampler channel instead. This behavior is due
+                     to preserving full behavior backward compatibility.
+ </p>
  <p>Possible Answers:
  </p>
  <p>
-Line 4740 
 Setting MIDI input port</h3>
+Line 5152 
 Setting MIDI input port</h3>
  </blockquote><p>
  </p>
+ <p>Deprecated:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>Should not be used anymore. This command is currently only preserved for backward compatibility.
+ </p>
+ <p>This command is a relict from times where only one MIDI input per sampler channel was allowed. Use <a class='info' href='#ADD CHANNEL MIDI_INPUT'>"ADD CHANNEL MIDI_INPUT"<span> (</span><span class='info'>Add MIDI input to sampler channel</span><span>)</span></a> and <a class='info' href='#REMOVE CHANNEL MIDI_INPUT'>"REMOVE CHANNEL MIDI_INPUT"<span> (</span><span class='info'>Remove MIDI input(s) from sampler channel</span><span>)</span></a> instead.
+ </p>
+ </blockquote><p>
+ </p>
  <a name="SET CHANNEL MIDI_INPUT_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.20"></a><h3>6.4.20.&nbsp;
+ <a name="rfc.section.6.4.23"></a><h3>6.4.23.&nbsp;
  Setting MIDI input channel</h3>
  <p>The front-end can alter the MIDI channel a sampler channel should
-Line 4756 
 Setting MIDI input channel</h3>
+Line 5180 
 Setting MIDI input channel</h3>
  </blockquote><p>
  </p>
- <p>Where &lt;midi-input-chan&gt; is the number of the new MIDI input channel where
+ <p>Where &lt;midi-input-chan&gt; is the number
-                     &lt;sampler-channel&gt; should listen to or "ALL" to listen on all 16 MIDI
+                     of the new MIDI input channel (zero indexed!) where
+                     &lt;sampler-channel&gt; should listen to, or "ALL" to listen on all 16 MIDI
                      channels.
  </p>
  <p>Possible Answers:
-Line 4799 
 Setting MIDI input channel</h3>
+Line 5224 
 Setting MIDI input channel</h3>
  <p>
                          </p>
  <blockquote class="text">
- <p>
+ <p>C: "SET CHANNEL MIDI_INPUT_CHANNEL 0 0"
+ </p>
+ <p>S: "OK"
+ </p>
+ <p>C: "SET CHANNEL MIDI_INPUT_CHANNEL 1 ALL"
+ </p>
+ <p>S: "OK"
  </p>
  </blockquote><p>
  </p>
  <a name="SET CHANNEL 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.4.21"></a><h3>6.4.21.&nbsp;
+ <a name="rfc.section.6.4.24"></a><h3>6.4.24.&nbsp;
  Setting channel volume</h3>
  <p>The front-end can alter the volume of a sampler channel by sending
-Line 4871 
 Setting channel volume</h3>
+Line 5302 
 Setting channel volume</h3>
  </p>
  <a name="SET CHANNEL MUTE"></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.22"></a><h3>6.4.22.&nbsp;
+ <a name="rfc.section.6.4.25"></a><h3>6.4.25.&nbsp;
  Muting a sampler channel</h3>
  <p>The front-end can mute/unmute a specific sampler
-Line 4937 
 Muting a sampler channel</h3>
+Line 5368 
 Muting a sampler channel</h3>
  </p>
  <a name="SET CHANNEL SOLO"></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.23"></a><h3>6.4.23.&nbsp;
+ <a name="rfc.section.6.4.26"></a><h3>6.4.26.&nbsp;
  Soloing a sampler channel</h3>
  <p>The front-end can solo/unsolo a specific sampler channel
-Line 5003 
 Soloing a sampler channel</h3>
+Line 5434 
 Soloing a sampler channel</h3>
  </p>
  <a name="SET CHANNEL MIDI_INSTRUMENT_MAP"></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.24"></a><h3>6.4.24.&nbsp;
+ <a name="rfc.section.6.4.27"></a><h3>6.4.27.&nbsp;
  Assigning a MIDI instrument map to a sampler channel</h3>
  <p>The front-end can assign a MIDI instrument map to a specific sampler channel
-Line 5101 
 Assigning a MIDI instrument map to a sam
+Line 5532 
 Assigning a MIDI instrument map to a sam
  </p>
  <a name="CREATE FX_SEND"></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.25"></a><h3>6.4.25.&nbsp;
+ <a name="rfc.section.6.4.28"></a><h3>6.4.28.&nbsp;
  Adding an effect send to a sampler channel</h3>
  <p>The front-end can create an additional effect send on a specific sampler channel
-Line 5194 
 Adding an effect send to a sampler chann
+Line 5625 
 Adding an effect send to a sampler chann
  </p>
  <a name="DESTROY FX_SEND"></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.26"></a><h3>6.4.26.&nbsp;
+ <a name="rfc.section.6.4.29"></a><h3>6.4.29.&nbsp;
  Removing an effect send from a sampler channel</h3>
  <p>The front-end can remove an existing effect send on a specific sampler channel
-Line 5255 
 Removing an effect send from a sampler c
+Line 5686 
 Removing an effect send from a sampler c
  </p>
  <a name="GET FX_SENDS"></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.27"></a><h3>6.4.27.&nbsp;
+ <a name="rfc.section.6.4.30"></a><h3>6.4.30.&nbsp;
  Getting amount of effect sends on a sampler channel</h3>
  <p>The front-end can ask for the amount of effect sends on a specific sampler channel
-Line 5298 
 Getting amount of effect sends on a samp
+Line 5729 
 Getting amount of effect sends on a samp
  </p>
  <a name="LIST FX_SENDS"></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.28"></a><h3>6.4.28.&nbsp;
+ <a name="rfc.section.6.4.31"></a><h3>6.4.31.&nbsp;
  Listing all effect sends on a sampler channel</h3>
  <p>The front-end can ask for a list of effect sends on a specific sampler channel
-Line 5352 
 Listing all effect sends on a sampler ch
+Line 5783 
 Listing all effect sends on a sampler ch
  </p>
  <a name="GET 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.6.4.29"></a><h3>6.4.29.&nbsp;
+ <a name="rfc.section.6.4.32"></a><h3>6.4.32.&nbsp;
  Getting effect send information</h3>
  <p>The front-end can ask for the current settings of an effect send entity
-Line 5428 
 Getting effect send information</h3>
+Line 5859 
 Getting effect send information</h3>
                                              channel 1 is routed to the channel 3 of the audio
                                              output device (see
                                              <a class='info' href='#SET FX_SEND AUDIO_OUTPUT_CHANNEL'>"SET FX_SEND AUDIO_OUTPUT_CHANNEL"<span> (</span><span class='info'>Altering effect send's audio routing</span><span>)</span></a>
-                                             for details)
+                                             for details), if an internal send
+                                             effect is assigned to the effect
+                                             send, then this setting defines the
+                                             audio channel routing to that
+                                             effect instance respectively
+ </p>
+ </blockquote>
+ <p>EFFECT -
+                                         </p>
+ <blockquote class="text">
+ <p>destination send effect chain ID
+                                             and destination effect chain
+                                             position, separated by comma in the
+                                             form "&lt;effect-chain&gt;,&lt;chain-pos&gt;"
+                                             or "NONE" if there is no send effect
+                                             assigned to the effect send
  </p>
  </blockquote>
-Line 5456 
 Getting effect send information</h3>
+Line 5904 
 Getting effect send information</h3>
  </p>
  <p>&nbsp;&nbsp;&nbsp;"AUDIO_OUTPUT_ROUTING: 2,3"
  </p>
+ <p>&nbsp;&nbsp;&nbsp;"EFFECT: NONE"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"."
+ </p>
+ </blockquote><p>
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "GET FX_SEND INFO 0 1"
+ </p>
+ <p>S: "NAME: Delay Send (Internal)"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"MIDI_CONTROLLER: 93"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"LEVEL: 0.51"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"AUDIO_OUTPUT_ROUTING: 1,2"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"EFFECT: 2,0"
+ </p>
  <p>&nbsp;&nbsp;&nbsp;"."
  </p>
  </blockquote><p>
-Line 5463 
 Getting effect send information</h3>
+Line 5933 
 Getting effect send information</h3>
  </p>
  <a name="SET FX_SEND NAME"></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.30"></a><h3>6.4.30.&nbsp;
+ <a name="rfc.section.6.4.33"></a><h3>6.4.33.&nbsp;
  Changing effect send's name</h3>
  <p>The front-end can alter the current name of an effect
-Line 5527 
 Changing effect send's name</h3>
+Line 5997 
 Changing effect send's name</h3>
  </p>
  <a name="SET FX_SEND AUDIO_OUTPUT_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.31"></a><h3>6.4.31.&nbsp;
+ <a name="rfc.section.6.4.34"></a><h3>6.4.34.&nbsp;
  Altering effect send's audio routing</h3>
  <p>The front-end can alter the destination of an effect send's audio channel on a specific
-Line 5550 
 Altering effect send's audio routing</h3
+Line 6020 
 Altering effect send's audio routing</h3
                      &lt;audio-src&gt; is the numerical ID of the effect send's audio channel
                      which should be rerouted and &lt;audio-dst&gt; is the numerical ID of
                      the audio channel of the selected audio output device where &lt;audio-src&gt;
-                     should be routed to.
+                     should be routed to. If an internal send effect is assigned
+                     to the effect send, then this setting defines the audio
+                     channel routing to that effect instance respectively.
  </p>
  <p>Note that effect sends can only route audio to the same audio output
                      device as assigned to the effect send's sampler channel. Also note that an
-Line 5608 
 Altering effect send's audio routing</h3
+Line 6080 
 Altering effect send's audio routing</h3
  </blockquote><p>
  </p>
+ <a name="SET FX_SEND EFFECT"></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;
+ Assigning destination effect to an effect send</h3>
+ <p>The front-end can (re-)assign a destination effect to an
+                     effect send by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>SET FX_SEND EFFECT &lt;sampler-chan&gt; &lt;fx-send-id&gt; &lt;effect-chain&gt; &lt;chain-pos&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;fx-send-id&gt; reflects the numerical ID of the effect send entity
+                     as returned by the <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>
+                     or <a class='info' href='#LIST FX_SENDS'>"LIST FX_SENDS"<span> (</span><span class='info'>Listing all effect sends on a sampler channel</span><span>)</span></a> command,
+                     &lt;effect-chain&gt; by the numerical ID of the destination
+                     effect chain as returned by the
+                     <a class='info' href='#ADD SEND_EFFECT_CHAIN'>"ADD SEND_EFFECT_CHAIN"<span> (</span><span class='info'>Add send effect chain</span><span>)</span></a>
+                     or
+                     <a class='info' href='#LIST SEND_EFFECT_CHAINS'>"LIST SEND_EFFECT_CHAINS"<span> (</span><span class='info'>Retrieve list of send effect chains</span><span>)</span></a>
+                     command and &lt;chain-pos&gt; reflects the exact effect
+                     chain position in the effect chain which hosts the actual
+                     destination effect.
+ </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 FX_SEND EFFECT 0 0 2 5"
+ </p>
+ <p>S: "OK"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="REMOVE FX_SEND EFFECT"></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.36"></a><h3>6.4.36.&nbsp;
+ Removing destination effect from an effect send</h3>
+ <p>The front-end can (re-)assign a destination effect to an
+                     effect send by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>REMOVE FX_SEND EFFECT &lt;sampler-chan&gt; &lt;fx-send-id&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;fx-send-id&gt; reflects the numerical ID of the effect send entity
+                     as returned by the <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>
+                     or <a class='info' href='#LIST FX_SENDS'>"LIST FX_SENDS"<span> (</span><span class='info'>Listing all effect sends on a sampler channel</span><span>)</span></a> command.
+ </p>
+ <p>After the destination effect has been removed from the
+                     effect send, the audio signal of the effect send will be
+                     routed directly to the audio output device, according to the
+                     audio channel routing setting of the effect send.
+ </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: "REMOVE FX_SEND EFFECT 0 0"
+ </p>
+ <p>S: "OK"
+ </p>
+ </blockquote><p>
+ </p>
  <a name="SET FX_SEND MIDI_CONTROLLER"></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.32"></a><h3>6.4.32.&nbsp;
+ <a name="rfc.section.6.4.37"></a><h3>6.4.37.&nbsp;
  Altering effect send's MIDI controller</h3>
  <p>The front-end can alter the MIDI controller of an effect
-Line 5681 
 Altering effect send's MIDI controller</
+Line 6285 
 Altering effect send's MIDI controller</
  </p>
  <a name="SET FX_SEND LEVEL"></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.33"></a><h3>6.4.33.&nbsp;
+ <a name="rfc.section.6.4.38"></a><h3>6.4.38.&nbsp;
  Altering effect send's send level</h3>
  <p>The front-end can alter the current send level of an effect
-Line 5753 
 Altering effect send's send level</h3>
+Line 6357 
 Altering effect send's send level</h3>
  </p>
  <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;
+ <a name="rfc.section.6.4.39"></a><h3>6.4.39.&nbsp;
  Sending MIDI messages to sampler channel</h3>
- <p>The front-end can send MIDI events to specific sampler channel
+ <p>The front-end can send MIDI events to a specific sampler channel
                      by sending the following command:
  </p>
  <p>
-Line 5796 
 Sending MIDI messages to sampler channel
+Line 6400 
 Sending MIDI messages to sampler channel
  </blockquote>
+ <p>"CC" -
+                                 </p>
+ <blockquote class="text">
+ <p>For changing a MIDI controller, where &lt;arg1&gt;
+                                     specifies the controller number and &lt;arg2&gt; the
+                                     new value of the controller as described in the Control
+                                     Change section of the MIDI specification.
+ </p>
+ </blockquote>
  </blockquote><p>
  </p>
-Line 5840 
 Sending MIDI messages to sampler channel
+Line 6455 
 Sending MIDI messages to sampler channel
  </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;
+ <a name="rfc.section.6.4.40"></a><h3>6.4.40.&nbsp;
  Resetting a sampler channel</h3>
  <p>The front-end can reset a particular sampler channel by sending the following command:
-Line 6319 
 General sampler informations</h3>
+Line 6934 
 General sampler informations</h3>
  <p>The mentioned fields above don't have to be in particular order.
                      Other fields might be added in future.
  </p>
+ <p>Example:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "GET SERVER INFO"
+ </p>
+ <p>S: "DESCRIPTION: LinuxSampler - modular, streaming capable sampler"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"VERSION: 1.0.0.svn23"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"PROTOCOL_VERSION: 1.5"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"INSTRUMENTS_DB_SUPPORT: no"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"."
+ </p>
+ </blockquote><p>
+ </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.6"></a><h3>6.6.6.&nbsp;
-Line 6407 
 Setting global volume attenuation</h3>
+Line 7042 
 Setting global volume attenuation</h3>
  </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;
-Line 7043 
 Create or replace a MIDI instrument map
+Line 7870 
 Create or replace a MIDI instrument map
  <a name="GET MIDI_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.7.8"></a><h3>6.7.8.&nbsp;
- Getting ammount of MIDI instrument map entries</h3>
+ Getting amount of MIDI instrument map entries</h3>
  <p>The front-end can query the amount of currently existing
                      entries in a MIDI instrument map by sending the following
-Line 8153 
 Adding instruments to the instruments da
+Line 8980 
 Adding instruments to the instruments da
  <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>
-Line 8211 
 Adding instruments to the instruments da
+Line 9038 
 Adding instruments to the instruments da
  </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.
-Line 9672 
 Retrieving informations about one instru
+Line 10504 
 Retrieving informations about one instru
  </blockquote><p>
  </p>
+ <a name="effects"></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.11"></a><h3>6.11.&nbsp;
+ Managing Effects</h3>
+ <p>Audio effects (e.g. reverb, delay, compression) can be
+                 applied to the audio signals generated by the sampler. The
+                 sampler usually provides a set of internal audio effects for
+                 this task. The exact set of effects depends on the availability
+                 of third party effect plugins installed on the system where the
+                 sampler runs on.
+ </p>
+ <p>At the moment only "send effects" are supported. Support for
+                 "insert effects" and "master effects" is planned to be added at
+                 a later point.
+ </p>
+ <p>The following commands allow to retrieve the set of internal
+                 effects available to the sampler, detailed informations about
+                 those effects and to create and destroy instances of such
+                 effects. After an instance of an effect is created, the effect
+                 instance can be inserted into the audio signal path of the
+                 sampler, e.g. as send effect.
+ </p>
+ <p>The sampler allows to create an arbitrary amount of so called
+                 send effect chains. Each effect chain can host an arbitrary
+                 amount of effect instances. The output of the first effect
+                 instance in an effect chain is fed to the input of the second
+                 effect instance of the chain and so on. So effects in one chain
+                 are processed sequentially. Send effect chains however are
+                 processed in parallel to other send effect chains. Audio signals
+                 of sampler channels are fed to send effects by creating FX sends
+                 to the respective sampler channel and assigning a destination
+                 send effect to that FX by using the
+                 <a class='info' href='#SET FX_SEND EFFECT'>"SET FX_SEND EFFECT"<span> (</span><span class='info'>Assigning destination effect to an effect send</span><span>)</span></a>
+                 command. The latter allows to route the FX send to the beginning
+                 of a send effect chain, as well as directly to any other
+                 position of the send effect chain.
+ </p>
+ <a name="GET AVAILABLE_EFFECTS"></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.11.1"></a><h3>6.11.1.&nbsp;
+ Retrieve amount of available effects</h3>
+ <p>The front-end can retrieve the amount of internal
+                     effects, available to the sampler by sending
+                     the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>GET AVAILABLE_EFFECTS
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>The sampler will answer by returning the current
+                             number of effects available to the sampler.
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "GET AVAILABLE_EFFECTS"
+ </p>
+ <p>S: "129"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="LIST AVAILABLE_EFFECTS"></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.11.2"></a><h3>6.11.2.&nbsp;
+ Get list of available effects</h3>
+ <p>The set of available internal effects can change at
+                     runtime. The front-end can retrieve the list of internal
+                     effects, available to the sampler by sending the following
+                     command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>LIST AVAILABLE_EFFECTS
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>The sampler will answer by returning a comma
+                             separated list with numerical IDs of effects. Note:
+                             the numercial ID of an effect is generated by the
+                             sampler for the current moment. The numerical ID of
+                             the same effect can change at runtime, e.g. when the
+                             user requests a rescan of available effect plugins.
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Example:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "LIST AVAILABLE_EFFECTS"
+ </p>
+ <p>S: "5,6,7,120,121,122,123,124"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="GET EFFECT 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.11.3"></a><h3>6.11.3.&nbsp;
+ Retrieving general information about an effect</h3>
+ <p>The front-end can ask for general informations about an
+                     effect by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>GET EFFECT INFO &lt;effect-index&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;effect-index&gt; is the numerical ID of an
+                     effect as returned by the
+                     <a class='info' href='#LIST AVAILABLE_EFFECTS'>"LIST AVAILABLE_EFFECTS"<span> (</span><span class='info'>Get list of available effects</span><span>)</span></a>
+                     command.
+ </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 effect information
+                             category name, followed by a colon and then a space
+                             character &lt;SP&gt; and finally the info character
+                             string to that effect information category. At the
+                             moment the following categories are defined:
+ </p>
+ <p>
+                                 </p>
+ <blockquote class="text">
+ <p>SYSTEM -
+                                         </p>
+ <blockquote class="text">
+ <p>name of the effect plugin system
+                                             the effect is based on
+                                             (e.g. "LADSPA")
+ </p>
+ </blockquote>
+ <p>MODULE -
+                                         </p>
+ <blockquote class="text">
+ <p>module of the effect plugin
+                                             system that contains this effect,
+                                             the module is usually the
+                                             dynamic-linked library (DLL)
+                                             filename of the effect plugin,
+                                             including full path (note that this
+                                             filename 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>
+ <p>NAME -
+                                         </p>
+ <blockquote class="text">
+ <p>character string defining the
+                                             unique name of the effect within its
+                                             module (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>
+ <p>DESCRIPTION -
+                                         </p>
+ <blockquote class="text">
+ <p>human readable name of the
+                                             effect, intended to be displayed in
+                                             user interfaces (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>
+ </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 EFFECT INFO 121"
+ </p>
+ <p>S: "SYSTEM: LADSPA"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"MODULE: /usr/lib/ladspa/lowpass_iir_1891.so"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"NAME: lowpass_iir"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"DESCRIPTION: Glame Lowpass Filter"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"."
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="CREATE EFFECT_INSTANCE"></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.11.4"></a><h3>6.11.4.&nbsp;
+ Creating an instance of an effect by its portable ID</h3>
+ <p>The front-end can spawn an instance of the desired
+                     effect by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>CREATE EFFECT_INSTANCE &lt;effect-system&gt; &lt;module&gt; &lt;effect-name&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;effect-system&gt; is the "SYSTEM" field,
+                     &lt;module&gt; the "MODULE" field and &lt;effect-name&gt;
+                     the "NAME" field as returned by the
+                     <a class='info' href='#GET EFFECT INFO'>"GET EFFECT INFO"<span> (</span><span class='info'>Retrieving general information about an effect</span><span>)</span></a>
+                     command. The filename of argument &lt;module&gt; and the
+                     character string of argument &lt;effect-name&gt; 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>
+ <p>The sampler will try to load the requested effect and to
+                     create an instance of it. To allow loading the same effect
+                     on a different machine, probably even running a completely
+                     different operating system (e.g. Linux vs. Windows), the
+                     sampler tries to match &lt;module&gt; "softly". That means
+                     it first tries to find an effect that exactly matches the
+                     given &lt;module&gt; argument. If there is no exact match,
+                     the sampler will try to lower the restrictions on matching
+                     the &lt;module&gt; argument more and more, e.g. by ignoring
+                     upper / lower case differences and by ignoring the path of
+                     the DLL filename and file extension. If there is still no
+                     match at the end, the sampler will try to ignore the
+                     &lt;module&gt; argument completely and as a last resort
+                     search for an effect that only matches the given
+                     &lt;effect-system&gt; and &lt;effect-name&gt; arguments.
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>"OK[&lt;effect-instance&gt;]" -
+                                 </p>
+ <blockquote class="text">
+ <p>in case the effect instance was
+                                     successfully created, where
+                                     &lt;effect-instance&gt; is the numerical ID
+                                     of the new effect instance
+ </p>
+ </blockquote>
+ <p>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
+                                 </p>
+ <blockquote class="text">
+ <p>in case the effect instance was spawned
+                                     successfully, 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>if the effect could not be instantiated
+ </p>
+ </blockquote>
+ </blockquote><p>
+ </p>
+ <p>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "CREATE EFFECT_INSTANCE LADSPA '/usr/lib/ladspa/mod_delay_1419.so' 'modDelay'"
+ </p>
+ <p>S: "OK[0]"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="CREATE EFFECT_INSTANCE (non-portable)"></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.11.5"></a><h3>6.11.5.&nbsp;
+ Creating an instance of an effect by its numerical ID</h3>
+ <p>The front-end can spawn an instance of the desired
+                     effect by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>CREATE EFFECT_INSTANCE &lt;effect-index&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;effect-index&gt; is the numerical ID of the
+                     effect as returned by the
+                     <a class='info' href='#LIST AVAILABLE_EFFECTS'>"LIST AVAILABLE_EFFECTS"<span> (</span><span class='info'>Get list of available effects</span><span>)</span></a>
+                     command.
+ </p>
+ <p>The sampler will try to load the requested effect and to
+                     create an instance of it.
+ </p>
+ <p>Note: Since the numerical ID of a certain effect can
+                     change at any time, you should not use this command in
+                     LSCP files to restore a certain effect at a later time! To
+                     store a sampler session including all its effects, use the
+                     <a class='info' href='#CREATE EFFECT_INSTANCE'>portable text-based
+                     version of "CREATE EFFECT_INSTANCE"<span> (</span><span class='info'>Creating an instance of an effect by its portable ID</span><span>)</span></a> instead! This
+                     allows to restore a sampler session with all its effects
+                     also on other machines, possibly even running a completely
+                     different operating system (e.g. Linux vs. Windows), with
+                     different plugin directories or plugin DLL names.
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>"OK[&lt;effect-instance&gt;]" -
+                                 </p>
+ <blockquote class="text">
+ <p>in case the effect instance was
+                                     successfully created, where
+                                     &lt;effect-instance&gt; is the numerical ID
+                                     of the new effect instance
+ </p>
+ </blockquote>
+ <p>"WRN:&lt;warning-code&gt;:&lt;warning-message&gt;" -
+                                 </p>
+ <blockquote class="text">
+ <p>in case the effect instance was spawned
+                                     successfully, 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>if the effect could not be instantiated
+ </p>
+ </blockquote>
+ </blockquote><p>
+ </p>
+ <p>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "CREATE EFFECT_INSTANCE 72"
+ </p>
+ <p>S: "OK[5]"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="DESTROY EFFECT_INSTANCE"></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.11.6"></a><h3>6.11.6.&nbsp;
+ Destroy an effect instance</h3>
+ <p>The front-end can destroy an unusued effect instance and
+                     thus freeing it from memory by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>DESTROY EFFECT_INSTANCE &lt;effect-instance&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;effect-instance&gt; is the numerical ID of the
+                     effect instance as returned by the
+                     <a class='info' href='#CREATE EFFECT_INSTANCE'>"CREATE EFFECT_INSTANCE"<span> (</span><span class='info'>Creating an instance of an effect by its portable ID</span><span>)</span></a> or
+                     <a class='info' href='#LIST EFFECT_INSTANCES'>"LIST EFFECT_INSTANCES"<span> (</span><span class='info'>Get list of effect instances</span><span>)</span></a>
+                     command.
+ </p>
+ <p>The effect instance can only be destroyed if it's not
+                     used in any part of the sampler's audio signal path anymore.
+                     If the effect instance is still in use somewhere, trying to
+                     destroy the effect instance will result in an error
+                     message.
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>"OK" -
+                                 </p>
+ <blockquote class="text">
+ <p>in case the effect instance was successfully destroyed
+ </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>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "DESTROY EFFECT_INSTANCE 5"
+ </p>
+ <p>S: "OK"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="GET EFFECT_INSTANCES"></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.11.7"></a><h3>6.11.7.&nbsp;
+ Retrieve amount of effect instances</h3>
+ <p>The front-end can retrieve the current amount of effect
+                     instances by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>GET EFFECT_INSTANCES
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>The sampler will answer by returning the current
+                             number of effect instances created and not yet
+                             destroyed in the current sampler session.
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "GET EFFECT_INSTANCES"
+ </p>
+ <p>S: "14"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="LIST EFFECT_INSTANCES"></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.11.8"></a><h3>6.11.8.&nbsp;
+ Get list of effect instances</h3>
+ <p>The front-end can retrieve the current list of effect
+                     instances by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>LIST EFFECT_INSTANCES
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>The sampler will answer by returning a comma
+                             separated list with numerical IDs of effects
+                             instances.
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Example:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "LIST EFFECT_INSTANCES"
+ </p>
+ <p>S: "9,11,14,15,16,17,25"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="GET EFFECT_INSTANCE 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.11.9"></a><h3>6.11.9.&nbsp;
+ Retrieving current information about an effect instance</h3>
+ <p>The front-end can ask for the current informations about
+                     a particular effect instance by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>GET EFFECT_INSTANCE INFO &lt;effect-instance&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;effect-instance&gt; is the numerical ID of an
+                     effect instance as returned by the
+                     <a class='info' href='#CREATE EFFECT_INSTANCE'>"CREATE EFFECT_INSTANCE"<span> (</span><span class='info'>Creating an instance of an effect by its portable ID</span><span>)</span></a>
+                     or
+                     <a class='info' href='#LIST EFFECT_INSTANCES'>"LIST EFFECT_INSTANCES"<span> (</span><span class='info'>Get list of effect instances</span><span>)</span></a>
+                     command.
+ </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 information
+                             category name, followed by a colon and then a space
+                             character &lt;SP&gt; and finally the info character
+                             string to that information category. At the
+                             moment the following categories are defined:
+ </p>
+ <p>
+                                 </p>
+ <blockquote class="text">
+ <p>SYSTEM -
+                                         </p>
+ <blockquote class="text">
+ <p>name of the effect plugin system
+                                             the effect is based on
+                                             (e.g. "LADSPA")
+ </p>
+ </blockquote>
+ <p>MODULE -
+                                         </p>
+ <blockquote class="text">
+ <p>module of the effect plugin
+                                             system that contains this effect,
+                                             the module is usually the
+                                             dynamic-linked library (DLL)
+                                             filename of the effect plugin,
+                                             including full path (note that this
+                                             filename 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>
+ <p>NAME -
+                                         </p>
+ <blockquote class="text">
+ <p>character string defining the
+                                             unique name of the effect within its
+                                             module (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>
+ <p>DESCRIPTION -
+                                         </p>
+ <blockquote class="text">
+ <p>human readable name of the
+                                             effect, intended to be displayed in
+                                             user interfaces (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>
+ <p>INPUT_CONTROLS -
+                                         </p>
+ <blockquote class="text">
+ <p>amount of input controls the
+                                             effect instance provides, to allow
+                                             controlling the effect parameters in
+                                             realtime
+ </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 EFFECT_INSTANCE INFO 3"
+ </p>
+ <p>S: "SYSTEM: LADSPA"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"MODULE: /usr/lib/ladspa/mod_delay_1419.so"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"NAME: modDelay"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"DESCRIPTION: Modulatable delay"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"INPUT_CONTROLS: 1"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"."
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="GET EFFECT_INSTANCE_INPUT_CONTROL 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.11.10"></a><h3>6.11.10.&nbsp;
+ Retrieving information about an effect parameter</h3>
+ <p>Effects typically provide a certain set of effect
+                     parameters which can be altered by the user in realtime
+                     (e.g. depth of a reverb effect, duration of a delay effect,
+                     dry / wet signal ratio). Those controllable effect parameters
+                     are called "input controls". The front-end can ask for the
+                     current informations of an effect instance's input control
+                     by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>GET EFFECT_INSTANCE_INPUT_CONTROL INFO &lt;effect-instance&gt; &lt;input-control&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;effect-instance&gt; is the numerical ID of an
+                     effect instance as returned by the
+                     <a class='info' href='#CREATE EFFECT_INSTANCE'>"CREATE EFFECT_INSTANCE"<span> (</span><span class='info'>Creating an instance of an effect by its portable ID</span><span>)</span></a>
+                     or
+                     <a class='info' href='#LIST EFFECT_INSTANCES'>"LIST EFFECT_INSTANCES"<span> (</span><span class='info'>Get list of effect instances</span><span>)</span></a>
+                     command and &lt;input-control&gt; is the index of the input
+                     control within the numerical bounds as returned by the
+                     "INPUT_CONTROLS" field of the
+                     <a class='info' href='#GET EFFECT_INSTANCE INFO'>"GET EFFECT_INSTANCE INFO"<span> (</span><span class='info'>Retrieving current information about an effect instance</span><span>)</span></a>
+                     command.
+ </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 information
+                             category name, followed by a colon and then a space
+                             character &lt;SP&gt; and finally the info character
+                             string to that information category. There are
+                             information categories which are always returned,
+                             independent of the respective effect parameter and
+                             there are optional information categories
+                             which are only shown for certain effect parameters.
+                             At the moment the following categories are defined:
+ </p>
+ <p>
+                                 </p>
+ <blockquote class="text">
+ <p>DESCRIPTION -
+                                         </p>
+ <blockquote class="text">
+ <p>(always returned)
+                                             human readable name of the
+                                             effect parameter, intended to be
+                                             displayed in user interfaces (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>
+ <p>VALUE -
+                                         </p>
+ <blockquote class="text">
+ <p>
+                                             (always returned)
+                                             current (optional dotted)
+                                             floating point value of this effect
+                                             parameter
+ </p>
+ </blockquote>
+ <p>RANGE_MIN -
+                                         </p>
+ <blockquote class="text">
+ <p>
+                                             (optionally returned)
+                                             minimum allowed value for this
+                                             effect parameter
+ </p>
+ </blockquote>
+ <p>RANGE_MAX -
+                                         </p>
+ <blockquote class="text">
+ <p>
+                                             (optionally returned)
+                                             maximum allowed value for this
+                                             effect parameter
+ </p>
+ </blockquote>
+ <p>POSSIBILITIES -
+                                         </p>
+ <blockquote class="text">
+ <p>
+                                             (optionally returned)
+                                             comma separated list of
+                                             (optional dotted) floating point
+                                             numbers, reflecting the exact set of
+                                             possible values for this effect
+                                             parameter
+ </p>
+ </blockquote>
+ <p>DEFAULT -
+                                         </p>
+ <blockquote class="text">
+ <p>
+                                             (optionally returned)
+                                             default value of this effect
+                                             parameter
+ </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 EFFECT_INSTANCE_INPUT_CONTROL INFO 1 0"
+ </p>
+ <p>S: "DESCRIPTION: Base delay (s)"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"VALUE: 0.500"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"RANGE_MIN: 0.000"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"."
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="SET EFFECT_INSTANCE_INPUT_CONTROL VALUE"></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.11.11"></a><h3>6.11.11.&nbsp;
+ Altering an effect parameter</h3>
+ <p>The front-end can alter the current value of an effect
+                     parameter by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>SET EFFECT_INSTANCE_INPUT_CONTROL VALUE &lt;effect-instance&gt; &lt;input-control&gt; &lt;value&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;effect-instance&gt; is the numerical ID of the
+                     effect instance as returned by the
+                     <a class='info' href='#CREATE EFFECT_INSTANCE'>"CREATE EFFECT_INSTANCE"<span> (</span><span class='info'>Creating an instance of an effect by its portable ID</span><span>)</span></a> or
+                     <a class='info' href='#LIST EFFECT_INSTANCES'>"LIST EFFECT_INSTANCES"<span> (</span><span class='info'>Get list of effect instances</span><span>)</span></a>
+                     command, &lt;input-control&gt; is the index of the input
+                     control within the numerical bounds as returned by the
+                     "INPUT_CONTROLS" field of the
+                     <a class='info' href='#GET EFFECT_INSTANCE INFO'>"GET EFFECT_INSTANCE INFO"<span> (</span><span class='info'>Retrieving current information about an effect instance</span><span>)</span></a>
+                     command and &lt;value&gt; is the new (optional dotted)
+                     floating point value for this effect parameter.
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>"OK" -
+                                 </p>
+ <blockquote class="text">
+ <p>in case the effect was altered successfully
+ </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>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "SET EFFECT_INSTANCE_INPUT_CONTROL VALUE 0 1 0.5"
+ </p>
+ <p>S: "OK"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="GET SEND_EFFECT_CHAINS"></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.11.12"></a><h3>6.11.12.&nbsp;
+ Retrieve amount of send effect chains</h3>
+ <p>The front-end can retrieve the current amount of send
+                     effect chains of an audio output device by sending the
+                     following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>GET SEND_EFFECT_CHAINS &lt;audio-device&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;audio-device&gt; should be replaced by the
+                     numerical ID of the audio output device as given by the
+                     <a class='info' href='#CREATE AUDIO_OUTPUT_DEVICE'>"CREATE AUDIO_OUTPUT_DEVICE"<span> (</span><span class='info'>Creating an audio output device</span><span>)</span></a>
+                     or <a class='info' href='#LIST AUDIO_OUTPUT_DEVICES'>"LIST AUDIO_OUTPUT_DEVICES"<span> (</span><span class='info'>Getting all created audio output device list</span><span>)</span></a>
+                     command.
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>The sampler will answer by returning the current
+                             number of send effect chains of the supplied audio
+                             output device.
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "GET SEND_EFFECT_CHAINS 0"
+ </p>
+ <p>S: "4"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="LIST SEND_EFFECT_CHAINS"></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.11.13"></a><h3>6.11.13.&nbsp;
+ Retrieve list of send effect chains</h3>
+ <p>The front-end can retrieve the current list of send
+                     effect chains of an audio output device by sending the
+                     following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>LIST SEND_EFFECT_CHAINS &lt;audio-device&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;audio-device&gt; should be replaced by the
+                     numerical ID of the audio output device as given by the
+                     <a class='info' href='#CREATE AUDIO_OUTPUT_DEVICE'>"CREATE AUDIO_OUTPUT_DEVICE"<span> (</span><span class='info'>Creating an audio output device</span><span>)</span></a>
+                     or <a class='info' href='#LIST AUDIO_OUTPUT_DEVICES'>"LIST AUDIO_OUTPUT_DEVICES"<span> (</span><span class='info'>Getting all created audio output device list</span><span>)</span></a>
+                     command.
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>The sampler will answer by returning a comma
+                             separated list with numerical IDs of send effect
+                             chains of the supplied audio output device.
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "LIST SEND_EFFECT_CHAINS 0"
+ </p>
+ <p>S: "3,4,7"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="ADD SEND_EFFECT_CHAIN"></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.11.14"></a><h3>6.11.14.&nbsp;
+ Add send effect chain</h3>
+ <p>The front-end can add a send effect chain by sending the
+                     following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>ADD SEND_EFFECT_CHAIN &lt;audio-device&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;audio-device&gt; should be replaced by the
+                     numerical ID of the audio output device as given by the
+                     <a class='info' href='#CREATE AUDIO_OUTPUT_DEVICE'>"CREATE AUDIO_OUTPUT_DEVICE"<span> (</span><span class='info'>Creating an audio output device</span><span>)</span></a>
+                     or <a class='info' href='#LIST AUDIO_OUTPUT_DEVICES'>"LIST AUDIO_OUTPUT_DEVICES"<span> (</span><span class='info'>Getting all created audio output device list</span><span>)</span></a>
+                     command.
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>"OK[&lt;effect-chain&gt;]" -
+                                 </p>
+ <blockquote class="text">
+ <p>in case the send effect chain was
+                                     added successfully, where
+                                     &lt;effect-chain&gt; is the numerical ID
+                                     of the new send effect chain
+ </p>
+ </blockquote>
+ <p>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
+                                 </p>
+ <blockquote class="text">
+ <p>if the send effect chain could not be added
+ </p>
+ </blockquote>
+ </blockquote><p>
+ </p>
+ <p>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "ADD SEND_EFFECT_CHAIN 0"
+ </p>
+ <p>S: "OK[2]"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="REMOVE SEND_EFFECT_CHAIN"></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.11.15"></a><h3>6.11.15.&nbsp;
+ Remove send effect chain</h3>
+ <p>The front-end can remove a send effect chain by sending
+                     the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>REMOVE SEND_EFFECT_CHAIN &lt;audio-device&gt; &lt;effect-chain&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;audio-device&gt; should be replaced by the
+                     numerical ID of the audio output device as given by the
+                     <a class='info' href='#CREATE AUDIO_OUTPUT_DEVICE'>"CREATE AUDIO_OUTPUT_DEVICE"<span> (</span><span class='info'>Creating an audio output device</span><span>)</span></a>
+                     or <a class='info' href='#LIST AUDIO_OUTPUT_DEVICES'>"LIST AUDIO_OUTPUT_DEVICES"<span> (</span><span class='info'>Getting all created audio output device list</span><span>)</span></a>
+                     command and &lt;effect-chain&gt; by the numerical ID as
+                     returned by the
+                     <a class='info' href='#ADD SEND_EFFECT_CHAIN'>"ADD SEND_EFFECT_CHAIN"<span> (</span><span class='info'>Add send effect chain</span><span>)</span></a>
+                     or
+                     <a class='info' href='#LIST SEND_EFFECT_CHAINS'>"LIST SEND_EFFECT_CHAINS"<span> (</span><span class='info'>Retrieve list of send effect chains</span><span>)</span></a>
+                     command.
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>"OK" -
+                                 </p>
+ <blockquote class="text">
+ <p>in case the send effect chain was
+                                     removed successfully
+ </p>
+ </blockquote>
+ <p>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
+                                 </p>
+ <blockquote class="text">
+ <p>if the send effect chain could not be removed
+ </p>
+ </blockquote>
+ </blockquote><p>
+ </p>
+ <p>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "REMOVE SEND_EFFECT_CHAIN 0 2"
+ </p>
+ <p>S: "OK"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="GET SEND_EFFECT_CHAIN 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.11.16"></a><h3>6.11.16.&nbsp;
+ Retrieving information about a send effect chain</h3>
+ <p>The front-end can ask for informations of a send effect
+                     chain by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>GET SEND_EFFECT_CHAIN INFO &lt;audio-device&gt; &lt;effect-chain&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;audio-device&gt; should be replaced by the
+                     numerical ID of the audio output device as given by the
+                     <a class='info' href='#CREATE AUDIO_OUTPUT_DEVICE'>"CREATE AUDIO_OUTPUT_DEVICE"<span> (</span><span class='info'>Creating an audio output device</span><span>)</span></a>
+                     or <a class='info' href='#LIST AUDIO_OUTPUT_DEVICES'>"LIST AUDIO_OUTPUT_DEVICES"<span> (</span><span class='info'>Getting all created audio output device list</span><span>)</span></a>
+                     command and &lt;effect-chain&gt; by the numerical ID as
+                     returned by the
+                     <a class='info' href='#ADD SEND_EFFECT_CHAIN'>"ADD SEND_EFFECT_CHAIN"<span> (</span><span class='info'>Add send effect chain</span><span>)</span></a>
+                     or
+                     <a class='info' href='#LIST SEND_EFFECT_CHAINS'>"LIST SEND_EFFECT_CHAINS"<span> (</span><span class='info'>Retrieve list of send effect chains</span><span>)</span></a>
+                     command.
+ </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 information
+                             category name, followed by a colon and then a space
+                             character &lt;SP&gt; and finally the info character
+                             string to that information category.
+                             At the moment the following categories are defined:
+ </p>
+ <p>
+                                 </p>
+ <blockquote class="text">
+ <p>EFFECT_COUNT -
+                                         </p>
+ <blockquote class="text">
+ <p>amount of effects in this send
+                                             effect chain
+ </p>
+ </blockquote>
+ <p>EFFECT_SEQUENCE -
+                                         </p>
+ <blockquote class="text">
+ <p>comma separated list of the
+                                             numerical IDs of the effect
+                                             instances in this send effect chain,
+                                             in the order as they are procssed in
+                                             the effect chain
+ </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 SEND_EFFECT_CHAIN INFO 0 2"
+ </p>
+ <p>S: "EFFECT_COUNT: 3"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"EFFECT_SEQUENCE: 31,4,7"
+ </p>
+ <p>&nbsp;&nbsp;&nbsp;"."
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="APPEND SEND_EFFECT_CHAIN EFFECT"></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.11.17"></a><h3>6.11.17.&nbsp;
+ Append effect instance to a send effect chain</h3>
+ <p>The front-end can add an unused effect instance to the
+                     end of a send effect chain by sending the following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>APPEND SEND_EFFECT_CHAIN EFFECT &lt;audio-device&gt; &lt;effect-chain&gt; &lt;effect-instance&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;audio-device&gt; should be replaced by the
+                     numerical ID of the audio output device as given by the
+                     <a class='info' href='#CREATE AUDIO_OUTPUT_DEVICE'>"CREATE AUDIO_OUTPUT_DEVICE"<span> (</span><span class='info'>Creating an audio output device</span><span>)</span></a>
+                     or <a class='info' href='#LIST AUDIO_OUTPUT_DEVICES'>"LIST AUDIO_OUTPUT_DEVICES"<span> (</span><span class='info'>Getting all created audio output device list</span><span>)</span></a>
+                     command and &lt;effect-chain&gt; by the numerical ID as
+                     returned by the
+                     <a class='info' href='#ADD SEND_EFFECT_CHAIN'>"ADD SEND_EFFECT_CHAIN"<span> (</span><span class='info'>Add send effect chain</span><span>)</span></a>
+                     or
+                     <a class='info' href='#LIST SEND_EFFECT_CHAINS'>"LIST SEND_EFFECT_CHAINS"<span> (</span><span class='info'>Retrieve list of send effect chains</span><span>)</span></a>
+                     command and &lt;effect-instance&gt; as returned by the
+                     <a class='info' href='#CREATE EFFECT_INSTANCE'>"CREATE EFFECT_INSTANCE"<span> (</span><span class='info'>Creating an instance of an effect by its portable ID</span><span>)</span></a> or
+                     <a class='info' href='#LIST EFFECT_INSTANCES'>"LIST EFFECT_INSTANCES"<span> (</span><span class='info'>Get list of effect instances</span><span>)</span></a>
+                     command.
+ </p>
+ <p>Only unused effect instances can be added to the effect
+                     chain. Trying to add an effect instance which is already in
+                     use somewhere in the audio signal path of the sampler will
+                     result in an error.
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>"OK" -
+                                 </p>
+ <blockquote class="text">
+ <p>in case the effect instance was
+                                     added successfully to the chain
+ </p>
+ </blockquote>
+ <p>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
+                                 </p>
+ <blockquote class="text">
+ <p>if the effect instance could not be added
+ </p>
+ </blockquote>
+ </blockquote><p>
+ </p>
+ <p>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "APPEND SEND_EFFECT_CHAIN EFFECT 0 2 38"
+ </p>
+ <p>S: "OK"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="INSERT SEND_EFFECT_CHAIN EFFECT"></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.11.18"></a><h3>6.11.18.&nbsp;
+ Insert effect instance to a send effect chain</h3>
+ <p>The front-end can add an unused effect instance to a
+                     certain position of a send effect chain by sending the
+                     following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>INSERT SEND_EFFECT_CHAIN EFFECT &lt;audio-device&gt; &lt;effect-chain&gt; &lt;chain-pos&gt; &lt;effect-instance&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;audio-device&gt; should be replaced by the
+                     numerical ID of the audio output device as given by the
+                     <a class='info' href='#CREATE AUDIO_OUTPUT_DEVICE'>"CREATE AUDIO_OUTPUT_DEVICE"<span> (</span><span class='info'>Creating an audio output device</span><span>)</span></a>
+                     or <a class='info' href='#LIST AUDIO_OUTPUT_DEVICES'>"LIST AUDIO_OUTPUT_DEVICES"<span> (</span><span class='info'>Getting all created audio output device list</span><span>)</span></a>
+                     command, &lt;effect-chain&gt; by the numerical ID as
+                     returned by the
+                     <a class='info' href='#ADD SEND_EFFECT_CHAIN'>"ADD SEND_EFFECT_CHAIN"<span> (</span><span class='info'>Add send effect chain</span><span>)</span></a>
+                     or
+                     <a class='info' href='#LIST SEND_EFFECT_CHAINS'>"LIST SEND_EFFECT_CHAINS"<span> (</span><span class='info'>Retrieve list of send effect chains</span><span>)</span></a>
+                     command, &lt;effect-instance&gt; as returned by the
+                     <a class='info' href='#CREATE EFFECT_INSTANCE'>"CREATE EFFECT_INSTANCE"<span> (</span><span class='info'>Creating an instance of an effect by its portable ID</span><span>)</span></a> or
+                     <a class='info' href='#LIST EFFECT_INSTANCES'>"LIST EFFECT_INSTANCES"<span> (</span><span class='info'>Get list of effect instances</span><span>)</span></a>
+                     command and &lt;chain-pos&gt; the exact position of the
+                     effect chain where the supplied effect shall be inserted
+                     to.
+ </p>
+ <p>Only unused effect instances can be added to the effect
+                     chain. Trying to add an effect instance which is already in
+                     use somewhere in the audio signal path of the sampler will
+                     result in an error.
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>"OK" -
+                                 </p>
+ <blockquote class="text">
+ <p>in case the effect instance was
+                                     added successfully to the chain
+ </p>
+ </blockquote>
+ <p>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
+                                 </p>
+ <blockquote class="text">
+ <p>if the effect instance could not be added
+ </p>
+ </blockquote>
+ </blockquote><p>
+ </p>
+ <p>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "INSERT SEND_EFFECT_CHAIN EFFECT 0 2 4 38"
+ </p>
+ <p>S: "OK"
+ </p>
+ </blockquote><p>
+ </p>
+ <a name="REMOVE SEND_EFFECT_CHAIN EFFECT"></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.11.19"></a><h3>6.11.19.&nbsp;
+ Remove effect instance from send effect chain</h3>
+ <p>The front-end can remove an effect instance from a
+                     certain position of a send effect chain by sending the
+                     following command:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>REMOVE SEND_EFFECT_CHAIN EFFECT &lt;audio-device&gt; &lt;effect-chain&gt; &lt;chain-pos&gt;
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Where &lt;audio-device&gt; should be replaced by the
+                     numerical ID of the audio output device as given by the
+                     <a class='info' href='#CREATE AUDIO_OUTPUT_DEVICE'>"CREATE AUDIO_OUTPUT_DEVICE"<span> (</span><span class='info'>Creating an audio output device</span><span>)</span></a>
+                     or <a class='info' href='#LIST AUDIO_OUTPUT_DEVICES'>"LIST AUDIO_OUTPUT_DEVICES"<span> (</span><span class='info'>Getting all created audio output device list</span><span>)</span></a>
+                     command, &lt;effect-chain&gt; by the numerical ID as
+                     returned by the
+                     <a class='info' href='#ADD SEND_EFFECT_CHAIN'>"ADD SEND_EFFECT_CHAIN"<span> (</span><span class='info'>Add send effect chain</span><span>)</span></a>
+                     or
+                     <a class='info' href='#LIST SEND_EFFECT_CHAINS'>"LIST SEND_EFFECT_CHAINS"<span> (</span><span class='info'>Retrieve list of send effect chains</span><span>)</span></a>
+                     command and &lt;chain-pos&gt; the exact position of the
+                     effect instance to be removed from the effect chain.
+ </p>
+ <p>Possible Answers:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>"OK" -
+                                 </p>
+ <blockquote class="text">
+ <p>in case the effect instance was
+                                     removed successfully
+ </p>
+ </blockquote>
+ <p>"ERR:&lt;error-code&gt;:&lt;error-message&gt;" -
+                                 </p>
+ <blockquote class="text">
+ <p>if the effect instance could not be removed
+ </p>
+ </blockquote>
+ </blockquote><p>
+ </p>
+ <p>Examples:
+ </p>
+ <p>
+                         </p>
+ <blockquote class="text">
+ <p>C: "REMOVE SEND_EFFECT_CHAIN EFFECT 0 2 4"
+ </p>
+ <p>S: "OK"
+ </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;
-Line 9791 
 Command Syntax</h3>
+Line 12042 
 Command Syntax</h3>
  </p>
  <p>/ FORMAT SP format_instruction
+ </p>
+ <p>/ SEND SP send_instruction
+ </p>
+ <p>/ APPEND SP append_instruction
  </p>
- <p>SEND SP send_instruction
+ <p>/ INSERT SP insert_instruction
  </p>
  <p>/ RESET
-Line 9811 
 Command Syntax</h3>
+Line 12068 
 Command Syntax</h3>
  <p>CHANNEL
  </p>
+ <p>/ CHANNEL SP MIDI_INPUT SP sampler_channel SP device_index
+ </p>
+ <p>/ CHANNEL SP MIDI_INPUT SP sampler_channel SP device_index SP midi_input_port_index
+ </p>
  <p>/ DB_INSTRUMENT_DIRECTORY SP db_path
  </p>
  <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>
-Line 9838 
 Command Syntax</h3>
+Line 12107 
 Command Syntax</h3>
  <p>/ MIDI_INSTRUMENT_MAP SP map_name
  </p>
+ <p>/ SEND_EFFECT_CHAIN SP device_index
+ </p>
  </blockquote><p>
  </p>
-Line 9922 
 Command Syntax</h3>
+Line 12194 
 Command Syntax</h3>
  <p>/ GLOBAL_INFO
  </p>
+ <p>/ EFFECT_INSTANCE_COUNT
+ </p>
+ <p>/ EFFECT_INSTANCE_INFO
+ </p>
+ <p>/ SEND_EFFECT_CHAIN_COUNT
+ </p>
+ <p>/ SEND_EFFECT_CHAIN_INFO
+ </p>
  </blockquote><p>
  </p>
-Line 10006 
 Command Syntax</h3>
+Line 12290 
 Command Syntax</h3>
  <p>/ GLOBAL_INFO
  </p>
+ <p>/ EFFECT_INSTANCE_COUNT
+ </p>
+ <p>/ EFFECT_INSTANCE_INFO
+ </p>
+ <p>/ SEND_EFFECT_CHAIN_COUNT
+ </p>
+ <p>/ SEND_EFFECT_CHAIN_INFO
+ </p>
  </blockquote><p>
  </p>
-Line 10042 
 Command Syntax</h3>
+Line 12338 
 Command Syntax</h3>
  <p>CHANNEL SP sampler_channel
  </p>
+ <p>/ CHANNEL SP MIDI_INPUT SP sampler_channel
+ </p>
+ <p>/ CHANNEL SP MIDI_INPUT SP sampler_channel SP device_index
+ </p>
+ <p>/ CHANNEL SP MIDI_INPUT SP sampler_channel SP device_index SP midi_input_port_index
+ </p>
  <p>/ MIDI_INSTRUMENT_MAP SP midi_map
  </p>
  <p>/ MIDI_INSTRUMENT_MAP SP ALL
  </p>
+ <p>/ SEND_EFFECT_CHAIN SP device_index SP effect_chain
+ </p>
+ <p>/ SEND_EFFECT_CHAIN SP EFFECT SP device_index SP effect_chain SP chain_pos
+ </p>
+ <p>/ FX_SEND SP EFFECT SP sampler_channel SP fx_send_id
+ </p>
  <p>/ DB_INSTRUMENT_DIRECTORY SP FORCE SP db_path
  </p>
-Line 10066 
 Command Syntax</h3>
+Line 12380 
 Command Syntax</h3>
  <p>AVAILABLE_ENGINES
  </p>
+ <p>/ AVAILABLE_EFFECTS
+ </p>
+ <p>/ EFFECT_INSTANCES
+ </p>
+ <p>/ EFFECT SP INFO SP effect_index
+ </p>
+ <p>/ EFFECT_INSTANCE SP INFO SP effect_instance
+ </p>
+ <p>/ EFFECT_INSTANCE_INPUT_CONTROL SP INFO SP effect_instance SP input_control
+ </p>
+ <p>/ SEND_EFFECT_CHAINS SP device_index
+ </p>
+ <p>/ SEND_EFFECT_CHAIN SP INFO SP device_index SP effect_chain
+ </p>
  <p>/ AVAILABLE_MIDI_INPUT_DRIVERS
  </p>
-Line 10189 
 Command Syntax</h3>
+Line 12524 
 Command Syntax</h3>
  <p>/ VOLUME
  </p>
+ <p>/ VOICES
+ </p>
+ <p>/ STREAMS
+ </p>
  <p>/ FILE SP INSTRUMENTS SP filename
  </p>
-Line 10216 
 Command Syntax</h3>
+Line 12557 
 Command Syntax</h3>
  <p>/ MIDI_INPUT_PORT_PARAMETER SP number SP number SP string '=' param_val_list
  </p>
+ <p>/ EFFECT_INSTANCE_INPUT_CONTROL SP VALUE SP effect_instance SP input_control SP control_value
+ </p>
  <p>/ CHANNEL SP set_chan_instruction
  </p>
-Line 10234 
 Command Syntax</h3>
+Line 12578 
 Command Syntax</h3>
  <p>/ FX_SEND SP LEVEL SP sampler_channel SP fx_send_id SP volume_value
  </p>
+ <p>/ FX_SEND SP EFFECT SP sampler_channel SP fx_send_id SP effect_chain SP chain_pos
+ </p>
  <p>/ DB_INSTRUMENT_DIRECTORY SP NAME SP db_path SP stringval_escaped
  </p>
-Line 10255 
 Command Syntax</h3>
+Line 12602 
 Command Syntax</h3>
  <p>/ VOLUME SP volume_value
  </p>
+ <p>/ VOICES SP number
+ </p>
+ <p>/ STREAMS SP number
+ </p>
  </blockquote><p>
  </p>
-Line 10279 
 Command Syntax</h3>
+Line 12632 
 Command Syntax</h3>
  <p>/ FX_SEND SP sampler_channel SP midi_ctrl SP fx_send_name
  </p>
+ <p>/ EFFECT_INSTANCE SP effect_index
+ </p>
+ <p>/ EFFECT_INSTANCE SP effect_system SP module SP effect_name
+ </p>
  </blockquote><p>
  </p>
-Line 10360 
 Command Syntax</h3>
+Line 12719 
 Command Syntax</h3>
  <p>/ FX_SEND SP sampler_channel SP fx_send_id
  </p>
+ <p>/ EFFECT_INSTANCE SP number
+ </p>
  </blockquote><p>
  </p>
-Line 10375 
 Command Syntax</h3>
+Line 12737 
 Command Syntax</h3>
  </blockquote><p>
  </p>
+ <p>append_instruction =
+         </p>
+ <blockquote class="text">
+ <p>SEND_EFFECT_CHAIN SP EFFECT SP device_index SP effect_chain SP effect_instance
+ </p>
+ </blockquote><p>
+ </p>
+ <p>insert_instruction =
+         </p>
+ <blockquote class="text">
+ <p>SEND_EFFECT_CHAIN SP EFFECT SP device_index SP effect_chain SP chain_pos SP effect_instance
+ </p>
+ </blockquote><p>
+ </p>
  <p>set_chan_instruction =
          </p>
  <blockquote class="text">
-Line 10489 
 Command Syntax</h3>
+Line 12869 
 Command Syntax</h3>
  <p>/ CHANNELS
  </p>
+ <p>/ CHANNEL SP MIDI_INPUTS SP sampler_channel
+ </p>
  <p>/ AVAILABLE_ENGINES
  </p>
+ <p>/ AVAILABLE_EFFECTS
+ </p>
+ <p>/ EFFECT_INSTANCES
+ </p>
+ <p>/ SEND_EFFECT_CHAINS SP number
+ </p>
  <p>/ AVAILABLE_MIDI_INPUT_DRIVERS
  </p>
-Line 10573 
 Command Syntax</h3>
+Line 12965 
 Command Syntax</h3>
  </blockquote><p>
  </p>
+ <p>effect_instance =
+         </p>
+ <blockquote class="text">
+ <p>number
+ </p>
+ </blockquote><p>
+ </p>
  <p>device_index =
          </p>
  <blockquote class="text">
-Line 10678 
 Command Syntax</h3>
+Line 13079 
 Command Syntax</h3>
  </blockquote><p>
  </p>
+ <p>control_value =
+         </p>
+ <blockquote class="text">
+ <p>real
+ </p>
+ </blockquote><p>
+ </p>
  <p>sampler_channel =
          </p>
  <blockquote class="text">
-Line 10759 
 Command Syntax</h3>
+Line 13169 
 Command Syntax</h3>
  </blockquote><p>
  </p>
+ <p>effect_name =
+         </p>
+ <blockquote class="text">
+ <p>stringval_escaped
+ </p>
+ </blockquote><p>
+ </p>
+ <p>effect_index =
+         </p>
+ <blockquote class="text">
+ <p>number
+ </p>
+ </blockquote><p>
+ </p>
+ <p>effect_chain =
+         </p>
+ <blockquote class="text">
+ <p>number
+ </p>
+ </blockquote><p>
+ </p>
+ <p>chain_pos =
+         </p>
+ <blockquote class="text">
+ <p>number
+ </p>
+ </blockquote><p>
+ </p>
+ <p>input_control =
+         </p>
+ <blockquote class="text">
+ <p>number
+ </p>
+ </blockquote><p>
+ </p>
  <p>param_val_list =
          </p>
  <blockquote class="text">
-Line 10828 
 Command Syntax</h3>
+Line 13283 
 Command Syntax</h3>
  </blockquote><p>
  </p>
+ <p>effect_system =
+         </p>
+ <blockquote class="text">
+ <p>string
+ </p>
+ </blockquote><p>
+ </p>
+ <p>module =
+         </p>
+ <blockquote class="text">
+ <p>filename
+ </p>
+ </blockquote><p>
+ </p>
  <a name="character_set"></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.1"></a><h3>7.1.&nbsp;
-Line 10885 
 Character Set and Escape Sequences</h3>
+Line 13358 
 Character Set and Escape Sequences</h3>
  <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
-Line 10957 
 Character Set and Escape Sequences</h3>
+Line 13431 
 Character Set and Escape Sequences</h3>
  </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>
+ <p><a class='info' href='#GET EFFECT INFO'>"GET EFFECT INFO"<span> (</span><span class='info'>Retrieving general information about an effect</span><span>)</span></a>
+ </p>
+ <p><a class='info' href='#GET EFFECT_INSTANCE INFO'>"GET EFFECT_INSTANCE INFO"<span> (</span><span class='info'>Retrieving current information about an effect instance</span><span>)</span></a>
+ </p>
+ <p><a class='info' href='#CREATE EFFECT_INSTANCE'>"CREATE EFFECT_INSTANCE"<span> (</span><span class='info'>Creating an instance of an effect by its portable ID</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
-Line 11021 
 Character Set and Escape Sequences</h3>
+Line 13501 
 Character Set and Escape Sequences</h3>
  </p>
  <p><a class='info' href='#FIND DB_INSTRUMENTS'>"FIND DB_INSTRUMENTS"<span> (</span><span class='info'>Finding instruments</span><span>)</span></a>
  </p>
+ <p><a class='info' href='#GET EFFECT INFO'>"GET EFFECT INFO"<span> (</span><span class='info'>Retrieving general information about an effect</span><span>)</span></a>
+ </p>
+ <p><a class='info' href='#GET EFFECT_INSTANCE INFO'>"GET EFFECT_INSTANCE INFO"<span> (</span><span class='info'>Retrieving current information about an effect instance</span><span>)</span></a>
+ </p>
+ <p><a class='info' href='#CREATE EFFECT_INSTANCE'>"CREATE EFFECT_INSTANCE"<span> (</span><span class='info'>Creating an instance of an effect by its portable ID</span><span>)</span></a>
+ </p>
  </blockquote><p>
                  Please note that these lists are manually maintained. If you
                  find a command that also supports escape sequences we forgot to
-Line 11658 
 Global settings changed</h3>
+Line 14144 
 Global settings changed</h3>
                          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 />
-Line 11851 
 Database job status information changed<
+Line 14353 
 Database job status information changed<
                  time events happening on the server, it is believed that an empty notification
                  message is sufficient here.
  </p>
- <a name="SUBSCRIBE MISCELLANEOUS"></a><br /><hr />
+ <a name="SUBSCRIBE EFFECT_INSTANCE_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.26"></a><h3>8.26.&nbsp;
+ Number of effect instances changed</h3>
+ <p>Client may want to be notified when the number of effect instances
+                 is changed by issuing the following command:
+ </p>
+ <p>
+                     </p>
+ <blockquote class="text">
+ <p>SUBSCRIBE EFFECT_INSTANCE_COUNT
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Server will start sending the following notification messages:
+ </p>
+ <p>
+                     </p>
+ <blockquote class="text">
+ <p>"EFFECT_INSTANCE_COUNT:&lt;instances&gt;"
+ </p>
+ </blockquote><p>
+ </p>
+ <p>where &lt;instances&gt; will be replaced by the new number
+                 of effect instances.
+ </p>
+ <a name="SUBSCRIBE EFFECT_INSTANCE_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.27"></a><h3>8.27.&nbsp;
+ Effect instance information changed</h3>
+ <p>Client may want to be notified when changes were made to effect instances
+                 on the back-end by issuing the following command:
+ </p>
+ <p>
+                     </p>
+ <blockquote class="text">
+ <p>SUBSCRIBE EFFECT_INSTANCE_INFO
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Server will start sending the following notification messages:
+ </p>
+ <p>
+                    </p>
+ <blockquote class="text">
+ <p>"EFFECT_INSTANCE_INFO:&lt;instance-id&gt;"
+ </p>
+ </blockquote><p>
+ </p>
+ <p>where &lt;instance-id&gt; will be replaced by the numerical ID
+                 of the effect instance.
+ </p>
+ <a name="SUBSCRIBE SEND_EFFECT_CHAIN_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.28"></a><h3>8.28.&nbsp;
+ Number of send effect chains changed</h3>
+ <p>Client may want to be notified when the number of send effect chains
+                 is changed by issuing the following command:
+ </p>
+ <p>
+                     </p>
+ <blockquote class="text">
+ <p>SUBSCRIBE SEND_EFFECT_CHAIN_COUNT
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Server will start sending the following notification messages:
+ </p>
+ <p>
+                     </p>
+ <blockquote class="text">
+ <p>"NOTIFY:SEND_EFFECT_CHAIN_COUNT:&lt;device-id&gt; &lt;chains&gt;"
+ </p>
+ </blockquote><p>
+ </p>
+ <p>where &lt;device-id&gt; will be replaced by the numerical ID of the audio
+                 output device, in which the number of send effect chains is changed and
+                 &lt;chains&gt; will be replaced by the new number of send effect chains.
+ </p>
+ <a name="SUBSCRIBE SEND_EFFECT_CHAIN_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.29"></a><h3>8.29.&nbsp;
+ Send effect chain information changed</h3>
+ <p>Client may want to be notified when changes were made to send effect chains
+                 on the back-end by issuing the following command:
+ </p>
+ <p>
+                     </p>
+ <blockquote class="text">
+ <p>SUBSCRIBE SEND_EFFECT_CHAIN_INFO
+ </p>
+ </blockquote><p>
+ </p>
+ <p>Server will start sending the following notification messages:
+ </p>
+ <p>
+                    </p>
+ <blockquote class="text">
+ <p>"SEND_EFFECT_CHAIN_INFO:&lt;device-id&gt; &lt;chain-id&gt; &lt;instances&gt;" -
+                         Notifies that the number of effect instances in a particular send effect chain
+                         is changed, where &lt;device-id&gt; will be replaced by the numerical ID of the audio
+                         output device the send effect chain belongs to, &lt;chain-id&gt; will be replaced
+                         by the numerical ID of the send effect chain in which the number of effect instances
+                         has changed and &lt;instances&gt; will be replaced by the new number
+                         of effect instances in the specified send effect chain.
+ </p>
+ </blockquote><p>
+ </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.30"></a><h3>8.30.&nbsp;
  Miscellaneous and debugging events</h3>
  <p>Client may want to be notified of miscellaneous and debugging events occurring at
-Line 11919 
 Acknowledgments</h3>
+Line 14541 
 Acknowledgments</h3>
  <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 />
-Line 11936 
 Acknowledgments</h3>
+Line 14558 
 Acknowledgments</h3>
  <td class="author-text">C.
  Schoenebeck</td></tr>
  <tr><td class="author-text">&nbsp;</td>
- <td class="author-text">Interessengemeinschaft Software Engineering e. V.</td></tr>
+ <td class="author-text">LinuxSampler.org</td></tr>
+ <tr><td class="author-text">&nbsp;</td>
+ <td class="author-text">Crudebyte Engineering</td></tr>
  <tr><td class="author-text">&nbsp;</td>
- <td class="author-text">Max-Planck-Str. 39</td></tr>
+ <td class="author-text">Hofgartenstr. 3</td></tr>
  <tr><td class="author-text">&nbsp;</td>
- <td class="author-text">74081 Heilbronn</td></tr>
+ <td class="author-text">74189 Weinsberg</td></tr>
  <tr><td class="author-text">&nbsp;</td>
  <td class="author-text">Germany</td></tr>
+ <tr><td class="author" align="right">Phone:&nbsp;</td>
+ <td class="author-text">+49 7134 911614</td></tr>
  <tr><td class="author" align="right">Email:&nbsp;</td>
- <td class="author-text"><a href="mailto:schoenebeck at software minus engineering dot org">schoenebeck at software minus engineering dot org</a></td></tr>
+ <td class="author-text"><a href="mailto:cuse@users.sf.net">cuse@users.sf.net</a></td></tr>
  </table>
  <a name="rfc.copyright"></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>
  <h3>Full Copyright Statement</h3>
  <p class='copyright'>
- Copyright &copy; The IETF Trust (2008).</p>
+ Copyright &copy; The IETF Trust (2014).</p>
  <p class='copyright'>
  This document is subject to the rights,
  licenses and restrictions contained in BCP&nbsp;78,
-Line 11992 
 or other
+Line 14618 
 or other
  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>

 Legend:



Removed from v.1773
 


changed lines


 
Added in v.2498
 Legend:



Removed from v.1773
 


changed lines


 
Added in v.2498
-Removed from v.1773
+Added in v.2498

	ViewVC Help
Powered by ViewVC