(For the short ones the lfo is actually triggering a decay envelope in another stages stage)
EDIT:
so today I was getting a much more responsive rate (nearly 100% of notes, no drift).
my first session I started getting this morse code looking midi where it was like short note, short note, short note, long note (sometimes 3, sometimes 4 short notes…pulse width of the trigger to ^^ins didn’t seem to effect it) and then eventually live being unresponsive to anything and crashed (I was at about 10-15% CPU, using a ^^jf with arp, ^^ins to trigger a note, and CV Clock In.
when I reopened live after the crash it seems to be working more or less 100% now, correct length notes and everything.
EDIT 2: Actually sorry, I had a note length midi effect device which was effectively making all the notes the same length:
the raw midi ^^ins is outputting looks more like the morse code I was experiencing pre-crash
EDIT 3: It’s also kind of strange, it seems like ^^ins is outputting at a slightly slower tempo than what the ^^jf arp line or the modular’s clock in is running at, which doesn’t really make sense to me (I’d understand “out of phase” with each other but I don’t understand “slower”)…maybe the issue is that each consecutive note generation on ^^ins is getting sort of a bit behind in the queue more?
That’s all I have time for this morning. I will say, ^^ins working rock solid, 100% isn’t super important to me. I got what I needed with the CV Clock In. but I am happy to keep going on the debug trail if y’all want to nail this down!
EDIT 2: So I need to do some testing, but I’m wondering if I am running into the ableton midi jitter on high buffer sizes issue with the above (it was the cause of some other weird midi issues for me). I’ll check my buffer size, try again, and report back if it fixes it.
