well it used to be the case that it was difficult to save per-abstraction parameters. with the addition of [savestate]
I don't think that's as much of a factor anymore.
In the past you could have a simple abstraction that could increment a value held in a message box to supply a different seed every
time a patch was loaded.
But now you could do basically the same with [savestate] I think. (and don't have to store save state outside the abstraction yourself)
of course the most common suggestion is to use [date] and [time] from zexy. maybe the better solution is to put those objects into vanilla..
because such an abstraction would be very simple also.
-seb
-----Original Message-----
From: Peter P. <peterparker@fastmail.com>
To: pd-list@lists.iem.at
Sent: Sun, Dec 11, 2022 2:22 pm
Subject: Re: [PD] [random] and seed value
Hi Thomas,
* Thomas Mayer <thomas@residuum.org> [2022-12-11 21:20]:
[...]
> My guess is, that most users probably expect at least different seed values
> every time.
>
> Maybe the help file should explicitely state the behaviour or a different
> way for deriving the initial seed should be used, e.g. taking the local
> time. Or a better PRNG could be used as well.
>
> If we take the solution to initialize [random] with a different seed each
> time, an explanation on how to revert to the old behaviour of a seed value
> of 1489853723 should be mentioned in the help.
I think the main thing to worry about is if any of the patches written
in the last 20+ years will stop working in the way intended by a such a
modification.
I loosely remember that someone somewhen showed how to get a different
seed every time using an abstraction. If such a solution exists in
vanilla Pd, it could be added as a solution to the docs perhaps?