cursedfrogurt's Recent Posts

You had me at arbitrary function generator.

That said, a UI option for this feature could be a "Vox Scale" dropdown, alongside the pre-existing Key/Scale selection. I've never actually investigated whether it is possible to define arbitrary key scales though . . .

That said, a pre-defined selection of VOX scales might do the trick as well. The combination of a collection of useful vox scales and the cv input attenuators would open up a lot of possibilities.

I updated Numerology and I can't reproduce this issue anymore. Numerology is 4.2 (build 178) here. I'm on MacOS 10.14.

I am on OSX 10.14.5 on a Macbook Air 5,2.
Aalto v 1.8.5 (AU.64)
Numerology Pro 4.2 (Build 181 + 182)

I was just testing again tonight, and Numerology is actually crashing. Maybe more of an issue with Num than with Aalto?

I noticed that certain parts of the Aalto UI will update when I change them (add patch cables, adjust dials, etc). The preset bar is always blank, but the menu will pop up when it is clicked. Loading a new preset does not update the UI -- dials and patch cords that were previously set remain.

When Aalto is closed with the preset menu open, the menu remains visible. If you click on the menu, Aalto immediately crashes. Again, this seems like it could be a Numerology UI bug, but it's always hard to tell with these things.

I'm hosting in another program right now, so I'm not banging down the doors or anything, but let me know if there's any testing I could do that would be helpful.

Maybe a precision attenuator on the vox output itself could help too? I'm open to ideas.

An arbitrary mapping would be really awesome here, similar idea to scale settings.

So with this scheme, a setting of vox 0 = 0, vox 1 = 1, vox 2 = 2, vox 3 = 3 would replicate the current scheme, but each voice's vox could be individually set/scaled to a different output value, like vox 0 = 0, vox 1 = 0.5, vox 2 = 3, vox 4 = -1

Curious, any update on this? I just booted up Numerology with the intent to play with some Aalto, and ran into this :(