that's the symptom exactly. the BeatStep sends official NRPNs, MSB-LSB, but the VS expects it the other way round. so the VS won't update until the *next* data value comes in, so in this case, your resonance MSB is interpreted as a cutoff MSB, and when the LSB comes in, the VS then starts waiting for the accompanying MSB...
fwiw, i've always found the VS to be pretty bulletproof when it comes to external control. my editor sends the full four-packet enchilada for every parameter change and the VS never so much as hiccups.
On Tue, Aug 7, 2018 at 1:14 PM, shalebridge@... [prophet_vs] <prophet_vs@...m> wrote:
Sorry if this double posts, I didn't see it pop up anywhere...Thanks for the extra info Jason! I was working on a sort of memory map for all the patch info, but I'll go back to working on the NRPN input.You know, there as a glitch I noticed while working with the BeatStep. If I adjusted Cutoff for example, then tried to adjust Res, the Cutoff value would change right before the Res would. I figured it just needed a null RPN between the adjustments.