03-03-21, 06:21 -
(22-02-21, 00:05)noek Wrote: Hi Ken,
OK, maybe I can help or inspire you as we use various repeating samples in our group.
First of all, the retrigger feature you use is mainly for making natural instruments sound more "fat" by mimicking a resonance box (the body of a guitar, the woodwork of piano etc). Not fit for the hip hop way of using samples.
Thanks for the detailed reply. I don't think I used a good example, as I am looking at accomplishing something less comprehensive than what you outlined.
Here's my thought process based on the documentation, without it being tied to a type of music.
Code:
%mode
the way that the box handles note-off and loop markers:
- once "Playback": play sample from start to end ignoring standard note-off.
Pressing a key will send a note-on message and will start playback from the beginning of the sample.
Releasing that key will send a note-off message, but it will be ignored.
Code:
%retrigger
What happens when same note is played again:
R Noteoff, fadeout according release time value.
D Noteoff, fadeout according damp time value.
Y Yes, retrigger is allowed, keep the playing sound
If retrigger is "Y", pressing a key will send a note-on message and will start playback from the beginning of the sample.
Releasing that key will send a note-off message, but it will be ignored.
Pressing the same key while the sample is playing will send a note-on message and will start playback from the beginning of the sample.
Any previous playback will continue until the sample ends.
I understand now why setting retrigger to "Y" results in instances of the sample playing at once.
I introduced a mutegroup into the configuration in an attempt to stop the previous instance of the sample.
I thought perhaps the key/note would "see" itself as a part of the same group and stop itself.
It makes sense why this doesn't work the way I initially thought. So let's forget setting retrigger to Y.
If retrigger is "R", pressing a key will send a note-on message and will start playback from the beginning of the sample.
Releasing that key will send a note-off message, but it will be ignored.
Pressing the same key will the sample is playing will send a note-on message and will start playback from the beginning of the sample.
If a previous instance of playback was playing, that previous instance will fade out according to the release time value.
When working with a release of %%release=1, %%retrigger=R, and %%once, I can achieve the desired behavior when I press the key/note twice.
I press a key and the sample plays. If I press the same key again, a second instance of the sample will start. And the first instance will fade out immediately (like a note-off message because of %%release=1).
This makes sense given the documentation, and I didn't have to use a mutegroup. SUCCESS!
Unfortunately the behavior only works if the sample is triggered/played twice. I can trigger the sample twice quickly. Or I can trigger the sample once, wait for a few seconds, and then trigger it a second time.
As soon as I attempt to trigger the sample a third time, the samples begin to "stack" again.
If I have to guess, this is because the %release fade out is implemented? I'll think about it some more.