Closed timlehr closed 3 months ago
Attention: Patch coverage is 90.90909%
with 4 lines
in your changes are missing coverage. Please review.
Project coverage is 74.20%. Comparing base (
134b9b2
) to head (f6b309e
).
@ssteinbach If you could have a look at this sometime, that'd be wonderful. See https://github.com/OpenTimelineIO/otio-aaf-adapter/pull/43 for why this is needed.
@timlehr Can you switch the base branch in this PR to the new extract_adapters_post_beta_16
branch - that one was rebased on the main branch after the beta 16 release.
@reinecke Just rebased the code!
@reinecke @timlehr did the rebase capture too much stuff? It seems like there is a lot in here -- or did the base change w/o/ rebasing?
(sorry, accidentally closed/reopened the PR)
@ssteinbach Seems like there were force-pushes to the extract_adapters_post_beta_16
branch after I rebased, so I will have to do that again.
Summarize your change.
This adds support for attributing custom hooks to adapters and executing them with
hook_function_argument_map
being passed along through the adapter IO functions.Describe the reason for the change.
I added two custom hooks to the OTIO AAF adapter (https://github.com/OpenTimelineIO/otio-aaf-adapter/pull/43), allowing for embedding of media essence into the resulting AAF. This was needed to facilitate just-in-time DNXHR transcoding of the media for the AAF creation and adding a certain level of control and flexibility to the feature.
These features to the core are required in order to properly pass the hook argument map along to potential custom hooks run by the adapter. I tried to work with
_FEATURE_MAP
instead of creating a new version of the Adapter schema in order to minimize the impact of this change, while adding the necessary changes to facilitate custom hooks for adapters.Reference associated tests.