When sharing media files in a network drive, you may need to mount it using different mount paths on different computers.
For example, a same network drive is typically mounted as a drive letter on Windows (D:\, E:\,..), but on MacOS it will be mounted under /Volumes, and it can be anywhere else on linux.
If that happens, when loading a Mistika timeline in other computer that is using different mount paths then Mistika will not find the original paths to the media, as they don't exist in the new computer.
To solve this, first time that Mistika does not find a media file it will ask you to "Relink" the file to the new locations as seen from the local computer, also offering a button to "remember" the new locations (from the local computer perspective).
In this way (if this button is active), next time that you load any other media files that have the same path translation needs Mistika will try to do the relink process automatically, and if the media is found no question will be asked to the user.
For more details (for system administration purposes) this is the file containing the path translation equivalences:
This is just a text file (using .json syntax) that is local to each computer, so you can also edit this file manually, for example to prepare a network infrastructure to be ready to find any media files without user intervention.
But if you do that we strongly recommend to use Mistika to relink some example files before doing manual changes to it, so you can start with an example to properly understand the syntax.
Please note that the pathsTranslator.json file is only for media files. If you also want to share the Mistika user settings (presets, render predefined paths, display filters, etc) then what you need to change is the Mistika "shared" folder, which is described in this other article
Another different case is the render path. If a render job (.rnd file) is created in a different computer than the render computer then the render path needs to be identical on both computers, otherwise the Mistika render will not find it.
- if they are unix computers (Mac, Linux) they should have the same mount path for the network path (or at least a resolvable link to it).
- if they are windows the network drive should be mounted in the same drive letter on both windows.
- Finally, if it is a mix of windows and unix it can get a bit complicated but it is perfectly solvable. In Windows there are different ways to access a network drive as a directory, someway emulating what unix systems do. One way could be by using the Windows "mklink" command, but there are others. However this matter is out of the scope of Mistika documentation. For more advanced uses a recommended 3rd party render manager for rendering across a network is Smedge, you can find more information here.