Thanks for testing. Please note my former statement - we can not reproduce this effect on any of our systems, so currently have no way of fixing it for you.

I'm able to replicate this issue as well with the release candidate.

Specs:
Firmware: v110, Driver: v1.02
UFX+ is connected to iMac Pro (2017) via Thunderbolt using Apple's Thunderbolt 3 to Thunderbolt 2 adapter
macOS Ventura 13.1

Steps to reproduce:
1) After a fresh boot, UFX+ works perfectly and is detected
2) Turn off UFX+
3) Turn back on UFX+
4) UFX+ is not detected

UFX+ is detected again by:
1) reboot while UFX+ is powered on, UFX+ works perfectly and is detected.

or

1) reboot while UFX+ is powered off
2) wait until reboot is complete, then turn on UFX+
3) UFX+ works perfectly and is detected

Could this issue be related to Apple's Thunderbolt adapter? I recall a note that this adapter was not preferred by RME, however I could be remembering incorrectly. In any case, I don't own any other adapter so I cannot test to confirm.

Hope this helps!

Thanks for the great product, the UFX+ is a wonderful interface.

(edited to clarify another scenario)

No. With three machines available to me the re-detection after turning off and on the UFX+ works on Apple Silicon (both a Macbook M1 Air and and Macbook Pro with M1 Max, both on Ventura 13.1), but fails with the Intel iMac Pro (also on Ventura).
It could be a TB security issue (Intel+T2) or TB is implemented differently on Apple Silicon?

This is another Intel iMac (Monterey/Ventura) with the same "on/off/on" driver problem.

1.03 is in the works, adding stuff we learnt from the HDSPe driver. Should come in the next days.

Thanks for the update!

Unfortunately, redetection of the UFX+ after switching off and on still doesn't work on the Intel (iMac Pro, Ventura 13.2 RC). It works on the M1 System.

Some further testing:
- as before all is working well on the M1 System (Ventura 13.2 RC)
- Crackling noise while clicking on the BT Mouse is gone!
- I got the UFX+ *re*detected *twice* after connecting it to a subsequently different TB port (Imac Pro has  4 ports / 2 bus TB3 system) until i ran out of ports. After that, the UFX+ is not redetected on any port until rebooting.

P.S.
- I remember another *re*detection problem with a Samsung X5 *TB* Drive after installing a *USB* S. M.A.R.T driver from DriveDX years ago. Works without problems ever since though. Maybe some strange things are happening on the TB3 bus on all Intel Macs?
- All four TB ports on the iMac Pro are working without problems with two TB Samsung X5 drives, an iLok USB-C and a cascade of UA Apollo/Satellite, in every permutation, redetection and sleep mode included ;-)
- I tested the *re*detection with the UFX+ as the only TB device and also in combination with two TB drives and an iLok. Same results in both cases.
- The adapter for the UFX+ is the "official" Apple TB3-TB2 white one, i have four of them...

Tested again with Ventura 13.2?

Wanted to share these steps that just worked to resolve the re-detection issue. In my case it seems to have been caused by an old version of the PCIe driver being loaded underneath the new DriverKit driver.

1- Uninstall DriverKit driver by dragging RME Thunderbolt Settings.app to trash.

2- Uninstall remnants of old driver manually per instructions in the UFX+ user manual by removing:

/Applications/RME Thunderbolt Settings
/Library/Extensions/RMEPCleAudio.kext
/Users/username/Library/Preferences/de.rme-audio.RMEThunderboltSettings.plist
/Library/LaunchAgents/de.rme-audio.RMEPCIeAgent.plist

Reboot.

3- However even after these steps, Under System Report > Extensions, still saw RMEPCIe driver 1.22 running. Why?!
System Report tells me the kext is located at /Library/StagedExtensions/Library/Extensions/RMEPCIeAudio.kext

“Staged Extensions” which I believe is a macos cache for SIP approved extensions, stores a copy of the kext that is still being loaded!

Clear the staged extensions cache with this command:
sudo kextcache --clear-staging

Reboot, and no longer seeing the RME PCIe 1.22 driver in System Report > Extensions. Yay!

4- Reinstall DriverKit UFX+ thunderbolt driver v1.03. However, not seeing an “allow” button in Security preferences this time. I reboot anyways. On reboot, still not seeing the driver appear, so I wonder if it got trapped in limbo.

5- Reboot into recovery mode  (on M1, shut down machine and hold down power button while booting).
Open terminal, and run:
kmutil trigger-panic-medic --volume-root /Volumes/Macintosh\ HD/

Reboot.

6- On boot, Security preferences asks me to re-approve all system extensions and reboot. I oblige.

7- FINALLY, RME Thunderbolt Settings is launching on login and subsequent reboots.

This was on MacOS Monterey, 12.6.3, M1 Pro.

I've never had an issue with (re-)detection on (two different) M1 Machines... It's an Intel Problem, since the TB controllers are different and also TB security (via separate T2 chip on the Intel side?) seem to be handled differently with Apple Silicon.

Also, the *usb* driverkit beta drivers 4.06 do work as expected on *both* systems (M1 and Intel), i.e. correctly (re-)dectecting the UFX+ after standby/wakeup and/or switching off/on!

Since the problem was reproduced by marcin_c, the problem can be regarded as a verified problem (bug)!

I've just deleted the driverkit drivers (TB and USB) on the iMac Pro and installed the 1.03 TB beta only, no difference, no (re-)detection (sigh...)

By the way, Steps 5-7 (and suggestions like disabling SIP) are completely out of question on a regularly used machine...

iMac Pro (Intel Xeon/T2), Macbook Air M1, Ventura 13.2

@Matthias

Any news regarding DK driver for UFX+ TB?

Currently using TB. But can switch to USB. Any words to the wiser?

Best,
Pål S.

Driver 1.04 is now available on the website.

what is your MacOS ?

Did you try Dorico on the computer without any interface connected ? Just over the internal loudspeakers of the MacBook ?

I figured out what the difference between DK driver is.  I restored the security level back to standard one.  Then, the RME Thunderbolt Setup started working showing version as 1.04 properly.  Dorico also started working after many trial and error.  RME needs to mention at the download page that one needs to download one of either, not both drivers.  There is no detailed explanations regarding which driver to download. I had to search on this forum about Driverkit driver and educate myself from other people's writing.

TB drivers have been updated to v 1.05 as DriverKit and 1.24 as Kernel Extension. The DriverKit driver reliably removes the Kernel Extension, so it is very easy to swap between these drivers and check which works better for you. That said CoreAudio works better in audio multiclient mode with the Kernel Extension...

Driver download links in this thread:
https://forum.rme-audio.de/viewtopic.php?id=38691