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

String as an argument...
by Dimitri 08 Oct '08

08 Oct '08

Hey guys, first time posting here; short-time reader :) I've run into a bit of trouble programming a function to fade a ugen in or out. The code below will work nicely on g.gain however I can't abstract it to affect anything else without controlling the reference object, in this case *'g.' * The input is time 'x' in number of seconds. //==============================================// function void fadeOut(int x) { 1 => float master; x * 1000 => int top; for( 0 => int i ; i < top; i++ ) { if (master > 0) master - (master / (top * .2 )) => master => *g *.gain; 1::ms => now; } } //==============================================// Obviously the below would be my desired function, but even delving through ChucK's string class, it doesn't seem that there's a function to return an object reference from a string... //==============================================// function void fadeIn(int x, *string y*) { .01 => float master; x * 1000 => int top; for( 0 => int i ; i < top; i++ ) { if (master < 1) master + (master / (top * .2)) => master => *y*.gain; 1::ms => now; } } //==============================================// Am I crazy for thinking something like this would be useful? If anyone could offer some insight, even to a possible workaround, I'm all ears! Cheers, Dimitri. -- Duc, sequere, aut de via decede.

2 1

what a nice guy...
by Brad Garton 08 Oct '08

08 Oct '08

I saw this on the SC mailing list: http://gilesbowkett.blogspot.com/2008/09/fuck-chuck.html Too bad none of us are Real Musicians. brad http://music.columbia.edu/~brad

7 11

SoundFonts in ChucK
by Tom Lieber 06 Oct '08

06 Oct '08

I've confirmed that Kyle Super's code for using SoundFonts in ChucK is working with version 1.2.1.2 in OS X, and it is said to work in Linux as well. These are the steps I took to install: 1) Download and install FluidSynth from <http://fluidsynth.resonance.org/trac/wiki/Download>. I installed version 1.0.8 from source with "./configure && make && sudo make install" 2) Apply the attached diff to chuck 1.2.1.2. 3) Compile ChucK with "make osx". If on Linux, build with "make alsa". -- Tom Lieber http://AllTom.com/

3 8

(no subject)
by inventor-66＠comcast.net 04 Oct '08

04 Oct '08

Kassen, I will look into tools for EChucK, though I suspect it will be a mix of assembler and C tools due to the chaotic and buggy nature of Microchip tools. It doesn't look like there is popular enough support for EChucK to justify having its own sub-forum. Lots of reads but few posts, so I doubt if it needs its own sub-forum just yet. I emailed Ge as you suggest about the name and copied to you. Thanks, Les Dear Les, Some suggestions; *If you are going the PIC route you may need to start thinking about a SDK. Some of my best friends think ASM is fun but then again... I tend to hang out with relatively unusual people. *This is veering a bit off-topic; not all ChucKists will be interested in this and not everyone who is interested in this will be interested in ChucK. I suggest you ask Mosc for your own sub-forum on EM for this project. You are already linking to EM on your page about this and Mosc is very supportive of open DIY projects. If you don't have it I could give you his address. * I'd sugest you ask Ge about using the ChucK name for something related yet different like this. I could imagine using something like "SticK", a name that would refer to a possible result of "ChucKing" some object, it could refer to sticking objects to eachother and it might refer to educational uses as well. Something like that could save confusion. These are purely my own personal opinions at this moment but right now I feel this idea is evolving into something that does -and can- stand on it's own. I suspect a aproach like that could improve things for everyone; this is note some veiled way of saying "stay on topic"; I'll be keeping a close eye on this regardless of how and where it evolves. Yours, Kas.

1 0

Re: [chuck-users] Electronic ChucK
by inventor-66＠comcast.net 04 Oct '08

04 Oct '08

Mike, I'm open to any digital control interface that anyone wants to use. Although I do have to define *some* standards, I'm trying to be as open and flexible as possible. If you've got an Arduino and you want to connect it to EChucK, then I say go for it. Just make sure you know what you are doing and don't fry another module, haha. Now having said that, I'm planning to actually *sell* PIC processor boards. The dsPIC I have chosen is $3 US in low quantities direct from Microchip, and for that you get a stand-alone 40 MIPs DSP with 6 channels of oversampled audio in and a few PWM outputs. That's a lot of processor for three bucks and it is only 18 pins so it is small too. The dsPIC is my next circuit board, and it will be programmable to be a do-it-all module. Whatever you need, a SinOsc, an FFT/IFFT class, a delay line, a multiplier - if you can program it then you can load up one of those modules to do the job. So some of the more digitally inclined folks will buy a bunch of dsPIC modules and code them up. Others will prefer to buy true analog modules, both will be available. Now, since folks will be learning and using PICs, natually the PIC interface products like USB, UART, RF, etc. will become product options. But that doesn't mean you can't use an Arduino if you want to do so. Of course smart technical people, being resourceful and creative, will do whatever they want regardless of the standards I set anyway, lol. So all I can really do is set standards for *my* boards and ask that people generally try to stick to them unless there is reason to do otherwise. I hope that clears things up a bit. Take care, Les (Inventor)

2 1

Time to SMIRK!
by Rebecca Fiebrink 04 Oct '08

04 Oct '08

Hi folks, We call your attention to the Small Music Information Retrieval toolKit, SMIRK, available and waiting for your download and abuse at http://smirk.cs.princeton.edu . Like smelt (http://smelt.cs.princeton.edu), SmirK is a set of ready-to- use building blocks and examples. It's all written in ChucK, so there's nothing to "install." (But it does come with its own ChucK class hierarchy, which you'll have to download, so you'll have to set your path carefully, unlike smelt. See the comments in each file for instructions.) Use the code as-is, or modify it to suit your needs. sMiRk includes 2 key components: feature extraction (using the UAna framework at http://chuck.cs.princeton.edu/uana/) and classification (e.g., k-nearest-neighbor, AdaBoost). This comes with some simple keyboard-based and MAUI-based interfaces for training and running classifiers. For example: * Train a classifier to recognize vowels versus consonants, and then apply it to pan the incoming audio appropriately * Do the same based on instrument, speaker, or even genre of songs in your iTunes collection * Recognize different trackpad or accelerometer gestures * Do all this training on-the-fly, in real-time! * Use MAUI to do simple visualizations of features and classification results (for Mac only; not required) We'd love you to download smirk, read about it, ask questions about it, abuse it, request new features, and contribute to it yourselves. We've set up a wiki at http://wiki.cs.princeton.edu/index.php/Chuck/SmirK where you can do all these things. Meanwhile, we're continuing to hack away... Cheers, Rebecca, Ge, and Perry

6 5

Re: [chuck-users] Time to SMIRK!
by Rebecca Fiebrink 03 Oct '08

03 Oct '08

> Problem solved. Please recommence your surfing! > This sounds good but I'm getting a "403, forbidden" on that and on > /index.html there. /index.htm gives me a 404 so I suspect there is a > issue > with settings on the index file. Regarding include/import mechanism: I agree, it would be totally wonderful. My hack for getting around this in smirk: A cludgey "add-machine" file for all mini-projects/examples. I don't have anything better right now, sorry! Rebecca

2 1

Re: [chuck-users] Electronic ChucK
by inventor-66＠comcast.net 03 Oct '08

03 Oct '08

Mike, The computer interface I am planning is an analog one. It will receive stereo audio from the headphones jack and send stereo audio to the line-in Jack. This way we can generate whatever signals we want from ChucK and pipe them into EChucK on adc.left and adc.right. We can also receive two separate audio signals on dac.left and dac.right. I was sort of generalizing the stereo input and outputs into a pair of do-anything audio outs and do-anything audio ins. This opens up many possibilities for ChucK to control EChuck or provide signals for EChucK. Don't have a filtered noise module in your EChucK module collection? Just write a ChucK program and you've got it. Want an analog multiplier but don't have a multiplier module? send the two signals to line-in, have ChucK multiply them, and receive your result on headphones out. That's the idea. The computer interface module will be just a quad opamp circuit with perhaps variable gain/attenuation and diode clamping for the line-in signals to protect your computer. It should be quite low in cost, just $5 or so in parts + profit margin for the seller. Other computer interfaces such as USB, parallel port, etc. are planned but I'm doing the simplest, easiest modules first to get a working prototype built and tested/working. Cheers! Les (Inventor)

4 3

Re: [chuck-users] Electronic ChucK
by inventor-66＠comcast.net 03 Oct '08

03 Oct '08

I threw together a quick starter web page with a somewhat funny introduction. It has links to the Eagle CAD files so you can download them and check them out. So far there is only the Power and ADC microphone interface. Here is the link: http://www.freedomodds.com/music/echuck/index.html I think that perhaps the next most important module for me to create is a computer interface module. Please let me know what other things you would like to see on the page or created next. Also if you would like to contribute in some way, tell me that as well. Cheers! Les (Inventor)

4 5

Re: [chuck-users] Electronic ChucK
by inventor-66＠comcast.net 03 Oct '08

03 Oct '08

Peter, Yes, any kind of transducer would be an excellent addition to EChucK. I'm open to anything that is inexpensive and adds to the fun. I'm most excited about the notion of making music synthesis in all its forms accessible to us, and especially to kids. Breadboarding is inaccessible due to cost, complexity, and learning curve. Traditional synthesizers are inaccessible due to cost and size. Typical electronic experimenter's kits have the same problem as breadboarding, though they do make it fun with sensors and output devices. What is needed is something with a granularity that exists somewhere above component level and below system level, while still retaining the component level cost advantage. And how boring and useless would EChucK be without a diverse selection of sensors? I'd like to have or facilitate the building of rain detectors, wind sensors (weather sensors), EKG sensors to detect heartbeats, and Kassens' suggestions of excited resonators is perfect for EChucK. Well, perhaps my imagination runs amok, I've had only a few short naps these past two days so I'm a bit over tired. Oh, by the way, the EChucK web site is now up to 400 hits in less than 24 hours of existence. I sure hope this means some folks will collaborate, that would be great fun! And as Ge once said... "For those about to ChucK, we salute you!" Les (Inventor)

1 0