-
Workaround for sequence importing between cloned drives no longer works — duplicated clips appear no matter what
So we’ve struggled massively with the perennial Premiere problem of having multiple editors working on the same project using cloned drives. To say sharing sequences is a nightmare is putting it mildly. We’re on a feature documentary and our projects are massive, so we’re importing each other’s sequences praying to god each time that it works without duplicating the master clips. The previous workaround for this if I wanted to, say, import a B drive sequence onto an A drive sequence, would be to dupe the B drive project file, open it on A drive with B drive disconnected, reconnect all media in the project to their A drive counterparts, save the project, open A drive project, and import the desired sequence from my duped B drive project. As much of a headache as that was, at least it tended to work.
Now, I duped the B drive project, and to my surprise, it automatically relinked to everything on A drive without even asking. Great, right!? It seems to now ignore the top-level name difference (beyond the A and B drive names, the drive structure is precisely the same) and is able to relink automatically without asking from the main directory up. Except when you import sequences from that automatically reconnected project, it now dupes every single clip in the sequence. I’ve been pulling my hair out trying to find a way around this, as it’s effectively grinding our entire project to a halt right now. Was the automatic reconnection a feature that was just added with an unintended consequence? Is anyone else experiencing this problem, and have you found a way around it?
For all it’s foibles, I really think Premiere is a great platform, but this one caveat of insisting that clips in a sequence reference master clips in the project panel as opposed to simply directly referencing the clips on the drive is crippling it to the point of madness.