/[svn]/doc/docbase/release_notes/linuxsampler_2_2_0/01_linuxsampler_2_2_0.html

Diff of /doc/docbase/release_notes/linuxsampler_2_2_0/01_linuxsampler_2_2_0.html

Parent Directory | Revision Log | View Patch Patch

-revision 3887 by schoenebeck,
Sun May  9 18:00:00 2021 UTC
+revision 3888 by schoenebeck,
Sun May  9 18:18:23 2021 UTC
 Line 17
        release.
      </p>
-     <h3 id="cpp14">C++11/C++14 Requirement</h3>
+     <h3 id="cpp14">C++11 / C++14 Requirement</h3>
      <p>
-       Starting with Gigedit 1.2.0 and libgig 4.3.0 you now need at least a C++11
+       Starting with <b>Gigedit 1.2.0</b> and <b>libgig 4.3.0</b> you now need at
+       least a <b>C++11</b>
        compliant compiler to build them from source; and for building
-       LinuxSampler 2.2.0 you now need at least a C++14 compliant compiler.
+       <b>LinuxSampler 2.2.0</b> you now need at least a <b>C++14</b> compliant compiler.
        Originally it was planned to only raise the minimum compiler
        requirement to C++11 for LinuxSampler in this release as well, however
        during this development cycle, some C++14 features came across which helped
-Line 42
+Line 43
        are now all 64-bit internally, which prevents unexpected side effects of
        script authors due to potential integer overflows that easily had happened
        before when integer script variables were just 32-bit wide.
+       &nbsp;&nbsp;
        <a href="01_nksp_real_unit_final.html#64bit">Find out more ...</a>
      </p>
-Line 53
+Line 55
        ) and floating point arrays (e.g.
        <code lang="nksp">declare ?foo[] = ( 1.6, 4.7 )</code>
        ).
+       &nbsp;&nbsp;
        <a href="01_nksp_real_unit_final.html#real_numbers">Find out more ...</a>
      </p>
-Line 60
+Line 63
      <p>
        Another huge new NKSP language feature is
        <a href="01_nksp_real_unit_final.html#units">support for standard measuring units</a>
-       like <code>Hz</code> (Hertz), <code>dB</code> (Decibel),
+       like <code lang="none">Hz</code> (Hertz), <code lang="none">dB</code> (Decibel),
-       <code>s</code> (seconds), <code>c</code> (cents) in conjuction with
+       <code lang="none">s</code> (seconds), <code lang="none">c</code> (cents) in conjuction with
-       arbitrary metric prefixes like <code>kHz</code>, <code>mdB</code>,
+       arbitrary metric prefixes like <code lang="none">kHz</code>, <code lang="none">mdB</code>,
-       <code>ms</code>, <code>mc</code>, etc. For instance previously for pausing
+       <code lang="none">ms</code>, <code lang="none">mc</code>, etc.<br>
-       a script for one second, you had to write <code>wait(1000000)</code>,
+       <br>
-       which still works, but now you can also just write <code>wait(1s)</code>.
+       For instance previously for pausing
+       a script for one second, you had to write <code lang="nksp">wait(1000000)</code>,
+       which still works, but now you can also just write <code lang="nksp">wait(1s)</code>.
+       &nbsp;&nbsp;
        <a href="01_nksp_real_unit_final.html#units">Find out more ...</a>
      </p>
-Line 76
+Line 82
        that should not be overridden by any other modulation source (e.g. neither
        from patch level, nor LFOs, nor from EGs, ...). This is sometimes helpful
        for being able to e.g. say in a script, "hey, the volume of this voice
-       should be exactly -3dB, period. I mean it!":
+       should be exactly -3dB, period. I mean it!", which is as simple as
-     </p>
+       <code lang="nksp">change_vol($EVENT_ID, !-3dB)</code>
-     <p>
+       &nbsp;&nbsp;
-       <code lang="nksp">
- on note
-   change_vol($EVENT_ID, !-3dB)
- end note
-       </code>
-     </p>
-     <p>
        <a href="01_nksp_real_unit_final.html#finalness">Find out more ...</a>
      </p>
+     <img src="nksp_multi_mods_fin.png" caption="Force 'Finalness' by Script">
      <h3 id="functions">New Built-In NKSP Functions</h3>
      <p>
        Furthermore there are <b>23 new</b>
        <a href="01_nksp_reference.html#functions">built-in NKSP script functions</a>
-       and <b>6 new</b> <a href="01_nksp_reference.html#variables">NKSP constants/variables</a>.
+       and <b>6 new</b> <a href="01_nksp_reference.html#variables">NKSP constants/variables</a>.<br>
+       <br>
        There also <b>2 new event handler types</b> for processing MIDI <b>RPN events</b>:
      </p>
      <p>
-Line 129 
 end on
+Line 130 
 end on
        parameters on the other hand, hard coded into the sampler engines and
        supported already by the underlying file format allow very quick and
        convenient parameter changes, e.g. simply by few clicks in the Gigedit
-       instrument editor. What about having both?
+       instrument editor. What about having both?<br>
-     </p>
+       <br>
-     <p>
-       <img src="nksp_new_patch_script_example_shot.png">
        This is what the new NKSP "patch" variables are for. By simply declaring
        an instrument script variable with the new NKSP keyword <code>patch</code>
        you are publishing and exposing that variable as parameter in the
-Line 148 
 end on
+Line 147 
 end on
        By selecting one of the overridden variables and hitting the
        <b>Backspace</b> (&#9003;) key you can revert those variables back to
        their default values.
-       <img src="gigedit_new_patch_vars_cut.png">
+     </p>
+     <p>
+       <img src="nksp_new_patch_script_example_shot.png" caption="NKSP Code Example using 'patch' qualifier">
+       <img src="gigedit_new_patch_vars_cut.png" caption="Overriding 'patch' variables in Gigedit">
      </p>
      <h2 id="gig">GigaStudio Format Engine</h2>
-Line 163 
 end on
+Line 165 
 end on
      <h3 id="lfo">LFO Extensions</h3>
      <p>
-       <img src="gigedit_new_lfo_wave_forms.png">
        You now have much more control over LFOs with the gig engine like
        selecting different LFO waveforms as sine, triangle, saw or square.
        GigaStudio had this limited to sine only. The default LFO wave form in
-Line 172 
 end on
+Line 173 
 end on
        can now also fine control the start phase of individual LFOs. In the
        original gig format you were only able to flip the phase.
      </p>
+     <img src="gigedit_new_lfo_wave_forms.png">
      <h3 id="filters">New Filter Types</h3>
      <p>
-       <img src="gigedit_new_audio_filter_types.png">
        Furthermore there are now new audio filter types available for the Giga
        engine: new lowpass 1/2/4/6-pole, new highpass 1/2/4/6-pole, new bandpass
 -pole, and finally a bandreject 2-pole filter. You might say that some of
-Line 187 
 end on
+Line 188 
 end on
        some of the new filter types more for certain reasons when creating your
        own gig instruments from scratch.
      </p>
+     <img src="gigedit_new_audio_filter_types.png">
      <h2 id="sfz">SFZ Format Engine</h2>
      <p>
-Line 221 
 end on
+Line 223 
 end on
      <h3 id="script_tab">New "Script" Tab</h3>
      <p>
-       <img src="gigedit_new_patch_vars.png">
        On the right hand side of Gigedit (the main working area actually) there
        is now a new tab "Script" which reveals a list of so called NKSP "patch"
        variables which have been <a href="#patch_variables">described above</a>
        among LinuxSampler's new features.
      </p>
+     <img src="gigedit_new_patch_vars.png" caption="Gigedit's new 'Script' tab">
      <h3 id="sample_info">Sample Properties Dialog</h3>
      <p>
-Line 242 
 end on
+Line 244 
 end on
      <h3 id="gain">More Flexible Gain</h3>
      <p>
        Gain can now be set to any arbitary value between -96 dB .. +96 dB.
+       Previously it was only possible to set gain to max. 0 dB and there was a
+       checkbox which allowed a hard coded boost to exactly +6 dB. The previous
+       appearance replicated the appearance of GigaStudio's original instrument editor.
      </p>
      <p>
      <img src="gigedit_more_flexible_gain_setting.png">
-   Previously it was only possible to set gain to max. 0 dB and there was a checkbox which
+   The previous limitation of having just a single possible value for positive gain
-   allowed a hard coded boost to exactly +6 dB. The previous appearance
-   replicated the appearance of GigaStudio's original instrument editor. The
-   previous limitation of having just a single possible value for positive gain
    was unfortunate, but as it turned out this was actually not a limitation of
    the original gig file format. And in fact we have not added any gig file
    format extension for this reason to achieve this new freedom of arbitrary gain
-Line 270 
 end on
+Line 272 
 end on
    actually have two distinct operations per button: a regular left-mouse click
    for small changes and middle-mouse click for larger changes. Both have been
    adjusted appropriately for the individual synthesis parameters they control.
+      <img src="gigedit_spinbox_fine_tuning_steps.png">
      </p>
-     <img src="gigedit_spinbox_fine_tuning_steps.png">
      <h2 id="libgig">libgig 4.3.0</h2>
      <p>

 Legend:



Removed from v.3887
 


changed lines


 
Added in v.3888
 Legend:



Removed from v.3887
 


changed lines


 
Added in v.3888
-Removed from v.3887
+Added in v.3888

	ViewVC Help
Powered by ViewVC