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

Creating a THX-like sound in ChucK
by Perry R Cook 22 Feb '07

22 Feb '07

Hi all, here's a little New Year's gift. After reading a posting by an STK user to the stk list about reading Andy Moorer's account of how he created the THX sound, I decided to whip one up in ChucK. As easy as one might expect. Enjoy!! PRC http://musicthing.blogspot.com/2005/05/tiny-music-makers-pt-3-thx-sound.html // THX emulator, Perry R. Cook, Jan. 8, 2007 // // F-1, B1b, F1, B2b, F2, B3b, F3, A5, F4, A6 [ 29.0, 87.5,116.0,175.0,233.0,350.0,524.0,880.0,1048,1760, 29.0, 87.5,116.0,175.0,233.0,350.0,524.0,880.0,1048,1760, 29.0, 87.5,116.0,175.0,233.0,350.0,524.0,880.0,1048,1760 ] @=> float targets[]; float initials[30]; float deltas[30]; sawosc s[30]; gain gl[30]; gain gr[30]; JCRev rl => dac.left; JCRev rr => dac.right; 0 => int i => int j; for (0 => i; i<30; i+1 => i) { std.rand2f(200.0,800.0) => initials[i] => s[i].freq; // random freqs. (targets[i] - initials[i]) / 10000.0 => deltas[i]; // 10 sample updates 0.1 => s[i].gain; std.rand2f(0.0,1.0) => gl[i].gain; // random 1.0 - gl[i].gain() => gr[i].gain; // panning s[i] => gl[i] => rl; // hook up s[i] => gr[i] => rr; // all the oscs } 10000 :: samp => now; // steady cluster while(j < 10000) { for (0 => i; i<30; i+1 => i) { initials[i] + (deltas[i]*j) => s[i].freq; // sweep freqs. } j + 1 => j; 10 :: samp => now;} while (j < 30000) { // hold chord 10 :: samp => now; j + 1 => j; } while (j < 35000) { for (0 => i; i<30; i+1 => i) { 0.1 * (35000 - j) / 10000.0 => s[i].gain; // decay gains } 10 :: samp => now; j + 1 => j; } 60000 :: samp => now; // reverb tail

11 19

Cpu time between audio samples?
by karl.petermichl＠orf.at 21 Feb '07

21 Feb '07

Dear ChuKees, I am particularely interested in the wonderful feature which allows me to calculate EVERY SINGLE AUDIO SAMPLE prior to outputting it to the dac via the impulse ugen. Is there a rough estimation just how much calucaltion can go on between each sample at 44100hz? Does this depend on the cpu type and speed, or is there an inherent ChuK limit? I want to create some amazing sounds by making extremly complicated computations for each sample, as in theory one could just create about any sound in the world this way (including semi-talented clarinet players just having been woken up from a deep alpha-cycle..---)) Thanks and cheers, Karl.

11 24

Observer and Observable
by David Michael 31 Jan '07

31 Jan '07

I realize that the Event model in Chuck handles events, but it seems to be implicitly time-based. This is a good thing. I could be completely mistaken, but it seems that for something to respond to an event, a t(s)hread is f(sp)orked, time is stopped, and the thread waits for an event to come in from another running thread before proceeding. But what if you want a process in a thread to change from an event, but not to stop what it's doing waiting for said event. There may be a Chuckish way to approach this, but here is a possible solution. In some experiments, I implemented a simple Observer pattern for signaling without being dependent on time, i.e., to send events to objects within a single thread (named like in Java classes minus some functions) ... not sure if this is useful, but it initially began as an experiment in efficiency. At the moment, using Observer type signals over Events does not seem to save any cpu, but it did allow me to spawn 1/3 fewer threads. In a situation where you have many instances that need events without keeping their own time, this might useful. To use: extend Observer class for all objects you want to register with an signal producer (an Observable)... and visa versa (extend Observable) for those who are going to be sending signal. You will need to write a Signal class or something equivalent to get a rich message to the receivers (Observers), but whatever. For more on the topic for those unfamiliar with what I am talking about, see Java Observer/Observable - signal/slot in C++ or Head First Design Patterns, which has a nice clear explanation (and some corny pictures). Also for those interested, I also have a Dispatcher class for a collection of Observables, indexed by string. More like sig/slot. I suppose you could also create "ObservableObservers" if you just renamed the class and stuck the Observer update() function in Observable. Same basic concept though: event signaling without Events. Please let me know if I have any typos, or if the example program is convoluted or just doesnt work. David class Observer { function void update(){} // receive } class Observable { 20 => int size; // this could be any size... just be reasonable. In the near-term this should be a "dynamic array" Observer observers[size]; int count; function void addObserver(Observer o) // subscribe { if(count < size){ o @=> this.observers[count]; count++; } } // is this properly garbage collected? // if its not, there could be orphaned objects, and a growing application, right? function void deleteObserver(Observer o) // unsubscribe { for(0 => int i; i < count; i++){ if( observers[i] == o ){ if(i >= 0 && i < count) { for(i => int j; j < count; j++) { observers[i + 1] @=> observers[i]; } } count--; } } } function void notifyObservers() // publish { for(0 => int i; i < count; i++){ this.observers[i].update(s); } } } class Receiver extends Observer { func void update() { <<< "I got something." >>>; } } // make some instances Receiver r; Receiver r2; Observable observable; // register the observers (who receive) with the observable (who signals) observable.addObserver(r); observable.addObserver(r2); // send the signal observable.notifyObservers(); // should print: // $ "I got something" // $ "I got something" // remove an observer observable.deleteObserver(r2); // send the signal observable.notifyObservers(); // should print: // $ "I got something"

4 3

Destroying object instances ... unchuck?
by David Michael 30 Jan '07

30 Jan '07

Is there a way to explicitly destroy object references? For instance, in a loop, I am creating an array of objects like so: Object objects[4]; 0 => int count; for(0 => int i; i < 4; i++ ) { new Object @=> objects[count]; count++; } Now how would I delete the Object referenced at, say, objects[0]? If I reassign an Object to objects[0], what happens to the object that was there? Is it destroyed and cleaned up, or do I need to delete the object from memory somehow? Thanks D

5 7

OSC reliability issues
by David Michael 28 Jan '07

28 Jan '07

Hello list, I have been running experiments with Chuck's OSC implementation and have found that when I have an instance of Chuck producing regular OSC events under a relatively heavy load (heavier than the example files), the receiver only gets a few of these events - perhaps less than 20% of them. This situation makes it very difficult for parallel instances of Chuck (on different machines) to communicate reliably. I have reproduced this on both Mac and Linux (Ubuntu) installations. I am curious if anyone else on the list has come across this issue. Does anyone have suggestions for dealing with OSC communication reliably? Best, David

4 8

Fwd: Writing to text files? Visualization?
by jochen lists 25 Jan '07

25 Jan '07

Question: is there an update on when file I/O will be possible? thanks - jochen Begin forwarded message: > From: "David Michael" <david.michael(a)gmail.com> > Date: December 8, 2006 12:31:33 PM EST > To: "ChucK Users Mailing List" <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] Writing to text files? Visualization? > Reply-To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > > Just an update on my question about writing to text file. > I just found this thread that pretty much answers it: > https://lists.cs.princeton.edu/pipermail/chuck-users/2006-January/ > 000293.html > > Keep up the good work, ChucK is a really nice language. There are a > ton of things missing, but the VM works as expected, is relatively > stable, and the language is relatively easy to use. In fact, I am > finding that because the language is still very small and well > documented, it has been very easy to learn and get things going. > > I look forward to the addition of file I/O and array.size() > :) > > > > On 12/8/06, Bruce Harris <nitro2k01(a)gmail.com> wrote: >> This is not really an answer to your question, and not even >> chuck-related: >> But once upon a time, I had an idea to use my 386 laptop as a lo-fi >> visualization device, by connecting it with a serial port and sending >> data to be displayed on its screen. >> To come back to your question, I think I remember seeing the question >> on this list before, and I think the answer was it's on the todo list. >> (But I may be wrong on that.) >> >> On 12/8/06, David Michael <david.michael(a)gmail.com> wrote: >>> Hello list >>> >>> Can someone please tell me if it is possible to write text files, or >>> any other files for that matter that are not audio files? >>> >>> I would like to store a sequence of values that im generating >>> someplace outside of ChucK so I can graph it or log it. >>> >>> Any ideas? >>> >>> Thanks >>> David >>> _______________________________________________ >>> chuck-users mailing list >>> chuck-users(a)lists.cs.princeton.edu >>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >>> >> >> >> -- >> Love. /Bruce Harris >> >> -- >> -----BEGIN 2ROT13 MESSAGE----- >> The blog of nitro2k01: <http://soundandcomplete.wordpress.com/> >> Electronic music forum: >> <http://oxo-unlimited.com/forums> >> Sätt på ett par flipflops, vippa på rumpan >> och gör det här till en minnesvärd sommar! >> -----END 2ROT13 MESSAGE----- >> _______________________________________________ >> 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

chuck ide plans / ideas
by tazumi 24 Jan '07

24 Jan '07

Hello List, i was using chuck very much in the last few month.. and - as you all know - you always want to have some extra features (that are sometimes very special), some stuff that fits exactly to your needs.. So i decided to start an own Project, an alternative chuck environment.. mainly to have the features of my dreams. anyway, as some other people might be interested, i would like to introduce and describe this project here, and would love to hear what others think about those ideas/plans. actually they are more than plans by now, as maybe 50-60% is already finished for a first basic usable version... the main components are of course basic stuff like a source editor with add/replace/remove shred functions or a lists of the sporked shreads. (Nothing you cant do with mini audicle so far..) There will be no direct connection between the programm and chuck. once chuck is started, all interaction will be done using osc messages - start/stop shreds, keeping the list of running shreds etc.. then there are these special features - very often I do pattern-oriented / loop based stuff when i use chuck. my intention is to create some helping features for that. for example i want to have something like code plugins - a feature that writes some code for you.. mainly they should assist you in tasks that are very basic and can be used in many situations, but need a lot of code writing or are bad to handle.. Its hard to explain in general, so look one example: I often create patterns or sequences using array data. so some typical chuck code looks like this: BlitSaw osc => LPF filt => dac; [ 44, 54, 44, 54, 54] @=> int note; [ 0.5, 0.5, 0,5, 0.25, 0.25] @=> float length; [8000, 12000, 8000, 12000, 12000] @=> float freq; int actual = 0; while(1) { playnote (note[actual], length[actual], freq[actual]); actuall ++; // if (actual > 5) 0 => actual; .. and so on... } this plays a simple little sequence.. Now what i like to do is create a 'Table' or 'Array' Plugin. It will have a user interface that provides a table (like for example in excel) where you can enter your data. The table (columns etc) can be defined by the user - in this case i would create a table with 3 columns, like this: ----------------------------------------- | note | length | freq | ----------------------------------------- | 44 | 0.5 | 8000 | ----------------------------------------- | 54 | 0.5 | 12000 | ----------------------------------------- | 44 | 0.5 | 8000 | ----------------------------------------- | 54 | 0.25 | 12000 | ----------------------------------------- | 54 | 0.25 | 12000 | ----------------------------------------- so you can enter your values in a more easy and comfortable way.. extra features like select multiple cells / copy and paste etc. would make life much easier.. when sporking that file, the plugin will write code that creates the arrays to your file.. the plugin could also write some additional code that creates for example an osc receiver with an array updating function.. so while the shred is running, and you change the value of a cell, the plugin sends an update osc message to the shred, which updates the changed array element immediately.. so you change sequences (or anything that uses data stored in arrays) without stopping or replacing the shred.. (all that done by the pugin, you just have to create a table, enter data, and user that data in your code). Also, you can do it the other direction: if you update array elements using a function that sends a osc message back to the program (provided the plugin ) the table will be updated.. One way to keep / store data generated from within chuck.. i know some people asked about sth like that.. Just one of many ideas.. besides those plugins there will be some other basic components like a file browser, with sample preview function (as i also often use samples) the preview function would do nothing more than create some code like: sndbuf buf => dac; "mysample.wav" => buf.read; buf.length => now; then the plugin would write that code to a temporary file and sporks it.. So many stuff could be done which are very easy to implement, by just generating some code and let chuck do the work :-) As the Program mainly consists of UI stuff and no realtime / time critical stuff is needed, it is written in .Net, i know some people will not like that but it is perfect for those tasks.. And if some other people using linux or osx are interested, let me know, then i would keep in mind to only use parts of the framework that are impelementes in mono too, which i didn't look after so far.. I really would love to hear some opinions about the ideas.. and i hope i can come up with a first version soon.. -- tazumi

2 3

Chuck and External audio?
by jochen lists 19 Jan '07

19 Jan '07

hi, sorry about this stupid question, but i can't seem to find any documentation on how to use chuck to process audio files, i.e. open a wav, aiff, whatever and run it through some filters. is this possible??? thx - jochen

3 3

Trouble with sequencer.ck
by Hilquias Abreu da Costa 19 Jan '07

19 Jan '07

hi there. I've found a simple sequencer at chuck wiki (http://wiki.cs.princeton.edu/index.php/ChucK/sequencer.ck) but when i try execute it, the console show: sequencer.ck]:line(9): cannot declare static non-primitive objects (yet)... I've found some info about this here, but I can't solve the problem, any tip? _______________________________________________________ Yahoo! Mail - Sempre a melhor opção para você! Experimente já e veja as novidades. http://br.yahoo.com/mailbeta/tudonovo/

3 4

Re: [chuck-users] compile problem with miniAudicle <Slackware Linux>
by ka1iic＠prexar.com 19 Jan '07

19 Jan '07

Hi all, I posted this to the Audical list but all is very quiet on that list it seems so please excuse my reposting it to this list. I have a compile problem with miniaudicle-0.1.3.6 my system is as follows: (Chuck compiles fine BTW... version 1.2.0.7) I've tried Chuck and like very much what I hear and would like to get miniaudical up and going too :-) Thanks for your help in advance! vince stats... Slackware Linux 10.2 wxWidgets-2.8.0 wxGTK-2.8.0 GCC version 3.3.6 The output I am getting follows: root@crypto5:/miniAudicle-0.1.3.6# make linux-alsa make -f makefile.alsa make[1]: Entering directory `/miniAudicle-0.1.3.6' gcc -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config --cppflags` -O3 -c -DwxABI_VERSION=20600 -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.6 miniAudicle.cpp gcc -o wxw/mAParentFrame.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config --cppflags` -O3 -c -DwxABI_VERSION=20600 -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.6 wxw/mAParentFrame.cpp gcc -o wxw/mADocument.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config --cppflags` -O3 -c -DwxABI_VERSION=20600 -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.6 wxw/mADocument.cpp gcc -o wxw/mAView.o -D__LINUX_ALSA__ -D__LINUX__ -D__MA_WXWIDGETS__ `wx-config --cppflags` -O3 -c -DwxABI_VERSION=20600 -D__CK_SNDFILE_NATIVE__ -Ichuck/src -Iwxw -I/miniAudicle-0.1.3.6 wxw/mAView.cpp wxw/mAView.cpp: In member function `void mADocMDIChildFrame::RegisterWithWindowMenu()': wxw/mAView.cpp:315: error: no matching function for call to `mAApp:: AddWindowMenuItem(mADocMDIChildFrame* const)' wxw/mAParentFrame.h:109: error: candidates are: int mAApp::AddWindowMenuItem(mAFrameType*) make[1]: *** [wxw/mAView.o] Error 1 make[1]: Leaving directory `/miniAudicle-0.1.3.6' make: [linux-alsa] Error 2 (ignored) root@crypto5:/miniAudicle-0.1.3.6#

3 2