Expansion system installer

[arminh]

@d-healey i don't need installer i need working exp system :D

[d.healey]

@arminh Me too :D

[Christoph Hart]

Yes I am currently rebuilding my studio, so I am more into woodworking at the moment than debugging...

[arminh]

@Christoph-Hart but i hope that you made small updates :D

[d.healey]

@Christoph-Hart said in Expansion system installer:

Yes I am currently rebuilding my studio, so I am more into woodworking at the moment than debugging...

You should post some photos once finished so we can see your mad scientist laboratory where HISE is brewed.

[gorangrooves]

@Christoph-Hart said in Expansion system installer:

Yes I am currently rebuilding my studio, so I am more into woodworking at the moment than debugging...

The studio-building/ woodworking department is one area I could offer helpful suggestions, should you need any :)

[Christoph Hart]

Yeah, I am pretty much done with the wood stuff. I'm glad I kept all my fingers though...

I'll post pics when ready...

[Lindon]

@d-healey said in Expansion system installer:

@Christoph-Hart For my current project I want to make use of expansions. I plan to include a built in downloader/installer in the plugin and before I go rolling my own system I wanted to know if you will be implementing a system in HISE to handle installing expansions?

In the custom settings floating tile there is a button to relocate the sample folder, does this change to reflect the expansion that is loaded?

Well expansions are a bit more reliable now so I was wondering how you were going with this?

I can build all sorts of expansion installers (using whitebox) but I think the "problem" is the ch1 files - which really need to go in the folder where the original samples were placed by the user... so HISE knows the name of this folder

something like:

var mySamplesFolder = FileSystem.getFolder(Samples);

Its also in the LinkWindows file in the config folder - but I cant work out a 3rd-party solution (on the Mac) to :

1. read the LinkWindow file for the location of the "Samples Folder"
2. write all the expansion ch1 files there..

I have a few other files that need to go in the config folder (AppData/Roaming/CompanyName/productName on windows, and similar on Mac) but these are always the same - so installing these (JSON) files is pretty trivial...

So before I go much further with this - anyone have a solution for installing Expansion samples in the same spot as the original samples?

unless some kind soul can confirm this works and how to make it work:

ExpansionHandler.installExpansionFromPackage(var packageFile)

[d.healey]

@Lindon said in Expansion system installer:

I can build all sorts of expansion installers (using whitebox) but I think the "problem" is the ch1 files - which really need to go in the folder where the original samples were placed by the user... so HISE knows the name of this folder

I disagree. I like to spread my samples over multiple drives, expansions offer a perfect way to do this. But, it would be handy to get the installation location on a per expansion basis.

So before I go much further with this - anyone have a solution for installing Expansion samples in the same spot as the original samples?

Could you ask the user to select the location where they already installed their samples? and maybe do a check of the files that in the selected location to confirm that it is right.

[Lindon]

@d-healey said in Expansion system installer:

@Lindon said in Expansion system installer:

I can build all sorts of expansion installers (using whitebox) but I think the "problem" is the ch1 files - which really need to go in the folder where the original samples were placed by the user... so HISE knows the name of this folder

I disagree. I like to spread my samples over multiple drives, expansions offer a perfect way to do this. But, it would be handy to get the installation location on a per expansion basis.

Sure fine, that too. But at the moment I cant see a way to get the ch1 files installed anywhere...

So before I go much further with this - anyone have a solution for installing Expansion samples in the same spot as the original samples?

Could you ask the user to select the location where they already installed their samples? and maybe do a check of the files that in the selected location to confirm that it is right.

YEs I could but I'm not smart enough at whitebox packages to know how to make it do all this...