Custom Preset Browser example
d.healey last edited by
@orange You can already implement an A/B comparison, this is the responsibility of the dev not of HISE... I think
orange last edited by
@d-healey You are right. But it is not only A/B comparsion. I've written all the ideas above
You have all tools available to build your custom preset browser:
It may be possible that at some point I add more properties to the PresetBrowser and make it more generic, but the general idea is: use the inbuilt thing until it doesn't meet your requirements anymore, then roll your own solution. This step might be tedious, but I can't put every option that anybody might ever think of in the generic preset browser.
jadg last edited by jadg
A problem with all this is :
Everytime you need a litle modification of a preexisting user preset you must create a new one because you cant overwrite with this method the user preset file.
In a few time you´ll have hundreds of user presets, making tedious the action of looking for and selecting them.
Why is not posible overwrite the user preset file with the Engine.saveUserPreset() method ?
d.healey last edited by
@jadg Christoph said he's going to change it this week to do that
I'll come up with a clear API for this in the next days...
jadg last edited by
ok, of course,
@christoph-hart Yes man you are right, it's impossible to put everything that anybody might ever think.
But believe in me, the things that I've mentioned are standarts for a plugin and it will meet everybody's needs. So no one can ask you a different idea. So why HISE doesn't have such generic features / standarts that every plugin developer needs... I'm sure if you would have enaugh time, you would the best bro.... I understand you.
Here are just a few different companies that uses this menu structure like other fx plugin developers...
d.healey last edited by d.healey
@orange I can show you many others that don't It is better if Christoph creates an API that each developer can use to make their own preset handling solution rather than having one setup that will suit some people but not others.
For example for my current project I'm using the preset system to change entire instruments and this reloads all the sample maps, an A/B button would not be very useful for this purpose.
@d-healey A/B button is used for fx plugins, not for instruments
Yes, it's better to have API so the developers can customize their own preset menus.