Link in vst
-
@d-healey this is the extract just above
-
@yall I mean show me where you are loading the samplemap into the sampler.
-
@d-healey I put the sampler in the big screen. and in the "select expansion" section. I can clearly see my expansion. then on the drop-down window of the sampler (where you can choose your sample Map) the window is empty
-
@yall You mean there are no sample maps to choose from?
-
@d-healey yes
-
@yall Does it work if you install it manually?
-
@d-healey I just got it. stupid mistake on my part.
I took an extension created on another project. I redid an empty project to try. it didn't work because the sampler didn't have the same name. already error. then I just understood that the samples extracted, we could put them where we wanted because there was a link windows file in the expansions folder.
so now everything is working as I wanted. now, for the user, the extracted folder will be automatically present in AppData? -
@yall Yep
-
@d-healey thank you for your time :)
-
@d-healey I just tried in a compiled vst it works perfectly. at the end of the cycle, the "select hr1 file" window is still present. is this normal?
moreover, how to add a progress bar?
I'm thinking of preparing a project to share here for the noobs like me -
@yall Everything you need is in the docs :) https://docs.hise.audio/scripting/scripting-api/expansionhandler/index.html#installexpansionfrompackage
The select window shouldn't be there. My guess is you forgot to check the value of your momentary button in the callback before triggering the install function, so it's actually triggering twice (once when you press the button and once when you release).
-
@d-healey precisely it is momentary that's why I'm asking the question ^^
-
if (value) { // Do stuff here }
-
@d-healey I modified. it works as it should when the button is not momentary
-
@yall It will work when momentary too. You just need to put the value check in the button callback so it only triggers when the button is pressed not released.
-
@d-healey now i'll work on a progress bar .. stay tuned lol
-
@yall I tried this function before modifying it. during the loading the panel changes color well but once the loading is finished it remains on the loading color. Any idea?
const var panel = Content.addPanel("Panel", 0, 0); panel.data.colour = Colours.grey; panel.setPaintRoutine(function(g) { g.fillAll(this.data.colour); }); // This function will be executed whenever the preload state changes panel.setLoadingCallback(function(isPreloading) { if(isPreloading) this.data.colour = Colours.white; else this.data.colur = Colours.grey; // Update the UI this.repaint(); });
-
@yall Check your spelling.
-
@d-healey the o of color was missing ^^ I had taken the example of Christoph without an auditor. So I got to rewrite from scratch. 1 / invisible panel 2 / loading = visible panel 3 / fin = invisible panel it seems that creating a progress bar is too complex at my level so i'm thinking about this. once the panel is opened for loading, I integrate an automatic rotary knob with a film strip loading logo image as well as a "please wait" message. just one thing to ask you .. once the loading commcé, my button turns automatically and at the end of the loading it becomes invisible. Is it possible to tell him to stop the rotation? it has become invisible while it is still spinning is useless
-
@yall Just stop the timer