[chuck-users] Various general questions

Robin Haberkorn robin.haberkorn at googlemail.com
Sat Mar 24 10:46:44 EDT 2012

Hello Spencer!

On 23/03/12 22:54, Spencer Salazar wrote:
> Hey Robin!
> ...
> You can check out the primary development branch using SVN, like so:
> svn checkout https://chuck-dev.stanford.edu/svn/chuck/trunk/ chuck
> Development has been moving kind of fast lately, so things might not
> totally be working/compiling on some platforms (e.g.Windows or Linux).
> This will likely get cleaned up in the next week or so, now that I
> have some free time to do so.

this is just what I was looking for. Thanks!

Btw. current SVN compiles fine on my
$ uname -a
Linux nb005-lx001 2.6.32-40-generic #87-Ubuntu SMP Tue Mar 6 00:56:56
UTC 2012 x86_64 GNU/Linux

using -m32 of course

but sample programs crash with badalloc exceptions. Looking at the
backtrace it seems it tries to allocate an obscene amount of "SAMPLE"s.
Haven't looked any further into this; and I don't need it at the moment
- just wanted to give it a quick try.

btw. ChucK dracula is compiled with -m32 on my machine and I haven't
found any bug I could blame on that.
After all it should be built as a true 32-bit application.

one remark about the build system (ok this is truly off-topic in
 * CHUCK_DEBUG should add -O0 and -O flags should be removed from the
platform specific makefiles (only the last -O on the gcc command line


>> 2) Is there a real bug tracker somewhere?
>> I found the one in the wiki, but it is somewhat confusing...
> ChucK has a "private" (to SVN committers only) bug tracker, which
> isn't that helpful, but which actually is only a recent addition.
> Having a public bug tracker is on our to-do list.
>> 3) Is there a way to use multiple sound devices in one ChucK VM?
>> I'm using chuck on Linux-ALSA. It seems I have to specify the
>> dac on the command line (--dacX). This could probably be used to start
>> one VM per soundcard and exchange audio data via netout/netin. I will
>> try this soon.
> This is not currently possible.
>> However just out of curiosity, is multiple-dac support in one VM
>> anticipated some time in the future?
> Yes! For Linux we haven't encountered compelling use cases other than
> removing the need for two different binaries. But for Windows,
> switching between ASIO and DirectSound within the same binary seems
> pretty useful, so likely it will be straightforward to extend this
> capability to ChucK on Linux once the Windows version has it.
>> 4) regarding netout/netin. This may also be useful for integration with
>> other applications like Pure Data. Does anyone have experience with it
>> or details about the protocol if there is any? If not I will have a look
>> at it as soon as I need it and write a Pure Data external if necessary.
> netin/netout is something of an ignored feature at the moment -- I
> sense a general interest in having working network audio xmitters, but
> network communication between ChucK and other audio/programming
> environments seems to be mostly confined to control-rate information,
> in which case OSC is sufficient.
>> 5) I read about an Un-Chuck operator (=<). However it appears nowhere in
>> the current docs. Is it still supported, or temporarily disabled?
> Un-chuck is alive and well -- I believe this would be one of many
> shortcomings of the current set of documentation. You can use it to
> remove a UGen from the audio graph, and ensure that that UGen is no
> longer using up CPU cycles to generate/process samples.
> SinOsc s => dac;
> 1::second => now; // sound happens
> s =< dac;
> 1::second => now; // no sound!
>> 6) In the "Developer Guide" I read something about OpenGL support. This
>> was the only mention of OpenGL support I came across. I suppose if this
>> really exists, it is a new development feature since v1.2.1.3 does not
>> appear to posses any (undocumented) OpenGL API.
> OpenGL support has existed in various incarnations, mostly as a result
> of various student projects, but has never been released officially as
> part of ChucK. How best to integrate graphics processing into ChucK is
> an open issue at this point, one in which we (ChucK team) are very
> interested in, but also don't necessarily know the answer to.
> spencer
>> Best regards,
>> Robin Haberkorn
>> _______________________________________________
>> 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

More information about the chuck-users mailing list