MacBook Pro 2018 - Speakers Crackling

[fokmik]

I hope after the Mojave is official release, they will deliver the 2018 MBP with Mojave pre-installed OR release a patch to resolve the HS as well

 

[danieleilertsen]

Talked to Apple support norway. Apple knows about the issue, and the fix will come out anytime now.

Workaround: forceclose audioaud.

Anyway, I had this problem, and the crackling was low. It seemd like the speaks got blown out.

Apple says the speakers will not take any damage of this, but does it? I still have my 14 days return.

what do you suggest?

 

[fokmik]

return it...the speakers can take damage, remember the bootcamp audio issue from 2016 MBP fiasco

 

[MD7200]

Send it back... I've also sent mine back. Only if these problems are solved, I would perhaps order one more. It can not be healthy for the speakers!

 

[AdamA9]

Hopefully, the fix will mean I can also game and listen to YouTube music at the same time. This machine is so poor at handling the basic things I use it for. I swear my 2013 was much better.

I have Safari and a game open, and it's stuttering, freezing, and lagging even when typing this. Mojave better fix all of this crap as I'm losing patience.

 

[danieleilertsen]

return it...the speakers can take damage, remember the bootcamp audio issue from 2016 MBP fiasco

Thank you for this.

I am sending it back, and getting it replaced. Its nice to know that this is a software issue that will be fixed. They told me this again, that apple know about the problem and is working on a fix.

I kinda think there are more issues they are working on since they havnt released the update yet?

 

[CreeptoLoser]

Hopefully, the fix will mean I can also game and listen to YouTube music at the same time. This machine is so poor at handling the basic things I use it for. I swear my 2013 was much better.

I have Safari and a game open, and it's stuttering, freezing, and lagging even when typing this. Mojave better fix all of this crap as I'm losing patience.

YouTube and your game are both trying to write to video memory and are running out of VRAM and bandwidth. The problem here is you don’t understand how these things work.

 

[AdamA9]

YouTube and your game are both trying to write to video memory and are running out of VRAM and bandwidth. The problem here is you don’t understand how these things work.

Thanks for the condescending remark, but this isn't my problem at all. My problem is that my 2013 MacBook pro could handle these two tasks with ease. My 2018 MacBook Pro cannot. For a consumer, that is the only issue here. It has nothing to do with my understanding of how these things work.

 

[M.Rizk]

YouTube and your game are both trying to write to video memory and are running out of VRAM and bandwidth. The problem here is you don’t understand how these things work.

“You are using it wrong” mentality. Got it.

 

[AdamA9]

“You are using it wrong” mentality. Got it.

How dare you expect to be able to do two things at once on the three-thousand-pound laptop! Learn how it works, luddite!

 

[mdnz]

Thanks for the condescending remark, but this isn't my problem at all. My problem is that my 2013 MacBook pro could handle these two tasks with ease. My 2018 MacBook Pro cannot. For a consumer, that is the only issue here. It has nothing to do with my understanding of how these things work.

If I were you I'd return it until they fix it. Who knows how long it can be still.

 

[Painter2002]

“You are using it wrong” mentality. Got it.

"You are using it wrong" isn't really a good quote here. I have to agree with @CreeptoLoser here. We are talking about trying to use a device for something it is generally been known for not being very proficient at.

We don't know what game @AdamA9 is playing, but it really isn't surprising that a game and safari combined together will cause the MBP to stutter, it just doesn't have the VRAM to handle both without stuttering. The MacBook Pro has never been well designed to run games period. Most of this has to do with the graphic limitations.

Besides that, this thread is about speaker crackling, not graphics issues. My suggestion to @AdamA9 is if you want to play games on a computer, there are a lot of better game-optimized computers in the Windows universe, such as Dell, Razor, etc.

 

[fokmik]

"You are using it wrong" isn't really a good quote here. I have to agree with @CreeptoLoser here. We are talking about trying to use a device for something it is generally been known for not being very proficient at.

We don't know what game @AdamA9 is playing, but it really isn't surprising that a game and safari combined together will cause the MBP to stutter, it just doesn't have the VRAM to handle both without stuttering. The MacBook Pro has never been well designed to run games period. Most of this has to do with the graphic limitations.

Besides that, this thread is about speaker crackling, not graphics issues. My suggestion to @AdamA9 is if you want to play games on a computer, there are a lot of better game-optimized computers in the Windows universe, such as Dell, Razor, etc.

Like the user said, HIS 2013 MACBOOK PRO can handle these things perfectly...so no matter what he plays..your statement is not relevant here

 

[Painter2002]

Like the user said, HIS 2013 MACBOOK PRO can handle these things perfectly...so no matter what he plays..your statement is not relevant here

Why so hostile over a simple comment? Maybe I miss-worded my comment, but I honestly have a hard time believing that his 2013 MBP can handle it better than his 2018. And if it is a software bug causing the issue, then report it to Apple and wait for them to release a fix. It may take time, but there are always bugs on new releases, and its part of being an early adopter of a product.

 

[mdnz]

Why so hostile over a simple comment? Maybe I miss-worded my comment, but I honestly have a hard time believing that his 2013 MBP can handle it better than his 2018. And if it is a software bug causing the issue, then report it to Apple and wait for them to release a fix. It may take time, but there are always bugs on new releases, and its part of being an early adopter of a product.

I'm sorry but being a beta tester when paying over $3000 should be unacceptable. Apple also has labs you know? They can actually use it before releasing something. Look at the amount of """""early adopter""""" problems with the older MBP models and this one.

 

[M.Rizk]

Gaming might not be a major use preference on macOS but it exists. Blizzard has all their games ported to macOS (except OW due to Metal restrictions). Fortnite is there. Dota2 is there (using MoltenVK).

Apple itself advertised gaming on this MBP for the first time ever in the history of MBPs. (There is literally a screenshot from Fortnite on the MBP page on Apple.com)

MacBook Pros use hardware that is also used in Windows laptops. It is not like they are using custom made hardware that doesn’t support gaming.

Apple is severely under delivering here. So many issues on macOS for the 2018 MBPs. Out of date/incompatible drivers for it on Bootcamp. It is a huge mess.

 

[MD7200]

I'm sorry but being a beta tester when paying over $3000 should be unacceptable. Apple also has labs you know? They can actually use it before releasing something. Look at the amount of """""early adopter""""" problems with the older MBP models and this one.

So I complained to Apple that their statement was, buy the 2017 model. Oh, sorry, this is no longer available. So probably a "normal" user can only buy a new MacBook if it is at least 3 months on the market?!? realize that this is pretty stupid.

 

[GameChanger23]

Can I use the Mojave beta and High Sierra on the Same machine and will the mentioned Firmware that is contained in Mojave fix it in High Sierra as well? Or is switch to 48000HZ each time I exit logic the only solution at the moment?

 

[Abumuslim]

Can I use the Mojave beta and High Sierra on the Same machine and will the mentioned Firmware that is contained in Mojave fix it in High Sierra as well? Or is switch to 48000HZ each time I exit logic the only solution at the moment?

Mojave is an update for High Sierra, after I installed mojave, logic pro did switch my MIDI settings to 44,1000 as it did in High Sierra, but the fix is there is no crackling in 44,100 with Mojave
[doublepost=1535404491][/doublepost]BTW, Mojave beta is very stable now, and probably you will not notice any crucial difference from High Sierra

 

[CreeptoLoser]

Gaming might not be a major use preference on macOS but it exists. Blizzard has all their games ported to macOS (except OW due to Metal restrictions). Fortnite is there. Dota2 is there (using MoltenVK).

Apple itself advertised gaming on this MBP for the first time ever in the history of MBPs. (There is literally a screenshot from Fortnite on the MBP page on Apple.com)

Apple has always advertised a couple of games on their PowerBook and then MacBook Pro sites starting with Unreal Tournament 2004.

In the case of the new 2018 models, the page is explicitly advertizing the eGPU and stating how much faster it is than the dGPU.

Todays new Mojave beta again has a new firmware. I think we are 2-3 weeks away from gold release because progress looks really good. Easily the best macOS ever and really makes Windows look backwards.

 

[Jorg1312]

I have mad problems with audio here. Started working on real projects now with a professional sound card but still problems. I have loads of DAW crashes I never had before and lost of audio glitches and dropouts. This is even through my sound card. Must be a core audio thing.

This is the cause for pretty much all my crashes in case anyone knows what that means:

Process:               Cubase 9.5 [1887]

Path:                  /Applications/Cubase 9.5.app/Contents/MacOS/Cubase 9.5

Identifier:            com.steinberg.cubase9v5

Version:               9.5.30.192 (9.5.30.192)

Code Type:             X86-64 (Native)

Parent Process:        ??? [1]

Responsible:           Cubase 9.5 [1887]

User ID:               501



Date/Time:             2018-08-27 22:56:07.962 +0100

OS Version:            Mac OS X 10.13.6 (17G2208)

Report Version:        12

Bridge OS Version:     2.4.1 (15P6703)

Anonymous UUID:        BD5B825A-DC80-FCF4-0C05-5D06969A18FE





Time Awake Since Boot: 22000 seconds



System Integrity Protection: enabled



Crashed Thread:        0  Dispatch queue: com.apple.main-thread



Exception Type:        EXC_CRASH (SIGABRT)

Exception Codes:       0x0000000000000000, 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY



Application Specific Information:

Performing @selector(select:) from sender SMTGCocoa1525696875_MenuItem 0x6080004d9980

Pure virtual function called!

abort() called



Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   libsystem_kernel.dylib            0x00007fff5000ab66 __pthread_kill + 10

1   libsystem_pthread.dylib           0x00007fff501d5080 pthread_kill + 333

2   libsystem_c.dylib                 0x00007fff4ff661ae abort + 127

3   libc++abi.dylib                   0x00007fff4de60f8f abort_message + 245

4   libc++abi.dylib                   0x00007fff4de7d952 __cxa_pure_virtual + 18

5   com.steinberg.cubase9v5           0x00000001114e8d12 0x10f77e000 + 30846226

6   com.steinberg.cubase9v5           0x000000011135500d 0x10f77e000 + 29192205

7   com.steinberg.cubase9v5           0x00000001113573af 0x10f77e000 + 29201327

8   com.apple.CoreFoundation          0x00007fff27fbfedc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12

9   com.apple.CoreFoundation          0x00007fff27fbfdaa _CFXRegistrationPost + 458

10  com.apple.CoreFoundation          0x00007fff27fbfae1 ___CFXNotificationPost_block_invoke + 225

11  com.apple.CoreFoundation          0x00007fff27f7d880 -[_CFXNotificationRegistrar find:eek:bject:eek:bserver:enumerator:] + 1664

12  com.apple.CoreFoundation          0x00007fff27f7c9b7 _CFXNotificationPost + 599

13  com.apple.Foundation              0x00007fff2a08c8c7 -[NSNotificationCenter postNotificationName:eek:bject:userInfo:] + 66

14  com.apple.AppKit                  0x00007fff25668973 -[NSWindow becomeKeyWindow] + 1488

15  com.steinberg.cubase9v5           0x0000000111524f40 0x10f77e000 + 31092544

16  com.apple.AppKit                  0x00007fff25667bcd -[NSWindow _changeKeyAndMainLimitedOK:] + 878

17  com.apple.AppKit                  0x00007fff256e2ca8 -[NSWindow _orderOutAndCalcKeyWithCounter:stillVisible:docWindow:] + 1261

18  com.apple.AppKit                  0x00007fff2566ac0c NSPerformVisuallyAtomicChange + 146

19  com.apple.AppKit                  0x00007fff25e18833 -[NSWindow _doWindowOrderOutWithWithKeyCalc:forCounter:eek:rderingDone:docWindow:] + 85

20  com.apple.AppKit                  0x00007fff25e19d26 -[NSWindow _reallyDoOrderWindowOutRelativeTo:findKey:forCounter:force:isModal:] + 446

21  com.apple.AppKit                  0x00007fff256728ec -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 172

22  com.apple.AppKit                  0x00007fff25671765 -[NSWindow _doOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 287

23  com.apple.AppKit                  0x00007fff256715cb -[NSWindow orderWindow:relativeTo:] + 169

24  com.apple.AppKit                  0x00007fff25e1740e -[NSWindow _finishClosingWindow] + 479

25  com.apple.AppKit                  0x00007fff257b6ed8 -[NSWindow _close] + 378

26  com.steinberg.cubase9v5           0x0000000111520423 0x10f77e000 + 31073315

27  com.steinberg.cubase9v5           0x00000001115204de 0x10f77e000 + 31073502

28  com.steinberg.cubase9v5           0x000000011105661c 0x10f77e000 + 26052124

29  com.steinberg.cubase9v5           0x00000001114e2419 0x10f77e000 + 30819353

30  com.steinberg.cubase9v5           0x0000000111427e06 0x10f77e000 + 30055942

31  com.steinberg.cubase9v5           0x00000001112cfb4f 0x10f77e000 + 28646223

32  com.steinberg.cubase9v5           0x00000001112d020a 0x10f77e000 + 28647946

33  com.steinberg.cubase9v5           0x00000001112cfbff 0x10f77e000 + 28646399

34  com.steinberg.cubase9v5           0x000000010fb007e1 0x10f77e000 + 3680225

35  com.steinberg.cubase9v5           0x000000010fb00609 0x10f77e000 + 3679753

36  com.steinberg.cubase9v5           0x0000000110749c3e 0x10f77e000 + 16563262

37  com.steinberg.cubase9v5           0x00000001107445dc 0x10f77e000 + 16541148

38  com.steinberg.cubase9v5           0x0000000110743b2c 0x10f77e000 + 16538412

39  com.steinberg.cubase9v5           0x0000000110745c1b 0x10f77e000 + 16546843

40  com.steinberg.cubase9v5           0x0000000110741727 0x10f77e000 + 16529191

41  com.steinberg.cubase9v5           0x000000011075bcf7 0x10f77e000 + 16637175

42  com.steinberg.cubase9v5           0x00000001110f5293 0x10f77e000 + 26702483

43  com.steinberg.cubase9v5           0x00000001107597f0 0x10f77e000 + 16627696

44  com.steinberg.cubase9v5           0x0000000110754c8f 0x10f77e000 + 16608399

45  com.steinberg.cubase9v5           0x00000001107591bc 0x10f77e000 + 16626108

46  com.steinberg.cubase9v5           0x000000011073ea1c 0x10f77e000 + 16517660

47  com.steinberg.cubase9v5           0x000000011073c945 0x10f77e000 + 16509253

48  com.steinberg.cubase9v5           0x000000010fb0b4e8 0x10f77e000 + 3724520

49  com.steinberg.cubase9v5           0x000000010fb666dc 0x10f77e000 + 4097756

50  com.steinberg.cubase9v5           0x0000000110c9de40 0x10f77e000 + 22150720

51  com.steinberg.cubase9v5           0x0000000110d56cdb 0x10f77e000 + 22908123

52  com.steinberg.cubase9v5           0x0000000111281208 0x10f77e000 + 28324360

53  com.steinberg.cubase9v5           0x00000001104a3e39 0x10f77e000 + 13786681

54  com.steinberg.cubase9v5           0x000000011127defa 0x10f77e000 + 28311290

55  com.steinberg.cubase9v5           0x0000000110cc7fcf 0x10f77e000 + 22323151

56  com.steinberg.cubase9v5           0x0000000110c8d7fa 0x10f77e000 + 22083578

57  com.steinberg.cubase9v5           0x000000011128040e 0x10f77e000 + 28320782

58  com.steinberg.cubase9v5           0x00000001114eb25e 0x10f77e000 + 30855774

59  com.steinberg.cubase9v5           0x000000011126c4eb 0x10f77e000 + 28239083

60  com.steinberg.cubase9v5           0x00000001112c29b8 0x10f77e000 + 28592568

61  com.steinberg.cubase9v5           0x000000011126dd70 0x10f77e000 + 28245360

62  com.steinberg.cubase9v5           0x0000000111268ae5 0x10f77e000 + 28224229

63  com.steinberg.cubase9v5           0x00000001112dd715 0x10f77e000 + 28702485

64  com.steinberg.cubase9v5           0x00000001104e733a 0x10f77e000 + 14062394

65  com.steinberg.cubase9v5           0x000000011132d879 0x10f77e000 + 29030521

66  com.steinberg.cubase9v5           0x000000011152cbd3 0x10f77e000 + 31124435

67  com.apple.AppKit                  0x00007fff25cdda43 -[NSApplication(NSResponder) sendAction:to:from:] + 312

68  com.steinberg.cubase9v5           0x000000011104c725 0x10f77e000 + 26011429

69  com.apple.AppKit                  0x00007fff25772213 -[NSMenuItem _corePerformAction] + 323

70  com.apple.AppKit                  0x00007fff25771f9b -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 114

71  com.apple.AppKit                  0x00007fff25770dff -[NSMenu performKeyEquivalent:] + 363

72  com.apple.AppKit                  0x00007fff25cdc6a9 routeKeyEquivalent + 884

73  com.apple.AppKit                  0x00007fff25cd9ce0 -[NSApplication(NSEvent) sendEvent:] + 1096

74  com.steinberg.cubase9v5           0x000000011104c24f 0x10f77e000 + 26010191

75  com.apple.AppKit                  0x00007fff2553a8b5 -[NSApplication run] + 812

76  com.steinberg.cubase9v5           0x00000001115049be 0x10f77e000 + 30960062

77  com.steinberg.cubase9v5           0x000000011132d13d 0x10f77e000 + 29028669

78  com.steinberg.cubase9v5           0x0000000111046690 0x10f77e000 + 25986704

79  com.steinberg.cubase9v5           0x000000011104b7fb 0x10f77e000 + 26007547

80  libdyld.dylib                     0x00007fff4feba015 start + 1



Thread 1:: CRASH THREAD

0   libsystem_kernel.dylib            0x00007fff5000125e semaphore_timedwait_trap + 10

1   com.steinberg.cubase9v5           0x000000011106c1c2 0x10f77e000 + 26141122

2   com.steinberg.cubase9v5           0x000000011106cadc 0x10f77e000 + 26143452

3   com.steinberg.cubase9v5           0x00000001104ee23e 0x10f77e000 + 14090814

4   com.steinberg.cubase9v5           0x000000011106bdcf 0x10f77e000 + 26140111

5   libsystem_pthread.dylib           0x00007fff501d5ae0 _pthread_suspended_body + 229

 

[zhy3213]

I have mad problems with audio here. Started working on real projects now with a professional sound card but still problems. I have loads of DAW crashes I never had before and lost of audio glitches and dropouts. This is even through my sound card. Must be a core audio thing.

This is the cause for pretty much all my crashes in case anyone knows what that means:

Process: Cubase 9.5 [1887]

Path: /Applications/Cubase 9.5.app/Contents/MacOS/Cubase 9.5

Identifier: com.steinberg.cubase9v5

Version: 9.5.30.192 (9.5.30.192)

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Cubase 9.5 [1887]

User ID: 501



Date/Time: 2018-08-27 22:56:07.962 +0100

OS Version: Mac OS X 10.13.6 (17G2208)

Report Version: 12

Bridge OS Version: 2.4.1 (15P6703)

Anonymous UUID: BD5B825A-DC80-FCF4-0C05-5D06969A18FE





Time Awake Since Boot: 22000 seconds



System Integrity Protection: enabled



Crashed Thread: 0 Dispatch queue: com.apple.main-thread



Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY



Application Specific Information:

Performing @selector(select from sender SMTGCocoa1525696875_MenuItem 0x6080004d9980

Pure virtual function called!

abort() called



Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 libsystem_kernel.dylib 0x00007fff5000ab66 __pthread_kill + 10

1 libsystem_pthread.dylib 0x00007fff501d5080 pthread_kill + 333

2 libsystem_c.dylib 0x00007fff4ff661ae abort + 127

3 libc++abi.dylib 0x00007fff4de60f8f abort_message + 245

4 libc++abi.dylib 0x00007fff4de7d952 __cxa_pure_virtual + 18

5 com.steinberg.cubase9v5 0x00000001114e8d12 0x10f77e000 + 30846226

6 com.steinberg.cubase9v5 0x000000011135500d 0x10f77e000 + 29192205

7 com.steinberg.cubase9v5 0x00000001113573af 0x10f77e000 + 29201327

8 com.apple.CoreFoundation 0x00007fff27fbfedc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12

9 com.apple.CoreFoundation 0x00007fff27fbfdaa _CFXRegistrationPost + 458

10 com.apple.CoreFoundation 0x00007fff27fbfae1 ___CFXNotificationPost_block_invoke + 225

11 com.apple.CoreFoundation 0x00007fff27f7d880 -[_CFXNotificationRegistrar findbjectbserver:enumerator:] + 1664

12 com.apple.CoreFoundation 0x00007fff27f7c9b7 _CFXNotificationPost + 599

13 com.apple.Foundation 0x00007fff2a08c8c7 -[NSNotificationCenter postNotificationNamebject:userInfo:] + 66

14 com.apple.AppKit 0x00007fff25668973 -[NSWindow becomeKeyWindow] + 1488

15 com.steinberg.cubase9v5 0x0000000111524f40 0x10f77e000 + 31092544

16 com.apple.AppKit 0x00007fff25667bcd -[NSWindow _changeKeyAndMainLimitedOK:] + 878

17 com.apple.AppKit 0x00007fff256e2ca8 -[NSWindow _orderOutAndCalcKeyWithCounter:stillVisible:docWindow:] + 1261

18 com.apple.AppKit 0x00007fff2566ac0c NSPerformVisuallyAtomicChange + 146

19 com.apple.AppKit 0x00007fff25e18833 -[NSWindow _doWindowOrderOutWithWithKeyCalc:forCounterrderingDone:docWindow:] + 85

20 com.apple.AppKit 0x00007fff25e19d26 -[NSWindow _reallyDoOrderWindowOutRelativeTo:findKey:forCounter:force:isModal:] + 446

21 com.apple.AppKit 0x00007fff256728ec -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 172

22 com.apple.AppKit 0x00007fff25671765 -[NSWindow _doOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 287

23 com.apple.AppKit 0x00007fff256715cb -[NSWindow orderWindow:relativeTo:] + 169

24 com.apple.AppKit 0x00007fff25e1740e -[NSWindow _finishClosingWindow] + 479

25 com.apple.AppKit 0x00007fff257b6ed8 -[NSWindow _close] + 378

26 com.steinberg.cubase9v5 0x0000000111520423 0x10f77e000 + 31073315

27 com.steinberg.cubase9v5 0x00000001115204de 0x10f77e000 + 31073502

28 com.steinberg.cubase9v5 0x000000011105661c 0x10f77e000 + 26052124

29 com.steinberg.cubase9v5 0x00000001114e2419 0x10f77e000 + 30819353

30 com.steinberg.cubase9v5 0x0000000111427e06 0x10f77e000 + 30055942

31 com.steinberg.cubase9v5 0x00000001112cfb4f 0x10f77e000 + 28646223

32 com.steinberg.cubase9v5 0x00000001112d020a 0x10f77e000 + 28647946

33 com.steinberg.cubase9v5 0x00000001112cfbff 0x10f77e000 + 28646399

34 com.steinberg.cubase9v5 0x000000010fb007e1 0x10f77e000 + 3680225

35 com.steinberg.cubase9v5 0x000000010fb00609 0x10f77e000 + 3679753

36 com.steinberg.cubase9v5 0x0000000110749c3e 0x10f77e000 + 16563262

37 com.steinberg.cubase9v5 0x00000001107445dc 0x10f77e000 + 16541148

38 com.steinberg.cubase9v5 0x0000000110743b2c 0x10f77e000 + 16538412

39 com.steinberg.cubase9v5 0x0000000110745c1b 0x10f77e000 + 16546843

40 com.steinberg.cubase9v5 0x0000000110741727 0x10f77e000 + 16529191

41 com.steinberg.cubase9v5 0x000000011075bcf7 0x10f77e000 + 16637175

42 com.steinberg.cubase9v5 0x00000001110f5293 0x10f77e000 + 26702483

43 com.steinberg.cubase9v5 0x00000001107597f0 0x10f77e000 + 16627696

44 com.steinberg.cubase9v5 0x0000000110754c8f 0x10f77e000 + 16608399

45 com.steinberg.cubase9v5 0x00000001107591bc 0x10f77e000 + 16626108

46 com.steinberg.cubase9v5 0x000000011073ea1c 0x10f77e000 + 16517660

47 com.steinberg.cubase9v5 0x000000011073c945 0x10f77e000 + 16509253

48 com.steinberg.cubase9v5 0x000000010fb0b4e8 0x10f77e000 + 3724520

49 com.steinberg.cubase9v5 0x000000010fb666dc 0x10f77e000 + 4097756

50 com.steinberg.cubase9v5 0x0000000110c9de40 0x10f77e000 + 22150720

51 com.steinberg.cubase9v5 0x0000000110d56cdb 0x10f77e000 + 22908123

52 com.steinberg.cubase9v5 0x0000000111281208 0x10f77e000 + 28324360

53 com.steinberg.cubase9v5 0x00000001104a3e39 0x10f77e000 + 13786681

54 com.steinberg.cubase9v5 0x000000011127defa 0x10f77e000 + 28311290

55 com.steinberg.cubase9v5 0x0000000110cc7fcf 0x10f77e000 + 22323151

56 com.steinberg.cubase9v5 0x0000000110c8d7fa 0x10f77e000 + 22083578

57 com.steinberg.cubase9v5 0x000000011128040e 0x10f77e000 + 28320782

58 com.steinberg.cubase9v5 0x00000001114eb25e 0x10f77e000 + 30855774

59 com.steinberg.cubase9v5 0x000000011126c4eb 0x10f77e000 + 28239083

60 com.steinberg.cubase9v5 0x00000001112c29b8 0x10f77e000 + 28592568

61 com.steinberg.cubase9v5 0x000000011126dd70 0x10f77e000 + 28245360

62 com.steinberg.cubase9v5 0x0000000111268ae5 0x10f77e000 + 28224229

63 com.steinberg.cubase9v5 0x00000001112dd715 0x10f77e000 + 28702485

64 com.steinberg.cubase9v5 0x00000001104e733a 0x10f77e000 + 14062394

65 com.steinberg.cubase9v5 0x000000011132d879 0x10f77e000 + 29030521

66 com.steinberg.cubase9v5 0x000000011152cbd3 0x10f77e000 + 31124435

67 com.apple.AppKit 0x00007fff25cdda43 -[NSApplication(NSResponder) sendAction:to:from:] + 312

68 com.steinberg.cubase9v5 0x000000011104c725 0x10f77e000 + 26011429

69 com.apple.AppKit 0x00007fff25772213 -[NSMenuItem _corePerformAction] + 323

70 com.apple.AppKit 0x00007fff25771f9b -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 114

71 com.apple.AppKit 0x00007fff25770dff -[NSMenu performKeyEquivalent:] + 363

72 com.apple.AppKit 0x00007fff25cdc6a9 routeKeyEquivalent + 884

73 com.apple.AppKit 0x00007fff25cd9ce0 -[NSApplication(NSEvent) sendEvent:] + 1096

74 com.steinberg.cubase9v5 0x000000011104c24f 0x10f77e000 + 26010191

75 com.apple.AppKit 0x00007fff2553a8b5 -[NSApplication run] + 812

76 com.steinberg.cubase9v5 0x00000001115049be 0x10f77e000 + 30960062

77 com.steinberg.cubase9v5 0x000000011132d13d 0x10f77e000 + 29028669

78 com.steinberg.cubase9v5 0x0000000111046690 0x10f77e000 + 25986704

79 com.steinberg.cubase9v5 0x000000011104b7fb 0x10f77e000 + 26007547

80 libdyld.dylib 0x00007fff4feba015 start + 1



Thread 1:: CRASH THREAD

0 libsystem_kernel.dylib 0x00007fff5000125e semaphore_timedwait_trap + 10

1 com.steinberg.cubase9v5 0x000000011106c1c2 0x10f77e000 + 26141122

2 com.steinberg.cubase9v5 0x000000011106cadc 0x10f77e000 + 26143452

3 com.steinberg.cubase9v5 0x00000001104ee23e 0x10f77e000 + 14090814

4 com.steinberg.cubase9v5 0x000000011106bdcf 0x10f77e000 + 26140111

5 libsystem_pthread.dylib 0x00007fff501d5ae0 _pthread_suspended_body + 229

Hey don't post these things here, send it to Steinberg or Apple. It's obviously software issue.

 

[zhy3213]

Todays new Mojave beta again has a new firmware. I think we are 2-3 weeks away from gold release because progress looks really good. Easily the best macOS ever and really makes Windows look backwards.

Would you test on the latest firmware? After all the status shared in this thread, I'm going to buy my stuff back now.

 

[user3887]

anyone trying to understand sample rate and how it might relate to or be causing the crackling issue
watch the first 15 minutes or so...of this

the answer is around 11 min45sec in...and onward
2 and 8...numbers 48 and 96 are divisible by...44 100 not so much
the sample rate/bit depth conversion was off somewhere in the firmware for the T2 chip possibly

sounds like the issue is resolved in new firmware now...and not far from an update

great news

can't wait

 

[AdamA9]

Apple has always advertised a couple of games on their PowerBook and then MacBook Pro sites starting with Unreal Tournament 2004.

In the case of the new 2018 models, the page is explicitly advertizing the eGPU and stating how much faster it is than the dGPU.

I've been using my 2013 for five years. I'd have stopped long ago if I could do the two things I've always done, listen to music via YouTube and game. It's a very simple, non-graphically intensive strategy game. It isn't Fortnite or anything of that sort. It's a glorified spreadsheet.

You absolutely cannot defend the poor performance of this MacBook right now. Sure, it might all be sorted with a software update, but the bottom line is it cannot handle two very simple tasks in this moment that my old laptop could.
[doublepost=1535440406][/doublepost]

Why so hostile over a simple comment? Maybe I miss-worded my comment, but I honestly have a hard time believing that his 2013 MBP can handle it better than his 2018. And if it is a software bug causing the issue, then report it to Apple and wait for them to release a fix. It may take time, but there are always bugs on new releases, and its part of being an early adopter of a product.

I'd have stopped using my 2013 years ago if it couldn't handle the same process. Playing a YouTube video, simple process. Playing a strategy game which is essentially a very complex spreadsheet, very simple. My old laptop could run these two quite easily and has done for years. I only changed because of the claims that the quad-core and 16GB RAM would allow me to do so much more than on my old machine.

Software, probably. But that doesn't detract from my current disappointment with this machine.