@d-healey This was what I was missing. Thank you!

@d-healey Yes, the latest version. The workaround was to create 16 outputs somewhere else and then copy to the container.

@Christoph-Hart I knew it was simple! Thank you so much :)

@ustk Perfect. Thank you!!

For anyone doing it it manually, here is the code.

Thanks @d-healey as always!

Codesigning Plugin
codesign --remove-signature "MacHD/User/Desktop/PluginName.vst3"
codesign --remove-signature "MacHD/User/Desktop/PluginName.component"
codesign -s "Developer ID Application: YOURTEAMID" "MacHD/User/Desktop/PluginName.vst3" --timestamp
codesign -s "Developer ID Application: YOURTEAMID" "MacHD/User/Desktop/PluginName.component" --timestamp

Build Installer

Sign Installer
productsign --sign "Developer ID Installer: YOURTEAMID" "MacHD/User/Desktop/PluginName.pkg" "MacHD/User/Desktop/Signed/PluginName.pkg"

Notarize Installer
xcrun notarytool submit --apple-id "YOURAPPLEID" --password "App-Specific-Password" --team-id "YOURTEAMID" "MacHD/User/Desktop/Signed/PluginName.pkg"

Wait For Upload To Complete

Staple Installer
xcrun stapler staple "MacHD/User/Desktop/Signed/PluginName.pkg"

Check Status (Accepted)
spctl --assess -vvv --type install "MacHD/User/Desktop/Signed/PluginName.pkg"

FYI: Just a tip coming from the altool manual notarizing. I used to have to enter my TEAMID including my name like "My Name (GD78YHD87G)" but with the notarytool, it seems you just need the actual TEAMID Number, not the name as well.

Also, I dont think this way sends the Notarization Email Confirmation. I did a fairly small upload a while ago and have yet to receive it. I've had it take hours before, but for a much larger file. Typically it sent the email within 10 or so minutes with altool. (it does not send the email. Once the upload is complete, youre good to go).

@TNTHM There are no ID numbers that I know of (maybe they are used internally). The only id is the one you set, and can be retrieved using the getId() function.

@Christoph-Hart ok I will give it a try...

@ustk
That's true...
Even though its not the same Sampler you might be correct. As far as I know there is an AllNotesOff event, when changing Samplers Bypass.
But I already tried a different order, it did not make a difference.

I think I also tried delaying the PlayNote once, but did not work as well and lately I tried a different sample and it played, so it seems to be a quite specific issue.

I'll try to rebounce the sample I'm using, maybe that fixes things.

will try to figure out what have you done.

I've created the template functions for LAF (by right click on the slider pack and choose "Create local LAF for selection" and then I hacked around for 30 seconds...

@ustk said in FX plugin fail - works fine in HISE...:

@Lindon Is that EQ a panel of your own construction? Is it possible it simply has no data to draw?
When facing that kind of issue I add a dummy button to manually force a repaint, and a dummy label to show the data (values, mouse state, etc...) so you see what's behind the scene in real time
Could the data be in an object that is not saved in preset once exported? (in the case you save the state in a data object of a panel essentially...)

Well the "EQ Window" is showing the values for a set of Linkwitz Reily filters, so not really an eq in the sense of displaying incoming audio...so it does have some values.

I added repaint command in the init to force a repaint - and that didn't make any difference. The thing that really gets me is the preset name and the "preset browser opening" button not working....

audio makes it thru the plugin - but it has no effect on it...mystery.

@ustk thank you :D

@kameron Are you sure you are using the developer version of Pro Tools and not the standard version? Typically, this error occurs when trying to open an unsigned plugin in the standard version Pro Tools. That's why I suggest you code sign the plugin with PACE EDEN Tools and open it in Pro Tools.

Also which version of Hise & XCode are you using? Do exproted vsts work in your system?

@Gabor-K well as long as you understand the API and its using some sort of post system then you should be fine...

@DabDab said in Customize the values ​​shown in valuePopup:

@Fortune Do you need something like this ?

Yes exactly. Thank you so much!

I did something similar designing the LFO in scriptnode. I think I managed to trigger it with the playhead too.

Thank you @d-healey @orange

Both 2 solutions are really helpful.

@bendurso take a look here :
https://forum.hise.audio/post/50153

@alfaholic The samples need to be installed separately, same as a standard HISE project