Importing Drums Sounds - Getting Started with Chiptunes & MilkyTracker (Part 4)
🕑 Added 2018-08-13 14:00:02 +0000 UTCThis is the last video tutorial of a four-part introduction series to MilkyTracker. I’m experimenting with a tutorial structure where I introduce a concept, explain how to achieve it, write some music and show creative uses.
I want to make these tutorials as helpful as possible so feedback is appreciated! What do you like about them, what would you improve? Etc..
--
By the end of this tutorial you should be able to:
- Import samples into MilkyTracker
- Crop samples
- Maps notes to trigger samples
- Change the relative note of samples
Sometimes the sample editor isn’t the greatest for making sounds (drum sounds for example) It’s possible to design drum sounds in the sample editor, but it’s also easier to import them.
There are two ways to organize your drums sounds and samples, as a kit (drums, hi-hat, snare) or as a stand-alone instrument (‘Wut’). Each instrument has a 16-slot sample bank (or kit) and each of those 16 samples can be assigned to certain notes. Once you’ve imported your drum sounds (or any sample for that matter), the trickiest part is assigning those samples to specific pitches and changing the relative note so that it plays at the correct speed/pitch.
In my version of MilkyTracker, immediately after importing a sample, its relative note in the instrument editor changes to F-6 (and fine-tuning changes to -028). I have no idea why it does this. Despite this, the relative note is STILL actually C-4. So, when you import a sample and trigger it on C-4, it plays at the normal speed/pitch. Anybody know why it does this?
Hotkeys used (check manual for PC hotkeys!)
- ESC – Stop playback
- Cmd+F – Trigger Follow Mode
- DELETE – delete selection