ID 230032 - Versioning doesn't work if the filename contains a timestamp that changes between versions (script name or written footage's name)

Follow
  1. The Foundry SANDBOX
  2. Bug Tracker
  3. Nuke

Problem summary
If the timestamp (here meaning the time that the file was created, not the timecode start of footage) exists in the footage or script 's (.nk) filename, then versioning won't pick up new versions of the same script/footage for other timestamps.
 
Internal acceptance criteria:
  1. timestamps should be ignored in all version searching code for all file types, including:
    1. .nk files
    2. .dpx files
    3. .mov files
    4. etc. etc.
  2. no extra denotation of timestamp is required i.e. similar to "V" we should not add some tag such as "T", "TS" or simialr to denote timestamp sections.
  3. the assumption is that timecode values will never appear in the filenames (see Juan for clarification).
  4. no error handling for situations where you have the same file at the same version with different timestamps, outside of what STUDIO already does for multiple duplicate version detection (again see Juan for clarification)
  5. filenames of the following format should work:
    chars_v001_####.ext
    chars_v001_timecode_####.ext
    \(string\)\([vV]d\+\)O_grs080_v001_2016-07-27_09:09:46_####.dpx
 
Customer reported version
nuke.n/a
 
Customer reported platform
n/a
 
Steps to reproduce
  1. Create V1 (at 09:09:46)
    1. Open nuke and create checkerboard
    2. Create write node and set write path to:
      /temp/26/O_grs080_v001_2016-07-27_09:09:46_####.dpx
      IMPORTANT: Notice the timestamp is 09:09:46 not 10:09:59
    3. Save script as:
      /temp/26/O_grs080_v001_2016-07-27_09:09:46.nk
  2. Create V2 (at 10:09:59)
    1. Modify checkerboard
    2. Change write node path to:
      /temp/26/O_grs080_v001_2016-07-27_10:09:59_####.dpx
      NOTE: ensure this write path versions up to 002
    3. Save script as new comp and save name as:
      /temp/26/O_grs080_v002_2016-07-27_10:09:59.nk
  3. Import the following script into nukestudio:
    /temp/26/O_grs080_v001_2016-07-27_09:09:46.nk
  4. Attempt to version up
    Result: no version found
 
Workaround
  1. In Nuke open script:
    /temp/26/O_grs080_v001_2016-07-27_09:09:46.nk
  2. modify checkerboard
  3. Change write path to:
    /temp/26/O_grs080_v001_####.dpx
  4. Save script as:
    /temp/26/O_grs080_v001.nk
  5. Open New NukeStudio project and import the following script:
    /temp/26/O_grs080_v001.nk
  6. Scan for versions
    Result: the versions with differing timestamp in the names and write paths will now pick up
 
Reproduced by support
OSX 10.11.3 NukeStudio 10.0v3, 9.0v1
 
Unable to repro on windows 8 as the script file name would not accept colons
 
Expected behaviour
versions to be picked up even though timestamp in name were different
 
Actual behaviour
versions were not being picked up as the change in timestamp caused the file path to differ

    We're sorry to hear that

    Please tell us why