in GP5, using the Streaming Audio File Player, I have 44 drum loops in it. I use the “loop” option, and after some loops, the player becomes more an more irresponsive, so clicks are almost not working anymore, and the UI is refreshed less than once a second. If I close it and reopen it, it’s back working again, until I loop some more.
(MacOS Sonoma 14.4.1).
Good idea, but no, it’s the internal SSD of a Mac Studio, and it’s very efficient. By the way, the sound is working correctly, and the other plugins too, it’s just that player itself slows down a lot and become irresponsive.
I created a brand new gig, only added the player with one file (8s long, 2.1MB aiff file), in loop mode, and I get the same issue after 1 or 2 loops. In the activity monitor of MacOS, the CPU goes from 15% when not playing to 50% when playing the first time to more than 100% after 2 loops.
The audio file is on the local drive. Everything else works well on the Mac.
Here is an example gig, with simply the player and its audio file (I did not even put a button to open the player, so you need to open it from the wiring view).
Btw, I did not find how GP5 is referencing the file. The Gig’s XML is obfuscated… gp files.zip (1.3 MB)
There may be some memory leak with the project I sent, when keeping the UI open, the memory usage grows (in MacOS monitoring tool) steadily (rates varies from 2-10 MB per 5s). But it probably does not relate to the irresponsive issue.
Closing the Player’s windows gives back the CPU. After reopening, it’s responsive for some loops, then again becomes irresponsive, with CPU up to 100%.
I have read about issues with GPU’s in DAWs. In one case, the person disabled his Invidia GPU and just used his CPU (integrated) for graphics. I don’t know whether that is something you might want to explore (and least for testing purposes).