What is worth writing about is that El Capitan, through the magic of Metal or otherwise, finally fixed a bunch of graphics performance issues I had with Yosemite, with the immediately noticeable result that my 5-year-old MacBook Pro no longer slowed to a crawl when I plugged in an external display – and my home Mac mini, which predates it by another magnitude of obsolescence, is now perfectly at ease driving two full HD displays. The new Safari is pretty snappy, too, and as such remains my default browser for everything that doesn’t require Flash – which, fortunately, is most of what I visit daily. And, like before, I was largely unfazed by the tweaks to Mail.app, the window management features (Split View is nice, but I’ve been using Moom for so long to tile my windows that it’s not worth writing home about) or the usual barrelful of minutiae. Like Yosemite, it’s an iterative upgrade with a little more polish. I’ve been running the GM for a couple of weeks, and aside from a few tussles with MenuMeters (which I had to rebuild from source based on this port) and a few, erm… productivity apps that required an update to stop crashing randomly, I have had no relevant issues with it so far other than the usual development adjustments that come with a new OS. Clicking on the icon, indicates the current network (i.e., wifi or Ethernet). If you go into the preferences for MenuMeters it is possible to add a network icon to the OSX menu bar. If that happens to you, just remove that directory and restart it (worked for me so far). There is Menumeters: menumeters for OSX 10.10 and earlier The port of menumeters for OSX 10.11 onwards. Update: Apparently there’s a serious bug in Mail.app that makes it consume gigabytes of RAM due to the log files in ~/Library/Containers//Data/Library/Logs/Mail/. I have no idea what Steve would say, but I cannot help but wonder… If after some observations you notice that there's always 1 GB or more of RAM still free when using Logic, then you don't need to go to 16 GB.Also known as the silliest name for an operating system ever. MenuMetersis a superb tool for those who use their computers heavily. You should install a utility like MenuMeters to keep an eye on that. MenuMeters 1.9.1 seems to interfere with OS X Server 5 based Time Machine Service causing when run on server (OS X El Capitan 10.11.1 / Sever 5.0.4): making client time machine backups VERY slow. But then again, I have no idea how much RAM your overloading projects typically use. Though it won't hurt to get more RAM, I don't think it 'll be your most significant improvement. Having said all that, if you still have money left after buying an external disk (preferably FireWire or Thunderbolt, as USB is less suitable for heavy streaming it's fine for backups though), I'd also consider upgrading your internal disk to SSD, it does make a significant difference in snappyness of your MBP. You could go for an SSD, but a 7200 RPM disk will do just fine. If you'd like to help out drop me an email to the address on the contact page. Because Intel Macs are rare right now I need more beta testers. Usage: If you just want to use it, please go to. I expect that a final release will be available in the coming weeks. My fork of MenuMeters for El Capitan, Sierra, High Sierra, Mojave, Catalina and Big Sur. If, however, it is your disk that is overloading, the solution would be to get an external disk to store your Project Folders on this means that all audio files (including those from frozen tracks) that are playing in your session no longer have to be streamed from the already OS-traffic-heavy system disk. MenuMeters is now in beta testing with Intel Mac support. If you've used every method (freezing tracks, not selecting an instrument track, send tracks to one auxed reverb in stead of using individual insert reverbs, setting all your audio tracks to No Input) and it still happens, well, that's the limit, and you may have to "redesign" the project so it looses its' "heavyweights". Important to realize is that a CPU overload can be a bottom line: the limit of a given CPU. Remedy: select an audio- or aux- or any frozen track during playback, just NOT an instrument track. If it is the CPU crapping out, there are a few things to consider: are you using too many CPU heavy plugins perhaps? A Spacedesigner on half or all tracks? Or several instances of a CPUhogging software instrument? Also, if you have a software instrument track selected, the instrument on it goes into "live mode", meaning it is ready to immediately respond to input notes, meaning it is using CPU even when nothing is input to it. You can only run plugins from the actual startup disk.Īlso, it pays to investigate if your SO-message is from a CPU or a Disk overload (they require different solutions), for that, doubleclick your CPU/disk IO meter in the transport so it opens in a floating window and observe what it does right before a system overload happens.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |