Problem summary
Nuke Studio clips are slipping in timeline if frame count has changed
Customer reported version
nuke.10.0v6
Customer reported platform
windows10
Steps to reproduce
1. Open Nuke
2. Create colorwheel node
3. Add a text node and include the following in the message field (essentially just adds the frame number to the image so that you can see which frame you are on/rendering):
frame = [frame]
4. Place text within the format of the image
5. Create write node
6. Write to local directory with a frame range that starts after 1 i.e. frames 10-20 i.e.
/temp/22/test2.####.dpx
7. Open Studio
8. Import clip onto timeline
9. Move clip so it does not start on frame 0 on the timeline
10. Go back to comp and render a single frame that is the frame before your previous first frame i.e. frame 9 (render needs to go to same directory)
11. Go back to Studio timeline > select clip > right click > clip > refresh clips (I can only repro this bug with rescan clips - Jothi Puru)
Result: frames in the clip increase by 1, so that the original start frame of 10 becomes 11 and the last frame errors because nothing exists
Workaround
Unknown.
Reproduced by support
Nuke Studio 10.5v2 - OSX 10.11.6 - Windows 8
Nuke Studio 9.0v1 - OSX 10.11.6
Hiero 1.8v1 - OSX 10.11.6
Expected behaviour
Clips not to have frames move forward if new renders are added to the clip directory
Actual behaviour
Frames in the clip are moved if new renders are added to clip directory if the timecode has not been appropriately moved also