Store values in ScriptPanel data object

[toxonic]

@Lindon Oh, i see, i misspelled stutterPresets in my comments (i wrote stutterPanels), but I already tried that. The switch / case statement in UI_PanelsCallback seems not to be triggerd, so i tried to

UI_Panels[0].setValue(stutterPresets);

in diffenerent places, but it always results in a single 0.0 value in the dummy array (and some error messages related to that).

[Lindon]

@toxonic what is this giving you?

Console.print(UI_Panels[0].getValue());

[toxonic]

Okay, i made a mistake first... :D
The console spits out [Array], so i just don't really know, what's wrong....

EDIT: Inside the UI_PanelsControlCallback it spits out 0

[toxonic]

@toxonic I think I just have a basic problem understanding, how and where to store and recall values in panels.... :-(

[d.healey]

@toxonic Why are you wanting to store values in a panel in this way? There is probably a better way to do what you want.

[ustk]

@toxonic This should help you to understand the principle:

HiseSnippet 1486.3ocsW0raabCDlqr2zraZRZ.5wdfPmjPUbjb9soHs1R1tPMwxBVNIsHnHfZWJKFuhbAWJ6HXXfdnO.8QnuB8Mq25wzgjqzt5GqXKftHHVbFNC+luYHGx1RQ.MIQHQNdGMJlhb9R2Ni3p9M5SXbTycPN2wsiRHoM4sIbZDp9nXRRBMD43r1Oomii25Hy2+7i0IQDd.MSDB8FAKf9J1.lJSZ6sdIKJZORH8H1fby9Qa0LPvaHhDCA7rlaUTLI3DxwzVD8zJ3hbtwtgL.McTDEMAlScQ3nN8Emwsy+MrDV2HpdPMTGvQVwnF8YQgsGGqIHjy5syh70rQ9W6tOKjMQdFC7UFE3LKxyANEVFjpcMfjSNHstER2ysSfjEqxznwysbaxUTYOBP04ghctnBCccaHfYvUaLfbBcOILXhEkdR0pUvv+U9688A5NQgOkHwljaM7Kvis7XppgXPrfCCJUzptHXSlI0GpTB9kaSp9oM5kbQ2K2DiVsA9O3A3s4XQ2OPCTXUehBmnqBSfeSwAis.DpY8b92H3fte.Vhy6p3OuGIJgVAeBu6yqtQ0K.Oa7c6sas6qvMpiKkPNUWaCtlpvTNAxUgk8Y7HFmh6MjGnXB.H1p+ZZXKEQklffJvpFMjV1+beOvuGRCHQQ3dRw.brwm9drd3RJHcJ5kYlNtei1vRkKiewKvEsQZwx9dfi7RotMRFOKyhrADP.2joNnOgeLMrjQH7OC8MqQPnazaUl2jKLP9.fznJCulR2.fiDjPF+XizXovHtmPZF2iIAxVAac88n.6B9NKtlr3iSDvBArtk8zZSYvF.M0E1cWZFlsrICoSQ0Op07InPVxklgRYkOWJZGA9LndhdJU56ASNQDQ2HVxf5uoROMARB+s3hOGWD9i0E.oY7wqiCAOXK1vDdns3Dy33Xcv36MN50oLnTzXMXbFMrHRJWVedVZ5nKildYqCpe83ISgvRYoUgUlDwP81UNhmTvNe7lGkoQq4KWfzR.thWx.Y+K7wyppWuEpK0oQT4BUq6IIWlgk3CGzkJySX5IBGZOcmfab05DDXOIL2DE7lbl5fXZ538DQg5S30+d99FnziR0cPRQHLUko+wsG2+vz5lA93lt1LBx.djy8c+4NGz57hPcJjSgiHqfKBYPyue12Y9d5Sp83mU6QaV6BD50M2gnHiWJXUAjDSkJlNfc1gdJzs215xycGZxIJQLvKSNgG439YA1GytPvut0n7CxWgCqVAz798No90taw3XO2zsN477Vw477u+tY87ZKwychXgTowyegqoHMme+qQKEwS42aoRu0g0u6AG4pfibOhAkHZueW27hlhW9g7n+jsRSEVd+tt1kqtTbVB.ztGO9BUd2.l9+psgonCxj92e5O+zzR2LcxlOSBuveTv8beLtntLsCDUVNEJSTxgzJi0r6Ggy+RfcKIam.tZ3.8LrsfGOESwrbwlq20lLmOgMU1oOkpLwv9bHdAc0pNwnsCCW7RbHzhevkf9cnQT0knaOxoBIvP5anlWWJxZBQcHstPBw1TgbqgCrDgF7OzHxN9srPU+Cg7q.T7NPNF1w8vY9pbMkCh+MyZ7JVhZaIkLgaRWgJK5OSrxhrCEm0lDpa+eUsqCkHC5WmHqKFxC0Q56rJ1G5JZYnY0jUCMqlwL8bZ8u.cllzfsjNeSADpOkcbe8FTmsbzupXtaOC2aWDNLhnl9x75Wsjp.pTm5Fz5aICYR0n7up4ZbC+pK8F9WUHdO21LUP+EiwBK.iv4w+efwz2Eca2c60Ct.XF.W2cueYUeDzmY4OTLTej29DkjAm34B6e5.mHEPgUmC8GRz46B5td1wU0i0LPGJOzL3SvWpxZ5wNoJqMVIZ.IPJdefsWo9kW2zHAvD27PSO280iwSZR55BMFQCfGA99f.c3eenQ7hsYyUvlGtB17nUvlGuB17jUvlmtB17rkZi982aOTIFX2N.BZuqoujiyt1mrY5t9e.4zdxOB

Note that, as @d-healey said, there might be a better way for your use case. My example makes no sense since knobs and buttons can be saved in preset, but it's just an example for storing an object in a panel... I use this to store other kind of data than component values (and this was before the apparition of file handling...)

[toxonic]

@d-healey @ustk i'm not at home at the moment, but i'll try your example tomorrow. Indeed i want to store knob values , but in my project i use a sequencer, and when i try to use the preset browser, the sequencer will stop running on each preset change, so i can't use that option.
What could be another approach?

[d.healey]

@toxonic You could write the values to a file. Using a panel also relies on the preset system BTW.

[toxonic]

@d-healey okay, that's a good point!

[toxonic]

Saving values in a file works fine so far, this seems to be the way to go for me.
Just a quick question: which directory would i have to specify in the code, that the compiled plugin can find the preset files in it's own directory (or maybe a subdirectory)? is there a wildcard for that?

[d.healey]

@toxonic I'm not entirely sure of the question but I think your answer might be here - https://docs.hise.audio/scripting/scripting-api/filesystem/index.html#special-locations

[toxonic]

@d-healey ahh, okay! Is there a way to embed the textfiles with the stored parameter values in the compiled binary? I mean, i don't want the end user needing to care about the correct location for the files in order to get the compiled plugin working properly.

[d.healey]

@toxonic Just include them as scripts

[toxonic]

@d-healey Okay, i didn't know, that this works. Actually, the files are saved in the UserPresets Directory.

1. Do the files need a special filexetension, like .js?
2. Can i pass the path in the include statement? Soemthing like

include ("./UserPresets/filename");

or do the files then need to be stored in the Scriptssubfolder in order that HISE can find them?

3. Can the content of the files be modified, when the the plugin is compiled, so that the user can change the "presets" ?

Sorry for all these questions, but i never used includes for anything other than external scripts...

[d.healey]

@toxonic They will need to be js files and they need to be in the Scripts folder. The content can't be changed because they are part of the plugin. If you want the files to be separate then you need to find a way of including in one of the appData folders.

[toxonic]

@d-healey Okay,thank you for your quick response!
How will the AppData folder be created? When i compile a plugin i usually only find the compiled binary. Is there any information on that topic out there?

[d.healey]

@toxonic That folder is created automatically when the plugin/standalone runs the first time. If you want to put files in it then you'll need to build an installer that creates the folder and puts the files there.

[toxonic]

@d-healey uhh, that sounds complicated...

[d.healey]

@toxonic Yup :)

[d.healey]

If these are standard HISE preset files though (.preset) then they will automatically be in the appData/User Presets folder.