PPro cs6 not reading *.psd files from Photoshop cs6

PPro cs6 can and does read Photoshop cs6 *.psd files just fine on my laptop. But... laptop is more than five years old and is dying. So I build a new desktop:

Win8.1 64bit
Intel i7-4770K processor
ASUS Z87 Expert board
16GB memory
C: drive is an SSD, Samsung 840 EVO, 250GB
D: and E: are WD 1TB SATA 6GB/S 7200rpm drives

This new desktop replicated the diskdrive layout from the laptop, even using the same names for the disks drives. And there are no partitions on any of the disk drives.

I loaded Production Premium cs6 onto the new desktop from same DVDs as when I loaded it onto the laptop. Did the updates, etc. Then copied all the project files from the laptop to the desktop, carefully putting them on the same drives, same directories, etc. Basically, I duplicated the laptop setup on the new desktop. I opened up one of the old projects on the new desktop, saw that all was fine, all files found, video/audio played like it should, etc. All fine. Then for reasons out of my control, was unable to do any video work for several months.

Now I've come back. Edited a new project, everything just fine (but much faster because of newer hardware). No problem with importing video files, sound files, etc.

Until... need to import some stills. Found an old file from a previous project, copied it to new project, edited in Photoshop (like I've done dozens and dozens of times in past using cs6). Then I import into PPro and get a pop-up box that says "The importer reported a generic error." No, I'm not kidding. That's exactly what it says.

So I think... fine. Corrupted file. So I create a new file from Photoshop. Save it to the new project directory using a new file name. No dice, same error. Hmmm....

Have the idea that maybe PPro isn't setup to recognize Photoshop files. But in the Media Browser panel you can click on the "files of type" button and get a listing of all the file types supported, and sure enough there's Photoshop, just like on the laptop.

So I thought, what if I get PPro itself to create the Photoshop file? So in PPro I click on "File...New...Photoshop file" and create a new (and empty except for the guilds for the title and action safe areas) file in the correct directory. Turn right around and import it, only to get the same "The importer reported a generic error." Yet, when I brought up the file explorer and clicked on the file icon, it started Photoshop up, opened the file, and showed me that the file was empty except for the guides, as expected. So it doesn't seem to be an OS problem, or a Photoshop problem.

Finally, I decided to try it a different way -- instead of a *.psd file, I saved the file out of Photoshop as a *.tif. Same actions, but this time PPro imported it just fine. So this instance of PPro clearly has a problem importing *.psd files, and from what I can tell, only *.psd files.

Anyone else seen this behavior? Anyone have any idea what I can do to fix this?

For the record, I have asked this question on the Adobe forums. But I haven't gotten any meaningful answers at all. So I thought I'd ask a different set of NLE users, hopefully I'll get some insightful responses here.
 
Premiere reads files using a bunch of plugins that are installed with Premiere. A different plugin is used for PSD files than TIF so that may explain why TIF imports work but PSD doesn't. I think PSD's are read with "Adobe Premiere Pro CS6\Plug-ins\Common\ImporterPhotoshopProxy.prm" But Premiere also uses a PhotoshopServer system that may be getting in the way. Do you have full admin rights on the new machine or are you running a very locked down account?

In order to figure out what is not working here you are going to need some tools. If this were me I'd run SysInternals's Process Monitor (get it free from Microsoft at http://technet.microsoft.com/en-us/sysinternals/bb896645 )

Set it to watch Premiere and then do the Photoshop import. It will log every file and registry access. You'll likely see that it's trying to do something and failing. Perhaps something to do with temporary drive access or running the mess of server apps Adobe has become fond of using. From there you may be able to make Premiere happy. Perhaps it's something as simple as a environment variable for TEMP or TMP. Or maybe some registry entry that is missing. I wouldn't be surprised if your install of Premiere is the actual problem. Uninstalling Premiere and reinstalling it might help. Did you copy over files/settings from the first machine to the second? Blindly copying over internal settings can often mess up installs.

Short of that Adobe is really your only choice for support for something like this. Good luck.
 
Back
Top