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.

  • This project contained a sequence that could not be opened. No sequence preview preset file or codec could be associated with this sequence type.

    Posted by Joshua Weiss on August 18, 2014 at 4:08 pm

    This error seems to happen all too often. I am tired of doing the whole uninstall and reinstall of Adobe. I’ve done the adobe cleaner stuff also.

    HP Z600 Workstation
    2 Intel Xeon E5645 processors @2.40 GHz
    16gb ram
    Windows 7 Ultimate with SP1
    Nvidia Quadro FX4800
    G-Tech external raid connected esata with 156gb free
    Primary OS drive has 60gb free
    Footage shot on Canon 5D M2, 5D M3, and 7D

    Richard Clabaugh replied 9 years, 7 months ago 11 Members · 14 Replies
  • 14 Replies
  • Tim Kolb

    August 18, 2014 at 4:33 pm

    Hey Josh,

    Are you still using CC or have you moved to CC 2014?

    Adobe posted a fix for this on Windows…though i think you had to run the fix every time you updated CC.

    https://helpx.adobe.com/creative-cloud/kb/unable-login-creative-cloud-248.html

    Have you run this fix?

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Joshua Weiss

    August 18, 2014 at 4:47 pm

    Unfortunately, I have done this step a couple times over the course of the past couple months. I will attempt it again. That link also showed the solution for CONSTANTLY having to login. I have to login almost everytime I use any Adobe application which is ridiculous. I have 4 different Adobe accounts that are used on 5 or 6 different computers. I have the same issue on every system with every account. When I deal with Adobe support, they aren’t much help. I don’t know why they never sent me to the link you posted.

    Maybe this will fix at least one of my Adobe issues.

  • Tim Kolb

    August 20, 2014 at 2:07 pm

    [Joshua Weiss] “Unfortunately, I have done this step a couple times over the course of the past couple months. “

    Each update does cancel it out…though it’s supposed to be fixed in CC 2014.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

  • Joshua Weiss

    August 20, 2014 at 7:16 pm

    I think I may have finally figured out why my CC experience has pretty much been hell from the beginning and what the issue is with this current situation.

    When I first purchased CC, I was instructed by the Adobe salesman to pay for an Adobe team membership instead of a regular subscription. I don’t really know why he sent me that direction except maybe cause it was a more expensive route than the alternative (not too happy about that). Well, a few months into this, I realized that I was getting charged a good bit more than I needed to be and spoke with CS. They ended up cancelling the team membership (I actually had 3 different teams – one for the production company, one for the television ministry, and one for the church). They set me up with regular subscriptions and I have been that way ever since.

    Unfortunately, I think they screwed up with how they cancelled the other memberships so my computer is constantly confused whether I am using a current or expired adobe ID. Even though I have been paying for 3 every month, the system on their end shows an expired ID.

    Apparently, there are certain elements within the softwares that are not accessable on a trial membership such as certain codecs. So, I may work on a project when the system things I have a valid ID, and then later open up the exact same project and it thinks I am on a trial. At that point, those elements are no longer able to be used so it gives me the sequence errors and other compounding problems.

    I’m pretty frustrated over the whole thing because they have really made my life difficult since I reluctantly signed up for CC. I really would be happier if I could just buy the master collection and choose to update down the road when I feel rather than my computer constantly looking to destabilize what has been working just fine.

    Hopefully my issues are over but I am not too confident that they have it together even now. I guess we will see.

  • Matthieu Mailhé

    October 31, 2014 at 8:44 pm

    Fortunately, there is a simple workaround : set yourself the right settings / codecs parameters in the textfile of your .prproj

    This is how to do it :

    1- Find an old of your .prproj that you know is functionnal on your system (a “valid” project)
    2- Open it in a text editor (text edit in my case, on mac)
    3- In the text editor, locate this words (with the command “cmd-F” on a mac):

    MZ.Sequence.PreviewRenderingPresetCodec>

    The few lines below this part are the references for codec and preview settings. In my case, they look like this:

    EncoderPresets/SequencePreview/795454d9-d3c2-369d-9874-923ab14b7018/P2 1080i-1080p 50Hz DVCPROHD.epr

    4- copy those few lines
    5- Locate the same spot in the .prproj that you can’t open.
    6- Replace the few lines by the ones from your “valid” project
    7- Save in the text editor and close it.
    8- Open your now “valid”.prproj

    This is only a workaround and doesn’t adress the real issue. But still, when you have to meet tight deadlines, it can save the day.

  • Cansen Yilmaz

    November 20, 2014 at 3:25 pm

    Hi matthieu Mailhé,

    Came across this problem today out of the blue 🙁 Except when I open up my working or non-working prproj file in TextEdit I get jargon that’s not understandable and using Apple-F search I can’t find the reference

    MZ.Sequence.PreviewRenderingPresetCodec>

    anywhere in the script? Any Ideas why? This is what i’m looking at, am I doing something wrong?

  • Matthieu Mailhé

    November 20, 2014 at 6:45 pm

    I think I get your problem :

    The .prproj opened with TextEdit should read “real” english words, not the strange characters/Elvish paragraphs you sent attached and looks like (:°) @_@
    It’s because TextEdit misinterprets the text in your .prproj

    I am not a text expert but as I understand it, youd TextEdit is not in Unicode (UTF-8) mode. You can go in “Format” and change the settings of the document to Unicode (UTF-8) or you can set the default opening encoding to UTF-8 or UTF-16 in TextEdit Preferences/Open and Save.

    Of course, try all that on a copy of your original .prproj so that in case you accidently mess your .prproj in TextEdit you still have a clean copy.

    Let me know if it works !

  • Neiman Catley

    January 27, 2015 at 11:23 am

    You ROCK!!! This absolutely worked. I don’t need to do this often so I don’t mind having to do it every time. THANKS!

  • Mazda Alinia

    February 25, 2015 at 6:14 pm

    Hey Matthieu Mailhé,

    I still can’t open my prproj file in text edit even after changing the format to UTF-8 or UTF-16. u’m using CC2014. any solution?

  • Ben Brenner

    June 22, 2015 at 11:39 pm

    This didn’t work yet… but a hint. In mac the file didn’t open right in Atom, but worked great in TextWrangler

    Here’s the grep search:
    EncoderPresets\/SequencePreview\/.*

    search and replace with
    EncoderPresets/SequencePreview/b39d0224-c728-4ee7-9886-ccf837b5247f/DNX 290 1080p 59.94.epr

    or whatever you found in your working file.

    Hope this helps.

Page 1 of 2

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