Hey all. Just posting to see if others may be having a similar experience. I’ve noticed that when clocking externally and using arp beat sync, switching between programs will make the arp lose sync (phase, but not tempo). This may be difficult to notice unless you also listen to a metronome click/beat/whatever while trying this experiment. To reproduce: Find or make some plucky percussive sound. Turn the arpeggiator on. Save this sound to two program slots, let’s say 001 and 002. Make sure the synth global “arp beat sync” is on, and start sending it the midi clock. Listen to a metronome tick in time with your midi clock. Hold down a couple notes. The arp should sound tight and on-time. Release the notes. NOW- keep the midi clock running, and switch between programs 001 and 002 a few times. Every time you do, you’ll notice the tempo readout waver a bit and restabilize. Play an arp again. Notice how now, even though the tempo is correct, the arp has shifted phase in relation to your metronome tick. The more times you flip between program 001 and 002, the worse the drift becomes. The Arp is somehow decoupled from the clock feeding the synth. The only thing that fixes the issue is to stop and restart the midi clock.
I bring this up primarily because it’s a major kink in my workflow. In my jamming or live sessions, the midi clock needs to run continuously - I can’t afford to stop and start it at every program change. I would like to be able to change programs at will, and have everything locked and ready to arp immediately. I truly believe this is the intended behavior, but it just doesn’t work that way. I’ve tried with 1.5.5, 1.5.8, and 9.0.0, with identical results. I have submitted a support request, however, I’d be very interested to hear your test results. I’m assuming this issue may affect the Prophet 6 as well...