Guys, don't get me wrong, I'm not trying to defend Apple, as musician and producers I'm the user category that suffers probably the most, and believe me, I've spent my hours with'em on the phone already, though, it's just my own observation not pretending to be absolute.
I don't know which exact process make it trigger but what I CAN tell you is that it can be noticed while working in Logic and having CPU/HD monitor constantly open with console open in the background. When this "crack/noise/distortion" happens meter breaks the sealing and I get a crack. I can see it because after sound it's still there for a second. and instantly after that, just scrolling some events in console you can find some errors in console.
BTW. Before there were a couple of processes which were triggering it on a stable basis, and it appears to me that they've ironed them out somehow. but there are some, still, which can cause it.
p.s. all of that happens on a system which isn't perfectly clean and sterile, in my case, because I'm not their beta tester or whatever, so it might be that with clean install the latest mojave update actually solved it but who know. I can't wipe everything right now for that sake because I actually have some work to do.
All the best
Peace✌
Hey 8SlaiN,
Just curious... Are you getting Sample Rate Errors in Logic?
And, do you see any of the following messages in Console when the issue happens in Logic?
23:47:51.531293 -0500 launchservicesd CHECKIN:0x0-0x15c15c 7490
com.apple.audio.AudioMIDISetup
error 23:47:51.686156 -0500 Audio MIDI Setup
AEGetDescData of non-desc type 'reco' not a good idea
(^
Pretty damn sure this is the message "Error while trying to synchronize Audio and MIDI. Sample Rate "X" recognized.")
23:47:51.854687 -0500 coreaudiod HALS_UCPlugIn.cpp:1009:ObjectGetPropertyData: HALS_UCPlugIn::ObjectGetPropertyData:
['lchn', 'inpt', 1] failed: 1464353108
23:47:51.860089 -0500 coreaudiod HALS_UCPlugIn.cpp:1009:ObjectGetPropertyData: HALS_UCPlugIn::ObjectGetPropertyData:
['lchn', 'inpt', 1] failed: 1464353108
23:48:02.490031 -0500 Audio MIDI Setup
LSExceptions shared instance invalidated for timeout.
[doublepost=1545540245][/doublepost]
If it's purely software problem, when why is there an easy to follow set of instructions that causes it to trigger, yet some people can't get it to trigger (apparently) ?
Because as soon as you quit all apps, (at least on my machine), the problem goes away for a little while. It might go away for 15 mins, it might go away for an hour. Depends on whatever is kicking the issue off.
And again, I used my machine for 3 months with no distortion. I used it daily for many hours in a row with high end closed back headphones, plenty loud... Some days Logic or Live were open almost beginning to end of day. No distortion ever in the first 3 months.
As soon as I installed
Security Update 2018-002 and
Security Update 2018-003 on Dec. 9th distortion began within 15 mins after restart. (I noticed it on the speakers while watching Hulu at a really quiet level.) I restarted the machine again and it seemed like it went away.
The next day the issue started within an hour of using Logic, in headphones, and continued even if I unplugged and used the speakers. The issue stuck around as long as Logic was open. I also noticed sometime that first full day that the distortion got worse if I had iTunes, or anything else playing audio at the same time. As soon as I quit Logic it got better, when I quit anything else running the problem went away completely for an hour or so...
It's been like that every day since installing these two updates. Only the issue can take an hour, or 15 minutes to start, no set amount of time I can find yet. It just starts when whatever kicks it off triggers it, and it starts in any application playing audio for extended periods of time... iTunes, Chrome, Logic, even Finder.
But again, no set pattern or amount of time it takes, it just starts when it starts...
I've also been keeping Console open. The issue isn't displayed in Console by iTunes, Chrome or Finder. (Doubt iMovie or Quicktime will either). The only two apps I've found that print an error that looks like it refers to the issue are Logic and Ableton Live. (Probably part of why Apple hasn't done anything about it yet. Unless the Logic team were to devote some real time to this it seems like people developing the OS could easily miss it if they're not looking for it...)
At this point I'm pretty sure they need to be forced to look for it... After the past couple weeks of going back and forth, Engineering blew off my case and said they can't do anything until I upgrade to Mojave...
