Was mentioned in a few posts some of the things I've added people might be interested in, and since I no longer need to keep the HISE source code private and can just license the instruments, I've opened up the changes I've been working on.

It was built on the last stable commit of scriptnode at the time of making this so if you need anything after that you'll need to add it back in.

You can get it here.

Some features will likely not be for everyone, but here they are:

• Equal power loops: all loops are now equal power, so if you need linear this isn't for you.. Although I can't see why you'd want linear!
• Integrated Downloader + Installer: Download button added to the CustomSettings page (enabled via "DownloadSamples" in the json). This will download a set of files specified in the new command: Engine.setDownloadLinks(var) - this takes a var array of strings and will download them to the specified folder. If any of the files are .zip or .rar (although rar is untested) files, they will be extracted after all files are downloaded, and the source zip file will be deleted after use to save on space. Note: this also updates the sample location directory and notifies the user to restart the app/plugin.
• You can use this to create a bare-bone standalone installer instead if you want too, just create the URLs, create the button in the floating tile and disable the other buttons!

• Freeform Resize: resize via corner component. Scales to 0.5* original height and 2.0* original height - aspect ratio is locked. Note: scaleFactor resize box has been removed from CustomSettings for this reason.
  

• Tricolour and radial gradients: expands the g.setGradientFill() method to allow for more than 2 colours. Simply add three extra units and it will translate to a tricolour or radial gradient: g.setGradientFill([Colour1, x1, y1, Colour2, x2, y2, Colour3, proportionAlongGradient, isRadial]) (proportion is float 0-1, isRadial is bool). A fun thing you can do as a result of this:
  

• Combo Box Look and feel update (now transparent background with a new text)

• Probably other things I've forgotten about.

Enjoy!

Merry Christmas all!

@ustk Seconded, would be hugely helpful right now ^^

@d-healey you can do an a cheap and dirty update approach. Juce has an easy way to read a URL result as a text string and compare it with an input string, so you can just stick a .txt file on your site (hidden of course) and literally just have the text as the version number and match it against the current version. Whenever you load the plugin it can check that result against the internal version number and display it if needed. Just means you need to remember to update the text file.

Similarly you can do this for file activation for online list of CD keys, and it helps you to be able to disable any cd keys that are chargebacked/refunded. For this you probably would want credentials though, as having a publicly available list of keys is not really ideal :p

I might implement this in to my public branch once I'm finished with this chunk of work on release triggers

@d-healey I regularly use a piano standalone app when I'm just playing for pleasure. I know a lot of others that do this too, for anything recording related naturally a daw is miles better, but sometimes you just need a quick test rig rather than loading up a daw and possibly a template

@d-healey I noticed some people (such as yourself) had already added the combo box into their UI, often hidden within it by hiding the edges, this would break those for anyone that uses it (it would actually just straight up vanish).

I'll finish up a feature I think is pretty essential first (version checking from an external file) and then just make it public and do a quick tutorial on the changes somewhere, then if people want to merge changes and whatever I'll leave that to them?

@pnyboer I've been considering just opening up my branch since I've been moving everything back in to HISE for instrument building and I can just license the instruments themselves instead. I haven't looked too much into the licensing yet (but I was planning on using a commercial one) I've just been getting the code down, I'll take a look over the license and figure out if it'd cause any issues and then if people are interested I'll open it up. I've gutted a feature some people might want and added other things people might not want, so I'm not sure how much it'll help.

@dustbro https://forum.hise.audio/post/21655

Incase you still need to do this, you can do this with the StandalonePopupComponents.cpp file, just create your own custom look and feel class(s) in HI_LookAndFeels.h (I don't recommend editing the current popuplookandfeelmethod), add the lookandfeel object to the StandalonePopupComponents header file and reroute the existing look and feel pointers (applicable lines 147->182).

For the combo boxes, you need to specify both the PopupMenu:: settings and the ComboxBox:: settings, as the colours/fonts etc are handled separately for both in JUCE.

@Natanr @dustbro sorry, been busy on some disk streaming stuff for my own sampler so missed this - you don't have to do anything, you just compile and it's resizable.

@d-healey saw it in a couple places while I was using hise, just did a quick search for it so might be another version

@Lunacy-Audio https://github.com/christophhart/HISE/blob/e70e4e55dfaa0dddd50037d616e5441091120bf6/hi_streaming/hi_streaming/StreamingSampler.h#L130

Probably this.

@Christoph-Hart https://github.com/christophhart/HISE/blob/2cf72ddab4374aa10fba46da539e9abb945d9470/hi_streaming/hi_streaming/StreamingSamplerSound.cpp#L885

https://github.com/christophhart/HISE/blob/2cf72ddab4374aa10fba46da539e9abb945d9470/hi_streaming/hi_streaming/StreamingSamplerSound.cpp#L881

Also looks like it's on the monoloth audio format directly, but I haven't been using monolith myself, but from the differences in our implementations that looks like where the loading issues would be

@gorangrooves I understand, but it's sort of a bad solution to an underlying problem - that being that hise instruments take a long time to load initially.

The cause of that is not the samples loading directly, but instead the memorymapping that happens when each sampleSound is created - my solution above (to move the memorymapping and creation of the readers to another thread) resolves that, which means the UI loads virtually instantly, allowing the UI to then properly relay the information of the samples loading.

@gorangrooves Just FYI, you wouldn't want it tied to the interface loading - that's a very backwards way of programming, the interface should just reflect the data, not be part of it.

And an example of why it'd be a really bad idea; If a project starts with plugins already saved, they wouldn't load until you opened up the plugin, a plugin UI is actually completely disabled deleted when the plugin is hidden in a DAW, or even VE pro when you select another instrument (you can test this by resizing some plugins and then swapping between different plugins in VE pro - those that haven't properly coded their ui to save the resolution in the editor destructor, like SINE [at least in a previous update, don't know if it's still like that], will revert back to the original size).

That said, I've implemented this in my own sampler though by moving the creation of the readers (and mapping the file) to a background thread, rather than in the constructor of the samplersound, which has the benefit of skipping mapping samplersounds that purged on init, saving a lot of virtual memory, definitely something that's possible to port in to HISE.

@d-healey https://github.com/LightandSound/HISE-Stage/blob/d44b6d912390820c0b49e0dbb73e09c1d03ca83c/hi_tools/hi_standalone_components/SampleDisplayComponent.cpp#L392

register FLAC in the audio format manager and you're done :)

@dustbro I don't believe anything was merged with the live branches, at least not that I know of

@Natanr @dustbro sorry, been busy on some disk streaming stuff for my own sampler so missed this - you don't have to do anything, you just compile and it's resizable.

@tomekslesicki https://forum.hise.audio/topic/2620/possibility-of-changing-look-and-feel-of-custom-settings/4 if you don't mind looking at C++, but that post covers it step by step, it's pretty straight forward.

@d-healey you can do an a cheap and dirty update approach. Juce has an easy way to read a URL result as a text string and compare it with an input string, so you can just stick a .txt file on your site (hidden of course) and literally just have the text as the version number and match it against the current version. Whenever you load the plugin it can check that result against the internal version number and display it if needed. Just means you need to remember to update the text file.

Similarly you can do this for file activation for online list of CD keys, and it helps you to be able to disable any cd keys that are chargebacked/refunded. For this you probably would want credentials though, as having a publicly available list of keys is not really ideal :p

I might implement this in to my public branch once I'm finished with this chunk of work on release triggers