Expansion Tutorial



  • @d-healey said in Expansion Tutorial:

    @Lindon Allow the user to select the location they want to install the samples and pass this to ExpansionHandler.installFromPackage().

    For the original install HISE has the hr1 file set and a process of unpacking them

    That's what ExpansionHandler.installFromPackage() does, you just pass it the .hr1 file (the user can select this with a file browser) and the destination to extract the samples to (user can select this with a directory browser) 🙂

    OK great - so I check the status of expansions (how would I know if its already been installed?) and if samples not installed then pop a user dialog asking for the location of the hr1 file, when I have that pop another asking for where they want to store the samples..(suggesting SAMPLES as an option) and take their answers as params for ExpansionHandler.installFromPackage()

    yes?

    So what is ExpansionHandler.getUninitialisedExpansions() telling me?



  • @Lindon said in Expansion Tutorial:

    (how would I know if its already been installed?

    You could probably use the File API to check if the expansion folder exists in the app data folder. You could also check the list of available expansions in your script.

    samples not installed then pop a user dialog asking for the location of the hr1 file, when I have that pop another asking for where they want to store the samples..(suggesting SAMPLES as an option) and take their answers as params for ExpansionHandler.installFromPackage()

    The samples "should" be installed when they install the expansion, if they move the samples to a different location then you could handle that with the Expansion.setSampleFolder() function.

    So what is ExpansionHandler.getUninitialisedExpansions() telling me?

    According to the docs - Returns a list of all expansions that aren't loaded properly yet.

    So no idea, have a look in the source code and report back 🙂



  • @Lindon said in Expansion Tutorial:

    ExpansionHandler.getUninitialisedExpansions()

    This is only interesting if you use the Encrypted .hxp expansion type as it will wait with the initialisation of encrypted Expansions until you've passed the user credentials to ExpansionHandler.setCredentials() (because only then it can decrypt and verify the legitness of the user).

    The expansion installation procedure is supposed to be as streamlined as possible both for implementation and the end user (granted that you use the glorious .hr1 format and not some weird hacky solution including zipping the ch1 or embedding them in the installer).

    var hxiFile = getTheHxiFile(); // ask the user after he clicks on a button or whatever
    var targetFolder = FileSystem.getFolder(FileSystem.Samples); // Get the folder where all samples are or ask the user again
    
    // That's it
    expHandler.installFromPackage(hxiFile, targetFolder);
    

    So the most simple-to-implement procedure for a user that buys an expansion is:

    1. User buys the expansion. Gets a link with the download in an email.
    2. Downloads the .hr1 file directly (no installer required)
    3. Clicks somewhere on the UI that opens a file dialog
    4. Points to the downloaded file
    5. The plugin will extract the samples and copy the expansion to the app data, then does all the encoding (if required) and reinitialises the expansions

    There's even a better option available if you use the full force of the Server API and a user model:

    1. User buys expansion. Gets an email that says "Click refresh in the plugin" (or whatever)
    2. User clicks refresh in the plugin (or whatever)
    3. Plugin calls home, queries the list of expansions that the user has bought.
    4. Notices that there is a new expansion that is not installed on the computer
    5. Starts downloading the .hr1 file automatically
    6. When the download is finished, it will extract it automatically (the .hr1 file is the downloaded file and the sample target the default sample folder).


  • @Christoph-Hart damn Android. he did not copy the correct question lol. actually my question was. Since my expansion system is based on importing sample maps from a combobox, I should redo the sample map loading system? and necessarily redo my 250 preset? ^^



  • Well if you move your samplemaps from the factory content to an expansion, then yes, the samplemap ID will change. But it's nothing that isn't solvable with some concentration and a search+replace text editor.

    So if you have the samplemap stored in the preset from the factory content there's something in your .preset file that looks like this:

    "MySampleMap"
    

    So just replace it with

    "{EXP::MyExpansion/MySampleMap}"
    

    in all preset files.



  • @Christoph-Hart alright so i will see this and come back in about 14 years lol



  • Cool let me know how it went... 🙂



  • @Christoph-Hart I come back from the future. we are at covid 22+, Trump has become president again and Angela is in a relationship with Emmanuel Macron. it's horrible. on the other hand even 14 years later, in fact, my presets of my expansion have already "{EXP :: MyExpansion / MySampleMap}". so i exported my vst, put the hxi in app data ........ but the vst opens empty. Oh, I forgot, Microsoft bought hise for $ 5 million. but say nothing ^^



  • @Christoph-Hart said in Expansion Tutorial:

    @Lindon said in Expansion Tutorial:

    ExpansionHandler.getUninitialisedExpansions()

    This is only interesting if you use the Encrypted .hxp expansion type as it will wait with the initialisation of encrypted Expansions until you've passed the user credentials to ExpansionHandler.setCredentials() (because only then it can decrypt and verify the legitness of the user).

    The expansion installation procedure is supposed to be as streamlined as possible both for implementation and the end user (granted that you use the glorious .hr1 format and not some weird hacky solution including zipping the ch1 or embedding them in the installer).

    var hxiFile = getTheHxiFile(); // ask the user after he clicks on a button or whatever
    var targetFolder = FileSystem.getFolder(FileSystem.Samples); // Get the folder where all samples are or ask the user again
    
    // That's it
    expHandler.installFromPackage(hxiFile, targetFolder);
    

    So the most simple-to-implement procedure for a user that buys an expansion is:

    1. User buys the expansion. Gets a link with the download in an email.
    2. Downloads the .hr1 file directly (no installer required)
    3. Clicks somewhere on the UI that opens a file dialog
    4. Points to the downloaded file
    5. The plugin will extract the samples and copy the expansion to the app data, then does all the encoding (if required) and reinitialises the expansions

    There's even a better option available if you use the full force of the Server API and a user model:

    1. User buys expansion. Gets an email that says "Click refresh in the plugin" (or whatever)
    2. User clicks refresh in the plugin (or whatever)
    3. Plugin calls home, queries the list of expansions that the user has bought.
    4. Notices that there is a new expansion that is not installed on the computer
    5. Starts downloading the .hr1 file automatically
    6. When the download is finished, it will extract it automatically (the .hr1 file is the downloaded file and the sample target the default sample folder).

    --well that's about as sweet as its ever going to get ...nice job (again).



  • @dustbro said in Expansion Tutorial:

    That will allow you to load next and previous in the expansion. If set to 0, the presets will get stuck cycling in the UserPreset folder and not find their way out.

    @Christoph-Hart Is there any way to take another look at the preset browser in combination with expansions?
    I'm experimenting with a project that loads expansions and the preset system is a little buggy. I plan on only using expansions, so the main instrument doesn't contain any presets. I've got a project loaded up (with expansions) . loadNextUserPreset() and loadPreviousUserPreset() don't seem to work at initialization. I'm assuming the instrument is looking in the project User Presets folder and isn't seeing the expansion preset folders. If I load a preset from one of the expansions, Next/Previous works, with one exception:
    loadNextUserPreset() and loadPreviousUserPreset() will instantly crash HISE unless stayInDirectory is set to 1.

    Here's a minimized example:
    tinyurl.com/2fy7ycys

    Also, sometimes the bank column appears empty.

    bank missing.png



  • How we can get presets from expansion? Only by FileSystem?



  • @arminh

    @d-healey said in Expansion Tutorial:

    @dustbro Enable the expansion column:
    ef0ad6cf-3139-4a67-88ee-b2731a63db90-image.png



  • @dustbro yes I know how to use it in floating tile preset browser but I would like to create custom preset browser.


Log in to reply
 

10
Online

1.2k
Users

3.8k
Topics

33.6k
Posts