- #Mac os x capitan pref setter delete recent items update#
- #Mac os x capitan pref setter delete recent items manual#
- #Mac os x capitan pref setter delete recent items pro#
- #Mac os x capitan pref setter delete recent items mac#
No playback is possible at all with a couple tracks armed and hyperthreading on. Still occasionally spikes but only to 14% instead of into the red. This doesn't not change when I turn hyper threading off.
#Mac os x capitan pref setter delete recent items pro#
New experiment: When using a completely clean/stock plug-in folder (zero third party plug-ins) Pro Tools idles at 6% without any session loaded at all (64 buffer).
#Mac os x capitan pref setter delete recent items update#
My issues pre-date the OSX 10.13.4 update so though they may be related, its just one extra degree harder to troubleshoot. I have yet to really stress test but in the last couple hours, it has behaved very well. My computer had some kind of complete melt-down yesterday after a security update and in the interest of troubleshooting, I restored my High Sierra 10.13.4 backup onto a HFS+ formatted SSD instead of APFS (High Sierra installer forces the hard disk format change). I just tried this and the opening/closing of windows have no effect on my dsp. Wow! That is not my issues at all but the spikes looks identical when they happen.
#Mac os x capitan pref setter delete recent items mac#
Here's the issue, 96k and 128 buffer, mac 5,1 12 core with 64ram: EDIT: just saw you're on cheesegraters- maybe just try 1g. If my guess is right about a conflict with IO operations and audio, you could try a much simpler setup, just have a mac mini serve sessions over TB for a direct connection, or just try a 1G setup. So far the only errors I got with the server was when EUcontrol crashed and the system needed to be rebooted. I was able to work on my workstation (7980xe hack also with a solarflare SFP+ 10G nic) under 10.13.4, but the errors were annoying and not related to actual CPU load. I got it setup in anticipation for a move to a new multi-room studio (open any session in any room), right now it's only serving one workstation- but it seems the added benefit is a drastic reduction (so far elimination) of any of the CPU errors. I'm getting read and write speeds around 900MB/s either on the server or over the network. The drives are in Raid 10 (dual 6 + 2 hot spares). In my case I have a z370 hack with 14 3TB HGST drives and a solarflare SFP+ 10G NIC into a 10G TP link switch (the switch actually has 12 of the newer RJ45 10g ports as well as 4 SFP+ 10G ports). You mean you load your protools sessions from the server via 10G connection ?Yeah. Pro Tools 2018.1, OSX 10.13.3, 2 x 3.46 GHz 6-Core Intel Xeon, AMD Radeon R9, 32 GB 1333 MHz DDR3, all OWC SSD hard drives, Antelope Orion (USB/MADI), SSL Madiextreme, Antelope Satori, ATC SCM300a, Genelec 8050b.What about using another DAW? Pro Tools 2018.1, OSX 10.13.3, 2 x 3.46 GHz 6-Core Intel Xeon, AMD Radeon R9, 32 GB 1333 MHz DDR3, all OWC SSD hard drives, Antelope Orion (USB/MADI), SSL Madiextreme, Antelope Satori, ATC SCM300a, Genelec 8050b.
The computer isn't breaking a sweat and neither is pro tools but it still stops dead every couple of minutes. I am set up in a multi room facility and we have a couple 2009 Mac Pro's we heavily modified. Selecting Pro Tools Aggregate as my audio engine Un-installing all the audio drivers/software for every piece of hardware (Orion, Satori, SSl Madiextreme, etc)Ĭompletely clean plug-in folder (all up to date with no third party software) That gave me 45 minutes of the best pro tools experience I have ever had.
#Mac os x capitan pref setter delete recent items manual#
The only thing that helped was a complete manual un-install and then re-install of pro tools (including prefs). Cant even play through a song without it stopping! Opened a support ticket but nothing they suggested has changed anything.
0 kommentar(er)
