ID 546673 - Setting trackItem.addToNukeScript()'s outputToSequenceFormat argument to False doesn't work if the clip has a Clip Reformat applied to it

Problem summary
Setting trackItem.addToNukeScript()'s outputToSequenceFormat argument to False doesn't work if the clip has a Clip Reformat applied to it
 
If the clip doesn't a Clip Reformat then the outputToSequenceFormat argument works as expected
 
Customer reported version
hiero.12.2v8
 
Customer reported platform
centos7
 
Steps to reproduce
 
1) Open Hiero

2) Import any 4K footage, and add it to the timeline, making sure the Sequence Output Resolution is 1920x1080 HD_1080

3) Select the clip on the timeline, and in it's Sequence>Properties tab, set the Clip Reformat to To Sequence Resolution
 
4) With the clip on the timeline selected, run the following code in the Script Editor,  changing the <path/to/new/script> path to a valid path:
 

import hiero.core.nuke as hnuke script = hnuke.ScriptWriter() trackItem = hiero.ui.getTimelineEditor(hiero.ui.activeSequence()).selection()[0] trackItem.addToNukeScript(script, outputToSequenceFormat=False) script.writeToDisk("<path/to/new/script>.nk")

 
5) Open then Nuke script created in Nuke, there is a reformat node when there shouldn't be:
 

 
Expected behaviour
For no reformat node to be added when creating the Nuke script
 
Actual behaviour
A Reformat node is added which reformats the node to the sequence resolution
 
Workaround
Manually add the nodes to the Nuke script Python object, and don't include the Reformat node:
 

import hiero.core.nuke as hnuke script = hnuke.ScriptWriter() trackItem = hiero.ui.getTimelineEditor(hiero.ui.activeSequence()).selection()[0] nodes = trackItem.addToNukeScript() for node in nodes:     if not isinstance(node, hiero.core.nuke.ReformatNode):         script.addNode(node) script.writeToDisk("<path/to/new/script>.nk")

 
Reproduced by support
This bug has been reproduced in:
Hiero 14.0v5 - Windows 10, CentOS 7, macOS Monterey
Hiero 10.0v1 - Windows 10
 
Earliest version tested
Hiero 10.0v1 - This issue appears to be in all tested versions of the product