# Visually Match On-screen and Physical Rotary Knobs (Footswitch LEDs)
**URL:** https://unity.neuraldsp.com/t/visually-match-on-screen-and-physical-rotary-knobs-footswitch-leds/3864
**Category:** Feature Requests
**Created:** [March 20, 2021, 1:18pm UTC](https://unity.neuraldsp.com/t/visually-match-on-screen-and-physical-rotary-knobs-footswitch-leds/3864 "2021-03-20T13:18:00Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@jazon](https://unity.neuraldsp.com/u/jazon)
#### Post date: [March 20, 2021, 1:18pm UTC](https://unity.neuraldsp.com/t/visually-match-on-screen-and-physical-rotary-knobs-footswitch-leds/3864/1 "2021-03-20T13:18:00Z")
A current challenge is not knowing immediately which rotary knobs control which parameter. Linking the on-screen and physical knobs with color might help users understand which knob does what, at a quick glance.
---
### Author:  [@Davidportersr](https://unity.neuraldsp.com/u/Davidportersr)
#### Post date: [June 24, 2021, 1:05pm UTC](https://unity.neuraldsp.com/t/visually-match-on-screen-and-physical-rotary-knobs-footswitch-leds/3864/2 "2021-06-24T13:05:53Z")
YES. THIS. Please Neural lol.
---
### Author:  [@tonydavidcray](https://unity.neuraldsp.com/u/tonydavidcray)
#### Post date: [October 26, 2022, 12:33am UTC](https://unity.neuraldsp.com/t/visually-match-on-screen-and-physical-rotary-knobs-footswitch-leds/3864/3 "2022-10-26T00:33:51Z")
I joined the forums just to post this!!
Yes please, and in additional to could we have a preference for the encoder to parameter mapping as this is a significant detractor to using a device live. The variable acceleration of the values based on the rotary encoders being moved at different speeds makes the process of adjusting a parameter one where the user needs to look at the screen and assess the changes.
If the encoder swept the values according to the range set out on the screen parameter UI then device would be much more compelling to use, mirroring an actual hardware device.
The finer details can still be entered using the touch and keypad entry method ( which is great)
I know that UI/UX encoder ballistics is a large topic among hardware developers, so maybe this could be added as a user preference.
Encoder Ballistics:
1. Linear
2. Variable
---
### Author:  [@HonestOpinion](https://unity.neuraldsp.com/u/HonestOpinion)
#### Post date: [October 26, 2022, 4:08am UTC](https://unity.neuraldsp.com/t/visually-match-on-screen-and-physical-rotary-knobs-footswitch-leds/3864/4 "2022-10-26T04:08:28Z")
Love this idea! Too bad I am out of votes. 🤐
---
### Author:  [@RMBoosten](https://unity.neuraldsp.com/u/RMBoosten)
#### Post date: [November 27, 2022, 11:52am UTC](https://unity.neuraldsp.com/t/visually-match-on-screen-and-physical-rotary-knobs-footswitch-leds/3864/5 "2022-11-27T11:52:42Z")
Super smart idea.
---
### Author:  [@tonydavidcray](https://unity.neuraldsp.com/u/tonydavidcray)
#### Post date: [January 2, 2025, 4:09am UTC](https://unity.neuraldsp.com/t/visually-match-on-screen-and-physical-rotary-knobs-footswitch-leds/3864/6 "2025-01-02T04:09:57Z")
Had to use another pedalboard over the holidays and have just come back to my QC, and oh man the Rotary Encoders are driving me nuts again. It is so frustrating to have to dick around with looking at the screen to see how the parameters have moved based on my rotational input.
I spent a few hours yesterday sniffing the USB traffic with WireShark to see if I could intercept and make a custom set of linear knobs 🙂 alas I am not that clever.
Dearest QC Devs, would it be possible to add in a linear Encoder Mapping ?
Thanks