-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install for MacOS Monterey #10676
Comments
Hi @mingyangpeng A RealSense user created and shared a detailed RealSense installation guide for Monterey and M1 at https://lightbuzz.com/realsense-macos/ The brew install librealsense installation method lists support for Monterey and M1. Could you test please whether the 'Failed to set power state' error disappears if you unplug the micro-sized end of the USB cable from the base of the L515 camera, turn the connector around the other way and re-insert it into the base of the camera (USB Type-C cables are two way insertion at the micro-sized end). |
Hi, @MartyG-RealSense ,thank you for your advices, I try to insert USB Type-C in both directions, and the error information is as follows:
plug with face up :
plug with face down :
I also tried this way “https://lightbuzz.com/realsense-macos/”. I follow the steps in the article, I'm not see the RealSense target under the Products folder,I didn't find librealsense2.2.50.0.dylib , I'm not familiar with Xcode, I gave up. Thank you again for your advice,Is there any other simple installation method? |
For the M1 Macs, brew or the Lightbuzz guide are currently the best methods of performing an installation of the SDK. It sounds as though the brew install is functional, although you are receiving a power state error. Which RealSense program is producing the error, please? |
Sorry to reply you so late, These errors are produced by |
Other RealSense Mac users have experienced this issue with launching realsense-viewer with sudo, an example of which is #9916 (comment) Since that comment was published, the previously mentioned Lightbuzz installation guide for Monterey / M1 and support for them in 'brew install librealsense' have been released. However, you are still experiencing the problem. The best place to ask for advice on this subject is likely to be the main Monterey / M1 discussion thread at #9916 where fellow Mac M1 users are very willing to offer advice to other users who still have problems. |
Hi,@MartyG-RealSense, I've seen #9916 before, but it doesn't work. So far from last year, there is no definite solution to the USB connection problem. I hope your official team can adapt and reconstruct it on MacOS Monterey. |
Hi @mingyangpeng MacOS development work for the RealSense SDK ended after MacOS High Sierra and although the SDK has continued to be compatible with subsequent MacOS versions such as Catalina and Big Sur (and now Monterey), there are no plans for further Mac development by the Intel RealSense development team unfortunately. |
This is really bad news,, which will hinder the development of the RealSense,If there is any new development in the later stage, please let me know. Thank you! |
Thanks very much for your understanding. Mac members of the RealSense community can continue to submit updates that they have created via a Pull Request so that they can be reviewed by the RealSense development team for merging into the RealSense SDK. https://github.com/IntelRealSense/librealsense/pulls |
Hi @mingyangpeng Do you require further assistance with this case, please? Thanks! |
Hi,@MartyG-RealSense I hope to get further help. Let's keep this, Thank you! |
Okay, it is no problem to keep this open for other members of the RealSense Mac community to comment on. Thanks! |
@MartyG-RealSense, thank you for your help! |
Case closed due to no further comments after 4 months. |
Issue Description
Is there a simple installation method for MacOS monterey M1 pro? I tried “ brew install librealsense”, but error :failed to set power state,I read the previous installation method and tried it, but the errors were the same, I need help......
The text was updated successfully, but these errors were encountered: