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

[David Healey]

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

right now the expansions own project cant even find the sample maps in its own project structure...this is getting silly.

Do you mean when you load it through the player project?

[Lindon]

@David-Healey no - just loading the expansion project...it cant find anything, rebuilding a new test expansion project now.... called Test2

..ok thats back to working at least... now:

Building the hx1 file....
Expansion type = Full
Encryption key = Test

OK creating a new folder called Test2 in the AppData folder structure of the Player

Adding a Samples folder - with the LinkWindows file in it only...
Adding an empty UserPresets folder
putting my info.hxi that I just generated in the Test2 folder...

to get to this:

I load the Player project and execute this code:

reg eh = Engine.createExpansionHandler();
reg expansionList = eh.getExpansionList();
function instrumentMouseCallBack(event,panel)
{
	//Console.print(trace(event));
	if(event.doubleClick)
	{
		pos = InstrumentPanels.indexOf(panel);
		tempMouseJSON = getJSONforInstPanel(pos);
		//Content.getComponent("Label1").set("text", "here we load an expansion called:" + tempMouseJSON.ExpName);
		Console.print("loading an instrument........." + tempMouseJSON.ExpName);
		Console.clear();
		for(e in expansionList)
		{
			Console.print("the name of the expansion is:" + e.getProperties().Name);
		}
		
		eh.setCurrentExpansion("Test2");
		//Console.print(trace(eh.getExpansionList()));
	}
};

and nothing happens.......it cannot find the list of expansions in its AppData folder...

[Lindon]

@Lindon

Interface: the app data folder is:C:\Users\Lindon\AppData\Roaming\NomadSounds\KeyEngine
Interface: the number of expansions found is:0

[David Healey]

@Lindon Put this in on init after you declare the expansion handler

for(e in eh.getExpansionList())
    Console.print(e.getProperties().Name);

[Lindon]

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

for(e in eh.getExpansionList())
Console.print(e.getProperties().Name);

done:

reg eh = Engine.createExpansionHandler();
reg expansionList = eh.getExpansionList();
for(e in eh.getExpansionList())
    Console.print("we have found expansion:" + e.getProperties().Name);

and the output is.....

Interface: USER SAMPLES LOCATION:D:\AudioContent\NomadSounds
Interface: library panel repaint getting called

As I say its not finding any expansions in the AppData folder structure...

[David Healey]

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

the app data folder is:C:\Users\Lindon\AppData\Roaming\NomadSounds\KeyEngine

What did you use to print this?

[Lindon]

@David-Healey

Console.print("the app data folder is:" + FileSystem.getFolder(FileSystem.AppData).toString(0));

[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....