CopperLan

Hi guys

Is anybody experiencing problems with CL 1.4 on OSX not detecting when MIDI ports are connected or disconnected, i.e. if a USB midi controller is disconnected, CL doesn't reflect this change?

I'm on a MacBook Pro Retina 2012 with OSX 10.10.5

I also tried removing all drivers from /Library/Audio/Midi Drivers, and the result was the same.

Cheers

Lee

Hi,

We never had such plug&play related feedback before. But some people reported issues related to non-working CopperLan after upgrading to OSX10.10. We found that some MIDI software which is not compatible with OSX 10.10 can freeze the CopperLan engine. There is no warning nor clear information about that incompatibility during OSX upgrade, and it is resulting in blocking MIDI related system calls.

So please check that all the software running on your Mac, especially related to MIDI port, is compatible with Yosemite.

Hi Phil

This isn't related to any software, just copperlan. Try this:

On OSX 10.10, open copperlan manager and connect a midi device. The device shows up in audiomidi setup but not in copperlan manager..

Cheers

Lee

There is a workaround..

Manually killing the cpuserd process causes CopperLan manager to pick up the changes to the midi ports.

Cheers

Lee

Yes, cpuserd is probably frozen during a MIDI port operation. When you kill it, it restarts immediately and work normally if the condition causing the freeze is no more present.

The thing is, what is the cause of cpuserd freeze?...

Do you have this problem with any MIDI USB controller or only with some of them?

This problem is with all midi devices.

OK I succeeded to reproduce the problem. I just built a new package fixing it.

Can you please test it and tell me if the bug is fixed on your side?

https://dl.dropboxusercontent.com/u/215 ... %29%5D.dmg

Thanks

Thanks Phil, that seems to have fixed it!

Cheers

Lee