Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.

nuke: wrong frame offset in mov loader #971

Merged
merged 1 commit into from
Feb 4, 2021

Conversation

jakubjezek001
Copy link
Member

No description provided.

@jakubjezek001 jakubjezek001 self-assigned this Feb 3, 2021
@jakubjezek001 jakubjezek001 added type: bug Something isn't working release labels Feb 3, 2021
Args:
loader (tool): The fusion loader tool.
frame (int): The amount of frames to move.
relative (bool): When True the shift is relative, else the shift will
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

line too long (81 > 79 characters)

def loader_shift(self, node, frame, relative=True):
"""Shift global in time by i preserving duration

This moves the loader by i frames preserving global duration. When relative
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

line too long (83 > 79 characters)

@mkolar mkolar added this to the 2.15.0 milestone Feb 4, 2021
@mkolar mkolar merged commit 7df7d46 into release/2.15.0 Feb 4, 2021
@mkolar mkolar changed the title fix(nuke): frame offset mov loader nuke: wrong frame offset in mov loader Feb 4, 2021
@nextreleaseio nextreleaseio bot mentioned this pull request Feb 8, 2021
@mkolar mkolar deleted the bugfix/nuke-mov-loader-frame-offset branch February 10, 2021 10:19
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants