Exported vst3 for Windows, now macOS?

[d.healey]

@ThinkTank said in Exported vst3 for Windows, now macOS?:

so i need to install HISE, JUCE and everything on the VM?

You just need to clone the HISE repo, there's no installation required. All the instructions for building HISE on MacOS are in the repo's readme.

Here's a guide for notarizing - https://www.kvraudio.com/forum/viewtopic.php?t=531663

It's difficult and time consuming the first few times you do it, but after a while it will become fairly painless, and you can put it all in a bash script to automate it.

[ThinkTank]

@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 :grinning_squinting_face:

[ThinkTank]

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

@ThinkTank said in Exported vst3 for Windows, now macOS?:

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

Totally different systems, to run natively they need to be compiled on the OS you want it to run. Linux too.

[gorangrooves]

@ThinkTank Do not overlook AAX! It is an absolute must, despite what hoops you may need to jump through. Don't let anyone convince you otherwise.

Reach out to devauth@avid.com and get set up as a developer. Avid will get PACE to waive the signing tools fee. They have been great to deal with.

Once you set things up with scripts, it won't be difficult to re-sign things when recompiling software. Things are only challenging when you are doing them for the first time.

I regretted taking the advice of not doing AAX right away.

For skilled developers, doing these Apple and PACE extra steps are burdensome because they are out of their comfort zones. But for somebody who is struggling with everything (like me), it is just another little step of struggle.

[d.healey]

@gorangrooves said in Exported vst3 for Windows, now macOS?:

Don't let anyone convince you otherwise.

I'm not using it :D

[gorangrooves]

@d-healey and you have no idea of what you are missing out on!

[d.healey]

@gorangrooves said in Exported vst3 for Windows, now macOS?:

@d-healey and you have no idea of what you are missing out on!

I get a few enquiries about it but my hands are tied by the licensing. So I direct users to external hosts and wrapper plugins.

[ThinkTank]

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

[gorangrooves]

@d-healey there is more than that. Why are your hands tied by licensing?

[ThinkTank]

@gorangrooves

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

[d.healey]

@gorangrooves said in Exported vst3 for Windows, now macOS?:

@d-healey there is more than that. Why are your hands tied by licensing?

Can't release AAX as GPL.

[gorangrooves]

@d-healey Then change the license how you release the AAX.

[d.healey]

@gorangrooves I'd have to pay for a HISE, JUCE, and PACE/AVID license and I don't see me making that cost back from pro-tools users

[gorangrooves]

@d-healey FYI There is no fee for Avid/ PACE. Nobody will chase you from JUCE, and the HISE starting fee is quite reasonable. But yeah, you'd have to decide if/when the moment is right. I went all in.

One of the main reasons for me to develop plugins using HISE was the accessibility to as wide of a user base as possible. I didn't want to be limited to Kontakt users or, say, Halion. Part of the accessibility is affordable pricing to end-users. So, covering all grounds is very important for growth. There is a significant Pro Tools user base, especially in pro studios.
The mobile platforms are the next frontier.

[d.healey]

@gorangrooves said in Exported vst3 for Windows, now macOS?:

There is a significant Pro Tools user base, especially in pro studios.

But pro-tools is horrible for MIDI :p Are these people buying sample libraries or effects?

[gorangrooves]

@d-healey Agree, but yes. You can not underestimate the power of branding. Avid has quite a user base of Pro Tools subscribers. I read somewhere that it was about 200K, which I think is correct.

[Christoph Hart]

@gorangrooves To be honest, I think whether to offer AAX or not ends up being viable highly depends on the product category.

With virtual drums you have a much more ProTools leaning user base than David with his orchestral libraries.

This aside, you can be pretty sure that I will not lawyer up to sue you for copyright infringement just because you "accidentally" clicked on the wrong button in HISE and export an AAX plugin :)

[d.healey]

@Christoph-Hart said in Exported vst3 for Windows, now macOS?:

@gorangrooves To be honest, I think whether to offer AAX or not ends up being viable highly depends on the product category.

With virtual drums you have a much more ProTools leaning user base than David with his orchestral libraries.

Hmmm maybe I should reconsider it, since Rhapsody is not just for my instruments. ..

[Christoph Hart]

@d-healey yup for Rhapsody it might make sense and I think that Sordina would also be a good candidate for Protools.