User manual

The dCine can utilise external sources for media and playlists for eCinema and DCI content. The

<MediaStore> option is used to configure these data sources. When configured, the dCine can list

“Local” and “dStore” lists or media and playlists. If you select content which is located on a

remote location, it will be ingested into the dCine or DCI player when added to a playlist.

An example of the <MediaStore> configuration follows;

<Local>

<Playlist>../playlist/</Playlist>

<Media>../media/</Media>

<DCP>../DCIPlayer/</DCP>

</Local>

<Store>

<Config>ftp://dstore:dstore@10.30.1.3/config.xml</Config>

<Playlist>ftp://dstore:dstore@10.30.1.3/storage/playlist/</Playlist>

<Media>ftp://dstore:dstore@10.30.1.3/storage/media/</Media>

<DCP>ftp://dstore:dstore@10.30.1.3/storage/dcp/</DCP>

<Keys>ftp://dstore:dstore@10.30.1.3/storage/keys/</Keys>

</Store>

</MediaStore>

The dCine MediaStore configuration can point at a dStore Library server or another dCine player.

Four different storage types are set. These are set in the <Local> and <Store> options. The

<Local> option defines where the location of the files are relative to the MediaPlayer.exe

executable. For example, for <Playlist>, the value of “../playlist/” refers to the parent

directory (bin) of where Mediaplayer.exe resides. Ie, directory called “playlsit” in the

same directory as “bin”. This would typically be “V:\channel\playlist”

The different types of media sources are:

 <Playlist> : a repository of playlists.

 <Media> : a repository of media files.

 <DCP> : a repository of DCP's. This would need to point to a dStore system as the dCine

does not play DCP (but will come a in future release)

 <Keys> : With DCP's comes the need for keys. This would also usually point to the dStore

and its cache of KDM's for the content it has.

<Remote> defines the remote location of the files applicable to the <Playlist>, <Media>,

<DCP> and <Keys> files This option specifies a FTP location using the standard URL syntax used