Rapid Trigger Sensitivity

[quartz isle]

Currently the Rapid Trigger Sensitivity are the same for all the selected/enabled keys, they’re unable to have their own unique/different sensitivity.

I was wondering if it’s possible to add that option into the software, giving users more controls over their inputs.

[night fossil]

You've always been able to do this. What you can't do is enable RT on a per key basis, due to memory limits.

[quartz isle]

We were discussing how individual keys cant have thier own unique “upstroke” and “downstroke” sensitivity. Not the actuation of the press but the actual sensitivity of the rapid trigger.

https://media.discordapp.net/attachments/167181566978555904/1146942837582213160/WO4w1PH.png

[night fossil]

Up and downstroke is a different thing than just "sensitivity" though. But as mentioned not possible on current models due to memory limitations.

Nowhere to store the information.

[quartz isle]

So it’s not possible rn not because of software but the kb hardware limitations?

[night fossil]

Correct. We'd have to remove something else from every keyboard to make room for it.

[quartz isle]

Thanks for the explanation

[craggy valley]

Is it because you want the AVR version to have the same features as the ARM? Doesn't the ARM have more memory? A firmware with xbox controller replaced by more features would be awesome

[normal tendon]

its a ram limitation

[craggy valley]

Isn't it already using a whole byte per key to check if the key has rapidtrigger enabled? you could use that same byte to store sensitivity too. and the code should take about the same space too as it would need to just save/retrieve the sensitivity instead of enabled/disabled.

You surely already did this but just in case, loading the usb descriptors (or anything that doesn't need to be fast) from rom can save a bit of ram

Is it using LUFA for the AVR model right? just curious