Plus, I think the whole thing is easier to grok if you've used other DAWs and don't have much experience with the classic MPC program/sequence workflow. I'd say iMPC has a much better default drum library, sample slicing and IAA support for third party effects but NS beats it out with a lot of other features-namely much better sequencer/song mode, AudioBus support in and out, the Eden synth, built in effects and three audio busses per TRG. Oh, there's a free Win/Mac version of NanoStudio if you want to try it out first. If you don't own either, definitely watch some youtube videos or something. They are about the same price once you factor in the IAP for 15 tracks (vs 6) in NS. ^ basically the same idea as the NS idea I posted above but iMPC Pro calls them "Programs" and NS calls them TRG Instances. With the single available IAP you get 15 instrument channels, each mapped from MIDI Channel 1 through 15 by default (or 2-16, don't remember).
In case it's not clear, by default, NS maps each instrument you insert to it's corresponding MIDI channel. That will allow you to stack from 1 to 16 sounds in any given TRG instance and always know that your pads are mapped to a specified TRG.
Using Nanostudio as an example, you could set up each set of stacked sounds on separate TRG instances and use a MIDIFlow preset to convert each pad on your 16 pad controller to send all 16 possible TRG notes to NS on a different MIDI channel per pad. Or, set up your hardware pad controller to go through something like MIDIFlow and generate all the required notes from a single source note.
You could also try using whatever sound source app you like and then making a pad set in something like MIDI Designer that actually sends as many different NOTE ON messages as you like. Well, up to three mix groups per TRG instrument anyway. It will not allow you to assign multiple sounds to a single pad but it will allow you to easily group and process them.
0 kommentar(er)
