Can Anybody else reproduce this bit of oddness?

[Surreal]

I am doing this with a js heavy midi effect.

the effect works fine and the notes are on time, normally.

but if i scrub back and forth in the bottom little tab that shows a bird's eye view of all of the effect really quickly, the timing gets REALLY loose.

[Surreal]

you could try without js...i am just wondering if it is.reproducible

[amounra93]

I stay away from MIDI processing with js for this very reason....everything runs low priority, and in a single thread in m4l. That means if the API takes a hit for whatever reason (redraws, etc.), timing gets wonky. You'll get a pause in the output, then a stacked output of everything that got dropped until it catches up. I use js only for stuff that is UI related or for API calls (since they are always low-priority anyway).

So yes, very reproducible.

[Surreal]

well that is incredibly dissapointing. I remember the warning about timers, but didn't realize that it would mess up event based midi processing as much as it does.

i've done too much to scrap it, but now i don't know how useful this will be.

[Surreal]

immediate to the rescue!

[amounra93]

'immediate' is not a solution....in my own experience, it has been the most reliable means to ensure that your patch ALWAYS crashes. Sorry

a

edit:: to clarify: according to my information, the 'immediate' attribute is not correctly supported in m4l.

[Surreal]

hasn't done much ill to me...

so far.

heh.