PT 12 running slow after drum edit.

[Toddhq]

I'm having trouble with PT12 running sluggish after I do large drum edits with multiple fades etc. PT is slow to zoom in and out and is also slow when I move and edit clips/regions etc. I can fix the problem by consolidating everything but I prefer not to do this. My CPU load is on around 4% and my current running version of PT10 doesn't have the same problem, neither have older versions of PT on this same PC.

Are there new preferences I need to change in PT12 to change this?

[albee1952]

Help Us Help You
Post a Sandra report on the PC and what you are using as an interface

[Kris75]

Are you on Windows?

[lukeyy]

same problem here - not sure if its the drum editing but I noticed lately that protools is getting super slow (meters are not displaying correctly etc.) and cpu usage is around 8%! weird..
I´m on 12.3.1 HD Native on a mac mini

[mesaone]

Does this behavior improve when you turn on or increase disk cache?

[Thenewexhibit]

I have had strange behavior as well regarding drum editing, beat detective specifically. Whenever I select a decent chunk of audio, I use the analyze portion of beat detective to catch all of the transients. Then, I zoom in fairly close, and then scroll horizontally in a quick fashion to see if the markers are all in the right locations, or if I need to add/subtract any. The problem with this is when I scroll through like I've done since pro tools 8, the scrolling sticks and has to play catch up quite often, and lags. This may sound trivial, but for me, I can't stress how major of a problem that is because it plays tricks on my eyes and makes me second guess myself, causing me to work a lot slower than I do.

I know it is Avid version specific too. I tried 12.4 on yosemite, and the problem is there. Revert back to mavericks with pro tools 11.3.2, and there is no problem. Uninstall 11.3.2, and install pro tools 12.4; problem presents itself.

It's only happening in 12. It's easy to do. Basically:

select a protion of grouped audio; 8 bars perhaps.
Command + E to separate those regions.
Zoom in on the audio and scroll horizontally back and forth wherever you want fairly fast with the mouse using shift and the scroll wheel.
Open beat detective and analyze audio to bring up transient markers.
Scroll again and see if things get sticky and hung up.
Then, close beat detective and see if it goes away (which for me, it does).
Reopen beat detective (audio should already be analyzed, and the markers should reappear).
Try scrolling again.

For me, this sticky behavior only happens when the analyze portion of beat detective presenting the transient markers is being used. Sounds like a lot of steps, but it really only takes a minute or two to actually test. Also, quartz debug makes no difference in this matter at all.

I'm on a MBPr 15" mid 2014 with OSX 10.10.5.

If anybody else could test this out and let me know their findings, that would be rad, and very much appreciated.

I also made a quicktime video of this if anybody is interested in seeing what I'm talking about. I'm not exactly sure how to upload it though.

[lukeyy]

Originally Posted by mesaone

Does this behavior improve when you turn on or increase disk cache?

for me it stays the same.. 1024 or 128

[mesaone]

Originally Posted by lukeyy

for me it stays the same.. 1024 or 128

I think we're not seeing eye-to-eye here. I'm talking about disk cache, which reserves RAM to load session audio into. It is measured in GB. I think you're talking about buffer size, which is different - it's measured in samples.

[lukeyy]

actually changing both doesnt affect the slowing down...

[take77]

You can try selecting and removing unused regions in the clip bin drop down menu Select options. Right click the highlighted clips and choose CLEAR not delete.
All audio files will remain intact in the audio folder.

Then create a blank session>Import Session Data>Open original session file>Choose "copy from source media" in Media Options>click on Match Tracks under Destination>Select & Import all existing Session Data>Save as new session*.

Sometimes that helps reset session snappiness.
Worth a try. Just restored snappiness to a slow session today doing both.
Think it's because clip data accumulates and session files become fragmented. Re-importing & copying everything creates freshly written files.
The slow one of the bunch is back to being readily responsive.

*Timeline Data may take some time to process as indicated by the red TLD status icon. Will turn green once the task manager has completed processing. Close session, re-open and give it a test.