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
On 2/26/07, garton@columbia.edu
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 _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users