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).
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.
-
@nesta99 what David said.....
if you want your plugin to run on anyone else's machine you WILL have to do the notarizing... -
@d-healey Do I need to delete Hise and Rebuild it on the Projucer High Sierra?
Or Should I uprage my Mac to Mojave in order to make Hise Work and Notarize my plug ins?Thank you in advance for your replies
-
@nesta99 I've only ever used Mojave
-
@d-healey said in MAC AUi Component build doesn't show in a DAW:
@nesta99 Use xcode 10, don't build 32bit plugins.
What´s the lowest supported macOS version exportable in Xcode 10?
-
@Alex-Paradis said in MAC AUi Component build doesn't show in a DAW:
Thanks guy for the help!
I've tried multiple things on my MAC, removing caches and restarting, but still not showing :/.
User/system folders: (I´m sure you know this, but still) If you are trying to open au-plugins in the
user/Library/Audio/components/folder you won´t be able to. Logic only reads system folders. So HISE normally exports to a folder Logic cannot read from. Move the .component toMac HD/Library/Audio/components/instead, if you don´t normally. -
@Lindon said in MAC AUi Component build doesn't show in a DAW:
@nesta99 what David said.....
if you want your plugin to run on anyone else's machine you WILL have to do the notarizing...Is that for macOS >10.14.x (Mojave)? Or for them all? And are we talking about the actual .component files or the installer package (.pkg)?
-
@andioak said in MAC AUi Component build doesn't show in a DAW:
@Lindon said in MAC AUi Component build doesn't show in a DAW:
@nesta99 what David said.....
if you want your plugin to run on anyone else's machine you WILL have to do the notarizing...Is that for macOS >10.14.x (Mojave)? Or for them all? And are we talking about the actual .component files or the installer package (.pkg)?
Mojave onwards.
If you are using a packager then you can noterize the package - and the contents will be noterized for you.
You will have to code sign each thing separately before you do any of this.
-
@Lindon If each AUi component needs a unique code, how do you make sure your code doesn't accidentally match another developer's code?
-
@benosterhouse I believe the code is also checked again the company code. We should probably test this at some point...
-
Ooh I didn't distinguish between the two 4-letter codes. Company code and plugin code.
If it's checked against the company code, then is there some list of which companies are using which codes?
I can still see room for conflict there... -
is there some list of which companies are using which codes?
Nope, it's the Wild West. I wonder if the bundle ID is also taken into account.
