UA actually fixed some bugs?!
Apr 12, 2024 15:44:21 GMT -6
kcatthedog, viciousbliss, and 2 more like this
Post by doubledog on Apr 12, 2024 15:44:21 GMT -6
I know we often get on their case for all the weird sales events and all that... but I just installed the 11.2.0 build and it actually fixed some bugs for me. Sadly, UA may not even know that they fixed it, but whatever. I even went so far as to install the "new" UA Console after that (a glutton for punishment I guess) and it was still working (although for some reason that new console feels like Pro Tools 7 to me...)
In my particular case, I'm still running an Apollo 16 Silver (firewire) on Windows 10 and somewhere after 10.2.0, they broke firewire really bad - some people had no connectivity. I was able to connect, but then could not load Console most times, or it was unresponsive. Anyway, 11.0.1 ( I think) supposedly fixed this but I still had difficulty. I went around and around with support and finally figured out that I had to change the way that I sequenced the power up. All the UA support articles have always said power on the interface first. Well now support was telling me I might want to power on the computer first (if that works), and I figured out if I waited until it reached the login screen, then I could power on the interface, and then eventually I could open Console and everything worked. So I retrained myself to do this and for the last 3 months or so it's been stable ( if that's what you call stable...). But now with 11.2.0, I can power on the interface first again (which I prefer since I've got it on a switchable rackmount power strip). Not only that, but it almost seems like Avid and UA might have been talking because I see different messages when I switch to a session that is at a different bit/sample rate. Many times I would get blue screens doing this and I did not today (although it's too soon to really call this a win). But I had a faint glimmer of hope today.
In my particular case, I'm still running an Apollo 16 Silver (firewire) on Windows 10 and somewhere after 10.2.0, they broke firewire really bad - some people had no connectivity. I was able to connect, but then could not load Console most times, or it was unresponsive. Anyway, 11.0.1 ( I think) supposedly fixed this but I still had difficulty. I went around and around with support and finally figured out that I had to change the way that I sequenced the power up. All the UA support articles have always said power on the interface first. Well now support was telling me I might want to power on the computer first (if that works), and I figured out if I waited until it reached the login screen, then I could power on the interface, and then eventually I could open Console and everything worked. So I retrained myself to do this and for the last 3 months or so it's been stable ( if that's what you call stable...). But now with 11.2.0, I can power on the interface first again (which I prefer since I've got it on a switchable rackmount power strip). Not only that, but it almost seems like Avid and UA might have been talking because I see different messages when I switch to a session that is at a different bit/sample rate. Many times I would get blue screens doing this and I did not today (although it's too soon to really call this a win). But I had a faint glimmer of hope today.
