YES!!!
Thank you. I cannot wait.

@Chazrox Thanks.

Any chance we could change the angle of the gradient on the body & skirt layers?
Eg. For the inner circle here, I'd like the gradient to run from dark at 10 o'clock to light at 4 o'clock.
Right now I can only do top to bottom. Thanks.

6b6718e6-b0c9-4a03-8a6e-97da35b0f170-CleanShot 2026-07-01 at 16.25.54.png

@dannytaurus

I tried to load a 'duo-tone' svg with Base64SVG and this is the result?

Screenshot 2026-07-01 at 2.40.49 AM.png

SVG file:

Screenshot 2026-07-01 at 2.42.10 AM.png

Am I doing something wrong or not understanding something?

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 Give it a try and let us know.

@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

StarKnobNoiseMaskLayerFixed.gif

Heres the fix:

MyKnobLaf.registerFunction("drawRotarySlider", function(g, obj) { var a = obj.area; var range = obj.max - obj.min; var stableSize = a[2] * (1.0 - 2.0 * 0.15); var ox = a[0] + (a[2] - stableSize) / 2; var oy = a[1] + (a[2] - stableSize) / 2; var cx = ox + stableSize / 2; var cy = oy + stableSize / 2; var sw = stableSize / 200.0; var startOffset = 2.5; var totalSweep = 2.0 * startOffset; var endOffset = -startOffset + totalSweep * (obj.value - obj.min) / range; var cStarBody3Top = 0xffFF0000; var cStarBody3Bot = 0xff00FBFF; var cStarBody3Outline = 0xfa000000; var starBody3Size = stableSize * 0.76; var starBody3X = cx - starBody3Size * 0.5; var starBody3Y = cy - starBody3Size * 0.5; var starBody3Static = Content.createPath(); starBody3Static.addStar([0.5, 0.5], 3, 0.13, 0.5, 0); starBody3Static.roundCorners(1); var starBody3StaticBounds = starBody3Static.getBounds(starBody3Size).translated(starBody3X, starBody3Y); var starBody3Star = Content.createPath(); starBody3Star.addStar([0.5, 0.5], 6, 0.05, 0.6, endOffset); starBody3Star.roundCorners(1); var starBody3RotBounds = starBody3Star.getBounds(starBody3Size).translated(starBody3X, starBody3Y); // PASS 1: gradient fill g.beginLayer(false); g.setGradientFill([cStarBody3Top, cx, starBody3Y, cStarBody3Bot, cx, starBody3Y + starBody3Size, false]); g.fillPath(starBody3Star, starBody3RotBounds); g.endLayer(); // PASS 2: noise — use full obj.area so noise fills behind mask cleanly g.beginLayer(false); g.applyMask(starBody3Star, starBody3RotBounds, false); g.rotate(endOffset, [cx, cy]); g.addNoise({"alpha": 0.3, "monochromatic": true, "area": [a[0], a[1], a[2] * 2, a[3] * 2]}); g.rotate(-endOffset, [cx, cy]); g.endLayer(); // PASS 3: outline g.beginLayer(false); g.setColour(cStarBody3Outline); g.drawPath(starBody3Star, starBody3RotBounds, 3.06 * sw); g.endLayer(); });

@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 👍

Update: I bowed out gracefully.....for now lol

Not gonna lie I‘ve made this exact mistake about three times in my life already without help from a robot…

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