Set up SDK in Visual Studio 2022

[дм-11_6671]

Hi, everyone. I have problems with includes files from SDk, it shows errors, but i added path for headers and Utils. #include "PrSDKPlugIn.h" This file even doesn't exist. I tried another file, but this file exists, but error is the same. Who can help with this,plz?
Best regards

[Bruce Bullis]

Specifically, which SDK are you using?

[дм-11_6671]

PremierePro24.0 SDK

[Bruce Bullis]

I don't see "PrSDKPlugIn.h" referenced, within the PPro 24.0 SDK. 

What type of plugin are you building? 

[дм-11_6671]

#### Task: Develop a plugin for Adobe Premiere Pro to automatically detect bad shots

Description:
Need to develop a plugin for Adobe Premiere Pro that automatically analyses a video file and finds frames with poor quality, namely:
- Blurred frames (motion blur, out of focus, camera shake).
- Darkened frames (too low exposure, loss of detail in shadows).

Functional requirements:
1. video analysis
- The plugin should scan the video track and automatically mark problematic frames.
2. Defect Recognition
- Detection of blurred frames (analysis of sharpness, presence of motion).
- Detection of darkened frames (histogram, brightness and contrast analysis).
3. displaying the results
- The user should be able to see which frames are marked as problematic (e.g. via markers on the timeline).
- Ideally, add a window with a report of the number of bad frames and the ability to quickly view them.

Technical Requirements:
- Use of Adobe Premiere Pro SDK.
- Work as a plugin that integrates into the Premiere Pro interface.
- Optimised operation so that analysis does not slow down editing.
- Support for video files in common formats (.mp4, .mov, .avi, etc.).
- Ability to customise the sensitivity of detection algorithms.

Translated with DeepL.com (free version)

[Bruce Bullis · Accepted solution]

That's quite a list!

Based on what you've described, there is no C++ plugin type that will do what you want. A CEP extension can do much of what you've requested; here's the PProPanel example. Panels can (among other things):

• render a sequence using a specific output preset
• identify trackItems in the sequence (useful, if you're going to segment your analysis) 
• add sequence markers
• report bad frames (or anything you like) in PPro's Events panel

The only way to get source frames from a sequence, before they're exported to an output format (all of which have limitations), is through a C++ Exporter; that would make for a pretty strange workflow, for users. 

> Optimised operation so that analysis does not slow down editing.

Analysis will always require time; if you can violate the laws of physics in that way, you're definitely onto something. 🙂

[дм-11_6671]

I have several questions:
How to compile the extension code correctly? How do I connect the resulting file?

[bbb_999]

Extensions aren't compiled; they're interpreted. 

The PProPanel readme explains how to set up a development environment.