Expansion User Presets

[d.healey]

I think I might have solved the samplemap thing.

I was loading the sample map as {EXP::Kazbek}duduk_staccato.xml in my script. But it seems that I only need duduk_staccato.xml and HISE automatically works out that it's a sample map that belongs to the active expansion and fills in the rest.

So in my HISE project I need to specify the full sample map name but when I export I don't need to.

There's still some other funny stuff going on in my exported app but at least I seem to have figured out this one :)

[Christoph Hart]

So in my HISE project I need to specify the full sample map name but when I export I don't need to.

Well that's bad. You definitely shouldn't branch the script logic whether you're in HISE or in the compiled plugin. I'll take a look why it doesn't work.

[d.healey]

Also it seems I was premature when I said my test show everything as fine. I've now tested it with my larger project (probably should have done that before) and the scripts are being called before create expansions. I'll look into this some more.

This is the same with deferred callbacks enabled or disabled (which makes sense I guess since it's the init and control callbacks).

Compiling all scripts
Unknown function 'loadDataFile'
This expression is not a function!
no iterable type
Adding plugin parameters
Restoring global settings
Setting disk mode
Samples are validated. Skipping reference check
Loading samples
CREATE AVAILABLE EXPANSIONS

Edit: Actually the get list function is being called first. I'll shut up now until I figure this out :p

[d.healey]

Ok, after lots of poking around and head-scratching, I figured it out (as you thought) createAvailableExpansions() isn't being called until after getExpansionList(). So what I've done is put a call to rebuildExpansions(); inside the expansion handler constructor, do you think it would be more appropriate/better to call it from the getExpansionList() function, or somewhere else?

The other piece of the puzzle was I had HISE_ENABLE_EXPANSIONS=1 but not HI_ENABLE_EXPANSION_EDITING. So the Helpers::isValidExpansion was returning false. I've modified this to check for file based expansions as well as encrypted without needing editing enabled. Let me know if there is a better way to handle this too.

Also now I got around this issue I noticed my sample maps weren't loading again :( so I reverted to the previous format and it works, so not sure what was going on before but the correct format both in HISE and the exported app is "{EXP::" + expansionName + "}" + sampleMap + ".xml"

[d.healey]

I've created a pull request. I noticed that my text editor seems to have saved every blank line as a change which unfortunately clogs up the changelog a bit :( I'm assuming this is due to the line ending difference between Windows and GNU/Linux so next time I make edits I'll switch to Windows style line endings and see if that solves it.

[Christoph Hart]

Yeah I try to figure out how to show the actual diffs, because I can‘t check in stuff into the precious codebase without reviewing it ;)

[Christoph Hart]

Not sure if you noticed, but I merged the request and ran the API generator over it so you can use your script functions now in the "official" branch.

[d.healey]

@Christoph-Hart Oh excellent, I noticed the merge but forgot about the API generator :) I shall rebuild.

[d.healey]

Almost have my player plugin working, abusing the expansion system to the fullest!

[coreyu21]

I’m having trouble inheriting the presetbrowser class from the expansion handler(to show the updated user presets from the expansion folder) Would somebody be willing to help me in the right direction. Thank you lots!

[d.healey]

This is in the scriptnode branch, no need to tinker with the C++

[arminh]

Im waiting for tutorial tutorial :D

[Dalart]

Where do we find these settings in Scriptnode ?

[d.healey]

@Dalart Yes. You need to compile with these options HI_ENABLE_EXPANSION_EDITING & HISE_ENABLE_EXPANSIONS. This is an unofficial feature though currently so you'll need to create your own method for users to install expansions. Once Christoph is back from his music writing vacation I hope we might see some of the expansion handling stuff from PercX make its way into HISE.

[Dalart]

@d-healey Thanks again David, more stuff to tinker with. I appreciate the responses and help you give !

[Dalart]

@d-healey said in Expansion User Presets:

HI_ENABLE_EXPANSION_EDITING

I was able to find HISE_ENABLE_EXPANSIONS in the Projucer project file, I was unable to locate the HI_ENABLE_EXPANSION_EDITING setting though. Is there another location I need to look in ?

[d.healey]

@Dalart You have to add it as a Preprocessor definition.

[arminh]

@d-healey how i can get list of expansions? I tried something like this

const var Viewport1 = Content.getComponent("Viewport1");

var expList = Engine.getExpansionList();

Viewport1.set("items", expList.join("\n"));

It's not work for me, instead exp list im getting object code ;P

[d.healey]

@arminh You need to loop through the result. I'll make a video about the expansion system for next month.

[arminh]

@d-healey im waiting for this tutorial! I made simply for loop and yes i had arr with 2 values - 0 and 1, but i don't know what do next. I better wait for your guide :D