surely a new score opcode is easiest, Little code and reseedable PS Richard -- I think I lost an e-mail from Archer in my machine crash. something he wanted me to do? Quoting Richard Dobson : > That would do; but ideally I would really like to have a version of > the seed opcode which returns the new (score) seed value (unless it > can be arranged to display it directly from the score). I have done > this many times in other situations - run a process with a > clock-sourced new seed each time, but if/when a particularly "good" > run manifests, it is rather handy to know what the seed is so I can > then replicate it. This is (in my case) for experimental R&D, not > for guaranteeing fresh results in live performance. > > Richard Dobson > > On 19/04/2014 16:23, Steven Yi wrote: >> I had the thought that rather than add something new to the score, it >> would be possible to add a commandline flag such as >> --score-seed-random=x where x could be a given value or 0 to seed with >> current time. >> >> On Sat, Apr 19, 2014 at 11:14 AM, wrote: >>> Sounds reasonable request to me. Will consider. >>> > > > > Send bugs reports to > https://github.com/csound/csound/issues > Discussions of bugs and features can be posted here > To unsubscribe, send email sympa@lists.bath.ac.uk with body > "unsubscribe csound"