Adam Lindsay wrote:
Yves,
but, by the way, i received some very unfriendly mails from MAC users ( consumers ) UNHAPPY with their product as if they were writing to a company dealer,
It's true that there can be some culture shock between the Pd (do-it- yourselfers) and the Mac (click, and it just works) communities. I do hope you're not discouraged by those folks, but Pat also rightly brings up the idea of pent-up demand and excitement.
i ever you're a linux or a mac user, there's no reason to call someone a "rat" just because your software doesn't work.
Anyway, some hints to potential users, and comments to Sevy:
If you get an error message on startup about pdp_text not finding a default font, try this:
sudo cp pdp_pidip_osx/fonts/helmetr.ttf /usr/X11R6/lib/X11/fonts/TTF/
that's in the installation notes... http://ydegoyon.free.fr/INSTALL_NOTES.txt
The nifty pdp_ieee1394 object looks like it isn't re-entrant yet (i.e., you can't create a second pdp_ieee1394 object, even in another patch after one has been destroyed). This might show up with a bunch of lines like "pdp_ieee1394: SGIdle failed." or "pdp_ieee1394: grabber initialization failed". If you run into this, I think the only way to fix it is to close pd and restart. It's not pretty, but from the commented- out code, it seems like there's some trouble with the implementation.
It's most irritating when trying out all the nifty sample patches!
Can the Gem/OSX folks offer any insight into this?
should be the case for pix_video, too, no? some code of pix_video did not work also because, in pdp, everything is excuted in a thread ( i guess it's the more likely reason ).
cheers, sevy