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

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

[David Healey]

@Lindon Yes

[Lindon]

@David-Healey except damn it the loaded expansion doesn't know anything about the sample maps!!!!!!!

Where should I [put these in this work around....???

[David Healey]

@Lindon The sample maps are part of the hxi, you don't mess with them from the player project, you do that in the expansion's own project.

[Lindon]

@David-Healey yes thanks I know that, however when I put the expansion in the Players Expansion folder as a work around - it allows the Player to load the expansion,(great) and play the sample set it was loaded with (great again).

But look above, at the image I just posted, when I load the expansion in HISE there is no sample map set listed in the expansion Sampler.......it says Encrypted Expansion in the drop down, and when I open it it says "No samplemaps found"

So Im right back at the place I was in this morning.....

[David Healey]

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

But look above, at the image I just posted, when I load the expansion in HISE there is no sample map set listed in the expansion Sampler.......

Is that the expansion project or the player project > loading the expansion?

[Lindon]

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

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

But look above, at the image I just posted, when I load the expansion in HISE there is no sample map set listed in the expansion Sampler.......

Is that the expansion project or the player project > loading the expansion?

its the Player project loading the expansion.....

[David Healey]

@Lindon Then that is the expected result, you can't edit the embedded sample map.

[Lindon]

@David-Healey I dont want to edit it, I want to load another one.....are you saying I can only do that programatically in an Expansion?

[Lindon]

@Lindon Im going to need to embed possibly up to 100 sample maps....

[David Healey]

@Lindon Yes you should treat it just like it would be for the user.

[Lindon]

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

@Lindon Yes you should treat it just like it would be for the user.

Sorry I dont understand what this means....are you saying the HISE sampler "view" isnt available for Expansion stored maps?

[Lindon]

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

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

@Lindon Yes you should treat it just like it would be for the user.

Sorry I dont understand what this means....are you saying the HISE sampler "view" isnt available for Expansion stored maps?

time to go walk the dogs. Ive taken enough of your time today....

[David Healey]

@Lindon When the user loads your expansion they won't be able to change sample maps by opening the sampler and neither can you. The expansion is its own HISE project so any editing needs to happen there.

I actually put this in my expansion loading code because (except for testing) I don't ever load the expansions from within HISE

if (Engine.isHISE())
    return Console.print(company + " : " + name);

return eh.setCurrentExpansion(expansion);