User manual

Table Of Contents
254
The Sample Editor
8. To make the loop follow any further tempo changes,
make sure the track is set to “Musical time base” by using
the respective button in the Track list or Inspector (the
button should show a note symbol – see “Switching bet-
ween musical and linear time base” on page 42).
Note that if the project tempo is lower than the original
tempo of the loop, there may be audible gaps between
each slice event in the part.
This can be remedied by using the Close Gaps function on the Ad-
vanced submenu of the Audio menu, see “Close Gaps” on page 258.
You should also consider activating auto fades for the respective audio
track – fade-outs set to about 10 ms will help eliminate any clicks be-
tween the slices when you play back the part. See “Fades, crossfades
and envelopes” on page 87.
If the project tempo is higher than the loop’s original
tempo, you may want to activate auto crossfades for the
track.
You can use the Close Gaps functions in this case as well, see “Close
Gaps” on page 258.
Editing hitpoints
In this section, we go back a bit and look at what can be
done with hitpoints in the Sample Editor. There are two
ways to invoke the hitpoint calculation:
Use the sensitivity slider on the Hitpoints tab of the
Sample Editor Inspector.
Select Calculate Hitpoints from the Hitpoints submenu
on the Audio menu.
For some loops, this may be all that is needed to set the
hitpoints so that each slice to be created will contain a
single “hit” or sound. However, there will almost certainly
be cases when the automatic calculation may add a hit-
point where there shouldn’t be one, and fail to add a hit-
point where one is needed, even if the sensitivity slider is
set to maximum. If there are too many or too few hitpoints
in a loop, it will most probably not play back properly.
When this occurs, you have to edit the hitpoints manually
in the Sample Editor.
Auditioning slices
A slice is a section of the waveform, from one hitpoint to
the next.
The first thing you should do before editing hitpoints is to
listen to each slice in the Sample Editor to determine what
they contain. The aim is to avoid “double hits”, like a snare
hit being followed by a hi-hat hit within the same slice. You
also want to determine whether any hitpoints have been
added that should be removed:
1. Open a loop in the Sample Editor.
If you have already created slices, you can open them in the Sample Ed-
itor by double-clicking any event in the Audio Part Editor. If it is a new
loop, follow the instructions below.
2. Open the Hitpoints tab and select the Edit Hitpoints
tool.
When you point in the waveform display, the pointer changes to a
speaker icon.
Click on this button to edit hitpoints