-
reconnecting render files to duplicate projects?
We have a group of six people who use Premiere Pro to collaborate on the production of a large quantity of short videos. We all work in the same physical location and edit off of a shared storage volume. Our workflow is that one editor handles a 1st pass assembly edit, then one editor add markers to indicate where images and graphics need to be inserted, a second editor adds even more markers, then another editor turns the marker notes into motion graphics by importing AE comps, then it goes through a couple rounds of revisions and finally onto color correction. Along the way, whenever a new editor gets involved in the next phase of production, he or she duplicates a Premiere project file (which for us contains typically anywhere from four to ten different sequences) and includes his or her initials and what stage the project is in in the duplicated project file name. This has worked well for us, except for one snag. Many of the videos have complicated motion graphics, which must be rendered in order to play at the normal frame rate (these clips have a red line over them in the timeline). The motion graphics editor renders these during her edit, but, once her project is duplicated by the next editor, the render files files don’t connect to the duplicated project. The next editor can go ahead and render, but that can take some time (often at least 30 minutes). From what I understand, each sequence has to be rendered individually, and the machine can’t do anything while Premiere renders (there’s no background rendering). Is there any way to associate render files with a duplicated project that has a slightly different file name? If not, we can just continue with the current course of having editors re-render at each of the later stages of production, but we don’t want a workflow with a single project file where we don’t duplicate any project files.
-
4 Replies
-
I should mention that we did attempt to use the Project Manager to duplicate projects and selected the option to include Video and Audio Previews, but, even with just the sequences selected in the Source window of the Project Manager dialog box, it still duplicated the bulk of our media assets into the duplicated project folder, which isn’t a viable workflow for us because we often have six or more duplicates of a project file during the whole production cycle, and duplicating all the media takes just as long as re-rendering.
-
Hi Steve,
Just go to file > project settings > Scratch disks and make sure the video preview location is the same on every machine involved in the project.
But that may put too much overhead on that drive array, depending on your setup.
Vince
Vince Becquiot
San Francisco Bay Area
-
Vince– Thanks for the reply. Unfortunately, I don’t think your solution can work. When launching the duplicate project file (with the slightly amended file name), Premiere creates a new folder in the folder “Adobe Premiere Pro Preview Files” folder based on the duplicated project file name. When I go to Project Settings->Scratch Disks and set the preview file location for the previous editor’s preview file folder, save the project, and relaunch, it still doesn’t work (the render bar is still red and the previous renders haven’t connected to the new project file). What Premiere does is, within the previous editor’s preview file folder, create a new “Adobe Premiere Pro Preview Files” folder and then another folder based on the new project name within that. I don’t think you can trick Premiere into connecting render files from an original project to a duplicate project with a slightly different project file name. –Steve
-
Interesting, what if you did a “save as” instead?
Vince Becquiot
San Francisco Bay Area
Reply to this Discussion! Login or Sign Up