# [chuck-users] chuck vs supercollider?

ronni montoya ronni.montoya at gmail.com
Sat Aug 11 19:25:21 EDT 2012

Hi, Is this way of making sounds very expensive in cpu terms? :O

I was wondering if this type of  making sounds can be cathegorized as
"non standard synthesis"?
In sc3 i been experimenting with something similar but instead of
defining the sample values each sample, the approach is to generate
waveform segments, so you dont need to specify the values for each
sample, you just define the length of your segment and the amplitude
value.

Do you think defining each sample value instead of waveform segments
gives more posibilities? or new posibilities in sound construction?
Can the brain feel changes in segment less than 64 samples?

i been experimenting in the afternoon and i make this code, theres
somethings i still dont understand from chuck logic, for example if i
uncomment this line in the code " // v * Math.sin(k)  => k;"  why do i
get so dramatic changes? I was not expecting to have any change
because  that line of code is going to variable " k"  and variable "k"
is not being used in  "v  => s.next; "

Can anybody explain me whats happening?

thanks!

R.

Step s => dac;
// modulator
SinOsc m => blackhole;
0.15 => m.freq;
SinOsc t => blackhole;
0.015 => t.freq;
6 => float v;
6 => float k;

fun void sample_manipulation( )
{
0.1 + k => k;

220 * (now/ samp) => Math.sin  => v;

if (v > 0.9) {
-0.2 * 10 * m.last() => v;

}
if (v == 0.2) {
-0.2 * 10 * t.last() => v;
}

if (v < 0.2) {
v * Math.sin(k)  => v;
//  v * Math.sin(k)  => k;
}

v * ( v  * 100 ) +  m.last() * Math.sin( m.last() ) => v;

}

while (true)
{

sample_manipulation ( ) ;
v  => s.next;
1::samp => now;
}

2012/8/12 Kassen <signal.automatique at gmail.com>:
> On 11 August 2012 21:43, ronni montoya <ronni.montoya at gmail.com> wrote:
>> thank you, i will experiment and ill let you know.
>>
>
> Great!
>
> If you'd have the time I'd also be curious to hear how you came up
> with the question. Was this simply a matter of seeing that ChucK uses
> a process with some CPU penalty and being interested in what this cost
> was buying? I've seen the reverse happen; people trying to use
> feedback in Max/Msp or SC and noticing that they weren't getting what
> they expected and wondered why, but you are going the other way
> around. That's interesting.
>
> Yours,
> Kas.
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users