/[svn]/doc/docbase/release_notes/linuxsampler_2_0_0/01_linuxsampler_2_0_0.html
ViewVC logotype

Contents of /doc/docbase/release_notes/linuxsampler_2_0_0/01_linuxsampler_2_0_0.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 2816 - (show annotations) (download) (as text)
Sat Jul 18 19:03:21 2015 UTC (5 years, 3 months ago) by schoenebeck
File MIME type: text/html
File size: 16695 byte(s)
- Further additions to release notes regarding QSampler.

1 <html>
2 <head>
3 <meta name="author" content="Christian Schoenebeck">
4 <title>Release Notes LinuxSampler 2.0.0</title>
5 <navpath>LinuxSampler 2.0.0</navpath>
6 <meta name="description" content="Release notes for LinuxSampler 2.0.0.">
7 <link rel="stylesheet" href="http://doc.linuxsampler.org/css/preview.css">
8 <script type="text/javascript" src="http://doc.linuxsampler.org/js/preview.js"></script>
9 </head>
10 <body>
11 <h1>LinuxSampler 2.0.0</h1>
12 <p>
13 Unbelievable six years have passed since the last release of LinuxSampler.
14 A load of things have changed in silence, which I want to summarize for
15 you in this article.
16 </p>
17
18 <h3>New Sampler Engines</h3>
19 <p>
20 The sampler's code base has seen substantial changes during that long
21 period. The sampler engine code base has been unified to a set of common,
22 abstract base classes which cleared the way for two new sampler engines:
23 <ol>
24 <li>The <b>SFZ2</b> format engine (.sfz).</li>
25 <li>The <b>SoundFont 2</b> format engine (.sf2).</li>
26 </ol>
27 So LinuxSampler is not limited to just the GigaStudio/Gigasampler format
28 (.gig) anymore.
29 </p>
30
31 <h3>Real-Time Instrument Scripts</h3>
32 <p>
33 Another major new feature is the brand new support for so called
34 <i>Real-Time Instrument Scripts</i>, which are small programs that may be
35 bundled with sound files to extend the sampler with custom behavior for
36 individual sounds. You may know such instrument scripts from commercial
37 software samplers. At the moment this scripting feature is yet limited to
38 the Giga format engine. <a href="instrument_scripts.html">Find out more ...</a>
39 </p>
40 <img src="../../gigedit/scripts/gigedit_script_editor.png" caption="NKSP Instrument Script Editor of Gigedit">
41
42 <h3>LSCP Shell</h3>
43 <p>
44 Also noteworthy is the new command line application <i>lscp</i>, which is
45 a text based shell for controlling the sampler from the command line,
46 providing colored output, type completion, help text while typing LSCP
47 commands and other convenient features for terminal enthusiasts who want
48 to use the sampler without GUI frontend applications.
49 <a href="lscp_shell.html">Find out more ...</a>
50 </p>
51 <img src="../../lscp_shell/lscp_shell.png" caption="LSCP Shell">
52
53 <h3>Internal Effects &amp; Extensions to LSCP</h3>
54 <p>
55 You may now also load external effects directly into the sampler. The
56 <a href="http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html">LSCP network protocol</a>
57 (<a href="http://www.linuxsampler.org/api/lscp-1.7.html">v1.7</a>) has
58 been extended to manage such effects respectively. Effect chains may be
59 built, and the individual sampler parts may be routed to an individual
60 position of effect chains. At this point only LADSPA plugins are supported
61 yet. However the sampler's effect subsystem uses an abstract interface,
62 which allows easy integration of other effect systems. Also new with
63 latest LSCP version is the ability to trigger MIDI CCs by LSCP command.
64 </p>
65
66 <h3>New GigaStudio format features</h3>
67 <p>
68 <img src="gigedit_imidi_rules.png">
69 You may have heard that the GigaStudio software has seen its last version
70 with GigaStudio 4. Tascam officially discontinued this product, its
71 intellectual property has been sold several times among companies and
72 there is currently no way to buy a new copy of GigaStudio anymore. However
73 the GigaStudio format is still under active development with LinuxSampler.
74 We not only added support for the latest features introduced with
75 GigaStudio 4: iMIDI rules for example which allow to trigger notes by
76 MIDI CC and allow i.e. defining a set of legato samples; for the first
77 time ever we also added our own extensions to the Giga format: one of it
78 is the previously mentioned new instrument scripting feature and a more
79 minor extension is support for various other MIDI CCs which were never
80 supported by GigaStudio before. So you can now use any MIDI CC for EG1
81 controller, EG2 controller and attenuation controller.
82 </p>
83
84 <h3>DAW Plugin Enhancements</h3>
85 <p>
86 The sampler's host plugins have also seen some enhancements: the LV2
87 plugin now stores and restores the sampler's overall state with the song
88 of your DAW application, the LV2 and AudioUnit plugin's outputs
89 were increased from 2 audio channels to 16 upon request by some users and
90 the VST plugin now uses the sampler's
91 <a href="http://www.linuxsampler.org/api/draft-linuxsampler-protocol.html#MIDI%20Instrument%20Mapping">MIDI instrument mapping system</a>
92 to show a list of available sounds to allow the user to switch among them.
93 And last but not least the VST plugin may also be used on Mac now.
94 </p>
95
96 <h2>Gigedit 1.0.0</h2>
97 <p>
98 <img src="gigedit_format_extension_warnings.png">
99 Also <i>Gigedit</i>, our instrument editor for the GigaStudio/Gigasampler
100 format, had been enhanced quite a lot during the last six years. As
101 mentioned above, we introduced our own extensions to the Giga format.
102 Obviously all those extensions will not work with any GigaStudio version,
103 they only work with a recent version of Gigedit and LinuxSampler. Gigedit
104 will inform you whenever you are using such kind of custom Giga format
105 extension, so that you are always aware in case your changes to sounds are
106 not cross/backward compatible with the GigaStudio software. You may also
107 disable those warnings on the settings menu.
108 </p>
109
110 <h3>Multi-Selection of Dimension Zones</h3>
111 <p>
112 Until now you were only able to edit either exactly
113 one dimension region or all dimension regions simultaneously with gigedit. With this
114 release you may now hold the Ctrl button and select a specific set of
115 dimension region zones in the dimension region selector area (on the very
116 bottom of the Gigedit window) with your mouse. All synthesis parameters you
117 then change, will all be applied to that precise set of dimension region
118 zones.
119 </p>
120 <img src="gigedit_multi_zone_selection.png" caption="Multi-zone selection with Ctrl key">
121
122 <h3>Improvements to Dimension Management</h3>
123 <p>
124 <img src="gigedit_change_dim_type.png">
125 Also managing dimensions has been improved: previously to change the
126 type of a dimension you had to delete and recreate the
127 dimension. Which was not just inconvenient, but you also had to redefine
128 your synthesis parameters from scratch. Now you can just open the
129 dimension manager dialog, double click on the displayed dimension type
130 and select another type for the respective dimension.
131 </p>
132 <p>
133 <img src="gigedit_manage_dims_all_regions.png">
134 Another great enhancement of the dimension manager is the ability to alter
135 the dimensions of all regions of an instrument at once. Previously you had
136 to do that for each region on the keyboard separately. For example to
137 delete a velocity split dimension, you had to double click on a region,
138 delete the velocity dimension with the dimension manager dialog, then
139 double click on the next region, delete the velocity dimension there as
140 well, and so on. Now you can just click on the "All Regions" check box of
141 the dimension manager, select the velocity dimension, click on "Remove"
142 and that's it. Also notice the different display style in this
143 "All Regions" mode, like shown on the screen shot left: Since you are
144 viewing the dimension properties of not just one region, but of all
145 regions of your instrument, we thought we also need to show you in case
146 individual regions differ regarding their precise dimension properties.
147 For example on the screen shot on the left you see that some regions have
148 a velocity dimension with 2 zones, whereas other regions have a velocity
149 dimension with 4 zones instead. Also there seem to be some regions which
150 have a modulation wheel dimension and other regions which do not have a
151 modulation wheel dimension at all. Same applies to the Layer dimension:
152 in this particular example not all regions do have a Layer dimension.
153 However all regions seem to have a Sample Channel (Stereo) dimension,
154 and all regions even have the same amount of zones for that particular dimension.
155 </p>
156
157 <h3>Monitoring Sample References</h3>
158 <p>
159 <img src="gigedit_sample_references.png">
160 When working on complex Giga sounds you certainly noticed that one could
161 easily get lost about which samples are exactly used by which
162 instrument or even whether a sample is actually used at all by any
163 instrument or just left orphaned and wasting disk space. This was also due
164 to the fact that the Giga format does not require unique names for
165 samples. We have worked on resolving this usability issue. In the samples
166 list view you can now read the amount of times a sample is referenced by
167 instruments of your .gig file. If a sample is not used at all, then it
168 will be shown in striking red color in the sample list view. You may also
169 right click on a sample and select "Show references...", a new
170 window appears on your screen which will show you where exactly that
171 particular sample is used by, that is by which instruments and by which
172 regions of those instruments. Also the other way around has been
173 addressed: when you now edit the synthesis parameters of a particular
174 dimension region, you may now click on the new "&lt;- Select Sample"
175 button and Gigedit automatically selects and displays the respective sample
176 in the samples list view, which you then might rename to some more
177 appropriate sample name, or you might check by which other instrument(s)
178 that sample is used by, etc. You want to get rid of all unused samples?
179 Simply right click on the samples list view and select
180 "Remove unused samples", then select "Save" from the menu and all orphaned
181 samples are gone.
182 </p>
183 <img src="gigedit_go_to_sample.png" caption="Find and select used sample">
184
185 <h3>Silent Cases</h3>
186 <p>
187 <img src="gigedit_null_sample.png">
188 You may now also remove the current sample reference from individual
189 dimension regions (assigning a so called "NULL" sample instead) by clicking on
190 the new "X" button next to the sample reference field on the "Sample" tab
191 of a dimension region; this allows you to define "silent cases", that
192 is a case where no sample should be played at all, for example this is
193 often used for very low velocity ranges of i.e. between 0 and 6.
194 </p>
195
196 <h3>Reordering Instruments</h3>
197 <p>
198 <img src="gigedit_reorder_instruments.png">
199 If you are working on .gig files with a large amount of Instruments, then
200 you might also be glad to know that you can finally also re-order the
201 instruments of a file by simply dragging the instruments around in the
202 instruments list view.
203 </p>
204
205 <h3>Combine Tool</h3>
206 <p>
207 <img src="gigedit_combine_tool.png">
208 Another handy new feature for sound designers is the new "Combine" tool,
209 which you can reach from the main menu. It allows you to select two ore
210 more instruments (by holding down the Ctrl key while selecting with mouse
211 left click) from your currently open Giga file and combine those selected
212 instruments to a new instrument. This way you may for example create
213 stunning layered sounds, or you may create velocity splits, crossfade
214 sounds by MIDI controller and much more, all with just a few clicks. This
215 may sound like a trivial task, but if you have worked on this before, you
216 certainly noticed that this was often a very time consuming and error
217 prone task before, especially with complex individual sounds which had
218 custom region ranges, custom velocity splits and much more exotic stuff
219 to take care of. The combine tool handles all such cases for you
220 automatically.
221 </p>
222
223 <h3>Improved Interaction with LinuxSampler</h3>
224 <p>
225 Last but not least, the interaction of Gigedit with LinuxSampler (in so
226 called "live mode") had been improved: When you click on the "Edit"
227 button of a channel strip in QSampler or Fantasia, Gigedit will be
228 launched with the respective instrument automatically being selected.
229 Vice versa you may now also just select another instrument with Gigedit's
230 instrument list view and LinuxSampler will automatically load and play
231 that instrument on the respective sampler part for you. So no more need
232 to switch between the Gigedit window and QSampler/Fantasia window all the
233 time while working on your sounds with Gigedit.
234 </p>
235
236 <h2>QSampler 0.3.0</h2>
237 <p>
238 <img src="qsampler_sf2_selection.png">
239 As new sampler formats made it into LinuxSampler, this was also addressed
240 with QSampler. The sound selection dialog now also enumerates the sounds
241 of a selected SoundFont file. And to ease switching between sounds, you
242 may now click on the name of the current instrument of a channel strip,
243 a list will popup that alows you to quickly switch to another sound,
244 without having to open the channel strip's detailed part dialog.
245 </p>
246 <img src="qsampler_quick_switch.png" caption="Drop down list for fast switching between instruments">
247
248 <h3>Suppressing Error Popups</h3>
249 <p>
250 In the past, error message dialogs frequently popped up on the screen.
251 Most of them were just telling unuseful messages, even if the overall
252 operation with the sampler was working correctly. There is now an "ignore"
253 check box attached to those error message dialogs, which allow you to
254 suppress most of the annoying error messages.
255 </p>
256
257 <h3>Improved Mac Support</h3>
258 <p>
259 Recently we created a convenient installer for Mac OS X, which
260 conveniently installs all our software components on your Mac. So that
261 includes the stand-alone version of the LinuxSampler backend, VST and
262 AudioUnit plugin version of the sampler, "Fantasia" and "QSampler" frontends,
263 our instrument editor "Gigedit", the LSCP shell and various other command
264 line tools. You may also choose only some of them to be installed.
265 </p>
266 <img src="http://download.linuxsampler.org/pix/screenshots/mac_installer_1.jpg">
267 <p>
268 Using the sampler has also been improved on Mac. Before you first had to
269 launch the LinuxSampler backend separately and then launch QSampler.
270 Sometimes the sampler backend even had to be killed explicitly. Now
271 you can just click on the QSampler icon and it will automatically spawn
272 the sampler backend for you and shows its output on QSampler's integrated
273 terminal section. When you quit QSampler, it will also stop the sampler backend
274 for you automatically (you may tell QSampler to keep the sampler running in the background).
275 </p>
276
277 <h2>libgig 4.0.0</h2>
278 <p>
279 Our fundamental file access C++ library
280 <a href="http://download.linuxsampler.org/doc/libgig/api/">libgig</a>
281 is now more than just a supporter of the GigaStudio/Gigasampler file
282 format. New file formats have been added and are now bundled with libgig:
283 <ol>
284 <li>
285 <a href="http://download.linuxsampler.org/doc/libgig/api/namespaceKorg.html">
286 Classes for KORG's sample based instrument files
287 </a> (.KSF, .KMP).
288 </li>
289 <li>
290 <a href="http://download.linuxsampler.org/doc/libgig/api/namespacesf2.html">
291 Classes for SoundFont v2 files
292 </a> (.sf2).
293 </li>
294 <li>
295 <a href="http://download.linuxsampler.org/doc/libgig/api/classResource.html">
296 Classes for AKAI sampler data.
297 </a>
298 </li>
299 </ol>
300 Various command line tools have been added to libgig, which allow to
301 dump, correct, extract and convert sounds between those various file formats.
302 Refer to the individual <i>man pages</i> for details about how to use
303 those new command line tools. As you can see, the ground had been prepared
304 for further new sampler engines with LinuxSampler to come.
305 </p>
306
307 </body>
308 </html>

  ViewVC Help
Powered by ViewVC