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

Re: [chuck-users] stk Ugens between 1.2.0.6 -> 7
by babiakb＠bellsouth.net 26 Oct '06

26 Oct '06

well, i just used BlowHole in a song on Linux (Ubuntu) with chuck 1.2.0.7 and everything is good. i am sorry to hear about windows, but i wanted to let you know for sure the problem would appear to be confined to windows. > > From: Graham Coleman <gc(a)gehennom.net> > Date: 2006/10/26 Thu PM 11:37:22 EDT > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] stk Ugens between 1.2.0.6 -> 7 > > More details: > > It seems that for the builds that I have, > audicle 1.0.0.4 and chuck 1.2.0.7 on win32 > > the following STK ugens are not totally disconnected, > but start very very soft and take a while to get louder? > > Clarinet, ModalBar, BlowHole, Saxofony, VoicForm > > Haven't figured out what could be causing this yet. > > best, > > Graham > > On Wed, 25 Oct 2006, Graham Coleman wrote: > > > ChucKtivists, > > > > I'm having a problem with some of the Stk Ugens in 1.2.0.7-- > > certain Stk instruments no longer seem to play. > > > > Originally I noticed the problem in audicle 1.0.0.4 from 1.0.0.3. > > I prepared musical material for a local music competition using ...3 > > to be risk averse, but ...4 doesn't seem to play the parts using these > > instruments. Then I tracked it back to chuck. > > > > testStk.ck should demonstrate the basic problem-- > > if you are subject you may only hear one scale by one instrument (1.2.0.7) > > > > testStkAll.ck tests the whole gamut of StkInstruments. > > > > I have not yet tested the STK Ugens that are not StkInstruments. > > > > I'm on win32 and using lots of deprecated names, but hopefully neither > > make a difference. > > > > has anyone else seen this? > > > > best, > > > > Graham > _______________________________________________ > chuck-users mailing list > chuck-users(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >

1 0

mailing list archive search
by Spencer Salazar 23 Oct '06

23 Oct '06

Hey everyone, It has always been possible to search the various chuck mailing lists by means of your favorite search engine, but now the ChucK dev team has cut out the middleman (sort of). You can direct all of your chuck, chuck-users, chuck-dev, and audicle list archive searching needs to http://chuck.cs.princeton.edu/ community/, where you can easily Google-search those lists by keyword, without having to type the 'site:' restriction into the standard Google search query. Though, I believe Google's index is updated around once per week for a given site, so it won't always be completely up to date. spencer

1 0

Geting strange key combinations
by Hilquias.Abreu 22 Oct '06

22 Oct '06

how to catch strange combinations of hotkeys, like f1+enter? thanks, sorry by my babelfish english :-) _______________________________________________________ Novidade no Yahoo! Mail: receba alertas de novas mensagens no seu celular. Registre seu aparelho agora! http://br.mobile.yahoo.com/mailalertas/

6 9

Re: [chuck-users] manual, was; Geting strange key combinations
by Kassen 21 Oct '06

21 Oct '06

On 10/21/06, Adam Tindale <adamtindale(a)hotmail.com> wrote: > > The manual is badly outdated. I am in the process of a major > revision. Maybe we can start a page on the wiki of things to revise > in the manual for the next release. If anyone wants to help I would > greatly appreciate it. Sure. I still don't speak Latex but I'd be happy to add stuff that pops up on the forum or that I stumble into myself to such a page. The forum is a good source for such material because there are a lot of people just starting out there and they ask questions if the manual is unclear or outdated. I'd be happy to write a few paragraphs as well on areas I'm comfortable with. Oh, and could somebody please go into what the word "new" means in ChucK, exactly? It's currently mentioned in the manual exactly once (in that sense). It creates a new instance of a object and it's somehow syntactically similar to "!" and that's about it as far as the manual is concerned. This made the public static classes thing quite hard to understand for me untill Spencer demonstrated a while ago you can get around it (and now I understand that assignment trick). So, great plan, I'd be happy to contribute to this wiki page but we'll still need the list because I predict that the people who discover something is missing from the manual are probably not the people who can write the manual entry.... My cents, Kas.

2 3

TextMate bundle
by Tasmo 12 Oct '06

12 Oct '06

Hi ChucK on Mac users, I just finished my 1st version of a ChucK's language bundle for the popular editor Textmate (http://www.macromates.com/). The syntax file is based on Jesús Gollonet's Chuck jedit edit mode. Thank you Jesús! The bundle includes syntax highlighting, completition and basic ChucK remote through basic shortcuts. That means: You can start the Terminal.app with chuck in loop mode (I choosed 'chuck -l --bufsize 512'), add the actual file (without needing to save) (shortcut), remove last patch/programm (shortcut) and kill ChucK's engine. Please tell me if you wish to add some features and/or correct the syntax. The link to the first release: http://www.box.net/public/i2t4zjm4f3 Tom

1 0

Sharing Instantiated Objects Thru Shreds
by Piero B. Contezini 11 Oct '06

11 Oct '06

Hello, Maybe i'm missing something, but I need to share a instantiated object between my shreds, as this object will control the music flow, I need all my shreds to share this instance. It works like this: Shred 1 controls the basic bass sequence Shred 2 controls the fx sequence There is a common class between them notifying each shred when they must change their random parameters (for sequencing everything in the right compasses), but the class itself doesn't work if it has no instance controlling the time poll interval, so in a programming language I should implement a shared memory area with mutexes to control the access of the main object, anyone had this problem before? I'm still figuring out how to put my ideas on Chuck, maybe i'm just doing something that's already done. Basicly i'm thinking this way because of the common way eletronic music is built on (8 beats as a word, 32 beats as phrase, and so on) In this way, I can't just add a new shred to the machine without being in the right compass (in a new phrase) , I could use timing, but I still want to make breaks (with effects of course) live, where I just set the main object to stop allowing the shreds to processes its next words/phrases , play the hole effect, and leave the control of the machine to the old shreds again. Is this just insane? Thanks Piero

3 2

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