Skip to content
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

Show value units for more parameters #1495

Closed
mkruselj opened this issue Jan 22, 2020 · 7 comments
Closed

Show value units for more parameters #1495

mkruselj opened this issue Jan 22, 2020 · 7 comments
Assignees
Labels
UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.
Milestone

Comments

@mkruselj
Copy link
Collaborator

Currently pitch-based parameters (Pitch, Formant, Sync, Cutoff modulation depth, and pitch-based parameter modulation depths) which are in semitones, aren't stating that they're in semitones. Which they should :)

Also Uni Count should probably say "voices" as unit.

Modulation amounts should all be in % (except for pitch and Hz based parameters) with two decimals (i.e. moving from -1.000000 ... 1.00000 to -100.00% ... 100.00%).

I'd also suggest that any current %-based parameter should move to showing two decimals for consistency.

@baconpaul baconpaul added this to the 1.6.5 milestone Jan 22, 2020
@baconpaul
Copy link
Collaborator

As I commented on slack: need to be careful about which are in semitones and which are in notes; since notes != semitones with non-uniform tunings.

@baconpaul
Copy link
Collaborator

What I can do is make the display (if (is standard tuning) “st” : “scale notes” )

@mkruselj
Copy link
Collaborator Author

mkruselj commented Jan 22, 2020

What I can do is make the display (if (is standard tuning) “st” : “scale notes” )

Will be good enough. "st" vs "notes" is a fine (and short and to the point) distinction. Maybe it should actually say "keys" then? Because a "note" can mean other things (i.e. quarter, half, whole note).

@baconpaul
Copy link
Collaborator

I’m going to push this out of 1.6.5; the st/note thing is too much engineering and some of the others require re-typing some params which is too much surgery this late in the game. Will keep it open of course just not in this release.

@baconpaul baconpaul modified the milestones: 1.6.5, Currently Unscheduled Jan 24, 2020
@baconpaul baconpaul modified the milestones: Currently Unscheduled, 1.6.6 Feb 1, 2020
@mkruselj mkruselj added the UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc. label Feb 5, 2020
@mkruselj
Copy link
Collaborator Author

This is now closed after all the work on Ctrl+drag I did.

@mkruselj
Copy link
Collaborator Author

Actually it isn't because modulation amounts still don't use the relevant units based on the parameter they're modulating, sigh...

@mkruselj mkruselj reopened this May 25, 2020
@mkruselj
Copy link
Collaborator Author

mkruselj commented Jun 2, 2020

Successfully PRing #1991 will close this one too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.
Projects
None yet
Development

No branches or pull requests

2 participants