Clips have been duplicated in Productions

[Exquisite_build5C92]

When you are working on a Production in which there is one project with imported media, another project with media sync via multi-camera clips, and other projects with timelines. Sometimes in these editing projects, when you open them, the multicam clips or the video clips are imported directly, and if you reassociate the source clips, they disappear from the project because they connect with the real source, which in fact was already there when you created the editing.
The error therefore seems to be that the connection with the production project, which is the origin of the clips inserted in a timeline, is lost, but it is not known why this happens. It's obviously a Premiere bug, but no idea why it happens.

Translated with www.DeepL.com/Translator (free version)

[Exquisite_build5C92]

Using Premiere Pro 24.1 on iMac Pro and local storage.

[Kevin-Monahan]

Hi @Exquisite_build5C92,

Thank you for the bug report. The team may need more info from you. See: How do I write a bug report?

This might be "as-designed" behavior, but I'm not sure. @mattchristensen might have an idea.

I hope the team or the community can help you soon. Sorry for the frustration.

Thanks,

Kevin

[Todd_Reeder]

Hi @Exquisite_build5C92 

We have a fix coming soon that should address this.  It is currently in our beta builds if you want to have it now.  Reminder, beta builds can install alongside your release build.

[R Neil Haugen]

If you reassociate clips within a Production, you can end up with issues like what you describe. There are some frustrations with say trying to Match Frame to a clip that's in another project in Productions at times ... it currently isn't possible.

Why are you reassociating them? To get around the "Match Frame" problem?

[Exquisite_build5C92]

I don't reassociate clips because I want to or as an initial method. I reassociate clips because when I match frame it doesn't go to the source clip in the production project where it was ingested but it goes to the clip it has duplicated. Why have the source clips in the project I have just for the edits if I already ingested them in the other project from where I have included a cut in a timeline that is in the editing project?

[Exquisite_build5C92]

Tanks @Todd_Reeder I appreciate your answer.

[R Neil Haugen]

I'm a total on Productions user ... but that issue with "match frame" has for me been the one real irritant of Productions workflows.

I mean, the whole point of separating asset storage from asset usage is to speed your workflows along, right? Yet ... editors do need to get back to the original clip at X frame a lot.

And we haven't been able to do that in a Production.

So yea, hopefully that's being solved.

[Jordan38143198l8qz]

Hello everyone! My team uses Premiere Production for all of our projects and recently just switched over to Premiere 24 for our most recent project.

Since switching, we've been having an issues where when we cut a MultiCam into a sequence the raw clips from the MC are populating in the sequence. In all other versions of Premiere, the sequence would just reference the raw clips in the original MC project and not copy them over. (I've attached a video to illustrate what's happening)

Has anyone else encounter and/or know a solution. Thank you all!

[jamieclarke]

This issue has been fixed in the latest update, Premiere version 24.5.  Please update and let us know if you are still having problems.

[Jordan38143198l8qz]

This solved it. Thanks!

[El Rugido 338430147uufk]

I have tried the latest beta build (24.6.0 comp 47) and the problem remains.  It keeps duplicating clips, folders etc whenever you copy from one project to another a sequence which contains a multicam .

[Todd_Reeder]

Hmm....that should be fixed in 24.6....let me take a look

[Kevin-Monahan]

Hi @guille GM & @El Rugido 338430147uufk,

Are you still seeing the issue in the stable build of 24.6? Please let the developers know. I hope so! Take care.

Cheers,
Kevin

[El Rugido 338430147uufk]

It's working all right in version 24.6
Thanks!

[jamieclarke]

Updating Status to Fixed in 24.5