"Set Value" dialogue does not cover full range of new dB controllers
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 1.3k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
### System Information
Windows 11 25H2
### LMMS Version(s)
1.3.0-alpha.1.926+2db75bd
### Most Recent Working Version
1.3.0-alpha.1.102+g89fc6c960
### Bug Summary
When double clicking the volume controllers recently changed to the logarithmic scale, in "Set Value", the value is clamped to [-96, 6] and does not allow the full range supported by the controller. Throughout normal 0%-200% controllers, this bug is not so apparent, but in AudioFileProcessor, the full range is (-∞, 13.98] (500% in linear scale), which is impossible to type in the dialogue.
### Expected Behaviour
The "Set Value" dialogue should clamp the min/max values according to the controller.
### Steps To Reproduce
1) Add an AudioFileProcessor instrument.
2) Set gain to 500%/13.98 dB (the controller above the waveform).
3) Double click the gain controller. The value gets clamped to 6 dB.
### Logs
_No response_
### Screenshots / Minimum Reproducible Project
_No response_
### Please search the issue tracker for existing bug reports before submitting your own.
- [x] I have searched all existing issues and confirmed that this is not a duplicate.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the problem with an AudioFileProcessor on Windows by setting its gain to 500%/13.98 dB and opening the Set Value dialogue. Locate the dialogue's fixed clamp and the controller range handling; done means the dialogue accepts the full range supported by each controller, including 13.98 dB for this gain control.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100