[chuck-users] Wrapping ChucK
wittlist at googlemail.com
Fri Oct 16 20:44:39 EDT 2009
Never thought of that approach guess you could just write an
executable script and give it a nice image in the finder.
As for the Max issue I agree the ChucK object is great fun though I
think the cost and licensing issues associated with Max would make me
look towards processing or some other OSC aware language first, even
though it may make the end product more complex to setup and use.
On Sat, Oct 17, 2009 at 1:15 AM, Andrew C. Smith <acsmith at willamette.edu> wrote:
> That's kind of the case, actually. Aside from GUI functionality not
> being available in the console, you could absolutely just create a
> script that runs "chuck crazysounds.ck" and as long as they were in
> the same directory the whole thing would work perfectly (enough). For
> the mini, I believe you can add arguments to it or something like
> that--either way, it's not that hard to just hit start on the VM and
> then open a file and chuck it.
> If you want more GUI features (and are using a Mac) then Brad's chuck~
> object for Max works pretty well. It's a nice alternative to MSP,
> because MSP just doesn't do it for me.
> On Fri, Oct 16, 2009 at 5:56 PM, Scott Hewitt <wittlist at googlemail.com> wrote:
>> I have playing with ChucK quite alot recently though I teach Max/MSP currently.
>> Im finding that in many situations I choose to use Max due to the
>> application building functionality it offers. Means you can build an
>> app and then just give it to people to use. In the OSX world the apps
>> tend to just run as well no installs.
>> Having that kind of functionality could be really with useful for
>> ChucK, the ability to integrate the code and the VM into a single
>> executable file that a user can just run would be great.
>> I guess this sort of functionality would maybe require more GUI
>> objects directly from ChucK rather than integration with other
>> languages for the GUI.
>> On Fri, Oct 16, 2009 at 4:28 PM, Andrew C. Smith <acsmith at willamette.edu> wrote:
>>> Thanks all, it's good to hear people are building things. I have
>>> looked into Processing, but just don't really have the urge to learn
>>> it--would rather just work with Cocoa windows to allow for
>>> nearly-infinite extensibility. I already got a Cocoa interface working
>>> with OSC, using the Objective C library VVOSC (highly recommended for
>>> anyone doing Cocoa programming with OSC). Like Brad, though, I'm
>>> looking to get more control over the DSP environment with a direct
>>> Brad, I didn't think about your Max object, which seems like a logical
>>> model now that you mention it. In fact, I could probably do all of
>>> what I'm doing in Max, but where's the challenge in that?
>>> One thing, though, is that you're making ChucK output its sound to the
>>> Max/MSP interface, while I really just want it to output it to its
>>> default place (that is, CoreAudio or whatever else I make available
>>> from a mini-like menu option). So, I don't really mind using OSC to
>>> communicate over port 8888 (the ChucK-controller port), but I
>>> basically just want to make the user only start up one application
>>> instead of multiple apps, as is the case with the OSCSurface
>>> So, Brad, do you first "make maxmsp" in chuck-maxmsp.220.127.116.11/src, then
>>> use the resulting chuckdylib.so to run the engine in Max? This is
>>> tentative, because I don't really know what I'm talking about, but can
>>> NSCreateObjectFileImageFromFile with NSLinkModule link to a
>>> chuckdylib.so-type library in any environment (not just Max)? And,
>>> finally, thank you for commenting the source so heavily, including
>>> things like "BIG HACK" to point out where ChucK might trip someone up.
>>> I'll post a working product if I ever get one.
>>> On Fri, Oct 16, 2009 at 8:55 AM, Brad Garton <garton at columbia.edu> wrote:
>>>> I prefer a 'tighter' connection between the DSP engine (in this case chuck)
>>>> and the enclosing app-environment. Although I need to update it to reflect
>>>> the latest chuck-ness (which shouldn't be too hard), I set chuck up for the
>>>> maxp/msp chuck~ object as a loadable lib that can be built right into
>>>> the application. This gives access to all chuck functionality within
>>>> the app.
>>>> On Oct 16, 2009, at 12:07 AM, Andrew C. Smith wrote:
>>>>> Has anyone tried to wrap ChucK into a standalone program? I'm thinking
>>>>> (at the very least) it could just be made to run simultaneously and
>>>>> communication could be made over OSC, but it would be cool to have the
>>>>> whole thing communicate through 8888, the port that the console
>>>>> communicates on. Basically, the mini is an effective wrapper, right?
>>>>> I'm just wondering if anyone has created anything simpler, like even
>>>>> just a program that outputs ChucK sounds when you click buttons or
>>>>> something. It would be really cool for games (or toys, not really
>>>>> games) that let users play around with sounds using an integrated
>>>>> graphical interface. Anyone try it?
>>>>> chuck-users mailing list
>>>>> chuck-users at lists.cs.princeton.edu
>>>> chuck-users mailing list
>>>> chuck-users at lists.cs.princeton.edu
>>> chuck-users mailing list
>>> chuck-users at lists.cs.princeton.edu
>> 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