Hi Andrew, I'm glad you're coming to the show! I'm really excited about it. I'm looking forward to meeting you at the show. I would love to do a ChucK meet-up type thing. I know Zach Layton over there at Issue Project Room. It would be really cool to play with their sound system. They use the same kind of speaker systems that PlorK uses, but overhead and they are set up as a 15 channel system with a control interface in Max/MSP, if I'm not mistaken. I would love to do a granular synthesis thing there. But I'd be even more excited about setting up some kind of ongoing New York based ChucK meet-up / jam session. If Issue would be into hosting this, I think that we could really get things cooking here on the east coast. CVS access (correct me if I'm wrong, dev people) is obtained like this (on unix-like machines): $ export CVS_RSH=ssh $ cvs -d :ext:anon-chuck@cvs.cs.princeton.edu:/cvs checkout chuck_dev You'll get a folder called chuck_dev and inside that is a folder called v2 and that is where the code is. Cheers, Mike On Sat, Aug 29, 2009 at 4:20 PM, Andrew C. Smith wrote:

A statement and two questions:

1. The Stone is awesome.  I mean, it's blazing hot and there's no beer, but it's one of the coolest venues for the purpose of hearing rad music.  And it's curated, so there's some sense of artistic direction that is semi-unique.  John Zorn runs it.  See you there, Mike.

2. How do you get this so-called CVS?  Currently, I don't really perform with ChucK anyway, so stability is not so much an issue.  The text input/output thing seems fun, though.

3. Is anyone else going to be there?  Can we do some kind of NYC ChucK meet-up?  I'm grant writing/volunteering at ISSUE Project Room in Brooklyn, and we've got this excellent 15-channel floating speaker system (pretty sure Ge knows some Princeton people who have played there) and that would be a cool setting for a ChucK livecoding jam.

Thanks everyone.

Andrew

On Sat, Aug 29, 2009 at 3:48 PM, mike clemow wrote:

...

Hello,

If any of you are in or will be in the New York City area this coming Tuesday, I'm playing an hour-long set at a place called The Stone that will be all about Granular Synthesis / Resynthesis in a performance setting.  If you'll be in the area, it will be a cool show to see--everything is written in ChucK.  I'm planning on doing a quasi-participatory didactic thing with the audience to teach them about granular synthesis as I demonstrate the instruments I've built, so it's a little non-traditional as far as concert flow.

Even if you won't be in the area, you might want to take a look through my (spaghetti) code.  As Kassen can tell you, my attempts at doing granular synthesis in ChucK border on obsession and have spent a long time trying to squeeze out as much performance while keeping it as easy to program as possible.  For this show, I've built instruments that take their spectral profiles from small audio files that I've run through the Spear program for analysis (http://www.klingbeil.com/spear/).  Spear does "Sinusoidal Partial Editing Analysis and Resynthesis" and does a really good job at FFT analysis with transient sharpening and all kinds of other goodies. Spear outputs its information as a text file and I'm using the file IO routines that are currently only in the bleeding-edge CVS version of ChucK to parse these files into reasonably useful datasets.  Then I'm using standard HID stuff and a modified gamepad for interaction.  It's far from perfect, but it's a playable prototype.  I'll have this stuff organized and posted on my website and github by the show date (hopefully).  I'd really love to get some feedback on the code for the future.  Plus, if anyone is interested in getting a head start parsing Spear files with ChucK, this might be helpful.

There's a possibility that I'll document the show, so there might also be video at some point.

-Mike

"Cloud Seeding" Performing Granular Synthesis

Tuesday, Sept. 1st - 8pm @ The Stone - www.thestonenyc.com $10

-- http://michaelclemow.com http://semiotech.org _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- http://michaelclemow.com http://semiotech.org

Kas,

Friendly hint; Prepare for a bit of disorientation after you played a bit and resume talking, in my experience it's a good idea to think of a first sentence to say after you stop playing right before you start.

This is really good advice, thanks. I hope I can pull it off. I mean, it's hard enough trying to get things to work properly, but then it's kind of a strange thing to play for people when they have no idea what you're doing (or whether or not you're just there checking your email while your music plays ;-). I think that this approach is more approachable when so much of what is happening is "under the hood."

... Of what I've seen that code-base is one of the most interesting structures build in ChucK so far (my own code for long-term projects is very, very boring on a code level, I fear) so if I can vouch for anything it must be that those in the NYC area would have a great chance of seeing something very interesting at your performance.

I can only hope that's true, Kas! Thanks for the kind words. The code-base has changed dramatically since you've seen it. I think that the original way of doing what I was doing sacrificed so much performance in order to gain the programmatic control I needed, that it lent itself much easier to a non-realtime process in the end. What I'm using now isn't quite as open-ended, but it much better suited for doing performance in realtime. I got a lot of mileage out of using CurveTables as envelopes. Dimitris and I were on about that not too long ago.

BTW, I hope you'll be writing on this list about those Spear files later as well. Word on the (rather imaginary) street has it that people are pushing for a official release to include the file IO. So far I only saw the design on the Wiki and if I'd have to go by that alone I see no chance for even parsing files in ChucK at all. File parsing should be exciting; if we can parse Spears files we should be able to parse (and remix) .ck files, then save and run them. For all it's pervesity (and quite likely because of it) I find that idea very hard to resist indeed.

I will definitely be putting that together soon. You have every right to be totally underwhelmed by the file IO functions in CVS (at least, the version I'm using anyway)--they are very primitive. I really wish that ChucK handled strings better, but you can get away with using a lot of Std.atof() and Std.atoi() functions, although I do wish that they could fail with NaN rather than default to 0.0 if you feed them something like "asdf12.97asdf." What we have to look forward to are some file IO objects with various read functions - readFloat(), readInt(), and readline() - a simple tokenizer that splits on white space, and a way to write files too. I don't know if I would try to parse .ck files with them... but it can't hurt to try! It would be fun thing to mess around with. For some of my projects, I've been using OSC as a communication tool between ChucK programs and other running things. Now I'm really excited about the prospect of using fifo pipe in Unix to communicate lots of information between ChucK and something else--a simple numbers-only protocol between Python and ChucK over a fifo pipe would give a ChucK program access to Python's string-parsing abilities... Anyway, the possibilities are endless and endlessly interesting. I would love to see this functionality in the next release. (I would love to see the next release!) -Mike 2009/8/29 Kassen :

Mike;

...

I'm planning on doing a quasi-participatory didactic thing with the audience to teach them about granular synthesis as I demonstrate the instruments I've built, so it's a little non-traditional as far as concert flow.

The times when I saw Michel Waisvisz play he performed like that, gradually shifting the focus from a talk to a concert. If done well it can solve a lot of the problems with non-traditional performance methods. I tried it a few times as well and while it's hard to come anywhere near Michel's level (I consider him to have been one of the great minds and performers in the history of electronic music) it's a underapreciated form.

Friendly hint; Prepare for a bit of disorientation after you played a bit and resume talking, in my experience it's a good idea to think of a first sentence to say after you stop playing right before you start.

...

Even if you won't be in the area, you might want to take a look through my (spaghetti) code.  As Kassen can tell you, my attempts at doing granular synthesis in ChucK border on obsession and have spent a long time trying to squeeze out as much performance while keeping it as easy to program as possible.

I like obsessions (well, healthy obsessions). As I experienced that code the real obsession there isn't actually with the grains themselves but with your perspective on- and your control over them, which is of course a far more stimulating mental illness. Of what I've seen that code-base is one of the most interesting structures build in ChucK so far (my own code for long-term projects is very, very boring on a code level, I fear) so if I can vouch for anything it must be that those in the NYC area would have a great chance of seeing something very interesting at your performance.

...

There's a possibility that I'll document the show, so there might also be video at some point.

I hope you'll find the time and attention to do that; I know how hard it can be to have to mind both your own performance and record at the same time. I have of late been very bad at that.

BTW, I hope you'll be writing on this list about those Spear files later as well. Word on the (rather imaginary) street has it that people are pushing for a official release to include the file IO. So far I only saw the design on the Wiki and if I'd have to go by that alone I see no chance for even parsing files in ChucK at all. File parsing should be exciting; if we can parse Spears files we should be able to parse (and remix) .ck files, then save and run them. For all it's pervesity (and quite likely because of it) I find that idea very hard to resist indeed.

Yours, Kas.

_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

-- http://michaelclemow.com http://semiotech.org