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

Panic button?
by Ollie Glass 31 Oct '06

31 Oct '06

Related to Brian's question "how do you completely kill the audio from a shred in code?", is there a 'panic button' type command to completely kill all audio from chuck? Could be a useful feature. Ollie

3 3

Re: [chuck-users] Panic button?
by Ollie Glass 31 Oct '06

31 Oct '06

Sounds spot on and I'd expect it to work, just wondering if there might be a need for some under the hood control to kill the engine. Hopefully not! Ollie On 31 Oct 2006, at 17:00, chuck-users-request(a)lists.cs.princeton.edu wrote: > > Hmm, something like > > 0 => dac.gain; > > would probably do the trick. > > spencer > > On Oct 30, 2006, at 3:18 PM, Ollie Glass wrote: > >> Related to Brian's question "how do you completely kill the audio >> from a shred in code?", is there a 'panic button' type command to >> completely kill all audio from chuck? >> >> Could be a useful feature. >> >> Ollie >> _______________________________________________ >> chuck-users mailing list >> chuck-users(a)lists.cs.princeton.edu >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

1 0

Re: [chuck-users] question about sporking
by babiakb＠bellsouth.net 30 Oct '06

30 Oct '06

the code is up at the chuck forum at electromusic.com. i decided to separate the functions into separate .ck machines. everything worked perfectly then. Machine.add and Machine.remove. but when they are put all together and sporked in code, when removed, the notes stop processing but the last processed sample ran on for ever. actually, i tried unchucking the ugens at the end of the function and it still happened. but when called from .ck files on disk with machine.add and machine.remove everything was fine?!? i am using linux, ubuntu. alsa build. i believe this is a weird 1.2.7 bug that has something to do with my platform or hardware. brian > > From: Spencer Salazar <ssalazar(a)CS.Princeton.EDU> > Date: 2006/10/30 Mon PM 06:49:18 EST > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] question about sporking > > This is a strange problem... perhaps you could send some small > snippet of chuck source that reproduces the issue? > > One idea that might be worth trying is doing an un-chuck on all of > the shred's ugens from the dac before killing that shred. If I > recall correctly, the virtual machine should be doing this for you > for free, but maybe something is going wrong with that. Doing it > explicitly is supposed to stop all audio coming out of the ugens that > you unchuck. For example, for a patch like this: > > Blit b => LPF lowpass => dac; > BlitSquare sq => PRCRev rev => dac; > > you would unchuck everything directly connected to the dac before > exiting, like this: > > lowpass =< dac; > rev =< dac; > > spencer > > On Oct 29, 2006, at 12:03 PM, <babiakb(a)bellsouth.net> > <babiakb(a)bellsouth.net> wrote: > > > I sent a message earlier today but didn't see it. if it comes > > through twice for some reason, forgive. > > > > My problem is this: I spork a shred in code. I do this with a > > reference, like, spork ~ function () @=> Shred @ reference > > > > then when it's time to remove, i use Machine.remove( reference,id() ); > > > > the problem is, with oscillators and stks, the shreds do not stop > > audio cleanly. for example, when i have phasor => lpf => dac and > > remove the shred, the notes stop, but a high pitched tone lingers. > > also, when BlowBotl => rev => dac and remove the shred, the notes > > stop, but a medium pitched noise sound lingers forever. > > > > the time is synchronized to beat with now % T etc. I tried > > chucking and unchucking the ugens at the end of every loop. i > > tried with machine.add and remove from file instead of spork. i > > tried setting the gain and freq to zero at the end of every loop, > > but all these methods result in lingering sound. > > > > how do you completely kill the audio from a shred in code? > > > > any help? > > > > thanks in advance, > > brian > > > > > > _______________________________________________ > > 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 >

1 0

question about sporking
by babiakb＠bellsouth.net 30 Oct '06

30 Oct '06

I sent a message earlier today but didn't see it. if it comes through twice for some reason, forgive. My problem is this: I spork a shred in code. I do this with a reference, like, spork ~ function () @=> Shred @ reference then when it's time to remove, i use Machine.remove( reference,id() ); the problem is, with oscillators and stks, the shreds do not stop audio cleanly. for example, when i have phasor => lpf => dac and remove the shred, the notes stop, but a high pitched tone lingers. also, when BlowBotl => rev => dac and remove the shred, the notes stop, but a medium pitched noise sound lingers forever. the time is synchronized to beat with now % T etc. I tried chucking and unchucking the ugens at the end of every loop. i tried with machine.add and remove from file instead of spork. i tried setting the gain and freq to zero at the end of every loop, but all these methods result in lingering sound. how do you completely kill the audio from a shred in code? any help? thanks in advance, brian

2 1

stk Ugens between 1.2.0.6 -> 7
by Graham Coleman 30 Oct '06

30 Oct '06

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

4 7

Fwd: Linux Audio Conference #5 (LAC2007): Call for Papers - Music
by Kassen 29 Oct '06

29 Oct '06

Hi list! Marije Baalman asked me to forward the following, it's about a conference on Linux audio in Berlin. This might be a nice chance for anybody who would like to talk about ChucK or present a workshop or just jam with other musicians and spread the word. ChucK isn't realy speciffic to Linux but that might actually be good news for this context; I think much more fun can be had if people *don't* try their hardest to be incompattible with other platforms for a change... Yours, Kassen. ---------- Forwarded Message ---------- Subject: Linux Audio Conference #5 (LAC2007): Call for Papers - Music Date: Tuesday 17 October 2006 18:23 From: Simon Schampijer <simon(a)schampijer.de> To: lac2007(a)robin.kgw.tu-berlin.de Dear all, we are happy to announce the calls for papers for the 5th Linux Audio Developers Conference (LAC2007). The conference is organized by the TU-Berlin in cooperation with people of the Linux Audio Developers mailing list, the music festival Inventionen 2007 and the Humboldt University of Berlin. The LAC2007 is taking place at the TU-Berlin, Germany from the 22nd - 25th of March 2007. We have introduced some new tracks. Besides the category for papers, demos and workshops, calls for tutorials and hands on demos have been added. The tutorials aim is to give new (potential) users an overview of the possibilities of Linux Audio Software and how to get started. The LAC2007 provides a computer pool (LA Pool) where developers can give an introduction to their software and where participants can try out Linux Audio Software during the conference. This has been combined in the call hands on demos. Since the TU-Berlin is installing a new Wave Field Synthesis (WFS) system the call for music has been extended by a call for compositions for this system. Music that can be used for radio airplay can be submitted, and will after acceptance by the Campusradio of the TU Berlin, be played during the conference. More detailed Information can be found in the 'Call for Papers' attached to this email or on the website at: http://www.kgw.tu-berlin.de/~lac2007/ We are looking forward to many interesting submissions for the Linux Audio Conference 2007 and hope to see you in Berlin in 2007! Please feel free to forward this email to anybody who is interested. On behalf of the LAC2007 organisation team, Simon Schampijer and Marije Baalman ** Call for the Linux Audio Conference 2007 - 22nd - 25th of March 2007 taking place at the Technische Universität Berlin in cooperation with Inventionen 2007 and the Humboldt University of Berlin This call includes: Call for Papers Call for Demos Call for Hands On Demos Call for Workshops Call for Tutorials Call for Music (categories: Concert, Club, Radio and Wave Field Synthesis) ----------------------------- Call for Papers We invite submissions of papers addressing all areas of audio processing based on Linux and open source software. Papers can focus on technical, artistic or scientific issues and can target developers or users. This includes (but is not limited to) the following categories: Computer Music Music Production Instruments Drivers and Sound Architecture Audio Distributions Generic (Usage, Documentation etc.) The conference is held in English. Length of a paper is 4-8 pages. Papers have to include an abstract (50-100 words). The abstract will be published separately on the conference website once the paper has been accepted. Also, papers should include up to 5 keywords. In general talks should take 20-30 minutes followed by 5 minutes discussion. Please notify us if you need a special technical setup. The technical standard setup will be: microphone (head set) projector with XVGA input (resolution 1024x768) stereo speaker setup with mini jack input a PC with a pdf viewer How to submit File format is PDF, formatted for A4 paper. Make use of the templates for paper formatting available at: http://www.kgw.tu-berlin.de/~lac2007/download/templates-lac2007.tar.gz See our check list to ensure that you do not forget to enclose all necessary information. Send your paper and all necessary information by 8 Jan 2007 via email to this address: lac2007 AT robin.kgw.tu-berlin.de You will be notified by 05 Feb 2007 whether your paper has been accepted. The reviewers may ask you to modify your paper in order to be accepted. The deadline for the final version is March 1, 2007. Important Dates 08 Jan 2007: Paper submission deadline 05 Feb 2007: Notification of acceptance 01 Mar 2007: Final version deadline 22 - 25 March 2007: Conference ----------------------------- Call for Demos You do not need to write a whole paper, but rather a short abstract only (50-100 words). This category is mainly thought for software demos. Be aware though that in case of too many submissions papers take priority over demos... See section "Call for Papers" for info on the duration of talks and the technical setup. ----------------------------- Call for Hands On Demos A new item of the LAC 2007 is LA Pool: a pool with Linux audio computers, on which programs can be demonstrated. To give a "hands on" demo you can reserve LA Pool for 1 hour, of which ca. 20 minutes can be used as a general introduction and the rest should be free for participants to try out the program and ask questions. A Hands On demo can be held in addition to a Paper Presentation or as the presentation for the Demo, so you need to either submit a paper or an abstract as mentioned above. Additionally, you need to give us a version of your software, with clear installation instructions and requirements, so that we can install the software on the Pool before the conference. How to submit See our check list to ensure that you do not forget to enclose all necessary information. Send your abstract and all necessary information by 8 Jan 2007 via email to this address: lac2007 AT robin.kgw.tu-berlin.de Deadline for submissions is 08 Jan 2007. You will be notified by 05 Feb 2007 whether your submission has been accepted. ----------------------------- Call for Workshops With respect to their content workshops do not differ from talks: Workshops can have technical focus as well as artistic or scientific focus. Workshops can be targeted to developers as well as users. See section "Call for Papers" for more info on this. The shape of the workshop is completely up to you. E.g. it can be tutorial-like ("how to write an ALSA driver/ a jack application/ a LADSPA plugin/ etc.") or it can be BOFS-like (e.g. a meeting of like-minded users and/or developers to exchange experience and knowledge about a specific topic), or it can be anything in between. Workshops can take place in seminar rooms or in a public space like the TU Lichthof. Depending on the location, attendance might be limited to ca 10 people. We strongly encourage you to submit early. It will be more likely to get a free slot and it will be easier for attendants to know about the workshop if it is published on the conference website. If you expect the attendants to prepare their laptops for your workshop (e.g. by installing some software) or if there are other requirements, please note so in your abstract. How to submit: See our check list to ensure that you do not forget to enclose all necessary information. Send an abstract (ca. 50-100 words) and all necessary information via email to this address: lac2007 AT robin.kgw.tu-berlin.de The abstract will be published on the conference website once the workshop has been accepted (not before 01 March 2007 though). Submission deadline is 05 Feb 2007. You will be notified by 01 March 2007 whether your submission has been accepted. ----------------------------- Call for Tutorials New in this edition of the Linux Audio Conference will be a Tutorial track for new users. This Tutorial track will be hosted by the Media Science Department of the Humboldt University of Berlin. Proposals for additions to this Tutorial program are welcome. The aim of this Tutorial track is to give new (potential) users an overview of the possibilities of Linux Audio Software and how to get started. The difference to workshops is that the tutorials are given in a lecture environment and should focus on how to make music with Linux, more than going into specifics of certain programs. The tutorial track is supported by the LA Pool facility as attendants can try out the software themselves with hands on support. Send a short description of your proposed Tutorial topic (ca. 50-100 words), via email to this address: lac2007 AT robin.kgw.tu-berlin.de Submission deadline is 08 Jan 2007. You will be notified by 05 Feb 2007 whether your submission has been accepted. Criteria will be based upon creating a full fledged Tutorial program for Linux Audio. ----------------------------- Call for Music The conference will include several concerts. We are looking for music that has been produced completely or mostly under Linux and/or with open source software: Serious compositions, Electronica, Chill-Out, Ambient etc. Indicate whether you want to have your piece played in a concert like environment or a club like environment. Additionally you can submit Radio music (see below) and Wave Field Synthesis music (see also below). Additionally you are welcome to give a talk about your piece. We encourage you especially to show how you made the piece using open source software. Please send a short abstract (ca. 50-100 words) if you want to give a talk. If you want to participate, send your composition(s) to this address: LAC2007 - Call for Music Institute of Communications Research Sekretariat EN 8 Einsteinufer 17 D-10587 Berlin Germany Make use of one of the following media formats: Media: Audio-CD, DVD, DVD-R or CD-R File formats: aiff or wav Channels: mono, stereo, multi-channel and multi-mono (8 channels is no problem, more than 8 must be discussed). Samplerate: 44.1 or 48 kHz Resolution: 16 or 24 bit Include the following items with your submission (in English): A filled-out and signed printout of the form available here: http://www.kgw.tu-berlin.de/~lac2007/download/musicagreement.pdf For the printed program and to be published online and on the conference CD, in continuous text (no table or list please): A short commentary on the composition(s) (each ca. 150 words) A short Curriculum Vitae (ca. 100 words) Deadline for submissions is 08 Jan 2007. A jury will select the compositions that will be performed/played. Furthermore, the jury will give out three prices to participants to contribute to their travel expenses. Besides artistic criteria and technical reasons, these criteria apply for the selection: Tape pieces or pieces which are performed by the composers themselves will generally have more chances to get included. If we get more pieces than we can include in the program, composers who are attending the conference are preferred. Terms and conditions for participation can be found in the form mentioned above. This form includes among other things: I will receive no fees whether my composition is played or not. GEMA fees (in case of performance) will be paid by the organizer. The material I send to the TU Berlin will not be returned. Additionally to this Call for Music, during the late night concerts there will be an open stage: "Plug & Chill - The Linux Jam Nights" where attendants of the conference are invited to perform their pieces in a more club-like context. There is no deadline for this, so people can decide during the conference if they want to participate. However if you already know that you want to participate do not hesitate to inform us. Send us an email to lac2007 AT robin.kgw.tu-berlin.de and include a description of your equipment and a short characterization of your music (keywords only). During the conference it is possible to register at the info desk. Note that there is a time limit for "Plug & Chill". If we have received too many registrations already you might not get a slot. Contributions to "Plug & Chill" should not exceed 10 min. There will be a room at the TU Berlin where people can meet during the conference and rehearse for "Plug & Chill". ----------------------------- Radio Music A new category in the Music call is the call for music that can be used for radio airplay. In cooperation with the Campusradio ( http://www.campusradio-online.de) of the TU Berlin, who will do a live report on the conference, we invite composers, musicians and producers of Music made or recorded and mastered with Open Source tools, to submit their works. If you want to participate, send an email to: lac2007-radio AT robin.kgw.tu-berlin.de with a link to your audio files. Alternately, send your music to the address above, with the addition: LAC2007 - Call for Music Radio Make use of one of the following media formats: Media: Audio-CD, DVD, DVD-R or CD-R File formats: aiff or wav or ogg Channels: mono or stereo Samplerate: 44.1 or 48 kHz Resolution: 16 or 24 bit Include the following items with your submission (in English): A filled-out and signed printout of the form available here (sent by mail, or by fax to: +49 30 31421143): http://www.kgw.tu-berlin.de/~lac2007/download/musicagreement.pdf Deadline for submissions is 05 Feb 2007. The choice of which pieces are played is in the hands of the Campusradio crew. A program listing will be on their website http://www.campusradio-online.de shortly before the conference. ----------------------------- Wave Field Synthesis Music Shortly before the conference, a new Wave Field Synthesis (WFS) system will be installed in one of the lecture halls of the TU Berlin. We are looking for composers who are interested in creating a composition for this system or who have already written pieces for WFS, which could be played on the system. The WFS system will be based on the sWONDER software ( http://swonder.sourceforge.net), and can be controlled by OSC. For more information, please contact us at lac2007 AT robin.kgw.tu-berlin.de As there is no standard format for WFS material yet, we ask for a elaborate description of the piece and some examples of previous works. To prepare the piece for performance, it will be necessary for the composer to be present a few days before the conference. We will support efforts to get funding for this from external organizations (such as DAAD). Send your material to this address: LAC2007 - Call for WFS Music Institute of Communications Research Sekretariat EN 8 Einsteinufer 17 D-10587 Berlin Germany Make use of one of the following media formats: Media: Audio-CD, DVD, DVD-R or CD-R File formats: aiff or wav Channels: mono, stereo, multi-channel and multi-mono (8 channels is no problem, more than 8 must be discussed). Samplerate: 44.1 or 48 kHz Resolution: 16 or 24 bit Include the following items with your submission (in English): A filled-out and signed printout of the form available on: http://www.kgw.tu-berlin.de/~lac2007/download/musicagreement.pdf For the printed program and to be published online and on the conference CD, in continuous text (no table or list please): A short commentary on the composition(s) (each ca. 150 words) A short Curriculum Vitae (ca. 100 words) Deadline for submissions is 08 Jan 2007. Terms and conditions for participation can be found in the form mentioned above. This form includes among other things: I will receive no fees whether my composition is played or not. GEMA fees (in case of performance) will be paid by the organizer. The material I send to the TU Berlin will not be returned.

1 0

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

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

Re: [chuck-users] How can I filter silence?
by Jim Hinds 25 Sep '06

25 Sep '06

Kas, Graham! Ya gotta love the way you think out of the box. Break the rules to make better ones! Thanks for the comments, code and inspiration. Jim ---"I dream of cheese, It's toasted, mostly" Ben Gunn, Treasure Island. On Sep 24, 2006, at 8:55 09PM, Graham Coleman <gc(a)gehennom.net> wrote: > > From: Graham Coleman <gc(a)gehennom.net> > Date: September 24, 2006 9:50:44 AM HST > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Cc: jahbin(a)romatictrances.com > Subject: Re: [chuck-users] How can I filter silence? > Reply-To: ChucK Users Mailing List <chuck- > users(a)lists.cs.princeton.edu> > > > I came up with some cheesy code to implement the idea. > It speeds up the tape when it hits silence. You'll need to > tune the time constants and the threshold for best results: > > sndbuf buf => dac; > buf.read("speak/wave.wav"); > buf.pos( 0 ); > > 0.05 => float tresh; > 0.01 => float rt; //release const > 0.4 => float at; //attack const > float xd; > > while(true) { > > math.fabs( buf.last() )-xd => float a; //amp diff > if ( a < 0 ) 0=>a; //non-negative > xd*(1-rt)+at*a => xd; //the attack/release exponential filter > > if ( xd<tresh ) { > buf.pos( buf.pos()+6 ); //skip ahead > } > > 1::samp=>now; > } > > To compute the time constants, use this formula: > //AT = 1 - e ^ (-2.2T/t<AT) > > or this if t is in samples: > > time const = 1.0 - exp( -2.2 / t ); > > best, > > Graham > > On Sun, 24 Sep 2006, Graham Coleman wrote: > >> I'm not sure if there's anything in chuck that will currently do >> this, >> but I think you could write something like a noise gate, that >> tracks the >> amplitude of samples coming from a SndBuf and skips ahead until >> the level >> rises above a threshold. >> >> Not sure how well this would run in real time. >> >> Better, would be something that preprocesses the file with in/out >> points >> so the skips are quick. >> >> Graham >> >> On Sun, 24 Sep 2006, Jim Hinds wrote: >> >>> I want to scan some audio for dropped out sections. It's long and >>> talky with 'significant' pauses between question and answers. These >>> sections are filled with background noise, and often several seconds >>> long. I'd like to shorten these empty sections (there are a lot of >>> them). >>> >>> I'd like to keep the files more or less intact (not sliced up into a >>> zillion intermediate files) >>> >>> Is there a unit in chuck that will be able to delete samples as they >>> pass through? >>> >>> Jim >>> _______________________________________________ >>> 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 >> > > > > > From: Kassen <signal.automatique(a)gmail.com> > Date: September 24, 2006 10:23:58 AM HST > To: "ChucK Users Mailing List" <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] How can I filter silence? > Reply-To: ChucK Users Mailing List <chuck- > users(a)lists.cs.princeton.edu> > > > > > On 9/24/06, Graham Coleman <gc(a)gehennom.net> wrote: > I'm not sure if there's anything in chuck that will currently do this, > but I think you could write something like a noise gate, that > tracks the > amplitude of samples coming from a SndBuf and skips ahead until the > level > rises above a threshold. > > Not sure how well this would run in real time. > > Better, would be something that preprocesses the file with in/out > points > so the skips are quick. > > > But.... It doesn't look like it needs to be realtime. > > I'd think about playing the file once and storing the sample > locations where the volume drops below a treshold (as well as the > ones where it comes back) in a array, then playing it a second time > and skipping those sections while writing the results to a new > file. in "silent" mode this should be doable faster then realtime. > > You could also make a array of the length of the file (in samples) > and only write buf.last() => array[sample++] as long as it's over > the treshold. Once the buffer reaches it's end you'd playback the > array again and record that, taking care to stop after the highest > value that "sample" got to in the first pass. This would be CPU > intesive but it's quite clean as a method, I think. > > It all stands or falls with the quality of the envelope follower. > > I've been thinking about doing something similar to the first > option and pre-scanning wavefiles for positive zero-crossings and > storing those in a array. This would take extra time when loading a > file but from then on you could do very clean loops, for example to > loop just a few cycles. I wonder how samplers that have a "snap to > zero crossings" setting do this. It might still be quite tricky > because not all samplers that do this do it all that well.... > > Hope that's of some use. > Kas. >

2 1

##ChucK @ freenode
by Tasmo 25 Sep '06

25 Sep '06

Even though the mailinglist is a good place for the ChucK coders comunity I thought about a live conversation. So I want to announce the unofficial ##Chuck channel at the freenode network: irc://irc.freenode.net/##ChucK You're very welcome to join and chat! The double ## means at freenode this is not a primary group channel (yet). http://freenode.net/policy.shtml#topicalchannels Tasmo

3 6

How can I filter silence?
by Jim Hinds 24 Sep '06

24 Sep '06

I want to scan some audio for dropped out sections. It's long and talky with 'significant' pauses between question and answers. These sections are filled with background noise, and often several seconds long. I'd like to shorten these empty sections (there are a lot of them). I'd like to keep the files more or less intact (not sliced up into a zillion intermediate files) Is there a unit in chuck that will be able to delete samples as they pass through? Jim

3 3