That would be my thought as well
Is there a way to optimize the Mac from the ram issue? Note - this Mac is equipped with 18g of ram (yes you read that right 18 don’t ask it’s how it came from Apple)
For this reason I put 64 GB in my Win10 laptop. And during the last days I did a bit of programming the idea I mentioned 4 days ago in order to split the CPU intensive plugins among the 6 Cores of my CPU automatically. It seems to work, no crackling and and CPU load is quiet low at bufferlength 96.
But one still open issue is to replace the physical MIDI inputs in all my old gig files by some virtual ones. Is there an easy way how to do this?
I checked GP Scripting functions (version 4) and found this “ReplacePlugin” function but no Idea how to apply this to all my MIDI input blocks in a rackspace or in a gig file. Any tips how use it? Or or this the wrong thread for this question?
18 GB ram seems very low. Maybe a bit less so for a Mac than Windows, but still seems very low.
I would research whether you can add more ram. I suspect that is your problem.
Im a Win user but google says there is this Activity Monitor app showing “Memory Pressure” which shows how efficiently your memory is serving your processing needs including free memory, swap rate and file cached memory. May be this helps?
Wow - that’s frustrating - The ram is not upgradeable on my MacBook - and I bought it specifically for GP. All the reviews indicated that it should fly on all software.
If you were a guitarist, it would probably be fine. But, if you use sampled instruments, the ram limtation becomes a factor.
There are bunch of techniques to deal with ram constraints: Predictive Loading, use physically modeled sound sources instead of (ram heavy) sampled ones, purging samples in Kontakt, not re-using sample based sounds (instead put them in the Global Rackspace or reuse local rackspaces using widgets to bypass, etc.)
Maybe look at Pianoteq, Swam instruments, Modo Bass, modeled synths (most Arturia and Cherry Audio).
Which reviews? And with what application bias?
I don’t remember - it’s been a while but back during my research I went for a newer Mac with fast processing and there was a lot of chatter on how the silicon chips were able to handle lots of music and audio production with 16 being enough.
I’m working on removing sound paint and sample heavy programs
I think with pianoteq and arturia and cherry audio I’ll get what I need.
Future Macs I’ll go 32
16 should be enough for many purposes - however if your sample based plugins don’t stream directly from disk, you can end up with an issue.
Note however that Gig Performer has a mode called Predictive Loading where it only loads a few rackspaces (or songs) at a time and unloads not needed as you move forward in your setlist.
However before you go there, you should create a gigfile with just the rackspace where you were hearing noise and see if you hear noise when that’s the ONLY plugin