@Adam_G Thanks for the heads up!

My developer just confirmed this still crashes plugins on macOS (vst3)

Is this still an issue?

I got crashes on macOS, but not on preset loading, it just crashes on start.

@gorangrooves

Appreciate the tip. Will try and dig deep once more.

We need a vst3 wrapper for mac that can run windows plugins!

@d-healey

But i remember with an earlier plugin i did, on another platform i exported a VST3 plugin, that a friend of mine got running on his Mac, i dont know if he used a bridge or something, but it worked.

Is there something specific in a vst3 export on windows that would not make it work on mac?

@d-healey

Thanks!
Oh boy, a developer account again.
The thing about macOS is that everytime theres an update, you need to spend time fixing and updating stuff. I remember we did this with our apps for iOS. Until we just didnt want to do it anymore.

I think ill wait for the day an LLM or AI can do this for me

@Christoph-Hart

I forgot about that. Yay! Cant wait.. Fun will now commence.

@d-healey

Virtual Machine, here we go..
I was hoping i didnt need to compile on a MAC, so i need to install HISE, JUCE and everything on the VM?

I remember my earlier days developing apps for Android and iOS, XCode nearly killed me. I hate it like nothing else.

Hi All,

I have successfully released my plugin for Windows.
But i am still not sure where to go from here when i want to release it for macOS as well.

Do i need to compile builds on an actual mac?

• isnt vst3 supported on macOS?

AAX seems like i would need additional licensing etc, which im not interested in if its an expensive venture.

Who cares about installers, I'm gonna zip this bad boy up, and let the customers figure out the rest.

@Christoph-Hart said in Inno Setup is Flagged as Trojan?:

Or don't give in to the code sign mafia and raw dog your installers to your customers like a real man!

@d-healey Thanks!

@d-healey

I cant do something like this?

// KEYBOARD COLORING
namespace Keyboard {

    const var KeyboardPreload = Content.getComponent("KeyboardPreload");

    const samplerIds = Synth.getIdList('Sampler');

    const samplers = [];

    const KEY_COLOUR_OPACITY = 0.28;

    const KEY_COLOURS = [
        Colours.withAlpha(Colours.darkcyan, KEY_COLOUR_OPACITY), // Sampler 1
        Colours.withAlpha(Colours.darkcyan, KEY_COLOUR_OPACITY), // Sampler 2
        Colours.withAlpha(Colours.darkcyan, KEY_COLOUR_OPACITY) // Sampler 3
    ];

    for (id in samplerIds) {
        samplers.push(Synth.getSampler(id));
    }

    KeyboardPreload.setLoadingCallback(function(isPreloading) {
        if (!isPreloading) setKeyColours();
    });

    inline function setKeyColours() {
        for (i = 0; i < 128; i++) {
            Engine.setKeyColour(i, Colours.withAlpha(Colours.black, 0.2));
        }

        for (i = 0; i < 128; i++) {
            for (y = 0; y < samplers.length; y++) {
                local s = samplers[y];
                if (s.isNoteNumberMapped(i) && !s.isBypassed()) {
                    Engine.setKeyColour(i, Keyboard.KEY_COLOURS[y]);
                    break; // Exit the loop once a non-bypassed sampler is found
                }
            }
        }
    }
}

I just want to color the keys with Samplers which are NOT bypassed. Its a headache!

@d-healey

Great. Now i feel even more stupid.
Then why is there a enable/disable parameterID at all?

@Lindon

Does everyone use bypass and not enable/disable for samplers?
Isn't that a CPU drain or does it not matter at all?

@d-healey

There really should just be a:
Sampler1.isEnabled
funtion...

And a function for enable and disable Samplers in scripting.

@ulrik Can you apply multiple parameterid in the Interface designer? - or should it be done in scripting?

@ulrik said in Sampler (if enabled):

Sampler1.isBypassed();

Thanks, too bad i only use enable/disable for my samplers :/

Is there any function like this?

if (samplers[y].isEnabled() && samplers[y].isNoteNumberMapped(i)) {

Cant find it in the documentation, to check if a sampler is enabled or not.,