My UFX+ Thunderbolt connection does not work reliably with Loopback 2 app by Rogue Amoeba.

What happens is that the Loopback 2 "forgets" the UFX+ after a few days.  I have to remove it (from all the setups which use it !) and add it back, and rewire everything in the Loopback 2 window by hand.  Major pain.  This happens once or twice per week.  Once I do the manual "re-add" of the UFX+ everything works fine until I disconnect the Mac from the UFX+.  I'm running a 2015 MacBook Pro running Mojave.

This is the kinder version of the bug -- I originally had the UFX+ connected to the Mac via a Thunderbolt hub.  In this case, Loopback "forgot" the UFX+ every time I disconnected/reconnected the Mac from the hub.

RME support simply claims "this must be a software bug in the Loopback 2 app". 

Rogue Amoeba guys say they've heard about this issue with RME Thunderbolt before.  They also had me collect log dumps for them to verify.  After studying the logs they claim that the way the UFX+ does it's "Thunderbolt enumeration" is not following best practices.  In other words, there's no unique identifier set when the UFX+ registers itself as a Thunderbolt client.  Since it's the Thunderbolt unique identifier which Loopback uses to keep track of different hardware units, it can't tell for sure whether the UFX+ is the same unit (or a different one) than was connected previously.  I don't have a problem with Loopback 2 with any of my other interfaces.

Loopback 2 is the best loopback software available for Mac -- and I use it every day.  So this is a big deal -- for me at least.

I think that RME only has one Thunderbolt product so maybe Thunderbolt support is a low priority for you ... but any plans to improve the Thunderbolt drivers for Mac any time soon ?