DSP Robotics Support

trogluddite wrote:Well, I probably shouldn't take the credit - I think it's something migrated over from my old SM toolbox, so it might well be the work of long-lost gurus from the olden days

Glad that the hidden treasure in your toolbox is finally being explored Hope you didn't forget the Ruby voices thingy

trogluddite wrote:None that I can think of. In fact, I'd say that keeping them separate would be more useful for a "universal" toobox module

Well, I meant more in terms of schematic effectiveness. Let's say you have about 150 control elements in your schematic (buttons, knobs, etc.). What would be better then? 150 array preset primitives (that would store both value and cc value parameters as an array) or 300 single float preset primitives (that would store cc value and knob value separately)?

kortezzzz wrote:Well, I meant more in terms of schematic effectiveness

Without comparing directly, I can't say for sure, but I'd guess that the differences would probably cancel out - more presets in one case versus array index set/get logic in the other. In either case, no triggers escape the module just from the CC value changing, so I wouldn't expect much performance impact.

kortezzzz wrote:Hope you didn't forget the Ruby voices thingy

I've found both the green and Ruby versions that I made - just trying to get back up to speed with how the algorithms work so that I can start trying to match them to how the built-in manager works. Rain due tomorrow for the rest of the week!

trogluddite wrote:I've found both the green and Ruby versions that I made - just trying to get back up to speed with how the algorithms work so that I can start trying to match them to how the built-in manager works

Fantastic

Thanks for everything. And this one certainly would deserve it's own new post on "examples". It's raining some good news here as well