Re: [chuck-users] problems with chubgraphs

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.

I think I mixed up the Chugens with the (C++ based and compiled) Chugins? So many new words, sorry about the confusion.