HISE Logo Forum
    • Categories
    • Register
    • Login

    Plugin code

    Scheduled Pinned Locked Moved General Questions
    16 Posts 10 Posters 1.1k 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.
    • Dan KorneffD
      Dan Korneff
      last edited by

      There used to be a database to register your code, but hasn't been maintained in years.
      There's a VST plugin registration form from steinberg:
      http://service.steinberg.de/databases/plugin.nsf/plugIn

      From what I understand of AU, the plugin Type, Manufacturer, and plugin code need to be unique. That will limit the amount of possible collisions with other plugin codes.

      Dan Korneff - Producer / Mixer / Audio Nerd

      1 Reply Last reply Reply Quote 1
      • Y
        yall @d.healey
        last edited by

        @d-healey I think, but to verify, that the code also corresponds to the name that you give to your projects. your plugin and vst in application support are in a single folder and both folder correspond to plugin. So even if another brand has the same code as you on a plugin, they will be 2 different folders in application support. maybe I'm wrong but a 4 letter code is quite limited anyway

        1 Reply Last reply Reply Quote 1
        • d.healeyD
          d.healey
          last edited by

          456976 possibilities.

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

          Y hisefiloH 2 Replies Last reply Reply Quote 1
          • Y
            yall @d.healey
            last edited by

            @d-healey It's true that it does a lot of plugin 😂😂

            1 Reply Last reply Reply Quote 0
            • gorangroovesG
              gorangrooves
              last edited by

              I think that the issue will likely occur only if another plugin manufacturer has the same manufacturer code and then uses the same plugin code as you. I ran into issues where I used the same plugin code on two plugins and one of them would not show up. So, as long as your plugins all have unique plugin codes, it is unlikely you will run into issues.

              Goran Rista
              https://gorangrooves.com

              Handy Drums and Handy Grooves
              https://library.gorangrooves.com

              1 Reply Last reply Reply Quote 1
              • hisefiloH
                hisefilo @d.healey
                last edited by

                @d-healey I can remember to change the plugin code on Mac to avoid plugins to load stored data from older versions of it. So it make that plugin unique on your system I suppose. (don't know if 2 plugin form different devs can have same code. I guess yes)

                1 Reply Last reply Reply Quote 1
                • FrankbeatF
                  Frankbeat
                  last edited by

                  From my experience today, I'd dare to say it has serious relevance for at least some Mac systems (I'm working on High Sierra).

                  I experienced this weird behavior in Cubase: I had saved a project holding an instance of MyInstrument1. Later I also installed MyInstrument2 on that machine. Then I reopened that Cubase project and now it had an instance of MyInstrument2 when it shouldn't even know of the existence of it.

                  This bugged me for a day so I decided to have a closer look on the HISE project settings before export. It just felt right to replace Abdc by something related to me. I can't tell if really this was the culprit, but now I have both VSTs to choose in Cubase.

                  Using HISE from the develop branch (Feb '23)

                  1 Reply Last reply Reply Quote 0
                  • A
                    andioak
                    last edited by

                    This should be pretty easy to test out. One developer ID with 2 separate plugin codes. A few testers on different DAWs and machines with different OS versions.

                    I can be a tester on anyone's plugins. Do not, however, have a project ready or a functioning HISE install, cause of a re-installation issue at the moment...

                    1 Reply Last reply Reply Quote 0
                    • S
                      Soundavid
                      last edited by Soundavid

                      The Plugin Code are tied up with the Vendor Id, The code can be the same for two different developers but the most relevant code is the Component Manufacturer.

                      Link Preview Image
                      componentManufacturer | Apple Developer Documentation

                      The unique vendor identifier, registered with Apple, for the audio component.

                      favicon

                      Apple Developer Documentation (developer.apple.com)

                      Apple hasn't maintained this code registration for a long time so the recommendation is using something unique to your company and not using posible used codes like Wavs or Uadc or Demo...

                      The Bundle Identifier is important too, com.yourCompany.yourPlugin, when you sign two Plugins with the same Identifier could have some issues.

                      1 Reply Last reply Reply Quote 1
                      • clevername27C
                        clevername27 @d.healey
                        last edited by

                        @d-healey On the Mac side of things, just pick something you think will be unique, and don't worry about it.

                        LindonL 1 Reply Last reply Reply Quote 0
                        • LindonL
                          Lindon @clevername27
                          last edited by

                          @clevername27 said in Plugin code:

                          @d-healey On the Mac side of things, just pick something you think will be unique, and don't worry about it.

                          The Mac side is where the problems are - specifically Logic - which is one of the few DAWS to be rigorous with this Plug-in/vendor code stuff..

                          HISE Development for hire.
                          www.channelrobot.com

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

                          49

                          Online

                          1.7k

                          Users

                          11.7k

                          Topics

                          102.1k

                          Posts