Using Productions

Even if a project is locked by another editor and is in a read-only state, you can open it to do the following tasks:

• Load clips and sequences into the Source Monitor
• Set In/Out points and perform edits from the Source Monitor
• Play sequences in the Timeline and Program Monitor
• Export media, XML, AAF, EDL, etc.
• Copy project items into a project that is open Read/Write

Yes. If you are working in a Read-Only project, if the user who is editing the project saves new changes Premiere Pro shows you a notification.

• In the Production panel, the name of the project appears in italics.
• In the Project panel, a yellow triangle appears next to the project.

These notifications indicate that you are no longer looking at the most current version of the project. 

To see the new changes:

• Right-click the project in the Production panel and select Refresh.
• To refresh all projects in a production, select File > Refresh All Projects.

No. Every user with Premiere Pro can take advantage of productions. Collaborating with multiple editors requires a networked shared storage solution.

While solo editors can use productions and benefit from some of the features, it is up to each editor whether they prefer to work in a single project file, a production, or a Team Project.

No. A Team Project can be saved as a stand-alone project file and then added to a production, but not the other way around.

Productions replace Shared Projects, but the Shared Project functionality remains in Premiere Pro with the concept of a Project Shortcut. With a Project panel active, choose File > New > Project Shortcut. Project Shortcuts can be useful for editors working in a single project but still wanting to link to commonly used projects. Project Shortcuts can be created inside projects in a production. Although most workflows would benefit more from using the Add Project command to bring the project inside the production.

No. Individual editors can use productions while storing them anywhere they would normally keep a single project file. A networked shared storage solution is only required for collaborating with other editors in the same production.

At a basic level, no. Project files created inside a production have the same .prproj extension and are fully complete Premiere Pro project files. They can be moved outside of a production and opened as a stand-alone project.

 If clips in a sequence link to master clips in a different project, you cannot see those master clips when the project is opened outside of the production. Use the Generate Master Clips command if you want the project to exist as a stand-alone project.

Yes. Use the Add Project command to add your project file to your production. During this process Premiere Pro updates the project file if required.

Yes. In the same way that a stand-alone project file can be opened on either macOS or Windows, productions support both systems at the same time. The first time opening a production on a new platform you may be asked to confirm the scratch disk location. Make sure to set it to the same location on the server and Premiere Pro handles the translation of drive mounting between the two operating systems.

If the Renderer chosen in File > Production Settings > General is not available on one of the systems, Premiere Pro chooses the next best renderer automatically. For example, if a production is created on Windows with the CUDA renderer chosen, when it is opened on macOS Metal is used automatically.

Only one production can be open at a time, but there is no limit to the number of productions you can create or use. Choose File > Open Production to see a drop-down list of recently opened productions or select recent productions from the list of recent items on the Welcome screen.

This file is used by Premiere Pro to store production settings and other information. Do not move or modify this file.

Ingest settings are disabled in the Production Settings dialog because they are designed to apply to a single computer at a time. To use Ingest Settings, first close your production and create a stand-alone project that is saved outside of the production folder. Set your desired Ingest Settings and import your media. After all ingest operations have finished, save your project and close it. Open your production and use the Add Project command to bring the project file into your production. You can now use the ingested clips normally.

Do not store any other files or media inside your production folder. The Production panel only shows folders and project files, however, Premiere Pro scans all files placed in the production folder and so there could be performance issues.

Adobe recommends that you do organizational work inside the Production panel. Operations done on disk (moving files, renaming, etc.) are reflected in the Production panel, doing those operations inside Premiere Pro is the best option. For example Finder or Explorer may let you rename a project file that another editor is working on, whereas Premiere Pro would not allow it. Always avoid duplicating project files in Finder or Explorer.