PlumePack is made to work with any Premiere Pro Project ! Because Premiere Pro has a lot of different features, as you can imagine there are some edge cases where some special projects can be limited by PlumePack or have special issues with.
This article gives you details about all those limitations and issues we are aware of !
Note : this article will be updated with all modifications along the future versions of PlumePack.

General Limitations

  • Video Preview Files
    : Those files are rendered files generated by Premiere Pro and located next to your original project file. They are generated if you click on the top menu : "Sequence" -> "Render In to Out". The top timeline color becomes green then. Those files are not copied with PlumePack for now.
  • Proxies
    : Proxies are rendered files generated by the user aimed at having a smooth playback and editing in Premiere Pro. A proxy is attached to an original "main" heavy footage. When a proxy is attached to a file and the project is PlumePacked, the proxy is detached and neither copied nor trimmed.
  • After Effects Dynamic Linked Compositions
    : The AE Comp .aex file is well copied and replaced in the new PlumePacked project. The media dependencies of this AE comp (imported media in After Effects) are well copied in the same subfolder next to the .aex file but
    are not replaced
    in the AE comp.

General Trimming Limitations

First, there is a list of codecs which can be trimmed. Other codecs will be replaced. You can find this codec list here.
These Premiere Pro several elements can also not be trimmed. So if any media is used with one of these elements,
it will be copied instead
of trimmed :
  • Merged Clips
    : The Merged Clips are created from the timeline with different audio and video media (top menu : Clip -> "Merge Clips ..") It is used to link those media inside a unique Project Item in Premiere Pro.
  • Time Remapped Clips
    : On the "Effects Tab" when selecting a clip in your timeline, you can add keyframes for "Time Remapping". When using this we can't be sure of the exact used part of the media.
  • After Effects Dynamic Linked Compositions
    : AE composition from .aex file imported into Premiere Pro.
  • AEgraphics
    : AEgraphics are special After Effects "templates" which you can use and modify directly from Premiere Pro from a special Panel.
  • SubClip with Hard boundaries
    : After setting a InPoint and OutPoint on a Project Item Source, right clicking on this item make "Create Subclip" available. It creatse a new Project Item from the original one, called Subclip. An option is displayed to use "hard boundaries" or not : it will restrict the user to use the frames inside the InPoint/OutPoint (this option can be edited later).
  • Clips with one of these effects applied
    :
    • (Native) TimeWarp
    • (Native) Echo
    • (Native) Posterize Time
    • (Native) Pixel Motion Blur
    • (Plugin) Twixtor

Clip Names and Colors Reset

When Copied OR trimmed :
  • the
    Project Item Name
    is set to the default media name
  • the
    Project Item Color
    returns to its default color
When trimmed only :
  • the
    Timeline Clip Name
    returns to its default name for newly created ProjectItem (when media trimmed in multiple parts)
  • the
    Timeline Clip Color
    returns to its default color for newly created ProjectItem (when media trimmed in multiple parts)
Note : We are currently working on a fix for this.

Special Case : Nested Sequence

Nested Sequences are sequences used in another sequence.
When using the
"Keep only Chosen Sequence and Deps"
option in PlumePack, only media in this sequence AND in nested sequences AND in nested sequence of the nested sequence etc .. are processed. Others are removed.
However, the nested sequence are
processed entirely
and so are not processed from the used part of the parent sequence. We could add an option about this in the future.
Autokroma PremierePro PlumePack Sequence NestedSequence

Special Case : Project used in a Productions context

Productions is a Premiere Pro feature to manage a group of Premiere Pro Projects, especially when working with a team.
When using Productions, some footages can be imported in a
Project A
(so the Project Items are in this project) and use the Project Items in a timeline of a
Project B
. The timeline clips in the
Project B
have their Project Item in the
Project A
.
With such clips, if the
Project A
is PlumePacked with trimming enabled, then when opening the
Project B
with
Project A
opened, the
Project B
clips from trimmed media will be
shifted
! With copy only, in this case there should be not problem though.
With such clips, if the
Project B
is PlumePacked (with or without Trimming enabled), it will work as excepted and the
Project B
clips will be well replaced. However, as soon as both projects are opened at the same time, the
Project B
clips will return to their old filepath, and if trimming was enabled, they could also be shifted.
Note that before PlumePacking the
Project B
(so a Project with clips which have their Project Items into another Project), clicking on the top menu : "Edit" -> "Generate Master Clips for Media" automatically populates the
Project B
with Project Items used in its timeline (so the project has no more external project dependencies).
You can find here a full in depth tutorial about Productions. It links to the part of the video showing the "Generate Master Clips for Media" part.
Autokroma PremierePro PlumePack Productions

Special Case : Warp Stabilizer Effect

The warp stabilizer effect is a Premiere Pro native effect which can stabilize your moving video for a smoother result.
The particularity of this effect is that it is not a "Live" effect like classical ones. It needs to analyse the whole video first.
If a clip with the Warp Stabilizer applied is replaced by a
Trimmed Media
with PlumePack, you will need to analyse the video again in the new Project. You will be noticed by a big blue banner displayed on this video.
If a clip with the Warp Stabilizer applied is replaced by a
Copied Media
with PlumePack, the playback in Premiere Pro could be horribly slow on this clip. We don't know yet why ... A workaround for this can be to modify the params so the effect will detect that Analysis needs to be run again and Analyse a new time the footage. You can also use "Render In to Out" because rendering this clip will not be slower, only the playback is.
Autokroma PremierePro PlumePack Warp Stabilizer

Special Case : Closed Captions Media

Closed Captions media are captions put inside the file itself, as "Data Streams". There are several norms about those Data Streams but the most famous are "c608" and "c708".
When putting a Project Item from a Closed Caption media inside a timeline, a
Caption Clip
is automatically added at the top of the timeline (in the Caption Track).
There is no problem while copying those clips with PlumePack. The issue here is when you want to trim such media.
The PlumePack Trimming Engine drops (removes) the Captions Data Stream inside the trimmed file. However in Premiere Pro, the Captions clips don't refer to the Media anymore and
are stored directly inside the prproj
, so your Captions Clips inside the timeline Caption Track will not be affected at all ! But if you drag and drop the Project Item from the timeline a new time after PlumePacking, there will be no Caption Clip added to the timeline anymore.
If you prefer to not trim such media and so not loose the Captions Data Stream inside the files but trim other media in the project,
there is special option for that
: just uncheck the "Drop Metadata Streams if Necessary" option ! The Closed Captions media will not be trimmed and copied instead.
Autokroma PremierePro PlumePack ClosedCaptions

Special Case : Slow Motion Files with Audio

Some Cameras can record a video with a high framerate, and save the file with a lower framerate. The result is that the footage is played by default at the lower framerate and so directly looks like a SlowMotion video.
For example, the video is recorded at 120fps and saved as a 30fps footage, so it looks like a video 4x time slower.
The "problem" comes with Audio. On these files, the audio can be recorded and saved with the same Sample Rate. So the video is slowed down but not the audio, and it results with an audio part shorter in time than the video part. In Premiere Pro, even if the audio is shorter, the audio clip in timeline can be the same length of the video clip. So the final part of the audio clip is empty !
Obviously, we are talking here about the default interpreted footage. This behavior can be modified then in the NLE like Premiere Pro. In our example, you could set the 30 fps footage to be considered as a 120fps footage. The video would be played at a normal pace (without being slowed down), but the audio part would also be accelerated on this Project Item though.
In Premiere Pro, as we said, those kind of clips can have the same clip length in the timeline but
a part of the audio clip is empty
! When trimming, if the new trimmed part is inside this "empty" audio part, the new trimmed media has only a video stream without audio.
The problem comes when replacing the file ! If you do it manually, there is a message from Premiere Pro saying that the new file doesn't have audio (but the original had one) and so the audio clip in timeline is automatically removed.
PlumePack detects those kind of situation. If the audio clip is empty, it knows that the Trimmed media will not have audio inside and so it automatically deletes the audio clip in timeline (without reporting an error in the final report !).
However
if you set a transition on this empty audio clip
, removing this clip would also remove the transition, which is also partially applied into another clip ! So by security if there is a transition applied the media will be excluded from trimming.
Autokroma PremierePro PlumePack SlowMotion Video
How do you use PlumePack, do these limitations and issues are a problem for you? Contact us to tell us ! We might find more solutions

BETA for Autokroma Influx (All-in-one Importer for Adobe Premiere Pro, Media Encoder and After Effects)

Try out our BETA for our new Importer plugin for Adobe CC video software !
Read more

How to use Premiere Pro Project Manager

Full tutorial on how to use the Project Manager in Premiere Pro
Read more

Apple Silicon (M1) Plugins Compatibility with Adobe Creative Cloud and Autokroma products

If you just updated Premiere Pro you might have noticed some plugins don't appear anymore, here's the workaround to get back to Intel mode !
Read more

PlumePack VS Premiere Pro Project Manager

Premiere Pro has its own native Project Manager : in this article we will explain its differences with our plugin PlumePack so you can choose what's best for you
Read more

Vizual PixelPerfect : Upscale your Pixel Art with Nearest Neighbors in Premiere Pro for FREE !

Discover our new pack of filters for Adobe CC that brings you FREE pixel art upscaling algorithms for Premiere Pro and After Effects
Read more

How to work with Production in Premiere Pro

If you are working with BRAW Studio and the Premiere Pro feature called Production, there are some important things you need to know !
Read more

vcruntime140.dll was not found : How To Install VCRedist to use our plugins

You need to install VCRedist (Visual C++ Redistributable) from Microsoft in order to use our plugins and others Windows applications
Read more
If you're running Apple silicon (latest M1 CPU) please read our article about compatibility with Adobe !