Skip to main content
Known Participant
September 22, 2022
Question

Importing sequence from second editor creates duplicate master clips in my production

  • September 22, 2022
  • 2 replies
  • 748 views

Separate editors, both running Premiere 15.4.5 on different iMac Pros with Catalina/Mojave respectively. 

Working on a humngous documentary feature with 20,000+ media assets, and Premiere becomes so slow that it's unusable when they're all loaded in a single project.

So I wanted to try productions for the first time. I did, and successfully broke up my huge individual project into a production. My sequences preform fine now. 

The issue is that when I imported a sequence from the other editor into my production just now, it imported all of the media as new master clips. In spite of the media already existing in a project inside of my production, if I delete the newly imported duplicate masters, they disappear on the newly imported sequence. Obviously Premiere doesn't know they're the same assets. 

Is there a fix to this? Shared storage is not an option. 

Thanks for any insight!

This topic has been closed for replies.

2 replies

R Neil Haugen
Brainiac
September 22, 2022

That marvelous benefit of working within a Production works ... while working within a Production. Have you been through their manuals on using a Production? This may include information that will help you sort the dupes.

 

Premiere Pro Productions Introduction

Using Productions in Premiere Pro

Productions Workflow for Long Form & Episodic PDF

 

If you were working while sharing that Production, you wouldn't get this. That's ideally what you need to do ... use that Production collaboratively.

 

My partner is in Cape Town, I'm in western Oregon, we have a Production, and media for both that Production, and for several Team projects, living on Amazon S3 servers in London, and use LucidLink's amazing service to 'move' media and projects as needed within Premiere.

 

LucidLink is not like Dropbox or any other service I've tried. It creates a "virtual drive" on each connected computer. But doesn't sync the files to local service unless you "pin" them which would be useful if they are particularly large files.

 

As in ... Mo calls me on WhatsApp to tell me he's uploading a folder of media. Within a few  seconds, that folder appears in the LucicLink virtual drive on my machine. Within a few more seconds, I'm seeing filenames appear.

 

At that moment ... before they're completely uploaded from Cape Town to London! ... I can go into Premiere and Import that media into a project or sequence. As LucidLink does very 'smart' transfers of the data that Premiere would need as it needs it. And I can even start playback!

 

You do need 150Mpbs or better continual ISP speeds ... a ful gig is better. But 1080 ProRes is a dream over this system.

 

You can work by leaving the Production folder and projects on the virtual drive, and when necessary, "pinning" clips of assets. That tells LL to cache those files on the local system drives. In our experience, and from being on the LL Slack channels, that's only needed for 'heavy' files or for lower speed ISP service.

 

Neil

Everyone's mileage always varies ...
mjshadeAuthor
Known Participant
September 22, 2022

Thanks very much for your reply. For reasons of budget and the late stage of the edit, shared storage is not an option for my project. For that reason I am hoping that there is a way to share sequences between production/project files without creating the duplicate media issue. 

The other editor and I have managed to share sequences between each other in projects without creating duplicates by cloning our local storage, but the issue is that the project is so large that the program struggles with performance. Hence the switch to productions. 

mjshadeAuthor
Known Participant
September 22, 2022

Shared storage is not an option. 

 

Then how are you sharing media, today? 


The other editor's drive is a clone of mine. Same name, same file structure, same contents. When new media comes in, it is copied to both drives and imported to both projects. 

mjshadeAuthor
Known Participant
September 22, 2022

Note in case it helps - the other editor's drive is a clone of mine. Same name, same file structure, same contents.