-
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
Crashes in Mac M3 Pro Sonoma when connected to camera #12727
Comments
05/03 14:53:54,186 ERROR [0x1709cb000] (handle-libusb.h:127) failed to claim usb interface: 0, error: RS2_USB_STATUS_ACCESS |
Hi @philchao Intel has not provided official support for use of RealSense on Mac computers since 2017's MacOS High Sierra. Whilst the RealSense SDK has been able to work on Macs in subsequent years despite not being officially supported, problems have occurred more frequently since MacOS Monterey onwards and the introduction of the Apple Silicon Mac models (M1-M3). The community of RealSense Mac users is therefore usually the provider of solutions for issues by sharing knowledge with each other. The discussion at #12307 is likely to be relevant to your particular issue with Failed to set power state errors, especially the final comment in that discussion at #12307 (comment) |
@MartyG-RealSense Thank you for your prompt feedback. I am just wondering if is there some other way to change the output-input of the RealSense camera? For instance, I tried to connect this Apple USB-C Digital AV Multiport Adapter (https://www.apple.com/nz/shop/product/MUF82ZA/A/usb-c-digital-av-multiport-adapter) to the camera and provided charge for the camera through the adapter's USB-C charge input and output from the adapter's HDMI to the computer but it does not seem to register the device. Is it possible to output the RealSense camera to HDMI whilst providing it with power through a USB-C? Thanks |
I have never seen a case where RealSense has been made to work with HDMI, unfortunately. There have been a couple of past cases where a camera was able to be detected when attached to an adaptor cable on a Mac, but in most cases it is not successful. |
Hi @philchao Bearing in mind the advice in the comment above, do you require further assistance with this case please? Thanks! |
Thanks @MartyG-RealSense. Unfortunately, I still was not able to get RealSense Viewer to work with my M3 Mac on Sonoma. Not sure if @cansik has been able to with his pyrealsense2 |
@MartyG-RealSense @philchao Not really, it's a matter of trial and error. The second attempt to start the relasense-viewer (installed with brew) worked for me. The camera was already connected. However, only the depth camera produced an image, not the RGB camera. In my opinion, RealSense is no longer usable in production for MacOS users (which is a great pity). Today I would recommend the cameras from Luxonis, as they have an API that is supported on all major platforms. |
Hi @philchao Do you require further assistance with this case, please? Thanks! |
Hi @MartyG-RealSense, yes, I would like the Intel Real Sense Viewer to work with Mac Sonoma, but it does not seem possible at this stage. |
One Mac user took the approach of using the camera with the Asahi Linux OS on their Apple Silicon machine instead of MacOS and wrote an installation guide. https://github.com/HasanTheSyrian/librealsense-hasan/blob/master/doc/installation_asahi.md |
Hi @philchao Is the Asahi Linux solution suggested in the comment above of use to you or do you still require a MacOS Sonoma solution, please? |
Hi, I'm facing the same issue. My mac M2 (MacOS sonoma) is able to detect the camera but when I open the realsense-viewer its crashing and it's not able to open. Is there any solution I could get for this issue. |
Can you explain how you are able to start realsense viewer ? |
I have a very similar issue:
It's been reported here as well: https://support.intelrealsense.com/hc/en-us/community/posts/4548413451539-Activating-the-realsense-D435-Depth-Camera-in-MacOs Any solution? |
I’ve found recently that mine seems to work with Parallels now on a windows virtual environment
…On 23 Aug 2024 at 04:17 +1200, Michel Gokan Khan ***@***.***>, wrote:
I have a very similar issue:
$ sudo realsense-viewer
GLFW Driver Error: Cocoa: Regular windows do not have icons on macOS
22/08 18:16:01,479 INFO [0x2028e0f40] (context.cpp:116) ... 1-2-2
22/08 18:16:01,479 INFO [0x2028e0f40] (context.cpp:129) Found 1 RealSense devices (0xff requested & 0xff from device-mask in settings)
[1] 42953 segmentation fault sudo realsense-viewer
It's been reported here as well: https://support.intelrealsense.com/hc/en-us/community/posts/4548413451539-Activating-the-realsense-D435-Depth-Camera-in-MacOs
Any solution?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
yes, that's exactly what I did but it's not very efficient :-( |
Hi everyone, The current latest 2.56.1 version of the librealsense SDK contains a fix for SDK compilation on MacOS Apple Silicon 'M' processors and also an update for MacOS 14 (Sonoma). These changes are confirmed in 2.56.1's release notes. 2.56.1 is currently an 'interim beta' release of the SDK which can only be installed by source code compilation. https://github.com/IntelRealSense/librealsense/releases/tag/v2.56.1 |
@MartyG-RealSense My MacOS crash report is saying that the crash is occurring when libusb_get_device_list is called, same as with 2.55.1 I built with flags
My terminal reports the following at the time of crash
When typing
Hope that helps! MacOS 14.6.1 |
Hi @alifeinbinary Thanks very much for your feedback about LibUSB. Further information regarding the Mac support updates in 2.56.1, including the LibUSB issue, can be found at #9916 (comment) I will pass your information to my Intel RealSense colleagues. Thanks again! |
Please provide a description of the problem
I am able to start the Intel RealSense Viewer v2.54.2 without the camera connected. But once I connect the camera the application automatically shuts down:
Process: realsense-viewer [6158]
Path: /opt/homebrew/*/realsense-viewer
Identifier: realsense-viewer
Version: ???
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2024-03-05 14:34:00.6287 +1300
OS Version: macOS 14.2.1 (23C71)
Report Version: 12
Anonymous UUID: 9E225096-2F73-84E7-D358-A6214E7D6214
Time Awake Since Boot: 11000 seconds
System Integrity Protection: enabled
Crashed Thread: 1
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000028
Exception Codes: 0x0000000000000001, 0x0000000000000028
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [6158]
VM Region Info: 0x28 is not in any region. Bytes before following region: 68719476696
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
commpage (reserved) 1000000000-7000000000 [384.0G] ---/--- SM=NUL ...(unallocated)
Thread 0:: Dispatch queue: com.apple.main-thread
The text was updated successfully, but these errors were encountered: