[java-dev] Re: MXJ getting wrong inlet

Okay, so I built a smaller version of the patch. It's a network-like patch, and my original topology had 4 input nodes, 2 layer 2 nodes, and 1 layer 3 node. Node 1 of layer 2 was reporting the wrong inlet. I built another network, with a smaller topology of just 2 input nodes and 1 layer 2 node. Same error, and same topological location; that is, first node in layer directly below top layer (or, in Max terms, "the mxj instance on the left"). Exact same problem: trace shows the message going to inlet 0, but mxj's getInlet() reports inlet 1. 

Looking for updates I noticed that 10.5 is still "officially" not supported, so I assume I'm on my own. But this should be filed as a bug anyway. Also, Max won't gracefully exit from tracing - it becomes unresponsive to menu clicks (no spinning ball), then crashes.

Mac Pro 2.8 8-core
16 GB RAM
Apogee duet
MaxMSP 4.6.3
OS X 10.5.2 with all updates

cheers,

J.