@BWSounds In that case try a different xcode version, one up or down from your current one - not sure which I'm using, it's been a while.

Also only use the JUCE6 branch, JUCE8 is currently broken.

@GUJIAN No, but you seems to be trying to use Rhapsodist in the second image and the template in the first image.

@ustk I'm indeed still on the latest stable release...
I read it as 4.10 instead of 4.1 so I was convinced I was on the latest version.
I'll compile from the latest develop branch instead and try again.

So what state is the mod matrix actually in?
Do some things work but others don't?
I'd just like to know what to look out for, if the documentation isn't super up to date.

What are PRs?

@lalalandsynth

Ah that makes sense,
yes indeed that was the only thing.

In that case, great work all round.
I'll keep you in mind for some upcoming projects.

@duma Try a different xcode version

@ustk Until July 7th anyway. Then I'll probably only use it for big tasks! 💰

@Christoph-Hart Looks like you deliberately chose to not expose the preset list to host. Can you remember why?

"Here be dragons" maybe? 😂

# hi_frontend/frontend/FrontEndProcessor.h int getNumPrograms() override { return 1;// presets.getNumChildren() + 1; } const String getProgramName(int /*index*/) override { return "Default"; } int getCurrentProgram() override { return 0; //return currentlyLoadedProgram; }

@Oriah-Beats Enable one shot mode in the sampler's playback settings.

e0578f4f-f5c5-4dc6-ac61-199b6e8e48b8-image.png

@Jeetender You can use setLatencySamples() to report the latency amount to the host, so it can compensate.

https://docs.hise.dev/scripting/scripting-api/engine/index.html#setlatencysamples

However, I think the tool to measure the latency of your plugin is currently broken.

Tools > Check latency of signal chain

https://forum.hise.audio/topic/14245/check-latency-broken-on-latest-develop-build?_=1783032811243

@David-Healey Dang. Shame they don't have a time-limited demo or something.

@HISEnberg Alright man, Thanks!!

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

@Lindon
I second that! :-)

@David-Healey Please check your dms for me

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