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

Re: [chuck-users] String concatenation
by Graham Coleman 09 Oct '06

09 Oct '06

Norman, There's currently no support for building strings - strings are immutable once they are initialized from literals. String ops have been in development, but are waiting garbage collection to be added. A workaround for your task is to generate a large literal array of filenames in text and index them: ["a.wav","b.wav","c.wav","d.wav","e.wav","f.wav","g.wav","h.wav", "i.wav","j.wav","k.wav","l.wav","m.wav","n.wav","o.wav","p.wav", "q.wav","r.wav","s.wav","t.wav","u.wav","v.wav","w.wav","x.wav", "y.wav","z.wav","aa.wav","bb.wav","cc.wav","dd.wav","ee.wav"] @=> string names[]; > By the way, I'm doing the split by elaborating on > > SndBuf ibuf; > "test.aif" => ibuf.read; > 0 => ibuf.pos; > > WvOut ofile; > "out0.aif" => ofile.aifFilename; > > ibuf => ofile => blackhole; > 2::second => now; > > ofile.closeFile; > > Does that look reasonable, or am I misunderstanding something (on a > few hours' acquaintance with ChucK)? You might need parens on the function call: ofile.closeFile(); best, Graham On Mon, 9 Oct 2006, Norman wrote: > Greetings. > > Is there any support for building up strings within ChucK? > > I'd like to do something like > > WvOut ofile; > 0 => int idx; > "out" + idx + ".aif" => ofile.aifFilename; > > I'm trying to produce a script which will split an input file into > short sections. I think I can see how to do most of it, but can't > work out how to generate file names. > > The "string" type is mentioned in passing in the 'type' section of > the manual, but with no indication of what methods it might have (I > tried "idx => ofile.append", but...). Googling for 'string' at > chuck.csc.princeton.edu doesn't indicate that I've missed anything > major. And I can't spot anything in the FAQ at <http:// > wiki.cs.princeton.edu/index.php/ChucK>, other than a `medium > priority' note `string operations' in <http://wiki.cs.princeton.edu/ > index.php/ChucK/Dev/DoThisNow>. Does this latter note mean that this > isn't possible, but might be soon? > > > Thanks for any pointers. > > Norman >

1 0

sporking shreds, advancing time
by vb 08 Oct '06

08 Oct '06

hi all, i'm still struggling with the basics of chuck, it seems. let's say i have a process i want to have executed regularly, like a simple click of an impulse. is it more appropriate for chuck's liking to advance time inside the impulse function and spork it only once, or to spork the impulse function regularly? volker. // begin example 1 Impulse i => dac; fun void click() { while(true) { 1.0 => i.next; 0.5::second => now; } } spork ~click(); while( true ) 1::second => now; // end example 1 // begin example 2 Impulse i => dac; fun void click() { 1.0 => i.next; } while( true ) { spork ~click(); 0.5::second => now; } // end example 2

2 4

String concatenation
by Norman Gray 05 Oct '06

05 Oct '06

Greetings. Is there any support for building up strings within ChucK? I'd like to do something like WvOut ofile; 0 => int idx; "out" + idx + ".aif" => ofile.aifFilename; I'm trying to produce a script which will split an input file into short sections. I think I can see how to do most of it, but can't work out how to generate file names. The "string" type is mentioned in passing in the 'type' section of the manual, but with no indication of what methods it might have (I tried "idx => ofile.append", but...). Googling for 'string' at chuck.csc.princeton.edu doesn't indicate that I've missed anything major. And I can't spot anything in the FAQ at <http:// wiki.cs.princeton.edu/index.php/ChucK>, other than a `medium priority' note `string operations' in <http://wiki.cs.princeton.edu/ index.php/ChucK/Dev/DoThisNow>. Does this latter note mean that this isn't possible, but might be soon? By the way, I'm doing the split by elaborating on SndBuf ibuf; "test.aif" => ibuf.read; 0 => ibuf.pos; WvOut ofile; "out0.aif" => ofile.aifFilename; ibuf => ofile => blackhole; 2::second => now; ofile.closeFile; Does that look reasonable, or am I misunderstanding something (on a few hours' acquaintance with ChucK)? Thanks for any pointers. Norman -- ------------------------------------------------------------------------ ---- Norman Gray / http://nxg.me.uk eurovotech.org / University of Leicester, UK

1 0

mac intel audio i/o problem
by Manj Benning 03 Oct '06

03 Oct '06

hi i am running chuck 1.2.0.7 for the first time on my mac intel.And i keep getting the following problem when i try running the code below ------------------------ error msg: [chuck]: (via rtaudio): unable to open specified device(s) with given stream parameters: ... RtApiCore: unable to find OS-X audio stream on device (Apple: Built-in Microphone) for requested channels (2). [chuck]: cannot initialize audio device (try using --silent/-s) --------------------- code: --------------------- adc => dac; while( true ) { 100::ms => now; } ---------------------- when i do chuck --probe (output shown below) all devices, regardless if they are input (adc) or output (dac) are shown as dacs. With inputs channels set to 2 when the imic and line in are single channel devices. Whats up with this? And the built in mic on my laptop is working just fine when i check through the system prefs. thanks Manj ------------------------------- Macintosh-4:~/Documents/Development/chuck/code manj$ chuck --probe [chuck]: found 4 device(s) ... [chuck]: ------( chuck -- dac1 )--------------- [chuck]: device name = "Apple: Built-in Microphone" [chuck]: probe [success] ... [chuck]: # output channels = 0 [chuck]: # input channels = 2 [chuck]: # duplex Channels = 0 [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 [chuck]: [chuck]: ------( chuck -- dac2 )--------------- [chuck]: device name = "Apple: Built-in Input" [chuck]: probe [success] ... [chuck]: # output channels = 0 [chuck]: # input channels = 2 [chuck]: # duplex Channels = 0 [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 [chuck]: [chuck]: ------( chuck -- dac3 )--------------- [chuck]: device name = "Apple: Built-in Output" [chuck]: probe [success] ... [chuck]: # output channels = 2 [chuck]: # input channels = 0 [chuck]: # duplex Channels = 0 [chuck]: default device = YES [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 [chuck]: [chuck]: ------( chuck -- dac4 )--------------- [chuck]: device name = "Apple Computer, Inc.: Aggregate Device" [chuck]: probe [success] ... [chuck]: # output channels = 2 [chuck]: # input channels = 2 [chuck]: # duplex Channels = 2 [chuck]: default device = YES [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 [chuck]: [chuck]: ------( chuck -- 0 MIDI inputs )------ [chuck]: [chuck]: ------( chuck -- 0 MIDI outputs )----- [chuck]:

3 4

constructing UGens by composition
by Graham Coleman 03 Oct '06

03 Oct '06

Object Orientaters, In languages like Java or ChucK, there are two OO ways to reuse code (besides copy-paste): by Inheritance: in this method, the class being defined is an elaborated version of the parent class (uses the extends command), like the way Orange is a special version of a Fruit by Composition: in this method, the class being defined is pieced together with instances of other classes, perhaps the way a Car class might be assembled with four instances of Wheel Now, if we wish to make a special version of a UGen by inheritance alone, we can already do this. By extending the UGen class you wish to use, you should be able to add or overwrite methods or variables. But what about composition? What if we wish to chain together several already useful into some compound effects object (for brevity's sake, perhaps)? public class StdFx extends UGen { //preconstructor PoleZero pz => NRev nrev => pan2 p; //dc filter - some STK synths need this pz.blockZero( 0.99 ); //no rev by default nrev.mix( 0.0 ); //random pan p.pan( std.rand2f( 0.1, 0.9 )); //omitted: controls for pan, rev, gain ... } This does the trick, basically. However, ChucK has no way of knowing that, to connect an object to StdFx, you connect its input to the PoleZero and the output from the pan2 into the output of this UGen. We must create a method to facilitate this: public void inOut( UGen in, UGen out ) { in => pz; p => out; } Which sort of breaks the flow in the calling program; sndbuf inst; StdFx stdfx; stdfx.inOut( inst, dac ); instead of just: snfbuf inst => StdFx stdfx => dac; So, to get the behavior we are going for in the language, it seems like the most direct way would be to specify an in and out reference for the correct UGens like so: public class StdFx extends UGen { //preconstructor PoleZero pz => NRev nrev => pan2 p; pz @=> this.in; p @=> this.out; //other stuff ... } So, will this kind of behavior be possible within the language as currently designed? I don't know. Most likely this behavior would stem from the implementation of Chuck_UGen::add( Chuck_UGen * src ) which is eventually executed by the VM on finding a => that resolves to a link operation. Offhand, we come up with two alternatives for producing this kind of behavior: 1. route link operations of a composite UGen in Chuck_UGen::add 2. some sample copying arrangement that would seem similar to linking So, what's the plan for supporting this? Graham

2 1

how to set bufsize in miniaudicle
by vb 29 Sep '06

29 Sep '06

hello chuckers, just started looking into chuck and miniaudicle and already had a lot of fun playing with it. thanks a lot for making this available! i'm wondering how to set the bufsize when using miniaudicle (v. 0.1.3.6). using chuck in the terminal, i can do something like: chuck --bufsize512 myFile.ck how would i do this in miniaudicle? thanks, volker.

2 4

heads up for 1.2.0.7
by Ge Wang 28 Sep '06

28 Sep '06

Greetings fellow ChucKists, Here is a (not so) quick summary/warning about upcoming changes in chuck-1.2.0.7, to be released probably next week. what it don't got: - garbage collection is still on a holding pattern and will not be in 1.2.0.7 - the long-overdue string operations, unfortunately, insist on waiting for garbage collection, and also will not in 1.2.0.7 - file i/o api's have been implemented (thanks to Martin Robinson), will be included soon but not in 1.2.0.7 Sorry about that. Now that we've apologized about what's not in the release, it's time to apologize about what is. Due to recent discussions on this list, two sets of changes and additions have been made. We want to preview them here to get feedback before setting them in concrete. API deprecations. Our discussion more or less determined that it's best to unify the naming scheming now before things get further out of hand, particularly for UGen names and such. So the current solution deprecates the object names in question and provides more consistent naming. By default, when a deprecated name, such as 'sinosc', is encountered, a warning will be issued, such as 'line(1): deprecated: 'sinosc' --> use: 'SinOsc''. The behavior should be otherwise unchanged. In other words the program should still work as before. We've also added a --deprecate flag that allows you to stop, warn, or ignore upon encountering a deprecated item. The default is 'warn'. Here are the objects deprecated so far, and their replacements: - (api) deprecated --> new classes -------------------------- sinosc --> SinOsc triosc --> TriOsc sqrosc --> SqrOsc sawosc --> SawOsc pulseosc --> PulseOsc phasor --> Phasor osc --> Osc noise --> Noise cnoise --> CNoise impulse --> Impulse step --> Step halfrect --> HalfRect fullrect --> FullRect gain --> Gain zerox --> ZeroX delayp --> DelayP sndbuf --> SndBuf pan2 --> Pan2 mix2 --> Mix2 onepole --> OnePole onezero --> OneZero polezero --> PoleZero twopole --> TwoPole twozero --> TwoZero biquad --> BiQuad std --> Std math --> Math machine --> Machine A few more UGen's. From another discussion on list, also by popular demand, it seems convenient to have out-of-the-box filters, in addition to general 1st and 2nd order filters (OnePole/Zero, BiQuad, etc.). We've examined and plundered from Csound, SC, and PD source code, and chuckified a few UGen's. We are going to do this in installments, adding various UGens every release. In 1.2.0.7, They include: LPF : lowpass filter (2nd order butterworth) (also with cutoff resonance control) HPF : highpass filter (2nd order butterworth) (also with cutoff resonance control) BPF : bandpass filter (2nd order butterworth) BRF : bandreject filter (2nd order butterworth) ResonZ : resonant filter (BiQuad with equal-gain zeros) FilterBasic : base class to above filters Of course, all of these can be designed and implemented using existing filters, but these provide direct access to cutoff and Q out-of-the-box and behave in a familiar um Butterworthy way. (More are on the way) We'd appreciate your feedback on these. For example: 1. api changes are in general, not reasons for group celebration. what can be done to further smooth the transition? 2. new naming optimal? 3. anything else Thanks! Best, chuck team

11 36

A friendly note on joypad axes.
by Kassen 28 Sep '06

28 Sep '06

Hi list! Spencer and me figured out that with the new version of the HID object some axes changed name compared to the old version. At least number 3 is now called 5 and so there's probably (hopefully?) at least one more change. This will affect existing code so I thought it'd be nice to have it out in the open instead of leaving it to cause undocumented confusion. Not sure where stuff like that officially goes? Kas.

1 0

irc://irc.freenode.net/#ChucK
by Tasmo 27 Sep '06

27 Sep '06

finally welcome to irc://irc.freenode.net/#ChucK tasmo

1 0

list searching
by Tasmo 26 Sep '06

26 Sep '06

Is there any possebility to search the users list archive like through an online interface? Sometimes I wish to view entries only discuss a specific topic.

2 2