Where are we with Hise currently?

[David Healey]

@ustk

1. The JUCE sub-module is important because it's a new way to pull the latest version of HISE and allows you to use JUCE8 if you have a license for it.

2. 

3. Most of the AI stuff we've been discussing/using is related to writing code for the HISE codebase rather than scripting. Although making the scripting API more suitable for AI coding is also in the works.

[ustk]

@David-Healey Concerning the sub module thingy I was speaking about Hise supporting cross-project assets/script to make our life easier. I think I've read something about that...
Yes for JUCE I already use the git sub-module as I am on the latest Hise version

[David Healey]

@ustk ah the asset manager? Yes I want to know more too

[DanH]

@ustk said in Where are we with Hise currently?:

Because my plugin is waiting for the matrix modulation to work to be released

I don't think too much has been done with the mod matrix recently. Might be useful if we narrow down a target fix list between ourselves and others - I think there's only one or two more who are waiting on this? @Orvillain @dannytaurus @Oli-Ullmann perhaps?

[Christoph Hart]

yeah, the attempt of wrapping up the mod matrix lead to 5 people having 20 different requests for their individual projects. Maybe we need to settle on a common denominator feature set and make this robust - that's what this system was designed for.

[DanH]

@Christoph-Hart guilty as charged

[ustk]

@Christoph-Hart I’m pretty happy with the current mod matrix but my needs are rather simple so I am not yet facing limitations others might have with more advanced projects

However, the problem is that what’s existing already isn’t working:

• Matrix Modulators are not controlled in exported plugins (at least for FX) neither with UI sliders nor from modulation. But I reckon we narrowed this down to the extra_mod nodes not operating so it might not be the MM itself in the end but its connection to the node.

• there’s still the issue where changing the target from the dropdown messes up the connections. The automatic git branch fix isn’t fixing the issue.

[Oli Ullmann]

@DanH
I also remember that the MatrixModulator still does not render continuously when no note is pressed, which means that the modulation in the LAF of the slider only works when a note is played. This problem does not occur if only a matrixTargetId without MatrixModulator is used.

When it comes to modulation, however, I think it is more important to solve the envelope problem that I described in this post: https://forum.hise.audio/topic/14434/envelope-or-filter-trigger-problem
But I think @Christoph-Hart has that on his list.

@ustk I can confirm that the modulation system in effect plug-ins works in principle. I just tested it. It makes sense to me that the MatrixModulator doesn't work, as I think it needs a trigger input from a note, similar to an envelope, which is not the case with an effect plug-in. But that's just a guess and I haven't tested it.

[Lindon]

@Oli-Ullmann said in Where are we with Hise currently?:

When it comes to modulation, however, I think it is more important to solve the envelope problem that I described in this post: https://forum.hise.audio/topic/14434/envelope-or-filter-trigger-problem
But I think @Christoph-Hart has that on his list.

..and when it comes to modulation I think we should fix bugs that are regressions (used to work before all this mod matrix "stuff", now doesnt), like this:

https://forum.hise.audio/topic/14165/latest-version-of-hise-breaks-existing-presets?_=1772462759775

But I suspect we are heading into " 5 people having 20 different requests for their individual projects"

[dannytaurus]

@Lindon Fixing regression issues seems like it should be high(est?) priority.

[David Healey]

@dannytaurus I agree

[Oli Ullmann]

@Lindon
I agree with you! I think the bug I mentioned is also a regression.