Huge thanks to David for stepping to the rescue the other day, I'm still with the master build but managed to export my first VST.

For whoever it may help the solution was either:

Cleaning Build directory before export and exporting as 64bit VST
Screenshot 2021-09-21 105944.png David's mere presence

@Christoph-Hart Can I load any odd .wav file with the loadSfz? Or does it have to be sfz and sfz-only as the name might suggest?

@DabDab Great👏🏻

@ustk I mean with out modifying the source code.. is it possible in HISE only with Java Script? How?

@d-healey Wow That's it man! You've nailed it :) Thank you so much!

@ulrik Ulrik, Ulrik Ulrik you are a genius - great - looks a lot more complicated than mine but it works.

There is still one small problem.
It is possible and leads to the unloading of the sample if
the user sets the start knob to 2000 samples, for example.
and the end knob BELOW 2000.

Basically, the start knob can only go as far as the start value of the end knob and vice versa.

The two values must never overlap.

Another thought experiment will be that a call of the samples via combobox will fetch the SampleLenght - i.e. already outside the inline function.

@d-healey The Age Friends, The Age 😁

@d-healey Yeah! Will try this! Thanks David!

Or just get it as a child synth and use .asSampler() when you need to access sampler specific functions.

@gorangrooves I use zipped pkg files, it works for me. I don't see any reason to put the pkg file inside the dmg actually.

@ustk Interesting! Thx for the nudge! I’ll do some digging and eye-ball-bleeding myself and hopefully come up with something. Thanks a ton. Always helpful! Appreciated! 🙏

@d-healey Nice. So I've been testing the install and for some reason the new expansions are showing in the plugin a few moments after installing, presets and samples all seemingly available and working - so that's good!

EDIT - I think I figured it out, I have the Preset Browser set with the expansions column active at the moment, and the expansion appears there a few seconds after the expansion installation. So perhaps the refresh does work after all - just not quite how I wanted it 😆

@ustk said in set up complications...:

@Lindon Hmmm... Yes, this is what I mean, but I'm not sure there is a "timing" involved. It might something else that makes the detection to occurs too late, only Christoph could answer, I am looking at the code but I'm pretty sure I won't be able to find anything...

@Christoph-Hart - can we have a loop that goes around this a couple of time - to account for different drive speeds - and thus reduce these false positives?

@marcLab you might come unstuck if the knob's ranges differ. I'd be temted to go with a seperate panel for each effect in each slot which contains the relevant knobs etc

@Lindon You're confusing me again, you have two interface scripts in your snippet both with two slider packs...

This is probably the simplest way - using two global data objects that are assigned to the linked slider packs. However I think it should be possible using setAttribute but currently HISE throws an error saying you have to pass an array, it throws this error even when you do pass an array.

HiseSnippet 1440.3oc6Y00bSaDEUxNKSrA5TnLc5iZxzGLCTOxl3DxvzAm33jFZRjajgzY5CY1Hs1dIx6JVs1foSmxOv9P+IvOAdtuzdWIYKYPXLlvP4C+fGu6du28n6dt28DkVBtCIHfKzzKzdjOQS+RH6QLYuF8vTl1daqo+sn.OpKQ3icNyvixNyPRBjZaMxGGDPb0z0yuqxV8BKoE94E2cKrGl4PRlRS6AbpCYeZepLY1V0+Ypm2NXWRaZ+TVuZ88b3rFbO9..W4QlZp8F2kbHVYVNjl9EZ5RkbgsDCfQSeos3tir6weLKx9GPCnm5QTCpnYCAJZ5c3dtJDqlUqQOpmaqwO+AZZ5nVIYi7QYiqgNf5RmLeRV4qCWvHwiz4C8byBdUdyvyLK3kKE7PQv6JHaGA0WlrhBaEP65wOE6ELEnNbPe6vCxVPxD.EROOjqi7WK2U0QcCcxn6ItXIthwOZzj0kxHkcDD3wXSl6Qjtz.IQjDlsAKKU452o3T9Vc98s50uSmALGIkyL3rC4RhEqz0K96EKT7OJZ7xK0oSlq0fyjBtmGQj4xJxkXVNVhMn+oDwMMFh8FPlXHbtM8w3EluiQf6JILYJC4r8XTokOId7r4gZMhB.7q6umJKAm85wyA14SDRpBN5aSFBEUQLgBnsIAmI49PY0bRStHZOHlhNXnRc1DkboHJ+kNJFKk6iOiri.FLINkVyz7lF0LMAJQQHODHgbpv3k1cE2JrIS4tD4T0WkVIxzj5pJqLcnTXxlHg8SEkwHAhSCdeeNCFTZkT1n7NKmqNGNWMbqSErxBRGhnMOj4FWl.ljxiLr.X3E+3ghiNun3yhVqmKFUv1KCInWMlflv6zn.W7xnTYesPnqniWBBlJ0po+an0Vsbiis723ozsNdU3W26gV2p1uzciV26zaWSMdnU6aUaya7vsN1Zcaq6cZfE7kyFOc+Q6upMXDy51rgMuw1R21qaCt9XqtOZ2l2nbDdeKAY0DPpMMHI.J1nED50TfRXI1sobi8gsulM7EKBTqyFZtpBDbKExhdHn.9Br.mVeiNPPVSA5gVGAgRAxEoCgJ+Gy20zW9s3D3II2Qua8QSF7rCq6iEPzRE1KiRhTUsGSck8lX+y+y58Hzt8RjB7rGTOw78XtjmnRgg4vEBpUSA0m0LETeN48CTyEpmIow6RQ4bPk.2cfGVNszAkdo3EfpzoZ9pZkxBnxQo0S8Vnmvbtk6Luv8JnVToSurwatLvqp.+8LdiUmcYTyNcHNxDvtDZmecQkhsXPY4Wir4KEdMILRU3bNHV1etEKqm+cTbr4Gghi0eU1b1pd9FzqHwXJ3MVmSqDcNAD4OE1DnT0zJaB77SqAA65lzXnzJpUW4lFfbHyIZPf4pNSOpBdTsVrOEUg30n4PYa1hM9hViESqwEPpz8+WEYDhtOBUWflmb9SF+DMZ7OlCw.n4IeE54+7Fh7Wt69y06t+pHnbQjMbMc382wuwK0XiiwCIF6RfKvUI0YcI9ee9eItkiD191BLKvmGLUfsI8osgpffzSd+.3OEm7niTmxomuAGKxboWb2cfGxL8wFKGHBoKa1mOfImhdj+c716LeyaK8APbw4e016dyg7yGbeC5eJLFi1z99djlrgDOnscHFuJzmtCdfmb7rSyqOfy3983LpS5C8iHRAsaWhHM1y7AZSoT0BdxLWq9QDOBNMA96quOP7vBHOQVvbQk4OWLqyquCEAWCUwnwmFM0y+4YS8i3CjTV2Cv.QUcot5cXB8RcH.RXLh2jWiY7XyI5AHL2vA+K7IdwJi0anVrx3E+jYO5icD7SbhDdppWVNbFH2xB++qT.cfZrQhXXjYYSs9PW2SbbTGo+.bFjsOUW.et0B3ypKfO0V.eVaA7Y8EvmaOSeTW3s4.IueT4NLQqlgBy00axvP0RXkk1+gHkQ57

@d-healey 😢

Ok understood. Thanks for the explanation.

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