Alright, I want to post some useful info for anyone else that may encounter these issues in the future.

If you find that your plugins show 0 bites in size once installed into default system directories, or that your app won't open, it means that they don't have the right permissions set. On Mac, each plugin is not a single file like on PC, but rather a bundle consisting of several files and folders, which you can inspect by right-clicking on your plugin and selecting Show Package Contents.

The reason why your plugins and apps may not have the necessary permissions is if you compiled them on a network PC. Because of the different file systems, those permissions are either not written on the PC during compiling or are unable to be copied over to Mac.

All files and folders inside the plugins packages need to have the correct permissions set in order for them to appear as plugins and not empty folders. The source files need to have the correct permissions set in order for them to be properly added to the payload inside Whitebox Packages.

Since plugins on Mac are not single files, it is not enough to simply change their permissions. Permissions for all files and folders included in these plugin packages need to be set correctly in order for the plugins to work as single units.

The correct permission are 755: Owner (R/W/E), Group (R/E), Everyone Else (R/E).

A quick way to set permission for all plugins you will be using in a project is to put them in a single folder, then set the permissions for that folder and everything inside it, thus affecting all plugins and their internal components. This will need to be done using a command line in the terminal.

To verify that the installed plugins will have the correct permissions and therefore be usable on the destination computer, do the following in the Whitebox Packages.

Right-click on the plugin you added to your payload and from the popup menu and select Expand All. Click on each of the newly visible folders and files within the plugin and verify their permissions. If you are missing read/ execute permission for Owner/Group on any subfolder within your plugin, it means that your plugin won't be installed properly, so you will need to set it. The best is to ensure that the source files have all the necessary permissions set so that the permissions will automatically be set inside the Packages as well.

https://forum.hise.audio/topic/469/global-pitch-modulator-problem

On my side I simply use Pages on macOS

@orange Thank you . You explained very easily. I got you.
Cheers (y)
:)

@ustk Excellent, the joys of source code :)

@d-healey I will come on this thread after one year ;)

@ustk Ok I see. I'll mess around with these to see what comes out, and I'll post the result if I can come up with something nice.
Thank you for your help, I really appreciate !

@Lindon said in EQ Effect plugin - that generates a test tone:

strange - because it will compile here...it just wont make any noise...

Sorry, I mean the sound generator won't be embedded in the compiled plugin, it is simply ignored...

File.loadAsString()

@ulrik "aint got no use for no stinkin flats!"

@Christoph-Hart I agree, you have to find a balance and should always aim to make the code readable, even if that means it's more verbose. In this case I'd go with the two line version, but I'm used to reading code like this so my vision might be skewed :)

Okey It Was Pretty Easy :)
Here is The Code If Anyone Intrested

HiseSnippet 1372.3oc2W00ahaDE0NINpPap5J0e.V4IhxVKrg.DsppKeX6P.CrXBgvKqL1CISv3wXO7UVs+c6y8eP6L1lfgvljFoVoVmWxcN26cNyYl4dGZ4gLA99HOF1DcV5BXX+AN8kN36JemAzgoZEF1ejSyvGC73CGpzRWCeefECK69pzAXSb.Sv2e7akLrMbLAqGhgoKBZBpCGCwqGs0GqAssULr.cfii4c1OV0D4TFYilR3y9boYbMLGYbKngA0s83XXOT1BhQd5XCLvm3SIj0R86PycB8uKzGNvFPMDYzIIJbXlx2AssZsZs5yvvdPq0q78CW4+LmFzB933qUfeJ.fecDw0.181jRGrAkD+VTRAYaQSv2fdrwn2Agz6cb5ldPW7ZDJ29dtpNjMmgFDYONsB8kYue+.txHhGNXgwFi.JdDiGiHknTg2yKU3jObTxiRRzdeL+LCOd84Ft7+J+p.uEfKiF6hbHFoNlBd71QnYf8fKDIAEb5gFh7vg.Sh+QPAgrc.Re6.jhli3A0AQn0whmKJjAYdsF1qToxkqHaVZzkYJc50dMyq5bk7faaO+h6LlnUVTHc81sur+omkth+UWZ1USswfoRkzt5VkxnhcmgvpWLyV05999YDqMCm1pO.cUMfbwaLadolRGg5cEp0C1peUMot8+DrVekpmkI8C5ix0rdoF0zVLQKSyg5Z2epQUgroWn7o4ytWQP3ztsS6CfBdxp8mtD00T195qc6zCNIeKw5yTKTa5CKaTIiS67xV4vV2b+3aJrvo5hLEEqAUcQWaWuqc8N5Sqa5U2rs+DkZmVdlpfdN2B0NdCsrDBiQiioLM1VY5O4rlC2VYFcemGNO8jpEJ14Lu9MFzyNmlttry7V8GJOXhuRQwEylzAJ27bgF9R5iW52OqTudWaXhmOrzv4k5UTsR6ZnrhCp0evXLrhe91mAW3qpTVZjR1kW5oloibVo6DtvuS2pKTfOHHjYYaWqzpkl00DkUab+Gj60+Fb6auBOVcQWgy0yk4hl4ZMDd4mTyuTq7hdMWpb+7k2WE5QDEcrk6fB0yZiVnAk60Ba5NHWuhCOMyz7QJS3ePGanCfe3TGSLD4vibnmbomo8P1oLWcf98DIzdJ3jiR9kiRl.NjO0Jadx2W34C+G5WzIYAOfO4BOH3FeJxYxS9P.71NJsoig6RQ9F35WCi.X6ChlsWXtVmhWXtdjTqlmuFHKO2EZAe5fAhSYCa6AjJuo1PxnWGiIlMPXPSmTmj7KISj7qI42FZ3vchEkLaf2NgoMD7dt.S4Lc7.f2pcsUNRpRtYY3CeckgMCUjXNhbp5.wMcAQ1qKTKtiB0LQRJsjcDCIthCJX+iQErKMkrq4v.II4PNpfxDv83MNYtpZECrwprPRHYRbAdXHcsvVALizEMrMPBtJ.+QXjafuQahjk+KMmKh2UdYbClm1qgzwCYM01.uYaPZ+9H.xlxF8an8Tb7g3kwWV+M5Mldm8F2oj+Jo663ZAwl2sa9t2N3KQ8+mluQuz3HtvdcqI6AbJ89W3YE68TtjfqMZJFPldJORvEU3YSxr+y8rKwW+ytXnyEz41vIgHDMlNVm7ZOS.QJbbHUBYX4XOjduJzNM0lt0nCbrBL9SxWDnH0lMBTbKPoU1TPoUoIBLSbvLqRSDX13fY2JsmEG7QClWqtJ8+PcMF3S00XfOUWisi7TcM.8+lqqW97xXCSOzmMC6XPuY9cAiP1ecB9sNzyKDadwU8J33RKjlYL42g7YSSZ8hegTqY2wH8FhIyaHlrugXN6MDSt2PL4eCwT3Yig9S.KNk77qvdIjAZIGzylkU1wfbKM3FMyeA9k+bE.

@d-healey said in Problem Knob Range:

@MikeB

That this is not the case in HISE! - that is the problem

Oh there's a bug.

upps :-)

It used to work. Although it does work if you hold ctrl and you're already moving the knob.

on Mac with option - it works

@Christoph-Hart Holding shift now activates the text input box even if show text box is disabled.

on Mac it works on shift and klick - but It is not practicable with some values.
For example, 2.3 kHz is displayed - if I enter 200 now
Nothing happens. If I enter 1.5, it jumps to 1.5.

@Natan No idea

@UrsBollhalder I think external filters should simply be connected the same way we connect a filter module (floating tile in filter display mode, set Script FX processor and index)
But as soon as you set the processor and hit F5 it's an instant crash... @Christoph-Hart ?
Perhaps it should be used as a display buffer but I don't think so...

@UrsBollhalder Yes that's been on my wish list for years

@Christoph-Hart Cool thanks :)
In this case it's for a value -> HISE_PANEL_MOUSE_DRAG_THRESHOLD or something like this... Currently set to 4px, but I always use 0.
Or, a bool, like HISE_DISABLE_PANEL_MOUSE_DRAG_THRESHOLD might be good enough, I can't imagine one wants to set it at 50px 🙄