Premiere Pro SDK PrSDKVideoSegmentSuite AcquireOperatorOwnerNodeID() unavailable on adjustment layer

[FxFactory]

The APIs that allow a GPU accelerated effect to extract its start and end PrTimes on the timeline are inaccessible when the plugin is applied to an adjustment layer. There appear to be no other methods to extract that information, and this makes certain plugins unable to work correctly when applied to adjustment layers.

(This bug refers to plugins based on the AE SDK that implement the Premiere Pro extensions for GPU acceleration.)

Steps to reproduce:

- Take an existing AE plugin that implements the necessary Premiere Pro SDK extensions for GPU acceleration.

- When the GPU effect instance is created, extract the start and end times (in ticks) of the underlying video clip using this sequence:

1. Call PrSDKVideoSegmentSuite::AcquireOperatorOwnerNodeID() passing in the effect’s node ID as received in the PrGPUFilterInstance->inNodeID structure to get the node ID of the clip the effect is applied to.
2. Call PrSDKVideoSegmentSuite::GetNodeProperty() on the clip’s node ID, passing kVideoSegmentProperty_Clip_TrackItemStartAsTicks or 

   kVideoSegmentProperty_Clip_TrackItemEndAsTicks.

- Notice that when your plugin is applied to a video clip, the above technique allows you to extract the start/end times, in ticks, where your effect plugin is "live", relative to the timeline.

- Apply the same plugin to an adjustment layer, and notice that the AcquireOperatorOwnerNodeID() fails, thus preventing you from knowing the start/end times.

Expected results:

It would be best if the existing API would work in the second scenario too. Alternatively, a different API  is needed to extract values for` kVideoSegmentProperty_Clip_TrackItemStartAsTicks and kVideoSegmentProperty_Clip_TrackItemEndAsTicks when an effect is applied to an adjustment layer. It is unclear if any other APIs currently part of the SDK can be used to work around this problem.

Actual results:

GPU-accelerated effects have no way of knowing their in/out time in ticks when applied to adjustment layers.

[Kevin-Monahan]

Moving to discussions for SDK tagging. I hope this helps my ol' friends there @FxFactory! You'll get better traction with this tag even if it's a bug. I hope it helps you.

Cheers,

Kevin

[FxFactory]

Thanks Kevin! How can I add the SDK tag to other posts? It’s not listed among the options, and I've got quite a few reports I have a feeling went unnoticed. We need the SDK to improve so plugins can too! 🙂

[Stan Jones]

@FxFactory,

I see SDK in the tags now. If you were the original poster, click on the 3 dots/more options, pick Edit Message. You can edit the tags there.

Stan

[FxFactory]

I can see the SDK tag for this message too, but it isn't available for other posts. See screenshots below, for example:

The available tags are fewer than those I get when editing this message... I wonder if it's linked to where the post originally appears, and maybe it’s always best to post in general Discussions first and then hope the SDK tag shows up.

[Dan McSweeney · Accepted solution]

Thanks or bringing this up. Thanks @Kevin-Monahan  for promoting it.
I've written the bug/feature request, we're tracking it as DVAAP-3508.

-Dan

[FxFactory]

Amazing, thank you! Please contact us when the fix makes it to the Beta so we can start testing.

[FxFactory]

Seem to actually be tracked as DVAAP-3058