@dustbro Thanks, I saw some of these, but I thought I´d add this anyway, since the issue has not made it into the documentation yet. It should be included in the documentation on the main github page since you cannot export your instruments without it.

@Lindon What are you trying to do?

Thank you, I'll test this further!

@ustk Thank you for help :)

@lalalandsynth i use them both in a rompler i am building - though edit panels for both can be opened manualy, the pop up solution of @D-Williams23 is elegant!

1.png

Discovery of the year: you can actually run HISE as sudo! It builds fine then.

In standalone I think the number of outputs are limited by your soundcard. Use the plugin version to access more outputs.

@Lindon Thank you
@lalalandsynth It is working for me. When I first created the Synthesizer groups I was getting clicks on everything as well. But after compiling, saving, and opening it up the next morning there were no more clicks. Weird.

@Christoph-Hart totally missed it, thank you!

and when I do

saveAsMidiFile{PROJECT_FOLDER}

on a compiled vst I dont know where the midi file goes.. should I change the {PROJECT_FOLDER} part?

also going to try it with the commit you sent.. im using a comment from around 30 or so days ago

Nah it's something that should be addressed on the engine side. IIRC I did some work to remove clicks, but they have appeared to slip back in somehow.

I'll add it to the tiny TODO list.

You can grep the codebase for USE_IPP and see where it's being utilised.

The main advantage is a fast FFT for the convolution reverb, but there are a few other places that use optimised routines.

@Christoph-Hart makes since. I will give it try right now. Thank you

OK thanks guys. - my worst case is (I think) needing 30 voices for full polyphony and my buffer settings are at 4096 right now _ will see how I go.

simply delete the folder in library / application support / (your company name) / your plugin folder

Try it and see :p

@d-healey Perfect. I was close. I was thinking something had to go before the ".substring" Thank you sir!

@Christoph-Hart indeed stupid thing. thank you :)