Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Disappearing bins

  • Disappearing bins

    Posted by Doug Swift on July 2, 2013 at 12:31 am

    I’ve seen mentioned that some users have had an effects bin or two disappear upon starting up PP. When I started up today, ALL of my bins were gone, along with the 40 or 50 files (or more) that were in them. The only files I still have are the ones from the bin I was working from, and the bin itself is gone. Only the files themselves are left. Anyone ever hear of anything like this, or have any ideas on what happened? The assets aren’t “gone,” of course, and I can obviously reconstitute the bins, but what a pain.

    I’m using CS6 on Windows 7.

    Many thanks,

    Doug

    Doug Swift replied 12 years, 10 months ago 2 Members · 2 Replies
  • 2 Replies
  • Angelo Lorenzo

    July 3, 2013 at 4:14 am

    Knowing how the save files of Premiere work, I’d venture to say it’s a corrupted save file in some way or form.

    Try importing this current Premiere Pro Project file into a brand new empty project. This does some housekeeping that may solve the issue. My best guess anyways.

    ——————–
    Angelo Lorenzo

    Need to encode ProRes on your Windows PC?
    Introducing ProRes Helper, an awesome little app that makes it possible
    Fallen Empire Digital Production Services – Los Angeles
    RED transcoding, on-set DIT, and RED Epic rental services
    Fallen Empire – The Blog
    A blog dedicated to filmmaking, the RED workflow, and DIT tips and tricks
    Can your post production question fit in a tweet? Follow me on Twitter

  • Doug Swift

    July 3, 2013 at 11:53 am

    Thanks for the help, Angelo. Luckily it was an easier fix than this. The bins were drilled down some how, and I was able to find them by clicking the little folder in the upper left hand corner of the panel. Don’t know how it happened, and it was very disconcerting, but luckily, once someone on the Adobe forum pointed it out, an easy fix.

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