I find it unlikely for that to happen in the short term.
However I’ve been looking at the OWL toolchain and I want to integrate OWL as a generator, because it doesn’t make sense for me that you guys are doing that separately.
I’m also not 100% sold on the separate
@owl parameters, why is it done like this exactly?
For DPF I’ve instead extended the
@hv_param to allow for specifying parameter types (this way I now have booleans and triggers, and hopefully more, in the DPF builds) and the patches can stay waaaay more general and be used in other generators as well.
Heavy is used for so many different targets and I’d prefer if things don’t diverge or lock into a specific framework
(btw we support Daisy now as well )
One of the big wishes is to support [expr] objects, which could also bring in a ton of possible optimizations of the internal objects.
Personally I really want [midirealtimein] so we can do things with midi-clock synchronization and such.
Sometime this year I hope to chat with a number of “stakeholders” so we can draw up a kind of roadmap for the project.
Have invited some more people into the repository and hopefully we can all be good stewards for it!