posted 01 February 2001 13:14            

i have seen a discussion somewhere in the forum where the opposite philosophy was presented: dozens of flavors of sounds with mutually exclusive functionalities--i do not like that idea at all. i would much rather deal with too many fields on the screen at once than to not be able to use kyma as a tool for a specific musical purpose.

uber-sample should be able to index into a list of files given as a folder, pitch it's samples, loop them, have start/end points, be able to reverse (in real-time please), etc.

this uber-sound is uber-important because unlike the other sample sounds in kyma, multisample lets you specify a folder of samples--no typing of 100's of filenames, no compiling 100's of times. it's the most efficient way of having 100's of samples on demand. it's much more in line with the proven effectiveness of workflows such as photoshop, premiere, aftereffects, debabelizer, etc. where your amazing ideas can be batched using folders of files as inputs.

i'll give you the specific example which has sparked my passion on this topic: i have 100's and 100's of drum sample sounds: hihats, kiks, cymbals, and even non-drums sounds that just sound plain cool when sequenced. i want to be able to index into this library with multisample driven by kyma's analog sequencer (and THEN tweak the hell out the sound as only kyma can do). musically it's very important to be able to pitch each drum sound as you index into the library. the combination of these two ideas cannot be achieved in kyma today. currently, i just bite the bullet and use function generator and type in 100's of sample filenames and recompile 100's of times. imagine the pain.