Quick FYI and a followup question.
Re: phase syncing issues when stopping and starting an external clock, I made a little Max for Live device that provides a continuously-running lock that I can sync Batumi to. The clever (well, I think so) feature is that when I want to start or stop Live’s transport, I can just toggle a Sync button on the device and it will wait until the clock cycles through to the first beat to start Live’s transport. Seems to work okay despite me being a complete hack at M4L so maybe I’ll put out a more polished version if there is any interest.

OK, back to Batumi… I was a little mystified by the LEDs on the sliders at first, but I think I understand that they are tied to the Sine output? I tend to use a lot of downward ramp shapes and it’s really throwing me for a loop that the cycle and the LEDs are sort of offset 180°. Probably a long-shot but is anyone aware of a way to change the behavior e.g. with one of the alternative firmware modes?
Since each LFO can output different waveforms, I realize that some compromise is necessary, but it seems odd to pick the sine wave instead of trying to give some general indication of where a phase starts/stops on a module that relies so heavily on triggers and syncing. Seems like the ideal behavior would be to give an indicator of where the phase start is (e.g. downward ramping LED intensity that reset at 0°).