Hello,

I find it useful to wrap random in an abstraction, so that I use $2 as an instance id, to both receive a "seed" and to add the abstraction id to the seed.

But, it would be really useful to have a unique instance id already generated in the [random] object, and a global symbol to bind all [random]s to send a seed and increment it by each unique id.

what do you think? is this possible?

I tested briefly and thie wrapping method really gives different random streams provided there is a different seed when opening the patch

On May 31, 2018, at 10:00 PM, Martin Peach <chakekatzil@gmail.com> wrote:

On Thu, May 31, 2018 at 3:09 PM, hans w. koch <hansw.koch@gmail.com> wrote:

but couldn´t that pi limitation worked around by a loadbang -delay combo to read a date, once the system has established one?
would need mention in the helpfile though.

The pi might not be connected to any network, in which case it will always start at Jan 1, 2000.

/dev/random may not be usable right at startup as it needs time to accumulate entropy, .dev/urandom is guaranteed to give some sort of random. Reading a few bytes from /dev/urandom into a table then combining them into a float or long int seems like a better idea.

There's an equivalent method in the WIndows API (SystemPrng), but it would have to be coded into an external since it's not a file like in linux.

Martin

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list