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

pointing the ChucK Homepage to the new WIKI
by Mike McGonagle 26 Feb '06

26 Feb '06

Hello Ge, Thanks for all the hard work in getting the WIKI updated. I was noticing that on the home page for ChucK, it still points to the old one. Just thought it might be a good time to update that... Thanks again, Mike

3 4

New WIKI functional
by Adam Tindale 22 Feb '06

22 Feb '06

Hello All, Ge and I have been working for most of the day making the new WIKI functional. Please take a look and make some suggestions. We would love it if you would post some of your code or audio. Also, take a look at the old WIKI and see if we missed anything. We have moved some v1.1.x programs out of the way. If they are yours then maybe could upload your 1.2.x compatible versions. We would like to make the full switch in a day or two. With your help we should be able to do it. NEW http://wiki-new.cs.princeton.edu/index.php/ChucK OLD http://wiki.cs.princeton.edu/index.php/ChucK --art

1 0

Chucking scores
by Pedro Lopez-Cabanillas 21 Feb '06

21 Feb '06

Hi all, I've written a little article on the subject, that you can find here: http://www.telefonica.net/web/plcl/chuck/ There are also some merry melodies for ChucK. Hope you enjoy it. I would like to hear your opinion about everything, the music, the proposal, and the wording. Sorry for my poor English, BTW. Regards, Pedro

3 7

wiki upgrade and transfer
by Ge Wang 21 Feb '06

21 Feb '06

Hello again, Our ever-hardworking system staff has upgraded the wiki to a new version of mediawiki and also added more rigorous measures to prevent spammers from defacing the wiki. The upgraded wiki is temporarily at: http://wiki-new.cs.princeton.edu/ http://wiki-new.cs.princeton.edu/index.php/ChucK The existing wiki will remain at the current URL until we make the switch: http://wiki.cs.princeton.edu/ http://wiki.cs.princeton.edu/index.php/ChucK The new wiki requires one to be logged in before he/she can edit a page. Furthermore, the registration page now has a CAPTCHA feature to help prevent bots. I guess this would be a good time to start moving contents from the old wiki to the new and doing some housecleaning. 1. I think the <pre> tags now work, but it may be better to denote code by inserting spaces before each line, like in the page: http://wiki.cs.princeton.edu/index.php/FractalMelody 2. Some or maybe most of the page could use some organizing and updating. Perhaps the ChucK_Programs page can benefit from some basic categorization. 3.The upload feature seems to be enabled for now, though I am not sure if this will be permanet. I will find out. 4. We will switch over to the new wiki probably early next week. (just the URL change from wiki -> wiki-old, and from wiki-new -> wiki) 5. Use the talk page to avoid collisions on edit. The talk page is accessible via the 'discussion' link on the top. Ready? Everyone of course is invited to contribute. Adam T. and Mike M. might want to coordinate this? Best, Ge!

2 2

Re: [chuck-users] Joysticks anyone?
by Scot Gresham-Lancaster 20 Feb '06

20 Feb '06

While waiting for HID implementation on could use STEIM's JUNXION software which maps HID to MIDI. It works fine with a wide variety of input devices from my experience. http://www.steim.org/steim/products.html " junXion © is a software tool to process incoming data from USB devices (joysticks, touchscreens, mice) and MIDI devices using conditional processing and remapping. The outputted data can be routed to other MIDI controllable music and sound software or hardware." An HID interface inside of chuck would be great, of course ;-) Scot Gresham-Lancaster ¸,ø¤º°`°º¤ø¸,ø¤º°`°º¤ø http://o-art.org/Scot podcast: http://feeds.feedburner.com/blogspot/scotgl blog: http://scotgl.blogspot.com/ Quine in Br@!nF*ck ->++>+++>+>+>+++>>>>>>>>>>>>>>>>>>>>>>+>+>++>+++>++>>+++> +>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>+>+>>+++>>>>+++>>>+++>+>>>>>>>++>+++>+++>+>+++>+>>+++>>>++ +>+>++>+++> >>+>+>+>+>++>+++>+>+>>+++>>>>>>>+>+>>>+>+>++>+++>+++>+>>+++>+++>+>++ +>+>++>+++>+ +>>+>+>++>+++>+>+>>+++>>>+++>+>>>++>+++>+++>+>>+++>>>+++>+>+++>+>>++ +>>+++>>+[[> >+[>]+>+[<]<-]>>[>]<+<+++[<]<<+]>+[>>]+++>+[+[<++++++++++++++++>-]<++ ++++++++.<]

1 0

benchmarking chuck
by Graham Percival 20 Feb '06

20 Feb '06

Hi guys, I've discovered that I can only get 47 sine waves on my system (1 ghz G4 powerbook, 512 megs ram, OSX 10.3.9). I'm curious how other systems compare -- particularly on linux. If chuck works much better on linux, I may switch back to it... Here's the code. I ran it twice (in case there was any caching issue) and listened to the sound. With 48 waves, I could hear crackling; with 50 waves, it was unrecognizable. Cheers, - Graham 48=>int NUMSINS; sinosc s[NUMSINS]; for (0=>int i; i<s.cap();i++) { // s[i] => blackhole; s[i] => dac; 440 => s[i].freq; 0.01 => s[i].gain; } 5::second=>now;

8 12

Joysticks anyone?
by Jim Hinds 20 Feb '06

20 Feb '06

I was caught bragging to my peers (all of them) about how cool chuck is to do performance and real-time good stuff. One asked me about joystick interfaces into chuck and I blanked out. I didn't have an answer -- I should have. So, does anybody know how to read a joystick and get the info into (or through) chuck? Even a Rube Goldberg approach might help me here, although extra credit is given for simplicity and elegance. If the answer only worked on the Mac OS X implementation, that would be just fine. Jim

5 4

Re: chuck-users Digest, Vol 7, Issue 11
by Scot Gresham-Lancaster 17 Feb '06

17 Feb '06

This feels like a real simple problem, but I can not suss it out. In the chuck archive: > Julian Sorrel tacitdynamite at yahoo.com Wed Jan 25 17:05:25 EST > 2006 wrote: > > chuck D:\Chuck\examples\otf_06.ck > (using otf_06.ck here because it doesn't require external sound > files) > this works fine - I hear Chuck playing the file. When I try > chuck D:\Chuck\examples\otf_07.ck > the result is > [chuck](via sndbuf): cannot stat file 'data/snare.wav' ... > even though, again, that file can be found in "dir D:\Chuck > \examples\data" ... This was on an XP machine, but I am getting the same result on my mac and linux boxes. If I put in the full path these sndbuf objects function fine, but if I use a relative address such as "../data/ foo.wav" I get the "cannot stat file 'data/foo.wav' What is the obvious error that I am making? Also, stat? Is that supposed to be start? tocs_backwards Scot Gresham-Lancaster ¸,ø¤º°`°º¤ø¸,ø¤º°`°º¤ø http://o-art.org/Scot podcast: http://feeds.feedburner.com/blogspot/scotgl blog: http://scotgl.blogspot.com/ " Well, I let it play itself as much as I can, but if it doesn't, then I interfere. " David Tudor

3 2

comments, questions about chuck
by Charlls Quarra 16 Feb '06

16 Feb '06

Hi, I wanted to comment about things that i don't find yet on chuck which i would prioritize; please, take this freely as some brainstorming from a guy that has been using SuperCollider3 for some time and finds appealing the sample-accurate emphasis in Chuck. * ugen/plugin infrastructure; what headers you include? what classes you inherit? *block processing; i find amazing the feeling of putting your code directly into the sample stream, but i realize that it comes with a price; but before talking about block processing i wanted to ask first about; *** how much multithread-eable could be chuck; in other words, how possible is to implement shreds in a true multithreaded mode where each shred can run in a different core, but keeping the sample-synchronous approach? i imagine one could relax that to a "block-synchronous" multi-shreding. Currently one could have a chuck instance per core and pipe outs and in thru jack, but this would fix the block frame size to whatever jack is set to. * dynamic allocation of resources; of course, this could be implemented on top of the language; for example, creating a fixed number of audio buffers and calling .read as a score progresses a number of times in the same sndbuf object would (i imagine) free the previous allocated buffer and alloc for the new one. --------------------------------- 1GB gratis, Antivirus y Antispam Correo Yahoo!, el mejor correo web del mundo Abrí tu cuenta aquí

4 9

sndbuf.valueAtPos
by Charlls Quarra 13 Feb '06

13 Feb '06

Hi, I think a way to look ahead buffer values ahead could help solve a few issues, like avoid popping when a buffer jump is done; while (true) ... if (must_jump) { if ( std.fabs( buf.last() - buf.valueAtPos( toPos ) )< 0.01 ) { toPos => buf.pos; false => must_jump; } } ... 100::ms => now; --------------------------------- ¡Llamá a todo el mundo con las mejores tarifas! Comprá tus tarjetas de llamadas en tres simples pasos en Yahoo! Telefonía

2 1