13” seems fine tho.Too many quirks with the current generation in my opinion. I would wait if you can. Perhaps even pick up a used older MacBook Pro if you're itching to get used to the OS. You can then sell it later and will take a much smaller loss.
13” seems fine tho.
And dual vs quad jump was significant- doubt sunny cove will be such a big difference
What audio issues are you talking about? FWIW I have a 13" MBP 2018 and its been perfect.The 13" still has the audio issue, keyboard issue, and KP issues doesn't it?
I'm not sure how many units are affected of course.
What audio issues are you talking about? FWIW I have a 13" MBP 2018 and its been perfect.
The 13" still has the audio issue, keyboard issue, and KP issues doesn't it?
I'm not sure how many units are affected of course.
If you can wait for Sunny Cove, then wait, I would wait 100 percent. It is gonna be awesome, I am sure. i7 Sunny Cove is probably gonna be a beast.
How exactly is it gonna be awesome?
Kp/audio is t2 related.
So...
Unless apple admits all t2 computer are crap and does a 2017-2018 recall, 2019 wont fix that.
They had 2 years to fix the butterfly keyboard, 6 years to fix screen coating, and they didnt
Single core performance, multicore performance, lower power consumption, integrated graphics...everything is gonna see significant improvement with 10nm node. How exactly it is not gonna be awesome?
How exactly is it gonna be awesome?
Nah, i was talking about the TB anyway, just mentioning that sunny cove wont fix those unless apple admits t2 was a nuke. But yes you’re correct.When you mentioned the 13" I assumed you were talking about the TB, but now I think you were talking about the nTB? In which case, I agree. This is appears to be a T2 issue and will affect the 13" TB but not the 13" nTB.
Because the biggest bump on mbps was 2011 dualcore to quadcore switch - and it happend on the same die size.Single core performance, multicore performance, lower power consumption, integrated graphics...everything is gonna see significant bump with 10nm node. How exactly it is not gonna be awesome?
Nah, i was talking about the TB anyway, just mentioning that sunny cove wont fix those unless apple admits t2 was a nuke. But yes you’re correct.
I don’t think sunny cove will be a “night&day” moment for apple. Impossible. (I’m not having buyers remorse, still waiting for my 13” and mini2018 so return period hasnt even begun yet)
[doublepost=1545066885][/doublepost]
Because the biggest bump on mbps was 2011 dualcore to quadcore switch - and it happend on the same die size.
Its not going to be as awesome as 2017->2018 core count bump which literally doubled the 13” performance and made the i5 13” outperform last years 15” i7
This one:
https://forums.macrumors.com/threads/macbook-pro-2018-speakers-crackling.2128234/
I know it's not huge if you're not recording or whatever, but under those circumstances it seems like a pretty significant issue.
I am not experience this issue and I record with my 2018 MBP. I think we are seeing a magnification effect from the forums.
I’ll surely report when i recieve mine.Agreed. Unless Sunny Cove comes with a markedly improved T3, it'll be a "no-buy" for me too I expect. I like the 2018 13". I think it's got great potential, I'm just not that keen on rolling the dice when my current system is working great. I've been tempted though.
I’ll surely report when i recieve mine.
The i9 i had was a lemon, but i figured i’ll give it another shot with a different configuration. If it’s a dud, i’m returning both mini and 13” and buying a second hand 2015.
Dude, 4PB of physical RAM... nuff said
How exactly is it gonna be awesome?
At apple prices that’s... 90million $Dude, 4PB of physical RAM... nuff said
Yeah that's completely possible.
Have you looked for the issue? Or you're just saying you haven't come across it?
No, no. On the i9 i experienced it after 15 min of continuous playback on a simple 2track logic project.I looked through my logs for the issue and there is no occurrence of the KP. I also do not experience dropouts in the recordings or playbacks.
I may be that I have only recorded and processed about 25 hours worth of sound. Perhaps when I get more recordings I will experience the issue. But, so far so good.