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

rtaudio buffer size problem
by jo 25 May '09

25 May '09

Hi everyone, I'm trying to connect a mic via a Tascam US-122L to my mac, which works fine in other programs, however I get the following error when I do chuck --dac4 --in1 test.ck (the Tascam is nicely recognized as dac4, and the test just consists of adc => dac) [chuck]: (via rtaudio): unable to open specified device(s) with given stream parameters: ... RtApiCore: OS-X error setting the buffer size for device (TASCAM: US-122L). [chuck]: cannot initialize audio device (try using --silent/-s) I've tried all permutations of --dac, --in, --bufsize, --blocking etc. with no success. With --silent there are no errors, but of course, some sound would be nice... Curiously, when I do all of the above in miniAudicle, I never get any errors (but no sound either). I'd be grateful for any hints! jo p.s. this is the chuck --probe part chuck]: ------( chuck -- dac4 )--------------- [chuck]: device name = "TASCAM: US-122L" [chuck]: probe [success] ... [chuck]: # output channels = 2 [chuck]: # input channels = 2 [chuck]: # duplex Channels = 2 [chuck]: default device = NO [chuck]: natively supported data formats: [chuck]: 8-bit int [chuck]: 16-bit int [chuck]: 24-bit int [chuck]: 32-bit int [chuck]: 32-bit float [chuck]: 64-bit float [chuck]: supported sample rates: [chuck]: 44100 Hz [chuck]: 48000 Hz [chuck]: 88200 Hz [chuck]: 96000 Hz

1 0

name that shred
by Robert Poor 24 May '09

24 May '09

Hi gang; Is there a way to give a shred a name so that MiniAudicle displays something more useful than "spork~exp" in the list of running shreds? It would be handy -- reassuring even -- to be able to see what shreds are running. - rdp

6 13

chuck under gdb?
by Robert Poor 24 May '09

24 May '09

fellow chuckers: i'm trying to track down a persistent crasher in chuck using gdb. so far i can see that it's dying with a KERN_INVALID_ADDRESS in Chuck_VM::run(), two levels below a call to RtApiCore::callbackEvent(). but what I don't remember is how to instruct gdb to associate the source files with the executable, so I can look at the actual code where it's dying. can anyone offer a refresher / tutorial on that? (and do I need to recompile the sources with -g?) - rob

2 4

Re: [chuck-users] Using FFT 'manually'
by Siepie 24 May '09

24 May '09

> Hi, Siebe! Welcome on board, IMHO there is a great shortage of Dutch > ChucKists so it's good to see you here. Thanks for your reply, Kas. I hope I can help making ChucK a bit more popular around here, I'm sure others will like the way it works. > As FFT expects to deal with complex numbers it's not so > surprising that the one using floats doesn't work. Now I'm afraid you misunderstand. The one getting complex numbers is an IFFT. >From the manual: fft.transform(float[]) //input fft, which i believe doesn't work. fft.spectrum(complex[]) //output fft, which works when using fft.upchuck() ifft.transform(complex[]) //input ifft ifft.samples(float[]) //output ifft Also, both examples run, the FFT one is just not giving any output. In my experience the VM will break and give an error when variable types don't match, so that's not my problem here. I'm currently trying to tweak around a bit with the signal chain. There the types do not exactly match, but that I could correct with a dummy IFFT (FFT fft => IFFT dummy => blackhole), also that didn't help. IMO there really seems to be a problem with he fft.transform function. I can't get it to do anything. Siebe _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

2 2

Using FFT 'manually'
by Siepie 24 May '09

24 May '09

Hello all, My name is Siebe, I'm a MT-student from the Netherlands. I've just started experimenting with ChucK on Windows XP a bit and I really liked how quickly I was able to get things working. For my study I might be interested using ChucK for music and audio analysis. I'm currently trying to figure out how to 'manually' work with an FFT-class, by using .transform(float[]) instead of .upchuck(). But as far as I can see, the transform function for the FFT does nothing, in contradiction with the .transform(complex[]) function for the IFFT class, which seems to work fine. Here are two examples to clear up my point: The working IFFT code: http://pastebin.com/f9b762ad The not-working FFT code: http://pastebin.com/f7a8aae08 My question is, am I doing it right? Since both examples are pretty much the same, my guess is that both should work. Is this a bug in the i386 version? Or are users with another OS experience the same? Any help would be much appreciated. _________________________________________________________________ See all the ways you can stay connected to friends and family http://www.microsoft.com/windows/windowslive/default.aspx

2 1

Performing with ChucK in NYC tomorrow night
by mike clemow 18 May '09

18 May '09

Hey ChucKists, Just letting you all know of a show in NYC. We're performing with an application that makes heavy use of ChucK for sound design sonifying blob-detection information from an openFrameworks program that munges video. The system is called "Outis" and was my masters thesis project at NYU. If any of you are in town, I'd love to put faces to names. ;-) -Mike show: http://michaelclemow.com/?p=640 outis: http://michaelclemow.com/?p=616 -- http://michaelclemow.com http://semiotech.org

1 0

Re: [chuck-users] sillyness witth file names (Kassen)
by Les Hall 16 May '09

16 May '09

Les; couldn't he have made a script that would loop over the dir and delete anything that wasn't named like any of the other files? Yours, Kas. Kas I really don't know if that would have worked, we just all thought it was kind of funny. Les

1 0

Mix2 doesn't mix?
by Tom Lieber 15 May '09

15 May '09

Documentation says Mix2 will "mix stereo input down to mono channel." But then why does this example play the sine wave in my left ear and the noise in my right? Mix2 mix => dac; SinOsc s => mix.left; Noise n => mix.right; 1::second => now; Am I using it wrong? -- Tom Lieber http://AllTom.com/

2 1

sillyness witth file names
by Kassen 15 May '09

15 May '09

Dear list, I just discovered this is a valid filename under Linux (you can still play the file by double-clicking, even); foo";Machine.crash();"bar.wav This means that this; my_buffer.read("my_file"); //gives a syntax error with the above filename is more safe to use than this; "my_file" => my_buffer.read; //this parses, then crashes with the above filename. This isn't much good for anything, aside from pointing out that there can be valid files that can't be played back by ChucK, but it's a exciting, new and especially perverse way to crash so I find that noteworthy on it's own. Happy crashes and a good weekend, Kas.

2 2

Re: [chuck-users] sillyness witth file names
by Les Hall 15 May '09

15 May '09

Not to get off topic too far, but this reminds me of a funny situation back in college. Someone had managed to create an undeletable file, and even the superusers could not delete it. I think it had a single space character as the filename and the Unix of the day didn't let you surround a filename with quotes (this was close to 20 years ago). So the file lived on eternally, lol. Another funny story from college: One day the sysop asked me for my password. I replied sharply with what sounded to him like "bite me", an obvious rude remark. He said "No, really, I need it to fix some stuff." I replied by spelling out the password: "That's the password: byteme". Everyone had a great laugh. We now return you to your regularly scheduled ChucK mailing list. Les

1 0