1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Basic sample mapping and kit building questions

Discussion in 'MASCHINE Area' started by Gribs, Jan 16, 2010.

Thread Status:
Not open for further replies.
  1. Gribs

    Gribs NI Product Owner

    Messages:
    42
    I am learning how to make my own velocity-dependent multisamples using a software synthesizer (will eventually experiment with my Voyager and have also been toying with some found sounds), import them into Maschine, map them out, and save them. I have some questions that perhaps the veterans of Maschine and MPC work will be able to answer. I realize that much of this is up to personal preference for sounds and work flow but I would guess that the veterans have figured out something that makes good sense.

    1) Is there a way to load a set of samples into a pad directly into the hardware for mapping? I have not found a way to do this other than through entering sample mode, clicking on the mapping tab, and then dragging and dropping a group of my samples that I imported into my library onto the mapping work area. Once the samples are there I can go to the mapping menu under sample mode in the hardware and tweak the velocity ranges etc for each sample.

    2) Is there a preferred mode of mapping velocity ranges for electronic drum sounds? Do you like linear, log, exponential, or other type of distribution of ranges?

    3) Is there a preferred way to overlap the velocity switching between samples from none to some other range of overlap?

    4) I have noticed that the factory kits nearly always have various kit pieces on the same pads (kicks, toms, hats, rides, crashes, noises, etc). Is there an unwritten standard for placing sounds on pads? What sounds should go where?

    5) Any other words of wisdom? I should note that I have read Simon Caan's "Sample This" book to get a good overview of sampling.
     
Thread Status:
Not open for further replies.