Does anyone here have experience optimizing the CPU for the convolution node?

I have a product out that uses it extensively and the user said the following about having CPU issues with convolution based products

"This same thing happens with one or two other IR-based reverbs (and only with them). However, it seems fixable. For example, Korneff updated their Micro Digital Reverberator awhile back and it finally uses low CPU for me. The other culprit, which has improved but still isn't usable at 5+ seconds decay times is Transatlantic Plate. Reverberate3 has zero issues."

I know the developer of Korneff Audio uses HISE as well so I'm guessing there must be a solution around?

One thing is that I had to disable multi-threading on the convolution node for Windows because we had reports of crashing in Windows on Cubase with it enabled. Curious if there are optimizations beyond that though.

@d-healey Ah, that's the issue then! I have it working now. Thanks!

@DanH I appreciate the pointer!

I actually just figured this out with a google search and some trial and error. I'll post here in case it ends up helping anyone else in the future.

Instead of copying the whole folder I single AudioResources.dat file and created the folder with the installer.

In the "DestDir:" I used the tag {userappdata}. This allowed me to place the file in the expected located.

@gorangrooves Thanks for the detailed help on this one as well!

Just replied on my other codesigning thread and you definitely helped make this all far clearer than it was 48 hours ago!

Answering my own question here as I uncover the mysteries of HISE.

On macOS holding shift while setting the routing will set the send cables.

I'm going to answer my own question for anyone looking this up in the future ...

• There are two options for iLok encryption. One requires wrapping a binary that HISE creates and the other requires injecting custom code in your project but is more secure.
• The first option should easily be compatible with HISE and the second one I'm not so sure about it.

Likely we will end up using the first option and it is positive to see it should be possible.

Hi everyone

I am just at the tail end of developing several commercial products using HISE, an instrument and a line of effect plugins.

We have been fortunate to work with a great team for the core development and are nearly ready to go to beta. With this said though I could really use some help on two very specific issues which I have been suggested to reach out to the forum about.

1. Building AU, VST3 and AAX plugins for macOS and Windows. I have successfully been able to build AU on macOS however I have no experience with Visual Studio / Windows and haven't been able to build VST3 or AAX on either macOS or Windows.
   I have a dedicated MacBook with macOS 11 and Windows 10 installed just for building plugins. The idea would be to set this up once correctly and outside of critical updates leave the machine as is.
   I've searched the forum and followed various posts but still no luck. I've been getting various errors each time I've tried. I'm not sure if it is due to something in the current build of develop or something in my configuration.

2. Creating scriptnode effects from C++ DSP. We are working with an experienced DSP engineer who doesn't build GUIs. I would like to create a scriptnode from his C++ source code, or clearly explain to him how he can do this, so we can build a GUI around them using HISE. This would be for both the current projects and for future projects which are being planned.

One of the main reasons we are using HISE is that it makes communicating on a cross functional team including product, visual, UX and sound designers with developers and business stakeholders far smoother than a traditional JUCE build. In this regard it's been an absolute game changer and we've loved working with this platform.

At the same time I feel lost following along between the often out of date or incomplete documentation with browsing various forum posts which are also not always current. I have 10+ years in the music tech industry as a product designer (at companies both large and small) and my preference would be to hire a professional developer to consult with experience on both of these topics to ensure that I set these up correctly and in an efficient timeline.

Alongside this, we are also looking for someone with experience building custom LAF GUIs from Figma documents with all of the DSP being provided as wrapped C++. If you can take a vector based document and have experience turning these into HISE based UIs with animations and dynamic changes please feel free to send me a DM!

I'm also happy to discuss these solutions publicly as I know this information could help others and discussing on the forum does seem to be the HISE way. I would also suggest though that a tier of professional support for developers in our position, where time to market and stability is the top priority, would be really appreciated and something we would be interested in if it existed.

Thanks in advance for the help!

@Christoph-Hart Just rebuilt the latest commit and confirm the issue is fixed here. Thanks for sorting this out so quickly!

@orange ah, ok! Thanks for the help and that makes things clearer.

@Christoph-Hart this would be a great addition for effects to add to the backlog.

haha yeah! I am definitely more than a little addicted and I've been meaning to check out NoiseAsh plugins soon. I know a few people who have been raving to me about them. Great work on making those if that was you. Totally blew my mind when I realized those were made with HISE!

@orange Again, really appreciate you helping out here.

Your steps did work. I followed them exactly and was able to build an AU which could be loaded on a mono track as a stereo track.

The issue I see though is that this requires having two separate plugins and what I was hoping for was a single plugin which could either be loaded as mono, mono to stereo or stereo depending on the track type.

In my experience the only company offering separate plugins for this behaviour is Waves. Most others have a single plugin.

From a user perspective this also causes issues because AU preset data can't be copy and pasted between the different instances and the preset folders also won't be shared between the two.

Attached is a screenshot of TSAR-1 by Softube showing the type of experience I was expecting.

Do you know if this is possible with HISE?

Thanks for the replies everyone!

We're getting quite a few reports of poor multi-core performance and I'm guessing this is because I disabled "Enable Multicore" on the convolution.

@Matt_SF that's quite interesting you experienced crashes before IPP was enabled. I have IPP enabled in the project and also built HISE with IPP enabled. What did you do to resolve this because it also sounds like my issue.

@Dan-Korneff what do you mean by "wrapping the entire DSP chain a fix_block container"? Is that something using ScriptNode?

Does anyone here have experience optimizing the CPU for the convolution node?

I have a product out that uses it extensively and the user said the following about having CPU issues with convolution based products

"This same thing happens with one or two other IR-based reverbs (and only with them). However, it seems fixable. For example, Korneff updated their Micro Digital Reverberator awhile back and it finally uses low CPU for me. The other culprit, which has improved but still isn't usable at 5+ seconds decay times is Transatlantic Plate. Reverberate3 has zero issues."

I know the developer of Korneff Audio uses HISE as well so I'm guessing there must be a solution around?

One thing is that I had to disable multi-threading on the convolution node for Windows because we had reports of crashing in Windows on Cubase with it enabled. Curious if there are optimizations beyond that though.

@optimistic Just wanted to chime in again and thank everyone for this thread as this did indeed work.

It would be useful if HISE either added this feature in preferences (as it can with the AAX categories) or if there was even just an option to export to Juce. Never built the plugins from Xcode and VS but was surprisingly easy to do so.

@d-healey Ok, thanks for explaining that. I just checked it out and quite amazing how much is happening under the hood now.

I'll give this a shot tomorrow and see how. I just had a look at the Xcode project (I can't how much is in this project under the hood!) and will do the same on VS tomorrow. Less familiar there but hopeful I can figure it out.

Ok, interesting!

So you start the build from HISE, cancel it and then you open the projucer file manually and how do you export from this?

I’ve only ever exported from HISE so do I do this from Pro Jucer itself?

I also am building AU and AAX so I guess I should let everything finish and then manually do VST again. Would that make sense since this only applies to VST?

@Christoph-Hart this would be a nice addition to add to the settings of the HISE project at some point :winking_face:

Was just looking for this same answer. Thanks for posting this!

Even more basic question from my side. What Projucer file is this and how do you get this to save?

The only .jucer file in my project is in the DspNetworks and it is called “AutogeneratedProject.jucer” and editing that didn’t work

Could anyone point me towards which file should be edited exactly?

@Dan-Korneff Thanks for the quick reply and was just coming back to report the same thing.

I ran a test build and was surprised when it actually worked. Looks like I needed to rebuild the script as you suggested.

I have a tempo sync knob in a project and I'm trying to have it's default (double-click) value return to 1/8 but it keeps going to 1/1.

I have tried both "1/8" and any value other than "1.0" in the DefaultValue parameter but neither seem to work.

Does anyone know if this is possible?

@Christoph-Hart ok, will do.

Is the process as simple as building the debug version in Xcode and then getting a log somewhere?

@d-healey Ah, that's the issue then! I have it working now. Thanks!