Yes, system audio was spotty, and only worked at low sample rates. Daisy chaining was also spotty and while hot plug seemed to work in terms of connecting the interface to the comp, audio wouldn’t work properly. On the fly sample rate changing worked but resulted in massive audio distortion. The only sample rate that did work was 44.1khz, I think because thats sort of the default rate that most things would use anyway. Occasionally channel mapping was screwy and generally unusable. The IO tree before the update had the UAD driver on a completely different section than the TB controller, and the TB controller was not recognized in System Info. It was like the computer could see the device and the driver knew what to do, but they weren’t speaking the same language in terms of syntax, ie bussing.
With the firmware update, all of these aforementioned issues seem to have been solved. Of note, turning on the device on the end of the chain, waiting for it to initialize, and so on down to booting the computer seems to be the way to go, although hot plugging does also seem to be functional once everything has been booted properly once (see note at bottom). The UAD hardware reset was necessary, having the TB cables unplugged while doing it. I did not have to do the whole “unplug all power, disconnect all cables, let it sit for ten minutes” thing described elsewhere, which frankly i think is a load of hooey,lol. Just make sure the TB cables are unplugged when resetting and turn the devices on from last to first, and then the comp PSU (because the TB controller is powered without the comp being booted). I can’t think of anything else, but if anyone has any questions with regard to getting a UAD device working I’d be happy to help!
Note: HotPlugging seems to advance the ch count in Console by 2 every time, ie 1-2 becomes 3-4 and so on with each hotplug reinstatement of the audio session.
I've reconnected the cable and have uploaded the .ioreg file again.
