Could be, the TB2->TB3 dongle is not exactly Apple's greatest achievement. But I honestly would advise against spending that much money if you are not certain. You should test it first. The T2 chip bug is known to happen with USB 2.0 interfaces. I haven't seen any reports with a Thunderbolt 2 interface.Nimrod7 wrote: Wed May 01, 2019 6:16 pm Can this be the issue?
I don't have access to a T3 interface. I can get this which is not cheap but I am not willing to do that unless I am sure it's the reason:
https://www.thomann.de/ie/universal_aud ... 3_card.htm?
Live 10 don't play back smoothly on new mac hardware.
-
- KVRAF
- 2814 posts since 26 Jul, 2015 from Philadelphia
Follow me on Youtube for videos on spatial and immersive audio production.
-
- KVRist
- Topic Starter
- 216 posts since 10 May, 2006 from Ireland
Just tried playing back with Mac Internal Speakers.
On switching to internal speakers, CPU went down to 25% immediately (25% is due some master channel plugins I use, if I turn them off goes down to 3-4%). Then played back really smooth the entire song. Not a single drop.
Here is a video, first playing back with Core Audio - Internal, then switching to Universal Audio Interface with T2->T3 Adapter.
(video needs some time to process hi resolution)
Got in touch with Universal Audio they said that probably a faulty T2 cable. I switched the cable, same issue.
On switching to internal speakers, CPU went down to 25% immediately (25% is due some master channel plugins I use, if I turn them off goes down to 3-4%). Then played back really smooth the entire song. Not a single drop.
Here is a video, first playing back with Core Audio - Internal, then switching to Universal Audio Interface with T2->T3 Adapter.
(video needs some time to process hi resolution)
Got in touch with Universal Audio they said that probably a faulty T2 cable. I switched the cable, same issue.
-
- KVRAF
- 2814 posts since 26 Jul, 2015 from Philadelphia
Tricky. I found some reports from people who experienced the same issue and solved it by doing a hardware reset on the Apollo: https://help.uaudio.com/hc/en-us/articl ... ware-Reset
Did you try that yet?
Did you try that yet?
Follow me on Youtube for videos on spatial and immersive audio production.
-
- KVRist
- Topic Starter
- 216 posts since 10 May, 2006 from Ireland
Just tried hardware reset.mgw38 wrote: Thu May 02, 2019 10:39 pm Tricky. I found some reports from people who experienced the same issue and solved it by doing a hardware reset on the Apollo: https://help.uaudio.com/hc/en-us/articl ... ware-Reset
Did you try that yet?
No change sadly.
Thanks,
-
- KVRAF
- 2814 posts since 26 Jul, 2015 from Philadelphia
Looks like you need to find a way to get access to a TB3 audio interface for testing. You could also try a different TB2->TB3 dongle but chances that this works are not particularly high.
I had the same problem with a Focusrite interface one or two years back. I worked with Focusrite tech support for a month without getting anywhere. Switching to a different interface brand solved the issue. Couple of weeks later, a MacOS update resolved the original problem with the Focusrite. I’m back to the Focusrite now and it has worked perfectly ever since. Sometimes these things can be a bit temperamental.
I had the same problem with a Focusrite interface one or two years back. I worked with Focusrite tech support for a month without getting anywhere. Switching to a different interface brand solved the issue. Couple of weeks later, a MacOS update resolved the original problem with the Focusrite. I’m back to the Focusrite now and it has worked perfectly ever since. Sometimes these things can be a bit temperamental.
Follow me on Youtube for videos on spatial and immersive audio production.
-
colonel_mustard colonel_mustard https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=439842
- KVRist
- 124 posts since 24 Apr, 2019
Have you tried reinstalling the software that talks to the hardware?
I have a different setup (Apogee Quartet) but was having some issues after upgrading to a new mac and the latest OS. Sorted it out today, finally, which required a reinstall of software on the laptop and a firmware update on the interface. Something to do with third-party kernel extension permissions, which you're only able to grant within 30 minutes of an install if you're running High Sierra or Mojave.
https://knowledgebase.apogeedigital.com ... tallation/
Could be a similar issue with the UAD? Something to be aware of anyway.
Good luck!
I have a different setup (Apogee Quartet) but was having some issues after upgrading to a new mac and the latest OS. Sorted it out today, finally, which required a reinstall of software on the laptop and a firmware update on the interface. Something to do with third-party kernel extension permissions, which you're only able to grant within 30 minutes of an install if you're running High Sierra or Mojave.
https://knowledgebase.apogeedigital.com ... tallation/
Could be a similar issue with the UAD? Something to be aware of anyway.
Good luck!
Nimrod7 wrote: Fri May 03, 2019 9:46 amJust tried hardware reset.mgw38 wrote: Thu May 02, 2019 10:39 pm Tricky. I found some reports from people who experienced the same issue and solved it by doing a hardware reset on the Apollo: https://help.uaudio.com/hc/en-us/articl ... ware-Reset
Did you try that yet?
No change sadly.
Thanks,
-
- KVRist
- Topic Starter
- 216 posts since 10 May, 2006 from Ireland
Well, guess what, I have a Universal Audio Arrow in a video editing workstation. Totally forgotten that it exists.mgw38 wrote: Fri May 03, 2019 12:39 pm Looks like you need to find a way to get access to a TB3 audio interface for testing. You could also try a different TB2->TB3 dongle but chances that this works are not particularly high.
I have connected this to the Mac mini directly with thunderbolt 3. Having the exact same issue.
Stutters, and artefacts, unable to play back. No change from the T2 Apollo 8.
So I guess the problem is not on the adapter, neither the interface.
Last edited by Nimrod7 on Fri May 03, 2019 1:12 pm, edited 1 time in total.
-
- KVRist
- Topic Starter
- 216 posts since 10 May, 2006 from Ireland
I tried uninstalling with the official uninstaller, then deleting all the left over config and prefs files I found manually using spotlight search.colonel_mustard wrote: Fri May 03, 2019 1:05 pm Have you tried reinstalling the software that talks to the hardware?
Reinstalled, but still the same...
- Beware the Quoth
- 35506 posts since 4 Sep, 2001 from R'lyeh Oceanic Amusement Park and Funfair
Next step would be finding out if this happens with something other than Live, I would suggest.Nimrod7 wrote: Fri May 03, 2019 1:10 pmWell, guess what, I have a Arrow in a video editing workstation. Totally forgotten that it exists.mgw38 wrote: Fri May 03, 2019 12:39 pm Looks like you need to find a way to get access to a TB3 audio interface for testing. You could also try a different TB2->TB3 dongle but chances that this works are not particularly high.![]()
I have connected this to the Mac mini directly with thunderbolt 3. Having the exact same issue.
Stutters, and artefacts, unable to play back. No change from the T2 Apollo 8.
So I guess the problem is not on the adapter, neither the interface.
An idiot on Set Theory:
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
"In some cases there is an object called red that contains everything that is red. In much the same way a pot is a plate."
-
colonel_mustard colonel_mustard https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=439842
- KVRist
- 124 posts since 24 Apr, 2019
DAMN IT.Nimrod7 wrote: Fri May 03, 2019 1:12 pmI tried uninstalling with the official uninstaller, then deleting all the left over config and prefs files I found manually using spotlight search.colonel_mustard wrote: Fri May 03, 2019 1:05 pm Have you tried reinstalling the software that talks to the hardware?
Reinstalled, but still the same...![]()
Sounds like you're doing all you can. Besides that time-limited permissions button, the only other Mojave issue I'm aware of is the CoreMIDI bug that makes all of my DAWs hang at opening time. Could that be tripping up the UAD somehow?
https://music.stackexchange.com/questio ... -on-mojave
We're all rooting for you
-
- KVRist
- Topic Starter
- 216 posts since 10 May, 2006 from Ireland
I tried using my Machine MK3 as Audio Interface.
It works well. No playback issues.
Next on the list is trying Logic with Universal Audio and see from there...
It works well. No playback issues.
Next on the list is trying Logic with Universal Audio and see from there...
-
- KVRAF
- 2814 posts since 26 Jul, 2015 from Philadelphia
That would support the idea that there is some incompatibility with the UAD interfaces. Could be a misconfiguration or software conflict somewhere.Nimrod7 wrote: Fri May 03, 2019 1:27 pm I tried using my Machine MK3 as Audio Interface.
It works well. No playback issues.
The Machine MK3 is a USB 2.0 audio interface which should pretty much rule out the T2 chip bug. At least you have a functional setup at this point.
Follow me on Youtube for videos on spatial and immersive audio production.
-
- KVRist
- Topic Starter
- 216 posts since 10 May, 2006 from Ireland
CONSOLE is overloaded with message such as:
default 10:21:04.077186 +0100 kernel + IOAudioDevice[<private>]::initiatePowerStateChange(0x0) - current = 2 - pending = 1
default 10:21:04.077188 +0100 kernel + IOAudioDevice[<private>]:rotectedCompletePowerStateChange() - current = 2 - pending = 1
default 10:21:04.077190 +0100 kernel - IOAudioDevice[<private>]:rotectedCompletePowerStateChange() - current = 1 - pending = 1 returns 0x0
default 10:21:04.077191 +0100 kernel - IOAudioDevice[<private>]::initiatePowerStateChange(0x0) - current = 1 - pending = 1 returns 0x0
default 10:21:04.077192 +0100 kernel - IOAudioDevice[<private>]::scheduleIdleAudioSleep: idleSleepDelayTime = 00
default 10:21:04.077193 +0100 kernel - IOAudioDevice[<private>]::audioEngineStopped() - numRunningAudioEngines = 0
FL Studio has the same issue, all those messages, and doesn't play back.
Logic on the other hand works well. CONSOLE is silent, and playing smoothly.
default 10:21:04.077186 +0100 kernel + IOAudioDevice[<private>]::initiatePowerStateChange(0x0) - current = 2 - pending = 1
default 10:21:04.077188 +0100 kernel + IOAudioDevice[<private>]:rotectedCompletePowerStateChange() - current = 2 - pending = 1
default 10:21:04.077190 +0100 kernel - IOAudioDevice[<private>]:rotectedCompletePowerStateChange() - current = 1 - pending = 1 returns 0x0
default 10:21:04.077191 +0100 kernel - IOAudioDevice[<private>]::initiatePowerStateChange(0x0) - current = 1 - pending = 1 returns 0x0
default 10:21:04.077192 +0100 kernel - IOAudioDevice[<private>]::scheduleIdleAudioSleep: idleSleepDelayTime = 00
default 10:21:04.077193 +0100 kernel - IOAudioDevice[<private>]::audioEngineStopped() - numRunningAudioEngines = 0
FL Studio has the same issue, all those messages, and doesn't play back.
Logic on the other hand works well. CONSOLE is silent, and playing smoothly.