Problem summary:
An "Unable to transcode" error prevents Exports when a Clip's media starts at a later frame than other Versions of the Clip
Customer reported version:
Hiero 15.0v4
Customer reported platform:
N/A
Steps to reproduce:
1) Launch Nuke Studio and open the Node Graph
2) Create a CheckerBoard and a Write node
3) Export a "v001" EXR sequence that has a 1-10 frame range:
4) Export a "v002" EXR sequence that starts at a later frame, such as 3-10:
5) Switch to the Timeline environment, and navigate to File > Import File(s)...
6) Select the "v001" EXR sequence created in step 3, and add the Clip to the Timeline
7) Use the Alt+Up Arrow shortcut to Version Up the Clip to v002, and remove the red missing frames from the Track Item:
8) In the Timeline, Right-Click and select the Export... option
9) Attempt to Export using any Transcode Preset, and observe the "Unable to transcode, some clips being transcoded are in error state (perhaps colorspace is invalid)" error that occurs:
Expected behavior:
Clip Versions with different frame ranges should not prevent Exports from succeeding, or return colorspace errors.
Actual behavior:
When a Clip Version's first frame is later than previous Versions, it is not possible to Export the media and an unclear error message suggesting colorspace issues is displayed.
Prior to Nuke Studio 15.1v1, an error would always appear in the Viewer regarding the v002 Version missing frames:
Workaround:
It is possible to avoid this issue by setting the Clip's Missing Frames knob to anything besides "error". For example, the following script will set all Clips in the current Sequence that have an error to use the "checkerboard" option:
sequence = hiero.ui.activeSequence() for track in sequence.videoTracks(): for track_item in track.items(): clip = track_item.source() if clip.hasError(): print(f"{track_item.name()} has an error, setting Missing Frames knob to 'checkerboard'") clip.readNode()["on_error"].setValue(2)
Reproduced by Support in:
Nuke Studio 16.0v1 - Windows 11, macOS 14 Sonoma
Nuke Studio 15.1v1 - Windows 11
Nuke Studio 14.0v1 - Windows 11
Nuke Studio 13.0v1 - Windows 11
Nuke Studio 12.0v1 - Windows 11
Earliest version tested:
Nuke Studio 12.0v1 - This issue appears to be in all tested versions of the product
