Humanizer

[samuellouf]

I was chatting with a friend and showed him some of my music on signal. He told me that I should slightly offset the notes to humanise my music. He then told me about DAWs and other MIDI editor that had a "humanise" function that does just that.
I'm going to try to add one to signal. I'll keep you all updated in this issue.

[samuellouf]

Honestly, I'm not really used to TypeScript and the code for signal is massive. So I'm going to lay out what I would like the humaniser to look like in case someone's intrested/has more skills than me and wants to try to do it themselves.

Concept

The button would be in the "Edit" menu. It is never disabled. It's just below the Quantizer button.
When you click on it, a popup menu will appear (kinda like the velocity menu) and ask you how much do you want to humanize the notes and if you want to humanize the velocities.

Scenario 1 : Notes are selected

If notes are selected, then the humanizer will only apply to them.

Scenario 2 : No notes selected

If no notes are selected, there will be a select menu in the popup menu asking you if you want to apply the humanizer to the track or to the whole song.

Algorythm

h is considered the humanisation rate.
The alogrythm adds Math.round(Math.random()*(120*h)) - 60 the note's tick.

120 is considered the "standard" maximal humanization.
120 is multiplied by the humanization rate to get the maximum value to which the note can be delayed.
Math.random()*(120*h) gives us a random value and Math.round rounds it up.
The -60 is here to make the note able to start earlier.

The algorythm will have to check if the note's humanize tick is over/equal to 0. If note, set the tick value to 0.

The same process will be applied to the note's duration. (And, same thing here, the algorythm has to force the duration to be a positive number).

The same alogorythm is applied for the velocity, except 120 is replaced with 20.