Inspiring

Answered

Migrating a project into a Production - Workflow guide?

Forum|Forum|11 months ago
February 25, 2025
3 replies
1676 views

Is there a workflow guide for migrating a project into a Production? I appear to have done it wrong.

I am migrating a giant project into a Production. I dragged the sequences into several new projects, then dragged the footage into new projects. When I try to "Reveal [a clip] in Project", it wants to open the original, huge project from which I dragged these elements. I can manually open the correct new project, and it reveals the correct clip in that project; but I can't do that for all 30,000+ assets in this production.

Is there a way for me to tell the Production to look inside itself for all the correct source clips? Or, what's the proper way to turn a project into a Production?

How to

Correct answer mattchristensen

@KazuTa the key is to keep all the projects open as you do this initial breaking apart. Yes you'll end up with a lot of projects open, and you should do File > Save All often! If you don't keep all the projects open, they won't "see" the clips move and therefore you'll have the experience you describe of clips in a sequence not knowing that their source clips have moved. Also, you should be dragging the items from project to project, do not copy/paste.

See p. 73 of the Best Practices Guide (Working with Productions > Migrating an Existing Project to a Production > If your work is a single project file): https://adobe.ly/PremiereProGuide – click "Get File" on that link to download the PDF.

The whole chapter "Working with Productions" is an in-depth documentation of how the feature works.

A

Alain D.

Known Participant

Hi @KazuTa ,

I know I'm a bit late to the party, but this guide from Jarle Leirpoll is what I read before diving into my first Production workflow. He does raise a few known caveats and a few do's and don't's.

--Alain

K

KazuTaAuthor

Inspiring

@Alain D. Thanks for this. Reading it let me know that multicam sequences will not move to another project when I move a sequence with multicam sequences in it into another project. Unfortunately, the editors where I work use lots of Nested Sequences:

Productions and nested sequences

Moving a sequence that contains a nested sequence to another project in the Production will copy the nested sequence to the new project. Yes, nested sequences will be copied, not moved, when you move a sequence containing a nested sequence.

This can possibly create a mess—unless you actually want a copy—so beware. It’s probably safest to delete the old instance after the copy has been made. Or just avoid moving nested sequences around too much.

[Unfortunately, our Nested Sequences are more than likely reused in multiple sequences throughout our old project, so this likely isn't a possibility for me.]

If you only use nesting inside one project, you’ll have no problems. It’s when you start moving them you create chaos.

As Matt Christensen, who was on the team that developed Productions, explains it “This is intentional, and prevents Inception-like circles of nesting being formed and needing to be updated and conflicts resolved.”

A little hack from Paul Murphy is to change the nested sequence into a multicam ([select the sequence in the Project panel, "Open in Source Monitor", then] right-click [in the Source Monitor] and choose [Multi-camera / Enable]. This ensures that changes made to it will update across projects. It’s not recommended by Adobe, so use this method at your own risk.

A

Alain D.

Known Participant

@KazuTa , my pleasure. But the duplication problem is with nests, NOT multicams, right?

FYI, I used multicams in 3 different productions so far and they work great, but perhaps I am misunderstanding your need. Here's how I do it:
- 1x Project, "Multicam" where the interviews and multicams live

- 1x Project, "Edit" where the edit lives

- 1x Project, "Archive" where I copy the previous edit version to, so that my "Edit" project only has my main edit/sequence.

When I initiate my first edit in my Edit project, I use the "Multicam" project as the source "bin" if you prefer, to build my edit. From that point onwards, if I match any given multicam frame in my sequence, the associated multicam will pop in the Source Viewer; and if I match that again, it will open the "Multicam" project (if not already open) and show me where it resides in the project (or "bin").

There are no duplicates, no copies that get created this way. Even after copying the sequence to the "Archive" project before bumping up by +1 my version number on the edit to be updated.

With nests though, that's another story. Duplicates of the said nest will appear as explained by Jarle in the section you brought up. So, taking my previous example again, say there's "Nest_1" in my edit, and I copy that edit in my "Archive" project, 2 items will appear as I paste the sequence: the sequence itself, and "Nest_1". After a few iterations of this, as Jarle said, "it gets messy".

HTH --Alain

mattchristensen

Correct answer

Community Manager

@KazuTa the key is to keep all the projects open as you do this initial breaking apart. Yes you'll end up with a lot of projects open, and you should do File > Save All often! If you don't keep all the projects open, they won't "see" the clips move and therefore you'll have the experience you describe of clips in a sequence not knowing that their source clips have moved. Also, you should be dragging the items from project to project, do not copy/paste.

See p. 73 of the Best Practices Guide (Working with Productions > Migrating an Existing Project to a Production > If your work is a single project file): https://adobe.ly/PremiereProGuide – click "Get File" on that link to download the PDF.

The whole chapter "Working with Productions" is an in-depth documentation of how the feature works.

Kevin-Monahan

Community Manager

Excellent @mattchristensen! Thank you.

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

K

KazuTaAuthor

Inspiring

I found Edit/Reassociate Source Clips, which is working beautifully with my footage and sound. I am selecting all my dailies sequences for a particular year, then Reassociating footage & sound to the appropriate projects.

How do I Reassociate Source Clips for archival, music, sound effects, GFX? Those are used randomly in random sequences.

K

KazuTaAuthor

Inspiring

It seems Source Clips got Reassociated for the dailies sequences I selected; but the source clips are not reassociated in any of the hundreds of the edit sequences in this Production. Someone please help! Drowning here.

Kevin-Monahan

Community Manager

Dividing up the project was quite fun. The only problem is that there's no way I can Reassociate Source Clips to each footage, sound, music, SFX, GFX, and archival project for each of the hundreds of sequences in the Production. That would be thousands of steps.

I'm attempting to leave a giant "ASSETS" project and just divide up the sequence projects. The sequence projects seem to be the slow ones.

Is there a way I can break up the "assets" (into FTG, SND, MX, SFX, GFX, ARC) and maintain the Source Clip associations? That's the main thing I need, is for "Reveal in Project/Production" to continue to work.

I'm pretty sure you can. What have you tried so far. Have you made projects for each of these items yet? Any way you look at it, it's going to be an effort. Sorry about that.

Cheers,
Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio

Productions and nested sequences

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded