13 thoughts on “Creating 128’s With Sampler In Ableton Live

  1. The only problem I have with 128's is that they take several minutes to load in to your set. I stopped doing this approach because of that.

  2. This is a nice way of auditioning various drum sounds in context.

    The use of the term "Midi channel" was very confusing to me, however: the sample selector has nothing to do with Midi channel, it's just a parameter ranging from 0 to 127.

  3. Awesome now this is the kind of video I enjoy. I actually just looked this one up yesterday. Interesting you were looking at the same thing…..

  4. Those are not “MIDI Channels” nor a “parameter ranging from 0 to 127”. Those are the MIDI note numbers that will trigger the samples. What you do to audition is actually transposing the input note, one of the oldest samplers trick.

    1. I don't think so: what you're referring to are Key Zones, every sampler has this of course. But in Live's Sampler you also have Sample Select Zones, which are independent of the key zones. According to the manual, this is "a data filter that is not tied to any particular kind of MIDI input".

  5. This is a well known problem, and Sampler was my first choice when I started to do on-the-fly drum changes. Sampler is good for it, but you are basically stuck with one bank and you get all kind of performance issues with too many instances.To solve this, I programmed a Max for Live patch, called "Drumfire". Drumfire can store folders which can have anything up to over 1000 samples, which are all selectable with 3 knobs: 1. Sample, 2. Bank 3. Folder. Still, only one sample is loaded at any time, so its very performance friendly.
    You can find it here: http://www.maxforlive.com/library/device.php?id=4
    By the way version 3.0 will be up beginning of June 2011, rewritten from scratch.
    Go create some music! modul8tor

  6. This is a well known problem, and Sampler was my first choice when I started to do on-the-fly drum changes. Sampler is good for it, but you are basically stuck with one bank and you get all kind of performance issues with too many instances.To solve this, I programmed a Max for Live patch, called "Drumfire". Drumfire can store folders which can have anything up to over 1000 samples, which are all selectable with 3 knobs: 1. Sample, 2. Bank 3. Folder. Still, only one sample is loaded at any time, so its very performance friendly.
    You can find it here: http://www.maxforlive.com/library/device.php?id=4
    By the way version 3.0 will be up beginning of June 2011, rewritten from scratch.
    Go create some music! modul8tor

  7. This is a well known problem, and Sampler was my first choice when I started to do on-the-fly drum changes. Sampler is good for it, but you are basically stuck with one bank and you get all kind of performance issues with too many instances.To solve this, I programmed a Max for Live patch, called "Drumfire". Drumfire can store folders which can have anything up to over 1000 samples, which are all selectable with 3 knobs: 1. Sample, 2. Bank 3. Folder. Still, only one sample is loaded at any time, so its very performance friendly.
    You can find it here: http://www.maxforlive.com/library/device.php?id=4
    By the way version 3.0 will be up beginning of June 2011, rewritten from scratch.
    Go create some music! modul8tor

  8. This is a well known problem, and Sampler was my first choice when I started to do on-the-fly drum changes. Sampler is good for it, but you are basically stuck with one bank and you get all kind of performance issues with too many instances.To solve this, I programmed a Max for Live patch, called "Drumfire". Drumfire can store folders which can have anything up to over 1000 samples, which are all selectable with 3 knobs: 1. Sample, 2. Bank 3. Folder. Still, only one sample is loaded at any time, so its very performance friendly.
    You can find it here: http://www.maxforlive.com/library/device.php?id=4
    By the way version 3.0 will be up beginning of June 2011, rewritten from scratch.
    Go create some music! modul8tor

  9. This is a well known problem, and Sampler was my first choice when I started to do on-the-fly drum changes. Sampler is good for it, but you are basically stuck with one bank and you get all kind of performance issues with too many instances.To solve this, I programmed a Max for Live patch, called "Drumfire". Drumfire can store folders which can have anything up to over 1000 samples, which are all selectable with 3 knobs: 1. Sample, 2. Bank 3. Folder. Still, only one sample is loaded at any time, so its very performance friendly.
    You can find it here: http://www.maxforlive.com/library/device.php?id=4
    By the way version 3.0 will be up beginning of June 2011, rewritten from scratch.
    Go create some music! modul8tor

  10. This is a well known problem, and Sampler was my first choice when I started to do on-the-fly drum changes. Sampler is good for it, but you are basically stuck with one bank and you get all kind of performance issues with too many instances.To solve this, I programmed a Max for Live patch, called "Drumfire". Drumfire can store folders which can have anything up to over 1000 samples, which are all selectable with 3 knobs: 1. Sample, 2. Bank 3. Folder. Still, only one sample is loaded at any time, so its very performance friendly.
    You can find it here: http://www.maxforlive.com/library/device.php?id=4
    By the way version 3.0 will be up beginning of June 2011, rewritten from scratch.
    Go create some music! modul8tor

Leave a Reply