| 1 |
Version 1.0.0 (30 July 2009) |
Version 2.1.1 (27 Jul 2019) |
| 2 |
|
|
| 3 |
|
This is a maintenance release with various fixes. There are only two |
| 4 |
|
minor new features in this release: |
| 5 |
|
|
| 6 |
|
The Giga format engine adds a format extension which allows sound |
| 7 |
|
designers to define whether release trigger samples shall be played when |
| 8 |
|
the sustain pedal is released. In the previous release this was actually |
| 9 |
|
the default behaviour by the sampler, but meanwhile there was a consensus |
| 10 |
|
on the mailing list that release samples being triggered by sustain pedal |
| 11 |
|
is not the common, expected behaviour. So this is no longer the default |
| 12 |
|
behaviour, but you can still opt in to this old behaviour by using this |
| 13 |
|
new format extension option (i.e. by using latest release version of |
| 14 |
|
libgig and gigedit and enabling the respective checkbox for your |
| 15 |
|
gig instrument). If you don't enable this option then release samples are |
| 16 |
|
now only triggered by note-off events. |
| 17 |
|
|
| 18 |
|
The sfz engine adds support for the commonly used built-in sample |
| 19 |
|
'*silence' of the sfz format. It does what you think it does; it |
| 20 |
|
instructs the sampler to play no sound at all. This is commonly used |
| 21 |
|
in sfz files for instance for the lowest velocity switch to not play any |
| 22 |
|
sample. With the previous release trying to load sfz files which used this |
| 23 |
|
built-in sample caused a file loading error. There are various other |
| 24 |
|
commonly used built-in samples in sfz files which you can denote by the |
| 25 |
|
leading star character in the sample name, however the '*silence' one is |
| 26 |
|
currently the only supported built-in sample by our sfz engine yet. Trying |
| 27 |
|
to load sfz files which are using other built-in samples does not prevent |
| 28 |
|
your instrument from being loaded by the sampler, however you will get a |
| 29 |
|
warning message on the console that the built-in sample is not supported |
| 30 |
|
yet and the sampler will simply play silence for that non supported |
| 31 |
|
built-in sample. |
| 32 |
|
|
| 33 |
|
Version 2.1.0 (25 November 2017) |
| 34 |
|
|
| 35 |
|
This release adds a large amount of extensions and improvements for the |
| 36 |
|
real-time instrument scripting support of LinuxSampler (NKSP). |
| 37 |
|
For example 48 new built-in NKSP functions and 21 new built-in NKSP |
| 38 |
|
variables have been added. Also the NKSP language itself was extended. |
| 39 |
|
Most notably the script engine now has an execution scheduler which is |
| 40 |
|
the basis for many of the timing relevant new NKSP features in this |
| 41 |
|
release, like programmatically suspending and resuming scripts for an |
| 42 |
|
exact amount of time or triggering or killing notes at very precise |
| 43 |
|
times. Bitwise operators have been added to NKSP, as well as support for |
| 44 |
|
read only built-in variables, "synchronized" code blocks |
| 45 |
|
("synchronized .. end synchronized"), user declared functions and user |
| 46 |
|
declared const array variables have been added to the NKSP language, |
| 47 |
|
and automatic suspension of RT threatening scripts by the RT script engine |
| 48 |
|
has been implemented. Also syntax error messages with NKSP scripts have |
| 49 |
|
been improved to output more clear and user friendly error messages, as |
| 50 |
|
well as NKSP editor API has been improved which brings handy new features |
| 51 |
|
to gigedit's NKSP script editor like automatically graying out code blocks |
| 52 |
|
which are disabled by NKSP preprocessor statements. |
| 53 |
|
|
| 54 |
|
The SFZ engine now supports <global>, <master>, #define and set_ccN |
| 55 |
|
statements. And finally the SFZ engine now supports NKSP real-time |
| 56 |
|
instrument scripts as well by adding a new "script" opcode. |
| 57 |
|
|
| 58 |
|
Also the Instruments Database feature has received important maintenance |
| 59 |
|
fixes. Before this release the instrument DB feature was barely usable |
| 60 |
|
for quite some time. Fundamental instruments DB issues have been fixed in |
| 61 |
|
this release to finally consider this feature stable again. |
| 62 |
|
|
| 63 |
|
And finally this release provides a huge amount of general bug fixes. |
| 64 |
|
|
| 65 |
|
Version 2.0.0 (15 July 2015) |
| 66 |
|
|
| 67 |
|
The sampler's code base has seen substantial changes in the last six years, |
| 68 |
|
since the last release of LinuxSampler. The sampler engine code base has |
| 69 |
|
been unified to a set of abstract base classes which cleared the way for |
| 70 |
|
two new sampler engines: The SFZ2 format engine (.sfz) and the SoundFont 2 |
| 71 |
|
engine (.sf2). So LinuxSampler is not limited to the GigaStudio/Gigasampler |
| 72 |
|
format (.gig) anymore. Another major new feature is support for real-time |
| 73 |
|
instrument scripts, which may be bundled with sound files to extend the |
| 74 |
|
sampler with custom behavior for individual sounds. You may know such scripts |
| 75 |
|
from commercial software samplers. Find out more about instrument scripts |
| 76 |
|
on http://doc.linuxsampler.org/Instrument_Scripts/. At the moment this |
| 77 |
|
scripting feature is yet limited to the Giga format engine. Also noteworthy |
| 78 |
|
is the new command line application "lscp", which is a text based shell for |
| 79 |
|
controlling the sampler from the command line, providing colored output, |
| 80 |
|
type completion, help text while typing LSCP commands and other convenient |
| 81 |
|
features. You may now also load external effects directly into the sampler |
| 82 |
|
(only LADSPA plugins yet). The LSCP network protocol (v1.7) has been extended |
| 83 |
|
to manage such effects respectively. Also new with latest LSCP version is the |
| 84 |
|
ability to trigger MIDI CCs by LSCP commands. You may have heard that the |
| 85 |
|
GigaStudio software has seen its last version with GigaStudio 4. Tascam |
| 86 |
|
officially discontinued this product, its intellectual property has been sold |
| 87 |
|
several times among companies and there is currently no way to buy a new copy |
| 88 |
|
of GigaStudio anymore. However the GigaStudio format is still under active |
| 89 |
|
development with LinuxSampler. We not only added support for the latest |
| 90 |
|
features introduced with GigaStudio 4: iMIDI rules for example which allow to |
| 91 |
|
trigger notes by MIDI CC and allow i.e. defining a set of legato samples; for |
| 92 |
|
the first time ever we also added our own extensions to the Giga format: one |
| 93 |
|
of it is the previously mentioned new instrument scripting feature and a more |
| 94 |
|
minor extension is support for various other MIDI CCs which were never |
| 95 |
|
supported by GigaStudio before. The sampler's host plugins have also seen |
| 96 |
|
some enhancements: the LV2 plugin now stores and restores the sampler's |
| 97 |
|
overall state with your DAW application's song, the LV2 and AudioUnit |
| 98 |
|
plugin's outputs were increased from 2 audio channels to 16 upon request by |
| 99 |
|
some users and the VST plugin now uses the sampler's MIDI instrument mapping |
| 100 |
|
system to show a list of available sounds to allow the user to switch among |
| 101 |
|
them. And last but not least the VST plugin may also be used on Mac now. |
| 102 |
|
|
| 103 |
|
Version 1.0.0 (31 July 2009) |
| 104 |
|
|
| 105 |
This is the first release which allows the sampler to be used as audio |
This is the first release which allows the sampler to be used as audio |
| 106 |
host plugin, namely supporting the standards VST, AU, DSSI and LV2. The |
host plugin, namely supporting the standards VST, AU, DSSI and LV2. The |
Parent Directory
| 
Revision Log
| 
Patch