Disappointment with "Console".

[CVKBT]

This is honestly not what I expected from UAD.

The UAD Software "Console", with which we are controlling the ins and outs of our interface, is randomly not starting from time to time.
When Console is in infinite-loading-mode, it always takes a forced quit and a reboot of my Mac to get Console to work. This just really sucks when you're amidst a session with an artist and you can't even control whether they're getting the headphone mix or not - until you reboot your whole system.

On top of that, "Device code -129" shows up frequently; when it shows up, I can't click any of the buttons (Send or Dismiss). Can't close or hide the window. The only way to hide the device code message is by dragging it to a different desktop.. or restarting the Mac.

Cmon guys, I'm expecting the software to make this interface usable to work properly.. and yes, I've completely wiped all UAD Software from my Mac and installed it again. Big disappointment after the initial thunderbolt-cable-not-being-delivered-disappointment.

 

[JamesNorth]

I've not seen any of these errors or had this experience in several years of use of Console on Mac systems ... have you tried different cables etc?

Have you chatted with support?

Honestly not many companies provide TB cables included for free with devices like this.

 

[JohnR1]

Forum link from a while back. Could be a different issue or you already read this one.
Device Code 129

 

[CVKBT]

I've not seen any of these errors or had this experience in several years of use of Console on Mac systems ... have you tried different cables etc?

I didn't try different cables, but I'm leaning more towards thinking that it's a software related issue, as the Apollo is working flawlessly. Only the software is not starting.

Have you chatted with support?

I haven't, but probably should. Thanks for pointing out!

Forum link from a while back. Could be a different issue or you already read this one.

Yes I tried that one, but unfortunately doesn't seem to be related with Console not starting.

 

[UniversalAudio]

I didn't try different cables, but I'm leaning more towards thinking that it's a software related issue, as the Apollo is working flawlessly. Only the software is not starting.


I haven't, but probably should. Thanks for pointing out!


Yes I tried that one, but unfortunately doesn't seem to be related with Console not starting.

Def get with Support. None of this is normal or being widely reported.

 

[JamesNorth]

I didn't try different cables, but I'm leaning more towards thinking that it's a software related issue, as the Apollo is working flawlessly. Only the software is not starting.

You mentioned getting 'Device code -129' frequently which is why I thought it wasn't.

 

[CVKBT]

Update after communicating with UAD support:

My Apollo was connected via a CalDigit TS3 Docking Station. This configuration is not supported by UAD.
Support suggested to connect the Apollo directly to the Mac and see if the issue persists.

For now, everything seems to work fine.
Thanks @ everyone for helping out!

Cheers.

.. and please excuse the initial saltiness..