ggg
Interplay® | Media Indexer
Patches for Version 3.6 – Technical Overview
Installation Requirements........................................................................................................................ 1
Limitations ............................................................................................................................................... 1
Fixed in Interplay Media Indexer v3.6.2.28499 ....................................................................................... 2
Important Information
Avid recommends that you read all the information in this ReadMe file thoroughly before installing or using
any new software release.
Installation Requirements
Patch v3.6.2.28499 contains full installers for PC and Mac. The installers have the following requirements:
•
•
This patch is recommended to be installed on all Media Indexer v3.6.x servers and clients.
Note: If editor clients are at MI v3.4.3 or MI v3.5 because of editor dependencies, do not update the
clients to MI v3.6.2. If clients are at MI v3.6.x, then upgrade to this patch build.
•
The internal database schema version has not changed from MI version v3.6.1 but did partially change
from MI version v3.6.0. Upgrading from v3.6.0 or v3.6.1 will not require a reindex of the configured
storage locations but only a rescan.
•
For installation instructions, see the Interplay Media Indexer v3.6.2 Installation Guide.
Limitations
The following limitations are present in this patch release:
•
•
There is limited support for files with Unicode characters in MI v3.6.0, v3.6.1, and v3.6.2. This will be
addressed in a future version.
o The Media Status shown in Access 3.6.x or in Media Composer 8.6.x might show Offline for
media files with Unicode character in the name
In some situations MI might not display the folders for AMA media and their metadata files (SPAAF) in
the Web UI FI Storage Browse area
o This might result into Media Composer 8.6.x to see AMA media as offline
Fixed in Interplay Media Indexer v3.6.2.28499
IPMI-5665
MongoDB Statistics


The Media Indexer web interface Statistics Page now contains additional details for the connected
MongoDB.
The additional details include information on the collections in that database and their sizing.
IPMI-5819
FI Reindex Functionality Fixed

Fixed issue about Reindex functionality that led to situations where media files did not get reindexed.
IPMI-5805
Removal of FI Metadata when Files Are Deleted from File System

Fixed issue about deleting files and folders from the Media Indexer database when files or folders on
the file system are removed.
IPMI-5779
FI Storage Browse – Sorting Folders


The FI Browse Storage page in the Media Indexer web interface now lists folders in sorted order.
This was not the case in earlier v3.6.x versions of Media Indexer.
IPMI-5782
Improved Failure Log Message


The log message when media file processing failed some prerequisites has more details.
The log message now indicates the file under question to improve trouble shooting.
IPMI-5781
Configuration Options for Clean Folder Background Task











Cleaning the folder tree stored in the database in a background task is now configurable.
Configuration allows you to disable cleaning or define the interval at which the cleaning should recur.
By default, cleaning the folder tree is triggered every 10 minutes, but will be skipped if there was
indexing activity during the past 30 seconds.
Configuration is done via amqservices.properties file. Find the relevant section of that file listed
below.
#########################################################################
#---------------------FolderTreeRepository ------------------------#
#This flag is used in CleanFoldersManager implementation.
#It defines frequency of checking cleaning folder tree and its time unit
folderTreeRepository.cleanup.run=true
folderTreeRepository.cleanup.delay=10
folderTreeRepository.cleanup.timeUnit=MINUTES
IPMI-5826
Performance Enhancements for Clean Folder Background Task



Cleaning the folder tree stored in the database has been improved with regards to consumed memory
and CPU footprint.
Two options for determining if a certain folder can be removed from the database are available; the
default is to find any item in the folder under question rather than counting the number of items in
that folder.
The default option provides the best performance for CPU and memory consumption.
The option can be configured via the jini.config file when the default appears to be less optimal.

com.avid.mi.mdstorage.service.BasicFiStorageService

{



static useCount= Boolean.TRUE;
}

IPMI-5196
CPU Usage No Longer Listed in MI Statistics


CPU usage is no longer exposed / listed in MI web interface on the Statistics page.
The item was removed because the value no longer is an accurate representation of CPU usage.
Note: There is a separate page provided by MI to expose CPU, memory, and additional information
over time. The page is usually accessible via http://localhost:8888/mi/javamelody
IPMI-5673
Fixed Issue - Subfolder Representation in Database was Duplicated

When a subfolder of some indexed location was copied on the file system, the database
representation for that subfolder appeared to be duplicated as seen in the MI web interface Storage
Browse page. This was fixed.
IPMI-5414
Fixed Issue – Folder Tree was Missing Folder Names with Unmatched Parenthesis

Folder names with unmatched open-close parenthesis did not show in the folder tree that is displayed
on the FI Storage Browse MI Web UI page. This was fixed.
IPMI-5672
Fixed Issue – Folder Tree was Missing a Folder once the Folder was Renamed on File System

After a folder in some indexed location had been renamed, the folder was no longer showing in the
folder tree on the FI Storage Browse MI Web UI page. The folder was neither showing with the new
nor with the old name. This was fixed.
IPMI-5468
Fixed Issue – Inconsistent Database Index Name Assumptions Led to Duplicated Indexes



MI uses a database schema version check to verify the availability and the schema of the database as
well as existing and required indexes. Sometimes this operation created indexes with incorrect
names.
This issue led to indexes being recreated every time the database becomes available, ending up with
more indexes than needed and spending additional CPU power on indexing efforts that is not
required.
The described problem has been fixed.
IPMI-5400
Allowing a Local MI to Run on a Server OS




MI no longer requires that a Local MI must run on a non-server OS such as the OS on a Media
Composer system. This allows you to run a local MI on a Windows Server OS as would be the case for
virtualized Cloud offerings.
MI now allows you to connect to an MI Server instance independent from the operating system that
this MI runs on, as long as this MI is not a member of a NOMI (as will be the case when this MI is
supposed to run as a server MI).
Vice versa, MI allows an MI instance to join a NOMI (and as such function as an MI Server) as long as it
is not already connected to an MI Server.
These limitations are pointed out on the MI Web UI configuration page when attempting to violate
the new requirement (running as a NOMI instance and connecting to a server at the same time)
IPMI-5941
Improving Indexing Performance by Use of Buffered I/O


MI now uses buffered i/o when reading files via metadata-extractor to populate the information in
the Media Indexer MongoDB.
The performance gain related to reading the metadata from the file is expected to reach up to 50 %
compared to earlier MI 3.6.x versions.
IPMI-5928
Improving Display Performance on MI Web UI Configuration Page

MI Web UI for Local Media Indexer, when connected to an MI Server that is currently not reachable,
no longer waits for calls to that remote Server MI to time out and as a result the configuration page
renders much faster.