Maschine+ Auto Sampling always stays at the same (lowest) note

bonsaiooji
bonsaiooji Member Posts: 2 Member
in Maschine

Neither in standalone nor in controller mode. Also no difference between internal and external sounds. Set a low and high note, stride 1 (others also not working). Who can help?

Maschine Autosample Fehler.jpg
Tagged:

Best Answers

  • LostInFoundation
    LostInFoundation Member Posts: 5,095 Expert
    edited January 19 Answer ✓

    What do you mean by “always stays at the same (lowest) note”?

    If it is what I suspect, the problem resides on how you set up the VELOCITY MAP:

    The way you have it (Stride 1, Vel lo 0 and Vel hi 100) means it is gonna record a note moving at every step (the 1 in Stride…if you put 10 it is gonna record 1 note every 10: 1 at 0 velocity, 1 at 10, 1 at 20,…) for every “step” of the velocity from 0 to 100. 1 note at 0 velocity, 1 at 1, 1 at 2, 1 at 3, 1 at 4…and so on and so forth.

    This means that with your setup, before moving from C3, it has to record 101 times C3 (at 101 different velocities). And every recording takes 3 seconds (the ones you set up in sample. Note On is for how long the note is played (pressed) and Sample is how long in total the sample will last, composed by the Note on duration plus an eventual tail after the key is released (for decay)).
    Which will take a lot of time before it moves from C3

    Is this why you think it’s staying at the same note?

    (Sorry if it is a little confused: Stride is not so easy to explain writing. Keep this as a general rule: Stride means by how many “steps” it moves for next recording. Easier to understand with notes: if you put Stride 1, it’s gonna record at every note. C, C#, D, D#, E, F, F#, G, G#… If you put Stride 2 it’s gonna record every 2 notes. C, D, E, F#, G#…)

  • LostInFoundation
    LostInFoundation Member Posts: 5,095 Expert
    Answer ✓

    You’re welcome.

    Happy to be useful 👍🏼

  • LostInFoundation
    LostInFoundation Member Posts: 5,095 Expert
    Answer ✓

    To give further explanation and suggestion:

    Even the way you had it set up is viable. It just has to record more things, so it takes time. If you waited 5 min and 3 sec (well…longer than this…that is only the recording time…we probably have to add more time “wasted” when moving from one recording to the other), it would have moved to next note anyway.

    It’s just a matter of waiting patiently.

    Suggestion being: when you set up Autosampler to deeply sample an instrument (many notes, many velocities, long duration…), just make it start, go do something else and come back later.

    Some settings will require a long time to finish the work… and staring at the screen for the whole time could easily result into thinking something is not working correctly…or falling asleep ☺️

Answers

  • LostInFoundation
    LostInFoundation Member Posts: 5,095 Expert
    edited January 19 Answer ✓

    What do you mean by “always stays at the same (lowest) note”?

    If it is what I suspect, the problem resides on how you set up the VELOCITY MAP:

    The way you have it (Stride 1, Vel lo 0 and Vel hi 100) means it is gonna record a note moving at every step (the 1 in Stride…if you put 10 it is gonna record 1 note every 10: 1 at 0 velocity, 1 at 10, 1 at 20,…) for every “step” of the velocity from 0 to 100. 1 note at 0 velocity, 1 at 1, 1 at 2, 1 at 3, 1 at 4…and so on and so forth.

    This means that with your setup, before moving from C3, it has to record 101 times C3 (at 101 different velocities). And every recording takes 3 seconds (the ones you set up in sample. Note On is for how long the note is played (pressed) and Sample is how long in total the sample will last, composed by the Note on duration plus an eventual tail after the key is released (for decay)).
    Which will take a lot of time before it moves from C3

    Is this why you think it’s staying at the same note?

    (Sorry if it is a little confused: Stride is not so easy to explain writing. Keep this as a general rule: Stride means by how many “steps” it moves for next recording. Easier to understand with notes: if you put Stride 1, it’s gonna record at every note. C, C#, D, D#, E, F, F#, G, G#… If you put Stride 2 it’s gonna record every 2 notes. C, D, E, F#, G#…)

  • bonsaiooji
    bonsaiooji Member Posts: 2 Member

    Thank you VERY much, you cured my (almost upcoming) despair ;-)

    Now working perfectly!

  • LostInFoundation
    LostInFoundation Member Posts: 5,095 Expert
    Answer ✓

    You’re welcome.

    Happy to be useful 👍🏼

  • LostInFoundation
    LostInFoundation Member Posts: 5,095 Expert
    Answer ✓

    To give further explanation and suggestion:

    Even the way you had it set up is viable. It just has to record more things, so it takes time. If you waited 5 min and 3 sec (well…longer than this…that is only the recording time…we probably have to add more time “wasted” when moving from one recording to the other), it would have moved to next note anyway.

    It’s just a matter of waiting patiently.

    Suggestion being: when you set up Autosampler to deeply sample an instrument (many notes, many velocities, long duration…), just make it start, go do something else and come back later.

    Some settings will require a long time to finish the work… and staring at the screen for the whole time could easily result into thinking something is not working correctly…or falling asleep ☺️

Back To Top

Categories