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

Re: 2 questions (Adam Tindale)
by michael breitenbach 16 Dec '05

16 Dec '05

hi, this: sinosc a => dac; a.last => float x; was also my first idea - but it doesnt work. a error occurs: cannot resolve operator '=>' on types '[function]' and 'float'... (i have installed chuck 1.2.0.4.) micha

2 2

icons for upcoming Chuck IDE?
by Spencer Salazar 15 Dec '05

15 Dec '05

Hello, I have been working on a free GPLed integrated development environment ("IDE") program designed specifically for development in ChucK, called miniAudicle. It is planned to be released for Mac OS X, Win32, and Linux. I was hoping to design some pretty-looking icons to represent the "add," "remove," "replace," "remove all," and "remove last" on-the-fly programming commands within the miniAudicle. Unfortunately, my graphic design skills leave much to be desired. So i ask of the ChucK community at large: would anybody like to contribute their icon design talents for use within the miniAudicle? The only characteristics im really looking for are that the icons be 48x48 pixels or larger, that they have a transparent background, and that, to some degree, they can be intuitively associated with the corresponding ChucK OTF commands. Here is a screenshot of the icons currently in use: http:// www.princeton.edu/~ssalazar/miniaudicle.png they work well enough, but they were designed for a web browser, so some of the icons dont really match up as well with the corresponding functionality as they could. Also, due to some licensing issues im not sure if I would be able to distribute them in any case. please let me know if youd be willing to help with this. also if anyone has any pointers to any good repositories of decent looking icons which could be easily used in this project, that would also be very helpful and probably involve less redundant labor. thanks spencer

2 2

Re: [chuck-users] Segmentation fault
by Ollie Glass 15 Dec '05

15 Dec '05

Hi Ge, >> Sometimes I get a segmentation fault when loading a new sample >> into a sample buffer that's already playing. Sometimes it doesn't >> seem to cause a problem. Is there anything I can do to prevent >> these crashes? > > We just checked in a fix for sndbuf.read which now correctly > (hopefully) closes the file handles (which it wasn't doing) and > also resets a state variable. It is now in CVS, and will be part > of 1.2.0.4, which should be released by tomorrow. Please let us > know if this indeed remedies the problem. Also, which platform is > this crash on? Yes, 1.2.0.4 fixes the problem. I am on OS X 10.4.3. Thank you, Ollie

1 0

warning: the use of 'tmpnam' is dangerous, better use 'mkstemp'
by Tyler Gillies 14 Dec '05

14 Dec '05

chuckas, Just built and tested 1.2.0.4 on linux-alsa. Work great (BLITs! Yes!). When I built, I was given this message: warning: the use of 'tmpnam' is dangerous, better use 'mkstemp' dangerous?? - Tyler Gillies

2 1

2 questions
by michael breitenbach 14 Dec '05

14 Dec '05

hi, 1. is it possible to create a event from a audiosignal (for example a pulse force a event)? 2. and is it possible to use a audiosignal as a float value in chuck code - like a snapshot function? sinosc a => float x => dac; // this doesn't work micha

2 1

chuck manual
by James Baker 12 Dec '05

12 Dec '05

hey chuckers, i just spent a bit of time looking through the wip manual pdf and ive got to say im impressed. this thing is far superior than most ive seen - commercial or free. its things like this that imho will make chuck stand out. keep up the good work, james ps. its almost christmas, wheres audicle + the toys ? ;)

1 0

Segmentation fault
by Ollie Glaskovik 12 Dec '05

12 Dec '05

Sometimes I get a segmentation fault when loading a new sample into a sample buffer that's already playing. Sometimes it doesn't seem to cause a problem. Is there anything I can do to prevent these crashes? Thanks, Ollie

2 1

ffmup chuck duet video + new power toys
by Ge Wang 06 Dec '05

06 Dec '05

Greetings, Perry and I rendered another chuck performance/disaster last night as part of FFMUp in Princeton. Perry played the VOMID (Voice-Oriented Melodica Interface Device) [1] and projected the sound through the amazing Noggin-phonics speaker head (also a PRC production), while I programmed on-the-fly: http://soundlab.cs.princeton.edu/listen/chuck@ffmup-2005.11.29.mov The breath pressure sensor, joystick, sliders, and linear FSR 1 on the VOMID controlled a live vocal model in chuck; the consonants (and belching) were sound clips, played by the keys and linear FSR 2 - all projected through metal head + mounted speakers of the Noggin-phonics! (The wild spatializing effect of this is unfortunately lost in the video.) Another notable aspect of the ordeal was the debut of two new chuck things, soon to be released. Both are authored by Spencer Salazar, a most righteous programmer and CS major here at Princeton. The ChucK Shell is a built-in command line interface *within* chuck, from which on-the-fly programming commands (and even live code) can be issued with great efficiency. The other is a prototypical native ChucK editor (called the miniAudicle, using Cocoa on OSX, Win32/MFC on Windows, and we-haven't-decided-what on linux). This will be released along with the Audicle, to add to our arsenal of chuck power toys. We will be hearing more about both the shell and the miniAudicle very soon (they are still in intense development)... So a big thanks to Spencer, and to Scott Smallwood for setting everything up for FFMUP. Best, Perry + Ge! --- Read more about the VOMID here: [1] http://hct.ece.ubc.ca/nime/2005/proc/nime2005_236.pdf

6 8

sndbuf.pos
by eduard 04 Dec '05

04 Dec '05

Hello all, I have a question for whoever is willing to answer it. Has one to always set sndbuf.pos at each iteration? My scenario: Let's say I want to control the starting position of my sndbuf with a midi keyboard while sndbuf is set to loop mode ( 1 => sndbuf.loop ). Midi is received in a sporked MidiReceive() function and my sndbuf.pos is set inside this same function and not in the main while- loop. Thus when I press a key the sndbuf.pos is changed for that loop, but when it gets to the end of it, it starts at sndbuf.pos(0) instead of the previously set one. So it seems that sndbuf doesn't keep track of the position that was set, and automatically starts from the beginning when the end of the audiofile is reached. Is this true? Thanks, Eduard

2 1

sndbuf.pos
by eduard 04 Dec '05

04 Dec '05

ok, I think i got the answer. Sorry, but when one gets obsessed by something he becomes blind. sndbuf.pos it's just the current position in the buffer and it is obviously changing all the time.

1 0