/[svn]/doc/docbase/release_notes/linuxsampler_2_1_0/01_linuxsampler_2_1_0.html

Diff of /doc/docbase/release_notes/linuxsampler_2_1_0/01_linuxsampler_2_1_0.html

Parent Directory | Revision Log | View Patch Patch

-revision 3392 by schoenebeck,
Sun Nov 26 23:15:52 2017 UTC
+revision 3393 by schoenebeck,
Wed Dec  6 17:55:45 2017 UTC
 Line 70
        <code lang="sfz">script</code> opcode for this purpose. So NKSP scripts
        are no longer limited to our Giga engine.
      </p>
+     <p>
+       And yes, as you can see from the SFZ opcode links here, we also
+       started documenting the actual SFZ file format. You wanna help us
+       on completing the SFZ file format documentation? Great! Have a look
+       at <a href="01_writing_docs.html">how articles are written for this site</a> and
+       <a href="https://sourceforge.net/projects/linuxsampler/lists/linuxsampler-devel">get in touch with us</a>!
+     </p>
      <h3>New GigaStudio format features</h3>
      <p>
-Line 82
+Line 89
        Most notably you
        now have options to control envelope generators' state machines.
        For example you can now define whether a certain EG state should
-       either be aborted or continued to its end when a note off arrived.
+       either be aborted or continued to its end when a note off arrived
+       (or on a note on in the release stage).
        These controls are especially useful for certain kinds of sounds
        like percussive instruments.<br>
        <br>
-Line 148
+Line 156
        script editor's "Apply" button or using Ctrl+S keyboard shortcut, then
        the script is automatically reloaded by the sampler. So you no longer
        have to reload the respective instrument manually while you are
-       developing instrument scripts. There are also visual enhancements for the
+       developing instrument scripts.<br>
+       <br>
+       There are also visual enhancements for the
        script editor, for example the line numbers are now shown on the left,
        the font size can be altered by the user, and unused code portions (i.e.
        disabled by <a href="01_nksp.html#preprocessor_statements">NKSP preprocessor statements</a>)
        are automatically striked through. That way you can immediately see
-       which code portions of your scripts are actually used, and which are not.<br>
+       which code portions of your scripts are actually used, and which are not.
+       Everything you see striked through is completely ignored by the sampler.<br>
        <br>
        As as side note, you may have noticed a handy new built-in preprocessor
        condition in LinuxSampler 2.1.0 which can be enabled with
-Line 166
+Line 177
      <h3>Macros</h3>
      <p>
        Another major new feature in this release are macros.
-       A macro is a set of changes that should be applied to currently selected instrument.
+       A macro is a set of changes that should be applied to the currently selected instrument.
      </p>
      <p>
        <img src="gigedit_macros_setup.png" title="Macro List (Gigedit)">
        Such macros can be reviewed and edited, and they can be saved permanently for
-       example as templates for common instrument creation tasks. Macros can be
+       as templates for common instrument creation tasks. Macros can be
-       assigned to F keys on the keyboard so that they can be quickly triggered,
+       assigned to F keys on the keyboard so that they can quickly be triggered,
        you can transfer them over the OS clipboard and you can write comments
        to your macros so that you never forget what kind of purpose you had in
-       mind for them. The macro features are based on libgig's new
+       mind for them. Your macros will also appear in the application's menu,
+       and when you move the mouse pointer over a macro, a tooltop appears with
+       the comments you wrote for that macro.
+       The macro features are based on libgig's new
        "Serialization" framework (described below) and accordingly you need at
        least libgig 4.1.0 for using these macro features.
      </p>
-Line 190
+Line 204
        upcoming work, only those few parameters are modifed by this macro and all
        other ones are left untouched.
        Of course you can also alter the individual parameter values in
-       this editor as well.
+       this editor as well.<br>
+       <br>
+       You might now think, wait a minute, does such a macro change the entire
+       instrument, or only a portion of it? The answer is simple: you decide!
+       The precise scope a macro is going to modify behaves exactly the same like
+       you manually changed individual parameters in Gigedit before. That means
+       for example when you check the two check boxes "all regions" and "all dimension splits",
+       then when you trigger a macro, it is going to applied against the entire instrument.
+       If you uncheck those check boxes and select only one specific region and one specific
+       dimension region zone, then the macro only modifies this single dimension
+       region zone. Or yet another alternative: Ctrl+click the precise dimension
+       region zones you want to be changed by the macro and then trigger the macro.<br>
+       <br>
+       So as you might see, macros introduce a powerful way for you to create yourself
+       a personal instrument construction kit, not limited to only creating global
+       templates for entire instruments, but also for an arbitrary set of small and large
+       building blocks in any size and complexity you need. For example you may create a macro
+       which only sets one single parameter, and another macro which configures an entire filter
+       block with all its filter parameters and controllers, up to a macro which really
+       modifies every single parameter to build up an entire instrument with one stroke
+       of a key.
      </p>
      <h3>Persistent Settings</h3>
      <p>
        All user settings of gigedit are now persistently saved and automatically
-       restored. This also includes gigedit's windows' dimensions and positions.
+       restored. This also includes gigedit's windows' dimensions and positions,
+       and of course including all macros you create.
      </p>
      <h3>Multi-Row Selection</h3>
-Line 237
+Line 272
      <h3>Keyboard Shortcuts</h3>
      <p>
       Various new keyboard shortcuts have been added so you can work more
-      efficiently on your sounds. For example you can now use Ctrl+Left and
+      efficiently on your sounds. For example you can now use Ctrl+Up and Ctrl+Down
+      to switch between instruments, or use Ctrl+Left and
       Ctrl+Right to navigate through all regions of the currently selected
       instrument, and likewise you can use Alt+Left, Alt+Right, Alt+Up and
       Alt+Down to navigate through all dimension region zones of the currently
       selected region. Since there are many actions that can be either applied
-      on instrument level, or on region level, or on dimension region level, as
+      on file level, instrument level, on region level, or on dimension region level, as
-      a general rule, for all keyboard shortcuts:
+      a general rule of thumb for all keyboard shortcuts:
       <ul>
-        <li><b>Shift</b> key is used for actions on instrument level</li>
+        <li><b>Shift</b> key (&#8679;) is used for global actions</li>
-        <li><b>Ctrl</b> key is used on region level</li>
+        <li><b>Ctrl</b> key (&#8984; key on Mac) is used on region level</li>
-        <li><b>Alt</b> key is used by gigedit for actions on dimension region level</li>
+        <li><b>Alt</b> key (&#8997; key on Mac) is used by gigedit for actions on dimension region level</li>
       </ul>
       So as another example you may copy all parameters of the currently
-      selected dimension region zone by hitting Alt+C, then you might select
+      selected dimension region zone to the clipboard by hitting Alt+C.
-      another dimension region zone, or another instrument and then use Alt+V
+      Now when you change parameters of the selected dimension region,
-      to apply the parameters from the clipboard. While the parameters are
+      the original parameters are still there on the clipboard. Hit
-      (as macro actually) on the clipboard you can also review, edit and
+      Alt+X to review or even edit the parameters directly on the clipboard.
-      delete the individual parameters before applying them. As a final
+      Then select a dimension region zone, or another instrument and then use Alt+V
-      example for new important shortcuts you may now use Shift+Up and
+      to apply those parameters from the clipboard to the now selected dimension region.
-      Shift+Down for switching between instruments.
+      You want to keep those parameters on the clipboard permanently in the editor
+      for other instruments in future? Hit Ctrl+M to open the macro list, then hit
+      Ctrl+B to save the content on the clipboard permanently as a new macro.
+      From this point you can also simply duplicate the macro, fine tune and
+      adjust the cloned macros and so on. All macros are saved along with the settings
+      of the application. So they will always be there next time you launch gigedit,
+      and no matter on which gig files you are working on.
+     </p>
+     <p>
+      Too many shortcuts to remember? Of course you can find all keyboard
+      shortcuts from the menus and on the individual buttons. Simply place
+      the mouse pointer over the individual menu items or buttons and a tooltip
+      will explain what the action would do. For menu items and buttons you use
+      frequently, start using their displayed keyboard shortcuts instead.
+      And the ones you really are going to use frequently, you will remember as shortcut
+      in a very short time.
      </p>
      <h3>Combine Tool Improvements</h3>
-Line 266
+Line 317
        (multiple) instruments you want to combine directly from the applications
        main window, i.e. by Ctrl or Shift clicking them from the instruments
        list view, and then right click to call the combine tool on that
-       selection. The Combine Tool now also shows you as preview the order in
+       selection or even faster; simply hit Ctrl+j ("j" as in "join").
+       The Combine Tool now also shows you a preview of the order in
        which the selected instruments are going to be combined. This is
        especially useful when combining instruments with certain dimension
-       types where the order matters for the actual resulting sound; for example
+       types where the order significantly matters for the actual resulting sound; for example
-       when using the velocity dimension. Simply use drag n drop to reorder
+       when combining by velocity dimension. Simply use drag n drop to reorder
-       the previously selected instruments before combining them.
+       the previously selected instruments before combining them finally
+       (by clicking on Ok or simply hitting Enter).
      </p>
      <h3>Search Filter</h3>
-Line 280
+Line 333
        And last but not least a filter option field had been added to the
        instruments list view and samples list view, which allows you to find specific
        samples and instruments very quickly by typing search key words, which is
-       especially very helpful in case you are working on gig files which contain
+       especially very helpful in case you are working on huge gig files which contain
        a very large amount of samples or instruments in a single gig file
        (like this one, which apparently has far more than 400 instruments).
      </p>
-Line 292
+Line 345
        has also received some major improvements, which are outlined next.
      </p>
-     <h3>Files larger than 2 GB</h3>
+     <h3>Files larger than 4 GB</h3>
      <p>
-       libgig 4.1.0 adds support for files much larger than 2 GB for GigaStudio /
+       libgig 4.1.0 adds support for writing files much larger than 4 GB
-       Gigasampler (.gig), DLS, as well as for RIFF files in general. This file size
+       (or more exactly: up to now 16 Exabyte = 16 777 216 Terabyte)
+       for GigaStudio / Gigasampler (.gig), DLS, as well as for RIFF files in general. This file size
        limitation existed for a very long time due to the RIFF format's historical,
        internal 32 bit file offsets. To circumvent this file size limitation the
        concept of so called "extension files" was added in the past to the
-Line 318
+Line 372
        is already a broad standard. Accordingly instead of adding write support for
        extension files in libgig, the problem was addressed at its root by
        transparently using appropriate, automatic file offset sizes. So when writing
-       .gig/DLS/RIFF files smaller than 2 GB there are still 32 bit file offsets
+       .gig/DLS/RIFF files smaller than 4 GB there are still 32 bit file offsets
        being used by libgig. Accordingly such files are still backward compatible
-       with older software. However if the overall file size to be written is 2 GB or
+       with older software. However if the overall file size to be written is 4 GB or
        larger, then 64 bit file offsets are automatically used by libgig instead.
-       Note though that due to that circumstance such files &#8807; 2 GB are not backward
+       Note though that due to that circumstance such files &#8807; 4 GB are not backward
        compatible with older versions of libgig, nor could they be loaded with the
        original GigaStudio software.
      </p>

 Legend:



Removed from v.3392
 


changed lines


 
Added in v.3393
 Legend:



Removed from v.3392
 


changed lines


 
Added in v.3393
-Removed from v.3392
+Added in v.3393

	ViewVC Help
Powered by ViewVC