PresetBrowser

Alright everybody,

it was time to finally bump the version and upload new installers. Enjoy

Hi everybody,

I'm currently profiling a project I'm working on and noticed a rather significant optimization possibility: when there is no signal input, some FX can be suspended until a signal is detected and save some CPU. This might highly improve the idle performance of your plugin, which is important for big DAW sessions.

This is not a new idea (some DAWs implement this already) and in certain parts of the HISE codebase this is already implemented, but now I refactored it to a general system and also allow DSP networks to set the flag.

HiseSnippet 1427.3oc2X0raabCDlqrobkSbRSQP+AnG1C8fCfqgTRZZAxAKaYqTgFYK3UwMsWLn2kxhP6RtkKkrUK58donmys9Zza8Qn25w9J32f1gbWIsqzZAaE2DzJCXHNbH42Ly2LbnZIEtznHgDYUp8vPJx51XmgbU2ZcILNpwtHq6faRhTTocrncFFRhhndHKqkdlVfUokQlOWr0NDeB2kNQDBcjf4ReNKfolHsU0uh46Wm3QayBRo8iq1vUvqI7E8A7rDtLJj31ibJcehVsBXjUw87XJgzQQTzHPmcDdCc5JNiGq+QrH1I9T8fJHGXihEip0k460ZjsFgPV3VSr7khs76iax7XikOwC7tlIrmrhz9.qByCRUtFPxJEjVNFR2C63JYgpIynwysvM3P.oCAb0ogRrtHqeGWS.JvUaFP5QqKgAiWv5Oob4Mrg+8fm1oO2UwDbaAeeghd.e8Gr5OrZoU+wUsmdpNcxcN8wHE99TYtSqitx4sv048CNgJ2vd.wuOcrhf4m0mV7p4Scis5TJJ3M3L0Agzjw0E9dZek96yFAPItM3aunwtDEQGTRjA5ERkJlFNV6RG.r53PTI7tzndJQHvqmI9ALGgWeehJKcRm2jLA3OxDC0AJdDSMLcd00fiUdtbrqJDuGtES41MeLVHGLBdp+MvXRl4Z385zg5pl.vkw0e4hlFV9ZmFtZRZHbl5C+1ICsq+xJ4l.9S3Ij8PIMjHosEs7ICWOhDD5SODv3F1m3Kb64v9d5rYHgwPXGsFq61kv4T+nEIQp3MTwIzgh9JF+zlDkjcNT9b+9ANPYZWZsDzAxrJnyghGWVOVyKbnbOyf+F9jLYE8XqjIqLZxToe6SUmIj8LgijuirVI12GYbxG247Jns88EmUSDDxRXoPLvHqkveXXWAm4pEEqwHjtcfnObHIv8KIQsILeMs1oeDTnv6.tCnr4ZLqBGQkQlMdEb4Mg+.Z99BOXph0ItficXKhpqNeQW6AHmT4ltiIoYvZZdhdKFcMWrWBfXf1z0WxoiOsHR3NOnlstbSAqkRU9IlgpGA4eEhOmFQGom0k3iNRy.zKBoOkXOnAwXspqg6vN+QO7XC2CkwF9fT1PZkt5.+0ClERAy6iiBDBUWp2wgi7DYQ6GaPKP82LGMuwfbQcwQ5HvtF94f2gHsODxhQnIUGaSjmRUQIWWvotwjQiE0vSuMJBuKZbPUKaEb7thREp0vYrQXsRSFO4jmTlsI47ojcwVNJZntNRZ8b5QOK1gkVSsMM5fmYq2tuRD.0IL03Qo.Rwo.xu9pW8aaMCPp9KUmBHF8tbfbWriIzAkUL8ANEf9lpyCCWCmwEyACkv6wIPEPOzLaDJEe7tXw.H.YJdW4ImmkJ9QoRbxp1apTmzY3IbsLH7VXHt1cSyDWCLUHMlxxSslOO8hYoGnpUuQ3oWr0kvSmFiWNfKFu86JYCnna9jrwK8a8d5ecvO+maktpvkWjH2Zd4WxXGgnW.wb+3qcmp2Idxagc.Br4oel6tdeyX6ulLfZ+LJPs0MHVYNu96Otpu9K7J+5uCbUvw2VR3QghnrddZ.qsfqswIBeQD7XG52cntlbZ40DDYtScwV0AiL203PT8klh6i5WHUqtKksqpkuZcUksq+T5mSSnK+V34o2LOc3s3qaxz5doQXzgoKGuGe.0GRLLX78fLgNj99pQRyRraJ3hQcONIpeHEZ88zSoYKTkmAssRQfFmFK49UOj5SIoYveR03VILsWrX9hq+ulPtwqODGCWac1n8+ceU5R+u9UouQd+0ahyHf3JEGmz6tlm9NFIfcyM+HekvM0isqfFDeMJV+vKT.Tg6XWWsK9SgBl4ulGt.q4QKvZd7BrlOaAVySVf074KvZ9h4tF8kKIsboS4.As1yzxgk0ndmAlN5eLgWzyA

This is a simple overdrive going into a 16x oversample node. With the new SuspendOnSilence flag enabled, the CPU usage goes down to literally 0% if there is no signal present. You can try to disable the flag to check the effect (it's in the DspNetwork properties, next to the AllowCompilation and HasTail properties. The flag will be passed to the node compilation, so the HardcodedFX will inherit the behaviour of the network.

Be aware that this flag should not be used if your algorithm produces any sound from silence (eg. a test tone generator or a background noise player), because it will obviously mute the output when the input is silent.

You can also see the suspend state in the Module Tree, if a FX is suspended, it will show a S over the peak meters like this:

I've tested it rather thorougly and tried to cater in all use cases (polyphonic FX will also be suspended if the voice is not producing any sound), but please let me know if you find any issues.

There's also a preprocessor macro in the hi_dsp module (HISE_SUSPENSION_TAIL_MS) which defines the time that the processing stays active after the first silence detection (the silence detection is pretty sensitive, so it looks for a -90dB threshhold), if you prefer a different default value, let me know.

In my project it yields a ~40% CPU improvement in idle mode and ~10% CPU improvement when in usage (because some channels of the plugin are not always busy). I also improved the performance of reading the peak values of routing matrixes, so this might also be a contributing factor though...

Hi everybody,

I'm very thrilled to announce that the Faust integration is merged into the develop branch and ready to test.

The implementation of the Faust integration was a Google Summer of Code project that I was mentoring together with Stéphane Letz, @sletz from the GRAME Research Lab. The project was carried out by @etXzat which I would like to introduce with a warm welcome and I'm sure he's happy to answer some questions about the process or anything Faust related as he knows much more about the actual language than I do.

The Faust language allows you to write DSP algorithms using a very concise language. It's been around for quite some time and has a lively community of developers and a vast library of existing DSP algorithms that I know all of you are dying to play around with.

The current state of the Faust integration allows the full production cycle of using Faust within a HISE project:

• add the core.faust node
• write / import Faust code using the LLVM Jit compiler. Parameters will be parsed automatically and show up as node parameters that can be connected / modulated like any other parameter
• export faust code as C++ nodes (a DSP network with a faust node will create a C++ class from the faust node and use the C++ class instead when you export the network to the DLL)
• reload them as HardcodedFX modules or nodes in scriptnode

@etXzat has written a extensive blog post about the integration process as well as the build instructions and a quick getting started guide:

By default Faust is disabled in HISE because it requires a few non-trivial configuration steps and let's be honest, HISE isn't the most easiest software to get started with so there's no need to make it even harder...

So if you want to dive into Faust development in HISE, make sure to read the build instructions on the blog post and let us know if there are any roadblocks (we've been testing it on all three platforms the last week but I wouldn't be too surprised if we missed some build issues).

Also we would like to start the discussion on what steps should be next as there are quite a few features that we couldn't realize within the projects timeframe but hopefully will be added over the next months:

• support for MIDI and polyphony (at the moment it's only possible to use Faust for audio effects)
• enhanced IDE features (editing within HISE, SVG path diagram preview, etc).
• support for complex data communication (tables / slider packs / audio files in Faust)

I've also added a new category in the HISE forum for anything faust related, so that this topic will not explode with all kinds of different questions.

After what might be the single most offensive violation of the git flow branching model in the history of software development, I finally found the motivation to merge the develop branch back into the master branch, which had a pre-pandemic state.

Also from now on, I vow to respect the traditions of software development:

• keep the master branch stable and build at all times so it can be a valid entry point for HISE newbies.
• use the develop branch for testing new features / daily development work.
• whenever I merge the develop branch into the master branch, I'll run a CI test that ensures that it builds HISE and exports a test project on macOS / windows so that @ulrik can stop being my human build bot for macOS and notify my that I broke macOS again... I will also try to bump the version numbers with each merge to master.

I'll expect the frequency of master releases to be a few weeks to months so the general advice that David healey gave in all videos since 2019 to use the develop branch for actual development stays valid.

Oh and I've thrown in VS2022 support so you don't need to crawl the web for an ancient version of 2017 anymore...

So time went on and I simplified the build process for Faust a bit so I thought I'll post the build instructions (or the link to the instructions) here and update the post once it changes:

Windows

No Projucer modifications necessary!

• Download and install Faust to the default path (C:\Program Files\Faust). The latest version is available here: https://github.com/grame-cncm/faust/releases
• Open projects/standalone/HISE Standalone.jucer and click on Save and Open in IDE
• Change the build configuration in Visual Studio to either Debug with Faust or Release with Faust. This can be done with a drop down menu in the toolbar (which initially says Debug).
• Compile this configuration. HISE will have a text label in the top bar indicating that Faust is enabled.

macOS

See here: https://github.com/christophhart/HISE/tree/develop/tools/faust

Linux

See here:
https://resonant-bytes.de/blog/gsoc-final-submission/

Then you just need to add the directory of the Faust installation to your HISE settings under FaustPath so that it can find the Faust libraries and you're good to go.

I'll lock this topic and pin it to the top now.

What's the best way to return to coding after a vacation break? Yes, adding a fun feature that is easy on the brain cells. So here I present to you:

Code snippet templates

These extend the autocomplete items with templates of commonly used code snippets. Check out how it creates a CSS definition for a button LAF within seconds:

These are the features:

• use the stock templates that come with HISE or add your own templates in a JSON file for the ultimate customization
• use the preselect range feature to create multiple selections after inserting the template

Docs:

Have fun! Also I'm happy to accept snippets to be added to the default list, so post them if you find them useful!

Alright guys, here we go:

I tried to cover a few common edge cases, but I'm sure there's lots to discover when doing monkey testing, so let me know if you find glitches...

Hi everybody,

not sure if that feature made it to anybody's radar, but there is a quick connection mode that let's you connect parameters to your script controls with a single click and I've seen a lot of videos / screencasts which are missing out on that simple function so I'm trying to raise awareness for this awesome helper tool...

I've updated the UX to make it a bit more approachable, so now you just need to right click a component - either in the interface editor or in the script component list and choose Enable Connection Learn. Then you need to click on any parameter (either on the module editor interface or a macro parameter in a scriptnode network and it will automatically assign the UI element to control this parameter. It does this by setting all relevant properties (processorId / parameterId as well as the parameter range) so this will heavily speed up the process if you have to connect multiple elements.

SettingsWindows

@DanH no it figures it out using advanced AI technology:

numWavetables = fileLength / cycleLength.

Long overdue, but it seems that this was really holding people back from CSS...

These are the rules:

• you can now use local LAF objects with mixed CSS & script functions
• global look and feels can still be only script or CSS but that should be fine as you can always use a local LAF if you need both
• script functions have the precedence, so if a draw function was registered it will always supercede the CSS definition
• the exception is popup menu styling - as soon as you combine script functions & CSS, the popup menu will always be styled with the CSS.

Combobox with scripted draw function & CSS styled popupmenu:

const var laf = Content.createLocalLookAndFeel();

// Combobox is styled by a function
laf.registerFunction("drawComboBox", function(g, obj)
{
	g.setColour(obj.bgColour);
	g.fillRect(obj.area);
	g.setFont("Comic Sans MS", 21);
	g.setColour(Colours.blue);
	g.drawAlignedText(obj.text, obj.area, "centred");
});

// Popup menu is styled by CSS
laf.setInlineStyleSheet("
.popup
{
	background: #333;
}

.popup-item
{
	background: transparent;
	color: #999;
	padding: 10px;
}

.popup-item:hover
{
	background: rgba(255,255,255, 0.2);
}

.popup-item:active
{
	color: white;
	font-weight: bold;
}
");

Content.getComponent("ComboBox1").setLocalLookAndFeel(laf);

so how do you want to merge them? Is Alice 31 or 30?

I would refrain from a recursive logic, looks like you have a fixed depth hierarchy that you can just handcode.

don't use the velocity stacking (I think I've removed those). If you don't need to resample acousting material and already have power of two sized wavetables, just load in a sample that has all the wavetables stitched together, and use the resample mode. Ideally you can pass in the cycle length so the chances of the algorithm messing that up is smaller.

At some point we have to address that problem, I notice more and more posts just pasting the rubbish GPT output which dilutes the prestine information set available here in the forum.

Regarding the problem at hand, a single look at one of the many snippets / code examples from a good source should solve that problem, tuck inline before the function definition and pass it into the call.

@ustk nope once compiled they are a blackbox.

You don‘t need to compile nodes it just makes them faster especially when doing complex stuff and if you need to access them through the API then it‘s definitely a case of leaving them in the interpreted state.

@Oli-Ullmann obj.text

@Oli-Ullmann use the button text as the key in a JSON object with the display string as value then you don‘t need to branch at all.

@Lindon nope it‘s bypassed.

Also it's not stored as plain text, but as compressed zstd blob, but that won't stop the criminal masterminds of this world.