Why does file search destroy my machine?

[IO Composer]

When I open a session and select for PT to search for missing files, the process renders PT to a wheezing, panting crawl. I have the fastest mac pro you can purchase right now with all SSDs and oodles of RAM. This is 2012. There is absolutely no reason in the world why a simple system search should be doing this.

Drives me crazy!

[albee1952]

Me too. I think its just the way that the search function hogs resources. Its pretty much the same on my PC, which is plenty powerful for everything else. Is it searching for stuff you need, or searching for stuff you deleted? If its the latter, either skip the search, or go into the regions bin("clips" bin?) and find anything that is in italics, and remove from the session.

[Top Jimmy]

Using the auto find and relink function has always been a real PITA. Figuring out how to do it manually and when to use relink by name and/or file id saves a helluva lotta time. I don't know why they never improved this but I don't think the process starts in the folders listed in the disk allocation. It probably starts crawling at the root of the first drive.

[FilterDecay]

The reason is because its a disk intensive task and so your bottle neck becomes the speed of the hard drive.

[edadema]

Originally Posted by FilterDecay

The reason is because its a disk intensive task and so your bottle neck becomes the speed of the hard drive.

That might be true but in just Pro Tools 10 it has been unbearable. It used to just make the session feel slow, But now it completely takes over the whole session. I just force quit. I then use the "copy and relink" function.

[FilterDecay]

I wonder if it has something to do with the new disk cache?

[IO Composer]

Originally Posted by edadema

That might be true but in just Pro Tools 10 it has been unbearable. It used to just make the session feel slow, But now it completely takes over the whole session. I just force quit. I then use the "copy and relink" function.

Come to think of it, it does seem to have gotten significantly worse in PT10.

[IO Composer]

Originally Posted by FilterDecay

The reason is because its a disk intensive task and so your bottle neck becomes the speed of the hard drive.

Well, I'm using SSDs, so if that were the case, I would think that it would be relatively fast. I'm not entirely sure that this is an accurate assessment.