Skip to content

Unassigned Shots

In the case any capture files couldn't be matched to a shot they will appear in this table. To help aid in figuring out the issue the parent folder and filename are shown, plus any metadata. There are a number of reasons a file may fail to match a shot.

Misconfigured Capture Pattern

If all the files in a session are unassigned it's likely the capture pattern doesn't match the folder structure. Double check that the preview in Session Settings looks like your session structure.

  • Double check that any counters are in the correct place
  • Look for any spaces that shouldn't be there
  • Ensure your capture files are RAW files

Misnamed File

One of the most useful, and common file naming schemes, is shooting into folders by shot name and including that name in the filename. This allows Capturebot to detect when files are in the wrong folder. For example consider the following file:

LC_SP25_F01_GSTU271_ScreeningRoom/LC_SP25_F01_GSTU267_FirstContact_0009.eip

In this case the file could have been moved to the wrong folder or was maybe shot into the wrong folder before being moved.

When using suffixes in your file naming, such as _Plate, Capturebot can detect errors there as well. If the suffix was applied twice, misspelled, or otherwise in the wrong place the file will not match.

Test Folder

In the case you're using a test folder, but forgot to set the name in the Session Settings, those files will possibly appear unassigned. Either add the test folder name or add the folder as a shot.