Tagcache and disk access

[nigel]

Hey all. Just wondering if I would benefit from using tagcache instead of the standard directory browser. I browse by artist->album 99% of the time (which is exactly how I have the directory structure laid out). I'm just curious if using tagcache will save some disk access time when browsing? Currently every time I hit a directory the disk spins up and loads the current directory. It does this every time I change directories.

Obviously with tagcache there is a large cost upfront to build the DB, but after that it all gets loaded into memory, right? Do you have to completely rebuild the DB everytime you add files to the device?

I guess I'm just trying to minimize disk spinups and prolong the life of the drive. Thoughts or preferences, anyone?

Thanks, Rockbox is completely sick!

[Jon_]

No taggcatch won't elimitate that disk access.

[Llorean]

Actually either Dircache enabled in general while file browsing, or TagCache loaded into memory will eliminate that access.

[nigel]

Directory cache... perfect, I can't believe I hadn't found that earlier. Does it cache the entire directory structure during boot? It appears to be that way, eliminating the need to force a reload if the contents changes.

Thanks!

[Llorean]

Yep, the directory cache even runs in the background after booting, so that added files can be reindexed without really increasing future boot times, just the first one to initialize it.

[Jon_]

i have the directory cache enabled but my ipod still access the ipod's hdd for directory listings

[Llorean]

First question: Does it do this in an official build?
Second Question: If it does do this in an official build, does the debug menu tell you that DirCache is actually ready and working?