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

miniAudicle working directory?
by Ollie Glass 20 Jul '06

20 Jul '06

I'm using miniAudicle to develop Sequencer.ck. It's beautiful, thanks! When I run it, I'd like the working directory to be the directory the .ck file is in. Is this possible? Ollie

3 2

Question about OSC and Network Connections
by Mike McGonagle 20 Jul '06

20 Jul '06

Hi all, I was in the process of testing some code that I have that is using OSC, and in these tests, I got an error from ChucK saying that a port was busy and it could not connect. This was because I had another process running (dumpOSC from the OSC site) on that port. This seems normal in that ChucK complained about this. My trouble is that once I stopped the dumpOSC process, ChucK still would not connect to that port AND it didn't give any warnings or error messages saying that it would not connect. The only way that I was able to connect was to restart ChucK. I am not quite positive if just restarting the Compiler (using miniAudicle [latest]) would have been enough, as I restarted the whole program. Once I did this, my code worked fine. Is there a way that ChucK could be made to NOT fail when these things happen? It seems to me that this would be in line with the "on the fly" concept. I would think that ChucK should be able to detect, at any time, if a port was in use or not, and return the appropriate error message, or connect if it is unused. Thanks, Mike -- Help the Environment, Plant a Bush back in Texas! "I place economy among the first and most important republican virtues, and public debt as the greatest of the dangers to be feared. To preserve our independence, we must not let our rulers load us with perpetual debt." -- Thomas Jefferson, third US president, architect and author (1743-1826) "Give Peace a Chance" -- John Lennon (9 October 1940 – 8 December 1980)

1 0

warning: new chuck (bug fixes)
by Ge Wang 19 Jul '06

19 Jul '06

Hi! We are about to release new chuck/miniAudicle/audicle (announcements will be sent to [chuck] and [audicle]). It still won't have garbage collection or string manipulations, but several of the known long-standing bugs have been fixed, including multiple declarations, sporking member functions, ++/--, miniAudicle fixes, and more undocumented audicle features. Garbage collection will require several wide-area changes, and we would like to get a relatively stable pre-gc version of things out. If you like, test things a bit and let us know, once the new versions are out. So uh, stay tuned. This is only a warning. Thanks! chuck team

1 0

Re: [chuck-users] miniAudicle-0.1.3.0 released (now in color)
by Ge Wang 19 Jul '06

19 Jul '06

(redirected from [chuck]): message from Atte: --- Spencer Salazar wrote: > Coming very soon: Linux ... miniAudicle. Sounds nice, cant wait... -- 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

Re: [chuck-users] miniAudicle-0.1.3.0 crash report
by Ge Wang 19 Jul '06

19 Jul '06

(redirected from [chuck]) message from Ollie: --- Hi Spencer, miniAudicle looks great but freezes when I try to start my Sequencer.ck script (which works fine on the command line). You can get the script from blackholeprojector.com/Sequencer.ck Ollie > From: Spencer Salazar <ssalazar(a)Princeton.EDU> > Date: 14 July 2006 20:14:24 BDT > To: ChucK Central Mailing List <chuck(a)lists.cs.Princeton.EDU> > Subject: [chuck] miniAudicle-0.1.3.0 released (now in color) > Reply-To: ChucK Central Mailing List <chuck(a)lists.cs.princeton.edu> > > > Hello, > > miniAudicle-0.1.3.0 (alpha) is now available. > > http://audicle.cs.princeton.edu/mini/ > (may need to reload) > > miniAudicle-0.1.3.0 offers chuck-1.2.0.6-rc3, configurable syntax > coloring, new View, Button, and LED user interface elements, > revamped documentation, and new examples (thanks to Ananya Misra > for help in documentation and examples). > > Coming very soon: Linux and Windows miniAudicle. > > Please let us know about any problems, bugs, feature requests, etc. > > spencer > > --- > 0.1.3.0 > - added ChucK syntax coloring in editing windows > - added syntax coloring preferences item > - implemented MAUI_View, MAUI_Button, and MAUI_LED objects > - expanded MAUI_Element and MAUI_Slider object interfaces > - disabled network thread by default >

1 0

variable of type function
by Atte André Jensen 17 Jul '06

17 Jul '06

Hi Is it possible to have a variable of type function? If so, could someone provide a link to where I can read about it or a short example showing how it works? Will it work with overload definitions? -- peace, love & harmony Atte http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/compositions

3 5

Object array initialization
by Ollie Glass 16 Jul '06

16 Jul '06

I'm trying to declare an object array and initialize it later in a function: Channel channels[]; initChannels(4, 16); fun void initChannels(int num, int length) { Channel ch[num] @=> channels; ... This gives a segmentation fault, and trying like this: fun void initChannels(int num, int length) { channels[num]; gives a bus error. How should this be done? Thanks always, Ollie

3 6

Object array initialization
by Ollie Glass 15 Jul '06

15 Jul '06

Hi Ge, your example works on my system too (OS X 10.4.7 PPC, ChucK 1.2.0.5b). After some hacking I found the bus error stopped when I changed "int rootNote, mainPitch;" to "int rootNote; int mainPitch;". I don't know why, and strangely this test works: int x, y; 0 => x; 4 => y; <<< x >>>; <<< y >>>; If you'd like to recreate the error the offending variables are on lines 459 & 460 in the script at blackholeprojector.com/Sequencer.ck Ollie On 14 Jul 2006, at 17:00, chuck-users-request(a)lists.cs.princeton.edu wrote: > From: Ge Wang <gewang(a)CS.Princeton.EDU> > Date: 13 July 2006 17:36:16 BDT > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] Object array initialization > Reply-To: ChucK Users Mailing List <chuck- > users(a)lists.cs.princeton.edu> > > > Hi Ollie! > > Which platform are you running? Also, can you include the > greater program, or more of the context? I can't seem to > reproduce the crash on OS X using the following code: > > --- > > public class X > { > int hi; > fun void boo() > { <<< hi >>>; } > } > > class Y > { > X xs[]; > init( 4 ); > > fun void init( int num ) > { > X x[num] @=> xs; > > for( int i; i < num; i++ ) > i => xs[i].hi; > } > } > > // make y > Y y; > > // print > for( int i; i < y.xs.cap(); i++ ) > y.xs[i].boo(); > > --- > > It may be a chuck bug elsewhere... > > Best, > Ge!

3 2

instrument design considerations
by Atte André Jensen 15 Jul '06

15 Jul '06

Hi I'm wrestling with some mostly conceptual problems that I'd like to get some feedback on. I hope some of you people take the time to discuss this with me. It's not about chuck bugs, it's not about how-do-i-use-this-chuck-construct, it's about how I get my brain dead brain around a design problem for something that I really would like to do in chuck. Long story short: I'd like to be able to record sniplets of midi into chuck and grow it (by performing various transformations). For this to work my instruments need to work with noteon/noteoff, since that's what gonna happen with midiin. Currently I have a really simple, well working way of doing instruments by making each instrument a static member function of an Instruments class. Each function (might) take a length parameter indicating how long the instrument should sound before going into it's release phase. From a coding point of view I prefer my current instrument definition, but if it should work with midi I need to make instruments work with noteon/off. I'd like to be able to use the same instrument from both code and midi. Another issue with midi is that it should be polyphonic. First question: How are you guys handling this? Anyone recorded midi sniplets into chuck for processing? Attached is an (bit messy) attempt at this design. It's suffering from the CPU-eating problem that Ge advised about a couple of days ago (could/should be fixed, don't care at this point). There's currently also no support for "length-driven" use, but that would be easy, simply by having a play function that calls noteOn(), waits a few::ms and calls noteOff(). The reason for the four classes (monoInstrument, polyInstrument, mono_sine and poly_sine) is that I'd like to have as much of the book keeping as possible in the super classes, so basically only noise making is happening in sub classes. Actually I'd like to only have to write the mono_sine (or similar for other instruments) class. Second question: Would it be possible to get rid of poly_sine, or at least the repetitive (for other instruments) code in functions on(), off() and kill()? Main reason it's there is that the voices are not known in any of the other classes. Could that be changed? Supposed I actually get this thing going, I'm gonna set chuck to record to some data structure, probably an object. This is happening in one shred. But then I'd like to a) grow (permutate) and b) use this data structure in other shreds. Third question: But how is that gonna be possible? The recorded-to instance is not known outside the scope of the recording shred :-( Static class? Possible, but inelegant. Sorry for the loong post. Any feedback is highly appreciated! -- peace, love & harmony Atte http://www.atte.dk | quartet: http://www.anagrammer.dk http://www.atte.dk/gps | compositions: http://www.atte.dk/compositions // --------------------------------------------------- // ring_element // --------------------------------------------------- class ring_element{ int date; float freq; } // --------------------------------------------------- // ring // --------------------------------------------------- class ring{ 4 => int size; 1000 => int max_size; ring_element container[max_size]; int counter; fun int is_full(){ 1 => int result; for(0=>int i; i<size;i++){ if(container[i].freq == 0){ 0 => result; size => i; } } return result; } fun int remove_oldest(){ 1000000 => int min; -1 => int pos; for(0=>int i; i<size;i++){ if(container[i].date != 0 && container[i].date < min){ container[i].date => min; i => pos; } } if(pos != -1){ unset(pos); } return pos; } fun int add(float freq){ 10000000 => int min; int position; for (0=>int i; i<size; i++){ if(container[i].freq == 0 && container[i].date < min){ container[i].date => min; i => position; } } counter++; counter => container[position].date; freq => container[position].freq; return position; } fun void unset(int position){ 0 => container[position].date; 0 => container[position].freq; } fun int freq2voice(float freq){ -1 => int position; for(0=>int i; i<size;i++){ if(container[i].freq == freq){ i => position; size => i; } } <<<"freq2voice",freq,position>>>; return position; } fun void full_clear(int position){ //<<<"before">>>; //print(); unset(position); //<<<"after">>>; //print(); } fun void print(){ <<<"------">>>; for(0 => int i; i<size; i++){ <<<"date:",container[i].date,"freq:",container[i].freq>>>; } <<<"------">>>; } } // --------------------------------------------------- // monoInstrument // --------------------------------------------------- public class monoInstrument { .4 => float volume; ADSR env; env =< dac; 0 => env.gain; .001 => float attackTime; .01 => float decayTime; 1 => float sustainLevel; .01 => float releaseTime; attackTime => env.attackTime; decayTime => env.decayTime; sustainLevel => env.sustainLevel; releaseTime => env.releaseTime; 0 => env.gain; 1 => env.keyOff; fun void setFreq(float freq){} fun void noteOn(float freq, float dynamic){ env =< dac; attackTime => env.attackTime; decayTime => env.decayTime; sustainLevel => env.sustainLevel; releaseTime => env.releaseTime; volume * dynamic => env.gain; setFreq(freq); env => dac; 1 => env.keyOn; } fun void noteOff(){ 1 => env.keyOff; while(env.state() != 4){ 2::ms => now; } 0 => env.gain; env =< dac; 1::samp => now; } fun void hardOff(){ 1 => env.keyOff; 0 => env.gain; env =< dac; } fun void play(float freq, dur length, float dynamic){ noteOn(freq,dynamic); length => now; noteOff(); } } // --------------------------------------------------- // polyInstrument // --------------------------------------------------- class polyInstrument { 6 => int polyphony; ring pressed; polyphony => pressed.size; fun void on(int voice, float freq, float dynamic){ } fun void off(int voice){ } fun void kill(int voice){ } fun void noteOn(float freq, float dynamic){ int voice; if(pressed.is_full()){ pressed.remove_oldest() => voice; kill(voice); } pressed.add(freq) => voice; on(voice, freq, dynamic); pressed.print(); } fun void noteOff(float freq){ pressed.freq2voice(freq) => int voice; if(voice != -1){ off(voice); } else { <<<"oops, couldn't find match for",freq>>>; } pressed.full_clear(voice); } } // --------------------------------------------------- // mono_sine // --------------------------------------------------- class mono_sine extends monoInstrument{ sinosc osc => env =< dac; //.1 => decayTime; //0 => sustainLevel; //.1 => decayTime; 2.6 => releaseTime; fun void setFreq(float freq){ freq => osc.freq; } } fun void sine(float freq){ sinosc osc => ADSR env => dac; .001 => env.attackTime; .01 => env.decayTime; 1 => env.sustainLevel; .01 => env.releaseTime; 1 => env.keyOn; 10::ms => now; freq => osc.freq; 1 => env.keyOff; while(env.state() != 4){ 1::ms => now; } osc =< env =< dac; } // --------------------------------------------------- // poly_sine // --------------------------------------------------- class poly_sine extends polyInstrument { //2 => polyphony; polyphony => pressed.size; mono_sine voices[polyphony]; fun void on(int voice, float freq, float dynamic){ <<<"on",voice,freq>>>; voices[voice].noteOn(freq,dynamic); } fun void off(int voice){ <<<"off",voice>>>; voices[voice].noteOff(); while(voices[voice].env.state() != 4){ 2::ms => now; } 1::samp => now; } fun void kill(int voice){ <<<"kill",voice>>>; voices[voice].hardOff(); } } 400::ms => dur length; [0,3,5,7,10] @=> int notes[]; float freq; poly_sine s; while(true){ std.rand2(220,450) => freq; spork ~ s.noteOn(freq,std.rand2f(.6,1)); 10::ms => now; spork ~ s.noteOff(freq); 300::ms => now; }

1 1

chuck and pd OSC hack
by Scot Gresham-Lancaster 13 Jul '06

13 Jul '06

I don't know if this will help anyone out there, but I have had quite a bit of experience with getting OSC to work with chuck. While waiting for the chuck string manipulation features (which are on the horizon) I worked out a solution that is a bit of a kludge, but functional for now. OSCroute in pd gives a very flexible structure for parsing arbitrary OSC message. Once the message is parsed it is fairly simple to convert it to an appropriate midi message and then pass the midi parameter to chuck via the AIC midi bus (at least on the mac). Of course, this becomes a mute point once string manipulation, regex, etc. become integrated into chuck. Scot Gresham-Lancaster ¸,ø¤º°`°º¤ø¸,ø¤º°`°º¤ø http://o-art.org/Scot podcast: http://feeds.feedburner.com/blogspot/scotgl blog: http://scotgl.blogspot.com/ “In times of universal deceit, telling the truth is a revolutionary act.” —George Orwell

1 0