[chuck-users] problems with chubgraphs

[Spencer Salazar]

Hey all,

For the Chubgraph example, you'll want to use "outlet" instead of dac:

class TestChubgraph extends Chubgraph {
        SinOsc o => outlet;
        400 => o.freq;
}

outlet is the local output terminal for the Chubgraph, whereas dac is
the same dac it always is.

Performance-wise, Chugens are basically doing the exact same thing as
a conventional 1::samp/Step loop, so I would expect comparable
performance in those cases. Chubgraphs basically plug existing C++
ugens together, so they end up being an order of magnitude faster than
Chugens, which execute ChucK VM code for every sample. The main
advantage of Chugens in either case is ease of use and clarity, at the
potential expense of performance.

The paper is here:
https://ccrma.stanford.edu/~spencer/publications/CCC2012.pdf
(to be published later this year as part of ICMC 2012)

spencer


On Wed, Aug 29, 2012 at 11:24 AM, Michael Heuer <heuermh at gmail.com> wrote:
> Robin Haberkorn <robin.haberkorn at googlemail.com> wrote:
>
>> Also thinking about Chugens, could someone comment on the performance
>> aspect of using them for audio-rate processing (in comparison to a
>> traditional 1::samp loop, e.g. in a Chubgraph)?
>
> Spencer's 2012 paper "CHUGENS, CHUBGRAPHS, CHUGINS: 3 TIERS FOR
> EXTENDING CHUCK" provides examples and performance numbers.
> Unfortunately I'm not sure where that was published and two seconds
> with Google can't find the reference.  Check the mailing list
> archives.
>
>    michael
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
>