Oh man…my bad. I don’t know why I was thinking you were talking about something else. Now I see what you’re saying. You probably do understand it and I’m over here just making it more confusing.

1 program in a track right?

Yep, one active program at a time per track. It does come in handy like when you can’t decide which instrument you want playing a certain part. Just set up some options and then switch through them for comparison. Also, it’s a nice ability for when you want to send the MIDI data of a track to an external device. For the most part though I’m keeping it 1:1.

I didn’t see anyone recommend TubeDigga yet.

The videos on chopping samples might be the ones to start with. Once you learn how to do it and get good results it becomes addicting.

One reason I make a lot of programs per track is for mixing purposes later.

When you do an export of your song as stems it’s uses programs as the grouping for each stereo track rendered.

So if you load an entire pre-made kit then when you export each drum sound ends up in the same 2-channel file. I prefer each being in separate tracks so as I build my drum kits I make a new program for each drum (kick, snare, hat, etc). Hats usually have 3-4 different samples so those all go I to the same project. Kicks might have 2 or 3 as well.

This also makes it more fun to jam out on using program muting. You can build you drum part up on the fly, process the groups differently, replace them with less effort.