[maxmsp] Re: Bug in connecting objects in Max
Peter Castine
pcastine at gmx.net
Tue Apr 1 06:29:11 MDT 2008
- Previous message: [maxmsp] Noise Cancellation
- Next message: [maxmsp] Re: [jitter] Framesync issue ( frame vs. frame_true)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Are you sure your search path is kosher? Reading your symptoms, I'm thinking, well, when Max refuses to make a connection it's normally because the patch-time type-checking says the recipient won't understand the message the sender is transmitting. I always assumed that was one of the reasons for specifying message types in the API for creating inlets and outlets. So much is not news, but it may be a sign that Max is loading the wrong external file for one of your objects. I had this happen with scale object years ago, from the wild west days when there was no standard scale object but about 15 different 3PO implementations. One reason I gave scampi and scampf oddball names was to avoid external name ambiguity. I realize you can't save a patch with the connection that crashes Max, but can you localize to particular externals? And maybe Spotlight your search path to be sure there aren't any duplicates. Hope this helps. -- ---- Peter Castine Litter Power: <http://www.bek.no/~pcastine/Litter/> iCE Tools: <http://www.dspaudio.com/software/ice/ice_overview.php>
- Previous message: [maxmsp] Noise Cancellation
- Next message: [maxmsp] Re: [jitter] Framesync issue ( frame vs. frame_true)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
