< Previous | Contents | Manuals Home | Boris FX | Next >
Re-Finding Files
When you open an existing SynthEyes .sni file, SynthEyes attempts to verify that all the files referenced by it still exist: the shot, alpha images, texture files, preview files, etc.
If a file doesn't exist, SynthEyes looks around to find it. If the filename has leading folders in common with the .sni file path when the .sni was saved, SynthEyes will use the current sni path to look for the file now. For example, /A/B/C/foo.sni had
/A/B/D/texture.jpg, now it is opened as /E/F/G/H/foo.sni, so SynthEyes will look for
/E/F/G/D/texture.jpg.
If it isn't found that way, SynthEyes will just look in the same folder as the .sni file, in case the files have been consolidated.
Then SynthEyes will look in any sub-folder of the .sni file’s folder.
If it still hasn't been found, SynthEyes will ask you to find it—if you have the preference in the FILE OPEN section turned on. Once you've re-found a file, SynthEyes will check that folder for any other missing files also.
The situation is a little more complex for files that get written, such as export file names and preview movie output, because the file may not have been written at all, and you may not have bothered to copy the file to the new location since it's a derived output.
So for output files, if they aren't found, but the path matching processing above was successful, SynthEyes will keep the new relative name without further ado.
Otherwise, it checks a preference to determine whether to simply clear the file name (so you'll have to set it when you get around to using it), put it into the same folder as the
.sni file (make sure that following this plan will never overwrite something useful), or ask you for a new file name immediately.
©2024 Boris FX, Inc. — UNOFFICIAL — Converted from original PDF.