Csound Csound-dev Csound-tekno Search About

Re: Randon numbers again

Date1998-11-10 10:40
From"Matt J. Ingalls"
SubjectRe: Randon numbers again
AttachmentsNone  

Date1998-11-10 17:33
FromRichard Karpen
SubjectRe: Randon numbers again
I like the idea of updating the rand family to 31 bits and having an
optional mode for using it in the old mode. 

xr randi xamp, xfreq, [iseed, imode]

imode defaults to 31 bits. Any non-zero value will switch it to old rand.

RK

On 10 Nov 1998, Matt J. Ingalls wrote:

> --- You wrote:
> way).  Clearly to change it would or could break old orchestras which
> is something I am trying to avoid.  I have implemented a rand2, rand2h
> and rand2i set of opcodes which use a full 31 bit generator.
> But... is that what is needed or would you prefer to see this as an
> optional argument to the opcode rather than a new opcode?  Or not at
> --- end of quote ---
> 
> backwards compatibility is nice, but i prefer to look forwards..
> 
> my vote:
> make "rand" the 31 bit generator, and have an optional
> flag to turn it into old (16-bit?) rng...
> 
> this might make old orc/scos sound different, but at least they will still
> "render" with no errors
> -matt
> 

Date1998-11-10 17:52
FromRichard Boulanger
SubjectRe: Randon numbers again
I think it would be better to have imode default to the original version
and any non-zero value will switch  to the new mode. We shouldn't have to
change all the old orc and scores... for instance, this new rand breaks
Trapped or it did when John last implimented it.

Or I would be happy with a new opcode - especially in light of the fact
that we have added such an extensive new family of rand opcodes.

rick


>I like the idea of updating the rand family to 31 bits and having an
>optional mode for using it in the old mode.
>
>xr randi xamp, xfreq, [iseed, imode]
>
>imode defaults to 31 bits. Any non-zero value will switch it to old rand.
>
>RK
>
>On 10 Nov 1998, Matt J. Ingalls wrote:
>
>> --- You wrote:
>> way).  Clearly to change it would or could break old orchestras which
>> is something I am trying to avoid.  I have implemented a rand2, rand2h
>> and rand2i set of opcodes which use a full 31 bit generator.
>> But... is that what is needed or would you prefer to see this as an
>> optional argument to the opcode rather than a new opcode?  Or not at
>> --- end of quote ---
>>
>> backwards compatibility is nice, but i prefer to look forwards..
>>
>> my vote:
>> make "rand" the 31 bit generator, and have an optional
>> flag to turn it into old (16-bit?) rng...
>>
>> this might make old orc/scos sound different, but at least they will still
>> "render" with no errors
>> -matt
>>


==================
Dr. Richard Boulanger
Professor - Music Synthesis Department
Berklee College of Music
1140 Boylston Street  - Boston, MA  02215-3693
Office Phone: (617) 747-2485   Office Fax: (617) 536-2257
==========================================
Email: radiobaton@earthlink.net
URL: http://www.fortunecity.com/tinpan/underworld/836/
=================================================