This feature will be added in a future version. For now you can use this workaround: create a Temporary Sequence and import inside all the sequences you want to select. Then in PlumePack select this Temporary Sequence as the Main sequence and launch the process."
On Windows you should run your cmd.exe or Powershell in Administrator Mode, then run PlumePack installer executable with the /S argument, for example in Powershell : ./"PlumePack v1.0.0 Installer.exe" /S if you're in the extracted folder from the downloaded zip. Same goes for the uninstaller but you'll also need to specify the -Uninstall_PlumePack argument. If you want to be sure that the installer / uninstaller exit automatically without user confirmation you should run the .exe like this instead start "Autokroma" /wait /b "PathToInstallerOrUninstaller.exe" /S
Our installers are not viruses, but some AntiVirus software (Windows Defender, Norton AV, McAfee, Bitlocker etc.) sometimes produce false positive because of their probabilistic detection algorithms and the fact that we're using a very common library to create our installers. We regularly check our installers with VirusTotal.com too and there are never more than 1 or 2 AV producing a false positive. If that happens to you, please report this as a false positive to your AV software vendor ! You can disable the AV for the installation process, then re-enable it.
For example let's say you have a nested sequence with one clip inside fully used. In the parent sequence, you only select a part of the nested sequence.
Now you launch PlumePack from the parent Sequence and choose the options to optimize the disk space. In that case if you choose the "Remove Unused Elements in Nested Sequence" (or "Remove Unused Elements in Muticam Sequence") AND trim from the parent sequence (chosen in the PlumePack option), the clip in the Nested Sequence will be trimmed based on the parent sequence use. That's why you could end up with a clip in the nested sequence with diagonal danger lines in the timeline, but actually they should be reference to a part NOT used in the parent sequence.
No ! PlumePack makes a copy of your project, so your original project will not be modified, and your original media will never be modified or removed by PlumePack !
You can only continue editing other projects, but not the current project ! The PlumePack process could fail to relink the files at the end if you modify the project.
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.Find all PlumePack limitations in this article
PlumePack will rename the file is there is any conflict, so you will get a filename.ext and a filename_1.ext. This situation happens if you have 2 media with the same filename, and PlumePack consolidates them in the same folder.
No, PlumePack can only copy or Trim your media. By Trimming, you keep the same codec, metadata and pixel quality. However, you can use PlumePack to clean/filter your project first (because it gives you better features than the native Project Manager for that) and select the "No Process" Main Media Process. Then use the native Project Manager to transcode your cleaned project !
No sadly there is no way to continue a PlumePack process and you will need to relaunch it from the beginning. In most cases when the process failed the errors are well indicated into the final report, so you can eventually manually fix the issues yourself. If you would want to continue a PlumePack process, fill our Feature Requests Form.
PlumePack copies your media files following your Project Bins structure ! So your final Disk structure will be more organized than having everything in the same folder ! With PlumePack Premium you can also choose to use the Disk Data Structure of your files to organize your PlumePacked Project. Full comparison with the Project Manager in this article.
PlumePack copies the media dependencies of the AE comps (imported media in After Effects) into the same subfolder next to the .aex file. Those files are not replaced in the AE comp though and you will need to relocate manually in AE. The aex file itself is well copied and replaced in your premiere pro project. Full comparison with the Project Manager in this article.
PlumePack copies the media dependencies of the AE comps (imported media in After Effects) into the same subfolder next to the .aex file. Those files are not replaced in the AE comp though and you will need to relocate manually in AE. The aex file itself is well copied and replaced in your premiere pro project. Full comparison with the Project Manager in this article.
PlumePack copies and replace the Aaegraphic/MOGRT in your destination folder. It also detects if another media is used inside this Aegraphic and it is also copied and replaced. Full comparison with the Project Manager in this article.
With PlumePack you can choose one sequence and consolidates your project from this "Main" sequence. All nested sequences will be taken into account recursively. If you need to select many "Main Sequences", you can create a new sequence, put your "Main Sequences" inside, and PlumePack this new sequence. Full comparison with the Project Manager in this article.
Yes totally ! The native Project Manager and PlumePack are independent, and PlumePack is far more stable than the native solution. If you just need to copy your files, the PlumePack FREE version could be enough for your needs ! Note that PlumePack can't transcode your media. If you need to save some disk space, consider buying a PlumePack Premium license and trim your files without re-encoding ! Full comparison with the Project Manager in this article. If you still want to use the Project Manager (maybe because Transcoding is important for your workflow), here are the following advices to make it work :
Uncheck "Include Audio Conform Files"
Uncheck "Include Preview Files"
Delete all your proxies
Check if you have special characters in your video/photo/work files naming like "+", "#", "$", ...
Yes! PlumePack will move the entire tracks, not only clips on the tracks. This means that all audio effects and associated automation / key-framing will move along with the tracks.
Please try to open it directly by double clicking on the following file in your computer (you will need to restart Premiere Pro once modifications are done from here)
There are 2 actions you can make in order to fix this particular issue : resetting "Plugin Loading Cache" and making a new project from the original one. One could be enough, but let's make both of them to be sure !
Make sure Premiere Pro is closed
Start Premiere Pro from your project and maintain the "Shift" key of your keyboard maintained. A dialog should be opened : tick the "Reset Plugin Loading Cache" checkbox and click Ok
Once your project is opened, create a new empty project. Copy everything in the original project (from the root bin in the Project Panel) and paste it in the new created project. It should make a perfect copy of your original project
Close Premiere Pro
Launch Premiere Pro and re-do the same trick to "Reset Plugin Loading Cache" (by maintaining the "Shift" key while launching Premiere Pro)
Finally, launch the PlumePack process
If you have any issue remaining, enable the logs at the bottom of the panel, reproduce your issue and send us the logs following yellow guidelines at the top
PlumePack has a Free version! A bug free alternative to the Project Manager. Learn more about our Change of Policy and the Free version in this article
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
When using PlumePack, in case you have trouble with the plugin, you should send us some logs so we can give you assistance and fix a potential bug in our plugin. Here's how to do it.