Here is an example of using pattern browsing and openclip:
*Preamble:
- My job has a root directory called ‘my_special_job’
- Next I have a ‘shots’ directory
- In ‘shots’ is shot_0010, shot_0020, shot_0030, etc
- In each shot directory I have ‘batch_setups’, ‘media’ & ‘openclip’
- Let’s ignore ‘batch_setups’ - it’s only for flame.
- In ‘media’ is ‘renders’ and ‘sources’.
- In ‘openclip’ is ‘segment_clips’ and ‘output_clips’.
In order to use pattern browsing to view multiple ‘nuke_comp’ sequences without drilling into subdirectories I can park in my job root directory and use:
option A:
shots/{name}/media/renders/{shotName}_nuke_comp_v{version}/{shotName}_nuke_comp_v{version}.{frame}.exr
Or I can use:
option B:
shots/{name}/media/renders/nuke/comp/v{version}/{shotName}_nuke_comp_v{version}.{frame}.exr
I can wrap either option in xml to create a pattern based openclip using a text editor or openclip creator.
Here is option A pattern based openclip:
<clip>
<handler>
<name>MIO Clip</name>
<options>
<ScanPattern type="string">/JOBS/my_special_job/shots/{name}/media/renders/{shotName}_nuke_comp_v{version}/{shotName}_nuke_comp_v{version}.{frame}.exr</ScanPattern>
</options>
</handler>
</clip>
I saved it as:
/JOBS/my_special_job/shots/shot_0010/openclip/output_clips/shot_0010_nuke_comp
Here is option B pattern based openclip:
<clip>
<handler>
<name>MIO Clip</name>
<options>
<ScanPattern type="string">/JOBS/my_special_job/shots/{name}/media/renders/nuke/comp/v{version}/{shotName}_nuke_comp_v{version}.{frame}.exr</ScanPattern>
</options>
</handler>
</clip>
My job tree looks like this:
JOBS
│
├── other_jobs
│
└── my_special_job
│
├── other_directories
│
└── shots
├── shot_0010
│ │
│ ├── batch_setups
│ ├── media
│ │ ├── renders
│ │ │ ├── shot_0010_nuke_comp_v0001 (option A)
│ │ │ ├── shot_0010_nuke_comp_v0002 (option A)
│ │ │ ├── shot_0010_nuke_comp_v0003 (option A)
│ │ │ ├── shot_0010_nuke_comp_v0004 (option A)
│ │ │ ├── shot_0010_nuke_comp_v0005 (option A)
│ │ │ └── nuke
│ │ │ └── comp
│ │ │ └── shot_0010_nuke_comp
│ │ │ └── v0001 (option B)
│ │ └── sources
│ │ └── shot_0010_layer_01
│ │ └── v0000
│ │ └── P006YNIY
│ │ └── shot_0010_layer_01
│ └── openclip
│ ├── output_clips
│ │ └── shot_0010_nuke_comp
│ └── segment_clips
│
│
├── shot_0020
│ │
│ ├── batch_setups
│ ├── media
│ │ ├── renders
│ │ │ └── shot_0020_nuke_comp_v0001 (option A)
│ │ │ └── shot_0020_nuke_comp_v0002 (option A)
│ │ │ └── shot_0020_nuke_comp_v0003 (option A)
│ │ │ └── shot_0020_nuke_comp_v0004 (option A)
│ │ │ └── shot_0020_nuke_comp_v0005 (option A)
│ │ └── sources
│ │ └── shot_0020_layer_01
│ │ └── v0000
│ │ └── F004MN99
│ │ └── shot_0020_layer_01
│ └── openclip
│ ├── output_clips
│ │ └── shot_0020_nuke_comp
│ └── segment_clips
│
│
├── shot_0030
│ │
└── ├── batch_setups
├── media
│ ├── renders
│ │ └── shot_0030_nuke_comp_v0001 (option A)
│ │ └── shot_0030_nuke_comp_v0002 (option A)
│ │ └── shot_0030_nuke_comp_v0003 (option A)
│ │ └── shot_0030_nuke_comp_v0004 (option A)
│ │ └── shot_0030_nuke_comp_v0005 (option A)
│ └── sources
│ └── shot_0030_layer_01
│ └── v0000
│ └── F004MN99
│ └── shot_0030_layer_01
└── openclip
├── output_clips
│ └── shot_0030_nuke_comp
└── segment_clips
n.b. i edited {frame_number} to {frame} in all instances.
I zeroed out timecode before I exported my versions from nuke, relying solely on frame numbers to align versions.
Now the openclip works in a limited way as expected, including multiple resolutions, but not sure about timecode or offset variations.
Every time a nuke render follows this same render pattern your openclip will have access to the versions.
The pattern browse string permits viewing the individual clips in MediaHub but does not identify related versions.
You can use the pattern browse string to create pattern-based openclips with openclip creator or you can write the relevant strings in a text editor.
You can install openclip creator on non flame workstations or you can define your patterns and use a text editor on pretty much anything.
It shouldn’t be too difficult to script.
Finally, using my directory structure as an example, I can add a new pattern in MediaHub and this will reveal all of my ‘*_nuke_comp’ openclip files:
shots/{name}/openclip/output_clips/{name}_nuke_comp