OffGrid is designed for the highest possible Input Sensitivity in the operator's hands.
We've custom-designed and co-engineered the sensor layer with the industry-leading manufacturer of FSR* technologies Interlink Electronics for a maximum extended dynamic range to perceive impact and aftertouch velocities ranges.
The device stack is comprised of five major, seperately produced, components:
- Two Enclosure halves.
- PCB.
- Silicone Pad Layer.
- Sensor Layer.
Each component exhibiting its own mechanical, material specific properties.
In some cases, over time and the natural lifespan of materials and/or due to climate and/or atmospheric changes - a certain change of tolerances between any or all layers may introduce a perceivable change of pressure exterted on the sensor layer (without being affected by a human operator) which leads to self actuation of a single or a number of pads. In some cases, this can be perceived as neighboring pads being self-activated when a different pad is being pressed by the operator.
We would like to walk you through a short procedure that lets you change the threshold level for OffGrid to listen to for deciding to trigger pad actuation.
*Force Sensing Resistor® technology is registered to Interlink Electronics, Inc.,
First let's head over to:
https://offgrid.birdkids.io/#/experimental/fsr-threshold
1. You'll want to pair your OffGrid (ideally over Bluetooth in Chrome) first:
2. Once you're paired, the input that says "Threshold" will probably have a value reading "69":
3. Go ahead and change that to something like "120", and press the "Write to device" button.
It will immediately set the device velocity detection to a higher threshold (overwrite the current level).
If your device initially detected self-actuation, a change of Threshold Level might be immediately perceivable in that it does not self-actuate anymore. You might want to try the new setting in the context of your used Apps to see if there's any level of so-called ghost-notes occasionally.
If the unwanted actuation still occurs, try to change the level to a higher value setting f.e. 160, 200, 240 in steps that make sense to you.
Once you've found values where no unwanted behavior occurs, you can choose to dial back in increments of 2's within a range that does not exhibit any unwanted behavior.
Reducing the dynamic range by changing the Actuation Threshold Level is in fact a compromise on the entire available dynamic range. But should not be any cause for concern unless you have to dial in values over 500.
Comments
0 comments
Please sign in to leave a comment.