Alex Kempton

Yep, it definitely might start causing a lot of duplication. I don't think we need to keep the chunks anywhere special, we can just `export` various things from the modules...

For now, my feeling is that we'll be adding a lot of extra work for ourselves in these early stages of development and so I don't really want to go...

Sure, we could have a folder outside of `src`. I think this is a good starting point to get a feel for how backwards compatibility will work in the main...

I've started on this now: https://github.com/nudibranchrecords/hedron/tree/dev/projectFixScripts

A good test here would be to have a 100 params assigned to one midi control and see what happens.

More fundamental macro changes should be made before doing this. See https://github.com/nudibranchrecords/hedron/issues/10 for details.

Button macros should also be able to trigger anim input types

Macros work with boolean values. Wondering if shots can be added and they also just trigger like a boolean value, once the value is past 0.99.

I think generally it could end up making everything a fair bit simpler. Would be an opportunity to review the Redux architecture too. It's a big old job though!

Something like this might be easier to migrate, although I'd want to make sure it's widely supported because there's nothing worse than having unmaintained dependencies https://mohebifar.github.io/vidact/