Mac Export - arm64 unidentified symbols

[trillbilly]

@d-healey I have the VST folder in my directory but no VST3 folder. I created it myself, placed the VST in it and directed Live to this location. Still no luck.

[trillbilly]

@d-healey I see that in HISE preferences there is a "Support 32bit Mac OS" box selected. I believe Ableton (10 & 11) are only 64bit. Would this cause any issues?

[d.healey]

@trillbilly I wouldn't have thought so, but try disabling it and see if it works.

[Dan Korneff]

@trillbilly said in Mac Export - arm64 unidentified symbols:

I created it myself, placed the VST in it and directed Live to this location. Still no luck.

Do you have Cubase installed?
I ran into a similar issue with a new W11 build. Installed HISE and Reaper, created a VST3 folder for plugs, and Reaper couldn't read them. After I installed Cubase, everything just started working :man_shrugging:
I didn't really investigate, but you might be experiencing something similar?

[trillbilly]

@d-healey It didn't seem to matter.

I was able to export VST2 and locate with Live no problem. VST3 still a no-go.

@dustbro No, Ive never used Cubase. Did you install a Demo version or do I need to purchase?

[Dan Korneff]

@trillbilly said in Mac Export - arm64 unidentified symbols:

id you install a Demo version or do I need to purchase?

I believe they have demos. You could also send me a test VST3 file to check on my rig as well.

[trillbilly]

@dustbro Ok, cool! Im downloading trial of Cubase Elements now. If that fails then we will press onward...

[d.healey]

@d-healey said in Mac Export - arm64 unidentified symbols:

until someone updates the compile template in HISE and makes a pull request.

Done - https://github.com/christophhart/HISE/pull/217

[trillbilly]

@dustbro Got it downloaded and installed. Now when I view the VST3 folder in Live I can see the Cubase VST3s (Halion, some drum machine, etc) but not my exported plugin.

So the file path is correct but still the exported plugin does not show.

[Lindon]

@trillbilly - where did you put your VST3?

@d-healey already pointed out you MUST MUST MUST put your VST in the correct VST3 folder - which is what Cubase is probably doing -

Read this (if you havent already):

Just a moment...

(helpcenter.steinberg.de)

[trillbilly]

@lindon Yes, I have them in the same folder as the Steinberg Plugins.

Now that Im looking, the file type is "Alias" rather than "VST3 Plugin" like Steinberg. Am I pulling VST from the correct location?

Binaries/MacOSX/build/Release

Or does Mac build and overwrite in the Binaries/Compiled directory?

[Lindon]

@trillbilly read the page David and I have pointed you to...but in brief - dont put your work in another vendors sub-folder, and an alias is not a file.

[trillbilly]

@lindon I also tried in the VST3 folder but now I realize about the Alias file type. I have removed everything from previous export and am exporting again with some minor settings changes.

Im assuming I pulled the wrong file from Binaries? Sorry, my brain is a little fried as of late.

EDIT: Thanks for providing the link again, I did check it out and ensured all is correct. It seems it is.

[ulrik]

@trillbilly I see you're on Mac, when I compile the plugins, both au and VST 3 will automatically be placed in the right folder in the "User Library" (your name), not in the All Users Library as it is in your picture

[trillbilly]

@ulrik You were spot on. I thought I was going crazy for a second. I guess I still may be.

The exported directory is:
Users/Your Mac/Library/Audio/Plug-Ins/VST3

You may have to show your hidden folders in order to view it.

I just assumed exported VSTs would be in the HISE Folder, not on the Mac Drive.

Thanks @d-healey @dustbro @Lindon @ulrik fr the help, its super appreciated.

One las thing on the topic of Mac exports. For distribution purposes, is it wise to become a "Mac Developer" (I think its like $99/year) to ensure delivered files work properly? I don't intend to have an installer since its easy enough to just copy-paste & install samples.

[d.healey]

@trillbilly said in Mac Export - arm64 unidentified symbols:

is it wise to become a "Mac Developer"

Yes.

Also you shouldn't distribute VST2s unless you have an agreement with Steinberg, which they are no longer providing.

[trillbilly]

@d-healey I was reading on this recently. Noted. Thanks again.

[ulrik]

@trillbilly said in Mac Export - arm64 unidentified symbols:

is it wise to become a "Mac Developer"

Yes :)

[trillbilly]

@ulrik Great thanks. I was rummaging through Xcode and seen an area for your apple development profile. I think HISE has the same settings in the the preferences panel. Is this correct? If so, does it auto-fill from HISE to Xcode?

[Lindon]

@trillbilly said in Mac Export - arm64 unidentified symbols:

@ulrik Great thanks. I was rummaging through Xcode and seen an area for your apple development profile. I think HISE has the same settings in the the preferences panel. Is this correct? If so, does it auto-fill from HISE to Xcode?

they are not really the same thing.

You will need an Apple Developer account to create install certifiicates - but if you are not doing installers then this might not be a requirement - however you are going to have to codesign your plugins - so you will need an Apple Account (the sort of thing everyone has to use the Apple Store) to create a password for altool - which you will need as part of the codesigning process...