i386 deprecated!?!?!

[hisefilo]

@Christoph-Hart maybe a more intuitive way is to set hise to place compiled plugins into binaries/compiled on Mac? Like it does on win

[Christoph Hart]

Yes, the default location is the user's plugin directory:

~/Libraries/Application Support/Audio/Plug-Ins/VST

There is no way on Mac to point to a VST directory (on Windows it can be any path), so on macOS you're pretty much limited to this path and it's almost identical twin without write permissions /Libraries/Application Support/Audio/Plug-Ins/VST. That's why there is a plugin-copy step.

[hisefilo]

@Christoph-Hart ohhh! I see. MacOS is kind of weird on plugin locations. I got some under system folder. Some others on user folder. (Packed installlers i.e. kontakt places into system, asking for admin pass obviously)

[Christoph Hart]

And it all gets even more fun if you try to load it in a sandboxed host, then everything outside the Music folder isn't accessible.

[Lindon]

@hisefilo OK well I tried that and it seems its in a folder called VST(who knows where that is hiding on a disk I cant even get to the root of...) - well there's a file in there called ChromaticPanFlute.vst - which I assume is the VST plug-in...

though worryingly VST also has a folder in it called ChromaticPanFlute Debug.vst -- which has a folder structure but no content...

[Lindon]

@Christoph-Hart sadly when I use the Go menu in the Finder it tells me there is no folder called Libraries or Audio

when I go to the Users/name here folder in Macintosh HD then "Libraries" isnt there.

[hisefilo]

@Lindon LOL Macos hides dangerous folders to common users. Option click on Go menu to see Library folder

ChromaticPanFlute.vst is the file. You've found it

[Lindon]

@hisefilo really honestly - whats "option click" - I've tried cmd click that doesnt show me any thing more than normal click

[d.healey]

@Lindon option = alt

[orange]

@Lindon Go to the "Go" menu, then press and hold "alt" button, the hidden library folder appears.

[Lindon]

@orange so its not called "Libaries" at all as per Christoph's post - its called "Library"

This in the end this is moot as when I go to LibraryI can see Application Support but any way I get to Application Support there is no folder in it called Audio - so I still have no idea where my VST plug-ins are going.

[hisefilo]

@Lindon this is the place /Users/filo/Library/Audio/Plug-Ins/VST

replace "filo" for your usename on macos

You can also directly go to this folder on the Go menu >> Go to folder

[Lindon]

@hisefilo yes so everyone keeps telling me, but ...

whilst /Users/filo/Library exists, there is no Audio folder in there.

[hisefilo]

@Lindon replace filo with your username

[hisefilo]

@Lindon is your vst plugin accesible within your daw? I mean can you load it correctly?

[Lindon]

@hisefilo ...er, yes obviously...sorry talking about the user name replacement...

[hisefilo]

@Lindon if your daw on macos is loading it, it is somewhere. Also check /Library/Audio

[lalalandsynth]

@Christoph-Hart said in i386 deprecated!?!?!:

/Libraries/Application Support/Audio/Plug-Ins/VST

So, been through this as well, managed to build an AU plugin , shows up as .component in the plugins folder.
I have another plugin in that folder (Hello world) from Juce.
The plugin from Juce shows up in Reaper but my plugin does not.

Same plugin was built on Win as VST and works nicely.

Next up is trying to build a VST on Mac and see if that works.

[AxiomCrux]

I got this error just now trying to build. I am wondering if someone could please provide a compiled version on the github that works properly so that everyone doesn't have to re-build HISE. I am going to try and do that process now, but im having to do a fair bit in the process and I feel like thats something that should be made available, if I am successful in building the newer HISE, I would love to help in posting the mac version. I just want to make sure something like that is available to anyone new that comes to HISE. It seems like its starting to fall out of active production and its too good to become abandoned, but I am also not enough of a developer to be the guy to help take over and push it forward yet.

[ustk]

@MacroMachines The fact is that having a prebuilt version of Hise will not help you to export final products if you don't have the right tools anyway.
Another important part is that one can have different preprocessor settings in the Projucer, as well as other settings.

And this is not talking about the bug fixes and updates, especially with the V3 coming soon, and any custom modifications, custom nodes you need to compile with, etc…

My guess is that it worth having a setup that works so you're good to build by yourself. And once it works, re-compiling is very easy