Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro This project contained a sequence that could not be opened. No sequence preview preset file or codec could be associated with this sequence type.

  • Daniele Bonazza

    September 30, 2015 at 3:22 pm

    You saved my a.. life!
    Thanks

  • Andreas Urra

    May 8, 2016 at 10:44 am

    Hi, I came across this problem today. It is also wort mentioning that Premiere (CC 2015) had prompted me today that I had to sign in or run in trial mode. Out of the blue. I hadn’t changed anything since the evening before.
    After signing in, I could not open the project I had worked on only 14 hours before. I then quit the application. reopened it, opened an empty template project of mine, closed that and then opened the real project again. This time there were no problems. Maybe this works for someone else, too.

  • Laurence Yates

    October 10, 2016 at 6:41 am

    THANK YOU! I was having a mini heart-attack.

    I had exactly the same problem – signed out of CC the next time I opened the project and asked to use trial mode. I created a new project, saved it, then opened the old project file.

    As an aside, I also changed the Memory preference from “Performance” to “Memory” (may or may not have made a difference).

    Laurence Yates
    Motion Graphics Artist and Illustrator
    Creator of QuickDraw – https://aescripts.com/quickdraw/
    https://www.notbyhalf.com/

  • Richard Clabaugh

    October 11, 2016 at 5:49 am

    Same thing exactly here! In the last 3 days Premiere Pro has prompted me 3-times to sign in to stop running the “trial” version of the program.

    THEN – today — It gave me the sequence read error message when I tried to open my project.

    I took the drive to another machine in my office and the project opened with no problem at all. Saved it, walked it back to the first machine, and it opened fine – no problem.

    No idea what’s going on, but thought it interesting we’re having the same problem and symptoms.

Page 2 of 2

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