Thanks so much. I've been messing with Maize and it is OK, really wishing it had more effects. HISE is cutting edge and there is a huge need for it, so excited to see where it goes. My biggest issue with HISE right now would be exporting to VST.

Hi Christoph,

Thanks for your response. I just downgraded to Xcode 8.3.3 and the same issue still exists. Any idea what's going on there?

Yeah, first time I was literally pointing my finger at the debugger and laugh :)

Very impressive UI! Meanwhile I'm still trying to get the functions down first. XDD Still, this VST itself looks pretty interesting.

hello !
si tu crées tes presets avec le standalone et/ou les vst ils sont enregistré dans la zone que tu as cité (c/users/etc. ...) mais pas dans ton projet; Donc quand tu compiles tu ne les a pas. il faudra les copier et les coller dans le dossier user presets de ton projet

Si tu crées tes presets dans ton projet avant de compiler, ils inclus dans ton VST/standalone. Au premier lancement de ton vst/standalone il seront copiés dans c/users/etc....
PS: moi je compile d'abord sans presets. je teste le vst dans les DAW et en profite pour creer les presets dedans (pour voir aussi ce que ça donne en rajoutant d'autres effets VST). ensuite je copie les presets créé (du dossiers users) dans mon projet. je recompile et remplace la .dll dans mes dossiers vst. et voilà.

Pour Mac je ne sais pas, je n'utilise que windows.

If you create presets with compiled vst/standalone, presets are stored in c/user/etc... directly but not in your project. You must copy it in the user preset folder of the project before compiling.
if you create preset inside your project (hise) it's embedded with your compiled vst/standalone and stored at c/user/etc... at the first launch.

I don't think the MultiMic concept is suitable for your use case as you can't use different LFOs/ modulators on different mic channels. The idea behind this is exactly to prevent having multiple LFOs and envelopes when you only need one. There are more limitations (the loop points must be equal) etc. so it's really only usable for multi-mic configurations (hence the name).

Just use multiple samplers, the overhead of having multiple instances should not be a big problem (or in your special case use multiple JUCE synthesisers which load the streaming sampler sounds).

You might want to experiment with the SynthesiserGroup module which basically allows to coallescate multiple samplers on the voice level which allows stuff like having one envelope for all AHDSR. But after all since you want to go full C++ anyway, you can just hardcode this structure and get the exact signal flow you want.

working also in VST in this commit:
https://github.com/christophhart/HISE/tree/new_threading

I solved it. I thought the auto sample mapper was setting the number of round robin groups for me but it turns out it wasn't. So I set the number of RRs and remapped the samples and it all worked smoothly.

for now another new problem.
i have a synth group with 3 waveforms osc (osc1 & 2 for fm, 1subosc) & 1 noise osc.
if i enable FM (with scirpt on OnControl) i can enable osc1 & osc2 as carrier and modulator controled via on/off button in interface.
if i put off the button the Synth Group is soloed to Osc1 only.

is there a way to enable FM, osc1 and osc2 with button ON, and enable all synths when button is off ?

EDIT:
ok found that the synthesizer group has changed; and i hate the new one. Definitively. deactivate FM let just 1 waveform generator ON. The old one when deactivated let ALL the generators in it playing.

Yes, but this is like this since months. I removed the top bar because 100% of everybody wanted to customize it and use their layout etc.

You can use the FloatingTile component in conjunction with the PresetBrowser, TooltipBar etc. Take a look at the Floating Tile API for more information.

yes !
i also work with RackAfx (some times ago with WDL OL) and in this case using a lot of "if" and "else if" or "case" with the functions to do.
but it's pure C++
here it's JSON.
i must learn again how to work with C++ codes in hise before doing this.

i actually make the synth in hise and the BDD Juno/Dimension-D in Rackafx.

@Christoph: sorry but i resampled it (so erased the old ones and replaced it). the new works. So the problem was the wav file for sure.

@Alexaudio : Maybe just use 4 layer and use the velocity modulator to control this 4 layer like it could have 9 layer. not sure it will be as good as real 9 layers. remember that old Roland MKS-20/RD 1000 piano had beetween 4 and 8 layers and a velocity layer to map the all 0 - 128 velocity steps. that was causing (in parts) his particular sound and velocity response for a 80's digital piano.
But maybe with your real piano it will sound as a "digital" piano. So not sure.... just an idea...

I might have stumbled across a bug but as yet I haven't been able to repeat it reliably. It occurs when I load some samples into a sampler, run trim start, then decide I'm not happy with the threshold I chose so I reset the start time of all the samples to 0 and run trim start again with a different threshold. What happens is some of the samples end up with their start time being set to the same as their end time.

I checked the latest version. Now the front panel has become active!
Thank you very much

I think your confusing AU with AAX.

AU is Apple's native plugin format for Logic, Garageband etc (although VST is also supported on OSX). AAX is the plugin standard for ProTools and is available on both OS (Windows and macOS).

And yes, you definitely need a Apple system to compile AU plugins (and AAX plugins for ProTools on macOS). A mac mini will be just fine as long as it has an Intel CPU (you can't compile Universal Binaries on PowerPC CPUs). I am myself using one as main system (I am running Bootcamp for Windows so I have both OS on the same machine).

In order to compile AAX plugins, you need to register at Avid, compile their SDK, get a iLok, register at PACE for a code-signing account, get a digital codesigning certificate for Windows from Comodo (or another company), build the AAX versions and sign them using their codesign utility which I can tell you is a very tedious and annoying procedure.

RE Commercial license, I am cooperating with a few companies that are building commercial plugins, where I offer my support during development and after release. If you want to discuss the specifics, drop me an PM.

I'll take a look, but it's possible that my loop-point importer is not as robust as it should be (it worked for my samples in the past, but there is no hard standardisation for loop point definition so there are many edge cases).

It is done! And by the way, I really believe in your program. Good continuation!

awesome. could i just replace the code in the vumeter.js with this code?