HISE Logo Forum
    • Categories
    • Register
    • Login

    Request: ScriptNode Control.map Node

    Scheduled Pinned Locked Moved Feature Requests
    6 Posts 3 Posters 99 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      aaronventure
      last edited by

      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:

      1. clear
      2. add
      3. map
      4. peak
      5. clear
      ustkU 1 Reply Last reply Reply Quote 1
      • ustkU
        ustk @aaronventure
        last edited by

        @aaronventure Agree, I asked for this already, it would be very useful
        https://forum.hise.audio/topic/11739/request-control-cable_map?_=1739003974441

        Can't help pressing F5 in the forum...

        Christoph HartC 1 Reply Last reply Reply Quote 0
        • Christoph HartC
          Christoph Hart @ustk
          last edited by

          Isn‘t the minmax node doing the same already?

          A 1 Reply Last reply Reply Quote 0
          • A
            aaronventure @Christoph Hart
            last edited by

            @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.

            Christoph HartC 1 Reply Last reply Reply Quote 0
            • Christoph HartC
              Christoph Hart @aaronventure
              last edited by

              @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.

              A 1 Reply Last reply Reply Quote 0
              • A
                aaronventure @Christoph Hart
                last edited by

                @Christoph-Hart not sure I follow

                9cce4a7f-9ebc-44a8-be68-9835d0325fc3-image.png

                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.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post

                12

                Online

                1.7k

                Users

                11.8k

                Topics

                103.1k

                Posts