@Lindon said in Error when exporting:

@Sampletekk well your project is poorly named - theres a space at the start and end of the name - so I'd get rid of these first...as well as any spaces in the middle to be honest..

That worked! Thanks!

@Lindon said in Error when exporting:

@Sampletekk well your project is poorly named - theres a space at the start and end of the name - so I'd get rid of these first...as well as any spaces in the middle to be honest..

Aha! I'll try that!

@d-healey said in Error when exporting:

@Sampletekk does a blank test project compile?

Yes. I also exported another project earlier today without this error

@Lindon said in Error when exporting:

@Sampletekk does it include a Faust node? is it on a permanent drive?

No Faust nodes and it's on a permanent drive.

When exporting to VST3, AU, I'm getting the following:

Any ideas? I've exported other projects without problems

@aaronventure Yep, I have the latest release from the dev branch. I'll try it with the latest IPP and see what happens!

I'm installing Hise on a Windows 11 machine and I'm following David Healey's great video about this. However, the IPP version he uses is an old one, and the one available through the link in the video, is a newer version. So, would I run into any problem using the current IPP version, or should I look for an older one?

@d-healey I'm also trying to do this, getting a "Script not found", "Error loading script interface".

@d-healey Thanks!

If you want to change the mode on a knob with a script, like btnSync.set("mode", value);, what would you use as "vakue". Are the different mode-types indexed, so that "Frequence" is 0, "Decibel" 1 and so on?

@Simon said in vst3 is a folder in Windows?:

@Sampletekk Nope! Despite the deceptively consistent "vst3" naming, they must be separately compiled for whatever platforms you want them to run on.

@Simon Oki, good to know! Would a vst3-file compiled in Windows work on a mac?

After making a vst3-file, that works great on a mac, I tried it on a Windows PC, and there the VST3 file turns up like a folder:

When building a installer for windows using Inno, I can't add the file, since Inno looks at it as a folder and not a file.
Any ideas?

@d-healey said in Notarizing component (AU):

@Sampletekk You don't notarize the AU (or the VST3 or the standalone) you just codesign it. You notarize the PKG/DMG/Zip

Ok, think I've got it now......

Takes forever it seems, "In Progress" fot 5 hours now, The VST3 took about three minutes. Normal?

@d-healey said in Error when notarizing:

@Sampletekk Actually you don't notarize the binaries (vsts/au/standalone) you notarize and staple the pkg (or zip file, whatever the container is basically). A more detailed explanation is at that KVR link.

Can the pkg-file be notarized without making it into a zip-file?

@d-healey said in Error when notarizing:

@Sampletekk Actually you don't notarize the binaries (vsts/au/standalone) you notarize and staple the pkg (or zip file, whatever the container is basically). A more detailed explanation is at that KVR link.

Aha!

@d-healey Cool, Codesigned, Notarized and Stapled! Thank you David for all help!!!
If I make a pkg-file containing the vst3-file, do I need to repeat the process for the pkg-file?

@d-healey said in Error when notarizing:

@Sampletekk Path looks ok to me, except I Buids instead of Builds

Oh and you shouldn't use quotes and escape characters (\) use one or the other.

Woohoo! That worked! Notarisation too!

@d-healey said in Error when notarizing:

@Sampletekk said in Error when notarizing:

should it be the "Entity name" or the "Account holder"

I'm not sure, but if you click to view your certificates, you'll see the team name and ID in the top right corner.

Ok, some kind of progress, (I think...). At least another error message:

I drag the file that should be codesigned and drop it on the Terminal window, but the path looks a bit dodgy. Is there another way to get the correct path?