The Missing Piece of the HISE VI Puzzle: Continuous Per-Event Modulation

[aaronventure]

@Christoph-Hart said in The Missing Piece of the HISE VI Puzzle: Continuous Per-Event Modulation:

The update rate is tied to the buffer size though (because that's how the modules are processed one after another).

What does this mean for wrapping stuff up in frame/block nodes? Will it just shout about rate mismatch like the midi node when you try to place it within a block node?

[Christoph Hart]

@aaronventure no, the update rate is simply the buffer size as this is the rate that the sound generators are able to talk with each other.

[aaronventure]

@Christoph-Hart so on higher buffer sizes, you get lower resolution streams?

Alright, it's then important to highlight it, as this warrants like 20ms smoothing at the lowest for consistency. Can the read nodes have smoothing built in? it'll be necessary anyway, this would just make it less of a mess.

[Christoph Hart]

You can use Engine.setMaximumBufferSize() to limit the buffer length to 64 or something then you get a guaranteed update rate of 1,5ms if that‘s what you need.

The nodes will not have any smoothing as you can simply add a smoothed parameter node, but the event data envelope (which is a polyphonic HISE envelope that automatically reads out the values from the given slot will have a smoothing parameter (like the LFO).

[aaronventure]

@Christoph-Hart Ah, good to know, I didn't know I can hard limit the buffer size for the plugin.

Yes, smoothing parameter/control is what I meant. Hiding smoothing inside the actual readout would be naughty.

[Christoph Hart]

@aaronventure Alright, the feature is pushed now (alongside with the documentation for each thing).

I've also added a bunch of snippets to the browser that demonstrate various use cases (Custom Data Event 101/102/103).

Let me know if you find some quirks.

[d.healey]

Does that solve this request? https://forum.hise.audio/topic/9501/message-event-flags-or-meta-data?_=1716378593963

[Christoph Hart]

@d-healey yup. You can now write 16 number values to a slot using an event ID and pick it up later either using scripting, a new modulator or nodes in scriptnode.

[d.healey]

@Christoph-Hart Cool, have the docs been pushed?

[aaronventure]

@d-healey It also solves Per-event routing: https://forum.hise.audio/topic/9625/per-event-routing?_=1716386003580

https://github.com/christophhart/HISE/issues/521

[aaronventure]

This is still broken because 0 cannot be sent:

https://github.com/christophhart/HISE/issues/537