HISE Logo Forum
    • Categories
    • Register
    • Login

    Is the range warning indicator an issue for unscaled parameters?

    Scheduled Pinned Locked Moved General Questions
    7 Posts 4 Posters 494 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.
    • ustkU
      ustk
      last edited by

      When connected to an unscaled node the warning still shows up despite the range being the same.
      Does it means troubles down the road?

      Screenshot 2025-09-25 at 19.34.49.png

      Hise made me an F5 dude, browser just suffers...

      Dan KorneffD 1 Reply Last reply Reply Quote 0
      • Dan KorneffD
        Dan Korneff @ustk
        last edited by

        @ustk I've ignored them... wondering the same 😆

        Dan Korneff - Producer / Mixer / Audio Nerd

        ustkU 1 Reply Last reply Reply Quote 0
        • ustkU
          ustk @Dan Korneff
          last edited by

          @Dan-Korneff lol 🤣 🤞

          Hise made me an F5 dude, browser just suffers...

          HISEnbergH 1 Reply Last reply Reply Quote 0
          • HISEnbergH
            HISEnberg @ustk
            last edited by

            @ustk I ignore them too and don't have any issues. 😊

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

              @HISEnberg yeah if they are connected to a unscaled parameter the warning is pointless, but if not it might have performance implications or subtle range mismatches.

              I can look into removing the warning for unscaled parameters, but it's not super straightforward to do so.

              HISEnbergH 1 Reply Last reply Reply Quote 2
              • HISEnbergH
                HISEnberg @Christoph Hart
                last edited by

                @Christoph-Hart yes you are right.

                I don't think there is a justification for removing them on the unscaled parameters, you can figure out pretty quick if the parameter linking is broken using your ears in most cases, plus it's a good reminder to just try to make the ranges match (even if it doesn't always work).

                ustkU 1 Reply Last reply Reply Quote 0
                • ustkU
                  ustk @HISEnberg
                  last edited by ustk

                  @HISEnberg Well my fear wasn't if it work or not in the network and in Hise in general but I reckon a compilation issue with those warnings...
                  So if no issue with that, perhaps it would be easier for you @Christoph-Hart to just put a message in the range popup or anything telling the user not to worry about.
                  A warning is here to make you shaking and to remind you that the abyss is closer than you think... 😱

                  Hise made me an F5 dude, browser just suffers...

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

                  24

                  Online

                  2.0k

                  Users

                  12.6k

                  Topics

                  109.5k

                  Posts