The Official Sequential/DSI Forum

Arp sync lost between program changes

Arp sync lost between program changes
« on: February 11, 2020, 02:12:34 PM »
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...

Pym

Re: Arp sync lost between program changes
« Reply #1 on: February 11, 2020, 04:04:09 PM »
It's due to the way we handle MIDI when files change, which is to say we wait until the file is loaded to process clocks again. We can't do anything about it on old instruments, you have to resync when you change presets. We fixed this is our more recent instruments as one of the many small improvements when we moved to a far more complex underlying operating system but it hasn't been without growing pains. There's no easy way to fix it.

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...
Dave Smith Instruments

Re: Arp sync lost between program changes
« Reply #2 on: February 11, 2020, 04:28:26 PM »
Pym - thank you for the info. I understand what you are saying. I can’t say I’m not heartbroken to hear that though.

I understand that the OB6 needs a moment to begin to process the clock again, but what I don’t follow is why the code that manages the synth’s clock tracking locks its counter to some arbitrary point between the pulses sent by the midi clock. Or is it not that, but is more like the synth doesn’t know which of the midi clock pulses is the downbeat of a quarter note, so it locks to some arbitrary pulse within the duration of the quarter note? Does midi clock identify which pulse is the “1” of a quarter note string of pulses?

Would the arp sync “reset” by sending the synth a midi start message after a program change, even if the midi clock stream is not stopped? Could be a reasonable work around, if I could just press one button on a controller to get things back in sync...
« Last Edit: February 11, 2020, 04:34:17 PM by Zac Kyoti »