thank you for the details. Wow. that's much more complicated than I thought.
I am using the exposed parameters for my MIDI controller. With the newly added modules I just had to add the new parameters, and everything was working as before. Rather easy, and I'm glad about it. As you said, adding the new parameters to the back of the parameter list.
Diva digital osc shape - no automation/mapping?
-
- u-he
- 30248 posts since 8 Aug, 2002 from Berlin
I spent a LOT of effort ensuring that adding new parameters is a piece of cake. As one would notice from my first released plug-in, MFM 1.0, "adding parameters" is kind of how I like to work 
The funny thing about it is, it has restricted me in other ways, and we now have to do quite elaborate things to keep things sane.
It's easy to stay sane when one develops plug-ins "the easy way", like, having a big long list of parameters somehwere in a central file of the codebase. Had we had that, there would never have been any confusion. We'd (maybe) have properly working VST3 versions.
However, maintaining such a global parameter list is tedious. It slows development down and creates a dependency nightmare between building blocks.
Instead, we have an approach that automatically generates a list of parameters from all the modules that were added to a plug-in. That's extremely useful and adding a parameter is pretty much done with a line of code. It's cool, but it also makes a change like unhiding a parameter a pretty complex enterprise. We have to look through a lot of code if something unexpected happens
- Urs
The funny thing about it is, it has restricted me in other ways, and we now have to do quite elaborate things to keep things sane.
It's easy to stay sane when one develops plug-ins "the easy way", like, having a big long list of parameters somehwere in a central file of the codebase. Had we had that, there would never have been any confusion. We'd (maybe) have properly working VST3 versions.
However, maintaining such a global parameter list is tedious. It slows development down and creates a dependency nightmare between building blocks.
Instead, we have an approach that automatically generates a list of parameters from all the modules that were added to a plug-in. That's extremely useful and adding a parameter is pretty much done with a line of code. It's cool, but it also makes a change like unhiding a parameter a pretty complex enterprise. We have to look through a lot of code if something unexpected happens
- Urs
-
Echoes in the Attic Echoes in the Attic https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=180417
- KVRAF
- Topic Starter
- 12066 posts since 12 May, 2008
I see, thanks for the explanation.
Well I'm glad it's something you are considering carefully as I really believe that parameter IDs are becoming the standard way of mapping to hardware instead of midi. IT's always wonderful to see a plug-in with a fully automatable parameter set, drop down boxes, buttons and all, because you can basically turn that into a hardware synth.
Well I'm glad it's something you are considering carefully as I really believe that parameter IDs are becoming the standard way of mapping to hardware instead of midi. IT's always wonderful to see a plug-in with a fully automatable parameter set, drop down boxes, buttons and all, because you can basically turn that into a hardware synth.