-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
issue 2340: Mixer volume percentage labels are off by a factor of 100 #2614
Conversation
Corresponding issue: #2340 |
@@ -1044,7 +1044,7 @@ void AutomationEditor::paintEvent(QPaintEvent * pe ) | |||
for( int i = 0; i < 2; ++i ) | |||
{ | |||
const QString & label = m_pattern->firstObject() | |||
->displayValue( level[i] ); | |||
->displayValue( level[i] /100 ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should also use a space after the slash, like the other lines, for consistency: / 100
@StCyr Nice PR! it fixes the values in the context menus: Though I noticed some things in the tooltips that could also get fixed: The volume tooltip looks ok, but it has a space before the It should look like The send knob tooltip displays it as a decimal: Also it should have some descriptive text. Ideally it should look like |
@grejppi ouch. Forgot to check that. |
you're right @grejppi; I didn't check that, sorry. So, the problem is more difficult to handle than what I previously thought. After some debugging, it appears that Faders store their value in a range from 0 to 2, while Knobs use a range from 0 to 200. I guess, solving the problem will require unifying these behaviors, which will probably be quite invasive. For the record, here are some debugging outputs I could get: Knob::getValue() value=-0,116667
AutomatableModel::setValue value=158,133347
Knob::getValue() value=-0,116667
AutomatableModel::setValue value=158,333344
Knob::getValue() value=-0,116667
AutomatableModel::setValue value=158,533340
Knob::getValue() value=-0,116667
AutomatableModel::setValue value=158,733337
Knob::getValue() value=0,000000
Knob::getValue() value=-0,116667
AutomatableModel::setValue value=158,933334
...
Fader::mouseMoveEvent value=1,442256
AutomatableModel::setValue value=1,442256
Fader::mouseMoveEvent value=1,465512
AutomatableModel::setValue value=1,465512
Fader::mouseMoveEvent value=1,488768
AutomatableModel::setValue value=1,488768
Fader::mouseMoveEvent value=1,512023
AutomatableModel::setValue value=1,512023
Fader::mouseMoveEvent value=1,535279
AutomatableModel::setValue value=1,535279 |
@diizy did some work with this back in the day.... https://github.com/LMMS/lmms/compare/models. Not sure how much of it is relevant here. |
I'm closing this PR out to declutter the tracker, because this issue requires a lot more work. @StCyr if/when you come up with a solution to the problem, you can either open up a new PR or just push again to this one, and we'll reopen it. |
Simple fix for issue 2340
It seems to do the trick