Pro Tools Duet by Apogee does not wake up after sleep

[Nei]

I have a newly purchased "Pro Tools Duet by Apogee"-interface. It is connected on iMac (late 2009), macOS Sierra 10.12.3. I have installed the "PT I/O Control Panel"-software which functions normally.

The interface functions normally, except when I put the computer to sleep. When I return the computer from sleep, all visual indicators of the interface remain blank. The round volume-knob still modifies the volume, and pressing the knob still selects between the channels (in1, in2, out1-2, out phones). However, there is not visual indicator of any of this taking place, so I never know which channel/parameter I am adjusting. Only the one indicator that was active before sleep mode is lit (f.ex. phones), and it remains unresponsive. Working is not possible with the device on this mode.

The only way to fix the problem is to disconnect and re-connect the usb from the computer, which is highly undesirable in terms of optimizing workflow. I need to do this procedure several times a day, all the while making sure my active speakers are off/on. I made the purchase of this interface to optimize my workflow, so this is just ridiculous. Some of my collaborators don't have the same issue, so I am hoping there is something I could do to fix it.

Apogee suggested NVRAM reset of my Mac (https://support.apple.com/en-us/HT204063). I did it, and it does not solve the issue. I was also given the following speculation: "If you boot your Mac with Duet connected (or Duet is left connected when your Mac goes to sleep) it can happen that Duet will not be detected normally on boot up and on the “wake” state . This is because your Mac will default to your core audio rather than your connected USB device so you may have sync issues. Normally unplugging and reconnecting your Duet's USB to your Mac will fix this."

Unfortunately, I am left with no solutions, and I can't continue working like this. Neither Apogee or Avid have offered any feasible ways to work around this ludicrous problem. And like I said, not all collaborators have the same issue, so I am hoping there is something I can do.