New Team Projects Feature - In BETA Now!
Media Relink Workflow Improvements
We are pleased to announce the availability of this new feature as part of our BETA program. We look forward to hearing what you think about these improvements and appreciate your time trying them out. This feature is available TODAY in the daily BETA builds of Premiere Pro.
Problem Statement and Intent
One of the most common questions we receive from customers on the forums is related to relinking media in Premiere Pro with Team Projects. Many customers follow the same relink workflow in Team Projects as they have done successfully before in stand-alone Premiere Pro (a reasonable assumption). But this can lead to trouble because with Team Projects, the normal “relink” command for Premiere Pro is treated as a change to the project (also referred to as an EDIT) that then needs to be SHARED to other collaborators. Once the SHARE occurs those relinked paths will update the paths for all collaborators – usually resulting in broken links and offline media. This can happen when not all collaborators in a project have the exact same storage paths to the media.
Our new relink workflow in Team Projects for Premiere Pro aims to resolve this problem and make it easier and more consistent to relink media whether you are using Team Projects or stand-alone Premiere Pro.
Customers have asked for the ability to use the standard Premiere Pro “Link Media” command in a Team Project and have it treated as a local-only change (I.e. does not require a Share operation and thus has no impact on the paths for other collaborator’s media).
So that is what we’ve done.
This operation now matches the user experience in stand-alone Premiere Pro, yet behind the scenes Team Projects generates the necessary media mapping for you – just as if you were to directly use the “Media Management” dialog.
And since these relink operations are local only, this solution prevents one collaborator from accidentally changing the media mappings for the other collaborators.
Media Relinking workflows in Team Projects have a unique workflow compared with the standard relink workflow in Premiere Pro. In a collaborative environment such as Team Projects, each collaborator will likely have unique paths to the media used in the project. As such, a mechanism must exist to allow each collaborator to generate the unique paths they require so that their media is found when the project loads.
In Team Projects, using the “Media Management” dialog is how these unique Media Mappings (paths to the media location) are created. These media mappings are unique to the user’s computer and have no impact on other collaborators. Each collaborator establishes their own unique media mappings to ensure proper loading of media in the project.
Although the Media Management dialog workflow does provide a viable solution to this problem, it is the number one point of confusion for Premiere Pro users who are familiar with the more direct “relink” media workflow found in Premiere Pro. In fact, when the Premiere Pro “relink” method is used with a Team Project, the collaborator who performed the media “relink” is now able to see their media load properly, but all other collaborators will most likely see their media now appear as “offline”. This is because the Premiere Pro “relink” workflow is treated like an EDIT to the Team Project, and when this change is shared all media paths are updated.
Our new feature work for relinking media in Team Projects should greatly reduce the confusion around media linking. It is now in BETA and available for download in the Adobe Creative Cloud Desktop App under the "Beta Apps" section.
We hope you will try this new feature out and let us know what you think.
The Team Projects Team
We have received several reports where some individuals in the community are posing as Adobe Employees. These individuals are falsely representing who they are to gain your trust, and possibly access to your computer or personal information by offering to help troubleshoot issues.
Here are 3 Easy ways you can identify Adobe Staff:
➊ All Adobe Staff have a RED ADOBE BADGE below their profile picture and an Adobe logo after their username. This staff badge is visible on Adobe Staff profile pages, original posts and reply threads.
➋ Genuine Adobe emails are always firstname.lastname@example.org
➌ Adobe Staff will never ask you to share your passwords or sensitive information in the Adobe Community. Adobe employees will always direct you to communicate through an official Adobe channel to set up support sessions.
Report abuse or suspicious behavior to: email@example.com