@Avián
Did you use Export->Compile Project?
As far as I know, that doesn't work. You have to use the direct selection. Export as VSTi, as Standalone, etc...
@dannytaurus This is 100% true. Our data and research show that music producers prefer interactive chord tools to chord packs. Chord packs are considered lazy.
What we've seen with AI is companies like Lemonaide training their models to let users generate chords with a single click, but these models take a long time to train.
Our approach is quite different. We want to use AI to help producers learn music theory as they produce.
@David-Healey oh, that was my bad... I think I stopped the upload - reuploaded them (should be around 61MB)
and yes I signed it with the built in tool, maybe thats it - I'll try signing it manually tomorrow (today?)
@David-Healey today I learned how to edit knobs in knobman. knob jumping through actual values is much better looking than a normal 0-10 scale like in the original5a357cd1-2fa5-4ea1-b884-96512c3da37b-image.png
@Oli-Ullmann Ah damn it, that was on me. There was a small typo in the DLL template that creates the Projucer file which messed up the Xcode project generation. The CI didn't catch it because it exports a standalone version of the demo project...
It's fixed now, let me know if you have other issues on macOS.
@Christoph-Hart It doesn't always. I'll do a little more research, and post info on why. It's Apple's way of saying, "We're Apple, and we don't think you need to worry about this. Because we're Apple."
@Christoph-Hart any idea what's going on here? I've selected the top params to have external modulation enabled but it's suggesting something also happening with the nested params in the child container.... ui glitch or bug?
