After working around with some really low values for the timer for an effect - I recognised that the timer always started with a 1, even if i set it lower at a value like 0.0000000001 and reloaded the patch.
It seems to work if the timer is already running - but if you reload it doesn´ t work anymore and if you reset - you can see that first it jumps already to higher value if it is then set (that might give you a nice hiccup in your effect at the start)- and sometimes it is not - so it just runs with the full “1” speed.
I tried to adjust the code of the op - but after breaking the whole patch beyond the point of repair twice (Script error.file: / row:0 ? ) - I have given up.
So far I can´t say that if the reasons might be a problem from the interface (it changes the values from 0.0000000000001 to the “1e-12” notation if you reload - which might be value wise correct but maybe interpret wrong from the .get() Method or the default values of the instanced CABLES.Timer() Object or there is simply just a missing update of the timer offset.But for that I am missing the insight of the CABLES.Timer() Object. If the op is already running, that doesn´´t matter. It adjust the time just fine for the position after the comma.
So far just my assumptions. Best wishes for the new year to all @cable.gl ;).