--- web/trunk/www.linuxsampler.org/api/draft-linuxsampler-protocol.txt	2019/03/11 15:42:54	3502
+++ web/trunk/www.linuxsampler.org/api/draft-linuxsampler-protocol.txt	2019/03/11 15:46:15	3503
@@ -1,10 +1,11 @@
 
 
 
-LinuxSampler Developers                                   C. Schoenebeck
+
+LinuxSampler Developers                              C. Schoenebeck, Ed.
 Internet-Draft                                          LinuxSampler.org
-Intended status: Standards Track                           July 15, 2015
-Expires: January 16, 2016
+Intended status: Informational                            March 11, 2019
+Expires: September 12, 2019
 
 
                      LinuxSampler Control Protocol
@@ -18,12 +19,10 @@
    like console application essentially playing back audio samples and
    manipulating the samples in real time to certain extent.
 
-Status of this Memo
+Status of This Memo
 
-   By submitting this Internet-Draft, each author represents that any
-   applicable patent or other IPR claims of which he or she is aware
-   have been or will be disclosed, and any of which he or she becomes
-   aware will be disclosed, in accordance with Section 6 of BCP 79.
+   This Internet-Draft is submitted in full conformance with the
+   provisions of BCP 78 and BCP 79.
 
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
@@ -35,307 +34,274 @@
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on January 16, 2016.
-
-
-
-
-
-
-
+   This Internet-Draft will expire on September 12, 2019.
 
+Copyright Notice
 
+   Copyright (c) 2019 IETF Trust and the persons identified as the
+   document authors.  All rights reserved.
 
+   This document is subject to BCP 78 and the IETF Trust's Legal
+   Provisions Relating to IETF Documents
+   (http://trustee.ietf.org/license-info) in effect on the date of
+   publication of this document.  Please review these documents
+   carefully, as they describe your rights and restrictions with respect
+   to this document.  Code Components extracted from this document must
+   include Simplified BSD License text as described in Section 4.e of
+   the Trust Legal Provisions and are provided without warranty as
+   described in the Simplified BSD License.
 
 
 
-
-
-
-Schoenebeck             Expires January 16, 2016                [Page 1]
+Schoenebeck            Expires September 12, 2019               [Page 1]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
 
+   This document may not be modified, and derivative works of it may not
+   be created, and it may not be published except as an Internet-Draft.
 
 Table of Contents
 
-   1.  Requirements notation . . . . . . . . . . . . . . . . . . . .   7
-   2.  Versioning of this specification  . . . . . . . . . . . . . .   8
-   3.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   9
-   4.  Focus of this protocol  . . . . . . . . . . . . . . . . . . .  10
-   5.  Communication Overview  . . . . . . . . . . . . . . . . . . .  11
-     5.1.  Request/response communication method . . . . . . . . . .  11
-       5.1.1.   Result format  . . . . . . . . . . . . . . . . . . .  12
-     5.2.  Subscribe/notify communication method . . . . . . . . . .  14
-   6.  Description for control commands  . . . . . . . . . . . . . .  16
-     6.1.  Ignored lines and comments  . . . . . . . . . . . . . . .  16
-     6.2.  Configuring audio drivers . . . . . . . . . . . . . . . .  16
-       6.2.1.   Getting amount of available audio output drivers . .  17
-       6.2.2.   Getting all available audio output drivers . . . . .  17
-       6.2.3.   Getting information about a specific audio output
-                driver . . . . . . . . . . . . . . . . . . . . . . .  17
-       6.2.4.   Getting information about specific audio output
-                driver parameter . . . . . . . . . . . . . . . . . .  18
-       6.2.5.   Creating an audio output device  . . . . . . . . . .  22
-       6.2.6.   Destroying an audio output device  . . . . . . . . .  23
-       6.2.7.   Getting all created audio output device count  . . .  24
-       6.2.8.   Getting all created audio output device list . . . .  24
-       6.2.9.   Getting current settings of an audio output device .  24
-       6.2.10.  Changing settings of audio output devices  . . . . .  26
-       6.2.11.  Getting information about an audio channel . . . . .  27
-       6.2.12.  Getting information about specific audio channel
-                parameter  . . . . . . . . . . . . . . . . . . . . .  28
-       6.2.13.  Changing settings of audio output channels . . . . .  30
-     6.3.  Configuring MIDI input drivers  . . . . . . . . . . . . .  31
-       6.3.1.   Getting amount of available MIDI input drivers . . .  32
-       6.3.2.   Getting all available MIDI input drivers . . . . . .  32
-       6.3.3.   Getting information about a specific MIDI input
-                driver . . . . . . . . . . . . . . . . . . . . . . .  33
-       6.3.4.   Getting information about specific MIDI input
-                driver parameter . . . . . . . . . . . . . . . . . .  34
-       6.3.5.   Creating a MIDI input device . . . . . . . . . . . .  36
-       6.3.6.   Destroying a MIDI input device . . . . . . . . . . .  37
-       6.3.7.   Getting all created MIDI input device count  . . . .  38
-       6.3.8.   Getting all created MIDI input device list . . . . .  38
-       6.3.9.   Getting current settings of a MIDI input device  . .  39
-       6.3.10.  Changing settings of MIDI input devices  . . . . . .  40
-       6.3.11.  Getting information about a MIDI port  . . . . . . .  40
-       6.3.12.  Getting information about specific MIDI port
-                parameter  . . . . . . . . . . . . . . . . . . . . .  41
-       6.3.13.  Changing settings of MIDI input ports  . . . . . . .  43
-     6.4.  Configuring sampler channels  . . . . . . . . . . . . . .  44
-       6.4.1.   Loading an instrument  . . . . . . . . . . . . . . .  44
-
-
-
-Schoenebeck             Expires January 16, 2016                [Page 2]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-       6.4.2.   Loading a sampler engine . . . . . . . . . . . . . .  45
-       6.4.3.   Getting all created sampler channel count  . . . . .  46
-       6.4.4.   Getting all created sampler channel list . . . . . .  47
-       6.4.5.   Adding a new sampler channel . . . . . . . . . . . .  47
-       6.4.6.   Removing a sampler channel . . . . . . . . . . . . .  48
-       6.4.7.   Getting amount of available engines  . . . . . . . .  49
-       6.4.8.   Getting all available engines  . . . . . . . . . . .  49
-       6.4.9.   Getting information about an engine  . . . . . . . .  49
-       6.4.10.  Getting sampler channel information  . . . . . . . .  51
-       6.4.11.  Current number of active voices  . . . . . . . . . .  54
-       6.4.12.  Current number of active disk streams  . . . . . . .  55
-       6.4.13.  Current fill state of disk stream buffers  . . . . .  55
-       6.4.14.  Setting audio output device  . . . . . . . . . . . .  56
-       6.4.15.  Setting audio output type  . . . . . . . . . . . . .  57
-       6.4.16.  Setting audio output channel . . . . . . . . . . . .  58
-       6.4.17.  Add MIDI input to sampler channel  . . . . . . . . .  59
-       6.4.18.  Remove MIDI input(s) from sampler channel  . . . . .  60
-       6.4.19.  Getting all MIDI inputs of a sampler channel . . . .  61
-       6.4.20.  Setting MIDI input device  . . . . . . . . . . . . .  62
-       6.4.21.  Setting MIDI input type  . . . . . . . . . . . . . .  63
-       6.4.22.  Setting MIDI input port  . . . . . . . . . . . . . .  64
-       6.4.23.  Setting MIDI input channel . . . . . . . . . . . . .  65
-       6.4.24.  Setting channel volume . . . . . . . . . . . . . . .  66
-       6.4.25.  Muting a sampler channel . . . . . . . . . . . . . .  66
-       6.4.26.  Soloing a sampler channel  . . . . . . . . . . . . .  67
-       6.4.27.  Assigning a MIDI instrument map to a sampler
-                channel  . . . . . . . . . . . . . . . . . . . . . .  68
-       6.4.28.  Adding an effect send to a sampler channel . . . . .  69
-       6.4.29.  Removing an effect send from a sampler channel . . .  70
-       6.4.30.  Getting amount of effect sends on a sampler
-                channel  . . . . . . . . . . . . . . . . . . . . . .  71
-       6.4.31.  Listing all effect sends on a sampler channel  . . .  71
-       6.4.32.  Getting effect send information  . . . . . . . . . .  72
-       6.4.33.  Changing effect send's name  . . . . . . . . . . . .  74
-       6.4.34.  Altering effect send's audio routing . . . . . . . .  75
-       6.4.35.  Assigning destination effect to an effect send . . .  76
-       6.4.36.  Removing destination effect from an effect send  . .  77
-       6.4.37.  Altering effect send's MIDI controller . . . . . . .  77
-       6.4.38.  Altering effect send's send level  . . . . . . . . .  78
-       6.4.39.  Sending MIDI messages to sampler channel . . . . . .  79
-       6.4.40.  Resetting a sampler channel  . . . . . . . . . . . .  80
-     6.5.  Controlling connection  . . . . . . . . . . . . . . . . .  81
-       6.5.1.   Register front-end for receiving event messages  . .  81
-       6.5.2.   Unregister front-end for not receiving event
-                messages . . . . . . . . . . . . . . . . . . . . . .  81
-       6.5.3.   Enable or disable echo of commands . . . . . . . . .  82
-       6.5.4.   Close client connection  . . . . . . . . . . . . . .  83
-     6.6.  Global commands . . . . . . . . . . . . . . . . . . . . .  83
-
-
-
-Schoenebeck             Expires January 16, 2016                [Page 3]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-       6.6.1.   Current number of active voices  . . . . . . . . . .  83
-       6.6.2.   Maximum amount of active voices  . . . . . . . . . .  83
-       6.6.3.   Current number of active disk streams  . . . . . . .  83
-       6.6.4.   Reset sampler  . . . . . . . . . . . . . . . . . . .  84
-       6.6.5.   General sampler informations . . . . . . . . . . . .  84
-       6.6.6.   Getting global volume attenuation  . . . . . . . . .  85
-       6.6.7.   Setting global volume attenuation  . . . . . . . . .  86
-       6.6.8.   Getting global voice limit . . . . . . . . . . . . .  86
-       6.6.9.   Setting global voice limit . . . . . . . . . . . . .  87
-       6.6.10.  Getting global disk stream limit . . . . . . . . . .  87
-       6.6.11.  Setting global disk stream limit . . . . . . . . . .  88
-     6.7.  MIDI Instrument Mapping . . . . . . . . . . . . . . . . .  88
-       6.7.1.   Create a new MIDI instrument map . . . . . . . . . .  89
-       6.7.2.   Delete one particular or all MIDI instrument maps  .  90
-       6.7.3.   Get amount of existing MIDI instrument maps  . . . .  91
-       6.7.4.   Getting all created MIDI instrument maps . . . . . .  91
-       6.7.5.   Getting MIDI instrument map information  . . . . . .  91
-       6.7.6.   Renaming a MIDI instrument map . . . . . . . . . . .  92
-       6.7.7.   Create or replace a MIDI instrument map entry  . . .  93
-       6.7.8.   Getting amount of MIDI instrument map entries  . . .  96
-       6.7.9.   Getting indeces of all entries of a MIDI
-                instrument map . . . . . . . . . . . . . . . . . . .  96
-       6.7.10.  Remove an entry from the MIDI instrument map . . . .  97
-       6.7.11.  Get current settings of MIDI instrument map entry  .  98
-       6.7.12.  Clear MIDI instrument map  . . . . . . . . . . . . .  99
-     6.8.  Managing Instruments Database . . . . . . . . . . . . . . 100
-       6.8.1.   Creating a new instrument directory  . . . . . . . . 100
-       6.8.2.   Deleting an instrument directory . . . . . . . . . . 101
-       6.8.3.   Getting amount of instrument directories . . . . . . 102
-       6.8.4.   Listing all directories in specific directory  . . . 102
-       6.8.5.   Getting instrument directory information . . . . . . 103
-       6.8.6.   Renaming an instrument directory . . . . . . . . . . 104
-       6.8.7.   Moving an instrument directory . . . . . . . . . . . 104
-       6.8.8.   Copying instrument directories . . . . . . . . . . . 105
-       6.8.9.   Changing the description of directory  . . . . . . . 106
-       6.8.10.  Finding directories  . . . . . . . . . . . . . . . . 106
-       6.8.11.  Adding instruments to the instruments database . . . 108
-       6.8.12.  Removing an instrument . . . . . . . . . . . . . . . 109
-       6.8.13.  Getting amount of instruments  . . . . . . . . . . . 110
-       6.8.14.  Listing all instruments in specific directory  . . . 111
-       6.8.15.  Getting instrument information . . . . . . . . . . . 111
-       6.8.16.  Renaming an instrument . . . . . . . . . . . . . . . 114
-       6.8.17.  Moving an instrument . . . . . . . . . . . . . . . . 114
-       6.8.18.  Copying instruments  . . . . . . . . . . . . . . . . 115
-       6.8.19.  Changing the description of instrument . . . . . . . 115
-       6.8.20.  Finding instruments  . . . . . . . . . . . . . . . . 116
-       6.8.21.  Getting job status information . . . . . . . . . . . 118
-       6.8.22.  Formatting the instruments database  . . . . . . . . 120
-
-
-
-Schoenebeck             Expires January 16, 2016                [Page 4]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-       6.8.23.  Checking for lost instrument files . . . . . . . . . 120
-       6.8.24.  Replacing an instrument file . . . . . . . . . . . . 121
-     6.9.  Editing Instruments . . . . . . . . . . . . . . . . . . . 121
-       6.9.1.   Opening an appropriate instrument editor
-                application  . . . . . . . . . . . . . . . . . . . . 121
-     6.10. Managing Files  . . . . . . . . . . . . . . . . . . . . . 122
-       6.10.1.  Retrieving amount of instruments of a file . . . . . 123
-       6.10.2.  Retrieving all instruments of a file . . . . . . . . 123
-       6.10.3.  Retrieving informations about one instrument in a
-                file . . . . . . . . . . . . . . . . . . . . . . . . 124
-     6.11. Managing Effects  . . . . . . . . . . . . . . . . . . . . 126
-       6.11.1.  Retrieve amount of available effects . . . . . . . . 126
-       6.11.2.  Get list of available effects  . . . . . . . . . . . 127
-       6.11.3.  Retrieving general information about an effect . . . 127
-       6.11.4.  Creating an instance of an effect by its portable
-                ID . . . . . . . . . . . . . . . . . . . . . . . . . 128
-       6.11.5.  Creating an instance of an effect by its
-                numerical ID . . . . . . . . . . . . . . . . . . . . 129
-       6.11.6.  Destroy an effect instance . . . . . . . . . . . . . 130
-       6.11.7.  Retrieve amount of effect instances  . . . . . . . . 131
-       6.11.8.  Get list of effect instances . . . . . . . . . . . . 131
+   1.  Requirements notation . . . . . . . . . . . . . . . . . . . .   6
+   2.  Versioning of this specification  . . . . . . . . . . . . . .   7
+   3.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   8
+   4.  Focus of this protocol  . . . . . . . . . . . . . . . . . . .   8
+   5.  Communication Overview  . . . . . . . . . . . . . . . . . . .   8
+     5.1.  Request/response communication method . . . . . . . . . .   9
+       5.1.1.  Result format . . . . . . . . . . . . . . . . . . . .   9
+     5.2.  Subscribe/notify communication method . . . . . . . . . .  12
+   6.  Description for control commands  . . . . . . . . . . . . . .  13
+     6.1.  Ignored lines and comments  . . . . . . . . . . . . . . .  14
+     6.2.  Configuring audio drivers . . . . . . . . . . . . . . . .  14
+       6.2.1.  Getting amount of available audio output drivers  . .  14
+       6.2.2.  Getting all available audio output drivers  . . . . .  15
+       6.2.3.  Getting information about a specific audio
+               output driver . . . . . . . . . . . . . . . . . . . .  15
+       6.2.4.  Getting information about specific audio
+               output driver parameter . . . . . . . . . . . . . . .  16
+       6.2.5.  Creating an audio output device . . . . . . . . . . .  20
+       6.2.6.  Destroying an audio output device . . . . . . . . . .  21
+       6.2.7.  Getting all created audio output device count . . . .  21
+       6.2.8.  Getting all created audio output device list  . . . .  22
+       6.2.9.  Getting current settings of an audio output device  .  22
+       6.2.10. Changing settings of audio output devices . . . . . .  23
+       6.2.11. Getting information about an audio channel  . . . . .  24
+       6.2.12. Getting information about specific audio channel
+               parameter . . . . . . . . . . . . . . . . . . . . . .  26
+       6.2.13. Changing settings of audio output channels  . . . . .  28
+     6.3.  Configuring MIDI input drivers  . . . . . . . . . . . . .  29
+       6.3.1.  Getting amount of available MIDI input drivers  . . .  29
+       6.3.2.  Getting all available MIDI input drivers  . . . . . .  30
+       6.3.3.  Getting information about a specific MIDI input
+               driver  . . . . . . . . . . . . . . . . . . . . . . .  30
+       6.3.4.  Getting information about specific MIDI input driver
+               parameter . . . . . . . . . . . . . . . . . . . . . .  31
+       6.3.5.  Creating a MIDI input device  . . . . . . . . . . . .  34
+       6.3.6.  Destroying a MIDI input device  . . . . . . . . . . .  35
+       6.3.7.  Getting all created MIDI input device count . . . . .  35
+       6.3.8.  Getting all created MIDI input device list  . . . . .  36
+       6.3.9.  Getting current settings of a MIDI input device . . .  36
+       6.3.10. Changing settings of MIDI input devices . . . . . . .  37
+       6.3.11. Getting information about a MIDI port . . . . . . . .  38
+       6.3.12. Getting information about specific MIDI port
+               parameter . . . . . . . . . . . . . . . . . . . . . .  39
+
+
+
+Schoenebeck            Expires September 12, 2019               [Page 2]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
+       6.3.13. Changing settings of MIDI input ports . . . . . . . .  41
+     6.4.  Configuring sampler channels  . . . . . . . . . . . . . .  41
+       6.4.1.  Loading an instrument . . . . . . . . . . . . . . . .  42
+       6.4.2.  Loading a sampler engine  . . . . . . . . . . . . . .  43
+       6.4.3.  Getting all created sampler channel count . . . . . .  44
+       6.4.4.  Getting all created sampler channel list  . . . . . .  44
+       6.4.5.  Adding a new sampler channel  . . . . . . . . . . . .  44
+       6.4.6.  Removing a sampler channel  . . . . . . . . . . . . .  45
+       6.4.7.  Getting amount of available engines . . . . . . . . .  46
+       6.4.8.  Getting all available engines . . . . . . . . . . . .  46
+       6.4.9.  Getting information about an engine . . . . . . . . .  47
+       6.4.10. Getting sampler channel information . . . . . . . . .  48
+       6.4.11. Current number of active voices . . . . . . . . . . .  52
+       6.4.12. Current number of active disk streams . . . . . . . .  52
+       6.4.13. Current fill state of disk stream buffers . . . . . .  52
+       6.4.14. Setting audio output device . . . . . . . . . . . . .  53
+       6.4.15. Setting audio output type . . . . . . . . . . . . . .  54
+       6.4.16. Setting audio output channel  . . . . . . . . . . . .  55
+       6.4.17. Add MIDI input to sampler channel . . . . . . . . . .  56
+       6.4.18. Remove MIDI input(s) from sampler channel . . . . . .  57
+       6.4.19. Getting all MIDI inputs of a sampler channel  . . . .  58
+       6.4.20. Setting MIDI input device . . . . . . . . . . . . . .  59
+       6.4.21. Setting MIDI input type . . . . . . . . . . . . . . .  60
+       6.4.22. Setting MIDI input port . . . . . . . . . . . . . . .  61
+       6.4.23. Setting MIDI input channel  . . . . . . . . . . . . .  62
+       6.4.24. Setting channel volume  . . . . . . . . . . . . . . .  63
+       6.4.25. Muting a sampler channel  . . . . . . . . . . . . . .  63
+       6.4.26. Soloing a sampler channel . . . . . . . . . . . . . .  64
+       6.4.27. Assigning a MIDI instrument map to a sampler channel   65
+       6.4.28. Adding an effect send to a sampler channel  . . . . .  66
+       6.4.29. Removing an effect send from a sampler channel  . . .  67
+       6.4.30. Getting amount of effect sends on a sampler channel .  68
+       6.4.31. Listing all effect sends on a sampler channel . . . .  68
+       6.4.32. Getting effect send information . . . . . . . . . . .  69
+       6.4.33. Changing effect send's name . . . . . . . . . . . . .  71
+       6.4.34. Altering effect send's audio routing  . . . . . . . .  71
+       6.4.35. Assigning destination effect to an effect send  . . .  73
+       6.4.36. Removing destination effect from an effect send . . .  74
+       6.4.37. Altering effect send's MIDI controller  . . . . . . .  74
+       6.4.38. Altering effect send's send level . . . . . . . . . .  75
+       6.4.39. Sending MIDI messages to sampler channel  . . . . . .  76
+       6.4.40. Resetting a sampler channel . . . . . . . . . . . . .  77
+     6.5.  Controlling connection  . . . . . . . . . . . . . . . . .  78
+       6.5.1.  Register front-end for receiving event messages . . .  78
+       6.5.2.  Unregister front-end for not receiving event messages  78
+       6.5.3.  Enable or disable echo of commands  . . . . . . . . .  79
+       6.5.4.  Close client connection . . . . . . . . . . . . . . .  80
+     6.6.  Global commands . . . . . . . . . . . . . . . . . . . . .  80
+
+
+
+Schoenebeck            Expires September 12, 2019               [Page 3]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
+       6.6.1.  Current number of active voices . . . . . . . . . . .  80
+       6.6.2.  Maximum amount of active voices . . . . . . . . . . .  80
+       6.6.3.  Current number of active disk streams . . . . . . . .  80
+       6.6.4.  Reset sampler . . . . . . . . . . . . . . . . . . . .  81
+       6.6.5.  General sampler information . . . . . . . . . . . . .  81
+       6.6.6.  Getting global volume attenuation . . . . . . . . . .  82
+       6.6.7.  Setting global volume attenuation . . . . . . . . . .  83
+       6.6.8.  Getting global voice limit  . . . . . . . . . . . . .  83
+       6.6.9.  Setting global voice limit  . . . . . . . . . . . . .  84
+       6.6.10. Getting global disk stream limit  . . . . . . . . . .  84
+       6.6.11. Setting global disk stream limit  . . . . . . . . . .  85
+     6.7.  MIDI Instrument Mapping . . . . . . . . . . . . . . . . .  85
+       6.7.1.  Create a new MIDI instrument map  . . . . . . . . . .  86
+       6.7.2.  Delete one particular or all MIDI instrument maps . .  87
+       6.7.3.  Get amount of existing MIDI instrument maps . . . . .  88
+       6.7.4.  Getting all created MIDI instrument maps  . . . . . .  88
+       6.7.5.  Getting MIDI instrument map information . . . . . . .  88
+       6.7.6.  Renaming a MIDI instrument map  . . . . . . . . . . .  89
+       6.7.7.  Create or replace a MIDI instrument map entry . . . .  90
+       6.7.8.  Getting amount of MIDI instrument map entries . . . .  93
+       6.7.9.  Getting indeces of all entries of a MIDI instrument
+               map . . . . . . . . . . . . . . . . . . . . . . . . .  93
+       6.7.10. Remove an entry from the MIDI instrument map  . . . .  94
+       6.7.11. Get current settings of MIDI instrument map entry . .  95
+       6.7.12. Clear MIDI instrument map . . . . . . . . . . . . . .  96
+     6.8.  Managing Instruments Database . . . . . . . . . . . . . .  97
+       6.8.1.  Creating a new instrument directory . . . . . . . . .  97
+       6.8.2.  Deleting an instrument directory  . . . . . . . . . .  98
+       6.8.3.  Getting amount of instrument directories  . . . . . .  99
+       6.8.4.  Listing all directories in specific directory . . . .  99
+       6.8.5.  Getting instrument directory information  . . . . . . 100
+       6.8.6.  Renaming an instrument directory  . . . . . . . . . . 101
+       6.8.7.  Moving an instrument directory  . . . . . . . . . . . 101
+       6.8.8.  Copying instrument directories  . . . . . . . . . . . 102
+       6.8.9.  Changing the description of directory . . . . . . . . 103
+       6.8.10. Finding directories . . . . . . . . . . . . . . . . . 103
+       6.8.11. Adding instruments to the instruments database  . . . 104
+       6.8.12. Removing an instrument  . . . . . . . . . . . . . . . 106
+       6.8.13. Getting amount of instruments . . . . . . . . . . . . 106
+       6.8.14. Listing all instruments in specific directory . . . . 107
+       6.8.15. Getting instrument information  . . . . . . . . . . . 107
+       6.8.16. Renaming an instrument  . . . . . . . . . . . . . . . 110
+       6.8.17. Moving an instrument  . . . . . . . . . . . . . . . . 110
+       6.8.18. Copying instruments . . . . . . . . . . . . . . . . . 111
+       6.8.19. Changing the description of instrument  . . . . . . . 112
+       6.8.20. Finding instruments . . . . . . . . . . . . . . . . . 112
+       6.8.21. Getting job status information  . . . . . . . . . . . 113
+       6.8.22. Formatting the instruments database . . . . . . . . . 114
+
+
+
+Schoenebeck            Expires September 12, 2019               [Page 4]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
+       6.8.23. Checking for lost instrument files  . . . . . . . . . 115
+       6.8.24. Replacing an instrument file  . . . . . . . . . . . . 115
+     6.9.  Editing Instruments . . . . . . . . . . . . . . . . . . . 116
+       6.9.1.  Opening an appropriate instrument editor application  116
+     6.10. Managing Files  . . . . . . . . . . . . . . . . . . . . . 117
+       6.10.1.  Retrieving amount of instruments of a file . . . . . 117
+       6.10.2.  Retrieving all instruments of a file . . . . . . . . 118
+       6.10.3.  Retrieving information about one instrument in a
+                file . . . . . . . . . . . . . . . . . . . . . . . . 118
+     6.11. Managing Effects  . . . . . . . . . . . . . . . . . . . . 120
+       6.11.1.  Retrieve amount of available effects . . . . . . . . 121
+       6.11.2.  Get list of available effects  . . . . . . . . . . . 121
+       6.11.3.  Retrieving general information about an effect . . . 122
+       6.11.4.  Creating an instance of an effect by its portable ID 123
+       6.11.5.  Creating an instance of an effect by its numerical
+                ID . . . . . . . . . . . . . . . . . . . . . . . . . 124
+       6.11.6.  Destroy an effect instance . . . . . . . . . . . . . 125
+       6.11.7.  Retrieve amount of effect instances  . . . . . . . . 126
+       6.11.8.  Get list of effect instances . . . . . . . . . . . . 126
        6.11.9.  Retrieving current information about an effect
-                instance . . . . . . . . . . . . . . . . . . . . . . 132
-       6.11.10. Retrieving information about an effect parameter . . 133
-       6.11.11. Altering an effect parameter . . . . . . . . . . . . 135
-       6.11.12. Retrieve amount of send effect chains  . . . . . . . 135
-       6.11.13. Retrieve list of send effect chains  . . . . . . . . 136
-       6.11.14. Add send effect chain  . . . . . . . . . . . . . . . 136
-       6.11.15. Remove send effect chain . . . . . . . . . . . . . . 137
-       6.11.16. Retrieving information about a send effect chain . . 138
-       6.11.17. Append effect instance to a send effect chain  . . . 139
-       6.11.18. Insert effect instance to a send effect chain  . . . 139
-       6.11.19. Remove effect instance from send effect chain  . . . 140
-   7.  Command Syntax  . . . . . . . . . . . . . . . . . . . . . . . 142
-     7.1.  Character Set and Escape Sequences  . . . . . . . . . . . 159
-   8.  Events  . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
-     8.1.  Number of audio output devices changed  . . . . . . . . . 164
-     8.2.  Audio output device's settings changed  . . . . . . . . . 164
-     8.3.  Number of MIDI input devices changed  . . . . . . . . . . 164
-     8.4.  MIDI input device's settings changed  . . . . . . . . . . 165
-     8.5.  Number of sampler channels changed  . . . . . . . . . . . 165
-     8.6.  MIDI data on a sampler channel arrived  . . . . . . . . . 165
-     8.7.  MIDI data on a MIDI input device arrived  . . . . . . . . 166
-     8.8.  Number of active voices changed . . . . . . . . . . . . . 166
-     8.9.  Number of active disk streams changed . . . . . . . . . . 167
-     8.10. Disk stream buffer fill state changed . . . . . . . . . . 167
-     8.11. Channel information changed . . . . . . . . . . . . . . . 167
-     8.12. Number of effect sends changed  . . . . . . . . . . . . . 168
-
-
-
-Schoenebeck             Expires January 16, 2016                [Page 5]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-     8.13. Effect send information changed . . . . . . . . . . . . . 168
-     8.14. Total number of active voices changed . . . . . . . . . . 169
-     8.15. Total number of active disk streams changed . . . . . . . 169
-     8.16. Number of MIDI instrument maps changed  . . . . . . . . . 169
-     8.17. MIDI instrument map information changed . . . . . . . . . 169
-     8.18. Number of MIDI instruments changed  . . . . . . . . . . . 170
-     8.19. MIDI instrument information changed . . . . . . . . . . . 170
-     8.20. Global settings changed . . . . . . . . . . . . . . . . . 171
-     8.21. Number of database instrument directories changed . . . . 171
-     8.22. Database instrument directory information changed . . . . 171
-     8.23. Number of database instruments changed  . . . . . . . . . 172
-     8.24. Database instrument information changed . . . . . . . . . 172
-     8.25. Database job status information changed . . . . . . . . . 173
-     8.26. Number of effect instances changed  . . . . . . . . . . . 173
-     8.27. Effect instance information changed . . . . . . . . . . . 174
-     8.28. Number of send effect chains changed  . . . . . . . . . . 174
-     8.29. Send effect chain information changed . . . . . . . . . . 174
-     8.30. Miscellaneous and debugging events  . . . . . . . . . . . 175
-   9.  Security Considerations . . . . . . . . . . . . . . . . . . . 176
-   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 177
-   11. References  . . . . . . . . . . . . . . . . . . . . . . . . . 178
-   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . 179
-   Intellectual Property and Copyright Statements  . . . . . . . . . 180
-
-
-
-
-
-
-
-
-
-
-
+                instance . . . . . . . . . . . . . . . . . . . . . . 126
+       6.11.10. Retrieving information about an effect parameter . . 128
+       6.11.11. Altering an effect parameter . . . . . . . . . . . . 130
+       6.11.12. Retrieve amount of send effect chains  . . . . . . . 130
+       6.11.13. Retrieve list of send effect chains  . . . . . . . . 131
+       6.11.14. Add send effect chain  . . . . . . . . . . . . . . . 131
+       6.11.15. Remove send effect chain . . . . . . . . . . . . . . 132
+       6.11.16. Retrieving information about a send effect chain . . 132
+       6.11.17. Append effect instance to a send effect chain  . . . 133
+       6.11.18. Insert effect instance to a send effect chain  . . . 134
+       6.11.19. Remove effect instance from send effect chain  . . . 135
+   7.  Command Syntax  . . . . . . . . . . . . . . . . . . . . . . . 136
+     7.1.  Character Set and Escape Sequences  . . . . . . . . . . . 153
+   8.  Events  . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
+     8.1.  Number of audio output devices changed  . . . . . . . . . 157
+     8.2.  Audio output device's settings changed  . . . . . . . . . 157
+     8.3.  Number of MIDI input devices changed  . . . . . . . . . . 157
+     8.4.  MIDI input device's settings changed  . . . . . . . . . . 158
+     8.5.  Number of sampler channels changed  . . . . . . . . . . . 158
+     8.6.  MIDI data on a sampler channel arrived  . . . . . . . . . 158
+     8.7.  MIDI data on a MIDI input device arrived  . . . . . . . . 159
+     8.8.  Number of active voices changed . . . . . . . . . . . . . 159
+     8.9.  Number of active disk streams changed . . . . . . . . . . 160
+     8.10. Disk stream buffer fill state changed . . . . . . . . . . 160
+     8.11. Channel information changed . . . . . . . . . . . . . . . 160
+     8.12. Number of effect sends changed  . . . . . . . . . . . . . 161
+     8.13. Effect send information changed . . . . . . . . . . . . . 161
+     8.14. Total number of active voices changed . . . . . . . . . . 162
 
 
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016                [Page 6]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
+Schoenebeck            Expires September 12, 2019               [Page 5]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
+     8.15. Total number of active disk streams changed . . . . . . . 162
+     8.16. Number of MIDI instrument maps changed  . . . . . . . . . 162
+     8.17. MIDI instrument map information changed . . . . . . . . . 162
+     8.18. Number of MIDI instruments changed  . . . . . . . . . . . 163
+     8.19. MIDI instrument information changed . . . . . . . . . . . 163
+     8.20. Global settings changed . . . . . . . . . . . . . . . . . 164
+     8.21. Number of database instrument directories changed . . . . 164
+     8.22. Database instrument directory information changed . . . . 165
+     8.23. Number of database instruments changed  . . . . . . . . . 165
+     8.24. Database instrument information changed . . . . . . . . . 166
+     8.25. Database job status information changed . . . . . . . . . 166
+     8.26. Number of effect instances changed  . . . . . . . . . . . 167
+     8.27. Effect instance information changed . . . . . . . . . . . 167
+     8.28. Number of send effect chains changed  . . . . . . . . . . 167
+     8.29. Send effect chain information changed . . . . . . . . . . 168
+     8.30. Miscellaneous and debugging events  . . . . . . . . . . . 168
+   9.  Security Considerations . . . . . . . . . . . . . . . . . . . 168
+   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 168
+   11. References  . . . . . . . . . . . . . . . . . . . . . . . . . 169
+   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . 169
 
 1.  Requirements notation
 
@@ -354,7 +320,7 @@
 
       C: "some line"
 
-         "another line"
+      "another line"
 
    must actually be interpreted as client sending the following message:
 
@@ -363,6 +329,15 @@
    where <CR> symbolizes the carriage return character and <LF> the line
    feed character as defined in the ASCII standard.
 
+
+
+
+
+Schoenebeck            Expires September 12, 2019               [Page 6]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    Due to technical reasons, messages can arbitrary be fragmented, means
    the following example:
 
@@ -384,15 +359,6 @@
    where again <CR> and <LF> symbolize the carriage return and line feed
    characters respectively.
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016                [Page 7]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 2.  Versioning of this specification
 
    LSCP will certainly be extended and enhanced by-and-by.  Each
@@ -418,37 +384,20 @@
    2.  The frontend's LSCP minor version is less or equal than the
        sampler's LSCP minor version.
 
-   Compatibility can only be claimed if both rules are true.  The
-   frontend can use the "GET SERVER INFO" (Section 6.6.5) command to get
-   the version of the LSCP specification the sampler complies with.
-
-
-
-
-
-
-
-
-
-
-
 
 
 
 
 
-
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016                [Page 8]
+Schoenebeck            Expires September 12, 2019               [Page 7]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   Compatibility can only be claimed if both rules are true.  The
+   frontend can use the "GET SERVER INFO" (Section 6.6.5) command to get
+   the version of the LSCP specification the sampler complies with.
+
 3.  Introduction
 
    LinuxSampler is a so called software sampler application capable to
@@ -459,7 +408,7 @@
    virtual channels which will be referred in this document as "sampler
    channels".  The channels are in such way virtual as they can be
    connected to an arbitrary MIDI input method and arbitrary MIDI
-   channel (e.g. sampler channel 17 could be connected to an ALSA
+   channel (e.g.  sampler channel 17 could be connected to an ALSA
    sequencer device 64:0 and listening to MIDI channel 1 there).  Each
    sampler channel will be associated with an instance of one of the
    available sampler engines (e.g.  GigEngine, DLSEngine).  The audio
@@ -467,44 +416,6 @@
    output method (ALSA / JACK) and an arbitrary audio output channel
    there.
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016                [Page 9]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 4.  Focus of this protocol
 
    Main focus of this protocol is to provide a way to configure a
@@ -515,52 +426,6 @@
    covered by MIDI or which may at most be handled via MIDI System
    Exclusive Messages.
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 10]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 5.  Communication Overview
 
    There are two distinct methods of communication between a running
@@ -573,6 +438,18 @@
    more effort to be implemented in the front-end application.  The two
    communication methods will be described next.
 
+
+
+
+
+
+
+
+Schoenebeck            Expires September 12, 2019               [Page 8]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
 5.1.  Request/response communication method
 
    This simple communication method is based on TCP [RFC793].  The
@@ -610,13 +487,6 @@
    server they MUST be processed in the order they were received and
    result sets MUST be sent back in the same order.
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 11]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 5.1.1.  Result format
 
    Result set could be one of the following types:
@@ -627,6 +497,15 @@
 
    3.  Error
 
+
+
+
+
+Schoenebeck            Expires September 12, 2019               [Page 9]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    Warning and Error result sets MUST be single line and have the
    following format:
 
@@ -665,14 +544,6 @@
    Empty result set is issued when the server only needed to acknowledge
    the fact that the request was received and it was processed
    successfully and no additional information is available.  This result
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 12]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    set has the following format:
 
       "OK"
@@ -683,6 +554,14 @@
 
       S: "OK"
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 10]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    Single line result sets are command specific.  One example of a
    single line result set is an empty line.  Multi-line result sets are
    command specific and may include one or more lines of information.
@@ -696,19 +575,19 @@
 
       S: "DRIVER: ALSA"
 
-         "CHANNELS: 2"
+      "CHANNELS: 2"
 
-         "SAMPLERATE: 44100"
+      "SAMPLERATE: 44100"
 
-         "ACTIVE: true"
+      "ACTIVE: true"
 
-         "FRAGMENTS: 2"
+      "FRAGMENTS: 2"
 
-         "FRAGMENTSIZE: 128"
+      "FRAGMENTSIZE: 128"
 
-         "CARD: '0,0'"
+      "CARD: '0,0'"
 
-         "."
+      "."
 
    In addition to above mentioned formats, warnings and empty result
    sets MAY be indexed.  In this case, they have the following formats
@@ -721,14 +600,6 @@
    where <index> is command specific and is used to indicate channel
    number that the result set was related to or other integer value.
 
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 13]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    Each line of the result set MUST end with <CRLF>.
 
    Examples:
@@ -739,6 +610,14 @@
 
       C: "CREATE AUDIO_OUTPUT_DEVICE ALSA SAMPLERATE=96000"
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 11]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       S: "WRN[0]:32:Sample rate not supported, using 44100 instead."
 
 5.2.  Subscribe/notify communication method
@@ -777,14 +656,6 @@
    3.  When response is being sent to the client, event MUST be inserted
        in the stream before or after the response, but NOT in the
        middle.  Same is true about the response.  It should never be
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 14]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
        inserted in the middle of the event message as well as any other
        response.
 
@@ -793,6 +664,16 @@
 
       UNSUBSCRIBE <event-id>
 
+
+
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 12]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    where <event-id> will be replace by the respective event that client
    is no longer interested in receiving.  For a list of supported events
    see Section 8.
@@ -830,17 +711,6 @@
    reconnects it MUST resubscribe to all events that it wants to
    receive.
 
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 15]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 6.  Description for control commands
 
    This chapter will describe the available control commands that can be
@@ -850,6 +720,16 @@
    LinuxSampler signals the end of the response by a "." (single dot)
    line.
 
+
+
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 13]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
 6.1.  Ignored lines and comments
 
    White lines, that is lines which only contain space and tabulator
@@ -886,17 +766,6 @@
    retrieve what parameters drivers are offering, how to retrieve their
    possible values, etc.
 
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 16]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 6.2.1.  Getting amount of available audio output drivers
 
    Use the following command to get the number of audio output drivers
@@ -909,6 +778,14 @@
       LinuxSampler will answer by sending the number of audio output
       drivers.
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 14]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    Example:
 
       C: "GET AVAILABLE_AUDIO_OUTPUT_DRIVERS"
@@ -946,13 +823,6 @@
 
    Possible Answers:
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 17]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       LinuxSampler will answer by sending a <CRLF> separated list.  Each
       answer line begins with the information category name followed by
       a colon and then a space character <SP> and finally the info
@@ -965,6 +835,13 @@
 
             character string describing the audio output driver
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 15]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          VERSION -
 
             character string reflecting the driver's version
@@ -984,12 +861,12 @@
 
       S: "DESCRIPTION: Advanced Linux Sound Architecture"
 
-         "VERSION: 1.0"
+      "VERSION: 1.0"
 
-         "PARAMETERS: DRIVER,CHANNELS,SAMPLERATE,ACTIVE,FRAGMENTS,
+      "PARAMETERS: DRIVER,CHANNELS,SAMPLERATE,ACTIVE,FRAGMENTS,
       FRAGMENTSIZE,CARD"
 
-         "."
+      "."
 
 6.2.4.  Getting information about specific audio output driver parameter
 
@@ -1001,14 +878,6 @@
    Where <audio> is the name of the audio output driver as returned by
    the "LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS" (Section 6.2.2) command,
    <prm> a specific parameter name for which information should be
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 18]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    obtained (as returned by the "GET AUDIO_OUTPUT_DRIVER INFO"
    (Section 6.2.3) command) and <deplist> is an optional list of
    parameters on which the sought parameter <prm> depends on, <deplist>
@@ -1021,6 +890,14 @@
 
    Possible Answers:
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 16]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       LinuxSampler will answer by sending a <CRLF> separated list.  Each
       answer line begins with the information category name followed by
       a colon and then a space character <SP> and finally the info
@@ -1056,15 +933,6 @@
          AUDIO_OUTPUT_DEVICE' (Section 6.2.5) command (always returned,
          no matter which driver parameter)
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 19]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       MULTIPLICITY -
 
          either true or false, defines if this parameter allows only one
@@ -1078,6 +946,14 @@
          means the values for fields 'DEFAULT', 'RANGE_MIN', 'RANGE_MAX'
          and 'POSSIBILITIES' might depend on these listed parameters,
          for example assuming that an audio driver (like the ALSA
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 17]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          driver) offers parameters 'card' and 'samplerate' then
          parameter 'samplerate' would depend on 'card' because the
          possible values for 'samplerate' depends on the sound card
@@ -1113,14 +989,6 @@
 
          comma separated list of possible values for this parameter,
          character strings are encapsulated into apostrophes (optionally
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 20]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
          returned, dependent to driver parameter)
 
    The mentioned fields above don't have to be in particular order.
@@ -1131,69 +999,74 @@
 
       S: "DESCRIPTION: sound card to be used"
 
-         "TYPE: STRING"
+      "TYPE: STRING"
+
+      "MANDATORY: false"
 
-         "MANDATORY: false"
 
-         "FIX: true"
 
-         "MULTIPLICITY: false"
+Schoenebeck            Expires September 12, 2019              [Page 18]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
 
-         "DEFAULT: '0,0'"
+      "FIX: true"
 
-         "POSSIBILITIES: '0,0','1,0','2,0'"
+      "MULTIPLICITY: false"
 
-         "."
+      "DEFAULT: '0,0'"
+
+      "POSSIBILITIES: '0,0','1,0','2,0'"
+
+      "."
 
       C: "GET AUDIO_OUTPUT_DRIVER_PARAMETER INFO ALSA SAMPLERATE"
 
       S: "DESCRIPTION: output sample rate in Hz"
 
-         "TYPE: INT"
+      "TYPE: INT"
 
-         "MANDATORY: false"
+      "MANDATORY: false"
 
-         "FIX: false"
+      "FIX: false"
 
-         "MULTIPLICITY: false"
+      "MULTIPLICITY: false"
 
-         "DEPENDS: card"
+      "DEPENDS: card"
 
-         "DEFAULT: 44100"
+      "DEFAULT: 44100"
 
-         "."
+      "."
 
       C: "GET AUDIO_OUTPUT_DRIVER_PARAMETER INFO ALSA SAMPLERATE
       CARD='0,0'"
 
       S: "DESCRIPTION: output sample rate in Hz"
 
+      "TYPE: INT"
 
+      "MANDATORY: false"
 
+      "FIX: false"
 
+      "MULTIPLICITY: false"
 
-Schoenebeck             Expires January 16, 2016               [Page 21]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-         "TYPE: INT"
+      "DEPENDS: card"
 
-         "MANDATORY: false"
+      "DEFAULT: 44100"
 
-         "FIX: false"
+      "RANGE_MIN: 22050"
 
-         "MULTIPLICITY: false"
+      "RANGE_MAX: 96000"
 
-         "DEPENDS: card"
 
-         "DEFAULT: 44100"
 
-         "RANGE_MIN: 22050"
+Schoenebeck            Expires September 12, 2019              [Page 19]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-         "RANGE_MAX: 96000"
 
-         "."
+      "."
 
 6.2.5.  Creating an audio output device
 
@@ -1225,14 +1098,6 @@
          is the numerical ID of the new device, but there are noteworthy
          issue(s) related (e.g. sound card doesn't support given
          hardware parameters and the driver is using fall-back values),
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 22]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
          providing an appropriate warning code and warning message
 
       "ERR:<error-code>:<error-message>" -
@@ -1250,6 +1115,13 @@
 
       S: "OK[1]"
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 20]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
 6.2.6.  Destroying an audio output device
 
    Use the following command to destroy a created output device:
@@ -1282,13 +1154,6 @@
 
    Example:
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 23]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       C: "DESTROY AUDIO_OUTPUT_DEVICE 0"
 
       S: "OK"
@@ -1306,6 +1171,13 @@
 
    Example:
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 21]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       C: "GET AUDIO_OUTPUT_DEVICES"
 
       S: "4"
@@ -1338,13 +1210,6 @@
    output device as e.g. returned by the "LIST AUDIO_OUTPUT_DEVICES"
    (Section 6.2.8) command.
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 24]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    Possible Answers:
 
    LinuxSampler will answer by sending a <CRLF> separated list.  Each
@@ -1361,6 +1226,14 @@
          the "LIST AVAILABLE_AUDIO_OUTPUT_DRIVERS" (Section 6.2.2)
          command
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 22]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       CHANNELS -
 
          amount of audio output channels this device currently offers
@@ -1387,34 +1260,35 @@
 
       S: "DRIVER: ALSA"
 
-         "CHANNELS: 2"
+      "CHANNELS: 2"
 
-         "SAMPLERATE: 44100"
+      "SAMPLERATE: 44100"
 
-         "ACTIVE: true"
+      "ACTIVE: true"
 
+      "FRAGMENTS: 2"
 
+      "FRAGMENTSIZE: 128"
 
+      "CARD: '0,0'"
 
-Schoenebeck             Expires January 16, 2016               [Page 25]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      "."
 
+6.2.10.  Changing settings of audio output devices
+
+   Use the following command to alter a specific setting of a created
+   audio output device:
 
-         "FRAGMENTS: 2"
+      SET AUDIO_OUTPUT_DEVICE_PARAMETER <device-id> <key>=<value>
 
-         "FRAGMENTSIZE: 128"
 
-         "CARD: '0,0'"
 
-         "."
 
-6.2.10.  Changing settings of audio output devices
 
-   Use the following command to alter a specific setting of a created
-   audio output device:
+Schoenebeck            Expires September 12, 2019              [Page 23]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      SET AUDIO_OUTPUT_DEVICE_PARAMETER <device-id> <key>=<value>
 
    Where <device-id> should be replaced by the numerical ID of the audio
    output device as given by the "CREATE AUDIO_OUTPUT_DEVICE"
@@ -1445,18 +1319,6 @@
 
       S: "OK"
 
-
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 26]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 6.2.11.  Getting information about an audio channel
 
    Use the following command to get information about an audio channel:
@@ -1478,6 +1340,12 @@
 
 
 
+
+Schoenebeck            Expires September 12, 2019              [Page 24]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          NAME -
 
             arbitrary character string naming the channel, which doesn't
@@ -1506,50 +1374,51 @@
    driver.  Every audio channel might have its own, additional driver
    and channel specific parameters.
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 27]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    Examples:
 
       C: "GET AUDIO_OUTPUT_CHANNEL INFO 0 0"
 
       S: "NAME: studio monitor left"
 
-         "IS_MIX_CHANNEL: false"
+      "IS_MIX_CHANNEL: false"
 
-         "."
+      "."
 
       C: "GET AUDIO_OUTPUT_CHANNEL INFO 0 1"
 
       S: "NAME: studio monitor right"
 
-         "IS_MIX_CHANNEL: false"
+      "IS_MIX_CHANNEL: false"
 
-         "."
+      "."
 
       C: "GET AUDIO_OUTPUT_CHANNEL INFO 0 2"
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 25]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       S: "NAME: studio monitor left"
 
-         "IS_MIX_CHANNEL: true"
+      "IS_MIX_CHANNEL: true"
 
-         "MIX_CHANNEL_DESTINATION: 1"
+      "MIX_CHANNEL_DESTINATION: 1"
 
-         "."
+      "."
 
       C: "GET AUDIO_OUTPUT_CHANNEL INFO 1 0"
 
       S: "NAME: 'ardour (left)'"
 
-         "IS_MIX_CHANNEL: false"
+      "IS_MIX_CHANNEL: false"
 
-         "JACK_BINDINGS: 'ardour:0'"
+      "JACK_BINDINGS: 'ardour:0'"
 
-         "."
+      "."
 
 6.2.12.  Getting information about specific audio channel parameter
 
@@ -1561,14 +1430,6 @@
    Where <dev-id> is the numerical ID of the audio output device as
    returned by the "CREATE AUDIO_OUTPUT_DEVICE" (Section 6.2.5) or "LIST
    AUDIO_OUTPUT_DEVICES" (Section 6.2.8) command, <chan> the audio
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 28]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    channel number and <param> a specific channel parameter name for
    which information should be obtained (as returned by the "GET
    AUDIO_OUTPUT_CHANNEL INFO" (Section 6.2.11) command).
@@ -1588,6 +1449,15 @@
 
          TYPE -
 
+
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 26]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
             either "BOOL" for boolean value(s) or "INT" for integer
             value(s) or "FLOAT" for dotted number(s) or "STRING" for
             character string(s) (always returned)
@@ -1617,14 +1487,6 @@
             may also appear without (optionally returned, dependent to
             driver and channel parameter)
 
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 29]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
          RANGE_MAX -
 
             defines upper limit of the allowed value range for this
@@ -1644,19 +1506,27 @@
 
    Example:
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 27]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       C: "GET AUDIO_OUTPUT_CHANNEL_PARAMETER INFO 1 0 JACK_BINDINGS"
 
       S: "DESCRIPTION: bindings to other JACK clients"
 
-         "TYPE: STRING"
+      "TYPE: STRING"
 
-         "FIX: false"
+      "FIX: false"
 
-         "MULTIPLICITY: true"
+      "MULTIPLICITY: true"
 
-         "POSSIBILITIES: 'PCM:0','PCM:1','ardour:0','ardour:1'"
+      "POSSIBILITIES: 'PCM:0','PCM:1','ardour:0','ardour:1'"
 
-         "."
+      "."
 
 6.2.13.  Changing settings of audio output channels
 
@@ -1673,14 +1543,6 @@
 
    Possible Answers:
 
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 30]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       "OK" -
 
          in case setting was successfully changed
@@ -1700,6 +1562,14 @@
 
       C: "SET AUDIO_OUTPUT_CHANNEL PARAMETER 0 0 JACK_BINDINGS='PCM:0'"
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 28]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       S: "OK"
 
       C: "SET AUDIO_OUTPUT_CHANNEL PARAMETER 0 0 NAME='monitor left'"
@@ -1729,14 +1599,6 @@
    as the commands for configuring audio output drivers, already
    described in the last chapter.
 
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 31]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    Note: examples in this chapter showing particular parameters of
    drivers are not meant as specification of the drivers' parameters.
    Driver implementations in LinuxSampler might have complete different
@@ -1757,6 +1619,13 @@
       LinuxSampler will answer by sending the number of available MIDI
       input drivers.
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 29]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    Example:
 
       C: "GET AVAILABLE_MIDI_INPUT_DRIVERS"
@@ -1781,18 +1650,6 @@
 
       S: "ALSA,JACK"
 
-
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 32]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 6.3.3.  Getting information about a specific MIDI input driver
 
    Use the following command to get detailed information about a
@@ -1818,6 +1675,13 @@
 
             arbitrary description text about the MIDI input driver
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 30]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          VERSION -
 
             arbitrary character string regarding the driver's version
@@ -1835,19 +1699,11 @@
 
       S: "DESCRIPTION: Advanced Linux Sound Architecture"
 
-         "VERSION: 1.0"
-
-         "PARAMETERS: DRIVER,ACTIVE"
-
-         "."
+      "VERSION: 1.0"
 
+      "PARAMETERS: DRIVER,ACTIVE"
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 33]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
+      "."
 
 6.3.4.  Getting information about specific MIDI input driver parameter
 
@@ -1874,6 +1730,14 @@
    answer line begins with the information category name followed by a
    colon and then a space character <SP> and finally the info character
    string to that info category.  There is information which is always
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 31]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    returned, independent of the given driver parameter and there is
    optional information which is only shown dependent to given driver
    parameter.  At the moment the following information categories are
@@ -1898,13 +1762,6 @@
          MIDI_INPUT_DEVICE' (Section 6.3.5) command (always returned, no
          matter which driver parameter)
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 34]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       FIX -
 
          either true or false, if false then this parameter can be
@@ -1928,6 +1785,15 @@
          driver) offers parameters 'card' and 'samplerate' then
          parameter 'samplerate' would depend on 'card' because the
          possible values for 'samplerate' depends on the sound card
+
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 32]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          which can be chosen by the 'card' parameter (optionally
          returned, dependent to driver parameter)
 
@@ -1953,14 +1819,6 @@
          defines upper limit of the allowed value range for this
          parameter, can be an integer value as well as a dotted number,
          this parameter is often used in conjunction with RANGE_MIN, but
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 35]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
          may also appear without (optionally returned, dependent to
          driver parameter)
 
@@ -1978,17 +1836,25 @@
 
       S: "DESCRIPTION: Whether device is enabled"
 
-         "TYPE: BOOL"
+      "TYPE: BOOL"
 
-         "MANDATORY: false"
+      "MANDATORY: false"
 
-         "FIX: false"
+      "FIX: false"
 
-         "MULTIPLICITY: false"
 
-         "DEFAULT: true"
 
-         "."
+
+Schoenebeck            Expires September 12, 2019              [Page 33]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
+      "MULTIPLICITY: false"
+
+      "DEFAULT: true"
+
+      "."
 
 6.3.5.  Creating a MIDI input device
 
@@ -2008,15 +1874,6 @@
 
    Possible Answers:
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 36]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       "OK[<device-id>]" -
 
          in case the device was successfully created, where <device-id>
@@ -2040,6 +1897,15 @@
 
       S: "OK[0]"
 
+
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 34]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
 6.3.6.  Destroying a MIDI input device
 
    Use the following command to destroy a created MIDI input device:
@@ -2064,15 +1930,6 @@
 
       "ERR:<error-code>:<error-message>" -
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 37]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
          in case it failed, providing an appropriate error code and
          error message
 
@@ -2097,6 +1954,14 @@
 
       C: "GET MIDI_INPUT_DEVICES"
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 35]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       S: "3"
 
 6.3.8.  Getting all created MIDI input device list
@@ -2120,15 +1985,6 @@
 
       S: "1,3"
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 38]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 6.3.9.  Getting current settings of a MIDI input device
 
    Use the following command to get current settings of a specific,
@@ -2154,7 +2010,15 @@
 
          DRIVER -
 
-            identifier of the used MIDI input driver, as e.g. returned
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 36]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
+            identifier of the used MIDI input driver, as e.g.  returned
             by the "LIST AVAILABLE_MIDI_INPUT_DRIVERS" (Section 6.3.2)
             command
 
@@ -2177,17 +2041,9 @@
 
       S: "DRIVER: ALSA"
 
+      "ACTIVE: true"
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 39]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-         "ACTIVE: true"
-
-         "."
+      "."
 
 6.3.10.  Changing settings of MIDI input devices
 
@@ -2210,6 +2066,14 @@
 
       "WRN:<warning-code>:<warning-message>" -
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 37]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          in case setting was changed successfully, but there are
          noteworthy issue(s) related, providing an appropriate warning
          code and warning message
@@ -2233,14 +2097,6 @@
 
    Where <device-id> is the numerical ID of the MIDI input device as
    returned by the "CREATE MIDI_INPUT_DEVICE" (Section 6.3.5) or "LIST
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 40]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    MIDI_INPUT_DEVICES" (Section 6.3.8) command and <midi-port> the MIDI
    input port number.
 
@@ -2266,9 +2122,17 @@
 
       S: "NAME: 'Masterkeyboard'"
 
-         "ALSA_SEQ_BINDINGS: '64:0'"
 
-         "."
+
+
+Schoenebeck            Expires September 12, 2019              [Page 38]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
+      "ALSA_SEQ_BINDINGS: '64:0'"
+
+      "."
 
 6.3.12.  Getting information about specific MIDI port parameter
 
@@ -2289,14 +2153,6 @@
       LinuxSampler will answer by sending a <CRLF> separated list.  Each
       answer line begins with the information category name followed by
       a colon and then a space character <SP> and finally the info
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 41]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       character string to that info category.  There is information
       which is always returned, independently of the given channel
       parameter and there is optional information which are only shown
@@ -2321,6 +2177,15 @@
 
       MULTIPLICITY -
 
+
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 39]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          either true or false, defines if this parameter allows only one
          value or a list of values, where true means multiple values and
          false only a single value allowed (always returned)
@@ -2345,14 +2210,6 @@
 
          comma separated list of possible values for this parameter,
          character strings are encapsulated into apostrophes (optionally
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 42]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
          returned, dependent to device and port parameter)
 
    The mentioned fields above don't have to be in particular order.
@@ -2363,15 +2220,27 @@
 
       S: "DESCRIPTION: bindings to other ALSA sequencer clients"
 
-         "TYPE: STRING"
+      "TYPE: STRING"
+
+      "FIX: false"
+
+      "MULTIPLICITY: true"
+
+      "POSSIBILITIES: '64:0','68:0','68:1'"
+
+      "."
+
+
+
+
 
-         "FIX: false"
 
-         "MULTIPLICITY: true"
 
-         "POSSIBILITIES: '64:0','68:0','68:1'"
 
-         "."
+Schoenebeck            Expires September 12, 2019              [Page 40]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
 
 6.3.13.  Changing settings of MIDI input ports
 
@@ -2400,15 +2269,6 @@
          noteworthy issue(s) related, providing an appropriate warning
          code and warning message
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 43]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       "ERR:<error-code>:<error-message>" -
 
          in case it failed, providing an appropriate error code and
@@ -2430,6 +2290,14 @@
    channels, associate a sampler channel with a sampler engine, load
    instruments and connect sampler channels to MIDI and audio devices.
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 41]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
 6.4.1.  Loading an instrument
 
    An instrument file can be loaded and assigned to a sampler channel by
@@ -2457,14 +2325,6 @@
    (Section 6.4.10) command can be used to obtain loading progress from
    INSTRUMENT_STATUS field.  LOAD command will perform sanity checks
    such as making sure that the file could be read and it is of a proper
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 44]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    format and SHOULD return ERR and SHOULD not launch the background
    process should any errors be detected at that point.
 
@@ -2487,6 +2347,13 @@
          in case it failed, providing an appropriate error code and
          error message
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 42]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    Example (Unix):
 
       C: LOAD INSTRUMENT '/home/joe/gigs/cello.gig' 0 0
@@ -2513,14 +2380,6 @@
    be assigned to.  This command should be issued after adding a new
    sampler channel and before any other control commands on the new
    sampler channel.  It can also be used to change the engine type of a
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 45]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    sampler channel.  This command has (currently) no way to define or
    force if a new engine instance should be created and assigned to the
    given sampler channel or if an already existing instance of that
@@ -2543,6 +2402,14 @@
          in case it failed, providing an appropriate error code and
          error message
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 43]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    Example:
 
 
@@ -2566,17 +2433,6 @@
 
       S: "12"
 
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 46]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 6.4.4.  Getting all created sampler channel list
 
    The number of sampler channels can change on runtime.  To get the
@@ -2603,6 +2459,13 @@
 
       ADD CHANNEL
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 44]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    This will increment the sampler channel count by one and the new
    sampler channel will be appended to the end of the sampler channel
    list.  The front-end should send the respective, related commands
@@ -2624,15 +2487,6 @@
 
       "WRN:<warning-code>:<warning-message>" -
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 47]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
          in case a new channel was added successfully, but there are
          noteworthy issue(s) related, providing an appropriate warning
          code and warning message
@@ -2661,6 +2515,13 @@
 
       "OK" -
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 45]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          in case the given sampler channel could be removed
 
       "WRN:<warning-code>:<warning-message>" -
@@ -2678,17 +2539,6 @@
 
 
 
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 48]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 6.4.7.  Getting amount of available engines
 
    The front-end can ask for the number of available engines by sending
@@ -2721,6 +2571,13 @@
       can consist of lower and upper cases, digits and underlines ("_"
       character).
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 46]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    Example:
 
       C: "LIST AVAILABLE_ENGINES"
@@ -2737,14 +2594,6 @@
    Where <engine-name> is an engine name as obtained by the "LIST
    AVAILABLE_ENGINES" (Section 6.4.8) command.
 
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 49]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    Possible Answers:
 
       LinuxSampler will answer by sending a <CRLF> separated list.  Each
@@ -2772,34 +2621,32 @@
 
       S: "DESCRIPTION: GigaSampler Format Engine"
 
-         "VERSION: 1.110"
+      "VERSION: 1.110"
 
-         "."
+      "."
 
       C: "GET ENGINE INFO sf2"
 
-      S: "DESCRIPTION: SoundFont Format Engine"
-
-         "VERSION: 1.4"
 
-         "."
 
-      C: "GET ENGINE INFO sfz"
+Schoenebeck            Expires September 12, 2019              [Page 47]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      S: "DESCRIPTION: SFZ Format Engine"
 
-         "VERSION: 1.11"
+      S: "DESCRIPTION: SoundFont Format Engine"
 
-         "."
+      "VERSION: 1.4"
 
+      "."
 
+      C: "GET ENGINE INFO sfz"
 
+      S: "DESCRIPTION: SFZ Format Engine"
 
+      "VERSION: 1.11"
 
-Schoenebeck             Expires January 16, 2016               [Page 50]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
+      "."
 
 6.4.10.  Getting sampler channel information
 
@@ -2835,6 +2682,14 @@
             signal, "-1" if there's no device connected to this sampler
             channel
 
+
+
+
+Schoenebeck            Expires September 12, 2019              [Page 48]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          AUDIO_OUTPUT_CHANNELS -
 
             number of output channels the sampler channel offers
@@ -2849,14 +2704,6 @@
             device and the engine's output channel 1 is routed to the
             channel 3 of the audio output device
 
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 51]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
          INSTRUMENT_FILE -
 
             the file name of the loaded instrument, "NONE" if there's no
@@ -2892,6 +2739,13 @@
             commands, "-1" if there's no device connected to this
             sampler channel
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 49]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
             Should not be used anymore as of LSCP v1.6 and younger.
             This field is currently only preserved for backward
             compatibility.
@@ -2904,15 +2758,6 @@
 
             DEPRECATED: THIS FIELD WILL DISAPPEAR!
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 52]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
             port number of the MIDI input device (in case a MIDI device
             was already assigned to the sampler channel)
 
@@ -2950,6 +2795,13 @@
 
          MIDI_INSTRUMENT_MAP -
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 50]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
             Determines to which MIDI instrument map this sampler channel
             is assigned to.  Read chapter "SET CHANNEL
             MIDI_INSTRUMENT_MAP" (Section 6.4.27) for a list of possible
@@ -2959,51 +2811,52 @@
 
    Example:
 
+      C: "GET CHANNEL INFO 34"
 
+      S: "ENGINE_NAME: gig"
 
+      "VOLUME: 1.0"
 
+      "AUDIO_OUTPUT_DEVICE: 0"
 
+      "AUDIO_OUTPUT_CHANNELS: 2"
 
-Schoenebeck             Expires January 16, 2016               [Page 53]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      "AUDIO_OUTPUT_ROUTING: 0,1"
 
+      "INSTRUMENT_FILE: /home/joe/FazioliPiano.gig"
 
-      C: "GET CHANNEL INFO 34"
+      "INSTRUMENT_NR: 0"
 
-      S: "ENGINE_NAME: gig"
+      "INSTRUMENT_NAME: Fazioli Piano"
 
-         "VOLUME: 1.0"
+      "INSTRUMENT_STATUS: 100"
 
-         "AUDIO_OUTPUT_DEVICE: 0"
+      "MIDI_INPUT_DEVICE: 0"
 
-         "AUDIO_OUTPUT_CHANNELS: 2"
+      "MIDI_INPUT_PORT: 0"
 
-         "AUDIO_OUTPUT_ROUTING: 0,1"
+      "MIDI_INPUT_CHANNEL: 5"
 
-         "INSTRUMENT_FILE: /home/joe/FazioliPiano.gig"
+      "VOLUME: 1.0"
 
-         "INSTRUMENT_NR: 0"
+      "MUTE: false"
 
-         "INSTRUMENT_NAME: Fazioli Piano"
+      "SOLO: false"
 
-         "INSTRUMENT_STATUS: 100"
+      "MIDI_INSTRUMENT_MAP: NONE"
+
+      "."
 
-         "MIDI_INPUT_DEVICE: 0"
 
-         "MIDI_INPUT_PORT: 0"
 
-         "MIDI_INPUT_CHANNEL: 5"
 
-         "VOLUME: 1.0"
 
-         "MUTE: false"
 
-         "SOLO: false"
 
-         "MIDI_INSTRUMENT_MAP: NONE"
+Schoenebeck            Expires September 12, 2019              [Page 51]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-         "."
 
 6.4.11.  Current number of active voices
 
@@ -3018,13 +2871,6 @@
 
    Possible Answers:
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 54]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       LinuxSampler will answer by returning the number of active voices
       on that channel.
 
@@ -3061,6 +2907,13 @@
 
       GET CHANNEL BUFFER_FILL BYTES <sampler-channel>
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 52]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    to get the fill state in bytes or
 
       GET CHANNEL BUFFER_FILL PERCENTAGE <sampler-channel>
@@ -3072,15 +2925,6 @@
 
    Possible Answers:
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 55]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       LinuxSampler will either answer by returning a comma separated
       string with the fill state of all disk stream buffers on that
       channel or an empty line if there are no active disk streams or
@@ -3111,31 +2955,29 @@
    The front-end can set the audio output device on a specific sampler
    channel by sending the following command:
 
-      SET CHANNEL AUDIO_OUTPUT_DEVICE <sampler-channel>
-      <audio-device-id>
+      SET CHANNEL AUDIO_OUTPUT_DEVICE <sampler-channel> <audio-device-
+      id>
 
    Where <sampler-channel> is the respective sampler channel number as
    returned by the "ADD CHANNEL" (Section 6.4.5) or "LIST CHANNELS"
    (Section 6.4.4) command and <audio-device-id> is the numerical ID of
    the audio output device as given by the "CREATE AUDIO_OUTPUT_DEVICE"
-   (Section 6.2.5) or "LIST AUDIO_OUTPUT_DEVICES" (Section 6.2.8)
-   command.
 
-   Possible Answers:
-
-      "OK" -
-
-         on success
 
 
+Schoenebeck            Expires September 12, 2019              [Page 53]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   (Section 6.2.5) or "LIST AUDIO_OUTPUT_DEVICES" (Section 6.2.8)
+   command.
 
+   Possible Answers:
 
-Schoenebeck             Expires January 16, 2016               [Page 56]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      "OK" -
 
+         on success
 
       "WRN:<warning-code>:<warning-message>" -
 
@@ -3177,21 +3019,19 @@
          related, providing an appropriate warning code and warning
          message
 
-      "ERR:<error-code>:<error-message>" -
-
-         in case it failed, providing an appropriate error code and
-         error message
-
-   Examples:
 
 
+Schoenebeck            Expires September 12, 2019              [Page 54]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+      "ERR:<error-code>:<error-message>" -
 
-Schoenebeck             Expires January 16, 2016               [Page 57]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+         in case it failed, providing an appropriate error code and
+         error message
 
+   Examples:
 
 
 
@@ -3234,20 +3074,18 @@
 
       "ERR:<error-code>:<error-message>" -
 
-         in case it failed, providing an appropriate error code and
-         error message
-
-   Examples:
-
 
 
 
+Schoenebeck            Expires September 12, 2019              [Page 55]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-Schoenebeck             Expires January 16, 2016               [Page 58]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+         in case it failed, providing an appropriate error code and
+         error message
 
+   Examples:
 
 
 
@@ -3293,17 +3131,16 @@
 
       C: "ADD CHANNEL MIDI_INPUT 1 0"
 
-      S: "OK"
-
-      C: "ADD CHANNEL MIDI_INPUT 1 1 1"
 
 
+Schoenebeck            Expires September 12, 2019              [Page 56]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-Schoenebeck             Expires January 16, 2016               [Page 59]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      S: "OK"
 
+      C: "ADD CHANNEL MIDI_INPUT 1 1 1"
 
       S: "OK"
 
@@ -3349,18 +3186,19 @@
          issue(s) related, providing an appropriate warning code and
          warning message
 
-      "ERR:<error-code>:<error-message>" -
-
-         in case it failed, providing an appropriate error code and
-         error message
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 60]
+Schoenebeck            Expires September 12, 2019              [Page 57]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+      "ERR:<error-code>:<error-message>" -
+
+         in case it failed, providing an appropriate error code and
+         error message
+
    Examples:
 
       C: "REMOVE CHANNEL MIDI_INPUT 0"
@@ -3404,18 +3242,17 @@
 
       C: "LIST CHANNEL MIDI_INPUTS 0"
 
-      S: "{0,0},{1,3},{2,0}"
-
-   Since:
 
 
 
+Schoenebeck            Expires September 12, 2019              [Page 58]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-Schoenebeck             Expires January 16, 2016               [Page 61]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      S: "{0,0},{1,3},{2,0}"
 
+   Since:
 
       Introduced with LSCP v1.6
 
@@ -3462,17 +3299,15 @@
 
 
 
-   Deprecated:
 
 
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 62]
+Schoenebeck            Expires September 12, 2019              [Page 59]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   Deprecated:
+
       Should not be used anymore as of LSCP v1.6 and younger.  This
       command is currently only preserved for backward compatibility.
 
@@ -3522,13 +3357,9 @@
 
 
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 63]
+Schoenebeck            Expires September 12, 2019              [Page 60]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
    Deprecated:
@@ -3576,16 +3407,16 @@
          related, providing an appropriate warning code and warning
          message
 
+      "ERR:<error-code>:<error-message>" -
 
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 64]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
 
+Schoenebeck            Expires September 12, 2019              [Page 61]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      "ERR:<error-code>:<error-message>" -
 
          in case it failed, providing an appropriate error code and
          error message
@@ -3634,14 +3465,14 @@
 
    Examples:
 
+      C: "SET CHANNEL MIDI_INPUT_CHANNEL 0 0"
+
 
 
-Schoenebeck             Expires January 16, 2016               [Page 65]
+Schoenebeck            Expires September 12, 2019              [Page 62]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      C: "SET CHANNEL MIDI_INPUT_CHANNEL 0 0"
 
       S: "OK"
 
@@ -3687,20 +3518,18 @@
    The front-end can mute/unmute a specific sampler channel by sending
    the following command:
 
+      SET CHANNEL MUTE <sampler-channel> <mute>
 
+   Where <sampler-channel> is the respective sampler channel number as
+   returned by the "ADD CHANNEL" (Section 6.4.5) or "LIST CHANNELS"
 
 
 
-
-Schoenebeck             Expires January 16, 2016               [Page 66]
+Schoenebeck            Expires September 12, 2019              [Page 63]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-      SET CHANNEL MUTE <sampler-channel> <mute>
-
-   Where <sampler-channel> is the respective sampler channel number as
-   returned by the "ADD CHANNEL" (Section 6.4.5) or "LIST CHANNELS"
    (Section 6.4.4) command and <mute> should be replaced either by "1"
    to mute the channel or "0" to unmute the channel.
 
@@ -3743,22 +3572,20 @@
 
          on success
 
+      "WRN:<warning-code>:<warning-message>" -
 
+         if the channel was soloed/unsoloed, but there are noteworthy
+         issue(s) related, providing an appropriate warning code and
+         warning message
 
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 67]
+Schoenebeck            Expires September 12, 2019              [Page 64]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-      "WRN:<warning-code>:<warning-message>" -
-
-         if the channel was soloed/unsoloed, but there are noteworthy
-         issue(s) related, providing an appropriate warning code and
-         warning message
-
       "ERR:<error-code>:<error-message>" -
 
          in case it failed, providing an appropriate error code and
@@ -3802,18 +3629,18 @@
    Read chapter "MIDI Instrument Mapping" (Section 6.7) for details
    regarding MIDI instrument mapping.
 
+   Possible Answers:
 
+      "OK" -
 
-Schoenebeck             Expires January 16, 2016               [Page 68]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+         on success
 
 
-   Possible Answers:
 
-      "OK" -
+Schoenebeck            Expires September 12, 2019              [Page 65]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-         on success
 
       "ERR:<error-code>:<error-message>" -
 
@@ -3842,29 +3669,38 @@
    described in chapter "Character Set and Escape Sequences
    (Section 7.1)".
 
-   By default, that is as initial routing, the effect send's audio
-   channels are automatically routed to the last audio channels of the
-   sampler channel's audio output device, that way you can i.e. first
-   increase the amount of audio channels on the audio output device for
-   having dedicated effect send output channels and when "CREATE
-   FX_SEND" is called, those channels will automatically be picked.  You
-   can alter the destination channels however with "SET FX_SEND
-   AUDIO_OUTPUT_CHANNEL" (Section 6.4.34).
+   Note: there are two possible approaches to apply audio effects with
+   FX sends: you can either use a) internal effects or b) external
+   effects.  By default, that is as initial routing, effect sends are
+   automatically routed directly to the sampler channel's audio output
+   device and the effect send's audio channels are by default
+   automatically routed to the last audio channels of that audio output
+   device (for the purpose of applying effects externally that is, e.g.
+   by using another application), that way you can i.e. first increase
+   the amount of audio channels on the audio output device for having
+   dedicated effect send output channels and when "CREATE FX_SEND" is
+   called, those channels will automatically be picked.  You can alter
+   the destination channels however with "SET FX_SEND
+   AUDIO_OUTPUT_CHANNEL" (Section 6.4.34).  If your intention is rather
+   to use internal effects instead of external effects, then you first
+   need to load those internal effects (Section 6.11) and then assign
+   the FX sends to the desired internal effect by sending "SET FX_SEND
+   EFFECT" (Section 6.4.35).
 
    Note: Create effect sends on a sampler channel only when needed,
    because having effect sends on a sampler channel will decrease
    runtime performance, because for implementing channel effect sends,
-   separate (sampler channel local) audio buffers are needed to render
-   and mix the voices and route the audio signal afterwards to the
-   master outputs and effect send outputs (along with their respective
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 69]
+Schoenebeck            Expires September 12, 2019              [Page 66]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   separate (sampler channel local) audio buffers are needed to render
+   and mix the voices and route the audio signal afterwards to the
+   master outputs and effect send outputs (along with their respective
    effect send levels).  A sampler channel without effect sends however
    can mix its voices directly into the audio output devices's audio
    buffers and is thus faster.
@@ -3879,7 +3715,7 @@
 
       "ERR:<error-code>:<error-message>" -
 
-         when a new effect send could not be added, i.e. due to invalid
+         when a new effect send could not be added, i.e.  due to invalid
          parameters
 
    Examples:
@@ -3910,17 +3746,16 @@
 
       "OK" -
 
-         on success
-
-
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 70]
+Schoenebeck            Expires September 12, 2019              [Page 67]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+         on success
+
       "ERR:<error-code>:<error-message>" -
 
          in case it failed, providing an appropriate error code and
@@ -3970,11 +3805,9 @@
 
 
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 71]
+Schoenebeck            Expires September 12, 2019              [Page 68]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
       The sampler will answer by returning a comma separated list with
@@ -4023,18 +3856,16 @@
             a value between 0 and 127 reflecting the MIDI controller
             which is able to modify the effect send's send level
 
+         LEVEL -
 
 
 
 
-
-Schoenebeck             Expires January 16, 2016               [Page 72]
+Schoenebeck            Expires September 12, 2019              [Page 69]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-         LEVEL -
-
             optionally dotted number reflecting the effect send's
             current send level (where a value < 1.0 means attenuation
             and a value > 1.0 means amplification)
@@ -4067,37 +3898,37 @@
 
       S: "NAME: Reverb Send"
 
-         "MIDI_CONTROLLER: 91"
+      "MIDI_CONTROLLER: 91"
 
-         "LEVEL: 0.3"
+      "LEVEL: 0.3"
 
-         "AUDIO_OUTPUT_ROUTING: 2,3"
+      "AUDIO_OUTPUT_ROUTING: 2,3"
 
-         "EFFECT: NONE"
+      "EFFECT: NONE"
 
-         "."
+      "."
 
       C: "GET FX_SEND INFO 0 1"
 
       S: "NAME: Delay Send (Internal)"
 
+      "MIDI_CONTROLLER: 93"
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 73]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
 
+Schoenebeck            Expires September 12, 2019              [Page 70]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-         "MIDI_CONTROLLER: 93"
 
-         "LEVEL: 0.51"
+      "LEVEL: 0.51"
 
-         "AUDIO_OUTPUT_ROUTING: 1,2"
+      "AUDIO_OUTPUT_ROUTING: 1,2"
 
-         "EFFECT: 2,0"
+      "EFFECT: 2,0"
 
-         "."
+      "."
 
 6.4.33.  Changing effect send's name
 
@@ -4133,23 +3964,19 @@
 
       S: "OK"
 
+6.4.34.  Altering effect send's audio routing
 
+   The front-end can alter the destination of an effect send's audio
+   channel on a specific sampler channel by sending the following
+   command:
 
 
 
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 74]
+Schoenebeck            Expires September 12, 2019              [Page 71]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-6.4.34.  Altering effect send's audio routing
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-   The front-end can alter the destination of an effect send's audio
-   channel on a specific sampler channel by sending the following
-   command:
 
       SET FX_SEND AUDIO_OUTPUT_CHANNEL <sampler-chan> <fx-send-id>
       <audio-src> <audio-dst>
@@ -4160,11 +3987,10 @@
    entity as returned by the "CREATE FX_SEND" (Section 6.4.28) or "LIST
    FX_SENDS" (Section 6.4.31) command, <audio-src> is the numerical ID
    of the effect send's audio channel which should be rerouted and
-   <audio-dst> is the numerical ID of the audio channel of the selected
-   audio output device where <audio-src> 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.
+   <audio-dst> is the numerical ID of either a) the audio output channel
+   of the sampler channel's audio output device (i.e. if external effect
+   shall be applied) or b) of the audio input channel of an internal
+   effect assigned to the FX send where <audio-src> should be routed to.
 
    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
@@ -4192,15 +4018,6 @@
 
       "ERR:<error-code>:<error-message>" -
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 75]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
          in case it failed, providing an appropriate error code and
          error message
 
@@ -4210,10 +4027,17 @@
 
       S: "OK"
 
+
+
+Schoenebeck            Expires September 12, 2019              [Page 72]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
 6.4.35.  Assigning destination effect to an effect send
 
-   The front-end can (re-)assign a destination effect to an effect send
-   by sending the following command:
+   The front-end can (re-)assign an internal destination effect to an
+   effect send by sending the following command:
 
       SET FX_SEND EFFECT <sampler-chan> <fx-send-id> <effect-chain>
       <chain-pos>
@@ -4229,6 +4053,14 @@
    chain position in the effect chain which hosts the actual destination
    effect.
 
+   Note: This command MUST NOT be used if you want to apply audio
+   effects externally!  By default FX sends are routed directly to the
+   audio output device for that purpose.  You can also revert this
+   command later on by sending "REMOVE FX_SEND EFFECT" (Section 6.4.36),
+   which will cause the FX send to be routed directly to the sampler
+   channel's audio output device instead (i.e. for using external
+   effects instead of internal effects).
+
    Possible Answers:
 
       "OK" -
@@ -4252,9 +4084,10 @@
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 76]
+
+Schoenebeck            Expires September 12, 2019              [Page 73]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
 6.4.36.  Removing destination effect from an effect send
@@ -4308,9 +4141,9 @@
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 77]
+Schoenebeck            Expires September 12, 2019              [Page 74]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
    controller which shall be able to modify the effect send's send
@@ -4364,9 +4197,9 @@
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 78]
+Schoenebeck            Expires September 12, 2019              [Page 75]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
       "WRN:<warning-code>:<warning-message>" -
@@ -4420,9 +4253,9 @@
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 79]
+Schoenebeck            Expires September 12, 2019              [Page 76]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
    CAUTION: This command is provided for implementations of virtual MIDI
@@ -4476,9 +4309,9 @@
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 80]
+Schoenebeck            Expires September 12, 2019              [Page 77]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
    Examples:
@@ -4528,15 +4361,16 @@
 
       UNSUBSCRIBE <event-id>
 
-   Where <event-id> will be replaced by the respective event that client
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 81]
+
+Schoenebeck            Expires September 12, 2019              [Page 78]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   Where <event-id> will be replaced by the respective event that client
    doesn't want to receive anymore.
 
    Possible Answers:
@@ -4584,15 +4418,16 @@
 
          on syntax error, e.g. non boolean value
 
-   Examples:
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 82]
+Schoenebeck            Expires September 12, 2019              [Page 79]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   Examples:
+
 
 
 6.5.4.  Close client connection
@@ -4640,14 +4475,14 @@
 
       GET TOTAL_STREAM_COUNT
 
-   Possible Answers:
-
 
 
-Schoenebeck             Expires January 16, 2016               [Page 83]
+Schoenebeck            Expires September 12, 2019              [Page 80]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
 
+   Possible Answers:
 
       LinuxSampler will answer by returning the number of all active
       disk streams on the sampler.
@@ -4669,9 +4504,9 @@
 
 
 
-6.6.5.  General sampler informations
+6.6.5.  General sampler information
 
-   The client can ask for general informations about the LinuxSampler
+   The client can ask for general information about the LinuxSampler
    instance by sending the following command:
 
       GET SERVER INFO
@@ -4698,11 +4533,9 @@
 
 
 
-
-
-Schoenebeck             Expires January 16, 2016               [Page 84]
+Schoenebeck            Expires September 12, 2019              [Page 81]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
          PROTOCOL_VERSION -
@@ -4725,13 +4558,13 @@
       S: "DESCRIPTION: LinuxSampler - modular, streaming capable
       sampler"
 
-         "VERSION: 1.0.0.svn23"
+      "VERSION: 1.0.0.svn23"
 
-         "PROTOCOL_VERSION: 1.5"
+      "PROTOCOL_VERSION: 1.5"
 
-         "INSTRUMENTS_DB_SUPPORT: no"
+      "INSTRUMENTS_DB_SUPPORT: no"
 
-         "."
+      "."
 
 6.6.6.  Getting global volume attenuation
 
@@ -4756,9 +4589,9 @@
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 85]
+Schoenebeck            Expires September 12, 2019              [Page 82]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
 6.6.7.  Setting global volume attenuation
@@ -4812,9 +4645,9 @@
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 86]
+Schoenebeck            Expires September 12, 2019              [Page 83]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
 6.6.9.  Setting global voice limit
@@ -4868,9 +4701,9 @@
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 87]
+Schoenebeck            Expires September 12, 2019              [Page 84]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
    The disk stream limit setting defines how many disk streams should
@@ -4920,15 +4753,16 @@
    The MIDI protocol provides a way to switch between instruments by
    sending so called MIDI bank select and MIDI program change messages
    which are essentially just numbers.  The following commands allow to
-   actually map arbitrary MIDI bank select / program change numbers with
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 88]
+
+Schoenebeck            Expires September 12, 2019              [Page 85]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   actually map arbitrary MIDI bank select / program change numbers with
    real instruments.
 
    The sampler allows to manage an arbitrary amount of MIDI instrument
@@ -4975,15 +4809,17 @@
 
       "ERR:<error-code>:<error-message>" -
 
-         when a new map could not be created, which might never occur in
-         practice
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 89]
+
+Schoenebeck            Expires September 12, 2019              [Page 86]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
 
+         when a new map could not be created, which might never occur in
+         practice
 
    Examples:
 
@@ -5030,16 +4866,15 @@
 
       S: "OK"
 
-      C: "REMOVE MIDI_INSTRUMENT_MAP ALL"
-
 
 
 
-
-Schoenebeck             Expires January 16, 2016               [Page 90]
+Schoenebeck            Expires September 12, 2019              [Page 87]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
 
+      C: "REMOVE MIDI_INSTRUMENT_MAP ALL"
 
       S: "OK"
 
@@ -5087,16 +4922,16 @@
 
       GET MIDI_INSTRUMENT_MAP INFO <map>
 
-   Where <map> is the numerical ID of the map the front-end is
-   interested in as returned by the "LIST MIDI_INSTRUMENT_MAPS"
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 91]
+Schoenebeck            Expires September 12, 2019              [Page 88]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   Where <map> is the numerical ID of the map the front-end is
+   interested in as returned by the "LIST MIDI_INSTRUMENT_MAPS"
    (Section 6.7.4) command.
 
    Possible Answers:
@@ -5128,9 +4963,9 @@
 
       S: "NAME: Standard Map"
 
-         "DEFAULT: true"
+      "DEFAULT: true"
 
-         "."
+      "."
 
 6.7.6.  Renaming a MIDI instrument map
 
@@ -5142,17 +4977,18 @@
    Where <map> is the numerical ID of the map and <name> the new custom
    name of the map, which does not have to be unique (name MUST be
    encapsulated into apostrophes and supports escape sequences as
-   described in chapter "Character Set and Escape Sequences
-   (Section 7.1)").
 
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 92]
+Schoenebeck            Expires September 12, 2019              [Page 89]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   described in chapter "Character Set and Escape Sequences
+   (Section 7.1)").
+
    Possible Answers:
 
       "OK" -
@@ -5199,16 +5035,15 @@
 
       "ON_DEMAND" -
 
-         The instrument will be loaded when needed, that is when
-         demanded by at least one sampler channel.  It will immediately
-
 
 
-Schoenebeck             Expires January 16, 2016               [Page 93]
+Schoenebeck            Expires September 12, 2019              [Page 90]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+         The instrument will be loaded when needed, that is when
+         demanded by at least one sampler channel.  It will immediately
          be freed from memory when not needed by any sampler channel
          anymore.
 
@@ -5255,16 +5090,16 @@
    this, in case the frontend shows the load modes of entries, the
    frontend should retrieve the actual mode by i.e. sending "GET
    MIDI_INSTRUMENT INFO" (Section 6.7.11) command(s).  Finally the
-   OPTIONAL <name> argument allows to set a custom name (encapsulated
-   into apostrophes, supporting escape sequences as described in chapter
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 94]
+Schoenebeck            Expires September 12, 2019              [Page 91]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   OPTIONAL <name> argument allows to set a custom name (encapsulated
+   into apostrophes, supporting escape sequences as described in chapter
    "Character Set and Escape Sequences (Section 7.1)") for the mapping
    entry, useful for frontends for displaying an appropriate name for
    mapped instruments (using "GET MIDI_INSTRUMENT INFO"
@@ -5311,15 +5146,15 @@
       C: "MAP MIDI_INSTRUMENT 0 0 0 gig '/usr/share/piano.gig' 0 1.0
       'Normal Piano'"
 
-      S: "OK"
-
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 95]
+Schoenebeck            Expires September 12, 2019              [Page 92]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
 
+      S: "OK"
 
       C: "MAP MIDI_INSTRUMENT 0 1 0 gig '/usr/share/piano.gig' 0 0.25
       'Silent Piano'"
@@ -5367,16 +5202,17 @@
 
    Where <map> is the numeric ID of the MIDI instrument map.
 
-   The front-end can query a list of all currently existing entries of
-   all MIDI instrument maps by sending the following command:
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 96]
+Schoenebeck            Expires September 12, 2019              [Page 93]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   The front-end can query a list of all currently existing entries of
+   all MIDI instrument maps by sending the following command:
+
       LIST MIDI_INSTRUMENTS ALL
 
    Possible Answers:
@@ -5387,7 +5223,7 @@
       single line.  Each triple just reflects the key of the respective
       map entry, thus subsequent "GET MIDI_INSTRUMENT INFO"
       (Section 6.7.11) command(s) are necessary to retrieve detailed
-      informations about each entry.
+      information about each entry.
 
    Example:
 
@@ -5425,12 +5261,9 @@
 
 
 
-
-
-
-Schoenebeck             Expires January 16, 2016               [Page 97]
+Schoenebeck            Expires September 12, 2019              [Page 94]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
 6.7.11.  Get current settings of MIDI instrument map entry
@@ -5460,7 +5293,7 @@
          name shall be used by frontends for displaying a name for this
          mapped instrument.  It can be set and changed with the "MAP
          MIDI_INSTRUMENT" (Section 6.7.7) command and does not have to
-         be unique. (note that this character string may contain escape
+         be unique.  (note that this character string may contain escape
          sequences (Section 7.1))
 
       "ENGINE_NAME" -
@@ -5480,15 +5313,16 @@
 
          Name of the loaded instrument as reflected by its file.  In
          contrast to the "NAME" field, the "INSTRUMENT_NAME" field
-         cannot be changed (note that this character string may contain
 
 
 
-Schoenebeck             Expires January 16, 2016               [Page 98]
+
+Schoenebeck            Expires September 12, 2019              [Page 95]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+         cannot be changed (note that this character string may contain
          escape sequences (Section 7.1)).
 
       "LOAD_MODE" -
@@ -5510,19 +5344,19 @@
 
       S: "NAME: Drums for Foo Song"
 
-         "ENGINE_NAME: GigEngine"
+      "ENGINE_NAME: GigEngine"
 
-         "INSTRUMENT_FILE: /usr/share/joesdrumkit.gig"
+      "INSTRUMENT_FILE: /usr/share/joesdrumkit.gig"
 
-         "INSTRUMENT_NR: 0"
+      "INSTRUMENT_NR: 0"
 
-         "INSTRUMENT_NAME: Joe's Drumkit"
+      "INSTRUMENT_NAME: Joe's Drumkit"
 
-         "LOAD_MODE: PERSISTENT"
+      "LOAD_MODE: PERSISTENT"
 
-         "VOLUME: 1.0"
+      "VOLUME: 1.0"
 
-         "."
+      "."
 
 6.7.12.  Clear MIDI instrument map
 
@@ -5539,10 +5373,9 @@
 
 
 
-
-Schoenebeck             Expires January 16, 2016               [Page 99]
+Schoenebeck            Expires September 12, 2019              [Page 96]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
       CLEAR MIDI_INSTRUMENTS ALL
@@ -5596,9 +5429,9 @@
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 100]
+Schoenebeck            Expires September 12, 2019              [Page 97]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
       "OK" -
@@ -5652,9 +5485,9 @@
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 101]
+Schoenebeck            Expires September 12, 2019              [Page 98]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
 6.8.3.  Getting amount of instrument directories
@@ -5708,9 +5541,9 @@
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 102]
+Schoenebeck            Expires September 12, 2019              [Page 99]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
    Example:
@@ -5764,9 +5597,9 @@
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 103]
+Schoenebeck            Expires September 12, 2019             [Page 100]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
    Example:
@@ -5776,11 +5609,11 @@
       S: "DESCRIPTION: Piano collection of instruments in GigaSampler
       format."
 
-         "CREATED: 2007-02-05 10:23:12"
+      "CREATED: 2007-02-05 10:23:12"
 
-         "MODIFIED: 2007-04-07 12:50:21"
+      "MODIFIED: 2007-04-07 12:50:21"
 
-         "."
+      "."
 
 6.8.6.  Renaming an instrument directory
 
@@ -5815,17 +5648,15 @@
    The front-end can move a specific instrument directory by sending the
    following command:
 
+      MOVE DB_INSTRUMENT_DIRECTORY <dir> <dst>
 
 
 
 
-
-Schoenebeck             Expires January 16, 2016              [Page 104]
+Schoenebeck            Expires September 12, 2019             [Page 101]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      MOVE DB_INSTRUMENT_DIRECTORY <dir> <dst>
 
    Where <dir> is the absolute path name of the directory to move and
    <dst> is the location where the directory will be moved to.
@@ -5873,16 +5704,16 @@
          exists in the destination directory.  Error is also thrown when
          trying to copy a directory to a subdirectory of itself.
 
+   Example:
+
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 105]
+Schoenebeck            Expires September 12, 2019             [Page 102]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-   Example:
-
       C: "COPY DB_INSTRUMENT_DIRECTORY '/Piano Collection/Acoustic'
       '/Acoustic/Pianos'"
 
@@ -5929,50 +5760,16 @@
    directory to search in.  If NON_RECURSIVE is specified, the
    directories located in subdirectories of the specified directory will
    not be searched. <criteria-list> is a list of search criterias in
+   form of "key1=val1 key2=val2 ...".  The following criterias are
+   allowed:
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 106]
+Schoenebeck            Expires September 12, 2019             [Page 103]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-   form of "key1=val1 key2=val2 ...".  The following criterias are
-   allowed:
-
-   NAME='<search-string>'
-
-      Restricts the search to directories, which names satisfy the
-      supplied search string (encapsulated into apostrophes, supporting
-      escape sequences as described in chapter "Character Set and Escape
-      Sequences (Section 7.1)").
-
-   CREATED='[<date-after>]..[<date-before>]'
-
-      Restricts the search to directories, which creation date satisfies
-      the specified period, where <date-after> and <date-before> are in
-      "YYYY-MM-DD HH:MM:SS" format.  If <date-after> is omitted the
-      search is restricted to directories created before <date-before>.
-      If <date-before> is omitted, the search is restricted to
-      directories created after <date-after>.
-
-   MODIFIED='[<date-after>]..[<date-before>]'
-
-      Restricts the search to directories, which date of last
-      modification satisfies the specified period, where <date-after>
-      and <date-before> are in "YYYY-MM-DD HH:MM:SS" format.  If <date-
-      after> is omitted the search is restricted to directories, which
-      are last modified before <date-before>.  If <date-before> is
-      omitted, the search is restricted to directories, which are last
-      modified after <date-after>.
-
-   DESCRIPTION='<search-string>'
-
-      Restricts the search to directories with description that
-      satisfies the supplied search string (encapsulated into
-      apostrophes, supporting escape sequences as described in chapter
-      "Character Set and Escape Sequences (Section 7.1)").
-
    Where <search-string> is either a regular expression, or a word list
    separated with spaces for OR search and with '+' for AND search.
 
@@ -5984,15 +5781,6 @@
 
       "ERR:<error-code>:<error-message>" -
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 107]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
          if the given directory does not exist.
 
    Example:
@@ -6001,8 +5789,8 @@
 
       S: "'/Piano Collection'"
 
-      C: "FIND DB_INSTRUMENT_DIRECTORIES '/' CREATED='..2007-04-01 09:
-      30:13'"
+      C: "FIND DB_INSTRUMENT_DIRECTORIES '/' CREATED='..2007-04-01
+      09:30:13'"
 
       S: "'/Piano Collection','/Percussions'"
 
@@ -6030,6 +5818,14 @@
 
       "RECURSIVE" -
 
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 104]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          All instruments will be processed, including those in the
          subdirectories, and the respective subdirectory tree structure
          will be recreated in the instruments database
@@ -6039,16 +5835,6 @@
          Only the instruments in the specified directory will be added,
          the instruments in the subdirectories will not be processed.
 
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 108]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       "FLAT" -
 
          All instruments will be processed, including those in the
@@ -6088,22 +5874,20 @@
       C: "ADD DB_INSTRUMENTS '/Piano Collection' '/home/me/gigs/PMI
       Bosendorfer 290.gig' 0"
 
-      S: "OK"
-
-6.8.12.  Removing an instrument
-
-   The front-end can remove a particular instrument from the instruments
-   database by sending the following command:
 
 
 
+Schoenebeck            Expires September 12, 2019             [Page 105]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+      S: "OK"
 
-Schoenebeck             Expires January 16, 2016              [Page 109]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+6.8.12.  Removing an instrument
 
+   The front-end can remove a particular instrument from the instruments
+   database by sending the following command:
 
       REMOVE DB_INSTRUMENT <instr_path>
 
@@ -6146,20 +5930,19 @@
 
          if the given directory does not exist.
 
-   Example:
 
-      C: "GET DB_INSTRUMENTS '/Piano Collection'"
-
-      S: "2"
 
 
+Schoenebeck            Expires September 12, 2019             [Page 106]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   Example:
 
-Schoenebeck             Expires January 16, 2016              [Page 110]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      C: "GET DB_INSTRUMENTS '/Piano Collection'"
 
+      S: "2"
 
 6.8.14.  Listing all instruments in specific directory
 
@@ -6203,20 +5986,20 @@
    Where <instr_path> should be replaced by the absolute path name of
    the instrument the front-end is interested in.
 
-   Possible Answers:
-
-      LinuxSampler will answer by sending a <CRLF> separated list.  Each
-      answer line begins with the settings category name followed by a
-      colon and then a space character <SP> and finally the info
-      character string to that setting category.  At the moment the
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 111]
+Schoenebeck            Expires September 12, 2019             [Page 107]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+   Possible Answers:
+
+      LinuxSampler will answer by sending a <CRLF> separated list.  Each
+      answer line begins with the settings category name followed by a
+      colon and then a space character <SP> and finally the info
+      character string to that setting category.  At the moment the
       following categories are defined:
 
 
@@ -6259,19 +6042,18 @@
             A brief description of the instrument.  Note that the
             character string may contain escape sequences (Section 7.1).
 
-         IS_DRUM -
-
-            either true or false, determines whether the instrument is a
-            drumkit or a chromatic instrument
 
 
 
+Schoenebeck            Expires September 12, 2019             [Page 108]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-Schoenebeck             Expires January 16, 2016              [Page 112]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+         IS_DRUM -
 
+            either true or false, determines whether the instrument is a
+            drumkit or a chromatic instrument
 
          PRODUCT -
 
@@ -6298,38 +6080,37 @@
 
       S: "INSTRUMENT_FILE: /home/me/gigs/Bosendorfer 290.gig"
 
-         "INSTRUMENT_NR: 0"
+      "INSTRUMENT_NR: 0"
 
-         "FORMAT_FAMILY: GIG"
+      "FORMAT_FAMILY: GIG"
 
-         "FORMAT_VERSION: 2"
+      "FORMAT_VERSION: 2"
 
-         "SIZE: 2050871870"
+      "SIZE: 2050871870"
 
-         "CREATED: 2007-02-05 10:23:12"
+      "CREATED: 2007-02-05 10:23:12"
 
-         "MODIFIED: 2007-04-07 12:50:21"
+      "MODIFIED: 2007-04-07 12:50:21"
 
-         "DESCRIPTION: "
+      "DESCRIPTION: "
 
-         "IS_DRUM: false"
+      "IS_DRUM: false"
 
-         "PRODUCT: GRANDIOSO Bosendorfer 290"
+      "PRODUCT: GRANDIOSO Bosendorfer 290"
 
-         "ARTISTS: Post Musical Instruments"
 
-         "KEYWORDS: Bosendorfer"
 
 
+Schoenebeck            Expires September 12, 2019             [Page 109]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+      "ARTISTS: Post Musical Instruments"
 
-Schoenebeck             Expires January 16, 2016              [Page 113]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      "KEYWORDS: Bosendorfer"
 
-
-         "."
+      "."
 
 6.8.16.  Renaming an instrument
 
@@ -6373,18 +6154,16 @@
 
       "OK" -
 
-         on success
 
 
 
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 114]
+Schoenebeck            Expires September 12, 2019             [Page 110]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+         on success
+
       "ERR:<error-code>:<error-message>" -
 
          in case the given instrument does not exists, or if an
@@ -6427,20 +6206,23 @@
 
       S: "OK"
 
-6.8.19.  Changing the description of instrument
 
-   The front-end can alter the description of a specific instrument by
-   sending the following command:
 
 
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 115]
+
+Schoenebeck            Expires September 12, 2019             [Page 111]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+6.8.19.  Changing the description of instrument
+
+   The front-end can alter the description of a specific instrument by
+   sending the following command:
+
       SET DB_INSTRUMENT DESCRIPTION <instr> <desc>
 
    Where <instr> is the absolute path name of the instrument and <desc>
@@ -6479,100 +6261,18 @@
    form of "key1=val1 key2=val2 ...".  The following criterias are
    allowed:
 
-   NAME='<search-string>'
-
-      Restricts the search to instruments, which names satisfy the
-      supplied search string (encapsulated into apostrophes, supporting
-      escape sequences as described in chapter "Character Set and Escape
-      Sequences (Section 7.1)").
-
-   SIZE=[<min>]..[<max>]
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 116]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-      Restricts the search to instruments, which size is in the
-      specified range.  If <min> is omitted, the search results are
-      restricted to instruments with size less then or equal to <max>.
-      If <max> is omitted, the search is restricted to instruments with
-      size greater then or equal to <min>.
-
-   CREATED='[<date-after>]..[<date-before>]'
-
-      Restricts the search to instruments, which creation date satisfies
-      the specified period, where <date-after> and <date-before> are in
-      "YYYY-MM-DD HH:MM:SS" format.  If <date-after> is omitted the
-      search is restricted to instruments created before <date-before>.
-      If <date-before> is omitted, the search is restricted to
-      instruments created after <date-after>.
-
-   MODIFIED='[<date-after>]..[<date-before>]'
-
-      Restricts the search to instruments, which date of last
-      modification satisfies the specified period, where <date-after>
-      and <date-before> are in "YYYY-MM-DD HH:MM:SS" format.  If <date-
-      after> is omitted the search is restricted to instruments, which
-      are last modified before <date-before>.  If <date-before> is
-      omitted, the search is restricted to instruments, which are last
-      modified after <date-after>.
-
-   DESCRIPTION='<search-string>'
-
-      Restricts the search to instruments with description that
-      satisfies the supplied search string (encapsulated into
-      apostrophes, supporting escape sequences as described in chapter
-      "Character Set and Escape Sequences (Section 7.1)").
-
-   PRODUCT='<search-string>'
-
-      Restricts the search to instruments with product info that
-      satisfies the supplied search string (encapsulated into
-      apostrophes, supporting escape sequences as described in chapter
-      "Character Set and Escape Sequences (Section 7.1)").
-
-   ARTISTS='<search-string>'
-
-      Restricts the search to instruments with artists info that
-      satisfies the supplied search string (encapsulated into
-      apostrophes, supporting escape sequences as described in chapter
-      "Character Set and Escape Sequences (Section 7.1)").
+   Where <search-string> is either a regular expression, or a word list
+   separated with spaces for OR search and with '+' for AND search.
 
-   KEYWORDS='<search-string>'
+   Possible Answers:
 
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 117]
+Schoenebeck            Expires September 12, 2019             [Page 112]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-      Restricts the search to instruments with keyword list that
-      satisfies the supplied search string (encapsulated into
-      apostrophes, supporting escape sequences as described in chapter
-      "Character Set and Escape Sequences (Section 7.1)").
-
-   IS_DRUM=true | false
-
-      Either true or false.  Restricts the search to drum kits or
-      chromatic instruments.
-
-   FORMAT_FAMILIES='<format-list>'
-
-      Restricts the search to instruments of the supplied format
-      families, where <format-list> is a comma separated list of format
-      families.
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-   Where <search-string> is either a regular expression, or a word list
-   separated with spaces for OR search and with '+' for AND search.
-
-   Possible Answers:
 
       A comma separated list with the absolute path names (encapsulated
       into apostrophes) of all instruments in the specified directory
@@ -6584,8 +6284,8 @@
 
    Example:
 
-      C: "FIND DB_INSTRUMENTS '/Piano Collection' NAME='bosendorfer+
-      290'"
+      C: "FIND DB_INSTRUMENTS '/Piano Collection'
+      NAME='bosendorfer+290'"
 
       S: "'/Piano Collection/Bosendorfer 290'"
 
@@ -6600,15 +6300,6 @@
    The front-end can ask for the current status of a particular database
    instruments job by sending the following command:
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 118]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       GET DB_INSTRUMENTS_JOB INFO <job-id>
 
    Where <job-id> should be replaced by the numerical ID of the job the
@@ -6632,6 +6323,13 @@
 
             The current number of scanned files
 
+
+
+Schoenebeck            Expires September 12, 2019             [Page 113]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          SCANNING -
 
             The absolute path name of the file which is currently being
@@ -6651,21 +6349,13 @@
 
       S: "FILES_TOTAL: 12"
 
-         "FILES_SCANNED: 7"
-
-         "SCANNING: /home/me/gigs/Bosendorfer 290.gig"
-
-         "STATUS: 42"
-
+      "FILES_SCANNED: 7"
 
+      "SCANNING: /home/me/gigs/Bosendorfer 290.gig"
 
+      "STATUS: 42"
 
-Schoenebeck             Expires January 16, 2016              [Page 119]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-         "."
+      "."
 
 6.8.22.  Formatting the instruments database
 
@@ -6685,6 +6375,17 @@
 
          If the formatting of the instruments database failed.
 
+
+
+
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 114]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
 6.8.23.  Checking for lost instrument files
 
    The front-end can retrieve the list of all instrument files in the
@@ -6710,17 +6411,6 @@
       S: "'/gigs/Bosendorfer 290.gig','/gigs/Steinway D.gig','/gigs/Free
       Piano.gig'"
 
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 120]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 6.8.24.  Replacing an instrument file
 
    The front-end can substitute all occurrences of an instrument file in
@@ -6745,6 +6435,13 @@
 
    Example:
 
+
+
+Schoenebeck            Expires September 12, 2019             [Page 115]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       C: "SET DB_INSTRUMENT FILE_PATH '/gigs/Bosendorfer 290.gig'
       '/gigs/pianos/Bosendorfer 290.gig'"
 
@@ -6767,16 +6464,6 @@
    The front-end can request to open an appropriate instrument editor
    application by sending the following command:
 
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 121]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       EDIT CHANNEL INSTRUMENT <sampler-channel>
 
    Where <sampler-channel> should be replaced by the number of the
@@ -6803,6 +6490,14 @@
 
          when an appropriate instrument editor was launched
 
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 116]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       "WRN:<warning-code>:<warning-message>" -
 
          when an appropriate instrument editor was launched, but there
@@ -6820,19 +6515,11 @@
 
 6.10.  Managing Files
 
-   You can query detailed informations about files located at the same
+   You can query detailed information about files located at the same
    system where the sampler instance is running on.  Using this command
-   set allows to retrieve file informations even remotely from another
+   set allows to retrieve file information even remotely from another
    machine.
 
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 122]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 6.10.1.  Retrieving amount of instruments of a file
 
    The front-end can retrieve the amount of instruments within a given
@@ -6859,6 +6546,14 @@
 
    Examples:
 
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 117]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       C: "GET FILE INSTRUMENTS 'D:/Sounds/Foo.gig'"
 
       S: "10"
@@ -6880,15 +6575,6 @@
 
    Possible Answers:
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 123]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       On success, the sampler will answer by returning a comma separated
       list of instrument IDs.
 
@@ -6902,9 +6588,9 @@
 
       S: "0,1,2,3,4,5,6,7,8,9"
 
-6.10.3.  Retrieving informations about one instrument in a file
+6.10.3.  Retrieving information about one instrument in a file
 
-   The front-end can retrieve detailed informations about a specific
+   The front-end can retrieve detailed information about a specific
    instrument within a given instrument file by sending the following
    command:
 
@@ -6916,9 +6602,17 @@
    the numeric instrument ID as returned by the "LIST FILE INSTRUMENTS"
    (Section 6.10.2) command.
 
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 118]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    The sampler will try to ask all sampler engines, whether they support
    the given file and ask the first engine with a positive answer for
-   informations about the specific instrument in the given file.
+   information about the specific instrument in the given file.
 
    Possible Answers:
 
@@ -6936,15 +6630,6 @@
 
          FORMAT_FAMILY -
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 124]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
             name of the sampler format of the given instrument
 
          FORMAT_VERSION -
@@ -6973,49 +6658,70 @@
             127, reflecting the analog meaning of the MIDI
             specification.
 
-   The mentioned fields above don't have to be in particular order.
 
-   Example:
 
-      C: "GET FILE INSTRUMENT INFO 'D:/Sounds/Foo.gig' 0"
 
-      S: "NAME: Lunatic Loops"
-
-         "FORMAT_FAMILY: GIG"
-
-         "FORMAT_VERSION: 3"
+Schoenebeck            Expires September 12, 2019             [Page 119]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-         "PRODUCT: The Backbone Bongo Beats"
 
-         "ARTISTS: Jimmy the Fish"
+   The mentioned fields above don't have to be in particular order.
 
-         "."
+   Example:
 
+      C: "GET FILE INSTRUMENT INFO 'D:/Sounds/Foo.gig' 0"
 
+      S: "NAME: Lunatic Loops"
 
+      "FORMAT_FAMILY: GIG"
 
+      "FORMAT_VERSION: 3"
 
+      "PRODUCT: The Backbone Bongo Beats"
 
-Schoenebeck             Expires January 16, 2016              [Page 125]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      "ARTISTS: Jimmy the Fish"
 
+      "."
 
 6.11.  Managing Effects
 
-   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.
+   There are two possible approaches to apply audio effects (e.g.
+   reverb, delay, compression).  You can either a) load and apply
+   internal effects or you can b) route effect sends directly to
+   dedicated output channels of your audio device and apply effects
+   externally (e.g. by routing those dedicated output channels to
+   another application).
+
+   This chapter describes how to load and manage internal effects.  If
+   your intention is rather to apply effects externally, then you can
+   omit this chapter.  For applying effects externally, you just need to
+   create FX sends (Section 6.4.28) on the respective sampler channel(s)
+   and adjust their destination audio channels (Section 6.4.34)
+   appropriately, because by default FX sends are automatically routed
+   directly to the audio output device.
+
+   The sampler usually provides a set of internal audio effects.  The
+   exact set of effects depends on the availability of third party
+   effect plugins installed on the system where the sampler runs on
+   (e.g.  LADSPA plugins).
 
    At the moment only "send effects" are supported.  Support for "insert
    effects" and "master effects" is planned to be added at a later
    point.
 
    The following commands allow to retrieve the set of internal effects
-   available to the sampler, detailed informations about those effects
+   available to the sampler, detailed information about those effects
    and to create and destroy instances of such effects.  After an
+
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 120]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    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.
 
@@ -7048,15 +6754,6 @@
 
       C: "GET AVAILABLE_EFFECTS"
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 126]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       S: "129"
 
 6.11.2.  Get list of available effects
@@ -7072,6 +6769,15 @@
       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
+
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 121]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       of the same effect can change at runtime, e.g. when the user
       requests a rescan of available effect plugins.
 
@@ -7083,7 +6789,7 @@
 
 6.11.3.  Retrieving general information about an effect
 
-   The front-end can ask for general informations about an effect by
+   The front-end can ask for general information about an effect by
    sending the following command:
 
       GET EFFECT INFO <effect-index>
@@ -7106,13 +6812,6 @@
             name of the effect plugin system the effect is based on
             (e.g.  "LADSPA")
 
-
-
-Schoenebeck             Expires January 16, 2016              [Page 127]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
          MODULE -
 
             module of the effect plugin system that contains this
@@ -7127,6 +6826,14 @@
             within its module (note that the character string may
             contain escape sequences (Section 7.1))
 
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 122]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          DESCRIPTION -
 
             human readable name of the effect, intended to be displayed
@@ -7141,13 +6848,13 @@
 
       S: "SYSTEM: LADSPA"
 
-         "MODULE: /usr/lib/ladspa/lowpass_iir_1891.so"
+      "MODULE: /usr/lib/ladspa/lowpass_iir_1891.so"
 
-         "NAME: lowpass_iir"
+      "NAME: lowpass_iir"
 
-         "DESCRIPTION: Glame Lowpass Filter"
+      "DESCRIPTION: Glame Lowpass Filter"
 
-         "."
+      "."
 
 6.11.4.  Creating an instance of an effect by its portable ID
 
@@ -7162,13 +6869,6 @@
    <module> and the character string of argument <effect-name> may
    contain escape sequences (Section 7.1).
 
-
-
-Schoenebeck             Expires January 16, 2016              [Page 128]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    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
@@ -7183,6 +6883,13 @@
    search for an effect that only matches the given <effect-system> and
    <effect-name> arguments.
 
+
+
+Schoenebeck            Expires September 12, 2019             [Page 123]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    Possible Answers:
 
       "OK[<effect-instance>]" -
@@ -7218,13 +6925,6 @@
    Where <effect-index> is the numerical ID of the effect as returned by
    the "LIST AVAILABLE_EFFECTS" (Section 6.11.2) command.
 
-
-
-Schoenebeck             Expires January 16, 2016              [Page 129]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    The sampler will try to load the requested effect and to create an
    instance of it.
 
@@ -7239,6 +6939,13 @@
 
    Possible Answers:
 
+
+
+Schoenebeck            Expires September 12, 2019             [Page 124]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       "OK[<effect-instance>]" -
 
          in case the effect instance was successfully created, where
@@ -7273,14 +6980,6 @@
    EFFECT_INSTANCES" (Section 6.11.8) command.
 
    The effect instance can only be destroyed if it's not used in any
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 130]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    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.
@@ -7296,6 +6995,13 @@
          in case it failed, providing an appropriate error code and
          error message
 
+
+
+Schoenebeck            Expires September 12, 2019             [Page 125]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    Examples:
 
       C: "DESTROY EFFECT_INSTANCE 5"
@@ -7330,13 +7036,6 @@
 
    Possible Answers:
 
-
-
-Schoenebeck             Expires January 16, 2016              [Page 131]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       The sampler will answer by returning a comma separated list with
       numerical IDs of effects instances.
 
@@ -7348,9 +7047,17 @@
 
 6.11.9.  Retrieving current information about an effect instance
 
-   The front-end can ask for the current informations about a particular
+   The front-end can ask for the current information about a particular
    effect instance by sending the following command:
 
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 126]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       GET EFFECT_INSTANCE INFO <effect-instance>
 
    Where <effect-instance> is the numerical ID of an effect instance as
@@ -7386,13 +7093,6 @@
             within its module (note that the character string may
             contain escape sequences (Section 7.1))
 
-
-
-Schoenebeck             Expires January 16, 2016              [Page 132]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
          DESCRIPTION -
 
             human readable name of the effect, intended to be displayed
@@ -7406,21 +7106,29 @@
 
    The mentioned fields above don't have to be in particular order.
 
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 127]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    Example:
 
       C: "GET EFFECT_INSTANCE INFO 3"
 
       S: "SYSTEM: LADSPA"
 
-         "MODULE: /usr/lib/ladspa/mod_delay_1419.so"
+      "MODULE: /usr/lib/ladspa/mod_delay_1419.so"
 
-         "NAME: modDelay"
+      "NAME: modDelay"
 
-         "DESCRIPTION: Modulatable delay"
+      "DESCRIPTION: Modulatable delay"
 
-         "INPUT_CONTROLS: 1"
+      "INPUT_CONTROLS: 1"
 
-         "."
+      "."
 
 6.11.10.  Retrieving information about an effect parameter
 
@@ -7428,8 +7136,8 @@
    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:
+   front-end can ask for the current information of an effect instance's
+   input control by sending the following command:
 
       GET EFFECT_INSTANCE_INPUT_CONTROL INFO <effect-instance> <input-
       control>
@@ -7441,14 +7149,6 @@
    the "INPUT_CONTROLS" field of the "GET EFFECT_INSTANCE INFO"
    (Section 6.11.9) command.
 
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 133]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    Possible Answers:
 
       LinuxSampler will answer by sending a <CRLF> separated list.  Each
@@ -7462,6 +7162,14 @@
 
 
 
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 128]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          DESCRIPTION -
 
             (always returned) human readable name of the effect
@@ -7498,22 +7206,25 @@
 
    Example:
 
+      C: "GET EFFECT_INSTANCE_INPUT_CONTROL INFO 1 0"
 
+      S: "DESCRIPTION: Base delay (s)"
 
-Schoenebeck             Expires January 16, 2016              [Page 134]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      "VALUE: 0.500"
 
+      "RANGE_MIN: 0.000"
+
+      "."
 
-      C: "GET EFFECT_INSTANCE_INPUT_CONTROL INFO 1 0"
 
-      S: "DESCRIPTION: Base delay (s)"
 
-         "VALUE: 0.500"
 
-         "RANGE_MIN: 0.000"
 
-         "."
+
+Schoenebeck            Expires September 12, 2019             [Page 129]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
 
 6.11.11.  Altering an effect parameter
 
@@ -7553,14 +7264,6 @@
    The front-end can retrieve the current amount of send effect chains
    of an audio output device by sending the following command:
 
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 135]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       GET SEND_EFFECT_CHAINS <audio-device>
 
    Where <audio-device> should be replaced by the numerical ID of the
@@ -7570,6 +7273,15 @@
 
    Possible Answers:
 
+
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 130]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       The sampler will answer by returning the current number of send
       effect chains of the supplied audio output device.
 
@@ -7608,15 +7320,6 @@
    The front-end can add a send effect chain by sending the following
    command:
 
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 136]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       ADD SEND_EFFECT_CHAIN <audio-device>
 
    Where <audio-device> should be replaced by the numerical ID of the
@@ -7628,6 +7331,13 @@
 
       "OK[<effect-chain>]" -
 
+
+
+Schoenebeck            Expires September 12, 2019             [Page 131]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
          in case the send effect chain was added successfully, where
          <effect-chain> is the numerical ID of the new send effect chain
 
@@ -7665,14 +7375,6 @@
 
          if the send effect chain could not be removed
 
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 137]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    Examples:
 
       C: "REMOVE SEND_EFFECT_CHAIN 0 2"
@@ -7681,9 +7383,17 @@
 
 6.11.16.  Retrieving information about a send effect chain
 
-   The front-end can ask for informations of a send effect chain by
+   The front-end can ask for information of a send effect chain by
    sending the following command:
 
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 132]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
       GET SEND_EFFECT_CHAIN INFO <audio-device> <effect-chain>
 
    Where <audio-device> should be replaced by the numerical ID of the
@@ -7721,17 +7431,9 @@
 
       S: "EFFECT_COUNT: 3"
 
+      "EFFECT_SEQUENCE: 31,4,7"
 
-
-
-Schoenebeck             Expires January 16, 2016              [Page 138]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-         "EFFECT_SEQUENCE: 31,4,7"
-
-         "."
+      "."
 
 6.11.17.  Append effect instance to a send effect chain
 
@@ -7741,6 +7443,13 @@
       APPEND SEND_EFFECT_CHAIN EFFECT <audio-device> <effect-chain>
       <effect-instance>
 
+
+
+Schoenebeck            Expires September 12, 2019             [Page 133]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    Where <audio-device> should be replaced by the numerical ID of the
    audio output device as given by the "CREATE AUDIO_OUTPUT_DEVICE"
    (Section 6.2.5) or "LIST AUDIO_OUTPUT_DEVICES" (Section 6.2.8)
@@ -7775,16 +7484,6 @@
    The front-end can add an unused effect instance to a certain position
    of a send effect chain by sending the following command:
 
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 139]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
       INSERT SEND_EFFECT_CHAIN EFFECT <audio-device> <effect-chain>
       <chain-pos> <effect-instance>
 
@@ -7798,6 +7497,15 @@
    (Section 6.11.8) command and <chain-pos> the exact position of the
    effect chain where the supplied effect shall be inserted to.
 
+
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 134]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
    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.
@@ -7834,13 +7542,6 @@
    (Section 6.11.13) command and <chain-pos> the exact position of the
    effect instance to be removed from the effect chain.
 
-
-
-Schoenebeck             Expires January 16, 2016              [Page 140]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    Possible Answers:
 
       "OK" -
@@ -7853,49 +7554,17 @@
 
    Examples:
 
-      C: "REMOVE SEND_EFFECT_CHAIN EFFECT 0 2 4"
-
-      S: "OK"
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
 
 
 
+Schoenebeck            Expires September 12, 2019             [Page 135]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-Schoenebeck             Expires January 16, 2016              [Page 141]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      C: "REMOVE SEND_EFFECT_CHAIN EFFECT 0 2 4"
 
+      S: "OK"
 
 7.  Command Syntax
 
@@ -7941,17 +7610,17 @@
 
       / MAP SP map_instruction
 
-      / UNMAP SP unmap_instruction
 
-      / GET SP get_instruction
 
 
+Schoenebeck            Expires September 12, 2019             [Page 136]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-Schoenebeck             Expires January 16, 2016              [Page 142]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      / UNMAP SP unmap_instruction
 
+      / GET SP get_instruction
 
       / CREATE SP create_instruction
 
@@ -7997,18 +7666,19 @@
 
       CHANNEL
 
-      / CHANNEL SP MIDI_INPUT SP sampler_channel SP device_index
-
-      / CHANNEL SP MIDI_INPUT SP sampler_channel SP device_index SP
-      midi_input_port_index
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 143]
+Schoenebeck            Expires September 12, 2019             [Page 137]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+      / CHANNEL SP MIDI_INPUT SP sampler_channel SP device_index
+
+      / CHANNEL SP MIDI_INPUT SP sampler_channel SP device_index SP
+      midi_input_port_index
+
       / DB_INSTRUMENT_DIRECTORY SP db_path
 
       / DB_INSTRUMENTS SP NON_MODAL SP scan_mode SP db_path SP filename
@@ -8052,18 +7722,17 @@
 
       / DEVICE_MIDI
 
-      / VOICE_COUNT
-
-      / STREAM_COUNT
 
 
 
+Schoenebeck            Expires September 12, 2019             [Page 138]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-Schoenebeck             Expires January 16, 2016              [Page 144]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      / VOICE_COUNT
 
+      / STREAM_COUNT
 
       / BUFFER_FILL
 
@@ -8109,17 +7778,17 @@
 
    unsubscribe_event =
 
-      AUDIO_OUTPUT_DEVICE_COUNT
 
-      / AUDIO_OUTPUT_DEVICE_INFO
 
 
+Schoenebeck            Expires September 12, 2019             [Page 139]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-Schoenebeck             Expires January 16, 2016              [Page 145]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      AUDIO_OUTPUT_DEVICE_COUNT
 
+      / AUDIO_OUTPUT_DEVICE_INFO
 
       / MIDI_INPUT_DEVICE_COUNT
 
@@ -8165,17 +7834,17 @@
 
       / TOTAL_STREAM_COUNT
 
-      / TOTAL_VOICE_COUNT
 
-      / GLOBAL_INFO
 
 
+Schoenebeck            Expires September 12, 2019             [Page 140]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-Schoenebeck             Expires January 16, 2016              [Page 146]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      / TOTAL_VOICE_COUNT
 
+      / GLOBAL_INFO
 
       / EFFECT_INSTANCE_COUNT
 
@@ -8221,18 +7890,19 @@
 
       / MIDI_INSTRUMENT_MAP SP ALL
 
-      / SEND_EFFECT_CHAIN SP device_index SP effect_chain
 
-      / SEND_EFFECT_CHAIN SP EFFECT SP device_index SP effect_chain SP
-      chain_pos
 
 
-
-Schoenebeck             Expires January 16, 2016              [Page 147]
+Schoenebeck            Expires September 12, 2019             [Page 141]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+      / SEND_EFFECT_CHAIN SP device_index SP effect_chain
+
+      / SEND_EFFECT_CHAIN SP EFFECT SP device_index SP effect_chain SP
+      chain_pos
+
       / FX_SEND SP EFFECT SP sampler_channel SP fx_send_id
 
       / DB_INSTRUMENT_DIRECTORY SP FORCE SP db_path
@@ -8275,19 +7945,19 @@
 
       / AUDIO_OUTPUT_DRIVER_PARAMETER SP INFO SP string SP string
 
-      / AUDIO_OUTPUT_DRIVER_PARAMETER SP INFO SP string SP string SP
-      key_val_list
 
-      / AUDIO_OUTPUT_DEVICES
 
 
 
+Schoenebeck            Expires September 12, 2019             [Page 142]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-Schoenebeck             Expires January 16, 2016              [Page 148]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      / AUDIO_OUTPUT_DRIVER_PARAMETER SP INFO SP string SP string SP
+      key_val_list
 
+      / AUDIO_OUTPUT_DEVICES
 
       / MIDI_INPUT_DEVICES
 
@@ -8332,18 +8002,17 @@
 
       / MIDI_INSTRUMENT_MAPS
 
-      / MIDI_INSTRUMENT_MAP SP INFO SP midi_map
-
-      / FX_SENDS SP sampler_channel
 
 
 
+Schoenebeck            Expires September 12, 2019             [Page 143]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-Schoenebeck             Expires January 16, 2016              [Page 149]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      / MIDI_INSTRUMENT_MAP SP INFO SP midi_map
 
+      / FX_SENDS SP sampler_channel
 
       / FX_SEND SP INFO SP sampler_channel SP fx_send_id
 
@@ -8390,17 +8059,15 @@
       / EFFECT_INSTANCE_INPUT_CONTROL SP VALUE SP effect_instance SP
       input_control SP control_value
 
-      / CHANNEL SP set_chan_instruction
-
 
 
-
-
-Schoenebeck             Expires January 16, 2016              [Page 150]
+Schoenebeck            Expires September 12, 2019             [Page 144]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+      / CHANNEL SP set_chan_instruction
+
       / MIDI_INSTRUMENT_MAP SP NAME SP midi_map SP map_name
 
       / FX_SEND SP NAME SP sampler_channel SP fx_send_id SP fx_send_name
@@ -8450,11 +8117,9 @@
 
 
 
-
-
-Schoenebeck             Expires January 16, 2016              [Page 151]
+Schoenebeck            Expires September 12, 2019             [Page 145]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
       / MIDI_INPUT_DEVICE SP string SP key_val_list
@@ -8508,9 +8173,9 @@
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 152]
+Schoenebeck            Expires September 12, 2019             [Page 146]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
       AUDIO_OUTPUT_DEVICE SP number
@@ -8560,17 +8225,15 @@
 
       / VOLUME SP sampler_channel SP volume_value
 
+      / MUTE SP sampler_channel SP boolean
 
 
 
-
-Schoenebeck             Expires January 16, 2016              [Page 153]
+Schoenebeck            Expires September 12, 2019             [Page 147]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-      / MUTE SP sampler_channel SP boolean
-
       / SOLO SP sampler_channel SP boolean
 
       / MIDI_INSTRUMENT_MAP SP sampler_channel SP midi_map
@@ -8617,15 +8280,15 @@
 
       / AVAILABLE_ENGINES
 
+      / AVAILABLE_EFFECTS
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 154]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
 
+Schoenebeck            Expires September 12, 2019             [Page 148]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      / AVAILABLE_EFFECTS
 
       / EFFECT_INSTANCES
 
@@ -8672,18 +8335,16 @@
 
       ON_DEMAND
 
+      / ON_DEMAND_HOLD
 
+      / PERSISTENT
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 155]
+Schoenebeck            Expires September 12, 2019             [Page 149]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-      / ON_DEMAND_HOLD
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      / PERSISTENT
 
    effect_instance =
 
@@ -8729,17 +8390,17 @@
 
    midi_ctrl =
 
+      number
 
+   volume_value =
 
 
-Schoenebeck             Expires January 16, 2016              [Page 156]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
 
 
-      number
+Schoenebeck            Expires September 12, 2019             [Page 150]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-   volume_value =
 
       dotnum
 
@@ -8785,17 +8446,17 @@
 
       stringval_escaped
 
+   effect_name =
 
+      stringval_escaped
 
 
-Schoenebeck             Expires January 16, 2016              [Page 157]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
 
 
-   effect_name =
+Schoenebeck            Expires September 12, 2019             [Page 151]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      stringval_escaped
 
    effect_index =
 
@@ -8841,17 +8502,17 @@
 
       / stringval_escaped
 
+   scan_mode =
 
+      RECURSIVE
 
 
-Schoenebeck             Expires January 16, 2016              [Page 158]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
 
 
-   scan_mode =
+Schoenebeck            Expires September 12, 2019             [Page 152]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      RECURSIVE
 
       / NON_RECURSIVE
 
@@ -8897,18 +8558,18 @@
    |                        |                                          |
    | \OOO                   | three digit octal ASCII code of the      |
    |                        | character                                |
+   |                        |                                          |
+   | \xHH                   | two digit hex ASCII code of the          |
+   |                        | character                                |
+   +------------------------+------------------------------------------+
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 159]
+Schoenebeck            Expires September 12, 2019             [Page 153]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-   | \xHH                   | two digit hex ASCII code of the          |
-   |                        | character                                |
-   +------------------------+------------------------------------------+
-
    Notice: due to the transition of certain parts of the protocol which
    now support escape sequences, a slight backward incompatibility to
    protocols version v1.1 and younger has been introduced.  The only
@@ -8953,17 +8614,17 @@
 
       "SET DB_INSTRUMENT_DIRECTORY DESCRIPTION" (Section 6.8.9)
 
+      "SET DB_INSTRUMENT NAME" (Section 6.8.16)
 
+      "SET DB_INSTRUMENT DESCRIPTION" (Section 6.8.19)
 
 
-Schoenebeck             Expires January 16, 2016              [Page 160]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
 
 
-      "SET DB_INSTRUMENT NAME" (Section 6.8.16)
+Schoenebeck            Expires September 12, 2019             [Page 154]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      "SET DB_INSTRUMENT DESCRIPTION" (Section 6.8.19)
 
       "FIND DB_INSTRUMENTS" (Section 6.8.20)
 
@@ -9009,18 +8670,17 @@
 
    The following LSCP commands even support escape sequences as part of
    at least one of their text-based arguments (i.e. entity name,
+   description) and / or may contain escape sequences in at least one of
+   their text-based fields in their response:
 
+      "GET SERVER INFO" (Section 6.6.5)
 
 
-Schoenebeck             Expires January 16, 2016              [Page 161]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
 
-   description) and / or may contain escape sequences in at least one of
-   their text-based fields in their response:
+Schoenebeck            Expires September 12, 2019             [Page 155]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      "GET SERVER INFO" (Section 6.6.5)
 
       "GET ENGINE INFO" (Section 6.4.9)
 
@@ -9065,14 +8725,6 @@
       "CREATE EFFECT_INSTANCE" (Section 6.11.4)
 
    Please note that these lists are manually maintained.  If you find a
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 162]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
    command that also supports escape sequences we forgot to mention
    here, please report it!
 
@@ -9081,52 +8733,9 @@
 
 
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 163]
+Schoenebeck            Expires September 12, 2019             [Page 156]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
 8.  Events
@@ -9176,17 +8785,15 @@
 
    Server will start sending the following notification messages:
 
+      "NOTIFY:MIDI_INPUT_DEVICE_COUNT:<devices>"
 
 
 
-
-Schoenebeck             Expires January 16, 2016              [Page 164]
+Schoenebeck            Expires September 12, 2019             [Page 157]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-      "NOTIFY:MIDI_INPUT_DEVICE_COUNT:<devices>"
-
    where <devices> will be replaced by the new number of MIDI input
    devices.
 
@@ -9233,15 +8840,15 @@
    Server will start sending one of the the following notification
    messages:
 
+      "NOTIFY:CHANNEL_MIDI:<channel-id> NOTE_ON <note> <velocity>"
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 165]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
 
+Schoenebeck            Expires September 12, 2019             [Page 158]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      "NOTIFY:CHANNEL_MIDI:<channel-id> NOTE_ON <note> <velocity>"
 
       "NOTIFY:CHANNEL_MIDI:<channel-id> NOTE_OFF <note> <velocity>"
 
@@ -9289,15 +8896,15 @@
    Client may want to be notified when the number of voices on the back-
    end changes by issuing the following command:
 
+      SUBSCRIBE VOICE_COUNT
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 166]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
 
+Schoenebeck            Expires September 12, 2019             [Page 159]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      SUBSCRIBE VOICE_COUNT
 
    Server will start sending the following notification messages:
 
@@ -9345,15 +8952,15 @@
    Client may want to be notified when changes were made to sampler
    channels on the back-end by issuing the following command:
 
+      SUBSCRIBE CHANNEL_INFO
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 167]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
 
+Schoenebeck            Expires September 12, 2019             [Page 160]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
-      SUBSCRIBE CHANNEL_INFO
 
    Server will start sending the following notification messages:
 
@@ -9404,9 +9011,11 @@
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 168]
+
+
+Schoenebeck            Expires September 12, 2019             [Page 161]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
 8.14.  Total number of active voices changed
@@ -9456,17 +9065,15 @@
    Client may want to be notified when changes were made to MIDI
    instrument maps on the back-end by issuing the following command:
 
+      SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO
 
 
 
-
-Schoenebeck             Expires January 16, 2016              [Page 169]
+Schoenebeck            Expires September 12, 2019             [Page 162]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
-      SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO
-
    Server will start sending the following notification messages:
 
       "NOTIFY:MIDI_INSTRUMENT_MAP_INFO:<map-id>"
@@ -9516,9 +9123,11 @@
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 170]
+
+
+Schoenebeck            Expires September 12, 2019             [Page 163]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
 8.20.  Global settings changed
@@ -9565,17 +9174,22 @@
    Note that when a non-empty directory is removed, this event is not
    sent for the subdirectories in that directory.
 
-8.22.  Database instrument directory information changed
 
-   Client may want to be notified when changes were made to directories
-   in the instruments database by issuing the following command:
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 171]
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 164]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
 
+8.22.  Database instrument directory information changed
+
+   Client may want to be notified when changes were made to directories
+   in the instruments database by issuing the following command:
 
       SUBSCRIBE DB_INSTRUMENT_DIRECTORY_INFO
 
@@ -9617,21 +9231,25 @@
    Note that when a non-empty directory is removed, this event is not
    sent for the instruments in that directory.
 
-8.24.  Database instrument information changed
 
-   Client may want to be notified when changes were made to instruments
-   in the instruments database by issuing the following command:
 
-      SUBSCRIBE DB_INSTRUMENT_INFO
 
-   Server will start sending the following notification messages:
 
 
 
-Schoenebeck             Expires January 16, 2016              [Page 172]
+Schoenebeck            Expires September 12, 2019             [Page 165]
 
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
 
+8.24.  Database instrument information changed
+
+   Client may want to be notified when changes were made to instruments
+   in the instruments database by issuing the following command:
+
+      SUBSCRIBE DB_INSTRUMENT_INFO
+
+   Server will start sending the following notification messages:
 
       "NOTIFY:DB_INSTRUMENT_INFO:<instr-path>"
 
@@ -9668,6 +9286,18 @@
    real time events happening on the server, it is believed that an
    empty notification message is sufficient here.
 
+
+
+
+
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 166]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
 8.26.  Number of effect instances changed
 
    Client may want to be notified when the number of effect instances is
@@ -9682,13 +9312,6 @@
    where <instances> will be replaced by the new number of effect
    instances.
 
-
-
-Schoenebeck             Expires January 16, 2016              [Page 173]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 8.27.  Effect instance information changed
 
    Client may want to be notified when changes were made to effect
@@ -9719,6 +9342,18 @@
    and <chains> will be replaced by the new number of send effect
    chains.
 
+
+
+
+
+
+
+
+Schoenebeck            Expires September 12, 2019             [Page 167]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
+
+
 8.29.  Send effect chain information changed
 
    Client may want to be notified when changes were made to send effect
@@ -9737,14 +9372,6 @@
       changed and <instances> will be replaced by the new number of
       effect instances in the specified send effect chain.
 
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 174]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 8.30.  Miscellaneous and debugging events
 
    Client may want to be notified of miscellaneous and debugging events
@@ -9760,47 +9387,6 @@
    to the client.  Client MAY display this data to the user AS IS to
    facilitate debugging.
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 175]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 9.  Security Considerations
 
    As there is so far no method of authentication and authorization
@@ -9808,55 +9394,6 @@
    connect, running LinuxSampler might be a security risk for the host
    system the LinuxSampler instance is running on.
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 176]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 10.  Acknowledgments
 
    This document has benefited greatly from the comments of the
@@ -9865,53 +9402,19 @@
 
       Rui Nuno Capela
 
-      Vladimir Senkov
-
-      Mark Knecht
-
-      Grigor Iliev
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
 
 
 
+Schoenebeck            Expires September 12, 2019             [Page 168]
+
+Internet-Draft        LinuxSampler Control Protocol           March 2019
 
 
+      Vladimir Senkov
 
-Schoenebeck             Expires January 16, 2016              [Page 177]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
+      Mark Knecht
 
+      Grigor Iliev
 
 11.  References
 
@@ -9927,51 +9430,9 @@
    [RFC793]   Defense Advanced Research Projects Agency, "TRANSMISSION
               CONTROL PROTOCOL", RFC 793, 1981.
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 178]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
 Author's Address
 
-   C. Schoenebeck
+   C. Schoenebeck (editor)
    LinuxSampler.org
    Crudebyte Engineering
    Hofgartenstr. 3
@@ -10000,81 +9461,4 @@
 
 
 
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 179]
-
-Internet-Draft        LinuxSampler Control Protocol            July 2015
-
-
-Full Copyright Statement
-
-   Copyright (C) The IETF Trust (2015).
-
-   This document is subject to the rights, licenses and restrictions
-   contained in BCP 78, and except as set forth therein, the authors
-   retain all their rights.
-
-   This document and the information contained herein are provided on an
-   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
-   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
-   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
-   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
-   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
-   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-
-
-Intellectual Property
-
-   The IETF takes no position regarding the validity or scope of any
-   Intellectual Property Rights or other rights that might be claimed to
-   pertain to the implementation or use of the technology described in
-   this document or the extent to which any license under such rights
-   might or might not be available; nor does it represent that it has
-   made any independent effort to identify any such rights.  Information
-   on the procedures with respect to rights in RFC documents can be
-   found in BCP 78 and BCP 79.
-
-   Copies of IPR disclosures made to the IETF Secretariat and any
-   assurances of licenses to be made available, or the result of an
-   attempt made to obtain a general license or permission for the use of
-   such proprietary rights by implementers or users of this
-   specification can be obtained from the IETF on-line IPR repository at
-   http://www.ietf.org/ipr.
-
-   The IETF invites any interested party to bring to its attention any
-   copyrights, patents or patent applications, or other proprietary
-   rights that may cover technology that may be required to implement
-   this standard.  Please address the information to the IETF at
-   ietf-ipr@ietf.org.
-
-
-
-
-
-
-
-
-
-
-
-Schoenebeck             Expires January 16, 2016              [Page 180]
-
+Schoenebeck            Expires September 12, 2019             [Page 169]