[chuck-users] ResonZ Documentation

Mario Buoninfante mario.buoninfante at gmail.com
Wed Jun 16 02:58:56 EDT 2021


Hi Matt,

I did work a bit on documenting all the UGens (and not only) last year and
updated the FLOSS manual you can find here:
https://en.flossmanuals.net/chuck/_full/
Hope this might be of some help.. and also let me know if you want to
contribute! ;)

Cheers,
Mario

On Wed, 16 Jun 2021 at 05:43, Matt Comeione <matt at ideocentric.com> wrote:

> Thank you Jack,
>
> I think the point of confusion is looking at all of the ugens for
> available parameters while not seeing all of the available options. I had
> submitted a merge request recently for documentation on vec3 and vec4.  I
> started with the example code and then reviewed the code to derive the
> other features of these ugens.  I thought I might need to do the same for
> ResonZ as I did not recognize the .gain in the code.
>
>
> On Jun 15, 2021, at 9:14 PM, Jack Atherton <lja at ccrma.stanford.edu> wrote:
>
> Every UGen has a .gain, and it’s just multiplied against the signal to
> attenuate it or amplify it.
>
> The only place I’m aware of this in the documentation is in the Gain node,
> which has flavor text “NOTE — all unit generators can themselves change
> their gain”. It might be other places too. But it’s possibly worth making
> more apparent if it’s causing confusion!
>
> (Sorry I can’t point you to the code because I’m on my phone right now.)
> ~Jack
>
> On Tue, Jun 15, 2021 at 8:50 PM Matt Comeione <matt at ideocentric.com>
> wrote:
>
>> I was reviewing some code from the “Physics-Based Sound Syntheses for
>> Games and Interactive Systems”.  Some of the code examples utilize .gain on
>> the ResonZ filters which is not outlined in the documentation.  I was able
>> to extract some information on the documentation of the vec3 and vec4 by
>> looking at the code (additionally have submitted this documentation to
>> GitHub), however, the ResonZ code is a little more elusive.   Is there
>> someone that might have some insight into the code that could point me in
>> the direction to where I might find the appropriate relevant code?
>> _______________________________________________
>> chuck-users mailing list
>> chuck-users at lists.cs.princeton.edu
>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>>
>> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>
>
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20210616/d337747d/attachment-0001.html>


More information about the chuck-users mailing list