Processor usage doubles after bounce and commit

Processor usage doubles after bounce and commit

---

I have been having an issue since upgrading to OS X 10.11.1 and 12.3 with CPU usage doubling after an offline bounce (WAV or MP3) and after track commit (audio or instrument). I have trashed Prefs using the PT Prefs tool from the site, repaired permissions (Onyx), tried a fresh session with minimal tracks and had the same out come. Everything works great until right at the end of commit or bounce, there is a slight pause at the end of rendering (about a second or two) then the CPU usage nearly doubles and stays there. This doesn't make it hang,
as I've tried to continue playing after the spike. Only resolution is to quit the session and restart.

Has any one else seen this or have any ideas of what to check next?

See screen shots of before and after.

Attached Thumbnails

   

__________________
stock Mac Pro 5,1 2010 12-core 2.66/48GB/ATI HD5870/OSX-10.11.1
mod. Mac Pro 5,1 2009 6-core 3.46/32GB/NVIDIA GT-120/OSX-10.10.5
I/O: Yamaha 01v96i, M-Audio 2626, M-Audio Octane
Plugs: Avid, Waves, Blue Cat, Eventide, Sonnox, Massey, Softube, AD2, SSD4, ReValver 4, Line 6
DAW: PT 12.3.1 vanilla, Cubase 8x, Mixbus
CS: Command 8

---

Last edited by msponie; Today at 07:30 PM. Reason: No Sig

This entry passed through the Full-Text RSS service - if this is your content and you're reading it on someone else's site, please read the FAQ at http://ift.tt/jcXqJW.

Processor usage doubles after bounce and commit