Mac Exports

[d.healey]

@itsmochajones I think AU plugins have a .component extension.

[ulrik]

@d-healey said in Mac Exports:

@itsmochajones I think AU plugins have a .component extension.

Yes, that's right :)

So the "components" (au plugins) go to User/library/Audio/Plug-Ins/Components
and the VST3 goes to
User/library/Audio/Plug-Ins/VST3

[Natan]

These are paths for Mac:

• Macintosh HD:/Library/Audio/Plug-Ins/Components/ (AU .component file extension)
• Macintosh HD:/Library/Audio/Plug-Ins/VST/ (VST 2 .vst file extension)
• Macintosh HD:/Library/Audio/Plug-Ins/VST3/ (VST 3 .vst3 file extension)

For windows, There is No Default Location For VST2
But For VST3, This Is The Default Location:

• C:\Program Files\Common Files\VST3 (64Bit)
• C:\Program Files (x86)\Common Files\VST3 (For 32-bit VST 3 plug-ins )

Tip:
Just Get @d-healey 's HISE EXPORTER TOOL, and Don't Worry About The Installers For Mac/Pc, That Gold Tool Will Do It All For You

[ulrik]

@Natan if I export from Hise both the VST3 & Component will be exported to User/Library.........., is it different for you?

Or are you referring to exporting with Davids export tool?

[Natan]

@ulrik Same Here, It Places The Files into the User/Library.

"I Remember Somewhere Christopher Said that This is Because Mac Ask For Permission To Let Hise to Export Into The System Folder, So He Decided to Not Using That Destinations"

And Yeah I Use Dave's Exporter Tool, And It Places The Files into Dummy Folder Inside your Project Folder, And Will Create The Installer By Looking At That Folder.

To Me, It Is The Easiest Method, It Compiles All Formats, And Then Exports The Installers As Easy As A Few Clicks.

[trillbilly]

@d-healey Thats what I was wondering. Thanks!

@ulrik Perfect, thanks!

@Natan This is super useful, thanks! What folder do you recommend for VST2 (.dll) in the Windows system? Also, the HISE EXPORT TOOL sounds amazing. If you get the chance, can you post a link in the thread? Ill search for it right now!

[Natan]

@itsmochajones Glad to help

Windows Installers All Shipped With This Location As The Default:

• C:\Program Files\VSTPlugins

But All Users Use Their Own Location During The Installation.

To Get Hise Exporter Tool, Check Out @d-healey 's Patreon.

Get A Cup Of Coffee For Dave, and Enjoy His Masterpiece Tool

[trillbilly]

@Natan Much appreciated! Ive found the code on GitHub but will definitely pay a visit to his Patreon page as well!

Speaking of the HISE EXPORTER TOOL code, I assume this is something I need to build into HISE, is that correct?

[Natan]

@itsmochajones No It's An Independent Program And Just Connects To Hise To Export The Au/Vst/Vst3 and Aax Formats For You At Once, As Plugins Or Instrumnets.

Also It Packages Your File Into Installers As Easy As One Click.

Take A Look At Forum Called "Export Tool" For More Infos And Troubleshooting, And Dont Forget To Ask Whatever You Want From The Greatest Legend Of All Time @d-healey Sir David.

He Is A Teacher Indeed

[trillbilly]

@Natan Im signing up for the Patreon now and will get started with the Export Tool. Thanks again!

[trillbilly]

So I understand that you must use MAC to export any AU plugins, correct?

MAC users can also use VST3 (I think) but only the AU will compile and export the .components?

Is there another way to generate the component files that VST3 needs to be compatible with MAC on Windows?

[d.healey]

@itsmochajones said in Mac Exports:

So I understand that you must use MAC to export any AU plugins, correct?

Yes

MAC users can also use VST3 (I think) but only the AU will compile and export the .components?

Mac can use VST2 and VST3. VST2 has a .vst extension, VST3 has the .vst3 extension, AU has the .component extension.

Is there another way to generate the component files that VST3 needs to be compatible with MAC on Windows?

No, you have to export for each OS's plugin on its own operating system, there is no cross-compiler available for HISE plugins.

[DanH]

@itsmochajones you need a Mac to compile plug-ins for Mac, and a pc running windows to compile for windows.

There’s no way around this.

[trillbilly]

@d-healey

Thanks! Do you have any recommendations of a cheaper Mac that will suffice to only do HISE compilations on?

[d.healey]

@itsmochajones I'm using a 2013 Mac Mini, it takes a while but it does it. I don't know how much they cost, this was given to me.

[Natan]

@itsmochajones Get Macbook Air 2018
Intel Core I5
256 Gb Ssd
8/16 Gb Ram ( Not Sure About Which One Ist)
And It Will Do The Job Very Nicely

[trillbilly]

@Natan Much appreciated!

And I believe I seen thus elsewhere on the forum but just to clarify...

HISE files are the same for MAC or PC, correct?

Say I create an instrument on PC, I can then use the same project folder to open and compile on MAC?

[DanH]

@itsmochajones yes

[Natan]

@DanH said in Mac Exports:

@itsmochajones yes

Yes, Mate :)
Just Aware Of An Issue With Font (It's Not Because Of Hise)

Not All Fonts Made Cross-Platform Compatible, So You May Notice Some Changes In Terms Of Size, And Your Labels Go Crazy.

Use Google Fonts, They Optimized
& Work Nicely On Both Mac/Pc.

Other Than That All Files Inside Your Hise Project Will Translate Perfectly :)

[trillbilly]

@Natan Thank you fine sir