Quoting David Powers :

How much code/difficulty was involved in creating the [chuck~] object?

The only tricky part was the loading into max/msp of a bundled/shared lib that I compiled from the chuck sources (I need to update it to the latest version of chuck soon!). Apple did a good thing in their bundle idea, I just needed to change a few compilation flags. I also added a few additional functions (and renamed "main()" to "chuck-main()" or something like that) to allow me to find the entry points I need to call the chuck engines from max/msp.

Max/msp is WAY out of my price range, but I'd love to have something like that in PD. I don't know if I could convince someone on the PD list to port it though...

Supposedly there are some people working on this -- Marcus Bittencourt at William and Mary had expressed a lot of interest. Not sure what stage those projects are right now, though. brad http://music.columbia.edu/~brad

I did a port of [rtcmix~] to windows, and RTcmix was originally developed under unix (linux now). Apple does provide some very useful development tools, and I have to make decisions about how much time to spend in porting to platforms I don't use. This is why I put all my source code on-line, in case others want to laugh their way through my pathetic coding skills and make it fly for others. I probably will attempt a windows port of [chuck~] for max/msp sometime in the not-to-distant future, but that's mainly responding to the needs of our students (many of whom are windows users). I look forward to a day when compiling for other platforms simply involves changing a few makefile/project switches. Someday... brad http://music.columbia.edu/~brad Quoting David Powers :

Well, I guess it's a big difference also, that PD doesn't just run on a Mac. So if your code is Mac-specific, that's could be a huge pain. But I hope that the port is really happening as you suggest.

I get a little frustrated when people write Mac-only stuff, as I don't see ever affording a mac in the near future. I realize many have access to them or just consider them the natural platform for artistic/musical software. But it's not very accessible for people with low incomes I think.

~David

...

Quoting David Powers :

...

How much code/difficulty was involved in creating the [chuck~] object?

The only tricky part was the loading into max/msp of a bundled/shared lib that I compiled from the chuck sources (I need to update it to the latest version of chuck soon!). Apple did a good thing in their bundle idea, I just needed to change a few compilation flags. I also added a few additional functions (and renamed "main()" to "chuck-main()" or something like that) to allow me to find the entry points I need to call the chuck engines from max/msp.

...

Max/msp is WAY out of my price range, but I'd love to have something like that in PD. I don't know if I could convince someone on

On 2/26/07, garton@columbia.edu wrote: the

...

...

PD list to port it though...

Supposedly there are some people working on this -- Marcus Bittencourt at William and Mary had expressed a lot of interest. Not sure what stage those projects are right now, though.

brad http://music.columbia.edu/~brad _______________________________________________ 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

On Tue, 27 Feb 2007, Scott Wheeler wrote:

garton@columbia.edu wrote:

...

I also added a few additional functions (and renamed "main()" to "chuck-main()" or something like that) [...]

I also did the same in a project that I'm currently hacking on. This might be something that would make sense in the authors might consider for a future version: installing ChucK as a shared library with the executable as a very thin wrapper around the lib. That would make things easier on those of us that are messing around with integrating ChucK into other environments and might make sense for miniAudicle as well.

Yes yes yes yes yes yes. In my case, I had to comment out the main vm->run() loop in favor of spawning a new thread of vm_cb. And getting rid of the "exit" calls. What is the best way to incorporate our lib-friendly changes into the main chuck sources? Graham