Hi, I am on a Mac Studio M2 with latest Ventura. My NI installation has been working flawlessly, but today things started to get problematic (and i suspect it is related to the latest Native Access version i updated a few days ago).
My setup:
Mac Studio M2 Max
Sabrent USB3.2 (gen2) with Kingston Fury 2TB nvme (reads 800+/- mb/s) as storage for the kontakt libraries.
When I install libraries with Native Access (lets say i.ex several 100GBs in size) Native Access downloads and then install. Everything works as expected and is fine, but for some reason the Sabrent/nvme get VERY hot. I am scared the chassis and/or Nvme will fail.
As a workaround I change library location in preferences to a temporary old spinning disk storage I got. When the installation is done I close Native Access and move the downloaded content to the Sabrent Nvme. That move job is rather quickly done. The Nvme does not get hot at all. Absolutely no problems to move 100GB in one go. I then start Native Access and do the well known REPAIR/relocate and point to the new location. Everything is fine and works perfect.
This is not the case anymore. After the latest Native Access update, the same process described above still works, but the libraries say they need UPDATE. Expected would be they say "INSTALLED".
The only way I now can get to say "INSTALLED" is by avoiding to move/repair/relocate. This means there are no other solution than to install directly to the final destination.
Luckily I have a Flir Thermal imaging camera, and as you can see in the picture the Sabrent/nvme get VERY hot.
I always thought that nvme disks only get HOT if they do massively writes (like big data in longer periods). But in my case it seems that it heats up even if it is writing slow, but in long periods. This might be a design flaw from sabrent or kingston. I dont know, but I can live with that as long as i can move and relocate without having a false status (UPDATE and not INSTALLED). Here is a picture of my poor nvme disk:
I hope some NI devs can check into this issue?
Thank you so much for reading
HFK