Skip to content

AAF adapter: added clip_timecode_offset argument#1029

Closed
timlehr wants to merge 1 commit intoAcademySoftwareFoundation:mainfrom
AnimalLogic:aaf_include_timecode
Closed

AAF adapter: added clip_timecode_offset argument#1029
timlehr wants to merge 1 commit intoAcademySoftwareFoundation:mainfrom
AnimalLogic:aaf_include_timecode

Conversation

@timlehr
Copy link
Copy Markdown
Contributor

@timlehr timlehr commented Jul 29, 2021

Link the Issue(s) this Pull Request is related to.

Fixes #1028

Summarize your change.

AAF adapter: added clip_timecode_offset argument

Added clip_timecode_offset as new optional argument. By default, the behaviour is the same as before. However, if the parameter is set to False, the track timecode offset will not be added to the clip source range. This allows for easy access to the actual source range used in the clip.

Reference associated tests.

  • updated test_aaf_adapter.py

Added `clip_timecode_offset` as new optional argument.
By default, the behaviour is the same as before.
However, if the parameter is set to `False`, the global
timecode offset will not be added to the clip source range. This allows for easy access to the actual
source range used in the clip.
@fabal fabal force-pushed the aaf_include_timecode branch from 5e49cc5 to c19aa58 Compare July 29, 2021 03:32
@jminor jminor self-requested a review August 19, 2021 17:18
@jminor jminor self-assigned this Aug 19, 2021
@ssteinbach ssteinbach added this to the Public Beta 14 milestone Aug 19, 2021
@jminor
Copy link
Copy Markdown
Collaborator

jminor commented Sep 7, 2021

In discussion with @timlehr, @andrewmoore-nz, and others we would like to hold on this PR until Andrew updates his older PR that touches this same code. The current implementation finds timecode for a clip only from a single mob, but should sum the offsets from a chain of mobs instead. Once that is in place, we can re-examine this PR with a better understanding of how timecode for a clip should be retrieved.

@jminor jminor modified the milestones: Public Beta 14, Public Beta 15 Oct 13, 2021
@timlehr
Copy link
Copy Markdown
Contributor Author

timlehr commented May 2, 2022

Playing around a bit more with #1063, we get the source range we expect internally. This one ignores the mob chain entirely based on some wrong understanding I had of the AAF parser code last year. I think this one can probably be closed. @jminor

@meshula
Copy link
Copy Markdown
Collaborator

meshula commented May 2, 2022

Closing i n favor of #1063

@meshula meshula closed this May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

AAF adapter: track timecode offsets clip source range

4 participants