nothing. i dont have it and experienced similar dropouts on the i9 before it got refunded.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Audio interface issues with 2018 Macbook Pro
- Thread starter T_Oscura
- Start date
- Sort by reaction score
In this case Spotify is just reporting the error since it happened to be the process using the underlying subsystem. The glitch is the pausing and restart of the audio engine above it. My logs show the kernel reporting the error, but the same chain of timed and the audio engine.
PS. Has the thread starter filed a bug report with Apple? The more documented cases of this they have, perhaps the more likely they are to fix it. Especially since this log looks a *lot* like the logs I’ve submitted.
PS. Has the thread starter filed a bug report with Apple? The more documented cases of this they have, perhaps the more likely they are to fix it. Especially since this log looks a *lot* like the logs I’ve submitted.
Last edited:
I think I've got it beat now ...
1) Turn OFF 'Set date/time automatically' in Date/Time
2) Turn OFF 'Set time zone automatically' in Date/Time
3) Turn off Location Services
4) Reboot
For me timed runs every 30 mins approx
Previously the timed calls were immediately followed by kernel calls to the IOAudio subsystem to close it down and restart it.
This appears to be what caused the dropouts.
Now I still get the timed calls but NOT the kernel calls for IOAudio.
No dropouts since I made this change
1) Turn OFF 'Set date/time automatically' in Date/Time
2) Turn OFF 'Set time zone automatically' in Date/Time
3) Turn off Location Services
4) Reboot
For me timed runs every 30 mins approx
Previously the timed calls were immediately followed by kernel calls to the IOAudio subsystem to close it down and restart it.
This appears to be what caused the dropouts.
Now I still get the timed calls but NOT the kernel calls for IOAudio.
No dropouts since I made this change
The source of audio does not matter. It can be either Logic, Spotify or YouTube.
Not yet, but I definitely will when I finally have some free time.
[doublepost=1544308682][/doublepost]Here's another log. This time the audio source was YouTube.
I have just had another glitch caused by IOAudio stopping and restarting.
Obviously my suggestion above is not a complete solution but it has had some effect.
Back to the drawing board.
I really think at this point apple should go back to the drawing board.
As it stands the only mac you can buy for audio is the nTB 13" and the overpriced 5y old trashcan Mac Pro.
So here are my recent findings:
- The good news is that disabling Wifi solves the problem for me.
- With Wifi disabled, I can't reproduce a dropout by changing the time sync settings.
- As soon as I switched back to Wifi, a dropout occured.
Here's a screenshot of the timed event with the connection disabled. I listened to a continous mix for 2 hours and the only time the timed process came back is when I enabled Wifi again.
Now it's possible that I spoke too early again, time will tell, but right now it looks like this is a solution for me until Apple fixes it.
- The good news is that disabling Wifi solves the problem for me.
- With Wifi disabled, I can't reproduce a dropout by changing the time sync settings.
- As soon as I switched back to Wifi, a dropout occured.
Here's a screenshot of the timed event with the connection disabled. I listened to a continous mix for 2 hours and the only time the timed process came back is when I enabled Wifi again.
Now it's possible that I spoke too early again, time will tell, but right now it looks like this is a solution for me until Apple fixes it.
We have also been experiencing this very frustrating bug during recording and playback on multiple RME devices, using their latest drivers and class compliant mode, throughout the last few OSX updates (including 10.14.2). It affects YouTube, Spotify and iTunes as much as it does Reaper and other DAWs. Switching off wifi definitely does not solve the issue. Currently on deadline but will contact Apple with log reports from Console next week and I hope everyone else does likewise to push this up Apple's priorities list...
Have you had a chance to look at the logs? I wonder if your issue is related or completely different than the time sync one. Which would mean yet another issue with audio and these 2018 T2 machines.
Didn't RME have issues with the drivers on other iterations of the O/S? I seem to remember reading something like that in their forums when I was first hunting around trying to figure out what was going on with the audio glitches. I don't have an RME so I could be completely mistaken. Definitely very, very, very annoying to say the least.
Anyone having these issues with Presonus products? They have a post on their site saying everything should be compatible if you put a traditional USB hub between the computer and the interface, but curious if this is still an issue.
RME never had issues with drivers and it works flawlessly on Mojave on non-T2 machines.
As an owner of their products, I'll just add my agreement that RME drivers are typically rock-solid and best-in-industry on both Windows and macOS.
It's extremely concerning that recent Macs don't appear to be suitable for audio production. Apple needs to get to the bottom of this yesterday.
It's extremely concerning that recent Macs don't appear to be suitable for audio production. Apple needs to get to the bottom of this yesterday.
Just as an added point of reference, I got a 2018 15'' this week, and have been using it with a Presonus Audiobox interface (with Logic and Max/MSP mostly). I haven't had any issues thus far. The interface is recognized normally, and behaves as expected.
Just purchased a USB-C Audio Interface from M-Audio (M-Track 2x2), hoping that the direct connection to USB-C and no adapter in between would fix the glitching issue I've had with my PreSonus interface running through an adapter, but nope, still experience periodic dropouts when recording audio. If I only use software instruments and USB-Midi keyboard I don't have any problems, it's only when recording audio from say, my electric guitar.
If I disable the automatic update of the System time in Time and Date Preferences and do a
command, I haven't noticed these glitches until restarting the Mac, but this could be a coincidence, so it's premature to claim that it does anything to solve the issue.
But I've been recording for some time now without problems after shutting down the "timed" daemon.
Just trying to find a work-around...
If I disable the automatic update of the System time in Time and Date Preferences and do a
Code:
sudo killall timedBut I've been recording for some time now without problems after shutting down the "timed" daemon.
Just trying to find a work-around...
Are you using a USB 2.0 hub in between the Presonus and the USB C adaptor? That's what I had to do for it to work (and that solution is recommended on their site). I have a Audiobox 96 plugged into a small $5 USB hub, which is plugged into the USB-C dock. Works fine for both playback and recording in Logic.
Read this thread on the RME board
https://www.forum.rme-audio.de/viewtopic.php?pid=136666#p136666
Based on this I bought a Caldigit Thunderbolt 3 hub
This is expensive but DOES fix the problem.
We have been discussing this on a thread in the mac mini section but I see no reason it won't work on any other machine with a T2 chip.
Of course I should not have needed to buy the hub, this IMO is a software problem that Apple need to fix ASAP.
https://www.forum.rme-audio.de/viewtopic.php?pid=136666#p136666
Based on this I bought a Caldigit Thunderbolt 3 hub
This is expensive but DOES fix the problem.
We have been discussing this on a thread in the mac mini section but I see no reason it won't work on any other machine with a T2 chip.
Of course I should not have needed to buy the hub, this IMO is a software problem that Apple need to fix ASAP.
Didn't try using a USB 2.0 Hub with the PreSonus interface.
I assume it must be a powered USB 2.0 interface to work? I have both powered and passive USB 2.0 hubs, so I'll try running it through one of them.
Thanks for the tip!
Maybe my native USB-C interface runs better as well if I "downgrade" it by running it through a USB 2.0 hub...
Hmm.. So passing the USB traffic through a Thunderbolt adapter somehow solves this issue?
I don't need the Display Port / docking functionality, just need my damned USB-C Audio interface to work.
I plug it directly into a combined USB-C / Thunderbolt 3 port on my MacBook, so I can't understand how running it through another Thunderbolt adapter would make it work any better. All it does is to route the USB traffic through the same circuits in the end anyway...
I don't understand either, I just know it works.
I have a theory though. With the hub you are using usb2 software in the hub and thunderbolt software/hardware in the mac. Without the hub you are using both usb2 software and thunderbolt software/hardware in the mac.
As I said before it should not have been necessary for me to buy the hub, this is a software issue that apple should fix pronto.
Just to be clear here, I have studied the console logs both with and without the hub and the results are quite different. With the hub, timed does not cause the kernel to close and restart the ioaudio system.
Last edited:
No, I'm using a passive hub which is drawing power from the computer. The Presonus is buss powered as well.
Hmm... Interesting. Then it has to be some internal routing in the kernel modules gone haywire...
Please send your logs to Apple, just so they get confirmation on this bug from as many sources as possible.
This did not work. I was able to reproduce the exact same audio dropout bug. Having said that, this isn't a bad thing to do...I was unable to boot from a USB drive when I reinstalled my OS, and now I can. Thanks for that!
Dumb question. Does you DAW let you set the timing source? If so, do you have it set to the PreSonus or the computer. I have glitchy results when I set to the computer. But when I set it to my Audio Interface (Audient ID14) every thing works fine. My DAW is Adobe Audition.
Also I use a $30 USB Molkin adapter/dongle to connect the computer to USB 2.0 on the Audio Interface.