…
if you have a number of fast succeeding notes then they are harder to time correctly, the same is applied for the note interval (the larger it gets for succeeding notes, the harder to hit them in time). so the script basically creates a score and schedules notes according to that, this score is used to give every midi event a new spawn time. for the prescheduling the plugin uses PDC (0.125 seconds).
for the weight:
i used the idea from the LFO script (http://stash.reaper.fm/v/9283/lfo) by youn. it shows : green incoming events (on time - without PDC, so dont get confused ), out events (red). weight for the events to reschedule: blue scope. yellow bars indicate that messages have been lost! there is also an indicator that shows “how much memory” is currently used for events (cyan scope).
WORKS ONLY FOR MONOPHONIC MATERIAL!! Bugs: fixing appreciated :-)
The audio out can be VERY LOUD - disable it anyways (disconnect the plugin outputs to the track bus)! if you are sending many midi events (and have CC enabled) then this plugin becomes quite stressfull to the cpu - remember it has to reschedule everything, re-time events (meaning: “memory allocation”, sorting, comparing timestamps per sample/event). there is the possibility of events being lost (if the delay impact is too large in comparison to the number of incoming events). and yeah, its ugly code; created in a rather hack-ish mood.