@Yannrog
You must codesign your plug-in files.
And you must codesign, notarize, and staple your installer.

Here are the commands I use. Of course, you'll need to enter your own data. For the commands to work, the files must always be on your desktop.

// AU Component (Sign) codesign -s "Developer ID Application: YOUR NAME (YOUR CODE)" "/Users/YOUR_USERNAME/Desktop/YOUR_PLUGIN.component" --timestamp // VST3 (Sign) codesign -s "Developer ID Application: YOUR NAME (YOUR CODE)" "/Users/YOUR_USERNAME/Desktop/YOUR_PLUGIN.vst3" --timestamp // Installer (Sign) codesign --deep --force --options runtime --sign "Developer ID Application: YOUR NAME (YOUR CODE)" "/Users/YOUR_USERNAME/Desktop/YOUR_INSTALLER.pkg" // Installer (Notarization) xcrun notarytool submit --apple-id "YOUR_MAIL_ADRESS" --password "YOUR_PASSWORD" --team-id "YOUR_CODE" --wait "/Users/YOUR_USERNAME/Desktop/YOUR_INSTALLER.pkg" // Installer (Staple) xcrun stapler staple "/Users/YOUR_USERNAME/Desktop/YOUR_INSTALLER.pkg"

This article is very helpful, and it allowed me to set up my system:
https://www.kvraudio.com/forum/viewtopic.php?t=531663

This article is also very helpful if you run into any problems:
https://developer.apple.com/documentation/security/resolving-common-notarization-issues

@brucerothwell Yes

@brucerothwell said in Is HISE Compatible with Xcode 26?:

Curious… what is the HISE 4.1 installer for, then?

Mostly for confusing people :)

The prebuilt version if a good way for people to try out HISE before committing to going through the process of setting up their system for compiling.

Also be aware that you're going to need macOS, Windows, and Linux systems in order to be able to export for each platform (all covered in the course).

@jeffd Thanks for confirming.

@Morphoice what kind of custom control?

@VybeCodeDSP StripKit looks really nice!

It seems you only support the Windows platform?
If so, are you planning to support MacOS?
If so, let me know if you need a beta tester!

@paper_lung Check this thread: https://forum.hise.audio/topic/5499/audiowaveform-laf

@dannytaurus Yeah, keeping the colours tidy in your code is easier in the end. Then you can set the component colours from script when needed and everything updates automatically if you adjust something instead of copy/paste in all components...

I tend to to everything I can in paint routines, the less components in the tree, the happier I am!
That being said... In order to reduce CPU load, I still tend to keep fixed drawing (bg, mask, etc...) in separate panels so the LAF function job is only constrained to what is really necessary. I also keep all the math constants externally, unlike the example...

Other issue with the "multiple panel masking technique" is that when you want to move it, it can be very annoying, unless adding them all in an holder panel, which is one more component... 😬

@Felix-W Break it down. Make a minimal project with one sampler where notes only trigger during legato transitions. Once you get that working you can start to incorporate it into your project.

@David-Healey Ok,

Is it possible to discuss in private?

@dannytaurus said in Stop pruning default values from XML?:

because I'm setting some values in script that happen to be default values.

Hmm this might be the source of an issue I was having too, I might try it.

@dannytaurus Good job detective!
I agree to the WTF, seems that developing new protocols of all sorts but there's still no agreement whatsoever in the way DAWs handle such a simple task... Shame...

@dannytaurus said in Anyone doing factory presets only, with no Save button?:

power-user feature

It for sure is a power-move and not as intuitive as a user preset.

@zachhealy1005 said in Linux:

so compiling hise on my laptop is in fact impossible.

If you reduce the number of compile threads to 1 or 2 it might still compile.
make CONFIG=Release -j 2

@David-Healey well done...for now I might stick to my "Load Request File" based appraoch...

@ustk Good call. Claude suggested I update to this:

UserPresetHandler.setPostCallback(function(presetFile) { // On first launch the default preset loads with no file (frontend leaves // currentlyLoadedFile empty), so getCurrentUserPresetName() is "". Fall back // to the default preset name. (Editor returns the real name, so it's unaffected.) var name = Engine.getCurrentUserPresetName(); btnShowPresetBrowser.set("text", name != "" ? name : "00 INIT"); });

I'll try it and make sure it works on first launch, and doesn't interfere with reloading DAW sessions.

There is a detailed comparison of various pitch algorithms.
Rubberband performs really well and it's not too difficult to integrate into Hise.
I think there's even a detailed post somewhere here on the forum about this topic.

@Sampletekk David, I bow in your general direction!