DSP Robotics Support

R&R wrote:If I can have strings, the sky is the limit... HEX or straight of using any number of letters as the base. Splendid!

I'm glad I could be of service
But unfortunately I have to slow you down. Any number of letters is not possible. A preset string is limited to 255 ascii characters (=255 byte). Still, that's a lot

Thanks for the advice, this will likely alleviate my problems with loading time by alot...

tulamide wrote:But unfortunately I have to slow you down. Any number of letters is not possible. A preset string is limited to 255 ascii characters (=255 byte). Still, that's a lot

255 is far more than i'll ever need

First of all... I have to try using strings in a preset for the first time
Then ponder a bit what makes most sense how to use them in my particular case.

Using map as you suggested Tulamide, to spit out 0,1 integers from Ruby box will work perfect for now I think

Took a while but seems to work with my reset schematics and insane amount of selectors after some additional trigger blockers and "changed prims" etc to avoid potential trigger storm and unwanted triggers during knob movements.

Guess there will be a little extra overhead since alot of knobs are sharing the same string, that has to be updated, but shouldn't cause problems I hope. I'll keep my structure as is and let the strings be around max 30 chars per preset.

Going to try and implement it with dropdowns eventually. Have to see first if using strings this way is stable when scaling up

Hmmm...
Noticed this "carry over" to poly... after working alot in green. I have to go through alot of my poly schematics or?
Edit: Phew!... luckily wasn't that many Question... anyone know how this prim works inside or looks in Ruby?
Edit: Seems slightly different from just doing a for/while/times loop in the Ruby box. Might be a changed and/or samplehold behaviour due to having stored internal input variable, but still passing the trigger along...