Problem summary
The timeline In and Out values can be modified by changing the inTime and outTime in the Project Settings tab, or by changing the hidden workingInTime and workingOutTime parameters on the root node via Python.
However, when these values are driven by a different parameter via an expression, the parameter values are updated, but the timeline In and Out frames are not.
Customer reported version
Not supplied
Customer reported platform
Not supplied
Steps to reproduce
-
Launch Katana. In the Project Settings tab, open the wrench menu and select Edit User Parameters.
-
Click Add to the right of the User group header, add a Number parameter and rename it ‘timeIn’.
-
Right-click in the value field of the inTime parameter and choose Expression from the context menu.
-
Set the expression to the following:
getParam('rootNode.user.timeIn')
-
Update the user.timeIn parameter. The value of inTime changes, but the timeline stays where it was.
-
Run the following commands in the Python tab to drive the workingInTime parameter via an expression:
NodegraphAPI.GetNode('rootNode').getParameter('workingInTime').setExpression("getParam('rootNode.user.timeIn')")
Result: If the previous value of workingInTime is different to user.timeIn, the timeline In value is updated. Any subsequent changes of user.timeIn don’t result in updates to the timeline, even though querying the parameter value via Python returns the correct value.
Workaround
An update to the outTime or workingOutTime parameter also updates the timeline In (if outTime or workingOutTime are not driven by expressions)
Reproduced by support
Katana 2.5v1, 2.5v5, 2.6v1 Windows 7
Katana 2.1v5, 2.5v1, 2.5v5, 2.6v1, 2.6v2 CentOS 7
Expected behaviour
A change to workingInTime or workingOutTime should update the timeline In or Out points.
Actual behaviour
When workingInTime or workingOutTime are changed via an expression, the timeline In or Out points aren’t updated.