Avid indexing on each launch.

[James Mckenna]

Hi Scott,

That indicates to me that there’s a mod date change in/on the host-named MXF folder. If the folder date is newer than the date of the databases, Avid thinks there’s indexing to be done. This could also be a problem of an improper exit of the application after writing, where Avid isn’t allowed to clean up the database. Next time you exit Avid, check the mod time/date on the pmr and mdb files, and compare to the upper level folder mod time/date. If the folder date is newer, you’ll likely get an index.

This can also happen if another Avid is deleting media from your subdirectory. This is why we recommend project-based volumes when possible, to limit the amount of housekeeping that can impact your databases.

Since you’re in emulation mode (I hope), you can rename that directory to anything you want and still have access to the media (i.e. from hostname.1 to hostnamexx.1). Only the databases in the folder that has your specific Avid’s host name will be rebuilt. When you write media again to that volume, the Avid will generate a new folder. This is all Unity/Isis functionality as well, not specific to Facilis.

Jim McKenna
Facilis Technology
978-562-7022 x101

[Scott Davis]

Thanks, James. Renaming the Folders did the trick.

Scott Davis

[Aren Hansen]

Hi,
We have a terrablock as well. Every time my AVID crashes, which unfortunately is twice a day, my AVID has to index one of the terrablock volumes. It takes about 15 min. From talking to some of the other editors, they have the same experience.
Any ideas appreciated. Thanks,
Aren