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

For Dan
by Kassen 18 Jun '10

18 Jun '10

Fellow ChucKists, Yesterday I wanted to wish Dan a happy birthday on FaceBook, hoping for many more years of fun with strings and code but thought it'd be nicer to write this in ChucK. Then stuff happened and I was too late. Belated but no less sincere; emulating strings in LiSa... because we can, and because LiSa can (LiSa can actually do anything, she's just modest). We start out with a very literal implementation of Karplus-Strong at concert A4 tuning. Then we start mucking with various parameters in ways that are less traditionally Karplus-Strong for some more interesting tembral effects. Yours, Kas. /* Do copy, do share. No warranties, no refunds. Physical models can (and will!) blow up; please mind your speakers, neighbours and pets. Remixing and sharing results strongly encouraged (many parameters left....). Happy belated birthday to Dan! */ //the patch (noise or a saw plus a envelope could emulate a bow instead of a pluck) Impulse i => LiSa l => dac; //needs to be defined second => l.duration; //two voices for averaging 2 => l.maxVoices; //buffer duration = source of the pitch second / 440 => dur base_cycle; //create a looping delay //looping for both recording and playback is on by default base_cycle => l.loopEndRec; l.loopEnd (0, base_cycle); l.loopEnd (1, base_cycle); 1 => l.record; //offset the second voice by one sample //so we average between the current and the last sample value l.play (0, 1); l.playPos (1, -1 * samp); //"::" should work here but gives me a error? [BUG] l.play( 1, 1); //average between the two values. ratio sets the "filter's" effect. //make sure the two add up to unity (1.0). l.voiceGain (0, .5); l.voiceGain (1, .5); //feedback sets the tone's decay .995 => l.feedback; //off we go! 1 => i.next; 2::second => now; //tradition ends here. //fun starts l.loopEnd (1, base_cycle * .5); 1 => i.next; 2::second => now; l.loopEnd (1, base_cycle * 2); 1 => i.next; 2::second => now; l.loopEnd (1, base_cycle * .333333); 1 => i.next; 2::second => now; l.loopEnd (1, base_cycle * 1.5); 1 => i.next; 2::second => now; l.loopEndRec() * 2 => l.loopEndRec; l.loopEnd (1, base_cycle - samp); 1 => i.next; 4::second => now;

2 2

Latency measurement for ChucK
by Yonghao Wang 18 Jun '10

18 Jun '10

Hello All, I am new to ChucK but I've found it is very interesting and intuitive tool! I am interested in Latency issues of audio host. I've measured latencies on various hosts on standard Mac hardware (with on-board Intel HDA standard soundcard) with WindowsXP/MacOSx/Linux etc. So far linux has lowest overhead processing latency and also consistent as good as Mac or even better. I've tested ChucK on Mac OSX. The code I used is standard ADC one (http://chuck.cs.princeton.edu/doc/examples/basic/adc.ck) Buffer setting -> measured latency 16 samples -> 5ms 256 samples -> 20ms 512 samples -> 37ms In the console log messages, it always says: number of buffers 8. At sampling frequency of 44100Hz, so in theory: latency = (1/fs)*buffersize*8 16 samples -> 2.9 ms 256 samples -> 46.4 ms 512 samples -> 92.9 ms These two group of data doesn't seem consistent. I guess the buffer structure in ChucK is quite different with other audio hosts (normally they have both input buffer and output buffer). I am not quite understand the maths, can anyone give me some clue? How are the 8 buffers in ChucK arranged? I guess some buffers are in parallel otherwise the theoretical values wont be greater then measured values? I will try to test it on Linux/Jack soon that may be more consistent in terms of latency. Many thanks Y.Wang

1 0

code reusability
by Thomas Girod 16 Jun '10

16 Jun '10

Hi there. I'm currently working on a chuck project that is progressively increasing in size. Some parts of this project are already quite generic, and I will probably use them in other projects later (namely, an interface to communicate with the novation's monome ripoff). So I start to wonder: how can I organize my code for easy reuse ? What are the options / good practices to write less monolithic chuck code ? Is it possible to write something that could behave as a library ? Thanks for your attention Tom

8 18

launchpad class + mlr clone
by Thomas Girod 12 Jun '10

12 Jun '10

Hi fellow chuckers. this is my first contribution to the community - Hopefully some of you will find it useful / fun. http://github.com/jiyunatori/chuck launchpad.ck defines a class to interact with the Novation Launchpad controller. Right now it is far from complete, but the most important stuff is working: listening to press/release events, and controlling the LEDs. mluck.ck is a very basic clone of the excellent mlr app for the monome (http://docs.monome.org/doku.php?id=app:mlr), adapted to the launchpad. What it is doing: - play 8 pre-recorded loops in parallel (one per line) - jump around each loop with the main grid buttons - play/stop each loop with the scene buttons Feedbacks are welcomed ! enjoy Tom

2 1

sharing code
by Thomas Girod 12 Jun '10

12 Jun '10

Hi there. I would like to share some code I wrote with the community, so I turned to the wiki. but apparently, the registrations are restricted right now. Is it possible to have an account ? Is there another place where I should drop my code ? tom

2 1

Re: [chuck-users] chuck-users Digest, Vol 58, Issue 20
by jkZh 04 Jun '10

04 Jun '10

are there any illustration of installation or use this language to find at your web site? I visit the web site, but can't access to mov file with media player.

2 1

Running chuck
by Tom Aizenberg 02 Jun '10

02 Jun '10

Hi all, When I run ChucK from the console ChucK sometimes stops when the console doesn't have focus. Has anybody got an idea how to fix this? Thanks, Tom

1 0

input | chuck <read_stdin_and_do_stuff>
by v4hn 02 Jun '10

02 Jun '10

good ev'ning everyone, some time ago I showed ChucK to my girlfriend and she has been quite enthusiastic about it since then. So thanks for providing this interpreter! Well, right now she's coding a automatic composition tool(in python), which generates some (midi) numbers and prints them on the screen. Since this will be an any-time algorithm, the (actually quite simple) task for the audible back-end - which (she insists) should be written in ChucK - is to read the numbers from standard input and generate matching sounds. So the use-case would look like this: > ./compose | chuck play_composition.ck RTFM and RTFS got me to ConsoleInput and FileIO with the second not being able to connect to stdin. At the moment the only - quite hacked - way (AFAICS) to read /anything/ from stdin looks like this: <<< ConsoleInput in; while(true){ in.prompt(); line= in.getLine(); ... } >>> This doesn't realize EOFs, but keeps waiting, does it? And since FileIO provides a readInt() function, it would be nice to use it in this case... Is there a way, to read from stdin through some IO-Interface of ChucK or anything else 'official' - aka not stating in the source that it's just something hacked? If not, are there any ideas on implementing this in Version 1.2.1.4 ? Well, that's for now, regards, v4hn

5 5

Re: [chuck-users] bug in miniAudicle?
by Maurits Lamers 27 May '10

27 May '10

Hi, I'll try to give an example as soon as I have the time to do so :) greets Maurits > From: Kassen <signal.automatique(a)gmail.com> > Date: 25 May 2010 22:53:32 GMT+02:00 > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] bug in miniAudicle? > Reply-To: ChucK Users Mailing List <chuck- > users(a)lists.cs.princeton.edu> > > > Tom; > > > Do you have an example? I've never seen this problem. This works for > me: > > > I'm sure; as noted it "worked" like that in my little LAC workshop. > > This was running on OSX (not sure about the version) with a stock > version of the mini, freshly downloaded for the occasion. Maurits > had some Java experience so he started using block-comments on his > own. I actually assumed this must be a common/known bug on OSX, that > was just unknown to me as I don't have a OSX machine but still > suggested a bug-report as that was a nice chance to go into bug > reporting as a essential ChucKist skill. > > Yours, > Kas.

1 0

Filters blowing up: any news?
by Tomasz Kaye's brain 25 May '10

25 May '10

At the end of November last year I posted to the list about a problem experiencing where chucks filters (lp, bpf etc) 'blow up' under certain conditions. Here's the archived post: https://lists.cs.princeton.edu/pipermail/chuck-users/2009-November/005045.h… I wondered if anyone has made any progress with finding a solution and/or figuring out exactly what was causing this. In a couple of months I'll be performing with a synthesis environment that I was part way through creating in ChucK before I ran into the filter bug. I'm hoping that I don't have to switch back to max/msp to go further (i much prefer the chuck environment), so I thought i'd give this one more bump on the list to see if there may be a fix in SCM, or otherwise in the pipeline somehow. If anyone is able to fix this I'd be extremely grateful!

9 23