I think it helps but the error is still under such a broad umbrella. If so, it appears that somehow PT doesn't recover from the delay, failure etc., and doesn't realize that there is something amiss It's very possible that one of the plugins in one of the inactive tracks caused this initially, as they were open and I made them inactive. After it pukes the first error the session runs fine until closed.
For example, my Perception plugin can cause a 9171, 2, or 3 errors when starting the transport the first time when opening a session. I haven't removed app manager or cloud collaboration, however I don't startup app manager on either my PC or Mac. In my instance, where I see these wild CPU usage swings, it is plugin related where the plugs are loading some saved information, (even though I have M2 and SSDs). I don't recall having seen these spikes without a session open.
With the information you've provided my gut feel is that it is hardware accessing related and the CPU usage has to do with ProTools trying to access something/running something. It loses control of itself, and it looks like it loses track, or wastes cpu power in a weird loop. There is something fundamentally wrong with PT. I've submitted pics of this, as well as vid to avid on a ticket. I am running 12.5.2 now, but have had the same problem since 12.5 Most of the time I have to force it to close. If I choose to exit, PT will take at least a half hour to close the session, if it finishes at all. In the video, you'll see that no tracks are active, and I get the cpu error as soon as I hit play. I cannot isolate exactly what causes PT to get in this state, but when it does, you'll see that the CPU use goes to 100%, with all of the CPUs at 0%. The above video shows a state that I wind up in regularly with protools.
#Exhale problems with pro tools 12.7 not installed how to
Not sure how to imbed a youtube video here.
0 kommentar(er)
