In a widget, I noticed that my "lua driven" vars got “mixed up” after some FM changes
After some research, it turned out that I could recognize an FM change in lua, but if I read in the (now new) values immediately, I got them from the former FM
background:
I use the right slider to switch between Fms
the slider inputs are formed by a “step curve”, each step represents one FM
an LSW becomes active when the output value shows the corresponding FM value
Issue:
The change of a FM is immediately recognized in Lua, but in about 80% of the cases vars need some time to be updated with the new (FM-dependent) values
The actual workaround is to wait some time / read the vars in the next wakeup loop after the FM change has been recognized
Attached you will find a demo template and a demo widget that outputs FM and Var values after an FM change
(as mentioned, FM change by right slider, FM determined by LSW 63-69
When I tested this scenario back then on the 1.5.8 sim, I was surprised that this “fail” was only seen in rare cases, and then with a very short delay.
As I said, you can use a workaround, I personally don't see a high priority in a short-term fix.
Observation:
In a widget, I noticed that my "lua driven" vars got “mixed up” after some FM changes After some research, it turned out that I could recognize an FM change in lua, but if I read in the (now new) values immediately, I got them from the former FM
background:
Issue:
Attached you will find a demo template and a demo widget that outputs FM and Var values after an FM change (as mentioned, FM change by right slider, FM determined by LSW 63-69
When I tested this scenario back then on the 1.5.8 sim, I was surprised that this “fail” was only seen in rare cases, and then with a very short delay.
As I said, you can use a workaround, I personally don't see a high priority in a short-term fix.
regards Udo
demo script & template (1.5.8): FMvar.zip