MAC AUi Component build doesn't show in a DAW
-
Hi everyone,
I've been having weird bugs with the latest version of HISE right now.
I've been able to export an Audio Unit in MAC successfully, but still not showing in a DAW ?
Is there any way to debug this?
I'm not on Mac OS Catalina by the way.
Thanks again!
-
Does the VSTi work?
-
@d-healey said in MAC AUi Component build doesn't show in a DAW:
Does the VSTi work?
Yep! no problem on this side.
-
@Alex-Paradis facing the same on GarageBand. Try restarting. Logic works fine for me.
-
You might have to force your mac to rescan 3rd party plugins. This is from Apple's website
Rescan all plug-ins
To automatically rescan all installed plug-ins, remove the Audio Unit cache file.In the Finder, press Option and choose Go > Library.
In the Finder window, go to Library/Caches/AudioUnitCache.
Move the files from AudioUnitCache folder to the Desktop.
Restart the computer, then open Logic Pro X or MainStage (or Garageband). All installed Audio Units plug-ins will be rescanned. -
Usually a restart is all that’s needed. If not, there’s also a plugin manager in the preferences - you can see if it’s listed there and rescan it if needed.
-
Thanks guy for the help!
I've tried multiple things on my MAC, removing caches and restarting, but still not showing :/.
I will try with other MACs and see If I can find why I don't see it.
-
what happens if you run auval with your plugin?
-
@Christoph-Hart said in MAC AUi Component build doesn't show in a DAW:
what happens if you run auval with your plugin?
I will try this today and get you back on it.
-
@Alex-Paradis Hi Alex. Have you kindly found a solution for this.. I think it’s the 5th time that I’m trying without a positive outcome.
-
@nesta99
OK this is probably because you are using a DAW (Logic, GarageBand etc.) that checks the AU plugin code.
Once the DAW has found a plugin that reports its code as (say) "abcd" it will reject and not show all other plug-ins that report this ID
So you need to set the code for the plug-in:
File>Preferences>Project>Plugin Code
-
@Lindon Thanks! Yes I use Logic Pro X.
I do already have a demo Plugin that I made just to try out, and it has "Abcd" as the plugin code (and it works perfectly in Logic).
But for this new Plugin I've created is still not seeing it.
I think it's because of the Plugin code in the previous demo plugin I've made.So do I need to delete the demo plugin?
And what's the plugin code I should use?
Is it up to my choice or there's a rule on creating a Plugin?
Does every plugin have a different Plugin code?Thanks in advance. New to Hise.
-
@nesta99 said in MAC AUi Component build doesn't show in a DAW:
@Lindon Thanks! Yes I use Logic Pro X.
I do already have a demo Plugin that I made just to try out, and it has "Abcd" as the plugin code (and it works perfectly in Logic).
- yes it will..
But for this new Plugin I've created is still not seeing it.
I think it's because of the Plugin code in the previous demo plugin I've made.if it has "Abcd" as its code then Logic will reject it as a duplicate.
So do I need to delete the demo plugin?
- or reset the plugin codes
And what's the plugin code I should use?
up to you theres no official rules...Is it up to my choice or there's a rule on creating a Plugin?
no rules other than those applied by HISE.
Does every plugin have a different Plugin code?
only if it wants to get loaded in Logic...:-)
Thanks in advance. New to Hise.
-
@Lindon Thanks so much! I am really grateful
-
@nesta99 said in MAC AUi Component build doesn't show in a DAW:
@Lindon Thanks so much! I am really grateful
only be grateful if this solves your problem...
-
True @Lindon ! Trying exporting now.
-
@Lindon Sorry for disturbing again.
In this case I've changed the plugin code from "Abcd" to "Vygr" and it says : 14:48:06.555 › stdout: The Plugin Code must have this structure: 'Abcd'ERROR: Export Error.
I don't know what structure is talking about.
-
@nesta99 you need to find a value that matches the riules: the only rules I know are:
-
4 chars required
-
first char must be upper case
-
perhaps you have a space in there?
-
-
@Lindon Yeah, discovered that the problem wasn't there. Yesterday, Since to be Notarized by Apple, It was needed for my Mac to upgrade to Xcode 10 (I had the 8).
But the moment the plugin was exporting, the console said "The i386 architecture is deprecated. You should update your ARCHS build setting to remove the i386 architecture"
So I'm downgrading Xcode to 8 version... Crap!
Thinking about upgrading my mac from Sierra to Mojave but I'm seeing too many problems on the forum concerning this.
Since Notarizing is not compulsory imma go for Xcode 8 tho. -
@nesta99 Use xcode 10, don't build 32bit plugins.
