On the Mixer tab, make sure the Kick track is not muted, and then mute all other tracksġ3. In the upper right corner, click the memory usage meter, turn on the Cached switch and click Unload Drum Samples to save memoryġ4. Add another instrument track and name it Snare Topġ5. Copy the SD3 plug-in instance from the Kick track to the Snare track’s Instrument insertġ6. (I use a custom path from my sample libraries, rather than the default of C: drive, so, for example, my SD2 libraries are under S:ToontrackSuperior. Repeat steps 4 to 15 to setup the Snare Top track, and to setup individual tracks for all other drum instrumentsġ7. Create a new instrument track and name it Drum MIDIġ8. In the LUNA mixer’s Drum MIDI channel strip, click MIDI Outputġ9. In the routing pane, scroll down to reveal the MIDI inputs for the Kick, Snare Top, and other drum tracksĢ0. Add a programmed drum MIDI region to the Drum MIDI track Holding down the Command key, click the Kick’s All MIDI channel, the Snare Top’s All MIDI channel, and the rest of the drum kit’s individual tracks’ All MIDI channelsĢ1. The MIDI region’s output will trigger SD3 samples on the individual drum tracks. I’m running on a MacBook Pro with an Intel i9 and 16 GB of RAM. LUNA’s Render indicator shows some strain on the system, and playback isn’t always smooth.
Some samples are rendered with nasty digital clipping pops, but only rarely.
And after a few playbacks, things stabilized. Also worth noting my SD3 sample libraries are stored on an external SSD connected via Thunderbolt 3. I’m pretty sure by unassigning the close mic in the Route Instrument Microphones dialog box, samples are not loaded for that track’s SD3 instance and memory usage is minimized. Overall, it takes some time to setup, but in the end, I have a LUNA project with each drum on its own track. Pretty sweet!Ĭhances are, there’s a better way to use this method. Please reply if you see opportunities to streamline and optimize the approach.
0 kommentar(er)
