stubbornly i refused to reboot my machine, but after a bit of wandering i ran "top" only to discover that pd had just as stubbornly failed to quit (even though it wasn't appearing on my desktop, application switcher, or dock). so i killed it, restarted pd, and viola -- pdp_ieee1394 is working again!
not sure why this happened in the first place, but if anybody else gets stuck like this, run "top" and see if pd is still running in the background. _ j
justin c. rounds wrote:
i found this on an old thread -- is this still the case? or is there another workaround besides rebooting?
BEGIN QUOTE
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.
END QUOTE
/
[/(o)][:+:][/(o)] http://justincrounds.org/ __________________________