Request: ScriptNode Control.map Node
-
Basically a cable version of the map node.
Currently, when working with values from anything with cables including minmax, pma etc., it takes 5 nodes to properly use the map node in a chain in a way that lets you cable the output elsewhere:
- clear
- add
- map
- peak
- clear
-
@aaronventure Agree, I asked for this already, it would be very useful
https://forum.hise.audio/topic/11739/request-control-cable_map?_=1739003974441 -
Isn‘t the minmax node doing the same already?
-
@Christoph-Hart no, because the value is always 0-1. If I change the range of the value, it still only scales 0-1 to the minimum and maximum.
Also, it cannot be dynamically changed like the map node.
-
@aaronventure what if you slap a normaliser node before the value connection? All it does is converting the input range to 0…1 which is the first missing part of the map node functionality.
-
@Christoph-Hart not sure I follow
I changed the range on the Value parameter to 0-0.1, it still outputs the raw value to minmax value.
Even so, it's still not dynamic.
I think it's just a missing node, what are the odds of using it in a signal path instead of using it to cable things around? Dynamic range adjustment, that's it? It's much more likely to be used in the context of pma, cabletable, inputToggle which are the workhorse nodes for value manipulation when creating modulators.
Overall there's a workaround, so it just depends on how much time this takes you to do. This is just a QoL request.
