Two issues one might be PT11 bug

[propower]

Issue 1)
With no tracks in record enable (just playback) why does the system usage (ProTools or Activity monitor) change when I go from low buffer to high? With the new PT11 architecture the playback buffer is auto and all I can change is the record buffer. But I don't have any tracks in record mode and the system usage still goes up a lot from lets say 512=35% of a quad core machine (full load is 400%) and 64=80% ???

Issue 2)
With two different machines PT11 gets into a state (mostly from changing buffers but it is not a repeatable process) where the CPU usage at 64 becomes double what I typically see (goes from the normal 80% to 160%). Stranger still, if I quit the session - the usage remains. Stock plugins - 11.0.2 and 10.8.5. I thought this was an anomaly on one machine but I have had it a couple of times now on a brand new late 2013 imac. A simple reboot of protools fixes it. The only thing I can think of is the USB2 hub so I am trying plugging the ilok straight into the imac. Once again --- am I the only one ...

System is:
imac i5 3.4GHz 8G ram - PT11.0.2 - OSX 10.8.5 - ilok2 in usb2 hub - HDN TB Omni+16x16

[RyanC]

I don't know about the 2nd issue, but the way the hybrid buffer works in 11 is the aux tracks are still on the small (record) buffer. So usage will go up when all those tracks are on 64 instead of 512.

On the 2nd issue, it seems to me that 11 isn't entirely ready for primetime yet. I see the same types of things, disabling hyperthreading (hackintosh here) has helped immensely with these same types of issues (I also get 9172s, and roadrunner meep meep sounds with it on). I'm afraid we aren't yet to a reasonably stable version of 11.

[propower]

I think I found the CPU usage issue! Revibe!!!!!!!

I love Revibe (used for many years as TDM). But for 96kHz/64buffer recording on a small session Revibe is literally 1/2 of the processor load I am seeing. I had to take it out of the plug in folder but once I did this - not one incidence of weird CPU going to 2X the normal usage (and it was occurring pretty frequently). I have to run this a couple of days before i am sure but I think this is it.

If the results hold true how do I "report" a bug to AVID??

[propower]

Nope - its not Revibe - Not Waves --

It's PT11.0.2 (haven't tested the prior PT11 version yet but will go there next).

I started a new thread in the PT11 Forum...
http://duc.avid.com/showthread.php?t=345632

UPDATE 10/12/13 - 12:43PM :
PT 10.3.7 - no issues
PT11.0.0 with 11.0 driver - 2 hours use - no issue

UPDATE 10/12/13 - 1:55PM :
PT 10.3.7 - no issues
PT11.0.0 with 11.0 driver - 3 hours use - no issue

I don't know whether it appeared in PT11.0.1 or .2 or in the 11.0.1 Driver but rolling back to initial release seems to solve this.
What will be the worst bugs to look out for if I stick on 11.0.0 for awhile?
Running 96/64 all day -

[propower]

OK - So I am getting this in PT11.0.0 as well...........

And on 10.8.4 !

-----------------------------
UPDATE 10/16/13 12:07

Confirmed on at least two other systems

http://duc.avid.com/showthread.php?t=345632&page=3