Why do waveform views constantly need re-drawing in the Digibase browser?

[EricWillhelm]

Even though I've long since calculated waveforms on the entire drive...and even though I've visited the same files over and over again...why do the waveform views of sound files keep disappearing in the Digibase browser?

Not that it's the biggest problem, since re-drawing them occurs quickly enough when I select a file. But still, I thought the idea was that once you calculated waveforms for a file, they'd stick around. As it is, I have to keep getting them to re-draw so I can see which file is what.

Anyone?

I'm going to love it if the answer is "trash your prefs".

[DigiTechSupt]

Are these files being used in the session and possibly being altered in some way that a new waveform would have to be calculated for them?

[EricWillhelm]

Nope! I copy everything into sessions and leave the originals untouched. Also, it's not just the ones I use in my sessions, but huge swaths of them in my libraries. Some waveforms stay, some go. It always varies. Very strange.

[Big Crouton]

Is this just happening when you're importing tracks into new sessions, or does it happen when opening old sessions too?

I could be entirely wrong here, but I think that the WaveCache found in every session folder is a file containing all your waveform overviews. Because each session has it's own WaveCache file, Pro Tools has to calculate the overviews for the audio files for every new session you bring them into.

Like I said though, this is just a hunch.

[EricWillhelm]

This has nothing to do with waveforms in a session, or importing tracks or any other session data. This is just while working with the DigiBase browser from within one/any session. This browser keeps a constant cache of data on the root of your hard drive, in the Digidesign Databases folder (if I read correctly). I'm referring to the waveform views that represent files you're looking for within the browser.