Problem summary
When using 'input/frame' as an option within the Burn-In soft effect for NukeStudio & Hiero, any QuickTime clips (e.g .mp4, .mov, etc) will come into the viewer with a starting frame of '0'.
This is a problem because QuickTime files start at frame '1', meaning clips will appear to be one frame short.
Although this is the case when the sequence is exported, it is rendered starting at frame '1'
Customer reported version
Hiero10.5v5
Customer reported platform
n_a_mac
Steps to reproduce
1) Open NukeStudio / Hiero
2) Import an .mov clip and an image sequence (e.g .jpg, .png, .exr, etc)
3) Place both clips on the timeline
4) Create a Burn-In soft effect by right-clicking one of the clips and navigating to ( 'Effects -> Burn-In' )
5) Select the Burn-In and extend it over both clips
6) Within the soft effect, change one of the Burn-In options to 'input/frame'
Result 1: When viewing the .mov clip, it will start at frame 0 (When its properties state the first frame is 1)
In contrast, the Image sequence will start at its filename's number.
7) Render the sequence via ( 'Right-click sequence in bin -> Export' )
8) View the rendered sequence
Result 2: The first frame will now be 1 as expected.
Workaround
Unknown.
Reproduced by support
This bug has been reproduced in:
NukeStudio11.0v1 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio11.0v3 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio11.0v1 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio10.5v7 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio10.5v1 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio10.0v6 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio10.0v1 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio9.0v9 - Windows 7 - Mac10.12 - CentOS6.9
NukeStudio9.0v1 - Windows 7 - Mac10.12 - CentOS6.9
Earliest version tested
NukeStudio9.0v1 - This feature did not exist before this version
Expected behaviour
QuickTime files should be burned-in with a start frame of '1' within the viewer
Actual behaviour
QuickTime files are be burned in with a start frame of '0' within the viewer