Forum
    • Categories
    • Register
    • Login

    Plugin parameter values as names

    Scheduled Pinned Locked Moved Feature Requests
    4 Posts 2 Posters 56 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.
    • T
      tomekslesicki
      last edited by

      Hey @Christoph-Hart , would it be possible to add support for named plugin parameter values? For example, if I have a stepped slider that selects something, like an EQ shape or some other parameter, display it in the DAW not as 0, 1, 2, 3, etc., but low shelf, peak, notch, high shelf, etc.? Thank you!

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

        @tomekslesicki doesn‘t this already work with comboxes automatically?

        T 1 Reply Last reply Reply Quote 0
        • T
          tomekslesicki @Christoph Hart
          last edited by

          @Christoph-Hart I guess it might, I was just ignoring them my whole life! If I was using numerical values up to this point, and will replace them with a combobox, will the numbers translate to name values? So value 0 will be name 0, value 1 name 1 and so on? This is a question about older session compatability

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

            @tomekslesicki yes, if you keep the value range the same, you should be able to switch to comboboxes for named plugin parameters without backwards compatibility issues. The plugin APIs do not store the text value in the DAW project, but the index and the text is a simple text lookup requested by the plugin API.

            You might want to test this though as I can't guarantee that there are no glitches with this. Also watch out for off-by-one issues - zero in a combobox usually means not a value so the first item starts with 1.

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

            24

            Online

            2.2k

            Users

            13.3k

            Topics

            115.8k

            Posts