WARNING: UAD Console v1.2.7 Compatibility Issues

There are instructions on the UA Forum and the UA website on how to revert back to the previous version of Console. You might want to contact UA customer support to report your issue and see if they are aware of anyone else experiencing the same issue and to provide you with a solution. Best of luck getting this resolved.
Thanks for the info: yes, I've already been to their "Software Archive" to downgrade. Had all kinds of issues with UA Connect installing this version, reverted back to older one, cleaned system, talked with tech support etc. Finally got this version to work just to stay current.

Will keep an eye out and see if I can find a predictable way to make it happen. Not a big deal, just messy.

Cheers
 
I was one of the people who reported this issue to Universal Audio and Fractal Audio.
Following instructions from UA,
I reverted my console to the previous version (1.2.6), and Axe Edit 3 was able to be used without any problems.

To do this,

I first uninstalled it using UA connect, then installed 1.2.6 while still in that state.

Since 1.2.7 is likely an update for the new "VOLT" version,
plugins and other software will continue to work without any problems with 1.2.6.

LUNA 2.0 also works without any problems in this state.
I changed the audio interface when using LUNA from APOLLO to Axe FX III, and it's still working without any problems.
 

Any body know if the new 1.2.8 version fixed this issue? Bullet item 3 alludes to a MIDI fix effecting third party apps.

From the UAD site below:

Version 1.2.8 — November 18, 2025​

Improved​

  • Volt 876 stability improvements and bug fixes

Version 1.2.7 Supplemental — October 24, 2025​

Fixed​

  • (Apollo UAD Console) Resolved an issue that prevented Tap Tempo from functioning
  • (Apollo UAD Console) Resolved an issue that prevented Tap Tempo and Plug-in Scenes recall via MIDI
  • (Windows) Resolved an issue that caused MIDI issues with third-party applications
 
Sorry, I noticed after I sent this that the fix was mentioned under the last broken version 1.2.7. Question still remains though. Did 1.2.8 fix it?
 
Sorry, I noticed after I sent this that the fix was mentioned under the last broken version 1.2.7. Question still remains though. Did 1.2.8 fix it?
I haven't had any MIDI issues with UA 1.2.8 and the FM3 or Tonex One, though Ableton LIVE and Pro Tools have both had issues losing connections with Apollo USB HW during sessions..
 
If you are using a UAD audio interface it has been reported that Console v1.2.7 interferes with the operation of Axe-Edit. It is recommended to use an earlier version until UAD issues a fix.
FWIW I have an M1 Mac running Sequoia 15x and I use Universal Audio's Luna DAW and an Apollo Twin X audio interface. I have used it and my FM3 concurrently before with no issues. Last night without the FM3 plugged in to the Mac everything worked fine. This morning I plugged my FM3 directly into the Mac and now the Mac will not recognize my Apollo Twin X as an audio interface. It recognizes the FM3 as an audio interface, but that is not what I want.

I have started a ticket with UA and we'll see what they say. As of now I'm completely dead in the water. Total PITA.
 
Ive been shell shocked after going through hell with this a few months ago. Was a complete mess. Am I good to update to the latest UA 1.28 and 1.29 Console now on Windows 11?
 
Ive been shell shocked after going through hell with this a few months ago. Was a complete mess. Am I good to update to the latest UA 1.28 and 1.29 Console now on Windows 11?
One would hope they resolved this by now, I am assuming you're good to go - If you end up having a problem you can easily roll back to the previous console version, which is what I did back when this was going on. I ended up changing to the SSL 2 MKII interface however so I couldn't tell you for sure if the latest Console works with Axe Edit.
 
Back
Top Bottom