Where are we with Hise currently?

[ustk]

Hey guys. I've missed some important parts lately since I was away, apparently not at the best time concerning the newly discussed changes with Hise.
So I've heard about AI, proprietary sub-module-github-ish stuff, and of course the last bug fixes and improvements especially around the matrix modulation. In short, very interesting stuff !

1. So my question is, what is the order of importance in all this?

2. Because my plugin is waiting for the matrix modulation to work to be released (as it was planned to already be), are the bug fixes still a top priority?

3. I understand the necessity and the hype around AI that I can't myself wait to see and embrace. But is it not adding too much burden at a crucial moment where big stuff are still waiting to be released (and a new Hise version if I remember well), and for which many people are waiting a working/stable version to release their products?

It would be cool to understand the current roadmap better so that we can adapt to it

[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.