Problem summary
With the release of Nuke11.1v1, users can no longer manually set their Read node's Frame range below 0.
This can be an issue if the image sequence has negative frames.
Customer reported version
nuke.11.3v1
Customer reported platform
ubuntu
Steps to reproduce
1) Open Nuke, import an image sequence with negative frames.
The footage will import at frame 0
2) Within the imported image sequence's Read node, attempt to set the frame range to a negative number.
Result: The frame range automatically sets itself back to '0' Workaround
When importing the Image Sequence, manually set the negative values in the filename.
In future setups, it is recommended to setup frame range starting at '1001' .
Reproduced by support
This bug has been reproduced in:
Nuke11.3v1- Windows 7 - Mac10.13 - CentOS7
Nuke11.2v1 - Windows 7
Nuke11.1v1 - Windows 7 - Mac10.13 - CentOS7
Unable to reproduce bug in:
Nuke11.0v4- Windows 7 - Mac10.13 - CentOS7
Earliest version tested
- This issue no longer appears in this version and has regressed
Expected behaviour
Nuke should allow image sequences with negative frame ranges to be read.
Actual behaviour
when setting the negative frame range, it is automatically set back to '0'