project file unreadable after HD transfer

[Tim Kolb]

Why don’t you fill us in a little more on the procedure involved here…was the drive the C drive in the first computer? Was it the C drive in the second? Did you install PPro on the second computer? Are the project icons coming up as associated with PPro?

Have you attempted to import the projects into another project?

Fill in some blanks with your situation.

Before we blame Adobe for something weird with your hard drive changeout, I’d like to know a bit more…

(and AE and Encore don’t associate with projects in the same way, so that isn’t necessarily an indication)

TimK,

Kolb Syverson Communications,
Creative Cow Host,
2004-2005 NAB Post Production Conference
Premiere Pro Technical Chair,
Author, “The Easy Guide to Premiere Pro” http://www.focalpress.com
“Premiere Pro Fast Track DVD Series” http://www.classondemand.net

[Patrick Doan]

–
the HD that i moved from my friend’s computer was a slave disk. there were no project files on the master disk (SATA). the disk is a SATA Western Digital 160G (#WD1600JS).

–
in my new computer, this disk is also placed as a slave (master disk is a WD2500JS SATA).

–
i have installed the same adobe premiere pro build from the other computer to this computer that i am using now. the icons are coming up associated with premiere, no problem there.

–
i get the warning (as mentioned in my first post) when i attempt to open the file in premiere. i also tried the import option, and get the same message.

–
i should mention that the drive letter assigned to the slave drive is different then it was when it was installed on my friend’s computer.

i hope that was clear! i appreciate the help.

[Tim Kolb]

Has the project ever crashed?

Have you tried to load one of the backups?

It sounds like the file is just corrupt. It does happen from time to time. With all software, I might add.

TimK,

Kolb Syverson Communications,
Creative Cow Host,
2004-2005 NAB Post Production Conference
Premiere Pro Technical Chair,
Author, “The Easy Guide to Premiere Pro” http://www.focalpress.com
“Premiere Pro Fast Track DVD Series” http://www.classondemand.net

[Patrick Doan]

i would be hard pressed to believe that of all the files on my HD, that these premiere project files would be corrupt, among other, perhaps more, susceptible files which would be prone to truncation/corruption (no pun, heh).

i’m just speculating, but i think the problem has do with the way premiere handles file associations/linkage in a project’s library.

i’m going to reinstall the drive on my friend’s pc, and see what happens.

[Tim Kolb]

If it was file linkage, the project would open but the assets wouldn’t link.

I’m not saying that everything is perfect with PPro, but if the project won’t open, something is wrong with the project file itself, not the asset linkage.

As I asked before, has the project ever crashed…and have you attempted to open a backup?

I have a feeling the project file might be shot, but PPro save project backups. You would have to relink, but it’s way faster than re-doing the entire thing.

Try the backup route before you swap the drive again. I don’t think this is an Adobe problem.

TimK,

Kolb Syverson Communications,
Creative Cow Host,
2004-2005 NAB Post Production Conference
Premiere Pro Technical Chair,
Author, “The Easy Guide to Premiere Pro” http://www.focalpress.com
“Premiere Pro Fast Track DVD Series” http://www.classondemand.net

[Patrick Doan]

prior to the removal of the disk, the projects never crashed on me, and i always made incremental backups. i tried opening the backups, but i still receive the same error message.

i think i might have to redo the project. 🙁

[Peter Corbett]

Patrick,

I have had this once or twice. My experience is that once that project file is “corrupt” it is kaput. You will have to use an auto-save version if available. I set my autosave period to five minutes.

Peter Corbett
Powerhouse Productions
Australia
http://www.php.com.au

[Tim Kolb]

Was PPro 1.5 on your friend’s machine the same version as yours?

There has been an update to 1.5.1 that has a few changes. There may be an issue there.

Otherwise, I’ve seen times where a maladjusted PC clock/calendar on yours/your friends PC might create files with some date that according to the new machine hasn’t existed yet…that can create some interesting and varied issues.

Have you loaded the assets into a new project so you know they’re all good?

…again, I’m almost 100% positive this is something besides an Adobe issue.

TimK,

Kolb Syverson Communications,
Creative Cow Host,
2004-2005 NAB Post Production Conference
Premiere Pro Technical Chair,
Author, “The Easy Guide to Premiere Pro” http://www.focalpress.com
“Premiere Pro Fast Track DVD Series” http://www.classondemand.net

[Tim Kolb]

[Peter Corbett] “I have had this once or twice. My experience is that once that project file is “corrupt” it is kaput. You will have to use an auto-save version if available. I set my autosave period to five minutes.”

He said his backups all act the same way.

TimK,

Kolb Syverson Communications,
Creative Cow Host,
2004-2005 NAB Post Production Conference
Premiere Pro Technical Chair,
Author, “The Easy Guide to Premiere Pro” http://www.focalpress.com
“Premiere Pro Fast Track DVD Series” http://www.classondemand.net

[Steve Freebairn]

This might be too painfully easy, but have you installed the 1.51 update on your computer? If you are not using the exact same or newer version of the software then it wouldn’t work. Hope that helps. By the way, I’ve transferred all kinds of projects over email, hdds, flash drives, and never had a problem when I was using the same version.