Ah yes, I mis-read 8-10x as 8x10, thinking you had 10 different parameters you were mapping to or something (I haven’t had enough coffee yet today). 8 is a lot more managable, and since (in my experience) FreeG only takes 1-2% load, the result is still fairly low. I believe @Torsten has stated before that he sees no noticeable increase in load from FreeG, so your mileage may vary.
Regarding the timed “close GUI” trigger thing, perhaps @brad will be able to reassure us that it’s harmless and not wasteful of performance to send multiple “Show GUI Editor” events, in which case I guess your approach is fine. Internally I’m guessing Cantabile only does something as a result of a binding if it’s actually going to change the state of something.
However this sounds like a great feature request for @brad for a new binding type, which will not trigger again for a user-definable period of time. I can imagine people finding all sorts of other uses - for example to prevent people from accidentally double-tapping a “next song state” footswitch.
Neil