[chuck-users] WvIn on osx and linux
gelfmuse at gmail.com
Wed May 6 20:25:52 EDT 2009
Arduino => Python => ChucK is my mainstay, actually. ;-) works like a charm.
PySerial is a great lib, as you likely already know
(http://pyserial.wiki.sourceforge.net/pySerial). Also, I have had
more success with PyLiblo than with Simple OSC because it's much
faster, although you can easily flood ChucK with OSC with either
implementation. If you decide to go the PyLiblo route, however, and
you're using a Mac, you should be aware that there is a slightly weird
issue compiling it due to the place that the library hides on Mac OS.
See this post: http://michaelclemow.com/?p=556 if you're getting
errors. Simple OSC is much easier to install:
That being said, Serial support in ChucK would so, so, so badass...
imagine a million hardware hackers making insanely cool interfaces to
their digital instruments. Look out, NIME!
On Wed, May 6, 2009 at 6:52 PM, jo <jj.metzger at googlemail.com> wrote:
> Mike, thanks, I'll look into it!
>> don't think there is anything keeping you from using -say-
>> a 32 bit wave file.
> you're right, of course, I should do that and I could also interpolate, but
> so far I had no problems, updating the parameters every, say, 20ms, although
> it's very likely not to be the most efficient solution...
>> Python would mean involving a third system (matlab,
>> Python and ChucK).
> it would complicate things (matlab is also just out of convenience, could
> use python as well there), but I'd love to hook up an arduino to the whole
> thing (eventually I want to build an interactive sound installation,
> although the whole idea is only in its infancy) and arduino => python =>
> chuck seems easiest to me as long as there is no serial support in chuck.
> All the best,
> Am 06.05.2009 um 20:28 schrieb Kassen:
>>> So basically I would like to feed in floats (results from physics
>>> simulations, e.g. position of a particle at some point) which are stored
>>> an array in chuck and then apply them to some parameter of a sound (e.g.
>>> pitch, gain). Using a wav file turned out to work well for me (writing
>>> header and then the float data as 16bit integers in matlab and getting
>>> floats from -1. to 1. in chuck).
>> Yes, that makes perfect sense. I think I would considder increasing
>> the bit-depth of the wave file in this case, depending on how much
>> resolution you need. For gain 16 bit would likely do but when you are
>> modulating pitch I think it might make sense to increase the
>> 16 bit is a popular format and all soundcards will be able to play it
>> but here we aren't all that interested in actually playing the file as
>> audio so I don't think there is anything keeping you from using -say-
>> a 32 bit wave file.
>>> Actually, thinking about it now it would possibly be even easier to use
>>> and send the data using python, but I'll also look at using SndBuf...
>> I'm not sure; Python would mean involving a third system (matlab,
>> Python and ChucK). I think either the file-IO from CVS (I haven't
>> actually looked at that myself though) or your wave file method
>> combined with SndBuf would be faster and more efficient. Wave files do
>> seem like a very natural way to store tables to me, especially for
>> continuous data like particle locations. Interpolation might make
>> sense for that type of data as well. You may also want to poke around
>> multi-channel wav files to see whether those would be useful for you.
>> chuck-users mailing list
>> chuck-users at lists.cs.princeton.edu
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
More information about the chuck-users