Weird VI CPU spike workaround

[pgripp]

I started getting crazy CPU spiking in 12.5, and figured out that it was always caused by first instrument track in my session. Duplicating the track and making the original track inactive solves it. It happens with all of my VIs, no matter which I use on that first track. I've attached two pics showing the system usage and the tracks. A you can see, with the first track enabled the CPU usage is more and the spike is high.

Has anyone else experienced this?


---------------

Mac Pro 3.33 6core, macOS 10.12.1, Prismsound Titan, Pro tools 12.6

[albee1952]

Interesting In your Preferences settings, what do you have selected as the Default Thru Instrument on the MIDI tab?

[risey]

See my post here for a temp solution http://duc.avid.com/showthread.php?t=386402

[amagras]

Originally Posted by risey

See my post here for a temp solution http://duc.avid.com/showthread.php?t=386402

Will it work for Mac? The OP says he's on Mac.

[pgripp]

Hey Albee1952 - that's it!

I have "first selected MIDI track" as the Default Midi Thru in the preferences. If I select non-midi track, the midi thru goes to the first instrument track (causing the cpu hit). If I select an instrument track with no VI on it, the spike cpu goes back down.

Thanks! It's still annoying, but at least it makes more sense.

[dterry]

I have had random jumps in total processing usage (PT's System meter - no correlation to task manager's cpu usage that I can see). Depending on the average load, the jump may be from 5% to 50%, or 15% to 90% - no rhyme or reason, but it only happens in my scoring template, and only with Eucon enabled (so far - tried removing VEPro instances, and that didn't help - the Eucon fix could be a coincidence).

This may be something different, or these could all be part of the same issue with midi, VIs and PT 12.5.x. At the least, my system usage meter looks exactly like the OP's - same kind of random peaking. (I am on 12.5.2, PC, Windows 8.1).

I'll try the midi thru and core0 suggestions tomorrow and report back. Would be very interesting if one of these helps.

I've been talking with Avid support about this for a few weeks now, so support and dev are aware of the problem.

[rossi68]

Same problem here, and I will try this workaround. Great!
I also hava a 12 core cpu, and also find most activity in core 6.

[dterry]

Turning off Core0 in task manager for ProTools.exe affinity seems to have solved the cpu spiking for me.

Big thanks to user risey for that!