|
ChucK & The Laptop orchestra
Viewed 1686 times. 9 people liked this blog. You can rate it below if you haven't already.
-->
I really enjoyed this, It's about the development of chuck but it also shows really interesting about bit the Princeton Laptop Orchestra.
If you have the time, it's better than watching the wedding planner! | |
Comments
05/20/08
+
PM |
QUOTE |
PERMALINK |
REPORT
packetst0rm
ASIO version of ChucK is available here : link
05/20/08
+
PM |
QUOTE |
PERMALINK |
REPORT
Tripnik
hey flies,
have you done any scripting yet? If you have to do a lot of repetitive tasks it may be something to look into. You could also potentially save cpu cycles by only creating objects when you actually need them. I haven't done it myself, but it looks interesting.
I've also gotten a bit frustrated with the patching environment. I really want to get into supercollider and processing next, but I'd need to brush up on my java skills (or lack thereof) first.
05/20/08
+
PM |
QUOTE |
PERMALINK |
REPORT
jogn
Played around with it for a month or so. The fun part is, it's a lot easier to pick up than say csound. A lot more fun too. The downside is that some things are/were at the time a little flakey. For one you've got to be careful about how you instantiate objects, because garbage collection is zero. String manipulation is also an undocumented thing, which, if you create strings, and hence objects, in the main loop, you're going to run out of memory.
05/20/08
+
PM |
QUOTE |
PERMALINK |
REPORT
flies
tripnik said: "have you done any scripting yet? If you have to do a lot of repetitive tasks it may be something to look into."
i've looked into it. the syntax is utter crap. I mean, yes it works, but compared to any real programming language it's just plain crap. For repetitive tasks it's ok, so for instance if i wanted to make the same change in a family of abstractions i had built i would do scripting. But it's hardly less work to name every object i've created and write a script to connect each to its proper destination. I don't yet know how to make segmented patch cords with scripting, but i can only imagine that making them tidy would be a huge pain.
You could also potentially save cpu cycles by only creating objects when you actually need them. I haven't done it myself, but it looks interesting.
i looked into this a while back, and instantiating dsp objects always resets the audio, creating a silence and setting all the lfo's, etc back to home.
mute~ and poly~ are the way to go for processor saving.
I've also gotten a bit frustrated with the patching environment. I really want to get into supercollider and processing next, but I'd need to brush up on my java skills (or lack thereof) first.
the problem is that it takes so damn long to make patches. there's always a lot of juggling and work-arounds. for me, easily distractable and real busy with school, this gets annoying. I've griped about this particular problem before, but the lack of proper scoped sends and receives is exceedingly vexing for me.
I think what i may do is learn java and start basing all my control flow in mxj. What i want is a live tool, I already know max, i like its dsp options and I definitely like its UI options (a big advantage over chuck i guess), i have come to dislike its data structures intensely, so mxj might be what the doctor ordered.
does anybody know if it's possible to make something like matrix ctrl in chuck?
one of the things that i think max is the worst at is fft munging. Here is one case where having a proper array would really (for accessing the analysis data and storing the manipulations for memory betwen frames), really be a big help. Doing everything with ==~ and buffer~ juggling is a hassle.
05/20/08
+
PM |
QUOTE |
PERMALINK |
REPORT
craque
ditto here, chuck is interesting, but i find it unusable as a programming language
05/20/08
+
PM |
QUOTE |
PERMALINK |
REPORT
Otterfan
While you could easily create a matrix of state switches that change incrementally in ChucK (that's my understanding of what matrix control does, but I'm not a Max person), it wouldn't have any GUI. You would have to control it with MIDI, OSC, the computer keyboard, or on-the-fly programming. None of these would give you any feedback--ie, there won't be anything to tell you that button[1,3] is in state 2 other than whatever audible effects that state has.
The conventional GUI solutions for ChucK seem to be either Audicle (a visualization environment for ChucK that is pretty limited), writing an interface in some other language--usually Java--and communicating via OSC, or embedding ChucK in Max/MSP using the ~chuck object.
05/20/08
+
PM |
QUOTE |
PERMALINK |
REPORT
Otterfan
05/20/08
+
PM |
QUOTE |
PERMALINK |
REPORT
jp
craque said: "ditto here, chuck is interesting, but i find it unusable as a programming language"
why?
i think the design is pretty neat, it has some weak points but overall it's quite ok.
05/20/08
+
PM |
QUOTE |
PERMALINK |
REPORT
nagrom
I'm just starting to learn SuperCollider and after watching this I considered switching to ChucK while I still can. Google "Supercollider vs. ChucK". In the end I decided to stick with SuperCollider...mainly because ChucK seems to be developing with live-coding and rhythmic music in mind, while I'm not really interested in either of those things -- the advantages of ChucK are meaningless to me.
05/20/08
+
PM |
QUOTE |
PERMALINK |
REPORT
nagrom
I definitely like its UI options (a big advantage over chuck i guess),
I've seen some people do their interface in Max and their processing in SuperCollider and send data back and forth between the applications with OSC. And there's nothing stopping you from doing some of the logic (or even sound) in Max while you're at it.
It's too bad there isn't an sc~ object (yet).
05/21/08
+
PM |
QUOTE |
PERMALINK |
REPORT
packetst0rm
Just going through chuck's tutorial has given me a softer intro into audio programming I think once I've gone through some more of it I will move back to supercollider. I feel it's a bit like jumping in the deep end, be it a very flexable fun deepend but all the same it's scary!
05/23/08
+
PM |
QUOTE |
PERMALINK |
REPORT
fichu
haven't used chuck, but i heard it has some accurate timing stuff going on, something max/msp is lacking.. but then again why don't use supercollider? it's learning curve is said to be hard but i think that's mainly because of lack of documentation, find David Cottle's tutorial and you'll be up and running in no time. Interface wise, i've gotten great results by combining Processing (http://www.processing.org) and SC by using OSC! Ofcourse OSC isn't limited to this workflow so you can combine it with Max/MSP or whatever software that supports it.
05/23/08
+
PM |
QUOTE |
PERMALINK |
REPORT
ricemutt
yeah, im interested in playing around with chuck at some point, when I have some time for it.. code-wise, it seemed a lot more direct and natural than supercollider's stuff.
Register / login
|
^
EM411 is Copyright 2001-2008 EM411.com
All rights reserved. | Contact | RSS
|
