Do the files open back in PS? Are they saved with the Maximum Compatibility setting?
Many thanks for your response.
I can open up .PSD files in Photoshop without a problem. Just checked the PS preferences and the max compatibility for PSD and PB is set to 'always'
My only way around the current issue to export single layers as .jpgs or .pngs and put it back together in AE.
Just frustrating I can import the .psd files for some reason.
Not sure what I've done, or if I've done anything at all during the instalation process.
If you, or anyone else has any ideas, I'm all ears
Whoops - amendment to the above.
I still cannot import .psd files into AE
What are the specs of the PSD file you are importing? What is the dpi and spatial resolution (pixel dimensions) of the PSD? Does the problem occurr if you create a new, very small .psd file?
Thanks for your response.
It actually happens with every .psd file regardless of size or specs.
All the other programs in the CS6 master collection work fine, except for AE and PS.
I tried the small file. Created a small file, 100 px by 100px 72dpi, just with a gradient background. Same thing, not enough memory to initialise PSL.
I got the adobe cleaner, and re-installed on my system (again) .... same thing.
As long as I open AE with doing ctrl-alt-shift every single time or export layers from PS individually I seem to be OK.
The problem is far from solved, so I guess i just have to put up with workarounds.
Thanks for taking the time to respond
Unless I missed it somewhere we don't know anything about your system. It sounds like you don't have enough memory or that your preferences are not set up correctly.
The PC is a month old, here are the specs.
Intel (r) Core(TM) i7-3770 CPU @ 3.40ghz
64 bit os, x64 processor
C Drive 100gig
D Drive 2TB
Graphics: GeForce GT 630
I can get things to work in AE provided I do 'Crtl-Alt-Shift' everytime I open it up.
Maybe it is the system???
Sounds highly unusal, but I have no clue what else to try. The only thing I can think of is that you may need to update some system library like an MSVC runtime or a specific driver in your system like the SATA driver. Could be that this is some weird version conflict between different versions of a library having been used on compile or a processor-specific optimuization not working properly...
In my case, it was the directory name. It had a Turkish character in it, when I corrected it the error was gone. I recommend checking out your directory names for unusual characters.