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

blind user
by tempjayren＠gmail.com 04 Sep '10

04 Sep '10

Would like to know if there are any other blind users of chuck besides myself and perhaps talk to them offlist so as to not spam the list needlessly.

7 13

Re: [chuck-users] "Or"
by Rebecca Fiebrink 04 Sep '10

04 Sep '10

OR, because it's chuck and therefore more fun than your average language: if (maybe) 1.0 => sampleRate; else 1.5 => sampleRate; > > > Message: 2 > Date: Fri, 3 Sep 2010 11:21:34 -0400 > From: Timothy Leonido <timothy.leonido(a)gmail.com> > To: chuck-users(a)lists.cs.princeton.edu > Subject: [chuck-users] "Or" > Message-ID: > <AANLkTikKmHj+557HnyR5wB3Mpd1owLc+D8zhwrKrFFZT(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hallo, > > Once again, sorry for the rudimentary questions, but I can't seem to find > the correct language for a very simple function: Instead of using > Std.rand2f( ) for fluctuating volume or buf.rate, I'd like to simply have an > either/or option. Play sample at a rate of 1.0 *or *1.5, randomly. The moses > function (in pure data) was useful for this. Direction to the appropriate > helpful would also be appreciated. > > > > Thanks so much, > > Tim >

9 14

new ideas, new bugs...
by Kassen 04 Sep '10

04 Sep '10

Fellow ChucKists, I was poking around in the source for "maybe" to try to figure out how hard Joe's idea would be to implement. So far it looked really quite easy to me, except that the chuck operator would have to be overloaded to deal with chucking floats to "likely" and "unlikely". This made me wonder what kind of error this would give; 1 => maybe; It turns out that doesn't give a error at all and instead seg-faults (latest miniAudicle, linux ALSA, canonical version except for the CNoise fix). So; regardless of whether or not we go with Joe's idea this area does need a look. I vote that we do take this idea as it would be very little work for something that would be that much fun. With a default of .75% for likely and 25% for unlikely it would have all of the advantages of the various proposed strategies and on top of that we'd get a easy "crossfade" for chance-based techniques that may span several shreds. Yours, Kas.

3 2

new version of chuck
by tempjayren＠gmail.com 03 Sep '10

03 Sep '10

one of the webpages has code examples for current chuck and upcoming for chuck 2. i can't seem to locate any data on when this is to be released. i like version 1 so much i'll probably love v2.

3 4

Re: [chuck-users] chuck-users Digest, Vol 62, Issue 6
by Timothy Leonido 03 Sep '10

03 Sep '10

Ah, thanks so much-- this is very helpful. How about "impending" ? ;) 2010/9/3 <chuck-users-request(a)lists.cs.princeton.edu> > Send chuck-users mailing list submissions to > chuck-users(a)lists.cs.princeton.edu > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > or, via email, send a message with subject or body 'help' to > chuck-users-request(a)lists.cs.princeton.edu > > You can reach the person managing the list at > chuck-users-owner(a)lists.cs.princeton.edu > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chuck-users digest..." > > Today's Topics: > > 1. Re: "Or" (David M) > 2. Re: "Or" (Kassen) > 3. Re: "Or" (Rebecca Fiebrink) > 4. Re: "Or" (Kassen) > > > ---------- Forwarded message ---------- > From: David M <fimbulwintr(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Date: Fri, 3 Sep 2010 12:02:24 -0400 > Subject: Re: [chuck-users] "Or" > I believe that the much simpler way is to simply use "maybe" > > float sampleRate > > if (maybe) > 1.0 => sampleRate; > else > 1.5 => sampleRate > > 2010/9/3 Mark Cerqueira <mark.cerqueira(a)gmail.com> > >> Tim, >> You can use rand2f to do this.... >> >> float sampleRate; >> >> if (std.rand2f(0.0, 1.0) < 0.5) >> 1.0 => sampleRate; >> else >> 1.5 => sampleRate; >> >> I ran this section of code 1,000,000 times in my program doing this chunk >> of code every 1 sample and: >> >> 1. ChucK did not make my computer explode :) >> 2. The rate was set to 1.0 500,814 times and 1.5 499,186 times (pretty >> good distribution) >> >> Hope that helps! >> >> Best, >> Mark >> >> On Sep 3, 2010, at 8:21 AM, Timothy Leonido wrote: >> >> Hallo, >> >> Once again, sorry for the rudimentary questions, but I can't seem to find >> the correct language for a very simple function: Instead of using >> Std.rand2f( ) for fluctuating volume or buf.rate, I'd like to simply have an >> either/or option. Play sample at a rate of 1.0 *or *1.5, randomly. The >> moses function (in pure data) was useful for this. Direction to the >> appropriate helpful would also be appreciated. >> >> >> >> Thanks so much, >> >> Tim >> _______________________________________________ >> 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 >> >> > > > -- > David M > > > ---------- Forwarded message ---------- > From: Kassen <signal.automatique(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Date: Fri, 3 Sep 2010 18:04:34 +0200 > Subject: Re: [chuck-users] "Or" > > > 2010/9/3 Mark Cerqueira <mark.cerqueira(a)gmail.com> > >> Tim, >> You can use rand2f to do this.... >> >> float sampleRate; >> >> if (std.rand2f(0.0, 1.0) < 0.5) >> 1.0 => sampleRate; >> else >> 1.5 => sampleRate; >> >> >> > Mark is right, his code is clean, readable and correct. It could also > easily be tweaked to change the distribution.... And yet I'd still be > tempted to do this; > > 1 + (.5 * maybe) => float sampleRate; > > Generally "maybe" is my first port of call if I want to quickly and > randomly choose between two options; > > if (maybe) do_stuff(); > else do_things(); > > Take Mark's option for long term projects that you will need to get back to > or collaborate on. Pick my first option when livecoding as it's short to > type and audiences like "maybe" as a word. My second expample might be > closest to the PD object that you are missing. "maybe" resolves to "true" or > "false" ("1"(int) and "0" (int) in ChucK) with 50/50 chance at each call. > Practically speaking it's completely equivalent to; > > Std.rand2(0,1) > > However that, unlike Mark's example, can't be tuned in case you later > decide you need a 25/75 distribution instead. > > Yours, > Kas. > > > ---------- Forwarded message ---------- > From: Rebecca Fiebrink <fiebrink(a)princeton.edu> > To: chuck-users(a)lists.cs.Princeton.EDU > Date: Fri, 3 Sep 2010 12:09:53 -0400 > Subject: Re: [chuck-users] "Or" > OR, because it's chuck and therefore more fun than your average language: > > if (maybe) > 1.0 => sampleRate; > else > 1.5 => sampleRate; > > > > Message: 2 > Date: Fri, 3 Sep 2010 11:21:34 -0400 > From: Timothy Leonido <timothy.leonido(a)gmail.com> > To: chuck-users(a)lists.cs.princeton.edu > Subject: [chuck-users] "Or" > Message-ID: > <AANLkTikKmHj+557HnyR5wB3Mpd1owLc+D8zhwrKrFFZT(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hallo, > > Once again, sorry for the rudimentary questions, but I can't seem to find > the correct language for a very simple function: Instead of using > Std.rand2f( ) for fluctuating volume or buf.rate, I'd like to simply have > an > either/or option. Play sample at a rate of 1.0 *or *1.5, randomly. The > moses > function (in pure data) was useful for this. Direction to the appropriate > helpful would also be appreciated. > > > > Thanks so much, > > Tim >

1 0

"Or"
by Timothy Leonido 03 Sep '10

03 Sep '10

Hallo, Once again, sorry for the rudimentary questions, but I can't seem to find the correct language for a very simple function: Instead of using Std.rand2f( ) for fluctuating volume or buf.rate, I'd like to simply have an either/or option. Play sample at a rate of 1.0 *or *1.5, randomly. The moses function (in pure data) was useful for this. Direction to the appropriate helpful would also be appreciated. Thanks so much, Tim

4 3

In/Out Fest 2010!
by Chris Gilroy 01 Sep '10

01 Sep '10

We are curious, just like you. Because of this, we decided to bring those that inspire, move, and challenge us together to write, make, perform, and teach. Musicians and artists huddled together to learn and share the secrets of computers. How to make them do the things we dream, how to control them to do those things, and hopefully stumble across some happy accidents along the way. So join us for a time of sharing, learning, and experimenting in creating computer programs and designing control interfaces for audio and video performances. Let us rejoice in all things open source! Check out this years line up including performances by: Protofuse (maker of the Protodeck) Rosa Menkman Peter Kirn Makingthenoise Ostracon Philip White and more! and workshops on Building Your Own Controller using M4L Textiles and Electronics Creating a Digital Synth with CMOS Lecture by Brian Crabtree of monome and more! get all the details here: http://inoutfest.org/

1 0

miniAudicle bug: initial C comments
by Hans Aberg 26 Aug '10

26 Aug '10

It seems miniAUdicle 0.2.0 has a bug: files cannot have an initial C comment /* ... */. Perhaps to prevent people putting in useful comments. :-)

3 5

Question re: installing ChucK on Mac
by Edward Herbst 25 Aug '10

25 Aug '10

Hi, The installation instructions I downloaded say to reconfigure the terminal of a Mac but the Apple people I consulted advised me not to do that. They say reconfiguring the terminal is outside the warrantee and they see it as potentially destroying the computer! Is there another way to install ChucK without altering the terminal? Thanks for advice, Ed

11 27

Maybe * 0.7
by Tambet 24 Aug '10

24 Aug '10

http://wiki.cs.princeton.edu/index.php/ChucK/Features/Release - the most prioritized feat for next release is extending maybe. As I just thought of it today and my thoughts are better than there - I think that a simple overload for multiplication operator would be just enough. Like this: if (maybe * 0.2) { // Runs with probability of 20% } Or, more coherent, but less nice: if (maybe(0.2)) { // Runs with probability of 20% } Then, when doing switches, how to handle those? It would be nice to have something like: switch { case maybe * 0.3: case maybe * 0.5: case maybe * 0.6: case true: } In case it would automatically fix all maybes - so that actual probabilities would add up to 100% and, thus, first one is fixed to about 0.2 and second one to slightly less than 0.5 ..this would allow really nice play with probabilities (and, of course, optimizations internally). Tambet

2 1