Dan Nigrin

Say I have many (anywhere from 5 to 100) live.number, live.dial and live.menu objects in a patcher. In the case of the live.number and live.dial objects, they each have different ranges; some might be 0-64, others 0-100, or 0-127, or even -127-127. In the case of the live.menu, they are all likely to have different numbers of choices.

I'd like to randomize each of those objects.

My question: is there some programmatic way I could randomize each, without having to manually go into my patch and create separate random objects, each of which would have the correct range to apply to each individual object?

Say I have many (anywhere from 5 to 100) live.number, live.dial and live.menu objects in a patcher.   In the case of the live.number and live.dial objects, they each have different ranges; some might be 0-64, others 0-100, or 0-127, or even -127-127.  In the case of the live.menu, they are all likely to have different numbers of choices.

I'd like to  randomize each of those objects.

My question:  is there some programmatic way I could randomize each, without having to manually go into my patch and create separate random objects, each of which would have the correct range to apply to each individual object?

Say I have many (anywhere from 5 to 100) live.number, live.dial and live.menu objects in a patcher.   In the case of the live.number and liv

randomizing-multiple-values

Actually, this thread gave me an idea to try, using "rawfloat" and a range of 0. to 1.

https://cycling74.com/forums/trying-to-randomize-live%C2%B7dial-with-random-values-scaled-to-match-the-range-of-the-dial

Actually, this thread gave me an idea to try, using "rawfloat" and a range of 0. to 1.
https://cycling74.com/forums/trying-to-randomize-live%C2%B7dial-with-random-values-scaled-to-match-the-range-of-the-dial 

thats the main issue with all this live dot stuff... you are no longer forced to use a range of 0. - 1. at least anywhere near your interface elements.

if you would, you could easily solve this using vexpr.


thats the main issue with all this live dot stuff... you are no longer forced to use a range of 0. - 1. at least anywhere near your interface elements.

if you would, you could easily solve this using vexpr.



Yes, that's what I realized after messing with this last night - though the rawfloat message with a random value from 0. to 1. does work, it doesn't help in my particular use case, as I need to have the actual value that will result from the live.XXX interface element, and I can't just read what it's output will be after setting it, as I'll be just set'ing the value...

randomizing multiple values