Full Instrument Expansions - how, what where....

[Lindon]

@Lindon this is right yes?

[David Healey]

@Lindon Looks correct. I just noticed I'm compiling HISE with the HISE_ENABLE_EXPANSIONS=1 and HI_ENABLE_EXPANSION_EDITING=1 preprocessor definition2, I don't know if they are required though.

In your expansion projects you should leave the Expansion Type set to Disabled.

[Lindon]

@David-Healey looks like Im not - so let me go try that...(why was it working before tho?)

[David Healey]

@Lindon Dunno, just trying to find any differences between our setups.

[Lindon]

@David-Healey yeah...so doing this:

[Lindon]

@David-Healey -- sadly no different. Still not finding any expansions...

[Lindon]

..built an all new test loader - same problem - so its not the project, its something Im (not) doing...

[Lindon]

@David-Healey how long has this been working for you? Im on a HISE from April last year....

[David Healey]

@Lindon I've been using it for years

[Lindon]

@David-Healey Im all out of ideas.....can I send you the test loader and the expansion?

[Lindon]

@David-Healey oh, well... its working in the compiled plugin...

just not in HISE itself....

[Lindon]

@Lindon sigh..but not in the actual Player....

[Lindon]

grrrr..nope cant get it to load in the compiled plugin either....

[Lindon]

@David-Healey
Grasping at straws..

This is what you are doing?

[David Healey]

@Lindon yes, and sure send the project over

[David Healey]

So this led me to the answer Console.print(FileSystem.getFolder(FileSystem.Expansions).toString(0));

It returns the folder inside the project folder instead of the App Data folder.

So I checked what I was doing in Rhapsody, and in my project folder's Expansions folder, I have a Link file with the path to the Expansions folder in AppData. It basically does the opposite of the "Link Expansions to Project" setting in project preferences.

[Lindon]

@David-Healey said in Full Instrument Expansions - how, what where....:

So this led me to the answer Console.print(FileSystem.getFolder(FileSystem.Expansions).toString(0));

It returns the folder inside the project folder instead of the App Data folder.

So I checked what I was doing in Rhapsody, and in my project folder's Expansions folder, I have a Link file with the path to the Expansions folder in AppData. It basically does the opposite of the "Link Expansions to Project" setting in project preferences.

oh now Im in a nightmare of managing windows accounts and symlinks...

[David Healey]

@Lindon Well I think you could get around this by using the project's expansions folder as if it is the app data folder and enabling the Link Expansions to Project folder when testing the compiled version on your machine - just remember to disable it before sending to other people.

[Lindon]

@David-Healey looks like Im going to have to as even tho Im the Admin powershell and cmd prompt are saying I dont have privilidges

[Lindon]

@David-Healey

OK so that worked OK.... it loads and plays something..... so essentially I could (every time I want to test the compiled player or expansion), just copy the expansion form the Player Project to the Player AppData folder and it would work with the compiled Player???