Launching a session when content in Media Player playlists that is served across a network is offline or missing can result in lengthy delays, even making it seem as if TriCaster has ‘hung’.
Normally (i.e., when dealing with local content) the operating quickly reports file status to TriCaster, and missing media is ghosted in the playlist bin. This process is more complicated when dealing with networked media.
For example, if a volume is missing the operating system will automatically scan the network in an attempt to resolve the path. After some time, the operating system gives up, and the file is marked as inaccessible. Unfortunately, though, this process now iterates for as many files as you have added to the playlist.
Fortunately, the potential delay involved during this process can be easily bypassed. By default, the system uses a full UNC (“Universal Naming Convention”) path for all network connected resources (e.g., “\\myserver\myfolder\myfile.mov). Use the Windows “Map a Network Drive” feature to give the server (or folder) where your remote media is located a drive letter (e.g, “M:\”, or “M:\myfolder\”). This results in much quicker path resolution, and effectively eliminates the problem.
For more information please download the entire document at new.tk/rt-m