@David-Healey I doubt it. Once you start notarising, I reckon you'll never stop.

Two free Mac apps from Mothers Ruin.

First one is Apparency, which allows you to inspect the status of VST3 and AU plugins. You can see the signature and notarisation and the property list strings.

Here's Rhapsody VST3:

The AU has some extra property list strings, and one of them is a dead giveaway that it's a HISE plugin

Next app is Suspicious Package, which allows you to inspect your installer PKGs - what files they install and where, what scripts they run, the installer code sign and notarisation and more.

Here's the Rhapsody 3.0.0. installer PKG:

What's very cool is that you can drag and drop from the All Files tab in Suspicious Package, into Finder. So if you just want to grab any of the assets for a closer look, just drag them into a Finder window.

Oh, and it has a Finder Quick Look action too, so you can see the main details from Finder by hitting spacebar:

@Yannrog Where did you use the Apple Team ID?

I don't think it's needed for regular VST/AU exports, only for iOS exports (which are no longer supported).

How are you code-signing the plugin and the installer? Are you using an app, like Packages or Package Builder? Or are you using the command line?

@paper_lung Gotcha. Not too far behind then. Still worth getting up to date though

@paper_lung 08581208 isn't a commit. Did you build HISE yourself from a recent commit?

I can reproduce your bug in the latest commit anyway, so it's definitely there. But still a good idea for you to be on the latest commit.

When you drop an arbitrary audio file (not a power-of-two wavetable) onto the Wavetable module, it triggers the Resynthesis function, so that might be where the bug lives.

@brucerothwell Unfortunately, that's pretty much all wrong

You need to clone the latest develop branch and build HISE yourself.

Take a look here: https://github.com/christophhart/HISE and scroll down to System Requirements and How To Compile HISE

When you've compiled HISE, don't use the Export Wizard. I think it's still broken. Use the Export > Export As ... menu items.

@paper_lung Also, are you dropping an actual power-of-2 wavetable file, or an arbitrary audio file?

@paper_lung Can you send me one of the stereo files you're working with so I can test and find a fix?

@ustk Are you on Tahoe?

@paper_lung Which commit are you on?

@ustk I haven't done much with drawing code yet, but I'll try it. Thanks.

It achieves exactly the same thing as I'm achieving with multiple panels. Draw a 'hidden' border to mask the edges, then draw the real border on top.

The main reason I used panels in the first place was so I could see the colours in the interface designer properties panel. But since then I've moved all colours to script, so that reason no longer holds, I suppose.

Here's a zoomed-in GIF showing the corners leaking without the dark border:

I can't have that in one of my plugins!

@ustk Mine is actually four components, because I'm fussy and the it was the only way I could find how to do it!

My displays have rounded corners, and even though the parent panel crops the plotter waveform by width and height, it still leaks out of the rounded corners.

So, my setup is:

Parent Panel = 180x50
    Plotter floating tile = 182x48 at -1, -1
    2px background-colour border that covers the corners = 182x52 at -1, -1
    1px brand-colour border visible in the UI = 180x50 at 0,0

If the contents didn't leak out of rounded corners I wouldn't have to hack it like this.

This GIF of me hiding the various parts might explain:

Not sure if the GIF shows it well, but when I hide the hacky dark border, the waveform leaks out of the rounded corner.

@Oriah-Beats Mine is in a panel, where the panel is the actual size I want to see, and the Plotter floating tile is slightly bigger so the L/R edges are cut off by the panel.

Panel = 180x50
Plotter = 182x48

The Plotter's 182 width means the left and right edges are cropped. The 48 height stops the top/bottom of the wave being cut off.

@Yannrog If you have any more specific question let us know.

@Yannrog Docs are here:

https://docs.hise.dev/scripting/scripting-api/server/index.html#callwithget
https://docs.hise.dev/scripting/scripting-api/server/index.html#callwithpost

@ustk I'll try it and see how the XML comes out.

I was getting flip-flop noise in my XML after saving. On some saves, the default params were added, on other saves they were removed.

Something to do with CSS-LAF timing, according to Claude, because I'm setting some values in script that happen to be default values.

@Christoph-Hart If I patch my build of HISE to stop pruning default values when serialising the XML, will it have knock-on effects?

// hi_scripting/scripting/api/ScriptingApiContent.h

834      Array<Identifier> deactivatedProperties;
835      Array<Identifier> priorityProperties;
836
837 -    bool removePropertyIfDefault = true;
837 +    // meatbeats: stop pruning default values to reduce git noise
838 +    bool removePropertyIfDefault = false;
839
840      CustomAutomationPtr currentAutomationData;

I get a small amount of git noise from the pruning of default values when I save. It's nothing horrible, but I'd like to remove it.

I'm personally fine with default values hanging around in the XML. But will it have side-effects?

@chimaera_09 Make the button show/hide a panel. Use the panel to house all your extra controls.

const pnlSettings = Content.getComponent("pnlSettings");
const btnSettings = Content.getComponent("btnSettings");
btnSettings.setControlCallback(btnSettingsControl);

inline function btnSettingsControl(component, value) {
    pnlSettings.showControl(value); // button shows/hides the panel
}

You can add a button in the panel to close it too:

const btnSettingsClose = Content.getComponent("btnSettingsClose");
btnSettingsClose.setControlCallback(btnSettingsCloseControl);

inline function btnSettingsCloseControl(component, value) {
    if (value) {
        pnlSettings.showControl(false);
        btnSettings.setValue(0); // sets the 'off' state of the button
    }
}

@Oriah-Beats Yep, like David said.