When a sample event is selected its details are shown in the property panels at the bottom of the editor. These are 2 independent actions, otherwise it would practically impossible to only change one of them. Click and drag vertically to set the fade curve. Move the cursor to the top-left or top-right of a sample event and you'll see that the cursor changes in a pointing hand and a tooltip appears.Ĭlick and drag horizontally to set the fade time. Sample events can have a fade-in and fade-out: to trigger the ADSR on a lowpass filter that will process the sequenced audio. Sample events also send out a MIDI note so audio sequences not only output audio, but also the note events that generate that audio.Īn advantage of that is that you can use these note events in an FX MUX more downstream eg. Of course you can duplicate (a section of a) sample in order to have a separate version.
This also means that when you apply a DSP function on a sample this will affect all places where that sample is used. So the very same samples played by audio events can also be used in MuSampla etc. It is essential to understand that sample events do not contain audio, they link to samples.Īll samples are common to the project. If you want that middle transient to sound snappy like the original then split the sample event in 2 separate sample events so that the first event ends just before the transient and the second event starts with the transient. It is not possible to preserve a transient when it is in the middle of a sample event and when applying time stretching because then the transient will be stretched too which often results in a less snappy transient. So audio sequences can easily play different samples, but they can also play a single sample that is sliced into separate sample events in order to preserve the transients in that sample. So audio sequences can easily play different sections of different samples, each at different pitches and with different time stretch options! That allows for very creative sample sequencing!
You can look at it as if each sample event is a combi of a MIDI note and a built-in sampler, which can play and loop any section of any sample in your project, and time stretch it etc. So instead of the more traditional workflow of using a MIDI note sequence that plays a sampler plugin module somewhere else in the app (eg in a rack slot), MuLab's audio sequences do all that in an integrated way.
Audio sequences are like MIDI sequences but the big difference is that the note events directly play a sample.
0 kommentar(er)
