I have a Steinberg UR44C running the latest version of the USB drivers 3.1.7 on Mac OS Ventura (Intel) 15" 2017. I have the interface powered by the mains adaptor, connected via USB directly to one of the USB ports on the Mac.
My issue is, everytime I reboot my Macbook, the sounds panel no longer shows the interface. If I disconnect the USB cable from the thunderbolt port on my MacBook and reconnect it, the interface is still not recognised. However, if I power cycle the audio interface itself, the audio devices appear in the sounds panel.
Having checked the forum I cannot see a reference to this, is this a known problem or do I need to do something. There is nothing in the security panel requesting approval for the Yamaha driver. It appears that the power cycling when the machine is loaded initiates a different process to boot time.
Hi Alan, I’m not sure if this helps, but I use my UR44C mostly with a M1 Mac (where I don’t see this problem) and sometimes with a Windows PC, where I occasionally have the same symptoms as you. The only clue I’ve noticed is that maybe the psu to the UR or the usb between the UR and the laptop gets a brief interrupt sometimes, and the PC doesn’t cope as well as the Mac.. I have nothing conclusive as to why it sometimes happens to me though and the above is still just a hypothesis..
Thanks for sharing that, AlanP. I’m seeing the same issue with my UR44C on Intel Mac (Ventural, doesn’t show up after reboot unless I power cycle the interface. USB connection seems stable otherwise. Wondering if it’s something with how the driver loads at startup. Would be good to know if anyone found a workaround.
Hi Alan, thanks for taking the time to respond. My UR44C is powered directly from the mains adaptor. I know there are instances where a loss or drop in power can cause the loss of connection but. I really don’t think that is what is happening here. I do think that this is some kind of ‘timing’ issue with the driver at startup. When the UR44C is power-cycled, the Mac detects activity on the USB bus and initiates a full scan of all devices, which is why the device shows. There is clearly no issue with cabling or the UR44C as it works perfectly once the connection is established. I am surprised that there are not more users experiencing an issue to be honest. Let’s hope other users can add to this and Steinberg ‘chip in’ at some point.
Hi Jonathan, thanks for sharing your experience. I do not know if Steinberg moderate this forum or even comment on issues for that matter, if not perhaps there is a way to raise an official support ticket. I am happy to work with them on the issue as I have a scenario that ‘always happens’ making investigation and debugging somewhat easier with an issue that can be easily recreated. It certainly sounds like our experience is identical.
Hi Alan, although Steinberg do pop in on threads here from time to time, it does sound like you have a highly repeatable issue worthy of a support ticket? It may take several weeks for you to bubble up the support Q though…