Fix the 'recovered clips' bug
Everytime you copy or import anything from one project to another premiere creates automatically a bin called 'recovered clips' which is very annoying.
Then, you edit through all you clips and in your secuence if you choose to 'show you in project' it goes to the 'recovered clips' bin and not to the original bin that has your material.
This is a huge bug.
Manuel Tsingaris commented
Please, Adobe, help us out on this. The clip count in a project just grows and grows with this flaw in the import of sequence function.
Travis DeCola commented
Our projects become messy and cumbersome to use very quickly because of this!
Donald Hill commented
Bumping into this hassle more and more.
Ronald Hill commented
We're still running into this on Productions and it's extremely frustrating. It seems to be more likely to happen if the footage was grouped in a separate project. Or nested in a separate project.
Christian Simpson commented
This issue has been so frustrating. It defeats the whole purpose of productions.
Rebecca Fortuna commented
I just found this resource which might help you guys out in some way. http://www.thepremierepro.com/blog-1/tag/recovered+clips
Jeff Boyette commented
I've been working in Productions on my current long form doc with hopes of these sort of issues. Thankfully I have not been getting this error when trading sequences with my assistant, but it still occurs occasionally when over cutting a clip from one project into a sequence in a different project. It only happens occasionally, and I haven't noticed a pattern to explain it. In most cases I've been able to eliminate the duplicates by cutting and pasting from one sequence to another across projects rather than over cutting from the source window.
Thomas Baumann commented
I agree with this request. It's a very frustrating situation. Using Productions has been a great way to manage media and sequences for complex clients but this bug works against my efforts to keep imported assets clean, organized and duplicate-free. If it can't be fixed, at least some information on why it sometimes happens would be helpful. I can build work-arounds into my work flow to avoid the situation if I know what triggers it. Thanks!
Adamantios Petritsis commented
Any updates on this issue?