-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
[Audio Feature]: min / max value #453
Labels
Comments
2xAA
added a commit
that referenced
this issue
Dec 1, 2020
* feat(expression): adds expressions Adds the expression editor from modV 2 fix #453 fix #415 * feat(expressions): adds time variable to scope * feat(expressions): adds preset save/restore to expressions state * feat(expressions): Make textarea fill up the whole space * revert(expression): reduces textarea size to align with tween textarea Co-authored-by: Tim Pietrusky <[email protected]>
2xAA
pushed a commit
that referenced
this issue
Dec 1, 2020
🎉 This issue has been resolved in version 3.5.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I'm frustrated that the min / max that already exists for a module property is not used when attaching an audio feature to that property.
Describe the solution you'd like
Either add another min / max input to the audio feature or use the min / max value also as a range for the property value including the changes from the audio feature.
Describe alternatives you've considered
In modV 2 we could use expressions, but in modV 3 there is no possibility to limit the changes an audio feature has on a property.
Additional context
Party related to #415
The text was updated successfully, but these errors were encountered: