Engine.getCurrentUserPresetName() not working
-
-
Preset engine must have a complet revision
-
Preset loading is asynchronous (otherwise it would timeout the script) so you can‘t call directly after loading a preset.
I am using a timer with a slow interval (0.5 seconds) that checks whether the preset has changed.
-
@christoph-hart aha that makes sense, I'll give it a go
-
So I put
Console.print(Engine.getCurrentUserPresetName())in a panel's timer callback and it still outputs nothing, so then I tried putting it in the onNoteOn callback and even though the preset is loaded the output is still empty, what am I missing?
-
It's definitely working in HEXERACT but I'll take a look at it.
I am currently rewriting the convolution reverb to support background rendering & predelay and damping, but after this I'll clean up the preset API and take a look at all you sample related requests.
-
@christoph-hart Thanks Christoph, no rush
-
I think most of the problems about it could be resolve if you can choose the folder for user presets,( as you can do with sampler folder when you lunch at first time the standalone app), maybe not...., it´s just a suggestion....(move the userpreset folder out of Appdata/roaming folder).
When you create a new user preset in Hise enviroment there´s no problem, but when you create it outside HISE ( the compiled app) the problems appear... ???? !!!!
-
More flexibility about userpreset files location is what I mean....
or more transparence about that ....
-
No why would you want to do that? The sample location is changeable because you might not have enough space on your main drive for the gigabytes of data, but the user presets are merely a few kilobytes.
The only design flaw is that the three level folder hierarchy is hardcoded but apart from that and some API inconsistencies the system is fine.
-
Ok, If you think so, I´m a merely beginer....
Probably I´m wrong..., very sorry
-
Engine.saveUserPreset()Doesn't seem to be working either, maybe the two issues are related.
-
@d-healey
I think there´s a inconsistency between saveUserPreset , loadUserPreset and the folder hierarchy...., in my modest opinion...There´s no problem when you use the Preset Browser floating tile , however...
-
Yes this will be cleaned up (the saveUserPreset function is much older than the rest). And the three folder hierarchy will only be used if you use the inbuilt preset browser, otherwise you can use any folder structure you want.
-
@christoph-hart Any progress with this?
