|
Post by gravesnumber9 on Dec 4, 2021 14:36:41 GMT -6
Wait even better. I figured out how to trigger it again and how to fix it even faster.
It can be triggered by turning the Apollo on before connecting ADAT. (Not the only thing that does it but that can trigger it). I can see that my custom I/O settings then go into italics when I put the ADAT back on. Everything looks right but Console sees the entire I/O scheme in Italics. All I have to do is double click the custom I/O to reload it and problem is solved.
Hope this helps someone someday! My weeks of pain will have been all worth it!
|
|
|
Post by reddirt on Dec 4, 2021 15:54:02 GMT -6
Good on you - what a mongrel situation to have swallowed your attention for such a long time. That may well be good info for many Cheers, Ross
|
|
|
Post by javamad on Dec 5, 2021 2:38:30 GMT -6
Wait even better. I figured out how to trigger it again and how to fix it even faster. It can be triggered by turning the Apollo on before connecting ADAT. (Not the only thing that does it but that can trigger it). I can see that my custom I/O settings then go into italics when I put the ADAT back on. Everything looks right but Console sees the entire I/O scheme in Italics. All I have to do is double click the custom I/O to reload it and problem is solved. Hope this helps someone someday! My weeks of pain will have been all worth it! I have had this happen a few times. No idea how it gets triggered but I have learned to first look at I/O and load up my custom routing. I was reading through this thread thinking I would post my experience but I see you already found it. The only theory I have is that as both my Apollos are powered off the same rackmount power conditioner they get turned on at exactly the same time and might enter into some sort of race condition for master-slave assignment which leaves the I/O configuration unloaded.
|
|
|
Post by schmalzy on Dec 5, 2021 3:31:36 GMT -6
SUPER glad you figured it out!
It definitely feels like the DAW -> software -> connection -> Interface is a fragile area with the Apollo and UAD system and digging around in UAD Console is likely to yield results. It makes sense, there's a lot of talking back-and-forth and something being slightly unhappy for a second can send a wrench into the works.
I've also had a long-term problem with my Softube Console1 plugins and certain UAD plugins. Loading certain UAD plugin into my system when I have Console1 plugins loaded breaks the Console1 system a little. After that point the Console1 controller doesn't work and the Console1 plugins stop behaving and displaying properly.
I'm not getting rid of my Apollo any time soon - I tend to stick with gear a long time - but it definitely makes me consider my options. I'm looking at going to 24 channels of ins/outs soon and I'm expecting a few thousand of my dollars to be wrapped up in it. It would definitely make me more likely to stay with UA if they could get their shit figured out. I have interfaces that "haven't been supported" in years that work great on my system and a current-ish (was current when I bought it, anyway) UA product running with officially supported software that is constantly teetering on a knife-edge.
The least UA could do for your weeks of involuntary, unpaid beta testing and self-tech-support is to offer you discounts on plugins or hardware. Someone with one of their products is going to benefit from this and it's going to retain customers for them.
|
|
|
Post by gravesnumber9 on Dec 5, 2021 13:19:51 GMT -6
Yeah, there are times when I look at the x8 and x4 and things... how many channels of MOTU I/O could I get for this much? And keep my satellite for the UAD plugs that use to mix with.
Not nearly there yet because I appreciate a lot of the features that UAD brings to the table and I actually do use the Unison features. But yeah, the whole point of a DSP powered system is that it is supposed to be rock solid. It's supposed to "just work" and not be something I have to think about barely ever.
|
|