Is there a scrptlet that will quantize Note On to a 16th note or any other note value based on the project’s tempo? I have a step sequence on the DX7 that re-triggers when you play a note. However if you miss the beat the whole thing drifts off. If I’m able to quantize the note on, that should fix it
Did you try MIDI File Player with Step Sequencing?
Be aware that such a scriptlet could only quantize “forward”.
Means: Only trigger the note to the next possible step. If you are playing too late, it wouldn’t be able to step back… This would need a “quantize before played” magic. 
Yes That’ll work!. Have you got the scriptlet?
No, I’m using it’s as a modulation source
No… it just was a theoretical thought.
What do you mean by modulation source?
The BlueARP plugin has a feature called Real time input quantisation.
Perhaps someone here has the plugin and can comment.
Try this
Trigger.gig (29.0 KB)
Trigger.mid (78 Bytes)
Just connect you plugin under the MINTRIGGER plugin.
And connect you MIDI controller to the MIN plugin
this is the code used
var MIN : MidiInBlock
MINTRIGGER : MidiInBlock
nn : NoteMessage
play : Boolean
On NoteEvent(m : NoteMessage) from MINTRIGGER
if IsNoteOn(m) and play == true then
SendNow(MINTRIGGER, nn)
play = false
end
End
On NoteEvent(m : NoteMessage) from MIN
if IsNoteOn(m) then
nn = m
play = true
else
play = false
SendNow(MINTRIGGER,m)
end
End
The used MIDI File sends quarter notes
So now your played note will be processed with the next note coming from the sequencer.
To react on 16th just use a different MIDI File sending 16th notes.
2 Likes
That sounds like the feature I need to recreate via a scriptlet
A scriptlet alone will not work as you need a timeline.
therefore my proof of concept using a MIDI File Player.
With a Midi File you can define every sync you need.
dotted 8 or whatever you need.
Thank you, I’ll give it a go
That works fine, indeed, but you have to play your chords a little bit earlier to be sure to trigger BlueARP properly, which is not a big deal. If I remember well, I used this feature together with an ascending and another descending arpgegio that I triggereded alternatively using a Scriptlet which switched the BlueARP arpegio at each new chord played.
Maybe I do not understand.
@Narf wants to trigger a step sequence on his DX7, what could BlueARP help?
Can anybody check my uploaded gig?
It was for the left hand pattern of Girls Just Want To Have Fun. The step sequence triggered the volume of the sound to produce the organ pattern. Blue arp worked as intended as quantize filter for the DX7 step sequence but in the end, it was easier to just use Blue Arp instead to generate the Arp as midi instead. I wanted to play along a backing track but as it turned out, the backing track I had had an inconsistent tempo anyway. Also instead of making the DX7 sound like a Vox organ, I ended up using the actual Vox to be controlled by the Blue Arp.
This is what it sounded using the Arturia DX7 V
I had wondered if the ‘input quantization’ could be passed through to the output e.g. whether you could use it for just this midi processing. But perhaps not (I don’t own it).
I also think that we need to have some kind of time “raster” in which everything is scheduled.
In a DAW like Cubase (and such), everything is following a common time line that’s why quantisation works in that environment, but when playing live in GP, you are somewhere in “open space” - anything could be played at any time, so how could you tell when it is the right moment to quantize a note to?
@Pianopaul is most probably right to make use of the Midiplayer, because this would provide the needed time “raster”, defined by beats and bars.
Maybe BlueArp quantizes the incoming trigger notes within its own time raster of the running arpeggio, but i guess this is not something that can be influenced from “outside”.
And with the use of the MIDI File Player it is easy to quantize “laid back”
I don’t remember well how I made it work, but I played arpeggios of a Muse song with it. It followed the GP tempo (catched from the drummer tempo with a pedal) and it was resynced at each new chord played (we played without click). But of course there are other solutions…
1 Like