Skip to main content
Known Participant
June 18, 2024

Clips have been duplicated in Productions

  • June 18, 2024
  • 13 replies
  • 1344 views

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)

This topic has been closed for replies.

13 replies

jamieclarke
Community Manager
Community Manager
November 4, 2024

Updating Status to Fixed in 24.5

Participating Frequently
August 29, 2024

It's working all right in version 24.6
Thanks!

Kevin-Monahan
Community Manager
Community Manager
August 23, 2024

Hi @10260154 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

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Todd_Reeder
Inspiring
July 8, 2024

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

Participating Frequently
July 5, 2024

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 .

Participant
June 19, 2024
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
Community Manager
Community Manager
June 19, 2024

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.

Participant
June 19, 2024

This solved it. Thanks!

R Neil Haugen
Legend
June 19, 2024

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.

Everyone's mileage always varies ...
Known Participant
June 19, 2024

Tanks @Todd_Reeder I appreciate your answer.

Known Participant
June 19, 2024

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?

 

R Neil Haugen
Legend
June 18, 2024

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?

 

Everyone's mileage always varies ...