Some more context here (and in previous comments): Batumi
So there are two issues with LFO syncing that I have been on a quest to resolve. It seems that most people don’t really care about this so it’s likely just me being neurotic. It’s sort of my specialty.
The first is how the LFO handles stopping and starting the clock source. Batumi keeps running the LFO in the background and when the clock starts again, it immediately recalculates the tempo and tries to get back in sync. This is probably okay in many cases, but if you’re doing a recording where you need to start the clock and have predictable results (like trigger percussion), this can be problematic.
The second issue has to do with phase syncing on LFO modules that have don’t have a 1:1 relationship between clock source and LFo cycle time, e.g. those with a clock divider/multiplier such as Tides, Quadrax, Modbox). Batumi just sidesteps this by forcing a 1:1 relationship and making the sliders inactive when in free run mode while synced.
At any rate, I think Tides has the most elegant solution to the above issues because it lets the LFO pause when it the clock stops and then picks it back up at the previous tempo when the clock resumes. Right now Quadrax has probably the worst implementation of any of these modules because the LFO phase is totally random and it simply sets the LFO rate based on the incoming clock.
If Intellijel can get the Tides-like logic implemented in Quadrax it’s going to be an absolute killer module, but I suppose it’s too early to get excited 