One song has a ton of memory -no time to optimize (I think its the sampled horn section) but I was at 128 and 48,000 Hz thinking of moving to 160 48,0000 3.3 s don’t feel a difference and the CPU is not maxing to 98% -
does this make sense?
also where is the ultimate guide for MacBook Pro stability - the old ones references menus that don’t exist anymore on the new op system
I use 44.1k and 128
Ditto.
You mean 3.3 ms ?
But the options exist in the more recent OS also
WRT settings: I have mine set to 48KHZ and 256 samples (5.6 milliseconds). Mine is set to 48KHZ because that is the only rate my audio interface supports. What you choose should reflect the sample rates available on your interface. What interface are you using?
X
You mean milliseconds?
My view is if you are comfortable with latency (don’t really notice it or even get used to it), increase the buffer.
It’s sort of equivalent to getting a beefier cpu for free!
Yes haha
I have a motu4 and my settings last night seems to have some crackling - when I checked the cpu its was fine
Makes me thing the motu4 needs something other than the sample rate I set 48,000 and 3.3 ms
First, try different version of its drivers.
yeah… too quick on the draw that time
Every time I go back to my audio settings for latency - it seems that it didnt save and keeps going higher than the suggestions here. Any trick to getting it to save (opening a smaller gig file and then saving it there?)
The best is to change your audio settings on an empty gig file.
This is what I do. I hold Shift and start GP with nothing in it, make the adjustments and save.
Are you saying that the settings you choose (in your case for 3.3 ms you are using 48000 and buffer size 160), that those values don’t stick?
If so, that sounds like a disk access permission issue
By the way, for live performance I use 44100 and 128
I’m getting a bunch of crackking on my motu4 running rackspaes at 128 40k (whatever the suggested latency setting was)
It seems to go away a after a few chords - is that the computer catching up?
Not usual for a macOS system.
What are your computer specs? What version of macOS?
This sounds (no pun intended) that your computer is trying to pull in samples but not until you actually play the notes. Is this happening with any plugin or just certain ones?
I was getting this with Halion and a few others when I was running out of physical memory.
David and others pointed out it was because my Mac was using a swap file.
Always when I first went to a rackspace and played a plugin. After the first few notes there were no issues with that rack space.