Shabba Khe
It’s not really an issue since I know I’m due for an upgraded laptop soon, but I was curious about something I noticed regarding RAM usage across my Macs.
My main workhorse is an M1 Mac (Tahoe) with 16GB of RAM, and I also have two older Intel Macs (Catalina and Sequoia) with the same amount of RAM. I understand that Stems 2.0 — and by extension the lyrics editor — can’t be used in a live setting on the Intel machines. However, when using the BPM editor with Fluid Beat Detection, the Intel Macs maintain steady RAM usage that doesn’t exceed 2GB, while the M1 quickly spikes to using all available RAM and then starts going into swap because of it.
Overall, performance is still fine, but the difference in RAM usage between the machines is quite significant, and I was hoping to understand why that is.
My main workhorse is an M1 Mac (Tahoe) with 16GB of RAM, and I also have two older Intel Macs (Catalina and Sequoia) with the same amount of RAM. I understand that Stems 2.0 — and by extension the lyrics editor — can’t be used in a live setting on the Intel machines. However, when using the BPM editor with Fluid Beat Detection, the Intel Macs maintain steady RAM usage that doesn’t exceed 2GB, while the M1 quickly spikes to using all available RAM and then starts going into swap because of it.
Overall, performance is still fine, but the difference in RAM usage between the machines is quite significant, and I was hoping to understand why that is.
Mensajes 10 hours ago
Adion
To speed up the fluid detection, VDJ will use the NPU, which can use more ram. It should not continue to go up though, do you mean it continues to rise the more songs you analyze, or it stabilizes?
On my M4 mac it stabilizes around 6GB memory use, no matter how many songs I do the fluid detection on.
On my M4 mac it stabilizes around 6GB memory use, no matter how many songs I do the fluid detection on.
Mensajes 8 hours ago
Shabba Khe
Adion wrote :
On my M4 mac it stabilizes around 6GB memory use, no matter how many songs I do the fluid detection on.
On my M4 mac it stabilizes around 6GB memory use, no matter how many songs I do the fluid detection on.
In normal gigging with stems 2.0, lyrics detection etc., it would lurk in that area, but when i click on the BPM Editor and then go on to 'Fluid' it spikes and will go to swap memory. The only time it don't go to swap is if i disable stems completely and have no other apps open, however it will show a significant raise in RAM.
Lastly I hv my analysis set to analyze on view of new tracks and when new tracks are added and are being analyzed, this is what happens - see pic below
Mensajes 6 hours ago