Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Workaround for sequence importing between cloned drives no longer works — duplicated clips appear no matter what

  • Workaround for sequence importing between cloned drives no longer works — duplicated clips appear no matter what

    Posted by Nick Andert on August 27, 2014 at 4:41 pm

    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.

    Andrew Kimery replied 11 years, 8 months ago 2 Members · 5 Replies
  • 5 Replies
  • Andrew Kimery

    August 27, 2014 at 6:24 pm

    Which version of PPro CC are you running Nick?

    On early versions of CC2013 I had the media duplication problem but on the latest build of PPro CC2013 the problem seemed to be fixed. I was trading project files with up to 2 other machines and never saw any duplicate media. I would have my version of the project open, the other editor would give me their project file and then I wold use the Media Browser to import the sequence(s) I needed. The only time media would be added to my project was if they had a shot in their timeline that I didn’t have in my project (like some temp footage they’d added or something).

  • Nick Andert

    August 27, 2014 at 6:31 pm

    Whoa, simple as that, that did it. We’ve been importing with the import command this whole time, but dragging straight from the media browser does the trick. I wonder why there’s a problem with the other method when they’re ostensibly the same process.

    Thanks!

  • Andrew Kimery

    August 27, 2014 at 6:54 pm

    [Nick Andert] ” I wonder why there’s a problem with the other method when they’re ostensibly the same process.”

    I’m not sure. I do remember one time (and this was probably a year or so ago) someone from Adobe mentioning “Oh, try using the Media Browser instead of the Import command”. I don’t remember what exactly the statement was in reference to, but it got me thinking that maybe something different is going on under the hood so I always try to remember to use the Media Browser when bringing anything into PPro.

  • Nick Andert

    August 27, 2014 at 6:58 pm

    Huh. I’ll do the same from now on. Very helpful, thank you!

  • Andrew Kimery

    August 27, 2014 at 7:44 pm

    Hey, no problem, it’s what the COW is for.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy