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

dumb python question...
by forrest curo 07 Oct '12

07 Oct '12

Okay, I can easily get python to start a chuck shred... My question: What's the easiest way to let it feed that shred notes? -- rather than the burn-the-house-down kludge of killing the old shred, starting a new one with new command-line?

4 14

Okay, trying to compile chuck 1.3 etc
by forrest curo 06 Oct '12

06 Oct '12

Okay, so I needed to 'sudo apt-get' a couple things: 'bison' & 'flex' Did that. And now, error messages. There seems to be some real error in the script for 'linux-jack' -- but the other versions are hanging on the need for files that aren't there? [Help?] ---------------------------------------------------------------- forrest@critter:~/chuck-1.3.1.0/src$ make linux-jack flex -ochuck.yy.c chuck.lex gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck.yy.c -o chuck.yy.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c util_math.c -o util_math.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c util_network.c -o util_network.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c util_raw.c -o util_raw.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c util_xforms.c -o util_xforms.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_absyn.cpp -o chuck_absyn.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_parse.cpp -o chuck_parse.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_errmsg.cpp -o chuck_errmsg.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_frame.cpp -o chuck_frame.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_symbol.cpp -o chuck_symbol.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_table.cpp -o chuck_table.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_utils.cpp -o chuck_utils.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_vm.cpp -o chuck_vm.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_instr.cpp -o chuck_instr.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_scan.cpp -o chuck_scan.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_type.cpp -o chuck_type.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_emit.cpp -o chuck_emit.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_compile.cpp -o chuck_compile.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_dl.cpp -o chuck_dl.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_oo.cpp -o chuck_oo.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_lang.cpp -o chuck_lang.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_ugen.cpp -o chuck_ugen.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_main.cpp -o chuck_main.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_otf.cpp -o chuck_otf.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_stats.cpp -o chuck_stats.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_bbq.cpp -o chuck_bbq.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_shell.cpp -o chuck_shell.o chuck_shell.cpp: In member function ‘virtual long int Chuck_Shell::Command_VMAdd::execute(std::vector<std::basic_string<char> >&, std::string&)’: chuck_shell.cpp:1728:54: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘std::vector<Chuck_Shell_VM*>::size_type {aka unsigned int}’ [-Wformat] chuck_shell.cpp:1728:54: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘std::vector<Chuck_Shell_VM*>::size_type {aka unsigned int}’ [-Wformat] chuck_shell.cpp: In member function ‘virtual long int Chuck_Shell::Command_VMList::execute(std::vector<std::basic_string<char> >&, std::string&)’: chuck_shell.cpp:1817:41: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘std::vector<std::basic_string<char> >::size_type {aka unsigned int}’ [-Wformat] chuck_shell.cpp:1817:41: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘std::vector<std::basic_string<char> >::size_type {aka unsigned int}’ [-Wformat] gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_console.cpp -o chuck_console.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c chuck_globals.cpp -o chuck_globals.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c digiio_rtaudio.cpp -o digiio_rtaudio.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c hidio_sdl.cpp -o hidio_sdl.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c midiio_rtmidi.cpp -o midiio_rtmidi.o gcc -O3 -D__UNIX_JACK__ -D__LINUX_JACK__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c RtAudio/RtAudio.cpp -o RtAudio/RtAudio.o RtAudio/RtAudio.cpp:1835:23: fatal error: jack/jack.h: No such file or directory compilation terminated. make: *** [RtAudio/RtAudio.o] Error 1 forrest@critter:~/chuck-1.3.1.0/src$ make [chuck build]: please use one of the following configurations: make linux-alsa, make linux-jack, make linux-oss, make osx, make osx-ub, or make win32 forrest@critter:~/chuck-1.3.1.0/src$ make linux-alsa gcc -O3 -D__LINUX_ALSA__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c RtAudio/RtAudio.cpp -o RtAudio/RtAudio.o RtAudio/RtAudio.cpp:5212:28: fatal error: alsa/asoundlib.h: No such file or directory compilation terminated. make: *** [RtAudio/RtAudio.o] Error 1 forrest@critter:~/chuck-1.3.1.0/src$ make linux-oss gcc -O3 -D__LINUX_OSS__ -O3 -fno-strict-aliasing -D__CK_SNDFILE_NATIVE__ -c RtAudio/RtAudio.cpp -o RtAudio/RtAudio.o RtAudio/RtAudio.cpp:6455:23: fatal error: soundcard.h: No such file or directory compilation terminated. make: *** [RtAudio/RtAudio.o] Error 1

3 4

multiple inheritance
by Julien Saint-Martin 05 Oct '12

05 Oct '12

Hi, Is it possible to extend a class from two parents classes? So the child class will have the data and functions of the two parents. I am not an oriented object programming expert, but I understand (maybe I am mistaking) that C++ is able to do that. At first I wanted to do a kind of extended SndBuf UGen including and playing automatically a score. The goal is to write short code like: MySndBuf s=> dac; 120 => s.bpm; s.score << 1 << 1 << 0 << 1; // write the score "kick.wav" => s.read; while(1) 10::ms => now; // let's play I made some quick testing, this is possible. But then appears the second Idea ;-) Sequencers are really useful so why do not have a basic sequencer common for other application. For example: // the Synth frequency driver MyFreqExtendStep f => TriOsc s => dac; f.note << 40 << 42 << 44 << 0; // Write score with midi note 120 => f.bpm; while(1) 10::ms => now; // let's play // The Event automatic boardcaster (to trig other scripts for example) MyEvent e; e.score << 1 << 1 << 0 << 1; // write the score 120 => e.bpm; while(1) 10::ms => now; // let's play Happy chucking, Ju

2 4

FM
by Alberto Alassio 05 Oct '12

05 Oct '12

Hi guys, I was looking at chuck manual, talking about LFO and then FM came to my mind. But...How? I was thinking to a very simple FM like this: 1) SinOsc alpha carrier 2) SinOsc beta modulator 3) SinOsc gamma beta's amplitude modulator So i thought something like this SinOsc alpha => dac; SinOsc beta => blackhole; SinOsc gamma => blackhole; then oscillators frequencies 220 => alpha.freq; 4 => gamma.freq; while (20::ms => now ) { (gamma.last () ) + 2 => beta.freq; in this way I've got my amplitude modulation on beta. Then I have to Beta.freq + alpha.freq => alpha.freq - Frequencies sum. - } This is just an idea..... Could it work ? And how can I make beta and alpha's sum? May I have to use fun like fun void ( int freqalpha, int freqbeta ) or something like this? Thankssssss

3 10

get hash keys from associative array
by George Locke 02 Oct '12

02 Oct '12

Hey, int hash[]; 0 => hash["zero"]; 1 => hash["one"]; hash.keys @=> string keys[]; Is there anything like this, some way for an associative array to tell you what keys it has? Ge apparently mentioned it as a development goal for 6 years ago ( https://lists.cs.princeton.edu/pipermail/chuck-users/2006-March/000436.html ), but searching for "key" in the versions page shows no update in this area. Thanks, George

3 3

Ugens for sound spatialization
by Wolfgang Gil 01 Oct '12

01 Oct '12

Hello Chuckers, I was wondering if there is anybody working on Ugens for sound spatialization or if there's any external library compatible with chuck for the same purpose. Best wishes, -- http://www.wolfganggil.com <http://www.wolfganggil.com/about> http://contoureditions.com/pages/about.html

1 0

Re: [chuck-users] Begin the beguine (Kassen)
by Perry Cook 01 Oct '12

01 Oct '12

Kas, So sorry for making my very personal confusing code public! The many lines per line is indeed me trying to optimize for screen space, grouping things together once I'm sure they're working. NOTE: Kids, don't do this yourselves. Only crusty old timers get to write code that looks unstructured and confusing :-) PICO actually refers not to the editor, but rather a whole series of small expressive controllers based on real-world objects I built back in the 90's. See: http://www.cs.princeton.edu/~prc/PICOSlide.jpg I do indeed use pico the editor, but one has nothing to do with the others. I have lately (Since NIME at CMU) taken to making a MAUI "Dashboard" for every controller I use, demo, (and hopefully every one I've ever made). The dashboard code checks for MIDI input, and if it's there it uses the data from the controller to update the controls on screen. This helps me debug the controller connections, individual sensors, battery, etc. If there is no MIDI seen, then the code switches over to just hanging out waiting for the user to move sliders and click buttons on the interface. This allows me to write and work on performance pieces on the airplane or other places where getting out the controller and plugging it in would be inconvenient (or get me arrested and sent to terrorist camp). PRC On Oct 1, 2012, at 9:00 AM, chuck-users-request(a)lists.cs.princeton.edu wrote: > Send chuck-users mailing list submissions to > chuck-users(a)lists.cs.princeton.edu > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > or, via email, send a message with subject or body 'help' to > chuck-users-request(a)lists.cs.princeton.edu > > You can reach the person managing the list at > chuck-users-owner(a)lists.cs.princeton.edu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chuck-users digest..." > > > Today's Topics: > > 1. Re: Begin the beguine (Alberto Alassio) (Kassen) > 2. Re: Begin the beguine (Alberto Alassio) (Alberto Alassio) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 1 Oct 2012 05:28:16 +0200 > From: Kassen <signal.automatique(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] Begin the beguine (Alberto Alassio) > Message-ID: <20121001032815.GF1526(a)gmail.com> > Content-Type: text/plain; charset=us-ascii > > On Sun, Sep 30, 2012 at 07:01:24PM -0700, Perry Cook wrote: >> Hey all, > > Hey Perry, >> >> I'll pipe in here with a set of course notes I put together for >> a workshop/tutorial on "Sonification in ChucK" It steps through >> chuck from Hello Sine through functions and built-in math.foo() and >> std.bar() functions through much more. > > Very nice indeed! > >> It is, I believe, the most short >> yet complete list of things you can and should do with ChucK. Not >> everything is explained, of course (it was only a 2 hour tutorial). > > I am curious about this; > http://www.cs.princeton.edu/~prc/ChucKU/Code/SonificationExamples/PICOBoxDa… > > I notice that you are quite often putting two or more lines of ChucK > code on a single screen line. Sometimes those statements are clearly > closely related pairs perhaps not worth a "for" loop, at other points > I'm left wondering. Are you optimising for fitting as many things as > possible on screen? That might make sense if "PICO" refers to the > editor which -from memory- supports a lot more than most think, but > not setting marks to jump to. > > No critique, genuinely curious. > > Yours, > Kas. > > > ------------------------------ > > Message: 2 > Date: Mon, 1 Oct 2012 10:58:19 +0200 > From: Alberto Alassio <alberto.alassio(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] Begin the beguine (Alberto Alassio) > Message-ID: > <CAHLGKcqrQTqTJVyW5F9g9KAHoU50sbpsaGHrPb4aMj_eq19YxQ(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > now that I know what it means I can say : yes! > > On Mon, Oct 1, 2012 at 4:21 AM, Renato Fabbri <renato.fabbri(a)gmail.com>wrote: > >> Alberto AlassioAA fan? >> http://wiki.nosdigitais.teia.org.br/AA_%28English%29 >> >> >> >> 2012/9/30 Perry Cook <prc(a)cs.princeton.edu> >> >>> Hey all, >>> >>> I'll pipe in here with a set of course notes I put together for >>> a workshop/tutorial on "Sonification in ChucK" It steps through >>> chuck from Hello Sine through functions and built-in math.foo() and >>> std.bar() functions through much more. It is, I believe, the most short >>> yet complete list of things you can and should do with ChucK. Not >>> everything is explained, of course (it was only a 2 hour tutorial). >>> >>> It's all on a sub-directory of my main web page called "ChucK U!" >>> >>> See: http://www.cs.princeton.edu/~prc/ChucKU/ >>> >>> The notes are at: >>> >>> http://www.cs.princeton.edu/~prc/ChucKU/SonifyingInChucKICAD2012.pdf >>> >>> but if you go to the main ChucKU page, you'll see code examples, links >>> to other things, etc. >>> >>> PRC >>> >>> >>> >>> _______________________________________________ >>> chuck-users mailing list >>> chuck-users(a)lists.cs.princeton.edu >>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >>> >> >> >> >> -- >> GNU/Linux User #479299 >> labmacambira.sf.net >> >> _______________________________________________ >> chuck-users mailing list >> chuck-users(a)lists.cs.princeton.edu >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >> >> >

2 1

Re: [chuck-users] Begin the beguine (Alberto Alassio)
by Perry Cook 01 Oct '12

01 Oct '12

Hey all, I'll pipe in here with a set of course notes I put together for a workshop/tutorial on "Sonification in ChucK" It steps through chuck from Hello Sine through functions and built-in math.foo() and std.bar() functions through much more. It is, I believe, the most short yet complete list of things you can and should do with ChucK. Not everything is explained, of course (it was only a 2 hour tutorial). It's all on a sub-directory of my main web page called "ChucK U!" See: http://www.cs.princeton.edu/~prc/ChucKU/ The notes are at: http://www.cs.princeton.edu/~prc/ChucKU/SonifyingInChucKICAD2012.pdf but if you go to the main ChucKU page, you'll see code examples, links to other things, etc. PRC

4 3

Begin the beguine
by Alberto Alassio 30 Sep '12

30 Sep '12

Hi guys this is my first thread because I've download Chuck just yesterday night and I'm trying to make something with this today (yes we can!). Really nice world! I read something from the manual ( the beginning tutorial) and also downloaded chuck pages where objects and other things about language are written. The question is : how can I understand every single line of Chuck? And I'm gonna make an example: foo.ck example. I was looking at this and also to other ones to understand how they work but... I saw that there are objects that are explained in Chuck homepage (sinOsc, delayD, etc) but where can I find informations about Std? Hi?How can I understand what does Hi.cap mean? These are just examples, is there a place where every command is explained? Or maybe (and probably) it's just me not so good searcher? Thank you everybody Balbit

5 23

Looping
by Alberto Alassio 27 Sep '12

27 Sep '12

I cannot understand how the while structure has to be used. I mean, I understood that while ( true ) means infinite loop and also that while ( n::second => now ) means an "n" second loop duration but... If I just want to do a really stupid thing like a Sine at 220 Hz that sounds for 2 seconds and then stops for 2 seconds and then goes again. How could I do? I thought that it was necessary just to do something like this SinOsc s => dac; .2 => s.gain; 220 => s.freq; while ( 2::second => now) 0 =>s.gain but I know that it's not the right way, also because in this method I would have to rewrite this thing an infinite ( whiletrue ahahah) number of times to have what I'm looking for. And I don't actually understand {} . How am I supposed to use these? Thanks

4 13