Merge pull request #8 from docsforadobe/users/bbb/26.0_SDK

bbb999 · web-flow · commit 430dee076141 · 2025-04-22T10:50:10.000-07:00
Plug-in --&gt; Plugin
diff --git a/docs/importers/getting-started.md b/docs/importers/getting-started.md
@@ -14,7 +14,7 @@ Premiere requests audio in arrays of 32-bit float, uninterleaved format.
 
 ---
 
-## Try the Sample Importer Plug-ins
+## Try the Sample Importer Plugins
 
 Choose which one of the three sample importers matches closest with your desired functionality.
 
diff --git a/docs/importers/structure-descriptions.md b/docs/importers/structure-descriptions.md
@@ -832,7 +832,7 @@ typedef struct {
 } imImageInfoRec;
 ```
 
-### Plug-in Info
+### Plugin Info
 
 |          Member          |                                                   Description                                                   |
 | ------------------------ | --------------------------------------------------------------------------------------------------------------- |
diff --git a/docs/intro/document-overview.md b/docs/intro/document-overview.md
@@ -4,7 +4,7 @@ This introduction information is common to all the plugin types.
 
 All developers should read this chapter, and browse through chapters two and three before diving too deep into plugin development.
 
-[Resources](../resources/resources.md) is a short chapter that describes the Premiere Pro-specific resources used by plugins, including the Plug-in Property List (PiPL).
+[Resources](../resources/resources.md) is a short chapter that describes the Premiere Pro-specific resources used by plugins, including the Plugin Property List (PiPL).
 
 [Universals](../universals/universals.md) documents concepts, data types, and structures used throughout the APIs. It also describes suites and functions used by more than one type of plugin.
 
diff --git a/docs/intro/load-em-up.md b/docs/intro/load-em-up.md
@@ -1,6 +1,6 @@
 # Load Em Up
 
-## Plug-in Caching
+## Plugin Caching
 
 On its first launch, Premiere Pro loads all the plugins, reads the [Plug-In Property Lists (PiPL) Resource](../resources/pipl-resource.md), and sends any startup selectors to determine the plugins' capabilities. To speed up future application launches, it saves some of these capabilities in what we call the plugin cache (the registry on Windows, a Property List file on macOS).
 
@@ -12,7 +12,7 @@ By default, legacy video filters and device controllers are cached by default. T
 
 ---
 
-## Resolving Plug-in Loading Problems
+## Resolving Plugin Loading Problems
 
 There are various tools to help in the development process.
 
diff --git a/docs/intro/localization.md b/docs/intro/localization.md
@@ -2,7 +2,7 @@
 
 The language used by Premiere Pro is decided by the user during installation.
 
-Plug-ins can determine this setting from the following locations:
+Plugins can determine this setting from the following locations:
 
 On Windows, in the registry at `HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\[version]`, in a key named `"Language"`.
 
diff --git a/docs/intro/plugin-installation.md b/docs/intro/plugin-installation.md
@@ -1,8 +1,8 @@
 # Plug In Installation
 
-Plug-ins must have an installer. This simplifies installation by the user, provides more compact distribution, and ensures all the pieces are installed correctly.
+Plugins must have an installer. This simplifies installation by the user, provides more compact distribution, and ensures all the pieces are installed correctly.
 
-Create a container folder for your plug-in(s) to minimize user confusion.
+Create a container folder for your plugin(s) to minimize user confusion.
 
 Don't unintentionally overwrite existing plugins, or replace newer versions.
 
@@ -34,7 +34,7 @@ Value data: `C:\Program Files\Adobe\Common\Plugins\7.0\MediaCore\\` (or whatever
 
 Starting in CC 2015.3, **control surface plugins** should be installed here:
 
-`/Library/Application Support/Adobe/Common/Plug-ins/ControlSurface/`
+`/Library/Application Support/Adobe/Common/Plugins/ControlSurface/`
 
 **For sequence presets:**
 
@@ -62,7 +62,7 @@ Value data: `[Adobe Premiere Pro installation path]\Adobe Premiere Pro\Plugins\C
 
 Third-party installers can start from this path, and then modify the string to build the path to the language-specific effect presets.
 
-**Prior to CC**, the only path given in the registry was the common plug-in path for the most recently installed version of Premiere Pro:
+**Prior to CC**, the only path given in the registry was the common plugin path for the most recently installed version of Premiere Pro:
 
 HKEY_LOCAL_MACHINE/Software/Adobe/Premiere Pro/CurrentVersion
 
@@ -94,11 +94,11 @@ Previously, starting in CC 2015, Premiere Pro provided installer hints for Mac.
 
 The **common plugin location** was at:
 
-`/Library/Application Support/Adobe/Common/Plug-ins/[version]/MediaCore/`
+`/Library/Application Support/Adobe/Common/Plugins/[version]/MediaCore/`
 
 Starting in CC 2015.3, **control surface plugins** should be installed here:
 
-`/Library/Application Support/Adobe/Common/Plug-ins/ControlSurface/`
+`/Library/Application Support/Adobe/Common/Plugins/ControlSurface/`
 
 Following OS X Code Signing guidelines, plugins should be installed in this separate shared location rather than in the application bundle.
 
@@ -126,7 +126,7 @@ Following OS X Code Signing guidelines, plugins should be installed in this sepa
 
 ## Plugin Naming Conventions
 
-On Windows, Premiere Pro plugins must have the file extension ".prm". On macOS, they have the file extension ".bundle". Other supported plug-in standards use their conventional file extensions: ".aex" for After Effects plugins, ".dll" for VST plugins.
+On Windows, Premiere Pro plugins must have the file extension ".prm". On macOS, they have the file extension ".bundle". Other supported plugin standards use their conventional file extensions: ".aex" for After Effects plugins, ".dll" for VST plugins.
 
 While it is not required for your plugin to load, naming your plugins using the plugin type as a prefix (e.g. ImporterSDK, FilterSDK, etc.) will help reduce user confusion.
 
diff --git a/docs/intro/premiere-pro-plugin-types.md b/docs/intro/premiere-pro-plugin-types.md
@@ -46,7 +46,7 @@
 |                         |                                                                                                                                                                                           |
 |                         | In CS6.x and previous versions, support was limited to version 2.4.                                                                                                                       |
 +-------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| ASIO                    | An ASIO driver is often provided in addition to a transmit plug-in, to provide audio output during editing, playback, and Export To Tape.                                                 |
+| ASIO                    | An ASIO driver is often provided in addition to a transmit plugin, to provide audio output during editing, playback, and Export To Tape.                                                  |
 |                         |                                                                                                                                                                                           |
 |                         | Prior to CS6, an ASIO driver was required to support audio input for voiceover recording in the audio mixer. On macOS, a Core Audio component may be provided rather than an ASIO driver. |
 +-------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
@@ -55,7 +55,7 @@
 
 ---
 
-### Plug-in Support Across Adobe Video and Audio Applications
+### Plugin Support Across Adobe Video and Audio Applications
 
 This chart shows which third-party plugins are supported by the various Video and Audio applications.
 
@@ -81,9 +81,9 @@ This chart shows which third-party plugins are supported by the various Video an
 
 ---
 
-### Premiere Elements Plug-in Support
+### Premiere Elements Plugin Support
 
-Premiere Elements uses the same core libraries for plug-in support that Premiere Pro does, although Premiere Elements is 32-bit, whereas Premiere Pro is 64-bit starting with CS5.
+Premiere Elements uses the same core libraries for plugin support that Premiere Pro does, although Premiere Elements is 32-bit, whereas Premiere Pro is 64-bit starting with CS5.
 
 | Premiere Elements version | Equivalent Premiere Pro API version |
 | ------------------------- | ----------------------------------- |
@@ -93,7 +93,7 @@ Premiere Elements uses the same core libraries for plug-in support that Premiere
 | 9                         | CS5                                 |
 | 8                         | CS4                                 |
 
-It's always important to test the plug-in fully in each application before advertising compatibility.
+It's always important to test the plugin fully in each application before advertising compatibility.
 
 Check out [Guidelines for Exporters in Premiere Elements](../exporters/additional-details.md#guidelines-for-exporters-in-premiere-elements) for instructions on how to set up your exporter to be used in Premiere Elements.
 
@@ -105,8 +105,8 @@ Premiere plugins contain a single entry point of a type specific to each API.
 
 Plugins are DLLs on Windows, and Carbon or Cocoa Bundles on macOS.
 
-Plug-ins in the \\Plug-ins[language] folder, and any of its subfolders, will be loaded at launch.
+Plugins in the \\Plugins[language] folder, and any of its subfolders, will be loaded at launch.
 
 Plugins can have private resources.
 
-Only one plug-in per file is parsed, unlike After Effects and Photoshop plugins, which can contain multiple entry points.
+Only one plugin per file is parsed, unlike After Effects and Photoshop plugins, which can contain multiple entry points.
diff --git a/docs/intro/sample-projects.md b/docs/intro/sample-projects.md
@@ -116,21 +116,21 @@ For macOS it is BuildAll.xcodeproj; for Windows, it is \_BuildAll.sln.
 
 You'll need to specify some settings so that the plugins are built into a folder where they will be loaded by the application you are developing for.
 
-We recommend plugins be built into the following folder for macOS: `/Library/Application Support/Adobe/Common/Plug-ins/[version]/MediaCore/`
+We recommend plugins be built into the following folder for macOS: `/Library/Application Support/Adobe/Common/Plugins/[version]/MediaCore/`
 
 Version is locked at 7.0 for all CC versions, or CSx for earlier versions.
 
-For example: `/Library/Application Support/Adobe/Common/Plug-ins/7.0/MediaCore/`
+For example: `/Library/Application Support/Adobe/Common/Plugins/7.0/MediaCore/`
 
-or: `/Library/Application Support/Adobe/Common/Plug-ins/CS6/MediaCore/`
+or: `/Library/Application Support/Adobe/Common/Plugins/CS6/MediaCore/`
 
 and the following path for Windows:
 
-`[Program Files]\Adobe\Common\Plug-ins\[version]\MediaCore\\`
+`[Program Files]\Adobe\Common\Plugins\[version]\MediaCore\\`
 
-for example: `C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore\\`
+for example: `C:\Program Files\Adobe\Common\Plugins\7.0\MediaCore\\`
 
-or: `C:\Program Files\Adobe\Common\Plug-ins\CS6\MediaCore\\`
+or: `C:\Program Files\Adobe\Common\Plugins\CS6\MediaCore\\`
 
 !!! note
     This Windows path is only recommended for development purposes.
@@ -144,7 +144,7 @@ In Visual Studio, for convenience, we have set the Output File for all sample pr
 
 1. On Windows, right-click *My Computer > Properties*, and in the left sidebar choose *Advanced System Settings*.
 2. In the dialog that appears, hit the *Environment Variables* button.
-3. In the *User variables*, create a new variable named PREMSDKBUILDPATH, with the path as described above. (e.g. "C:Program FilesAdobeCommonPlug-ins[version]MediaCore").
+3. In the *User variables*, create a new variable named PREMSDKBUILDPATH, with the path as described above. (e.g. "C:Program FilesAdobeCommonPlugins[version]MediaCore").
 4. Log out of Windows, and log back in so that the variable will be set.
 
 When compiling the plugins, if you see a link error such as:
diff --git a/docs/intro/whats-new.md b/docs/intro/whats-new.md
@@ -2,7 +2,7 @@
 
 ## What's New in 24.0
 
-With the removal of Capture functionality from Premiere Pro, support for Record modules and Device Control plug-ins have been removed from the SDK.
+With the removal of Capture functionality from Premiere Pro, support for Record modules and Device Control plugins have been removed from the SDK.
 
 ## What's New in 15.4
 
@@ -98,7 +98,7 @@ In [Video Segment Render Suite](../universals/sweetpea-suites.md#video-segment-r
 
 ## What's New in CC 2024.0
 
-The Transmit API has been expanded to enable multiple audio outputs, and plug-ins which stream video and audio information.
+The Transmit API has been expanded to enable multiple audio outputs, and plugins which stream video and audio information.
 
 ## What's New in CC 2015.4
 
diff --git a/docs/resources/pipl-resource.md b/docs/resources/pipl-resource.md
@@ -1,6 +1,6 @@
 # Plug-In Property Lists (PiPL) Resource
 
-For many plugin types, Premiere loads a PiPL (Plug-in Property List) resource. The PiPL is described in a file with a ".r" extension.
+For many plugin types, Premiere loads a PiPL (Plugin Property List) resource. The PiPL is described in a file with a ".r" extension.
 
 The complete PiPL syntax is described in PiPL.r.
 
diff --git a/docs/transmitters/suites.md b/docs/transmitters/suites.md
@@ -8,7 +8,7 @@ For information on how to acquire and manage suites, as well as information on m
 
 This suite is used to play audio during playback. There are many more functions that were used by players, still documented in the players chapter. Here we will only consider the single call in the suite that is relevant to transmitters.
 
-### Host-Based, or Plug-in Based Audio?
+### Host-Based, or Plugin Based Audio?
 
 A transmitter has two choices for playing audio: it can ask the host to play the audio through the audio device selected by the user, or it can get audio buffers from the host and handle its own playback of audio.
 
diff --git a/docs/transmitters/tmModule-functions.md b/docs/transmitters/tmModule-functions.md
@@ -126,19 +126,19 @@ Fill in `0` for any unsupported calls. Thread safety is defined per-module, only
 |                                    |                                                                                                                                                                                                                                                          |
 |                                    | <pre lang="cpp">tmResult (\*StopPushAudio)(<br/>const tmStdParms\* inStdParms,<br/>const tmInstance\* inInstance);</pre>                                                                                                                                 |
 +------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| `SetStreamingStateChangedCallback` | Set the host callback for notification streaming state changes, i.e. when the plug-in becomes active or inactive due to changes connections or enablement from the host.                                                                                 |
+| `SetStreamingStateChangedCallback` | Set the host callback for notification streaming state changes, i.e. when the plugin becomes active or inactive due to changes connections or enablement from the host.                                                                                 |
 |                                    |                                                                                                                                                                                                                                                          |
 |                                    | <pre lang="cpp">tmResult (\*SetStreamingStateChangedCallback)(<br/>const tmStdParms\* inStdParms,<br/>void\* inContext,<br/>tmStreamingStateChangedCallback inCallback);</pre>                                                                           |
 +------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| `EnableStreaming`                  | Enable/disable streaming to connected clients without loading or unloading the plug-in.                                                                                                                                                                  |
+| `EnableStreaming`                  | Enable/disable streaming to connected clients without loading or unloading the plugin.                                                                                                                                                                  |
 |                                    |                                                                                                                                                                                                                                                          |
 |                                    | <pre lang="cpp">tmResult (\*EnableStreaming)(<br/>const tmStdParms\* inStdParms,<br/>prBool            inEnabled);</pre>                                                                                                                                 |
 +------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
 | `IsStreamingEnabled`               | Returns whether streaming is enabled.                                                                                                                                                                                                                    |
 |                                    |                                                                                                                                                                                                                                                          |
 |                                    | <pre lang="cpp">tmResult (\*IsStreamingEnabled)(<br/>const tmStdParms\* inStdParms,<br/>prBool\*           outEnabled);</pre>                                                                                                                            |
 +------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| `IsStreamingActive`                | Returns whether the plug-in is actively streaming, i.e. streaming is enabled and the plug-in has active connections.                                                                                                                                     |
+| `IsStreamingActive`                | Returns whether the plugin is actively streaming, i.e. streaming is enabled and the plugin has active connections.                                                                                                                                     |
 |                                    |                                                                                                                                                                                                                                                          |
 |                                    | <pre lang="cpp">tmResult (\*IsStreamingActive)(<br/>const tmStdParms\* inStdParms,<br/>prBool\*           outActive);</pre>                                                                                                                              |
 +------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
diff --git a/docs/universals/sweetpea-suites.md b/docs/universals/sweetpea-suites.md
diff --git a/docs/video-filters/additional-details.md b/docs/video-filters/additional-details.md
