do you mean being able to have sort of like a slew when changing fader values? the problem with this is - teletype is not really set up to track continuous changes. say, if we had this ability and a fader is slowly changing its value from A to B when should we trigger the corresponding script? if we just trigger it when it reaches B then we don’t really gain much. the workaround is using a very fast metro script, but this really feels hackish…
i do agree it would be nice to have the ability to have finer control over fader values, otherwise they don’t seem all that useful. so yeah, we could use varibrightness and have some button combo to increase/decrease value in smaller steps. i will add this to the list!
this is probably less likely to happen… the reason is - if we had additional memory slots i would expect them to be stored in flash when i store my scene. we have some space there but storing grid state takes quite a bit of space, and in the future we might have new features that will also need to use storage, so we have to be careful what we allocate it for.
a workaround for this is using our existing infrastructure in the form of patterns. it’s really easy to do something like
L 0 15: PN 0 I G.BTN.V I. with upcoming bitwise ops it will also be easy to pack 16 button states into one pattern value (i have example of this above in the pattern canvas scene). i think what makes more sense is expanding the number of available pattern banks to 8 (or even more).