MAC AUi Component build doesn't show in a DAW

[benosterhouse]

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...

[d.healey]

@benosterhouse

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.

[benosterhouse]

Taking the bundle ID into account would be nice! I'll try making two AU's with the same plugin and company codes, but different bundle ids.

[benosterhouse]

When I try to change the Bundle Identifier it says, "BundleIdentifier doesn't match the required format.Press OK to load the default value."

There's one place here where it talks about bundle identifiers here, but I'm not sure how it relates: https://developer.apple.com/library/archive/documentation/MusicAudio/Conceptual/AudioUnitProgrammingGuide/AudioUnitDevelopmentFundamentals/AudioUnitDevelopmentFundamentals.html

[d.healey]

@benosterhouse The format should always be xxx.xxx.xxx usually it's a reversed URL, like com.osterhouse.ben

[benosterhouse]

When I try anything like "com.myCompany2.product" I get that message, so I think the format is ok.
Perhaps "myCompany" and "product" are variables that you have to change somewhere else.
In the preferences I don't see another setting to set the company and product.

[benosterhouse]

Actually, I see under User Settings you can change the Company. You wouldn't want to change that for every plugin though of course!

At the top, under Project Settings you could change "Name", and maybe that would change the product in the bundle identifier.

However, I've already tried exporting two AUi's with the same codes but different names.
Reaper would only show one of them at a time.

[d.healey]

Perhaps the bundle ID has to be lower case.

[benosterhouse]

That's not it. You can actually ignore that message. I'm just going to see what happens when I compile. It takes about 20 minutes on my 2014 macmini.

[d.healey]

@benosterhouse Do a debug build it will be much faster, it's the linking that takes the time.

[benosterhouse]

Soooo glad you told me that. I was wondering if this was just the way things were going to be ::squinting_face_with_tongue:

[benosterhouse]

How do you do a debug build?

[d.healey]

@benosterhouse Select build for running.

[benosterhouse]

Is that in the preferences somewhere?

[d.healey]

@benosterhouse It's in the build menu (I think) in Xcode. Build for profiling is for release and build for running is for debug (the naming makes no sense to me).

[benosterhouse]

If I start compiling the AU from Hise, then interrupt it and open up the autogenerated.jucer, in Xcode I can go to Product -> Build -> for Running, and then it starts compiling there.
Is that what you do for a debug build?

[d.healey]

@benosterhouse That will work. I probably do it from the commandline... I can't remember because I haven't built a debug build on MacOS for ages.

[benosterhouse]

Ok yeah, you use commandline scripts so you can automate building, right?

[d.healey]

@benosterhouse Yeah, or my export app.

[DanH]

@d-healey Any chance of a version of your export app being merged into HISE itself? Would certainly be useful (shall I add to the feature requests list?! )