You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: