I don't think it's possible, but white goes with everything :)

@d-healey Very cool, thanks...

@d-healey 👏 👏 👏 Thanks...

@christoph-hart just compiled mi first .exe VI and the trickiest part was to figure out vst and asio sdks should have the exact name you posted on tutorial

@christoph-hart How do you install xcpretty?

I tried compiling HISE on another computer. The build failed in visual studio, but visual studio ended up downloading the correct version of the Windows SDK.

I tried using the latest build to export as FX, which made it further than the previous attempts, but still failed when it could not find the following

Could Not Find C:...\Plugin Development\HISE-master\HISE-master\extras\demo_project\Binaries\Compiled\Demo Project x64.exp
Could Not Find C:...\Plugin Development\HISE-master\HISE-master\extras\demo_project\Binaries\Compiled\Demo Project x64.lib

Do I need the build from visual studio to export properly?

thanks buddy

@christoph-hart i understand what the user presets entail i have dug around in the files themeselves obviously its just stored parameters. but i have it figured out. and example is the main one we were working on, when it loads it is on the mix page etc. i simply want to make the default preset be starting points for everything. but the loaduserpreset seems to do that. as long as when the plugin is recalled it doesnt revert to that preset it will work

I see. I hope Player will be ready some day, it can be a real alternative to Kontakt.
That looks like a lot of work, if you are the only developer of Hise (why don't more people contribute to the project?)

Meanwhile, is it possible to make a sample player using Hise, like Sforzando?

@christoph-hart Thanks for the info. I have not been able to find the CLI HISE app? I have built HISE STANDALONE but I can't seem to find the HISE makefile etc...

Set isPluginParameter to true and give it a name using the pluginParameterName property.

Hahaha me too!
It's ambitious for people not really used to code, and compared with some others, HISE is far from the simplest VST creator ^^
So instead (because everyone here is yet very busy with their own code), you should have a look to Maize Sampler 2, very fast and simple to make a sample-based vst, or SynthEdit which is just a paradise of simplicity and unlimited creating tool for everyone, for synth-based VST.
But at some point you will realize that other editors are not as modular as HISE - since with HISE you code your own things how you want them to be.

So maybe start with lighter, and then get ready to lose your hair xD
What's your VST about?

@lindon Yeah use an image :p or a panel

@christoph-hart yeah it sounds the same im not sure if it was @d-healey or one of the other very active members had mentioned something about this a few months ago and said using a different VST sdk fixed it. an older one i believe. but i cant find it in the forum anymore. i believe it was using 2.3 and not 2.4 but i dont know where to get 2.3 to try

Ah, well, or, instead of adding another hardcoded path for the waveform generator...
you could probably draw your own waveform in the already existing wavetable synth? :) (I just found it...)

0_1529605862782_Bildschirmfoto 2018-06-21 um 20.29.00.png

Master Chain + -> Wavetable Synthesizer

ok i can paid somebody to do that...
do you know where i can found this developper profile?

@aombk For some modules like envelopes, EQs, etc. you can add the built in modulators. If it doesn't have the option for using the built in one you either need to write your own module or modulate the parameters through scripting.