I'm currently building an app which I hope will allow batch exporting of HISE projects, auto notarization on Mac, and auto-generating installers. So far I have the basics working on GNUx. I need to finish the interface and add the batch handling, but that shouldn't be too difficult, then I'll tackle the other platforms.

This app should make it much easier for everyone (and especially beginners) to export their projects from HISE and build installers.

This is what it looks like so far (it's an ugly work in progress).

It's starting to look a little nicer now.

pkgbuild works! I can programmatically generate unique packages on MacOS now! woohoo!

Status update:

GNU/Linux: Fully working (standalone, vst2, installer). x64 only
Windows: Fully working (standalone, vst2, vst3, installer). x86/x64
MacOS: Fully working (standalone, vst2, vst3, au, codesigning). Needs a bit of tuning but almost there (installer). x64 only.

When I say fully working, that's in my own tests, I expect many a bug report when I release it into the wild.

It's quite possible that AAX plugins will compile just fine on Windows and MacOS too, I've implemented it in the app but haven't tested it.

If all goes well I should finish up the tuning of the MacOS build tomorrow and it will be ready for my patrons to test this weekend!

@Christoph-Hart Could you merge my juce_template pull request (if all is well) as the mods there are needed for my app. The mods are also useful for regular exporting from HISE, bigobj is enabled by default and the VST3 SDK is set correctly to the one that is in the JUCE folder.

And a happy new year!

The source code is now online - https://github.com/davidhealey/hise-exporter

I'm just ironing out a few bugs then I'll build the beta executables for each platform and make them available on Patreon.

I've been thinking of making a HISE tutorial series, as I did for Kontakt, and wondering if there is any interest in it. I already have the Patreon page and YouTube tutorials, and a dedicated course would cover some of the same ground but in a more structured way. What do you guys think, worth doing?

I did a little Skype interview the other day where I was talking up HISE, as always.

@hisefilo We all do this - https://rubberduckdebugging.com/

Here is another method. It uses the same principle as your code but can be expanded to include many more panels and buttons and would only require you to change 1 value.

HiseSnippet 1162.3ocsWEtaaaCDlxwpnVqtnEXO.D8WxHcI1YscCHMnp1IYwXMIFyoAEnqHiVhxhHxjFRzowsH.8QZOB4QZuAYGEkrnSbBh+Q7OL7c7938w6Hu6buDgOMMUjfrpczzwTj0Sr6OkKi5DQXbT2sQVO0deRpjlf0pZOcLIMkFfrrV4OTJrpUEk84+dWaRLg6SKUgPGKX9zOvFwjkZG68mr33cIAziXiLr9Udc8E7NhXwDfOqX2DMl3eJYH8.hxrJ1HqGsS.SJR5KIRZJxpZaQvz9Qhux01eLKkMHlpDZg5CajV8th3.EiUZQchXwA8JN2oHXW5UFEVQGE9Y68YArY5KiFOKaAbIBy3gUk6hdsLoWy6O8rLnWUM8dtce+D1XY4JJt8S1c4PhJj.o.SZosEU4IUs6H.K3x0FQNktaBHLCg6aZ17k3W2rYiMq6T2IgNDyx9EjRRk3yHI3C939mz68GryG5i2Buwl30W+nHJlOYz.31gHDOlvowoqOXhTBXLQpWAP84uroo9bSKVntSnHA6x.4lahY32Z3RPd0UaT2460cvvG8N9Y1W.aKNTCoxNhQiEbPv8E8TV7hUcYq1pg5LoPk6u6BV6LStUbqkprlKSDwcHwwCfKnt9QD9PZl+ZroyEpyAiGy3Tb3DtujI3XCSb80veIDAhmPafyOQ5uiE9j3rHugTv4.cy4vZLd.87CCK1lFp7PWkNUJPaDVFQjXYBa3PZBM.DoX+b1Z5r0WeOV.ECqTjgHbv5IIbXuByzOKYpr+5YGMn0ho7gxnhDjxv7izbIp0RgGB4gN2PRbJsH5dyH7wpHiayBCtvjzrPraVjCu0V3V2tCCNedWJSffsJXodPpsJ6.AFt.ZjgtfH5DkBa6EFeKhsX.AVJzIVX2zj24hYWCD7CDR5gb2FNe2olyENWekvvEsT9QHllrnUUEQStCXt5WnE22xsCpkLewJ6auXkYsTe8qFCCE7tbl7vwT9sUBCk+TCJlUImTfoxrRYOMuTlNxhXPEqZ1ZgVnLFCJdTQ6DzR.eiE.+ic2lHIphp4TBn4XZhjoh.VaSOC5VoKwVydaZ5oRwXHPMq7.z.5dv5ym0R6xddSK6usm2WYAxnRE+iWDkMLxn03a8PFNyQ6r5EU6U2Yy70isy9soq9QaCW482WyU68iq6JuXOljNpnaaYLpT6FlpkzykkFe0UWQUZOq3Rh0JKCw2vj3dFD+xOcMh+u2f3WF3MPjDPS5y9lwvCO6FGmqZtviiV8sP7p2iaUFoW17oWzM6TCyKHBlDSjyODgZxo7Ef2py0sV0QlmxjSMmr5AYxh6KcetcOlzOZw7sxB3q5c9CLeymSqt8NggTeYIYqZu6md3GJC8WhIRFe39DnK.bgv9fIi5C2w7o.S3pFPfNqJpBVZ4lJYUjoOkGjI.OgtJewVJYq7EaUrHZDwOQbRded0jfONSCvId1.w0fIyAY7r5jJdOBFO8DeeUf3W.luXDarzH90kFwqVZDudoQ7lkFwuszH986.g5+B79IRwH8yBPQucxZvXYsCm.2pxtAh9e.HjLlMC

What I'd like is to have access via the scripting API to each of the custom settings functions.

This way I could add whatever GUI I like to control things like relocate samples folder, and changing the interface size, etc.

I can see these functions in the source code and how they interact with the custom settings panel controls but I'm not skilled enough to link to these functions from the scripting API code. So if I was going to implement it I would probably just end up duplicating the code inside the scripting API and that wouldn't be a good way to do it.

So @Christoph-Hart could you implement this or give me some pointers about how to do it?

I'd also like to see the relocate samples folder function able to handle expansions, so clicking the button would relocate the samples folder for the current expansion.

@Maichol Compiling scriptnode is exactly the same as what you've already done, you just need to download the scriptnode code instead.

Go here - https://github.com/christophhart/HISE/tree/scriptnode
Click the green Code button.
Select Download Zip.

Or a better choice - use git.

@Maichol Did you compile 2.1 or did you use a pre-built version?

@Christoph-Hart Excellent, thank you

Your snippet works fine for me. You sure your MIDI input and soundcard configuration are correct?

Go to the export menu, select Export as HISE snippet. Then paste it here inside code tags - three back ticks, or this just click this button

@Christoph-Hart I don't but I don't mind learning, can you point me to the documentation?

@Christoph-Hart All of the functions I'm adding are to make the custom settings panel options available via scripting. So maybe a Settings class would be the answer?

Bump bump

Can you post a snippet of your project?

@Tania-Ghosh

users(many of them are stupid also) don't find Appdata.... because it is hidden by default. So I want to put all things inside

They can access it from the preset browser in HISE. Go to the More menu and select the option to open presets folder.

And VST,VST3,AAX etc will be place on user preferable places.... Is it possible?

Check the standards for these formats. All (except VST2) have specific locations that they should be placed. VST3 for example - https://helpcenter.steinberg.de/hc/en-us/articles/115000177084-VST-plug-in-locations-on-Windows