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

Re: [chuck-users] newbie questions
by Adam Tindale 02 Sep '07

02 Sep '07

Hi, Welcome Robin! You have asked a question that has been at the back of my mind for a long time. Thanks! <snip> > > >Sure! Just create a simple file that just holds a line like this; > >.8 => dac.gain; > >This will affect the dac's gain, no surprise there, but as the dac is >shared by all shreds this work more or less like a master fader. Replace >the .8 by any number between 0 and 1, depending on how severe the clipping >is, turn it down further if clipping re-occurs. > fadeout.ck exists I think. You can fadeout all of chuck with this method but it isn't great for smoothly dumping one shred while keeping the others active. <snip> > > These two questions lead me to wonder if there is any way of exposing > the implicit mixer prior to the DAC, so that levels and mutes on each > channel/shred could be controlled. > > > >What you could do is supply each shred with a envelope before the dac and >have that one ramp down before making the shred itself exit, based on some >command? > I like this suggestion. I would love to have some boilerplate code so that you could work with shreds in a kind of mixing environment where each shred had it's own volume control that could be *easily* (not necessarily simply) accessed from another place. I have used OSC in the past but I would love to see some other suggestions, possibly using command line arguments. This is a worthy tutorial for the manual ;) Anyone got something working? --art _________________________________________________________________ Former Police Officer Paul Gillespies TAKE BACK THE INTERNET tips and tricks, watch the video now http://safety.sympatico.msn.ca/

3 4

No sound with ChucK
by Aggelos Orfanakos 02 Sep '07

02 Sep '07

Hello, I've installed ChucK on my system (Gentoo Linux), I run chuck foo.ck (foo.ck from the tutorial) and there is nothing to listen. The strange thing is I don't get any errors either. It's like something is muted. I experimented with alsa-mixer but I had no results. Any ideas? Thanks in advance. -- Aggelos Orfanakos 0x89D2D3D0 (GPG) http://agorf.gr/

1 0

newbie questions
by robin.escalation 01 Sep '07

01 Sep '07

Do I downloaded the new ASIO patch to version 1.2.1.0 and everything worked perfectly in Windows XP feeding an RME Fireface. Congrats to all for making this such an exciting application! I look forward to live coding experiments using miniAudicle but have a couple of questions of a newbie nature. As I add shreds to the VM the output overloads. Is there an easy way of tweaking the master out all at once, without individually editing each shred file? Better yet, is there a way of making the shreds "output-sensitive" so they adjust automatically using some standard audio amplitude summing law? Killing a shred happens abruptly and not always too musically. How can this be done for nicer sonic output in performance? These two questions lead me to wonder if there is any way of exposing the implicit mixer prior to the DAC, so that levels and mutes on each channel/shred could be controlled. A further usability issue was revealed when I tried to use a patch from the examples folder that required sound files. These were referred to by relative pathing, but this only works if the script is run in its own folder. It appears there is no way to programmatically specify the root folder. So how does one integrate patches like this into a miniAudicle session? Thanks for your help with these very practical issues. I will be writing an article soon on ChucK for my blog diagrammes modernes, so will incorporate any tips. ----- Robin Parmar robinparmar.com

2 1

Re: [chuck-users] priorities for next release
by Adam Tindale 01 Sep '07

01 Sep '07

> > >Yes, we would all like this, I think. At least we have a WiKi page where >everybody can post additions, remarks and requests which should at least >decrease the strain on maintaining the manual. I believe Adam Tindale was >the last to be semi-officially in charge of the manual but other things >took his time. I'd volunteer but I'd need a proofreader as I'm not a native >English speaker and I still don't speak any Latex at all (the manual is >done in Latex) > >At least most things can be found by searching the list archives and the >manual isn't *that* out of date. Aside from the latest greatest stuff this >matter might be one of the worst missing bits. > > Hi All, I have been silent for a long while. I am always happy to proofread and hack stuff into the manual and make the commits (as long as Ge doesn't kick me off CVS). Like Ge, I just got a teaching gig and I am a bit swamped being new at all this. I have pleaded in the past for other people to submit tutorials or find mistakes in the manual and pass them on to me and the whole ChucK team. It now seems that there are so many experts that this dream is coming true. Most of what I did for the manual was to edit the original APIs into some semi readable form. A lot of that work was done by Ge and Phil and I just merely put it into LaTeX. There have been many people talking on the list about knowing how something works and not seeing it in the manual. If you do know and it isn't there, just write something up and tell me where you would like it be. The hardest part for me is starting something. If you get it started then the rest isn't so bad. I haven't worked on the manual in a long time and I am seeing that it is badly out of date. I will do my best to devote some time to it in the coming months (I am hoping to teach ChucK, so a good manual helps me too). If you have something you would like added to the official docs please send it along to me directly or via the list and I will be happy to add it. --art _________________________________________________________________ Former Police Officer Paul Gillespies TAKE BACK THE INTERNET tips and tricks, watch the video now http://safety.sympatico.msn.ca/

6 7

priorities for next release
by Ge Wang 31 Aug '07

31 Aug '07

Greetings! We are nearing the next very sporktacular release of ChucK and want to coordinate with you on organizing and prioritizing some bug fixes/ features/updates. We've been scouring through the forums, wiki pages, and posts and collected much good info. Thanks to all who have been kind and patient enough to enter requests, reports, and suggestions into the various pages. At this stage, we'd like to get your input on prioritizing them for the new release (in about 2 weeks). For this purpose, we've created two new wiki pages for feature requests/reports and bug reports/requests from here: http://wiki.cs.princeton.edu/index.php/ChucK/Bugs http://wiki.cs.princeton.edu/index.php/ChucK/Features Please enter full descriptions and concise accompanying code when helpful. While we can't guarantee that these would make it into the immediate next version, they are very helpful in getting a sense of disaster zones that needs more urgent attention, and is a chance to tidy up the information. If you don't want to deal with the wiki directly, feel free to post here or to chuck-dev, and our uh wiki specialists will transfer the text there. As for the manual, let's keep going here: http://wiki.cs.princeton.edu/index.php/ChucK/Manual Thank you very much! Let us know if you have any questions. Keep on ChucKin' Best, chuck team

11 22

chuck on linux-amd64?
by Robert Edge 28 Aug '07

28 Aug '07

I miss chuck. I was starting to get in to playing with last year, but I have since decided to go with a pure 64 bit system. I've got everything tuned and working the way I want now, but no chuck. I build every release I notice come out but still things do not work on Linux-amd64. What is the status of chuck and this architecture? I seem to remember talk of the issue being looked in to some time ago. Also, for what it's worth somebody is keeping a broken build in the Debian repositories, I've sent a bug report but no one seems to care. I think it's a shame that someone could get the wrong impression about this wonderful project.

1 0

heads up; follow up; up chuck
by Ge Wang 28 Aug '07

28 Aug '07

Greetings! As announced on the [chuck] list, we've just released a new major version (1.2.1.0) of chuck that introduces audio analysis in ChucK. For more details see: http://chuck.cs.princeton.edu/uana/ The paper: http://soundlab.cs.princeton.edu/publications/uana_icmc2007.pdf Just want to thank everyone for the recent discussion and also re- prioritizing of features. We are by no means done, and many new features outlined are underway. So please continue! We are hoping for several new releases in the coming weeks/months. Thanks again! Alrighty, go check out UAna, upchuck, and the new release! Let us know how it goes (or crashes)!! Best, chuck team

4 6

rec2.ck
by 2g 28 Aug '07

28 Aug '07

in another japanese chuck community i asked if somebody knows about "rec2.ck" which i cannot find in the examples dir and at last a person gave me the sample he found mm? this one seems to create 2 files instead of one stereo at this moment we cannot write stereo things to HDD? then i have to use sox to combine these maybe...? rec2.ck (not the original?): dac.left => WvOut wL => blackhole; dac.right => WvOut wR => blackhole; 4::second => dur l; now + l => time later; "./wavs/rec2L.wav" => wL.wavFilename; "./wavs/rec2R.wav" => wR.wavFilename; <<<"writing to file: ", wL.filename()>>>; <<<"writing to file: ", wR.filename()>>>; while ( now < later ) 500::ms => now; wL.filename() => wL.closeFile; wR.filename() => wR.closeFile; <<< "rec2 done." >>>; -- 2g http://micro.ispretty.com

3 7

list oriented ways to make this more simple?
by 2g 28 Aug '07

28 Aug '07

mmm...i seem to be writing same things too much can't any of these done in list[] oriented ways? sa.ck: SinOsc sun1 => Pan2 ps1 => dac; SinOsc sun2 => Pan2 ps2 => dac; SinOsc sun3 => Pan2 ps3 => dac; SinOsc sun4 => Pan2 ps4 => dac; SinOsc sun5 => Pan2 ps5 => dac; SinOsc moon1 => Pan2 pm1 => dac; SinOsc moon2 => Pan2 pm2 => dac; SinOsc moon3 => Pan2 pm3 => dac; SinOsc moon4 => Pan2 pm4 => dac; SinOsc moon5 => Pan2 pm5 => dac; .1 => ps1.gain; .1 => ps2.gain; .1 => ps3.gain; .1 => ps4.gain; .1 => ps5.gain; .1 => pm1.gain; .1 => pm2.gain; .1 => pm3.gain; .1 => pm4.gain; .1 => pm5.gain; 27.5 * Math.pow(2.0,(3.0/12.0)) => float oilsun; 27.5 * Math.pow(2.0,(5.0/12.0)) * 7.0/8.0 => float oilmoon; oilsun * Std.rand2(16,8) / 8.0 => sun1.freq; oilsun * Std.rand2(16,8) / 4.0 => sun2.freq; oilsun * Std.rand2(16,8) / 4.0 => sun3.freq; oilsun * Std.rand2(16,8) / 4.0 => sun4.freq; oilsun * Std.rand2(16,8) / 4.0 => sun5.freq; oilmoon * Std.rand2(16,8) / 8.0 => moon1.freq; oilmoon * Std.rand2(16,8) / 4.0 => moon2.freq; oilmoon * Std.rand2(16,8) / 4.0 => moon3.freq; oilmoon * Std.rand2(16,8) / 4.0 => moon4.freq; oilmoon * Std.rand2(16,8) / 4.0 => moon5.freq; fun void ga() { while(true) { 900::ms => now; Std.rand2f(-1.0,1.0) => pm1.pan; oilmoon * Std.rand2(16,8) / 8.0 => moon1.freq; Std.rand2f(-1.0,1.0) => pm2.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => moon2.freq; Std.rand2f(-1.0,1.0) => pm3.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => moon3.freq; Std.rand2f(-1.0,1.0) => pm4.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => moon4.freq; Std.rand2f(-1.0,1.0) => pm5.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => moon5.freq; 900::ms => now; Std.rand2f(-1.0,1.0) => pm1.pan; oilmoon * Std.rand2(32,16) / 8.0 => moon1.freq; Std.rand2f(-1.0,1.0) => pm2.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => moon2.freq; Std.rand2f(-1.0,1.0) => pm3.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => moon3.freq; Std.rand2f(-1.0,1.0) => pm4.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => moon4.freq; Std.rand2f(-1.0,1.0) => pm5.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => moon5.freq; } } fun void ma() { while(true) { 7500::ms => now; Std.rand2f(45.0,75.0) => oilsun; Std.rand2f(45.0,75.0) => oilmoon; } } fun void pa() { while(true) { 700::ms => now; Std.rand2f(-1.0,1.0) => ps1.pan; oilsun * Std.rand2(16,8) / 8.0 => sun1.freq; Std.rand2f(-1.0,1.0) => ps2.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => sun2.freq; Std.rand2f(-1.0,1.0) => ps3.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => sun3.freq; Std.rand2f(-1.0,1.0) => ps4.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => sun4.freq; Std.rand2f(-1.0,1.0) => ps5.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => sun5.freq; 700::ms => now; Std.rand2f(-1.0,1.0) => ps1.pan; oilsun * Std.rand2(16,8) / 8.0 => sun1.freq; Std.rand2f(-1.0,1.0) => ps2.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => sun2.freq; Std.rand2f(-1.0,1.0) => ps3.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => sun3.freq; Std.rand2f(-1.0,1.0) => ps4.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => sun4.freq; Std.rand2f(-1.0,1.0) => ps5.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => sun5.freq; } } spork ~ ga(); spork ~ ma(); spork ~ pa(); while( true ) { 3333::ms => now; } -- 2g http://micro.ispretty.com

2 2

what is this stk control change thing?
by Fitzpatrick, Denis F 25 Aug '07

25 Aug '07

My confusion is deep and multifaceted, but just to get started, I gather it's a way of setting various instrument parameters, but how does it differ from like-named (where they exist) method calls? I made a Googley effort to find this explained, but failed. I would gladly accept an answer in the form of a link. Denis Fitzpatrick Boys Town National Research Hospital (402) 498-6378 fitzpatrickd(a)boystown.org

2 1