@ustk Australia. English. I am waiting to hear whether he has any alternative languages or keyboards set up in his system.

@d-healey said in Codesign error on Mac, what am I missing?:

https://youtu.be/PhhOw3PRX_w

Yes your video helped me out a lot previously setting up my package installer, really appreciate you sharing that.

I still don't know why but I was having one hell of a time trying to set up my certificates and getting it notarized, terminal kept failing me (not acknowledging my ID's specifically). In the end these two videos and their extended links did the trick for me:

Certificates:
https://www.youtube.com/watch?v=m097IHT7v0Q

Notarization:
https://www.youtube.com/watch?v=GpdN97OX1Z8

@Mors the notarization video may help you in stapling if you still haven't solved it.

how do you assign what parameters are modulated by P1 and P2? is it just parameter 1 and parameter 2? It does not seem to work for me.

@Mors Do you want to make A SidechainPlugin?
Like Kickstart? LfoTool?

@Christoph-Hart thank you i try it

@Christoph-Hart @bendurso yup thanks that did the trick!

..and supplementary question:

Can I store this in a panels data?

@Lindon what you do with the data is entirely up to you, you can still change the values by index even post-launch, but yes, the question is where and how would this be used other than for the voice start as script envelope doesn't care for event ID i.e. there's no code callback.

Would be great if the script envelope had some sort of process block callback where we can override the scriptnode part and return anything like with the voice start, except if we could query for note id, it opens up control over polyphonic modulation over time.

But yeah, back on topic, in your case sounds like you don't need polyphony so you can just pass artificial CC and control pan that way on your separate modules.

@yall What do you want me to do with that?

It makes no difference to the volume. Full dynamics = 24bit

@bendurso thanks,

@BWSounds

Settings.setZoomLevel() - 1.0 equals 100%

@d-healey said in Compiling macOS Components and VST3 Doesn't Put Them in the Project Folder:

In a recent commit of HISE Christoph removed the copy step so it should no longer be moving the plugin files automatically (although this might only apply on the latest MacOS version I'm not sure).

I can confirm. I'm using Sonoma 14.3.1, and the compiled plugins are now located inside the project folder. That was a good surprise :)

@Straticah said in I got a bug report for my plugin from a tester:
and the users could not use the new vst version with their old projects.

-- this case is exactly what the pre and post preset callbacks are for...

@d-healey I had some troubles saving the XML recently too (but not this warning)
My XML was saving 2 or 3 levels above the current project folder.
I reckon that I had to delete the pref files in the the Application Data folder