Page 2 of 2
Re: 0/16/16 not recognized in Max/MSP on High Sierra
Posted: Wed Dec 27, 2017 1:28 pm
by jlyjn
Happy Holidays!
Any word on the reproducibility of the issue?
Cheers
Re: 0/16/16 not recognized in Max/MSP on High Sierra
Posted: Mon Jan 01, 2018 2:09 pm
by MiraLuk
Hi,
I found that Phidgets was not marked as "identified developer" on my Macbook. By accident, when installing another app, I found those check-boxes in "Security & privacy" preferences. Since I checked the check-box for Phidgets, it is working!
Hope, it will help others.
Miroslav
Re: 0/16/16 not recognized in Max/MSP on High Sierra
Posted: Wed Jan 03, 2018 1:25 pm
by mparadis
It looks like in the newer versions of MacOS, you need to give explicit permission to drivers after installing in order for them to function. You can read more about it
here.
Re: 0/16/16 not recognized in Max/MSP on High Sierra
Posted: Wed Jan 03, 2018 5:47 pm
by jlyjn
thanks for the heads up!
i booted into recovery mode and ran:
spctl kext-consent enable /System/Library/Extensions/Phidget.kext
and rebooted.
in System Preferences>Security&Privacy>General
i approved the Phidgets program and rebooted.
the Phidget Control Panel is still operational
and i'm able to control the phidget with python
but am still having no luck with the max objects.
Re: 0/16/16 not recognized in Max/MSP on High Sierra
Posted: Thu Jan 04, 2018 4:27 pm
by jlyjn
the objects started working!
thanks for the help!
Re: 0/16/16 not recognized in Max/MSP on High Sierra
Posted: Wed Jan 17, 2018 4:55 pm
by jlyjn
...and the objects are no longer working.
this is now happening under high sierra and el capitain
both with phidgets 21 & 22 installed.
i tried deleting and replacing the interfacekit objects but no luck.
any suggestions?
cheers
Re: 0/16/16 not recognized in Max/MSP on High Sierra
Posted: Thu Jan 18, 2018 8:47 am
by mparadis
What happened in between the objects working and the objects ceasing to work? What kind of error are you getting?
Re: 0/16/16 not recognized in Max/MSP on High Sierra
Posted: Thu Jan 25, 2018 11:53 am
by jlyjn
no error messages- the behavior is the same as before
the only thing that changed is that i rebooted the machine