Automated nodes are very unintuitive #62
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lubba64/node_sound#62
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is a powerful feature of the application, and it’s really unfortunate that people really could
not figure out how to use it effectively. Automated nodes are nodes that allow you to change a
parameter over time, by controlling it with another audio source. Every automation has a
minimum and maximum value associated with the minimum and maximum of the audio source.
Currently you have to use a node called TranslateWave, which is extremely confusing to the
user to have to drag out a second node. And the other issue is that TranslateWave allows you to
change the input min and max, which is not something we need and just confuses the user
further.The proposed fix is removing the TranslateWave node (Breaking change) and move the
min and max directly onto each parameter of the automated node, so all of the settings for that
node are in the same place, and the tooltip will be much clearer because it can say “Min and
Max for parameter X control the min and max values of the automation” Which is better than
“Drag out a TranslateWave node and find out what it does”. There are a lot of nodes that would
need to be edited, even if this is a simple change. Should take no more than 3 hours.