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

MIDI port aliases
by Bruce Murphy 10 Jul '06

10 Jul '06

UNder Mac OS X, CoreMIDI provides really nifty aliases for ports which are plugged into named devices. This permits them to be easily identified by users with multiple interfaces. These mappings are set up in the audiomid tool by creating devices and setting up wiring The mappings are also useful for named virtual ports created by other MIDI aware applications. COreMIDI also provides an interface for getting the name of the MIDI device providing the port which can further aid identification. IT would be really nice if the chuck probe stuff actually provided this feature. It would be equally nice if a MIDI port open had a "name matching this string" facility, so devices could be moved around between interfaces and provided you had updated audiomidi, all the chuck software looking for that device would Just Work. Thoughts? B> -- Packrat (BSc/BE;COSO;Wombat Implementor) Nihil illegitemi carbovndvm

2 3

chuck manual errata
by eduard aylon 10 Jul '06

10 Jul '06

Hello Adam et al, I'd like to draw your attention on what I believe is an error in the Chuck manual. It seems to me that the Blit ugen section is not correct. According to the manual, Blit has only next() and value() as member functions. However, looking at ugen_stk.h reveals that Blit, as BlitSquare and BlitSaw, has freq(), harmonics() and phase() as memebers and not next () nor value(). Cheers, Eduard

4 9

block comments
by Atte André Jensen 08 Jul '06

08 Jul '06

Hi http://chuck.cs.princeton.edu/doc/language/overview.html#comment states that "For now, there is no block commenting". However, I find that /* and */ works as block comments. Maybe this should be updated in the doc... -- peace, love & harmony Atte http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/compositions

2 1

synchronizing multible chucks
by Atte André Jensen 07 Jul '06

07 Jul '06

Hi Suppose I have two machines each running it's own chuck. Is it possible (and if so, how?) to synchronize the two, for instance having them play a bleep at exactly the same time? How did you, Perry and Ge, go about handling this in the duets I downloaded from the website? -- peace, love & harmony Atte http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/compositions

2 2

[chuck]: cannot bind to tcp port 8888...
by Jochen Hartmann 07 Jul '06

07 Jul '06

linx@linx:/usr/bin/chuck/src$ ./chuck test.ck [chuck]: cannot bind to tcp port 8888... the above is what happened when i tried to run chuck on ubuntu 6.06. any advice would really be appreciated. i am not super well-versed with linux so i might be doing something wrong... thanks for the help !!! - jochen -- -------------------------------------------- Jochen.Hartmann(a)gmail.com

2 1

Re: [chuck-users] Distributing ChucK (Adam Tindale)
by Ollie Glass 05 Jul '06

05 Jul '06

It's done! Breakage v14 now includes, launches, uses and closes ChucK from the Java app. Download from www.blackholeprojector.com It took some fiddling to make this work, anyone who's interested in doing the same thing might like to know I had to: 1 open the OSC ports in Java before ChucK, else JavaOSC finds they are already taken. 2 check which OS Java is running on, so "chuck" or "chuck.exe" can be called as is appropriate. 3 use a Java thread to follow ChucK's stdout and stderr streams. Leave them untended and ChucK freezes after a while. 4 register a Java application exit listener to terminate the ChucK process when the app is quit, otherwise ChucK keeps running. I'm happy to make the Java / ChucK code avaliable to anyone who'd like it. Thanks again everyone! Ollie > From: Adam Tindale <adamtindale(a)hotmail.com> > Let us know when you are finished packaging your app. > > --art > > > On 22-Jun-06, at 2:26 AM, Ollie Glass wrote: > > > I'd like to distribute ChucK with my app, saving users from > > downloading it seperatly. Is it ok to do this? > > > > > Thanks, > > > > > Ollie > > _______________________________________________ > > chuck-users mailing list > > chuck-users(a)lists.cs.princeton.edu > > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > _______________________________________________ > chuck-users mailing list > chuck-users(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > >

2 1

hid
by eduard aylon 04 Jul '06

04 Jul '06

Answering to my previous post, and just remembered there was a HID object... I guess I could use that... thanks, Eduard

6 11

ChucK in WIRED!!
by Perry R Cook 03 Jul '06

03 Jul '06

It's not a whole article about ChucK, but a good mention: http://www.wired.com/news/technology/0,71248-0.html?tw=wn_index_1

2 1

Re: [chuck-users] Distributing ChucK
by Ollie Glass 03 Jul '06

03 Jul '06

Mike, not nosey at all, I could happily talk about it for a week but I'll keep this description short :-) It's an intelligent drum machine for live breakbeat manipulation above the note level. You can read more and download it from www.blackholeprojector.com. Please excuse my slow reply, have been on holiday. Olllie > Ollie, > > Pardon me for being nosey, but what does your app do? ;-) > > Regards, > Mike > > On 6/24/06, Ollie Glass <ollieglaskovik(a)gmail.com> wrote: > > Brilliant, thanks very much for clearing up the details. > > > > > if you are > > > just distributing chuck in the same zip file or something, and the > > > two programs interact through on-the-fly commands, OSC, or some other > > > IPC mechanism, then thats okay. > > > > > > > This is exactly what I'm doing, without modifying ChucK. I'll be in > > touch when I release the package. > > > > Cheers, > > > > Ollie > > > > > > > > > Though, if you do distribute chuck, you also have to distribute the > > > chuck source for at least 3 years after you last distribute it, > > > including modifications, if you made any. This can be as direct as > > > bundling the source with the chuck binary, or as indirect as sending > > > someone a CD with the source on it. (Assuming you arent distributing > > > a modified binary, you can actually just link to the chuck webpage.) > > > If you dont include the source with the binary, you have to indicate > > > somehow how people can get the source. > > > > > > Also, you have to include a copy of the GPL (available as the file > > > COPYING in the chuck download, among other places) directly with the > > > chuck executable. > > > > > > whew... hope this helps, > > > spencer > > > > > > On Jun 23, 2006, at 2:44 PM, Ollie Glass wrote: > > > > > > > My app isn't open source. Is it okay to distribute ChucK with it? > > > > > > > > Sorry if this seems like an obvious question, I'm not very clear on > > > > licences and don't want to make a mistake. > > > > > > > > Ollie > > > > > > > >> Yes! > > > >> > > > >> The GNU public license allows you to freely modify and distribute > > > >> derivative > > > >> works as long as you give due credit and provide the source code > > > >> for free. > > > >> If you look closely inside ChucK you will find RTMidi and RTAudio > > > >> by Gary > > > >> Scavone and libsndfile by Eric de Castro Lopo. > > > >> > > > >> Let us know when you are finished packaging your app. > > > >> > > > >> --art > > > >> > > > >> > > > >> On 22-Jun-06, at 2:26 AM, Ollie Glass wrote: > > > >> > > > >> > > > >> I'd like to distribute ChucK with my app, saving users from > > > >> > > > >> downloading it seperatly. Is it ok to do this? > > > >> > > > >> > > > >> > > > >> > > > >> Thanks, > > > >> > > > >> > > > >> > > > >> > > > >> Ollie > > > >> > > > >> _______________________________________________ > > > >> > > > >> chuck-users mailing list > > > >> > > > >> chuck-users(a)lists.cs.princeton.edu > > > >> > > > >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > > >> > > > >> _______________________________________________ > > > >> chuck-users mailing list > > > >> chuck-users(a)lists.cs.princeton.edu > > > >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > > >> > > > >> > > > >> > > > > _______________________________________________ > > > > chuck-users mailing list > > > > chuck-users(a)lists.cs.princeton.edu > > > > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > > > > > > > > > > _______________________________________________ > > chuck-users mailing list > > chuck-users(a)lists.cs.princeton.edu > > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > > > > -- > > "ooh aah bleep" > -miraton >

1 0

filter
by Atte André Jensen 02 Jul '06

02 Jul '06

Hi I'm just a simple guy, and I haven't got a clue what's up with the filters available in chuck. Poles and zeros and stuff... I'd appreciate if someone could: 1) Give an example of how to set up (something that in my simple brain is called) a low pass filter with/without resonance and a highpass filter with/without resonace. 2) Could direct me towards mind-expanding online information that might allow me to actually understand a fraction of what's going on? And while we're at it: I see no examples using either sawosc or sqrosc. I know how to use those though (just need some filters), but, still at the risk of seeming extremely conservative, wouldn't a classic, analog synth style patch (saw > low pass filter > envelope) or two be a nice and possible addition? Maybe someone even has such a simple example (involving filtering) that I could take a look at or we could throw on the wiki? -- peace, love & harmony Atte http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/compositions

5 14