![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#21
|
|||
|
|||
![]() Quote:
I have a partition for booting into incase something happens to my system, I can boot into the other and clone back easily. I've been running sessions and samples off externals without issue. So for me, I didn't see any need to run intenally. As well, with the 990s in a TB5 enclosure running 7000 MiBs I can build one if needed. And as you said if the internal goes, then you are dead in the water. I'd rather put the stress on something I can easily replace. Currently, the Mac hardware will no recognize v5 of the nvme's. Only v4. Not sure if that is something firmware will address or if a newer version of TB5 hardware has to be built into newer models. I don't understand the need for RAID anything anymore either. I know it is native in the Mac now, but haven't really seen a need. Question. What else is would be kernal device drivers and how would I know if it was?
__________________
Mac Mini M4 Pro 12core, 24gig RAM, PT 2024.10.2/2025.6 Ultimate, OSX 15.4.1. OCTO 8 card, Apollo 8 Quad, SSL Alpha 8 Almost every plugin ![]() |
#22
|
|||
|
|||
![]()
I hear you, but I'm not worried per se about write wear on the internal SSDs for our typical uses, but I'm maybe more worried about catastrophic NAND or controller failure or maybe more likely a software/firmware bug vs wear on the NAND. In my day job sometimes touches on SSD with things like transactional databases etc. that can be an issue with just hammering the hell a drive. But that's so far removed from the peaceful lay-back use we make of them in audio apps.
The thing that does worry me with uses in pro audio, (and by no means addressed to you, I know you are on top of lots of stuff here) is more just basic house keeping. Keeping firmware up to date/avoiding known potential data loss issues. Folks having good backups and a plan on how to recover from failures, and being aware of corner cases like once I've mentioned here, or begin aware that incremental updates on macOS clones are no longer bootable etc. And hopefully folks are archiving to quality HDDs, SSDs are not long term archival storage, especially with drives powered off and data that is not begin accessed. We live in magical times having access to such just stunningly fast storage (and yes even low cost stunningly fast if not from Apple... but I still will recommend Apple internal SSDs to lots of folks to consider). BTW I'd love to hear any more experience you have with TB5 enclosures and SSDs. I need to move a bunch of stuff over there soon. But have multiple systems stuck on Intel Macs for complex (non DAW) reasons. Quote:
$ kextstat | grep -v com.apple kext drivers might be installed for some high-performance devices (e.g. some exotic networking interfaces) or just old devices, networking, exotic I/O cards etc. Hopefully most audio stuff has migrated to use Driver Kit (user space) audio drivers. Avid HD Drivers are still kext, and who knows when this really might be a problem if Apple one day blocks all third party kext drivers. |
#23
|
|||
|
|||
![]()
Hey Darryl
Thanks for your replies - but you’ve completely derailed my post. Can we keep it to discussing ram use requirements in the Mac Studio please.
__________________
Pro Tools 2024.3.0|Perpetual • MTRX Studio • HDX1 • Sync-X • S3 • Dock • Mac Mini 2018 - 3.2GHz i7 6-core macOS 13.6 • RAM 64GB DDR4 GPU AMD 6900XT 16GB • Monitor LG 32UL950-W |
#24
|
|||
|
|||
![]() Quote:
If you are doing this work today the best guide for how much memory you need on these macs is how much memory you are using in your sessions today. Then factor in some more for ever increasing memory use. I've posted in the past on DUC how minimum memory needs can be non-obvious but how it can be measured if you want to do some testing. If nothing else what memory you have in your systems today is useful info, but might be a significant overestimate (modern OSes like macOS will tend to just fill up memory if there is no pressure on it to reduce memory use) and for large sessions disk caching it all may be overkill and use lots of memory unnecessarily (I think as BScout was warning about as well). And please don't listen to folks saying the Apple Silicon macs need less memory that Intel macs. |
#25
|
|||
|
|||
![]()
I think I'm around a year and a half now with my 64GB. Haven't regretted my decision.
Step up to 96GB if you like spending money and it makes you feel better. I tend to not run other hungry programs whilst I'm using PT - others might want or need to.
__________________
~Will |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Elastic videos for post prod | Brent_Sydney | Post - Surround - Video | 1 | 11-18-2008 09:34 PM |
Music prod V. Post prod monitoring - does a chasm exsist? | postprosound | Post - Surround - Video | 13 | 05-31-2007 12:24 PM |
Post prod Mix Tracking Sheets | elnonsense | Post - Surround - Video | 3 | 09-08-2006 04:40 PM |
Levels on Pro Tools in Post Prod. | DannyVanSpreuwel | Tips & Tricks | 9 | 12-18-2000 06:16 PM |
basic post-prod questions | anders | Tips & Tricks | 2 | 01-03-2000 09:18 PM |