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

[Jeremy Garchow]

What version of Pr?

Where did you make the proxy files?

[Roger Kean]

Premiere CS5, the proxies are generated in camera by the red one

[Jon Barrie]

If you are crossing platforms from Mac to Win there could be issues in proxies there. Example being some QT formats that are AIC (Apple Intermediate Codec) don’t work on Win. ProRes does with the latest QT or the ProRes decoder installed but that doesn’t include others like AIC XDCAM/P2 etc.

– JB

Jon Barrie
Adobe Video Solutions Consultant ANZ
Jon’s YouTube Tutorial Page
follow Jon with twitter

[Roger Kean]

All the computers I attempt to open it on are all mac. The only difference that I can tell between them is the original computer is running Snow Leopard and the ones I try to open it on are running Lion. Any advice on how to overcome this would be helpful

[Jeremy Garchow]

One potential problem is that Pr uses red native media and is having trouble reconnecting.

The other is a potential capture card conflict.

Do you have a capture card on one machine and not the other?

[Roger Kean]

Both machines aren’t using any capture cards. They are just using external LaCie hard drives with firewire to edit. Ive narrowed down what I think the issue is. I think it has to do with one being snow leopard and the other running lion. Ive found that I can import the sequences individually and reorganize the whole project. So that is what Im going to do. Faster and easier than starting over. Thanks for lending a hand

[Terence Kearns]

I’m experiencing exactly the same problem. Premiere CS6. The sequence in question is a series of PNG images. The original project was created on windows 8 and the computer attempting to open it is Lion (iMac).

[Terence Kearns]

Still have not solved this problem.

The latest is that I have tried exporting a final cut XML file from a project on the mac (CS6) and importing that project XML file on the PC. It produced exactly the same error.

[Jeremy Garchow]

Terence-

Did these projects both originate in Pr CS6?

Did you use any “non native” sequences (like AJA or Blackmagic sequences) when you created them?

Jeremy

[Terence Kearns]

In all cases, the sequences were originally created in ppro cs6.

I have read the entire thread at
https://forums.adobe.com/thread/478332

and the conclusion was that you could fix the problem simply by using Microsoft AVI as the preview codec for all your sequences. This didn’t work for everyone, and I can confirm that this will not fix it. Some people say that the trial version (which I am using) will not have all the codecs installed. HOWEVER, I ran some experiements using only the P2 DVCPRO codecs. The proj files are only interchangeable between my iMac and my Windows PC when I select DVCpro 50 as the codec (standard def). Anything else will cause that error to manifest on the system trying to open the project file when the other system created the sequence. IE, if I add a seq on the PC, the mac won’t open it. If I add a sequence [even with the exact same spec] using the mac, then the PC won’t open it…. doesn’t matter if the codecs chosen are identical (ie. dvcproHD).

Of course all my stuff is HD, so simply using an SD codec is not acceptable. I would like to find a solution before settling on CS6 when the trial ends. I’ll be coming over from Sony Vegas if it works out. Vegas is still a better tool IMO, but it doesn’t run on the mac.