Im always working on 1024 Samples and don't experience latency when recording MIDI unless I have the track routed to a group buss with plugins on. This gives a distorted playback which I can fix by toggling the Buffer Size in the Playback Engine. I have seen the CPU shoot once to 100% red and go back down. Memory Meter in Pro Tools is down from around 70% to 10%. Today Ive added 2 x 64 GB Samsung RAM modules (160 GBP total with the original 32 GB RAM). My current sample library is a Samsung 850 EVO SSD via USB 3, would I see a big improvement investing in an internal OWC PCIe SSD or even the Sonnet one (is there fan noise with the latter?) It takes a while, is this related to number of cores, or the read speed of the Mac HD or even memory related? How can I improve the Restoring Tracks Time of my Pro Tools Sessions. Going to try to keep it brief as Im still in my return period for the Mac Pro and need to troubleshoot Also on Monday Apple will have some news on their Arm Processor and new iMacs so looking forward to that :)ġ. Storage, depends on how much you need, what you need it for, and how many free PCIe slots you have?Ĭheers for the replies guys, enjoyed reading all your comments. When I bought mine a month ago I was supplied with Crucial/Micron memory but apparently it’s sometimes Samsung depending on availability. I got for RAM from VERY cheap but quality RAM, 5 year guarantee and 100 day returns. Whenever I use my MacBook Pro with VIs in Pro Tools the fans are ridiculously noisy! If you look at the single core benchmark of your MacBook Pro (I have the same one), it’s not a million miles away from the single core benchmark of a 16 core 7.1 Mac Pro. Having had my 16 core for a few weeks I’m inclined to agree with him. Since Pro Tools doesn’t spread plugins/VIs across multiple cores then there’s always going to be a balance between the number of cores and core speed. His take on it is that the 16 core is the sweet spot for PT and audio use and he could have tried to flog me something with more cores!Īpparently, it’s mostly number crunching scientific apps that are really optimised for very high core numbers and high core counts come at the expense of core speed. The business manager at my local Apple store is well versed in pro audio. If you have memory free make sure you have set disk cache to a size, not "normal", to accommodate all your session in memory (look at the disk cache meter). What problems do you want to solve? Session startup time? Plugin sample load times? Making better backups? Getting CPU errors now or expecting to run larger sessions (and you can't freeze tracks?). I'd focus my spend on what is important to improve things. and saldy even what the CPU meter means with hyperthreading enabled is really hard to make sense of), and whether that problem will be helped (or made worse) by adding more cores. And sadly CPU meter % is not that useful for knowing you *won't* have problems (if you were seeing high % usage now then that's a more useful predictor of issues. So I'm not sure advice from others is that helpful. If it's running OK why do you need to upgrade? 28 core scalability will be very dependent on your session/workload/plugins used. My sessions are virtual instrument heavy with lots of tracks (100 or more).Īt the moment I haven't upgraded the 32GB ram or SSD storage but will be doing so, do you guys recommend any (Ram is showing about 50% usage). With the 16 core, CPU is hovering around 25% to 30% - although an improvement, I would like to know your thoughts on upgrading to the 28 core? With my previous pro tools 2020 sessions on a 6 core MacBook Pro i9 2018, the CPU hovered around 50% max and I would get errors. Just got my new 16 core Mac Pro 2019 this week so I thought Id share my feedback:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |