Just learned something tonight. Sorry if it’s already been posted but hey anything like this is worth bringing attention to in my opinion!
I’m starting to use my DT as more of a hybrid audio track sequencer. Meaning, some tracks I’m keeping as micro-programmed drum sounds, but others I’m recording full phrases of synths or other stuff and just keeping that track as a full-length audio file with a single trigger.
On the song I’m currently working on I’m just barely running out of tracks for what I want to do, which led me to try this out, and thankfully it works:
THE TRICK: Once a long sample is triggered, you can change sample select to a different sample and it will not change the one currently playing, until it triggers again. This means you can queue up changes in advance, re-using the same track. Of course when you change the sample on that track it’s going to retain whatever effects settings you have etc. SO, my plan is to use one track as a “general flex” slot to bring in extra elements to a song.
Still going to use dedicated tracks for the core parts where I can do more specific balancing/effects/filtering etc. but I really like this idea of a “flex slot” for misc stuff.
I think this allows for a lot of mixing in different stuff throughout a song within one pattern, instead of just being limited to eight “static” sounds, or having to create new patterns. And with sample backup capability now I am not worried about filling up my DT with long audio clips
Also, similar to above, when you mute or unmute a long sample that’s already been triggered, it will keep playing to the end (or not playing if it was previously muted). The mute doesn’t actually mute/unmute the sound, just the event triggers. That has an obvious drawback in not being able to “instantly” mute the sound, BUT also has a cool benefit in that you can queue up mute states both on and off, in advance of the actual trigger (which presumably, if using standard-length phrases, would just be a one-trigger event at the beginning of the first bar).
EDIT: Also just noticed this is very similar to @LyingDalai 's very first post of this thread! but a slightly different side effect/application of the same underlying functionality.