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

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?

Is that in the preferences somewhere?

How do you do a debug build?

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

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.

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.

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.

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

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.

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

@Lindon If each AUi component needs a unique code, how do you make sure your code doesn't accidentally match another developer's code?

Yeah --it might be the case that more people want to stick within the familiarity of kontakt and other major samplers. I don't know. I should probably have done more research before diving in
But, it'd be nice to at least get this one vst out there.

Glad to hear it :thumbs_up: I'm still working in Kontakt of course, but am considering the benefits of hise for future projects.

I was thinking of putting out a vst version of Sospiro alongside the kontakt version, and seeing how many people get the kontakt version vs. the vst.

Ok, it finished building, and it worked on the first try with those settings!
Thanks again

No that was not intentional. Thank you, trying this now...

@d-healey
Hi David, I'm attempting to build Hise without IPP on Mojave.
I just downloaded the scriptnode branch, and without changing anything, the jucer file looks like this:

USE_IPP=0 looks like what I want.
When I try to build in Xcode I get this though:

Perhaps IPP needs to be turned off somewhere else...
I know that in the hi_core there's an IPP option, and I see that it's enabled there actually!

When I tried disabling IPP here I got the same error messages.
I wonder if there may be somewhere else where I need to disable IPP?

@Lindon Thank you, that doc will be very helpful

Ok that's what I figured. Good to know.

Ok cool.
Well, I ordered the 2014 macmini, so I'll learn soon enough about what you can and can't do.

By the way, you asked about x86 on Big Sur before, which reminds me of another question:
Why are plugins offered in 32-bit still? I always use 64-bit myself, but maybe there are some cases where users actually do need 32-bit?