|
Post by gravesnumber9 on Nov 27, 2021 18:00:20 GMT -6
Hey fellow UAD people. Posting this here because it's a holiday weekend and I don't feel like waiting for support and because UAD forum is way too slow.
Ever since I downloaded the new UAD update I am running into problems where my monitor out delivers no signal. Sometimes rebooting fixes it, sometimes it doesn't. But what ALWAYS fixes it is deleting my UAD files and redownloading the software. Very annoying.
And now, I'm getting the "garbled playback" problem. I'm sure delete and reinstall will work but anybody have an idea wth is going on? I feel like it's just me or else I'd be seeing this posted everywhere.
THE SYSTEM
X4, X8, and Satellite Mac mini M1 Big Sur 1.1 All firmware updated and latest UAD downloaded
|
|
kcatthedog
Temp
Super Helpful Dude
Posts: 15,219
Member is Online
|
Post by kcatthedog on Nov 27, 2021 18:08:26 GMT -6
Are you running rosetta2?
When you say garbled, like buffer problem ?
Are you running a lot of vi and see you checking your system and memory usage? What about UA dsp and memory usage ?
Have confirmed all plug ins in session are big sur compatible ?
|
|
kcatthedog
Temp
Super Helpful Dude
Posts: 15,219
Member is Online
|
Post by kcatthedog on Nov 27, 2021 18:09:54 GMT -6
Am running a similar system but no UA interface, no problems here.
|
|
|
Post by gravesnumber9 on Nov 27, 2021 18:09:59 GMT -6
This is just me trying to play from Spotify or Apple Music. Same issue from DAW as well.
So even with no plugins. And by garbled I mean it kind of sounds like it's underwater.
|
|
|
Post by gravesnumber9 on Nov 27, 2021 18:11:23 GMT -6
kcatthedog you've never had to reset your computer to get it to recognize your Apollo unit(s) or to play sound? Jealous. I had to do that with both previous laptops as well periodically.
|
|
kcatthedog
Temp
Super Helpful Dude
Posts: 15,219
Member is Online
|
Post by kcatthedog on Nov 27, 2021 18:31:47 GMT -6
Are you using a third party app to route sound through Apollo?
Once I went TB my Apollo experience:Sf, Bf and X was mostly flawless but that was on an Intel mbp I7, plus an octo card.
|
|
kcatthedog
Temp
Super Helpful Dude
Posts: 15,219
Member is Online
|
Post by kcatthedog on Nov 27, 2021 18:33:03 GMT -6
What’s your boot order? Comp or Apollo first?
|
|
|
Post by gravesnumber9 on Nov 27, 2021 18:36:08 GMT -6
What’s your boot order? Comp or Apollo first? The x4 runs into the x8 which runs into the Satellite which runs into Mini. Although this problem pre-dates that setup. I usually turn on the Apollo first but not always. Sometimes that fixes it actually, but sometimes it makes no difference. Maybe I have it backwards?
|
|
kcatthedog
Temp
Super Helpful Dude
Posts: 15,219
Member is Online
|
Post by kcatthedog on Nov 27, 2021 18:58:34 GMT -6
I’d experiment with just the x8 and see if you can run that and pass audio without problem , then add satellite , recheck, then add x4?
Try turning on Apollo first and let it stabilize 5-10 seconds, then power up computer, it should recognize Apollo just fine, , then test as above ?
|
|
kcatthedog
Temp
Super Helpful Dude
Posts: 15,219
Member is Online
|
Post by kcatthedog on Nov 27, 2021 19:03:09 GMT -6
From UA forum:)
Multi-Unit Operation Power On Sequence Thunderbolt devices may be connected and/or disconnected when the computer and/or devices are powered on (hot plugging). The order in which the Apollo units are connected and/or powered on is not critical. Apollo units are automatically detected a few moments after connection.
Page 198 of the Apollo Software Manual (Thunderbolt).
A lot of people reference having a power conditioner and turning on all UA boxes at same time .
|
|
|
Post by Johnkenn on Nov 27, 2021 19:09:10 GMT -6
I occasionally have issues with garbled sound coming from my Sonarworks system wide, like when I come out of pro tools and go to play something in a browser or iTunes. I usually just force quit SW and then open back up and it works.
|
|
|
Post by wiz on Nov 27, 2021 20:24:58 GMT -6
I occasionally have issues with garbled sound coming from my Sonarworks system wide, like when I come out of pro tools and go to play something in a browser or iTunes. I usually just force quit SW and then open back up and it works. Most likely sample rate mismatch
|
|
|
Post by Johnkenn on Nov 27, 2021 20:29:45 GMT -6
I occasionally have issues with garbled sound coming from my Sonarworks system wide, like when I come out of pro tools and go to play something in a browser or iTunes. I usually just force quit SW and then open back up and it works. Most likely sample rate mismatch Shouldn’t be. It changes with the sample rate the Apollo is set to
|
|
|
Post by gravesnumber9 on Nov 27, 2021 21:40:11 GMT -6
Most likely sample rate mismatch Shouldn’t be. It changes with the sample rate the Apollo is set to Fwiw reinstalled UAD software and everything peachy. I have my eyes on Sonarworks as the problem. Working for now.
|
|
|
Post by Johnkenn on Nov 28, 2021 8:51:21 GMT -6
Shouldn’t be. It changes with the sample rate the Apollo is set to Fwiw reinstalled UAD software and everything peachy. I have my eyes on Sonarworks as the problem. Working for now. Yeah, it’s Sonarworks
|
|
|
Post by schmalzy on Nov 29, 2021 12:57:18 GMT -6
I get stuff kind of like this every now and then.
I'll be mid-mix. I'll hit play and the playhead will move but there's no audio. Reaper is showing playback and levels on the output VU meter but the output VU on the Apollo hardware shows no signal. That told me the problem was after Reaper's mixer and before the DAC on the Apollo.
My found-it-by-chance solution after UAD support blamed Reaper and left me hung out to dry (while Reaper has had no problem with any of my other interfaces): Go to the Apollo Console and change the input delay compensation in the Console settings menu. It literally doesn't matter what you change it to or where it's set, just change it to something else. It's almost like sometimes Apollo forgets it's supposed to be working and me changing the IDC reminds it there's a job to do.
Good luck! Hopefully this helps you!
|
|
|
Post by gravesnumber9 on Nov 29, 2021 16:55:42 GMT -6
I get stuff kind of like this every now and then. I'll be mid-mix. I'll hit play and the playhead will move but there's no audio. Reaper is showing playback and levels on the output VU meter but the output VU on the Apollo hardware shows no signal. That told me the problem was after Reaper's mixer and before the DAC on the Apollo. My found-it-by-chance solution after UAD support blamed Reaper and left me hung out to dry (while Reaper has had no problem with any of my other interfaces): Go to the Apollo Console and change the input delay compensation in the Console settings menu. It literally doesn't matter what you change it to or where it's set, just change it to something else. It's almost like sometimes Apollo forgets it's supposed to be working and me changing the IDC reminds it there's a job to do. Good luck! Hopefully this helps you! This is great! No idea if it will work but at least it's a new thing to try that nobody else has suggested. And you described the experience I'm having very well.
|
|
|
Post by schmalzy on Dec 2, 2021 16:45:47 GMT -6
I get stuff kind of like this every now and then. I'll be mid-mix. I'll hit play and the playhead will move but there's no audio. Reaper is showing playback and levels on the output VU meter but the output VU on the Apollo hardware shows no signal. That told me the problem was after Reaper's mixer and before the DAC on the Apollo. My found-it-by-chance solution after UAD support blamed Reaper and left me hung out to dry (while Reaper has had no problem with any of my other interfaces): Go to the Apollo Console and change the input delay compensation in the Console settings menu. It literally doesn't matter what you change it to or where it's set, just change it to something else. It's almost like sometimes Apollo forgets it's supposed to be working and me changing the IDC reminds it there's a job to do. Good luck! Hopefully this helps you! This is great! No idea if it will work but at least it's a new thing to try that nobody else has suggested. And you described the experience I'm having very well. Any updates? Did it work for ya'?
|
|
|
Post by gravesnumber9 on Dec 2, 2021 16:47:14 GMT -6
Well it hasn't happened since then so I'm not sure. Last thing I did was re-install software and that worked (before your suggestion). But I will definitely update next time this happens which seems to about roughly weekly.
|
|
|
Post by gravesnumber9 on Dec 2, 2021 18:10:04 GMT -6
Well schmalzy, it happened again and none of the solutions worked. Not force quitting Sonarworks or the Console input delay trick. Rebooted with Apollos powered on. Rebooted with Apollos powered off. This is getting extremely frustrating. It's like one out of every four times I sit down to work on a mix I have to spend the first hour re-installing software. What is this 1999 again?
|
|
|
Post by yewtreemagic on Dec 2, 2021 18:48:35 GMT -6
I occasionally have issues with garbled sound coming from my Sonarworks system wide, like when I come out of pro tools and go to play something in a browser or iTunes. I usually just force quit SW and then open back up and it works. Most likely sample rate mismatch I've had occasional problems like this when I'm online while still running Reaper with Sonarworks ASIO, when a website randomly attempts to play back audio at a different sample rate and my audio just locks up. As far as I remember just re-loading the correct Sonarworks preset re-enables my audio.
|
|
|
Post by gravesnumber9 on Dec 2, 2021 18:52:47 GMT -6
Yet again reinstalling UAD fixed it. I exited Sonarworks, started it again. Rebooted. Everything I can think of. Uninstalled it. Rebooted again. Nope.
Nothing until I re-installed UAD software.
Is it possible that the Sonarworks software is somehow corrupting the UAD software or something? Sounds really far-fetched but I'm at a total loss at this point. This is seriously reducing my actual sanity.
|
|
|
Post by schmalzy on Dec 3, 2021 5:42:00 GMT -6
Well schmalzy , it happened again and none of the solutions worked. Not force quitting Sonarworks or the Console input delay trick. Rebooted with Apollos powered on. Rebooted with Apollos powered off. This is getting extremely frustrating. It's like one out of every four times I sit down to work on a mix I have to spend the first hour re-installing software. What is this 1999 again? Sorry, man. I wish I had a different solution for ya'. I don't know exactly how Sonarworks interacts with your audio chain. Is it a plugin inside your session or is it an intermediary program that sits between the DAW and your interface? When this glitch/garbled audio problem happens can you get any other audio working? For example, leave your DAW and your project up and go to System Preferences -> Sound -> Output and switch it to internal speakers. Does the sound play back ungarbled then? You should be getting your DAW audio just from the computer itself and not through your monitoring chain. You might need to plug headphones into the computer if it doesn't have internal speakers. Try Youtube or Apple Music. What happens then? Just like mixing, with computer systems the thing that seems like the problem isn't always where the problem actually is. If I were in your shoes, I'd start eliminating potential problems to figure out exactly where the problem is. Uninstall Sonarworks. Reduce to a single Apollo. Then try a different interface altogether. Seems like a difficult path to go down but at least you'll know what the problem is and can work towards a real solution.
|
|
|
Post by gravesnumber9 on Dec 3, 2021 9:17:32 GMT -6
Well schmalzy , it happened again and none of the solutions worked. Not force quitting Sonarworks or the Console input delay trick. Rebooted with Apollos powered on. Rebooted with Apollos powered off. This is getting extremely frustrating. It's like one out of every four times I sit down to work on a mix I have to spend the first hour re-installing software. What is this 1999 again? Sorry, man. I wish I had a different solution for ya'. I don't know exactly how Sonarworks interacts with your audio chain. Is it a plugin inside your session or is it an intermediary program that sits between the DAW and your interface? When this glitch/garbled audio problem happens can you get any other audio working? For example, leave your DAW and your project up and go to System Preferences -> Sound -> Output and switch it to internal speakers. Does the sound play back ungarbled then? You should be getting your DAW audio just from the computer itself and not through your monitoring chain. You might need to plug headphones into the computer if it doesn't have internal speakers. Try Youtube or Apple Music. What happens then? Just like mixing, with computer systems the thing that seems like the problem isn't always where the problem actually is. If I were in your shoes, I'd start eliminating potential problems to figure out exactly where the problem is. Uninstall Sonarworks. Reduce to a single Apollo. Then try a different interface altogether. Seems like a difficult path to go down but at least you'll know what the problem is and can work towards a real solution. I think there may be a couple things going on. This time there wasn't garbled audio, just no output at all which is the most common thing. And yes, the internal speakers play just fine. For now I'm going to leave Sonarworks uninstalled for a week or two and see what happens. If it comes back, we'll know it was not Sonarworks. And to answer your other question I'm using Sonarworks both as a plugin and also systemwide. The mod on the UAD support forum was at a total loss, waiting to hear back on UAD support ticket. Next step will be going down to just one Apollo unit which would be incredibly frustrating because I basically can't work with just one at this point. I've got everything patched into both units. Oh well, hopefully it doesn't come to that.
|
|
|
Post by gravesnumber9 on Dec 4, 2021 14:31:16 GMT -6
I think I may have found a solution... kind of similar to what schmalzy said but a bit different. I stumbled upon it accidentally. If I go to Console Settings and change the I/O to default and then back to my custom settings, it seems to restore everything. It's worked twice now. Very odd, seems like a bug. Reported to UAD.
|
|