--- doc/docbase/instrument_scripts/nksp/reference/functions/nksp_change_tune_function.html	2017/05/19 14:23:12	3188
+++ doc/docbase/instrument_scripts/nksp/reference/functions/nksp_change_tune_function.html	2017/05/19 14:26:05	3189
@@ -16,6 +16,14 @@
       all layers.
     </p>
     <p>
+      Internally the sampler always fades the tuning from its current value to
+      the new tuning as requested, however that tuning fade by default is so fast
+      that it sounds like its value jumps directly from its old to the new value.
+      You may also override that automated fade time explicitly by calling
+      <code lang="nksp">change_tune_time()</code> before calling the
+      <code lang="nksp">change_tune()</code> function.
+    </p>
+    <p>
       The tuning changes set by calling this function are always applied relatively to
       the tuning/pitch calculated by the synthesis model and sampler format. That means
       the various sources of tuning/pitch factors like MIDI pitch bend wheel, Pitch Envelopes,
@@ -59,7 +67,8 @@
         <td>Integer Number</td>
         <td>Tuning change in milli cents.
             A positive value increases the tuning,
-            a negative value decreases the tuning.</td>
+            a negative value decreases the tuning.<br>
+            [required]</td>
       </tr>
       <tr>
         <td><code>??relative??</code></td>
@@ -80,8 +89,17 @@
     <h3>Examples</h3>
     <p>None yet.<p>
 
+    <h3>See also</h3>
+    <p><code>change_tune_time()</code><p>
+
     <h3>Availabilty</h3>
     <p>Since LinuxSampler 2.0.0.svn11.<p>
 
+    <note>
+      The third argument of this function <code>??relative??</code> is only
+      optional with NKSP. If you want to keep compatibility with KSP, then you
+      should always pass a value for that third argument of this function.
+    </note>
+    
   </body>
 </html>