Sampler: key mapping when loading multiple samples
Posted: Fri Nov 24, 2006 4:12 am
As a bunch of samples can be dragged into Sampler in one go, it would make a lot of sense to be able to choose a way of mapping oneshots that doesn't require manually placing every single sample. Currently, the samples are mapped onto the full key range by default. When dragging a bunch of oneshots, say, 40-50 individual drum samples into Sampler, this trivial procedure becomes a pain. [Edit: even when using the "distrubute zones equally" functionality. See the next two posts.]
Along with the missing multiple outputs, this is the main reason I feel I can't use Sampler to intuitively and quickly sculpt drum material using oneshots. Of course there's Impulse and there are racks and so on, but I can't help feeling like there's a lot of wasted potential in Sampler because of this. It would be a really awesome drum workhorse with all its modulation capabilities and otherwise flexible editing.
So, in the same way this is currently possible in Shortcircuit (for example), I would like to 1) drag multiple oneshots into Sampler and have them instantly mapped and 2) select any individual sample inside the multisample and be able to instantly send it through a different effects chain (i.e. select a different output for it). Any individual sample, and without messing around with any unnecessary keyzone worries or automation or other switches for that simple thing.
For number two, stacking many Samplers inside a rack only yields this functionality if you design the groundwork for the rack beforehand and stick to that (basically, decide which ranges/devices will play through which chains, and keep loading your sounds into the instances accordingly). This way, you end up working inside multiple mapping interfaces and you are constrained to the rack design, choosing between different ranges and different chains, even when you'd just like to be freely importing new material to experiment with. Don't get me wrong: I love racks and the massive possibilities they brought, but in this particular case they are a workaround, resulting in fiddling with a literally redundant workflow and diving inside multiple Sampler instances - when all you'd like to do is to spontaneously send a certain drum hit, currently residing inside a certain Sampler instance and mapped to key X, into a different effects chain.
This is much less than optimal when you're just itching to load heaps of oneshots inside a sampler and improvise new rhythmic wonders hoping to freely utilise all the power there really is inside this instrument. To me, Live has always been about the workflow, about the flexibility of creating. If it's seriously suggested that Sampler doesn't need multiple outputs because you can always stack them in a rack, I think that's missing the main point.
I guess I'm just a bit shocked to find out how insanely fast this kind of workflow in Shortcircuit really is ... It's seriously very good for creative sampling.
Along with the missing multiple outputs, this is the main reason I feel I can't use Sampler to intuitively and quickly sculpt drum material using oneshots. Of course there's Impulse and there are racks and so on, but I can't help feeling like there's a lot of wasted potential in Sampler because of this. It would be a really awesome drum workhorse with all its modulation capabilities and otherwise flexible editing.
So, in the same way this is currently possible in Shortcircuit (for example), I would like to 1) drag multiple oneshots into Sampler and have them instantly mapped and 2) select any individual sample inside the multisample and be able to instantly send it through a different effects chain (i.e. select a different output for it). Any individual sample, and without messing around with any unnecessary keyzone worries or automation or other switches for that simple thing.
For number two, stacking many Samplers inside a rack only yields this functionality if you design the groundwork for the rack beforehand and stick to that (basically, decide which ranges/devices will play through which chains, and keep loading your sounds into the instances accordingly). This way, you end up working inside multiple mapping interfaces and you are constrained to the rack design, choosing between different ranges and different chains, even when you'd just like to be freely importing new material to experiment with. Don't get me wrong: I love racks and the massive possibilities they brought, but in this particular case they are a workaround, resulting in fiddling with a literally redundant workflow and diving inside multiple Sampler instances - when all you'd like to do is to spontaneously send a certain drum hit, currently residing inside a certain Sampler instance and mapped to key X, into a different effects chain.
This is much less than optimal when you're just itching to load heaps of oneshots inside a sampler and improvise new rhythmic wonders hoping to freely utilise all the power there really is inside this instrument. To me, Live has always been about the workflow, about the flexibility of creating. If it's seriously suggested that Sampler doesn't need multiple outputs because you can always stack them in a rack, I think that's missing the main point.
I guess I'm just a bit shocked to find out how insanely fast this kind of workflow in Shortcircuit really is ... It's seriously very good for creative sampling.