I'm surprised that no one has mentioned this before (or if this just happens to me), but I tested AudioUtopia's PT 12.5 on multiple systems, and every time the session got bigger, the project was slower, right-clicking clips would take couple of seconds, etc. Has anyone else experienced this?

 

It's called latency.....
A normal thing in low specs machines....

 

Pro Tools uses more resources than most other DAWs. When your machine starts to struggle it introduces quite a bit
of latency as Vader said. You could try to reduce the CPU load by disabling a few plugins and elastic audio or
commiting or freezing tracks as well as aux tracks. Has nothing to do with the Audioutopia release.

 

No, the problem isn't my machine, which is i7 workstation with Samsung Evo SSD drive for OS and WD Caviar Black for samples and recordings. Also, if you read the post more thoroughly, you would've noticed that I wrote "it happens on multiple systems"
Moreover, the problem doesn't happen on PT 12.3 by AudioUtopia. Try to fill the session up with tracks and notice how right clicking clips takes couple of seconds to do.

 

I reverted to 12.3.I had issues on 12.5 similar to this one and making pro tools to crash with some 3d party plugins.12.3 is more stable...for me (windows 10)

 

Well, they added new features in 12.5 and as far as I remember it was a major update. Could also be related to that.
I don't know 12.3 or 12.5 well enough to confirm that really is the reason.

 

This is how Pro Tools behaves when you have too many clips. After editing, chopping up drums etc., make sure to consolidate your changes into one clip and remove unused ones. You can save the previous state as a backup, then clean up your project for speed.

 

Really? No shit!
I was about to post the same as Billy, because I thought it was a problem with the AudioUTOPIA release.
That's really the reason why it lags so much?
Well... there is a reason why I still use Samplitude as my main DAW.

 

Last edited: Jul 16, 2017

It behaves the same way on the legit non-HD version I own. The quickest fix is CTRL+SHIFT+U (select unused) > CTRL+SHIFT+B (remove selected from project - not from disk!) then save as a new project file. This way you have a copy to go back to in case you need to pick a previous take, but you do get the full speed of a nice clean session. I also consolidate (ALT+SHIFT+3) and remove original cuts when editing drums as aligning those to the grid in a multitrack recording tends to create tons of clips that really slow things down. Periodically I just commit to what I've already done - apply fades then consolidate and remove the original cuts. Keeps your projects nice and snappy!

 

Where can one find this release? - I never saw it on the sister site.

 

Thanks a lot Qrchack for this explanation, it really helps.
I do a lot of editing, only for classical music (just editing, not mixing or mastering). As you may know editing in classical music, since everything is recorded together, copy and paste is the way to go. Tons of material (sometimes more than 10 hours) and select the best parts of that. For this reason I can't use ProTools as a main DAW, for the simple fact that it does not join objects with automatic crossfades, you have to do it manually. This may be a simple feature, but it saves a lot of time, specially in classical music.
The Recording Studio responsable for mixing and mastering uses ProTools, that is why I need it. Sometimes I correct some last things directly on ProTools before I give it to them.
The current project I'm working on is a six mono audio tracks (24bit, 96khz). Almost 10 hours of material at the beginning and the editing part at the end, with a lot of cutting (everything in the same session). Since this is the first time I work on such a big project, I was very surprised that ProTools behaved so slow... (same session with Samplitude just flies!!) I will try you suggestion and do some cleaning in the session, let's see what happens.
Greetings!

 

Last edited: Jul 17, 2017

Big Thanks friend !

 

Last edited by a moderator: Jul 17, 2017

I am about to install AudioUTOPiA 12.5. I am going to do a test to see if this version can run along side a legit copy of 12. If not, no harm no foul. AudioUTOPiA version is a god send simply for the fact that HD has so many features that the standard version does not as far as tracks alone (256) I have never had a problem with protools being sluggish. I have always consolidated or froze tracks to free up memory. Committing effects to tracks as well and deactivating them helps as well.

I wonder if there will ever be a update from AudioUTOPiA...

 

Please remove any links to downloads .
They are not allowed here...

 

Yeah, funny that we can talk about AudioUTOPIA's release but we can't post the link which is on the sister site of this forum.
Well, I don't make the rules here. Link removed.

 

Fades are really quick in Pro Tools, and there are tons of ways to do them. D/G will add a fade-in/fade-out from where your selection is at, F will do a crossfade at selection. If there are several clips in your selection, it will crossfade them individually. Splitting clips is simple as well - just hit B. Spend some time to learn your tools, Pro Tools is great for quick edits. In fact, this is one hell of a reason why it's so popular

 

I appreciate very much your explanation Qrchack, but that is not the way I like to work (as I said I do only classical music). Crossfade must come automatically when you join two different clips, as many other DAWs do (Reaper, Samplitude, Sequoia, Mixcraft to name a few), that is for me the best way to work. I'm sure Pro Tools is great for many things, so they say, but not my favorite cup of tea. Sorry.
Greetings!

 

Last edited: Jul 19, 2017

The usual way to do editing in Pro Tools is to do your editing without worrying about fades then select everything, hit F and have crossfades added automatically.

 

I noticed that sometimes grabbing a VCA laggs horrible.
However when using my Faderport it is smooth...

 

Anyone noticed that the whole Protools GUI freeze wehen you turn a knob or move the GUI of an opened Plugin ?