Direkt zum Inhalt

iLok2 and MacBook Pro issue

Posted

MacBook Pro (Early 2013) w/USB 3.0 ports

OS X 10.9.5 Mavericks (not Moutain Lion)

Synfire Pro 1.7.11b2

 

This is not a Synfire problem. It's an iLok problem. I searched the forum but found no results related to this.

I am activated and authorized, however this morning SFP and iLok Manager could not see the iLok. I was able to reauthorize and all is well for now.

 

I have been reading that the iLok2 has an issue with USB 3.0 ports. Does anyone know if this is still an issue?

 

Greg

Michiana, USA


Di., 24.03.2015 - 11:03 Permalink

Hi Greg,

If I remember correctly, this was an issue with Apple's implementation of their USB drivers. If this is still a problem with 10.9.5, Apple would more likely fix it in 10.10 rather than publishing a new update 10.9.6. I am just guessing, though.

I'll ask PACE support for the current status.

Di., 24.03.2015 - 12:57 Permalink

Thanks André.

I am always reluctant to upgrade to the lastest OS X right away due to possible driver issues. Lessons learned from Microsoft Windows. I ordered a little 2-port USB 2.0 (pigtail) hub just in case.

 

Greg

Michiana, USA

Di., 24.03.2015 - 21:11 Permalink

Yes, take your time with upgrading. After 10.6, the experience got worst with every upgrade. IMO Apple is pushing upgrades a bit too fast. I'm still at 10.9.5, since every upgrade takes me about a week to get the tool chain working again.

Fr., 27.03.2015 - 10:44 Permalink

There it goes again. Time to reactivate.

 

IMO At $50 US, the iLok case should be made of aluminium, not plastic. ;)

 

Edit:
I had read elsewhere that a USB 2.0 adapter may solve the MacBook Pro USB problem. This seems to work. The iLok wasn't seen by the system. I simply plugged it into the adapter and did nothing else. Four Synfire loads later and it works fine.

No one here seems to have the problem, but maybe it will help someone in the future.

Here is the link to the Amazon page for the adapter: (http://www.amazon.com/dp/B005HKIDF2/ref=cm_sw_r_tw_dp_QU8evb19E3092)

Attachments

Fr., 27.03.2015 - 11:33 Permalink

Thanks for sharing. 

Hopefully Apple will resolve this driver issue soon.