-
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
Process Killed RealSense SDK Mac M2 #12890
Comments
Hi @MhmRhm May I first confirm that you have set the position of a mode switch in the casing of your D457 to work with a USB cable, please? By default the camera is set to work with a non-USB connection type called GMSL/FAKRA. If you have not set the mode switch to the USB position yet then instructions are provided at the link below. https://support.intelrealsense.com/hc/en-us/community/posts/14840675121043/comments/14843232242835 It looks as though you have likely set the switch to the USB position though. In regard to MacOS 14.4.1 (Sonoma), the Lightbuzz guide was designed for use with MacOS Monterey. There have been reported issues with getting RealSense cameras to work with Sonoma that are unresolved at the time of writing this as far as I am aware - please see #12727 The brew install librealsense method of installing the SDK on MacOS claims to be compatible with Apple Silicon and Sonoma. |
Dear @MartyG-RealSense thanks for your fast response. The switch is on USB. |
I note that in the log at the bottom of your Mac screen you have Failed to set power state and No device detected - is it plugged in? errors, which can occur if the camera cannot be detected or cannot be accessed. On your Mac are you using the official USB A to C cable supplied with the camera or a USB C to C cable of your own choice, please? If it is a C to C cable then problems are more likely to occur with RealSense cameras, especially on Mac. |
Dear @MartyG-RealSense there are no USB A to C cables supplied with the camera. Only one GMSL/FAKRA cable. I am using an official USB Type C to C cable supplied with my iPad mini. The same cable that I used in the UTM image and it is working there. |
Thanks very much @MhmRhm for the reminder that D457 does not come with a USB-C cable. I use a cable from another RealSense camera with mine. Yes, with the D457 model the micro-sized end of the USB cable has to be inserted into the camera base in one particular direction of the two insertion directions available in order for the camera to operate at USB 3.2 speed, otherwise it is detected as USB 2.1 when inserted in the other direction. Aside from the known reliability issues when using a C to C cable with RealSense cameras, the cable that is chosen to use with RealSense cameras if not using the official one should also be designed for data transfer and not just be a charging / tablet to computer device sync cable. |
Dear @MartyG-RealSense thanks for your patience. I managed to test with a USB4 Gen3 40Gbps cable. Same outcome. In the attache image you can see that my virtual machine is recognizing the USB 3.2 but Mac failed to run the enumeration application. |
You could next check Sonoma's privacy and security settings to see whether there is a setting that might be blocking access to the camera in MacOS. https://support.apple.com/en-gb/guide/mac-help/mchlf6d108da/mac |
This error has been previously reported with a RealSense camera on an Apple Silicon Mac at the link below. https://support.intelrealsense.com/hc/en-us/community/posts/4548413451539/comments/27039742754195 My research indicates that it is not a RealSense-only issue but also occurs on MacOS in non-RealSense software that uses GLFW graphics such as the game Minecraft. In the small number of cases where a workaround was developed, it involved creating a custom 'forked' version of GLFW with the problematic code edited out, like the case at LWJGL/lwjgl3#695 I appreciate that this is something that the majority of RealSense MacOS users may not want to do or be able to do. |
Dear @MartyG-RealSense thank you so much for that. Hopefully, soon I will try the solution. |
Hi @MhmRhm Do you have an update about your case that you can provide, please? Thanks! |
Dear @MartyG-RealSense I followed this tutorial and was unable to connect. I am continuing in Linux VM on my Mac. Thank you for following up. |
A RealSense Mac user had success with using a type of Linux called Asahi on their Apple Silicon Mac and wrote an installation guide about the procedure that they used. https://github.com/HasanTheSyrian/librealsense-hasan/blob/master/doc/installation_asahi.md |
Hi @MhmRhm Do you require further assistance with this case, please? Thanks! |
Dear @MartyG-RealSense thank you for all the help so far. |
You are very welcome. As you do not require further assistance, I will close this case. Thanks very much for the update! |
Issue Description
I have followed this instructions to build RealSense SDK for Mac.
I also copied the libusb-1.0.0.dylib next to rs-enumerate-devices in /librealsense/build/RELEASE/Release.
The rs-enumerate-devices exits without any error output while run from terminal with sudo.
When running from Xcode it crashes at
PTHREAD_CHECK (pthread_mutex_lock(mutex) );
The following image shows the situation.
The text was updated successfully, but these errors were encountered: