Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Why does new Haswell Macbook have double the Latency!?!?!?

Everyone please call Apple to report this. The new Macbook is giving me, and others, double the latency in Logic and Ableton. This is not acceptable and hopefully Apple can fix. I don't think it's Mavericks because I haven't heard people reporting the same issue with a simple OS upgrade. Anyone else have any info or fixes please advise. Same buffer settings and sample rate and Logic reports an extra 10 ms of latency on the new Macbook I just saved up for.


See these threads for more info...


http://www.gearslutz.com/board/music-computers/880625-2013-retina-macbook-weird- issue.html#post9568985


https://forum.ableton.com/viewtopic.php?f=1&t=198974&start=0

Logic Pro X, OS X Mavericks (10.9)

Posted on Nov 6, 2013 11:28 AM

Reply
32 replies

Nov 15, 2013 6:27 PM in response to Pancenter

Please note:


This is the same HipDeeJay who;


Bitterly complained about and to Apple when Flash was being a huge resource hog a few years back.. and was overheating his girlfriends MacBook... but he didn't think about contacting Adobe....


Even more so, bitterly complained about the fact that 8 months after he bought a Macbook, Apple lowered the prices and felt he should get some kind of incentive or compensation....


Claims his mind was boggled when he couldn't account for 10GB that would come and go from his system HD (He calmed down once it was explained there are things called virtual memory files)


and finally, while trying to work out why a set of speakers were noisy and hissing... managed to...

accidentally tapped the tip of the external monitor's mini display port cable to a the wrong port of the MBP and immediately I heard a loud POP through my studio monitors and massive staticy hiss that was very loud.


Long story short.. it appears he had blown his onboard Audio.... unsurprisingly enough..


Maybe these 'unfortunate' incidents are why he truly believes his input latency is 0.0ms?


(Sorry Hip... but honestly, claiming someone like Blueberry is clueless/childlike/confused about such a subject.. is kinda dumb.. and so you sort of asked for this..)

Nov 15, 2013 7:23 PM in response to The Art Of Sound

The Art Of Sound wrote:


(Sorry Hip... but honestly, claiming someone like Blueberry is clueless/childlike/confused about such a subject.. is kinda dumb.. and so you sort of asked for this..)


Exactly, in fact it's so far off the mark that it's beyond nonsense. BB has supplied some of the best and most accurate answers in this forum.


What is Hip, tell me tell me if you think you know.

-Tower of Power

Nov 15, 2013 7:43 PM in response to The Art Of Sound

LOL it's nice to know you have nothing better to do then go back and read all my posts from the past 10 YEARS. Also taking everything I said out of context, good job. Don't see what your point is. As you can see from my screenshot 0.0ms INPUT LATENCY is real, believe it or not. I'm not making it up.


Blueberry really does not know what he's talking about regarding this specific subject. I don't care what else he may or may not know, in this case he is severely wrong. Nothing you say will change that. You clearly don't know anything about this subject either, judging by your responses.


We're talking about a specific issue here that is well documented. You can pull straws all you want, you're off topic and nothing you say is of any value. Do you even own this machine? Didn't think so. Do you even know what input latency is? Didn't think so either. Go troll somewhere else, I could care less what you have to say. Better yet, go pretend to be helpful somewhere else, like all your other posts. I got better things to do than argue with you over something you clearly know nothing about.


Have a good day 🙂

Nov 15, 2013 8:41 PM in response to hipdeejay

As you can see from my screenshot 0.0ms INPUT LATENCY is real, believe it or not. I'm not making it up.


The method being used to measure input latency is obviously incorrect... I don't doubt that is what it is showing you but it is incorrect.


Thats not to say there isn't an issue with Haswell based Macs.. but it isn't what you are being led to believe based on those incorrect figures.

Nov 15, 2013 8:41 PM in response to hipdeejay

Actually, I don't think you understand what Input Latency is. Not trying to start a war or offend.


I just checked my MacPro with RME audio "Roundtrip Latency" at 128 sample buffers is 7.3ms (that's both Input and Output latency), at 256 buffers it's 13.1ms Roundtrip latency.


Input latency comes into play when recording audio.


The measurement that counts is what you see in Logic's Preferences/Audio as the Roundtrip measurement.


What are you measuring the latency with.. I don't recognize the application. (Ableton?)


On a side note, and I've mentioned this before, recent Apple operating systems are less friendly to real-time applications, I don't doubt for a bit that Mavericks has increased latency in some situations.

Nov 15, 2013 9:03 PM in response to The Art Of Sound

There's no "method" being used. Those are the CORRECT latency settings. So now you know more then the computer right? My computer is wrong but you're right. Ok sure buddy.


That's just the audio preferences in Ableton. It's not wrong, trust me. I take Ableton's word over yours any day. I already wasted enough time, your thinking is incorrect. Deal with it.


If you have no INPUT, i.e. no INTERNAL MICROPHONE SELECTED in this case, there is no input to have a latency. Why is this so hard to understand? You're trying to make it into something it's not. None of this is even important, the INPUT LATENCY is not the problem. You're all off topic. Get over it, my god.


So sick of arguing with people who have no idea what they're talking about.

Nov 15, 2013 9:22 PM in response to hipdeejay

Ignoring the silly ranting from Hip going on....


Pancenter,


You are correct...



As an aside... Over in one of the Dev Plugin forums there is much talk about certain plugins being hard hit by the extra overheads found in LPX... Kontakt for example..seems to be particularly 'stressed' by LPX under certain circumstances. I've noticed the same sluggish behavior with Diva... on occasion.


There is something odd going on too.... CPU load flucuates quite wildly at times using the same plugins/project... Sometimes it is fine and other times it overloads for a while only to settle back down later for no apparent reason...and this has become so since the last couple of updates.. It reminds me of the issue when Spotlight/mdworker would get itself 'stuck' in a loop' slowing the system down to a crawl..but its not that this time...


Anyway, not sure why this is occuring but it is happening on all my different LPX rigs here.. and has been reported but without any response so far....

Nov 15, 2013 9:37 PM in response to The Art Of Sound

hipdeejay wrote:


the INPUT LATENCY is not the problem. You're all off topic. Get over it, my god.

You were the one who mentioned it as relevant in your first post.



If you have no INPUT, i.e. no INTERNAL MICROPHONE SELECTED in this case, there is no input to have a latency.


So your argument is that you've made an accurate measurment of something that isn't there?

Dec 5, 2013 2:52 AM in response to dolomick

Hi


Being a user of music computer for more than 15 years I can confirm that most of the modern DAWs can have physical inputs deactivated thus the Input Latency can equal 0. Period.


The higher latency using Core Audio on the new rMBP and iPad air is an issue that has been now identified and recognized by enough users on other forums to make it real and official to me.


This is an unacceptable issue to me has even Microsoft has resolved this problem since Windows 7. So Apple is going back with native audio performance equivalent of Windows XP ???


I was about to buy the higher end 15" rMBP, because on paper, it looks amazing.


After few researches, it seems to have overheating and performance freezing issues. Fans going hyper fast and loud (a big issue in home studios where you have improved and engineerd the acoustics of your mixing space room). And now a latency equivalent of the 2003 Windows XP multimedia audio driver !


I know new machines always have to be fine tuned as users discover issues , but if this latency thing cannot be fixed by a software or firmware update, it makes too many letdowns for a computer that price ... I'll be sadly obliged to buy another brand than Apple...


If the problem is hardware side and cannot be fixed, they better change the audio chipset ASAP no matter how complicated that might be, because they might just loose all the pro audio users there (including me), the word is spreading fast ...

Why does new Haswell Macbook have double the Latency!?!?!?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.