HISE Logo Forum
    • Categories
    • Register
    • Login

    Updating product and preset procedure

    Scheduled Pinned Locked Moved General Questions
    6 Posts 5 Posters 186 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

      Currently working on a project that will see new algorithms in the future (hardcoded DSP), I have a question regarding the preset compatibility.

      There's the Overwrite Old User Presets that takes care of the Factory presets, but then is there a way to populate customer presets with new controls?
      If not, is there a risk to load an older preset? (aside from just having new parameters not moving...)

      Anything I should be particularly careful about when developing and/or exporting?

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

      d.healeyD clevername27C orangeO 3 Replies Last reply Reply Quote 1
      • d.healeyD
        d.healey @ustk
        last edited by

        @ustk UserPresetHandler:

        https://docs.hise.audio/scripting/scripting-api/userpresethandler/index.html
        https://docs.hise.dev/scripting/scripting-api/userpresethandler/index.html#isoldversion
        https://docs.hise.dev/scripting/scripting-api/userpresethandler/index.html#setenableuserpresetpreprocessing

        Libre Wave - Freedom respecting instruments and effects
        My Patreon - HISE tutorials
        YouTube Channel - Public HISE tutorials

        ustkU 1 Reply Last reply Reply Quote 2
        • clevername27C
          clevername27 @ustk
          last edited by

          @ustk The biggest risk, I would guess, is if HISE is attempting to load values into components that don't exist.

          1 Reply Last reply Reply Quote 1
          • orangeO
            orange @ustk
            last edited by orange

            @ustk If there is a new parameter and the old preset does not contain it, the parameter will be loaded at the default value. So far I haven't seen any problems with this.

            Therefore, for the backwards compatibility, when adding a new parameter-algorithm, it should be added by default in a way that does not affect old user presets.

            develop Branch / XCode 13.1
            macOS Monterey / M1 Max

            1 Reply Last reply Reply Quote 1
            • ustkU
              ustk @d.healey
              last edited by

              @d-healey @clevername27 @orange Thanks guys for your precious answers!
              I have to delve into the PresetHandler, I'm not sure it could be/is helpful in this case.

              But anyway if nothing bad can happen loading an older preset, I'm feeling relieved already 😃

              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

                @ustk said in Updating product and preset procedure:

                But anyway if nothing bad can happen loading an older preset, I'm feeling relieved already

                Yup as @orange said, if you're only adding new controls, just make sure that the default values are sensible and they will be initialised to those values.

                There are more advanced tools available in the UserPresetHandler class, but they are only required if there are breaking changes in your preset design (eg. because you have changed internal ranges or something else).

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

                15

                Online

                1.8k

                Users

                11.9k

                Topics

                103.7k

                Posts