ViewVC logotype

Contents of /doc/docbase/release_notes/linuxsampler_2_1_1/01_linuxsampler_2_1_1.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 3542 - (show annotations) (download) (as text)
Sat Jul 27 22:33:53 2019 UTC (11 months, 1 week ago) by schoenebeck
File MIME type: text/html
File size: 8646 byte(s)
* Added release notes for LinuxSampler 2.1.1.

1 <html>
2 <head>
3 <meta name="author" content="Christian Schoenebeck">
4 <title>Release Notes LinuxSampler 2.1.1</title>
5 <navpath>LinuxSampler 2.1.1</navpath>
6 <meta name="description" content="Release notes for LinuxSampler 2.1.1.">
7 <link rel="stylesheet" href="https://doc.linuxsampler.org/css/preview.css">
8 <script type="text/javascript" src="https://doc.linuxsampler.org/js/preview.js"></script>
9 </head>
10 <body>
11 <h1>LinuxSampler 2.1.1</h1>
12 <p>
13 LinuxSampler 2.1.1 and friends were released on July 27th 2019.
14 This is mainly a maintenance release with fixes of the
15 <a href="01_linuxsampler_2_1_0.html">previous release</a>. So the
16 release notes will be quite short this time since there are only very
17 few and minor new features in this release.
18 </p>
20 <h3>Upcoming C++11 Requirement</h3>
21 </p>
22 Please note that this will most probably be the last release still supporting
23 compilers which are not C++11 compliant. There are plans for new engine
24 features for the next major release of the sampler which will strictly rely on
25 C++11 support by the compiler. Because some of the planned new features
26 are hardly feasible without C++11 language support at all and maintaining
27 legacy support for such old compilers simply no longer makes sense.
28 </p>
30 <h3>Real-Time Instrument Scripts</h3>
31 <p>
32 Behaviour of the built-in <a href="01_nksp.html">NKSP</a> functions
33 <code lang="nksp">change_sustain()</code>,
34 <code lang="nksp">change_cutoff_attack()</code>,
35 <code lang="nksp">change_cutoff_decay()</code>,
36 <code lang="nksp">change_cutoff_sustain()</code>,
37 <code lang="nksp">change_cutoff_release()</code> have been fixed.
38 <a href="instrument_scripts.html">Find out more ...</a>
39 </p>
41 <h3>SFZ Engine</h3>
42 <p>
43 The sfz engine adds support for the commonly used built-in sample
44 <code lang="none">'*silence'</code> of the sfz format. See the
45 <code lang="sfz">sample</code> opcode for details. It does what you
46 think it does; it
47 instructs the sampler to play no sound at all. This is commonly used
48 in sfz files for instance for the lowest velocity switch to not play any
49 sample. With the previous release trying to load sfz files which used this
50 built-in sample caused a file loading error. There are various other
51 commonly used built-in samples in sfz files which you can denote by the
52 leading star character in the sample name, however the <code lang="none">'*silence'</code> one is
53 currently the only supported built-in sample by our sfz engine yet. Trying
54 to load sfz files which are using other built-in samples does not prevent
55 your instrument from being loaded by the sampler, however you will get a
56 warning message on the console that the built-in sample is not supported
57 yet and the sampler will simply play silence for that non supported
58 built-in sample.
59 </p>
61 <h3>GigaStudio Format Engine</h3>
62 <p>
63 The Giga format engine adds a format extension which allows sound
64 designers to define whether release trigger samples shall be played when
65 the sustain pedal is released. In the previous release this was actually
66 the default behaviour by the sampler, but meanwhile there was a consensus
67 on the
68 <a href="https://sourceforge.net/projects/linuxsampler/lists/linuxsampler-devel">mailing list</a>
69 that release samples being triggered by sustain pedal
70 is not the common, expected behaviour. So this is no longer the default
71 behaviour by the sampler, but you can still opt in to this old behaviour by using this
72 new format extension option (see Gigedit changes below for details). If you
73 don't enable this option then release samples are now only triggered by
74 note-off events.
75 </p>
77 <h2>Gigedit 1.1.1</h2>
78 <p>
79 Our instrument editor for the GigaStudio/Gigasampler format received
80 primarily fixes as well, but also the following few new features.
81 </p>
83 <h3>File Format Version</h3>
84 <p>
85 <img src="gigedit_file_format_v4_select.png" title="File Format Selection">
86 From the file properties dialog you can now choose to specifically save a
87 gig file in GigaStudio v4 file format (from the main menu select
88 "File" -> "Properties" -> "File Format"). So you can override the file
89 format version of already existing gig files that way.
90 </p>
92 <h3>Release Trigger Options</h3>
93 <p>
94 <img src="gigedit_release_trigger_whence.png" title="Release Trigger Options">
95 There is now a combo box and checkbox on "Misc" tab which allow to define
96 when precisely release trigger samples shall be played. This is an
97 extension of the original gig file format. You have the option to play
98 release trigger samples only on note-off events, or only on
99 sustain pedal up events, or both on note-off events and on sustain pedal
100 up events. These are options on dimension region level, so you can
101 override this behaviour even for individual cases, not just for the
102 entire instrument.
103 </p>
105 <h3>Script Slots Tooltip</h3>
106 <p>
107 <img src="gigedit_scripts_tooltip.png" title="Script Slots Tooltip">
108 When working on gig files with more than one real-time instrument script
109 per file, it was sometimes a bit tedious to keep track of which instrument
110 was using which script exactly, because it involved a right-click on the
111 individual instrument to get to the script slots dialog of the instrument,
112 which finally listed the scripts being used. You no longer have to do that
113 just to check which scripts are being used: Just hover your mouse over the
114 "Scripts" column of the instruments table on the left hand side of
115 gigedit; a coloured popup will appear with the list of scripts currently
116 being assigned to the instrument.<br>
117 <br>
118 Likewise it is a very common task to remove all scripts from an
119 instrument. There is now a keyboard shortcut for that: Just select the
120 instrument from the instruments list and then hit
121 <b>Shift</b> (&#8679;) + <b>Backspace</b> (&#9003;).
122 </p>
124 <h3>Beginners' Tooltips</h3>
125 <p>
126 <img src="gigedit_menu_tooltips_for_beginners.png" title="Beginners' Tooltips">
127 Gigedit provides a large number of tooltips when you are hovering your
128 mouse over the huge amount of individual controls and menu items the
129 application is offering in the meantime. In case you find that annoying,
130 you can now disable those particular tooltips which are specifically
131 intended for beginners from the main menu by unchecking "View" ->
132 "Tooltips for Beginners". All other tooltips that are still useful for
133 daily work with gigedit are still being shown when this option is
134 unchecked.
135 </p>
137 <h3>Function Keys</h3>
138 <p>
139 The previous release of gigedit introduced "Macros" for quickly
140 performing frequently used sequences of editor actions, and you were able
141 to assign your macros to keyboard function keys F1 .. F12. In this release
142 you can now also assign macros to function keys up to F19, in case you own
143 one of those keyboards with such a large amount of function keys.
144 </p>
146 <h2>libgig 4.2.0</h2>
147 <p>
148 Our fundamental file access C++ library
149 <a href="https://download.linuxsampler.org/doc/libgig/api/">libgig</a>
150 has also received primarily corrections and improvements, which are outlined next.
151 </p>
153 <h3>GigaStudio v4</h3>
154 <p>
155 This release of libgig contains important fixes concerning the
156 GigaStudio v4 format. For instance in the previous release gig v4 files
157 were falsely detected as gig v2 files by libgig, which was leading to
158 numerous undesired behaviours.
159 </p>
161 <h3>Extension Files</h3>
162 <p>
163 It is now possible to write large gig files splitted over extension
164 files (.gx01, .gx02, ...). Previously it was only possible to read gig
165 files with extension files, but libgig only supported to save large gig
166 files as one single, monolithic gig file. The problem with the latter
167 was that gig files >= 2 GB could only be read by libgig, but could not
168 be loaded with any version of GigaStudio. So this solves that legacy
169 support issue, and you have the freedom to switch between a single, large
170 gig file or rather this extension file based format at any time.
171 </p>
173 </body>
174 </html>

  ViewVC Help
Powered by ViewVC