September 2012 - chuck-users - lists.cs.princeton.edu

chuck 1.3.1 on Windows 32-bit - possible OSC issue
by Simon Steptoe 11 Sep '12

11 Sep '12

Some of my existing patches are causing Chuck 1.3.1 to lock-up and crash. I think I've traced it back to a possible OSC issue as the example files s.ck and r.ck seem to cause the same problem... which would make sense in that my affected patches are also using OSC events. If the patch gets going at all, removing the shred(s) also causes a crash. OSC_send.ck and OSC_recv.ck however seem to work fine. On my own patches I can sometimes catch the error message; "OutOfMemory: while allocating stack"... increasing buffer size and/or decreasing sample rate seem to alleviate the problem somewhat in that things keep running a few seconds longer, but eventually the result is the same. However, I guess this might not be the same issue as with s.ck and r.ck. Running Chuck with --silent doesn't resolve things either. My machine is Windows 7, 32-bit... to be fair it is a bit on the old side (Pentium 4)... but it's coped fine with previous versions of Chuck and miniAudicle.... and I can't replicate the issue with Chuck 1.3.0.2. Many thanks. Simon

2 1

1.3.1 not happy with my jack (64-bit)
by plutek 09 Sep '12

09 Sep '12

greetings! i just compiled 1.3.1 on a 64-bit linux system. compilation for jack went fine, and chuck runs without error messages. however.... no jack client is created. (so, of course, i hear nothing) shreds don't actually get started. (i.e. chuck ^ shows NOTHING) when i stop chuck, it says: RtApiJack::closeStream(): no open stream to close! if i run with --silent, incoming shreds DO show up. my jack is working fine with other applications. any clues? what shall i send to help figure this out? thanks much... cheers! .pltk.

1 0

#chucktweets
by Thomas McColgan 08 Sep '12

08 Sep '12

Hi all, I was just playing around with chuck and I thought it would be fun to have a hashtag of chucktweets on twitter in the spirit of #sctweets that the supercollider guys have, ie self contained compositions that fit into 140 chars. I went ahead and posted a very simple one of my own: https://twitter.com/phreeza/status/242609758404747264 Looking forward to seeing what you guys can come up with. Cheers, Thomas

4 3

miniAudicle-0.2.2 (gidora) released
by Spencer Salazar 07 Sep '12

07 Sep '12

Howdy from Ljubljana, miniAudicle-0.2.2 has been released: http://audicle.cs.princeton.edu/mini/ The primary purpose of this release is to provide interoperability with the shiny new 64-bit chuck-1.3.1.0, for which minor cleanup of miniAudicle's internal workings was necessary. Also note that the Windows executable is still 32-bit, as we lack the appropriate resources to build/test on 64-bit Windows. Please let us know about any problems, bugs, feature requests, etc. Thanks, Spencer, Ge, + chuck team --- 0.2.2 - (added) chuck-1.3.1.0 - (fixed) 64-bit support

1 0

nable to find audio input device with requested channel count
by Jonas Gruska 07 Sep '12

07 Sep '12

Dear fellow Chuck users, I am now working on a system with no ADC, thus no input channels. But, for some reason, Chuck wants to use those, no matter the program. To quote: [chuck]: unable to find audio input device with requested channel count (2) [chuck]: cannot initialize audio device (try using --silent/-s) When I try adding --in0 it doesn't accept it as valid option. Is there a way how to deal with this? Regards, Jonas

2 1

wavetable synthesis
by Michael Heuer 06 Sep '12

06 Sep '12

Hello, I found this collection of 600-sample one cycle waveforms recently http://www.adventurekid.se/AKRT/ If I wanted to use these for "wavetable synthesis", is it just a matter of wrapping a looping SndBuf or LiSa with ADSR and tweaking the freq? What if I wanted to do something like the Shruthi1 hardware http://mutable-instruments.net/shruthi1/manual or the Animoog app http://www.moogmusic.com/products/apps/animoog-0 where a bunch of waveforms are combined into a single wavetable, e.g. the Shruthi1 doc "All these waveforms are wavetables, comprising 16 single-cycle waveforms. The parameter scans the wavetable, smoothly interpolating between each waveform. Some of these tables are 'transwaves': the single cycle waveforms were extracted from different 'stages' of a sample, and you can somehow recreate the original sample by using an envelope that will sweep the parameter from 0 to 127." Sorry if this question is Electronic Music 101. michael

2 4

problems with chubgraphs
by Robin Haberkorn 03 Sep '12

03 Sep '12

Sorry to bother you again, but I'm experiencing difficulties using the new Chubgraph feature. Using v1.3.0.2 of course. class TestChubgraph extends Chubgraph { SinOsc o => dac; 400 => o.freq; } TestChubgraph c; 10::second => now; This code does the sine wave sound but it should be silent since "c" is not connected to dac. Reading the Chubgraph example, I thought that the dac in the Chubgraph class is local to the object instance - as a way to connect to the UGen's output. Also what's strange is that the number of channels reported for dac in the class is the same as the number of output channels I've requested for ChucK. Did I miss something or is it a bug? 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)? Thanks in advance, Robin

4 9

me.source* always empty with chuck add
by Todd Willey 03 Sep '12

03 Sep '12

The examples/otf_01.ck file recommends running `chuck --loop` in one terminal, and `chuck + otf_01.ck` in another. The looping vm bombs out at: me.sourceDir() + "/data/kick.wav" => buf.read; with: [chuck](via SndBuf): cannot stat file '/data/kick.wav'... After adding some debugging statements, it looks like me.sourceDir returns the empty string, as does me.sourcePath. If there is a more appropriate place to report/discuss these things, please let me know. -todd[1]

3 4