Maybe Rick is dreaming of something like the attached .csd.

I've thought it out carefully. It implies *lots* of defaults, including a
function table. I think anything *less* might be dangerous and potentially
cause pitfalls.

I'm all for defaults - particularly ones that can be counted on not to cause
problems for beginners.

Art Hunkins

----- Original Message -----
From: "Dr. Richard Boulanger" 
To: 
Cc: 
Sent: Tuesday, March 29, 2005 5:39 AM
Subject: [Cs-dev] Re: [Csnd] statevar, atn Victor ( also svfilter bug too )


> I agree with Iain that it would be an excellent and incredibly useful
> addition to the manual to have recommended ranges for all opcode
parameters
> and/or default values for all parameters of an opcode so that you could
just
> slap together an instrument with just opcodes and no parameter
> specifications.
>
> As the Csound5 developers are so carefully combing through the language
and
> cleaning up so many bugs, maybe this is something to consider?
>
> Dr. B.
>
> on 3/29/05 4:06 AM, Iain Duncan at iainduncan@telus.net wrote:
>
> >
> >> statevar will limit the resonance depending on the amount of
> >> oversampling. The
> >> filter will not get unstable no matter what you do. More oversampling
> >> will let
> >> you have sharper resonances.
> >
> > What I actually meant was that the manual does not let me know what the
> > units *mean*. There is no explanation of a reasonable range, or how it
> > should be scaled, etc. Ie if we are emulating an analogue filter, how
> > would we emulate a knob? Linear from 0-1? Exponential from 1-100? etc.
> > Unfortunately a lot of the filter opcodes are guilty of this. Even if
> > the math is daunting I'd like to know what the units relate to, and a
> > good starting point for range.
> >
> > It also blow up. ( crashing the instrument ) This seems to be triggered
> > by cutoff frequency, but it definitely blows up in csound5, as does
> > svfilter. In their current states I'd have to say both are unusable for
> > live because I couldn't even figure out what a lower reasonable range
> > for cutoff was to prevent blow up, and the blow-up combos of res and fc
> > seem kind of unpredictable. It was low enough that I can't use it ( ie I
> > want to be able to open it all the way to essentially turn it off if
> > desired. ) I had it blowing up with certain values of cutoff well within
> > audible limits ( 12-16khz ) both with and without the use of the balance
> > opcode. Would love to play with it if it can be fixed up though!
> >
> > Thanks
> > Iain
>
> _______________________________________________________________________
>  +  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) 747-2564
>  +  eMail: rboulanger@csounds.com  or  rboulanger@berklee.edu
>  +  WebPage: http://csounds.com/boulanger/
> ________________________________________________________________________
>  +  Almost Everything Csound @ http://csounds.com/
>  +  The Csound Catalog with Audio @ http://csounds.com/catalog/
>  +  The Csound Book @ http://csounds.com/book/
>  +  The Csound Magazine @ http://csounds.com/ezine/
>  +  CsoundForums @ http://csounds.com/phpBB2/
> ________________________________________________________________________
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel