by CopperPhil » 11 Apr 2017, 18:31
That's weird... in this case, the CopperLan Manager is just a control software creating connections, you don't use the CopperLan Manager snapshot feature, exact? you rely on the AL88 current configuration storage since you're working without computer then.
The only cause I see is that you reached some AL88 connection amount limit... its memory is limited, you can't create hundreds of connections like you do on a computer having virtually unlimited resources.
The fact that some AL88 is not responding when you restart the CopperLan Manager may suggest that it is hanging, maybe due to connection overload. But it's just a idea, I never seen this before. And then the CopperLan Manager crash could be caused to an AL88 in a weird state on the network... This situation is unusual and unpredictable...
A solution is to avoid creating full virtual MIDI cables between the AL88. Just connect what you need, on a channel basis. We rarely have to use the 16 channels, and so it should dramatically reduce amount of connections. Then, let's see if you still have the problem.