4 ms·
The 'garbled microphone input' seems a bit of a red herring, it's likely that the thermal throttling is kicking in which is causing the audio recording app to g
by arcticbull 11y ago
The 'garbled microphone input' seems a bit of a red herring, it's likely that the thermal throttling is kicking in which is causing the audio recording app to get slowed to below real time making it sound like garbled.
I've had the laptop for about a month now, and yes, Hangouts will bring it to its knees, but for some reason Hangouts will bring just about any laptop to its knees.
Battery life is as advertised, you do get 8-10 hours of web browsing, and shockingly, about 6-7 hours doing some light development work with Xcode. I've definitely had times when battery life seemed a lot worse than it should have been but that has been solved with a quick trip to Activity Monitor to see what's eating the CPU.
Spotlight Web Content was a common culprit so I turned off Spotlight Suggestions (also Bookmarks and History) and that made a noticeable difference.
I've only had heat come up as an issue once; turns out it needs to be on a hard surface when you're doing something CPU intensive. Who'd have guessed?
- wutbrodo 11y ago>yes, Hangouts will bring it to its knees, but for some reason Hangouts will bring just about any laptop to its knees. I've got a couple year old x1 carbon 13", and it handles hangouts fine, more or less everyday. That's with the (annoyingly high) cpu usage of a couple hundred tabs open as well. If a tiny couple pound ultrabook van easily handle hangouts, I highly doubt that hangouts would be difficult on most laptops (let alone "just about any").
- rasz_pl 11y ago>Hangouts will bring just about any laptop to its knees. because Google insist on forcing their own codec and encodes in pure software bypassing hardware h264 encoder block on cpu/gpu.
- justizin 11y agoThey insist on forcing, for HD as someone noted earlier, an open and non-patent-encumbered codec. h.264 is great, but it is an Apple-centric solution.
- kitsunesoba 11y agoThe way I see it, H.264 is more about practicality than anything else. Hardware acceleration for it is everywhere. VP9 is great, but until there's hardware acceleration available for it, it's a bad idea to use the codec on devices where high CPU usage is undesirable.
- sangnoir 11y agoCodec & hardware acceleration is a chicken-and-egg problem: who would include h/w acceleration for a codec that isn't being used?
- kitsunesoba 11y agoIt wasn't a problem when H.264 was new. There were devices that had H.264 decoding support well before it was popular with users; I remember iPod videos sporting support for it back when DivX/XviD and flv was the norm. Eventually because devices had support for it, people switched over to H.264 and the older standards died out.
- sangnoir 11y ago> It wasn't a problem when H.264 was new. There were devices that had H.264 decoding support well before it was popular with users; You might be happy to know that it's not a problem for WebM either! There are[1] devices that have VP8 decoding support right now. Just not all devices (just as not all devices had H.264 hardware decoders when it was new.) Obviously the iPod would supported H264 since Apple were a member of the consortium pushing it (MPEG-LA)[2]. Similarly, ARM Chromebooks support VP8 because Google is behind it. Several chip-makers have promised support: Intel is taking a wait and see attitude [1] and might support it in the future 1. https://en.wikipedia.org/wiki/WebM#Hardware https://en.wikipedia.org/wiki/WebM#Hardware 2. https://en.wikipedia.org/wiki/MPEG_LA#H.264.2FMPEG-4_AVC_licensors https://en.wikipedia.org/wiki/MPEG_LA#H.264.2FMPEG-4_AVC_lic...