Skip to content
This repository has been archived by the owner on Nov 24, 2024. It is now read-only.

Max steps #17

Open
Andreya-Autumn opened this issue Nov 6, 2024 · 0 comments
Open

Max steps #17

Andreya-Autumn opened this issue Nov 6, 2024 · 0 comments
Labels
JUCE Needs further study of JUCE APIs etc Tuning Issue related to the tuning features themselves
Milestone

Comments

@Andreya-Autumn
Copy link
Owner

What should it be?

PositionX and PositionY are signed ints. The parameters which set them are also int types. With that structure, the max we could actuallty use it MAX_INT which is much much further than someone would need in any real music (even writing a deliberate comma drift example, you wouldn't even come close unless you let it run for days).

But how much is a good amount? Right now it's +/- 24 steps which is definitely too little. But once you get past +/- 50 or so, parameter automation in DAWs will become annoyingly finnicky. That's the advantage to keeping it small. And most of the music people will want to make with this probably lives within +/-10 steps or so... but some folks will definitely want to write those comma pump etudes and let them run... Tricky!

You could make this a user setting. But it would require re-negotiating the parameter range. Juce deals with that fine, but not all hosts do.

Probably I'll eventually do that anyway, and have the setting pop a window on change warning the user that they may need to re-load the DAW to make the change take effect.

@Andreya-Autumn Andreya-Autumn added Tuning Issue related to the tuning features themselves JUCE Needs further study of JUCE APIs etc labels Nov 6, 2024
@Andreya-Autumn Andreya-Autumn added this to the 1.0 milestone Nov 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
JUCE Needs further study of JUCE APIs etc Tuning Issue related to the tuning features themselves
Projects
None yet
Development

No branches or pull requests

1 participant