Note and Event Probability

Kai_NI

As a user,

I want to be able to assign a probability to a MIDI note or (or other applicable event types) that determines on a %-chance level whether the event is being triggered

in order to

create musical variations and generative music that is less predictable or repetitive as a statically programmed sequence.

This feature may include specific probability assignments per Note / Sound as well as e.g. velocity variations.

darkwaves

I like this idea and think it would work well with the current workflow of the step sequencer.

Schmapps1

definitely! I’d also suggest taking it a step further and include conditional triggers. “X cymbal hit only plays every 4th time through the pattern” etc

tetsuneko

Yes, absolutely needs conditionals like on Elektron grooveboxes. I rarely, if ever use percentage based note/trig probabilities, but use conditionals like 1:4 (ie trigger on the first cycle and reset after 4 cycles) ALL THE TIME

Probability based triggering does have some performance-related use cases which can be fun though, such as globally reducing probability for every trig within a pattern in order to create a temporary breakdown, for example.. But just having static probabilities for sequencer steps is not something I consider essential in a sequencer such as Maschine+, which does not suffer from typical groovebox constraints in terms of maximum possible step lenghts for a pattern. Just duplicate pattern lenght and create more variations instead, this is very fast to do on the Maschine already. Using only 16 or 64 steps in a Maschine pattern and then resorting to probabilities feels like a solution looking for a problem that doesnt exist in a unit which has no problems playing back 128 bar long patterns

ozon

@tetsuneko wrote:

Yes, absolutely needs conditionals like on Elektron grooveboxes. I rarely, if ever use percentage based note/trig probabilities, but use conditionals like 1:4 (ie trigger on the first cycle and reset after 4 cycles) ALL THE TIME.

Big plus one to this. And don’t forget the odd relations (e.g 7:8) which are great to break out of predictable repetition schemes.

Antonio B

High on list and was one of my own requests! Glad to see that it made the cut. I think what would make sure that this is a useful tool would be it's ease of use i.e. press the note, dial in percentage. That simple (see Novation Tracks for implementation of this on a step seq.) btw, please implement an auto step classic step sequence behavior! Thanks :)

skolarr

Just want to echo the previous comments that I have a preference for conditionals over percentages. Perhaps it's possible to have both? And allow the user to choose between the two depending on the situation. But if we can only have one or the other, I would prefer conditionals.

Infrabass

Please implement both systems, NI. They have their own unique musical applications. 🙏

Infrabass

I would even add another essential logic condition for live performance I often use in my Elektron Boxes:

FIRST

A step with a FIRST condition would only play the first time the pattern plays.

Ideal for musical punctuations (in its most basic form a crash cymbal).

Also useful in drone music genre to play a very long sample on top of other elements.

Infrabass

Ok I'll even mention another logic condition I never saw in any instrument but I think would be very useful.

LAST

A step with a LAST condition would only play if a pattern/scene change has been asked by the user.

Imagine a scene change quantization set to 1 bar with a LAST logic condition step on the 1/4 note before the end of the pattern.

This step would only play before switching to the next pattern/scene.

It would allow pre-musical punctuations which are very musical in my opinion as they can serve as transition elements.

I hope my ideas will be heard by the development team.

Thanks for all the work you already did and you are currently doing!

🙏

Percivale

Not sure to add to [Sequencer improvements] or here. I think they are too intertwined to be addressed separately, i.e. what is a sequence without notes and what are notes without a play head. Anyway, some ideas to include (just consider what you think is helpful):

1. Play direction
2. Euclidean mode
3. Stochastic mode, using parameters to influence & generate set of notes
4. Note range required, e.g. C2 to F#4
5. Note(s) permitted (after selecting a scale), e.g. select C major but uses C, E and G only
6. Note ratchet type, probability, and variation
7. Note length and variation
8. Note mute probability and variation
9. Note(s) repeat/retrigger - holding down one or more notes
10. Note(s) random type, probability and variation (can tie in with No. 3)
11. Note relation, e.g. legato, glissando or staccato, i.e. length (can tie in with No. 7)
12. Note(s) fill, e.g. activating it will play the inverse of note settings
13. Notes shift, e.g. nudge all notes by one step to the left/right

Jaskin

Votin for this!

Marc Hupkens

yes we need probability and also randomization

the team should have a very good look to the pattern sequencer in GarageBand on the iPad …. That combined with randomization to set on chords, notes, motives etc would free up so much my terrible plsying and finger drumming

do itttttttt

mat985

WE NEED PROPABILITY. I TOTALLY AGREE BUT I DON'T THINK THAT THE TEAM IS LISTENING TO US, CONSIDERING THAT THE UPDATE TO MASCHINE 3 IS READY AND IT'S SEEMS LIKE A JOKE!