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

Syntona V0.5.12. build 39, fader behavior #57

Open
DoctorNerve opened this issue Oct 16, 2017 · 0 comments
Open

Syntona V0.5.12. build 39, fader behavior #57

DoctorNerve opened this issue Oct 16, 2017 · 0 comments

Comments

@DoctorNerve
Copy link
Collaborator

I tested new fader behavior by connecting fader to frequency aInput of a Voice and confirm that if unedited, the fader takes on the min/max/default of the aInput and if edited, fader values will not be affected by aInput. This is nice.

Suggestion: I think that if I edit a fader and then connect it, it should kick the value into the aInput. So for example if I set fader value to 220 and connect it to frequency, I expect to hear the osc change tone. Either that, or it would be nice to have a kick on the fader itself so that after I connect it, I can just kick it with my mouse and it'll send the current value to the aInput. (I know I can open the fader edit and kick it like that, or connect a kick to it). But as a convenience, I think a kick on the fader itself where the user can click would be helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants