Intel realsense with M1 chips

AcidBoy · June 22, 2023, 12:23pm

HI!

I’m using a M1 Mac and I try to find a depth camera that will be able to work with TD.
I’ have tried to make the RealSense to work but it’s a pain and very complicated.

Any tips?

thanks

malcolm · June 22, 2023, 5:57pm

I don’t think it’s really well supported. On the github there is a thread about issues people are facing:

github.com/IntelRealSense/librealsense

Librealsense needs sudo on macOS Monterey and Ventura

opened 08:02PM - 17 May 23 UTC

jackjansen

MacOS

I am opening this issue because #9916 has become unwieldy and has an awful lot o…f information that is beside the point. Maintainers: feel free to close-as-duplicate if you think this is a bad idea. My hope is that there are some people out there who have an idea which MacOS change is the cause of this issue, then we should be able to come up with a fix or workaround. I presume the root cause is the continuous effort by Apple to harden MacOS against malware, that started with MacOS 10.8 with signed applications, System Integrity Protection, and all that. But I have no idea which specific feature has caused this behaviour. ### Issue Description Since MacOS Monterey any program that uses librealsense needs `sudo` rights. The error differs depending on the program, but it will often say something like "failed to set power state" or "failed to claim usb interface" or both: ``` 17/05 21:52:52,400 INFO [0x1f8359b40] (context.cpp:382) Found 1 RealSense devices (mask 0xff) 17/05 21:52:52,416 ERROR [0x16e0df000] (handle-libusb.h:125) failed to claim usb interface: 0, error: RS2_USB_STATUS_ACCESS 17/05 21:52:52,416 ERROR [0x16df3b000] (sensor.cpp:664) acquire_power failed: failed to set power state ``` ``` There are 1 connected RealSense devices. rs_error was raised when calling rs2_create_device(info_list:0x6000024b7360, index:0): failed to set power state ``` Requiring superuser rights is always inconvenient, but sometimes impossible (for example when trying to use librealsense from within `Unity`).

AcidBoy · June 29, 2023, 1:49pm

thanks a lot

looizinho · September 6, 2023, 1:52am

Hello!

I finally managed to make RealSense work on my MacBook M1. Follow the steps:

Install libusb via HomeBrew: brew install libusb.
Install librealsense via HomeBrew: brew install librealsense. It will install version 2.54.1.
Copy the librealsense2.2.54.1.dylib file to the /opt/homebrew/Cellar/librealsense/2.54.1/lib/ directory somewhere and rename it to librealsense2.2.50.0.dylib.
Move this file to /Applications/TouchDesigner.app/Contents/Frameworks, overwriting it.

Now it took me longer to find out. Starting with macOS Monterey, RealSense libraries should run with superuser privileges, so you should listen to TouchDesigner on the terminal: sudo /Applications/TouchDesigner.app/Contents/MacOS/TouchDesigner.

Sometimes it will work, sometimes it won’t. When it doesn’t work, unplug and plug the device in and try again.

I created a Shortcut to run TouchDesigner this way and it already asks for the files I want to open: Shortcuts

I am running TouchDesigner Build 2023.10130 (Apple Silicon Version), macOS Sonoma 14.0 Beta (23A5337a) on a MacBook Pro 13-inch, M1, 2020.

redbeard · October 6, 2023, 4:13am

Speaking of this… It’s more to say that the statement “The librealsense SDK v2.50.0 does not look like it will be updated for Apple Silicon, so it is not an option to add to these builds.” in the RealSense documentation is incorrect. This is understandable because I’m sure it came from the genuine belief of the developers. Regardless, that view is incorrect as @looizinho has demonstrated. The sources have been updated. Any chance of giving us some easy way of saying “use the dynamically provided librealsense” without having to muck around in the application? That way as Intel provides both an updated librealsense but also corresponding firmware we can consume their upstream work?

ben · October 6, 2023, 5:25am

Sure, we can update the docs to point here as a start.

“Sometimes it will work, sometimes it won’t.” ← this has been the case for us for years with RealSense on macOS and one of the reasons we don’t promote it in good faith. “You can get it to work” is a lot different than “it works and we support it” for professional applications.

But this is a good resource for those who want to work through it.

Can you elaborate on this? Especially what you meant by ‘without having to much around in the application’.

Any chance of giving us some easy way of saying “use the dynamically provided librealsense” without having to muck around in the application? That way as Intel provides both an updated librealsense but also corresponding firmware we can consume their upstream work?

Thanks

redbeard · October 6, 2023, 6:23am

Sorry, by “muck around in the application” I can imagine a number of options. potentially an environment variable(*1) or a configuration option(*2) with a path to search for librealsense2.dylib (especially since the mechanism above stomps all over your link tree and intimates version mismatches). At least that would still allow you to play nice with some semblance of semver built into the link structure of your (CMake?) tooling.

1: e.g. Starting the application with LIBREALSENSE_DIR=
2: e.g. Something in the configuration allowing a user to specify a version and or path.

I totally agree with your overall assessment as these devices are especially finicky. I’m just also thinking through my own “long term support” path.

MiguelF · January 19, 2024, 9:35pm

Im strugling to make any depth camera working on my mac. Im running macosventura on a macstudio m2, and still looking for a solution to use any depth camera and SDK for real time body tracking; I’ll be happy to get a simple silhuete so i can stream it via ndi to Resolume or Mad Mapper.

ben · January 20, 2024, 2:59am

The OAK-D cameras are fully compatible with macOS, might be work checking out. Requires TouchDesigner 2023.

spindlewhorles · March 19, 2024, 8:41pm

Hi, I’d like to try your fix. I’m currently on macOS Ventura, and I think because RealSense requires superprivileges to access high power USB I get the error ‘failed to set power state’ or "failed to claim usb interface no matter what I do the camera is only detected as webcam, no depth camera, so the TouchDesigner TOP also does not find it, only as videoin device can I use it in TD, which is against my purpose. Do you recommend upgrading to macOS Sonoma to try your approach? I’m on mac mini 2018 Intel though, not M1. I consider downgrading to Big Sur or Catalina cause I read that they don’t have enforced restrictions on USB access so you don’t need to use sudo (not sure if my interpretation is correct)

spindlewhorles · March 21, 2024, 11:49am

In the link provided it says
“The OAK operators are currently only supported for Windows.”

Does it mean one cannot use the OAK-D cameras in TD then?

ben · July 16, 2024, 9:07pm

@spindlewhorles Sorry for the late reply, I missed this somehow. All OAK operators are multi-platform, macOS supported!