1
MilkyTracker Support / Re: Multisampled amen break
« on: January 09, 2025, 10:27:46 »
If you want to have your sample slices under one instrument, counting and changing their relative note accordingly is the way to go.
It's not only slow but also limiting because you can't then play the slices at arbitrary pitches from the start. Not every song needs this though, or repeating the same sample mapping for each octave could be enough.
Having each slice as its own instrument is faster to set up and doesn't have this limitation but you may prefer having the slices under one instrument number. It's a matter of personal preference and can depend on what's best for any given module.
There's also the option of keeping the loop intact as one sample and chopping it live with 9xx, which I prefer, but that also comes with its drawback of slower setup of trimming and resampling the loop to make the hits align with the 256-byte offsets of 9xx's granularity. Another limitation of this is that 9xx of course reserves the effect column for the triggering row.
It's not only slow but also limiting because you can't then play the slices at arbitrary pitches from the start. Not every song needs this though, or repeating the same sample mapping for each octave could be enough.
Having each slice as its own instrument is faster to set up and doesn't have this limitation but you may prefer having the slices under one instrument number. It's a matter of personal preference and can depend on what's best for any given module.
There's also the option of keeping the loop intact as one sample and chopping it live with 9xx, which I prefer, but that also comes with its drawback of slower setup of trimming and resampling the loop to make the hits align with the 256-byte offsets of 9xx's granularity. Another limitation of this is that 9xx of course reserves the effect column for the triggering row.
