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

Problems building miniAudicle on Arch Linux
by Phil Thomson 18 Aug '12

18 Aug '12

Hi all, I am trying to build miniaudicle from source on Arch Linux and having a lot of trouble. I first tried building from an Arch package in the Arch User Repository (http://aur.archlinux.org/packages.php?ID=34472), but I get this error when running makepkg: [snip] g++ -o chuck chuck.tab.o chuck.yy.o chuck_absyn.o chuck_parse.o chuck_errmsg.o chuck_frame.o chuck_symbol.o chuck_table.o chuck_utils.o chuck_vm.o chuck_instr.o chuck_scan.o chuck_type.o chuck_emit.o chuck_compile.o chuck_dl.o chuck_oo.o chuck_lang.o chuck_ugen.o chuck_main.o chuck_otf.o chuck_stats.o chuck_bbq.o chuck_shell.o chuck_console.o chuck_globals.o digiio_rtaudio.o hidio_sdl.o midiio_rtmidi.o rtaudio.o rtmidi.o ugen_osc.o ugen_filter.o ugen_stk.o ugen_xxx.o ulib_machine.o ulib_math.o ulib_std.o ulib_opsc.o util_buffers.o util_console.o util_string.o util_thread.o util_opsc.o util_math.o util_network.o util_raw.o util_xforms.o util_hid.o uana_xform.o uana_extract.o -lasound -ljack -lstdc++ -ldl -lm -lsndfile/usr/bin/ld: chuck_main.o: undefined reference to symbol 'pthread_create@@GLIBC_2.1'/usr/bin/ld: note: 'pthread_create@@GLIBC_2.1' is defined in DSO /usr/lib/libpthread.so.0 so try adding it to the linker command line/usr/lib/libpthread.so.0: could not read symbols: Invalid operationcollect2: error: ld returned 1 exit statusmake[1]: *** [chuck] Error 1make[1]: Leaving directory `/home/phil/aur/miniaudicle/src/miniAudicle-0.2.0/chuck-1.2.1.3/src' make: *** [chuck] Error 2 ==> ERROR: A failure occurred in build(). Aborting... When I try to build straight from source (make linux-jack), I get this: [snip] g++ -o chuck chuck.tab.o chuck.yy.o chuck_absyn.o chuck_parse.o chuck_errmsg.o chuck_frame.o chuck_symbol.o chuck_table.o chuck_utils.o chuck_vm.o chuck_instr.o chuck_scan.o chuck_type.o chuck_emit.o chuck_compile.o chuck_dl.o chuck_oo.o chuck_lang.o chuck_ugen.o chuck_main.o chuck_otf.o chuck_stats.o chuck_bbq.o chuck_shell.o chuck_console.o chuck_globals.o digiio_rtaudio.o hidio_sdl.o midiio_rtmidi.o rtaudio.o rtmidi.o ugen_osc.o ugen_filter.o ugen_stk.o ugen_xxx.o ulib_machine.o ulib_math.o ulib_std.o ulib_opsc.o util_buffers.o util_console.o util_string.o util_thread.o util_opsc.o util_math.o util_network.o util_raw.o util_xforms.o util_hid.o uana_xform.o uana_extract.o -lasound -ljack -lstdc++ -ldl -lm -lsndfile/usr/bin/ld: chuck_main.o: undefined reference to symbol 'pthread_create@@GLIBC_2.1' /usr/bin/ld: note: 'pthread_create@@GLIBC_2.1' is defined in DSO /usr/lib/libpthread.so.0 so try adding it to the linker command line/usr/lib/libpthread.so.0: could not read symbols: Invalid operationcollect2: error: ld returned 1 exit statusmake[2]: *** [chuck] Error 1make[2]: Leaving directory `/home/phil/src/miniAudicle-0.2.0/chuck-1.2.1.3/src'make[1]: *** [chuck] Error 2make[1]: Leaving directory `/home/phil/src/miniAudicle-0.2.0' make: [linux-jack] Error 2 (ignored) My version of wxgtk is 2.8.12.1-3, if that matters. Any thoughts? Thanks in advance! -- Phil Thomson http://philthomson.ca/

2 1

Re: [chuck-users] chuck vs supercollider?
by Perry Cook 13 Aug '12

13 Aug '12

OK, I'll chime in here. Both languages are Turing complete, so anything logic- wise can be done in either. The ability to compute control, physical simulations, and/or samples at any time resolution, even sub sample, is super powerful from an experimental and philosophical perspective. Single sample computation does allow for feedback, and even parallel patches, that are not possible or indeterminant with vectorized (block), computation. And even delay-free loops (needed for some algorithms, like physical simulations) can be more accurately approximated with sub-sample computation. Efficiency is an issue. A more appropriate Ge quote, which came from Paul Lansky, is "never optimize." Ge set out to make ChucK unlike any other language, and efficiency was not a priority. Roger Dannenberg even was swayed, stating that ChucK isn't that inefficient, especially given the power it gives the programmer. One other really nice ChucK tool is the MiniAudicle. Some don't care for it, or don't see the point, but having a smart editor, monitor, shred manager, etc is reall powerful for development and real-time live coding. I don't know if SC has such a real-time IDE. Prc Sent from my iPad :-) On Aug 10, 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: chuck vs supercollider? (Kassen) > 2. Re: chuck vs supercollider? (Michael Clemow) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 10 Aug 2012 13:33:30 +0200 > From: Kassen <signal.automatique(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] chuck vs supercollider? > Message-ID: > <CAK4G45dVa3Z0iRXhzXUfx6VoMX68pV3+gdCj+S20f=ByEL+6Jw(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On 10 August 2012 04:11, David Ogborn <ogbornd(a)mcmaster.ca> wrote: >> Great answer - I'm going to save it and quote it whenever needed! :) >> > > Thanks Dan & David, > > Credit where it's due; this was more or less the conclusion of the > debates I had with SC expert James 'DewdropWorld' Harkins. > We found that the differences we and others with some expertise noted > didn't really matter at all for those picking up either language. > New users (who adopt either) simply seem to find that one is quite > straightforward and the other doesn't make a lot of sense. We didn't > notice any obvious structure or pattern in that. It's a interesting > phenomenon. > > It'd be nice to try to figure out whether things like lessons or > online tutorials, examples or more experienced friends influence this. > What I can tell though is that passionate online debates don't seem to > have any effect on this at all; they can take away misconceptions > about what is possible but not change what people find fun or easy. > > Yours, > Kas. > > > ------------------------------ > > Message: 2 > Date: Fri, 10 Aug 2012 10:19:03 -0400 > From: Michael Clemow <michaelclemow(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] chuck vs supercollider? > Message-ID: <510685F450A1428CB304BD1B4460CF4F(a)gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hey All, > > FWIW, I often take advantage of both systems in a piece. Sometimes I'll create a bunch of synths in SC that can be triggered by OSC and use Chuck as a score language. If I'm doing a lot of string/data processing, then I'll use Python to trigger them. But that's part of my practice, since many of my pieces involve interesting bits of hardware, I have to utilize OSCulator, SC, Chuck, and Puredata all for one piece of music. > > So, for the sake of completeness, I'll back the notion that you don't actually have to make an exclusive choice between environments. ;) The right tool for the job, right? > > -Mike > > -- > Michael Clemow > > http://michaelclemow.com > http://abattoirprojects.com > > > On Friday, August 10, 2012 at 7:33 AM, Kassen wrote: > >> On 10 August 2012 04:11, David Ogborn <ogbornd(a)mcmaster.ca (mailto:ogbornd@mcmaster.ca)> wrote: >>> Great answer - I'm going to save it and quote it whenever needed! :) >> >> >> Thanks Dan & David, >> >> Credit where it's due; this was more or less the conclusion of the >> debates I had with SC expert James 'DewdropWorld' Harkins. >> We found that the differences we and others with some expertise noted >> didn't really matter at all for those picking up either language. >> New users (who adopt either) simply seem to find that one is quite >> straightforward and the other doesn't make a lot of sense. We didn't >> notice any obvious structure or pattern in that. It's a interesting >> phenomenon. >> >> It'd be nice to try to figure out whether things like lessons or >> online tutorials, examples or more experienced friends influence this. >> What I can tell though is that passionate online debates don't seem to >> have any effect on this at all; they can take away misconceptions >> about what is possible but not change what people find fun or easy. >> >> Yours, >> Kas. >> _______________________________________________ >> chuck-users mailing list >> chuck-users(a)lists.cs.princeton.edu (mailto:chuck-users@lists.cs.princeton.edu) >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >> >> > > >

3 2

comparing fm in chuck an sc3
by ronni montoya 13 Aug '12

13 Aug '12

Hi, I was trying to recreate a simple fm synth in sc3 and chuck , so i can be able to compare the sounds of both. Is there any sc3 users in this list? i ve made this version of the fm code from chuck web site but it sounds so different. I was wondering maybe i made anything wrong? I was wondering also if doing this in chuck " m.last()" will be the same as "mod " in sc3? thanks. R. here is the code. Chuck: // FM synthesis by hand // carrier SinOsc c => dac; // modulator SinOsc m => blackhole; // carrier frequency 220 => float cf; // modulator frequency 550 => float mf => m.freq; // index of modulation 200 => float index; // time-loop while( true ) { // modulate cf + (index * m.last()) => c.freq; // advance time by 1 samp 1::samp => now; } Supercollider: ( SynthDef("fm1", { arg bus = 0, freq = 440, index = 200, mul = 0.05; var mod; var car; mod = SinOsc.ar( 550, 0, 1 ); car = SinOsc.ar( freq + (index * mod) , 0, mul ); Out.ar(bus,car) }).load(s); ) Synth("fm1");

2 1

Call for Participation: live.code.festival @ IMWI Karlsruhe
by David Ogborn 13 Aug '12

13 Aug '12

Begin forwarded message: > From: "Juan A. Romero" <rukano(a)gmail.com> > Subject: [livecode] Call for Participation: live.code.festival @ IMWI Karlsruhe > Date: 13 August, 2012 6:22:41 AM EDT > To: livecode(a)toplap.org > Reply-To: livecode(a)toplap.org > > *** Apologies for Multiple Posting *** > > Call for participants for the international live coding festival to be held at the University of Music Karlsruhe, Germany. > > ================================================================= > Dates: 19. - 21. April 2013 > Venue: University of Music Karlsruhe, Germany > Deadline for submission: 15th November 2012 > Website: http://imwi.hfm.eu/livecode/ > ================================================================= > > The live.code.festival will take place at the Institute for Musicology and Music Informatics (IMWI), University of Music Karlsruhe from 19th to 21th of April in 2013, organized by the IMWI, the local live coding band Benoît and the Mandelbrots and members of the live coding organization TOPLAP. It will be a weekend dedicated to this emerging discipline of computer music, to exchange ideas, demonstrate systems, enjoy concerts and establish connections between people and institutions interested in research and performance of live coding. Although the main focus of the festival is live coding of audio the festival will promote live coding in other disciplines as well. > > The festival will include live coding concerts and performances, talks, demonstrations, discussion panels, opportunities for collective improvisations and get-togethers. > > More information about deadlines, submissions and topics at http://imwi.hfm.eu/livecode ------------------------------------------------------------------- Dr. David Ogborn, Assistant Professor Communication Studies & Multimedia Director, Cybernetic Orchestra & ESP Studio McMaster University, Hamilton, Canada ogbornd --at-- mcmaster.ca http://davidogborn.net http://twitter.com/ogbornd http://esp.mcmaster.ca (Cybernetic Orchestra) 1-905-525-9140 ext 27603

1 0

chuck vs supercollider?
by ronni montoya 12 Aug '12

12 Aug '12

Hi, i was wondering, is there any benefit in chuck approach having one sample block size comparing with supercollider ? are there things that can be done with chuck that cannot be done with sc3? what do you think? Ronni

7 17

Re: [chuck-users] Sending raw midi / sysex
by Julian Faust 09 Aug '12

09 Aug '12

Success! Breaking 17 values into 6 triplets worked, with the data3 of the 6th being ignored. The first and last value mark the start and end of the sysex message, which I guess is why it works. Thankfully I only need to send and not receive these crazy messages. I'm playing around with a Livid Block and this allows me to set the state of all 64 lights with just 6 midi messages, instead of 64. I'm thinking this could make a difference in performance for something like making all the lights blink really fast, though that will also depend on if it prioritizes notes over sysex or something. -Julian

2 1

Sending raw midi / sysex
by Julian Faust 08 Aug '12

08 Aug '12

Hi all, Is it possible to send arbitrary midi messages like F0 00 01 61 03 04 7F 7F 7F 7F 7F 7F 7F 7F 7F 7F F7 (for example) ? I understand that you can work with hex, but it seems that MidiMsg is fixed at 3 data slots, and MidiIn and MidiOut interface via MidiMsg. Is there any way to use MidiOut without MidiMsg? Or possibly overload the class with a more flexible message holder? Cheers, Julian

4 5

MIDI tutorial problem
by Peter Lutek 07 Aug '12

07 Aug '12

BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }greetings! a chuck novice here, so likely some silly user error!.... ;-) working through the tutorials in the pdf manual, when following the Getting MIDI section, if i do this... MidiIn min; if( !min.open(1) ) { me.exit(); } while(true){ min => now; while( min.recv(msg) ){ ; } } ...chuck throws me an "undefined variable 'msg'..." error! something i'm missing? recent change in MIDI syntax? (i'm on chuck v1.2.1.3 on linux) "chuck --probe" does show my desired MIDI interface as "1". thanks in advance... cheers! .pltk.

3 2

waveform generation by function
by Sample Hampton 06 Aug '12

06 Aug '12

Users, What is the best way to do waveform generation--one sample at time of course--with math functions? First I tried chucking a variable straight to the dac, but it didn't take. Then I tried chucking a variable to the value of a Step, and chucking the Step to the dac. That did work, and below I have a simple lpf'ed sawtooth going. Is there, however, a more conventional and direct way of doing this? Step taint => LPF passer => dac; 400 => passer.freq; -0.2 => float v; while(true) { v + 0.004 => v; if (v > 0.2) { -0.2 => v; } v => taint.next; 1::samp => now; } Sample

2 3

Time doubt...
by John Gamboa 01 Aug '12

01 Aug '12

Hello Chuckist... I'm relatively new to Chuck -- although I've already used it some time ago -- and I have a doubt about how the time works in the VM. I was reading the Ge's PhD Thesis and I found this part: A ChucK shred must voluntarily relinquish the processor for other shreds to > run (In this they are like non-preemptive threads). [...] Shreds, by > design, > directly use ChucK’s timing mechanism: when a shred advances time or waits > for an event, it is, in effect, shreduled by the shreduler (which > interacts with > the audio engine), and relinquishes the processor. This is powerful in that > it can naturally synchronize shreds to each other by time, without using > any > traditional synchronization primitives. > My question is: if two threads try to change the same variable at the same time ("rounded" to the nearest sample), what is the expected behavior of the program? I tried to take a look at the code of the VM, but I couldn't understand exactly what would happen at that point D=. I imagine that the occurrence of such event is very unlikely (there are "a lot" of samples in one second), but supposing that the computation in Chuck really takes "no time" to happen (as the thesis often reforced), I believe it would happen soon or later. Anyway, I have right now [at least some] interest at how the shreduler works, so I'm possibly gonna spend some time trying to understand exactly what happens at that file. If you have some tip on where I should start, it would make me very happy =) -- John Gamboa rabanetescebolas.blogspot.com

3 3