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

controlling individual chuck patches
by Timothy Leonido 08 Apr '11

08 Apr '11

hello, could anyone offer advice on controlling individual chuck patches with an external device? currently my mode of operation is to add several shreds and control their parameters with maudi sliders (buf.rate, reverb, delay, gain), but i'd prefer to use an external controller. i have an 8 channel alesis mixer with usb-- could this help to answer my question? please let me know if you have any controllers in mind, and also which section of the manual is best to read for making these connections. thank you! tim

5 4

Wekinator
by Rebecca Fiebrink 08 Apr '11

08 Apr '11

>> >> ? ?http://wekinator.cs.princeton.edu/ > > Every time Ge drops by this mailing list, it feels like a drive-by. > > This is awesome! Why haven't we heard about it before? A lot of us > are doing similar things (Monome, iPhone/iPad, Android, > OpenKinect/OpenNI, game controllers <--> OSC <--> ChucK, Processing, > mlrv, PD) and probably could have been helpful in its development. Thanks for the shout-out, Ge, and for the interest, Michael. In short, you haven't heard about Wekinator because I was nose-deep in dissertation work until quite recently. The Wekinator is software I built during my recent PhD at Princeton, and it's meant to enable composers and musicians to more easily use machine learning to create interactive systems. (Please see the website for more info: http://wekinator.cs.princeton.edu/) The software is currently in a stable state, and it's usable by anyone who wants to control ChucK, Processing, Unity, Ableton, or pretty much anything else that can be controlled by a stream of OSC messages. These audio/video/etc. systems can be controlled by gesture (Kinect, Arduino, USB game controllers, webcam, ...), audio (e.g. using ChucK audio feature extractors, Max/MSP analyzer~, etc.), or anything else that can extract information about human actions in real-time and pass it to Wekinator via OSC. The software will continue to evolve. There are some architectural changes which must happen soon, but if anyone is looking to help with development, there are a few areas where I see room for collaboration: - UI (to keep this cross-platform, my plan is to stay in Java, using JavaFX + processing; that said, the UI needs an overhaul) - Documentation (READMEs, FAQ, and in-app help) - Examples (e.g., putting together a nice repository of code examples of ChucK, Max/MSP, Ableton, Processing, etc. being driven by Wekinator) - Determining what is necessary for tighter integration into Max/MSP (e.g. using Jamoma framework), with working examples for our Max-loving friends Additionally, I'm very interested in hearing suggestions, bug reports, and feature requests from people who are actively using Wekinator. From the beginning, the software has been driven by the ideas of people actually using it to make music, and it's become a much better project as a result. Lastly, if this project interests you at all, please consider joining the Wekinator mailing list at http://groups.google.com/group/wekinator-users?pli=1. That's the best forum to share your ideas, bugs, questions, etc. Best, Rebecca

3 3

Re: [chuck-users] Chaos functions in ChucK.
by Krzysztof Trzewiczek 05 Apr '11

05 Apr '11

Hi Anthony, I joined the list just now, but if you are still interested in Perlin Noise, I've got one to share. It's a direct implementation of this: http://freespace.virgin.net/hugo.elias/models/m_perlin.htm encapsulated in a small class. It's written in ChucK (but I've got a C version as well) and ready to use. I would be interested in your chaos related work a lot. Could you write how are the things? Best from sunny Poland, trzewiczek

2 2

Hello and the state of ChucK question
by s p 04 Apr '11

04 Apr '11

Hi ! I am quite new to chuck, and quite addicted as well ... After having tried many several other languages such as Pure Data and Super Collider, ... which are somehow nice, but the syntax just feels wrong (talking about Super Collider especially). I come from a strong development background (I am web developer during the day), and Even though I now know that Chuck rocks, I have to say that I was a little like Krzysztof at first ... very disturbed by the website, by the fact that there is no public repository, no raodmap, no issue tracker, a little repelled by the documentation, etc ... At first chucks seems like a dying project, then it just feels like something closed. I think it is really a pity now that I know there is an active community, many people willing to contribute (but who just cannot). I actually sent a mail to Ge once, to ask him what he thought about re-doing the website, and trying to gather the community a little bit but he didn't answer me (no offense taken). My offer is still valid, I am ready to start, gathering some ideas, then code, etc ... I even have a server that could host the thing, ... But I really don't understand how Chuck development works and what the development teams is aiming at, since they seem to keep things private !!! But of course a simple community website doesn't need the approval nor collaboration of the core team, ... so if some people are interested that would be good to know and start a brainstorming about what we want !!! Cheers !!! Sébastien

1 0

Re: [chuck-users] Hello and the state of ChucK question
by Harald Gutsche 04 Apr '11

04 Apr '11

Hi chuckers, I'm also new to chuck and this list. I'm a hobbyist musician and software engineer. I like chuck and it's concepts very much. >From the docs and examples I thought it could simplify all my near future sound programming needs, as it has all the building blocks (buffers, sound file handling, midi, osc, network) and very nice concepts (chuck operator, realtime), allowing me to express what I need in a few lines. I then tried to use it for my new project, which means I tried to create a kind of stereo looper with recording and beat detection etc. So I learned to use SndBuf, LiSa etc. and all the concepts in chuck. I then read from internet sources, that saving stereo files is not implemented. So I tried to save two single files (not nice but better than nothing). I further experienced that a SndBuf cannot be used to record sound. And on the other hand I couldn't create more than one (working) LiSa objects at the time (is this right?). So it seems I cannot record and save stereo sounds to files? So as being a software developer myself, I tried to look into chuck's source code and explored if I could solve some of these things. (Note that I am experienced in other fields but totally new to sound programming) The basic materials for my plans are all part of chuck, e.g. it seems STK should contain all things I need. I then also managed to change SndBuf (in a quick and dirty way) to be used for recording. But I didn't manage to save this as a stereo sound file. My main problem was that I don't really understand how multichannel and buffers are supposed to work. I see it is in the design at many places, but it seems to be unfinished. It looks that there are very different implementations of UGens and when looking at those tick functions I got a little bit confused. Running out of free time, I had to abandon the implementation of the project in chuck and am trying my way in pure C++ now. > ChucK development is indeed alive and well! > Actually a new release is nearing completion Ge, from your comment I get some hope again... Will the new release have changes in multichannel behaviour? Will it be possible to save multichannel files? When I looked last (somewhere in March), the repository had it's last checkins at the end of 2010, so I thought development had been stopped. I think I found the repo in a forum post...but cannot post the address here, because I'm at work now. I assume there must be another repo to work with? Or don't you use a central repo? It is also very unclear to me, how chuck development is coordinated. An integrated system like sourceforge would make this more easy, as all the development is (virtually) bundled in one place. How should external developers contribute to chuck? Thanks for great software, Harald

3 3

Re: [chuck-users] chuck-users Digest, Vol 69, Issue 1 NetIn [BUG]
by Kassen 03 Apr '11

03 Apr '11

2011/4/2 Joel Matthys <jwmatthys(a)yahoo.com> > I get an error -- undefined type 'netin' in declaration. Same with NetIn, > netout, NetOut. > > Crap. That's a plain bug then. I taged the subject of this mail for developer convenience and will try to find a moment to put it on the wiki page. Thanks for finding this. Kas.

1 0

the itch...
by Robert Poor 03 Apr '11

03 Apr '11

I've got an itch to test some synthesis[*] and control[**] algorithms I've got in mind[***]. What's the real-time audio streaming library on top of which ChucK is built, and where can I find its current repository? Related, what are the most current libraries to write an array of binary data to a sound file for playback? - Rob [*] Cross-coupled resonators, where each resonator is computationally super cheap (and stable). [**] Lazy-evaluated event streams, ala Abelson/Sussman http://mitpress.mit.edu/sicp/ [***] As if I actually have spare time for such stuff!

2 3

Re: [chuck-users] chuck-users Digest, Vol 69, Issue 1
by Joel Matthys 02 Apr '11

02 Apr '11

I get an error -- undefined type 'netin' in declaration. Same with NetIn, netout, NetOut. I'm on Ubuntu 10.04. Haven't tried it on Mac/Win yet. Joel > > > > Are netin and netout defunct? They are in the manual for 1.2.1.3 but > > they don't seem to work. > > > > > > netin net => dac; > > > > > > > > > > > > Strange. And you did set up your port end set a matching netout > > elsewhere on your network? Did you make sure you didn't pick a port > > that's blocked by any firewalls you may be running on either > > computer or by your router/switch? Are you receiving any errors? > > > > Yours, > > Kas.

1 0

netin & netout
by Joel Matthys 02 Apr '11

02 Apr '11

Are netin and netout defunct? They are in the manual for 1.2.1.3 but they don't seem to work. netin net => dac; --Joel

2 1