UPDATE: Plugin Storefronts now use Webview for smoother experience

Plugin Storefonts have been updated to use the same Webview model as the validation system. Now you can display your products directly in your plugin.

To implement is easy:

Firstly, you will need to make sure you have atleast 1 product created and live in your account.

Secondly, you will need to setup your Website/Storefront Credentials & Support Credentials.

Once that is complete, find the Plugin Storefront Package is in the TOOLS section of your Developer Account and open.
9a4ebe69-d9d3-4eec-9b32-ed1bab9c89ae-{C5EAF645-10E0-487B-8597-3318AED9F1DE}.png

Scroll Down and you will see the HISE Storefront Package Generator. Enter your GUI Height & Width and download the package. Unzip and place the SoundSyncStorfront folder in your HISE projects "Scripts" folder.
06a1c51d-4eb8-4738-93d3-b76533983580-{1C4EBE5B-FC47-4C2C-956E-D406727522D7}.png

Open your project and use 1 simple include line to generate the entire package in your project.

include("SoundSyncStorefront/Runtime/SoundSyncStorefrontRuntime.js");

Then your branded Plugin Storefront window will be present. It will pull your logo, brand colors, store name, products, support etc all from your Website/Storefront/Support pages in the developer account.

Public Catalog View:
3b917721-ae7a-4462-a2c6-d256e4f52aea-{40435235-D433-4C58-9122-03D3C9C356ED}.png

Customer Product View:
62118a87-c730-47c1-9ddc-7359f4dd31f3-{34AA5E77-0C2D-4A85-A12D-4575F4167AF5}.png

It makes for a pretty dope Storefront inside your plugin!

All the best,

Aaron

@duma Change the macOS version in Projucer

@Lindon
I second that! :-)

@David-Healey Please check your dms for me

@David-Healey
Looks like they are selling Plug-Ins and knives. :-)

@pratitghosh move all the xml files into the new project and then compile the DLL there

@observantsound You can use both references at the same time. Just use the one that works for the bypass, and the other for your sampler job

What I said might work, but do as @David-Healey said it's better implementation even if the reference are the same behind the scene 👍

I think you can probably do it using the MidiAutomationHandler: https://docs.hise.dev/scripting/scripting-api/midiautomationhandler/index.html

@David-Healey ok thank you

@JC Hey i actually got the moonbase module to work in juce 6..
took David's advice and messed around with Claude and got it to work.

little tricky for me but its working. I Havent shipped anything yet though--Hopefully soon.

@jeffd

So i got a notarized .pkg working of the .hr files. still need to test more but i got them into the plugin's own per-user app-data folder. Then when the plug-in opens and installs the samples it can also auto-delete the .hr files right after extracting. And no gatekeeper quarantine from macos. Ill have to do the same on pc and create .exe for the .hr files to match. but perhaps this will be best. less confusing for people i imagine?

@Oli-Ullmann Yes a vm is the way to go if you don't have a mac

@David-Healey payload is good.

Oh ok, I didn't know. I do it right now.

@David-Healey Thank you. It compiled and worked just fine.

@dannytaurus Oh nice one! 👍

@ustk very sexy!

@ulrik Thanks for clarifying that detail, I was able to export my practice projects.

@David-Healey No, because this is about persisting the file to the user's disk.

Although as I said earlier, I think the final best answer is to display the license directly in the plugin somewhere.

Then nobody could ever accuse the developer of not making the license easily available.

Website goes down - no problem
User moves the plugin to another machine - no problem
User wipes/moves/modifies their AppData folder - no problem

If the license is in the plugin itself, it can't be accidentally moved, deleted or overwritten, and it can't become unavailable because of server outage.

Probably going this route now...