Hi community
I have a question after resolving, with the help of Avid support, send to playback issues from cloud UX at one of our customers which proved to be caused by media indexer performance issues. These were mostly resolved with the info found here
https://avid.secure.force.com/pkb/articles/en_US/Troubleshooting/Recommended-changes-for-Media-Indexer-2020-x-and-2021-x
One other issue found by support from the indexer logs was the presence of offline AMA media. So I checked and indeed this customer hasn’t been cleaning out a lot of, what I believe are, obsolete AMA assets. But the Media Indexer and therefor Interplay Access only has information on the presence of the spaaf and aaf files inside the SPAAF workspace, not the actual linked media. So Interplay access can’t tell me which spaaf +aaf files still point to valid media locations.
I have asked the same question to support but I thought I might ask here as well. Is there any way to determine which spaaf+aaf files do and do not link to valid storage locations in an Interplay environment? Maybe from the Media indexer logs. But how to isolate the AMA logs in those?
Having to check the AAF files in each folder on the SPAAF workspace to verify if they still link to a valid location unc path will be a pain. Maybe Avid or somebody outside of Avid (makers of MDV) ever thought of writing a small utility that can do this cross check and/or maybe including that info in the Media indexer web page? That utility could also be used on a standalone media composer setup or media composer with Nexis only. In that configuration the content of the xml file on the individual media composer systems at C:\Users\Public\Documents\Avid Media Composer\AMA Management\Managed AMA Media Folders.xml might be of help although the drive letter mounted locations differ from system to system and have no relation to workspace names in a unc path.
Thanks