• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
1

Premiere Pro SDK PrSDKVideoSegmentSuite AcquireOperatorOwnerNodeID() unavailable on adjustment layer

Participant ,
Jan 14, 2025 Jan 14, 2025

Copy link to clipboard

Copied

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.

TOPICS
SDK

Views

52

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Jan 14, 2025 Jan 14, 2025

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

 

Votes

Translate

Translate
Adobe Employee ,
Jan 14, 2025 Jan 14, 2025

Copy link to clipboard

Copied

LATEST

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

 

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines