Client applications can filter the types of media files and playlists that get synchronized. The <extensions> element contains the <library> and <playlists> elements, which list the extensions that media files and playlists must have to be synchronized. Mediastore files with unlisted extensions don't get synchronized.
Both of these contained elements are required, and must list all extensions supported for that content type. This is done by defining an <extension> element for each supported file extension, within the <library> or <playlists> element.
The contents of the <extensions> element are:
| Tag name | Attribute | Default | Description |
|---|---|---|---|
| <extensions>/<playlists> | Specifies which file extensions are used for playlists. For each extension you want to support, define a separate <extension> element. | ||
| <extensions>/<playlists> /<extension> | value | (none) | Names the extension of a playlist type to synchronize. Typically, the extension is a three- or four-letter abbreviation of the format, although longer extensions are accepted. The matching ignores case, so listing an extension of "m3u8" means playlists with the extension "M3U8" will also be synchronized. |
| <extensions>/<library> | Specifies which file extensions are used for media files. For each extension you want to support, define a separate <extension> element. | ||
| <extensions>/<library> /<extension> | value | (none) | Names the extension of a media file type to synchronize. Typically, the extension is a three- or four-letter abbreviation of the format, although longer extensions are accepted. The matching ignores case, so listing an extension of "mpeg4" in the configuration file means playlists with the extension "MPeg4" will also be synchronized. |
| ftype | (none) | Names the default media type associated with the file extension. Acceptable values are audio, video, and photo. The ftype may change during the metadata pass of synchronization. For example, a file with an "mp4" extension can be an audio or video file. The customer must configure the file type to either audio or video to be used when mm-sync intially parses the file's information during the files pass. However, the ftype may change during the subsequent metadata pass if it's determined that the actual file type differs from the specified default type. |
<extensions> <library> <extension value="png" ftype="photo" /> <extension value="jpg" ftype="photo" /> <extension value="jpeg" ftype="photo" /> <extension value="gif" ftype="photo" /> </library> </extensions>Only media files with one of these four listed extensions will have their metadata extracted and uploaded to the database.