That essentially describes the UI in my Olight, sans the ramping mode:
L-M-H in normal rotation, hold to cycle. Single-click on/off.
ML = when off, long press to on.
Turbo = double click from any state.
Strobe = triple click from any state.
ML is memorized. Turbo is stepped down to H in memory. Strobe isn’t memorized at all.
It works well, isn’t complicated, and the “special” modes come into play only when called upon.
IMO, ideal for a single-switch, general purpose light, with no need to reinvent the wheel like some try to do.
At some point during the SP32A production run, the firmware was quietly updated with improved ramping speed. An unofficial “v1.1” if you will, not v2.0, which is an official new model.
Continuous improvement is fine, and welcome, but the manner in which some of these companies (fail to) document changes and market their products does no favors to consumers. I get that these are small entrepreneurial enterprises where labor of love plays a big role, but that doesn’t preclude a considered and consistent approach to the marketing as well.
AFAICT, there have been four versions of the SP32 thus far:
SP32 - the original. An evolution of the SP31 as a new model, with single side-switch.
SP32A - new model with ramping mode; lower modes slightly adjusted, higher modes significantly bumped up
SP32A “1.1” - “later production batches” with quiet running update for improved ramping speed
SP32A v2.0 - new model, with power indicator, temp regulation, mode adjustments, and other minor changes.
Given the notable changes in the v2.0, I don’t know why they abandoned the previous practice, and just iterate the suffix, and call it the SP32B, instead of the less elegant and confusing addition of yet another suffix. Or maybe it could have gone down the other path and just been the SP32 v3 or v4 to begin with. 