Haha at this point I'll just assume you're trolling
500 threads on Windows gaming, youtuber clickbait and stupid Cinebench.
Not even one thread on Mojave.
I’m trolling the time wasters and attention hos.
Haha at this point I'll just assume you're trolling
Yep I did - and it was loaded. I ran it with try - and I got the warning about code signing. Went into Settings and allowed it, and verified it was loaded. When it crackled again, I stopped my music and manually unloaded the kext.
Is there anything else I can try ? Do you think there would be any benefit in installing it and rebooting ?
Thanks.
When you get crackling try sleeping the computer. This causes the Apple driver to effectively power down the T2 audio interface. If the AudioFix driver is loaded it may keep things working thereafter.
It may be that there is more than one cause of the problems. With the driver loaded it seems to be reliable on my system, whereas without I get audio failures after about an hour of streaming / game play / DVD playback. As others have noted, the sample rate in Audio Midi Setup may also affect behaviour. I have been running at 44.1khz and 48khz - i have not tried 96khz.
Thanks for the additional info. I'm trying to understand the logical flows at work here. Since I initially loaded your kext with <try>, I'm wondering if a reset was necessary that didn't happen. I just installed your kext, and rebooted. So T2 should have been reset (I would think at least). I'm listening to a 2 hour vaporwave mix on YT now I'll let you know if installing / rebooting made a difference.
PS: Can anyone explain what changing this MIDI / audio setting really does ? If I'm at 44.1 default and change this to 48 - does this mean that I'm changing for "higher quality" audio ? If so - does this devote more resources to audio to workaround the T2 issues (i.e. power saving) ?
bootcamp is missing 1 driver only for power ACPI and oddly no one is reporting the issue with the 2018 13in most likely because it uses the older intel chipset ect.
[doublepost=1533216738][/doublepost]
you say YES based off of what? The 2018 13inch has NO reported speaker crackling as it uses the OLD bootcamp, and still uses the OLDER intel chipset that the 2016-2017 used as they converted to QUAD not sex (6) core. and uses the old ddr3 LP. So the answer is NO as the new quad core has ONLY a upgraded graphics chipset and processor. IF anyone had the problem then its a RARE hardware defect.
everythingIs the crackling only happening on builtin speakers?
Or on connected audio devices as well? Either via BT or audio jack.
which configuration?Are you guys sure this is 100% replicable on all machines? I've had my machine for a week now with zero crackling. And I'm the type of the guy who would go through 10 refunds to get a perfect machine.
Are you guys sure this is 100% replicable on all machines? I've had my machine for a week now with zero crackling. And I'm the type of the guy who would go through 10 refunds to get a perfect machine.
So this only seems to affect the 15" models?
So this only seems to affect the 15" models?
Base 15 2.6 $2700 after taxeswhich configuration?
so the easiest way to replicate is to play a game while listen for example itunes radio?For me it always happens within 30 minutes of using the machine at high stress, e.g., gaming while listening to music on iTunes with Slack, Safari and a few other apps open at once. Can replicate this at ease actually.
Spotify seems to do it really easily for me, either when using Safari or Parallels (working with a Linux VM)so the easiest way to replicate is to play a game while listen for example itunes radio?
so the easiest way to replicate is to play a game while listen for example itunes radio?
Base 15 2.6 $2700 after taxes
Apple return period is 15 days, I'm surprised you guys are not returning your machines for new ones and instead hoping for a fix... these are really expensive machines.
As you raise the sample rate, the DMA rate also increases, although even at 96KHz the load is still very very low. Some sample rates could be problematic if they provoke a different pattern of DMA or sometimes because the software timing calculations are not quite right.
With the driver uninstalled my laptop is currently much more stable than it was a few days ago - I have only had one failure. It may be that the problem is provoked by some pattern of activity such as heavy flash access (such as the initial spotlight indexing, running games etc), which is it comes and goes seemingly randomly.