Lightroom 3.4.1 won't import Photoshop 5.1 psd files

I can't get Lightroom to import psd files (they appear greyed out). I have set the Photoshop file handling preferences in Photoshop to "Maximize PSD and PSB File compatibly ALWAYS" and save the file as Photoshop with Layers. The Help doc says that this should save "This saves a composite version of a layered image in the file so it can be read by other applications"
Any suggestions?
Regards,
Steve

Maybe they are imported already?
If you open a RAW file from LR into PS and save your changes in PS, a psd-file will be created that is imported into LR automatically.
In the Import Dialog the file will then be greyed out because LR is set by default to NOT import duplicates. You can change that by unchecking tyhe box <Don't Import Suspected Duplicates> in the top right corner of the Import Dialog.
In case you cannot see the automatically imported psd-file besides your RAW-file, in the Library Module go to >View > Sort and select <File Name>. If <Capture Time> is selected the psd will be at the very end of your filmstrip, because LR equates the time the psd was created with Capture Time.
WW

Similar Messages

How do I import into Photoshop touch a PSD file from sketchbook pro mobile?

How do I import into Photoshop touch a PSD file from sketchbook pro mobile?

I don't believe you can at this time. The only way to get PS Touch to import a PSD is to upload it to Creative Cloud first (but even then it'll flatten any layers).

Photoshop not recognizing PSD files in my windows account but works on others

I tried browsing my computer for the default program to open .psd files, but when I double click photoshop cs6, it doesn't show up in the list of default programs. Please help, this is very annoying. Photoshop can open .psd files automatically in other user accounts, but not on mine.

Boilerplate-text:
Are Photoshop and OS fully updated and have you performed the usual trouble-shooting routines (trashing prefs by keeping command-alt-shift/ctrl-alt-shift pressed while starting Photoshop after making sure all customized presets like Actions, Patterns, Brushes etc. have been saved and making a note of the Preferences you’ve changed, 3rd party plug-ins deactivation, system maintenance, cleaning caches, font validation, etc.)?

Trouble with "Place Photoshop button". It is not importing or "placing" my PSD file.

So I have a triple layer PSD file of a custom facebook icon that I am trying to "place" into Muse. (PSD file includes transparent backgound, layer 1 image, and layer 2 image). When I go to the "Place Photoshop button" and select my PSD file containing this and click "ok", the dialog option box does pop up however without my images or file. Am I doing something wrong?

Hello SDM,
Are you getting this option after you select the .psd file ?
Regards,
Nitin Kapila.

Premiere Pro CC 7.2.1 won't import layers of an AI file

I know in the past Premiere Pro wouldn't import a layered AI file, but is that still the case? I can get a layered PSD file to import layers as normal. When I try to import a layered AI file, I don't get the "Import Layered File" dialog as I do with the PSD files; I get a flattened image. Is this a setting I've overlooked or is this STILL not a feature?
Thanks for your help!

No layered import for AI files.
But when imported in Premiere and you want to change something hit Edit Original and the file will open in layers in Illustrator.

Editing in Photoshop... psd file is huge!

In Lightroom, you can "Edit in Photoshop". After editing and saving the file, a .PSD file is created and is part of the library. Great. But the file size for the .PSD is about 5x as large as the original .DNG. (about 35 megs)
Is this normal? It would be nice to edit the .DNG in PS, and then the edited file is brought back into LR as a .jpg or even .DNG. My workaround is to export the new .psd to a .jpg and then import the .jpg back into the library, and then delete the .psd. That's not a quick or intuitive workflow.
Any advice?
Thanks!
John

Yeah that is completely normal. The DNG RAW file is typically a Bayerrized grid of 12 bit pixels. For example, a 10 MP camera has 5 million green pixels and 2.5 million each of blue and green. Uncompressed and at 12-bit res, that would take about 15 MB uncompressed and about 7.5 MB losslessly compressed. Now if LR's raw converter debayerizes it, which means that all color channels will be interpolated from neighboring pixels at every original pixel location, every pixel will end up as 3 (for each color channel) x8bit (if you use an 8-bit psd), which means 30 MB uncompressed or 15 MB compressed psd, or, in the case of 16-bit per colour channel about 30 MB compressed, precisely as you observe. If you want to send the dng to PS, you right click (or control-click) on the file in the grid view and choose show in Finder/explorer and then drag the file into PS. It will open in camera RAW with all your LR edits in place.

Is there a way to prevent LR from reducing size (pixels) of files transfered to Photoshop as a psd file for editing?

The subject line says it all. I have discovered that LR reduces the size of files transferred to Photoshop for further editing when compared to the same RAW file processed in ACR in Photoshop. For example, a psd file created by LR from a 36 MB RAW file will typically result in a 100 MB psd file. The same RAW file processed similarly in Photoshop will result in a file around 300 MB. This makes a huge difference when the files are converted to JPEGs for printing. The smaller LR psd files result in JPEGs typically under 500 KB where the Photoshop JPEGs are typically around 1.5 MB.

Whew! I didn't think this would turn into such a long discussion!. OK - my error, spatial data not color. But that is loosing focus on my question. My objective is to get the best print possible from the final JPEG file used for printing.. As previously noted, for a given RAW file w/similar adjustments but with one processed in LR and the other in PS , a print made from the larger of two resulting JPEG files, the larger JPEG file resulting from only PS ACR processing (i.e., no LR) will result in a better print. Elie-d appears to have answered my basic question. If LR will always pass a 103 MB file then I assume there is no way to change this size. In case anyone is interested here is some additional info for consideration. Both LR & PS using 8 bit mode and 240 ppi.. Procedure in LR: 1) download RAW files from camera CD; 2) make adjustments to photo; 3) using Edit in External Processor, photo transferred to PS in PSD format, 8 bit. 4) file size around 100 MB (103 MB per elie-d). Procedure in PS: 1) download RAW file to hard drive with Nikon View2; 2) open file in PS - auto opens in ACR; 3) apply essentially the same adjustments (e.g., exposure, highlight, shadow, etc) ) as applied in LR; 4) file opened in PS editor; 5) resulting PSD file size with no further processing (i.e., no layers, etc.) is 310 MB). The resulting JPEG file created from the LR PSD is typically less than 200 KB whereas the JPEG from the PS PSD will generally be around 1.5 MB. As an academic question it would still be interesting to know why one gets different size PSD files from LR and PS and what, if any, affect this has on print quality. As for now I will not use LR to process RAW files. I prefer the larger PSD & JPEG files I get using just PS

Photoshop saved a PSD file with security permissions, and now I can't access it. Please help!

Using Photoshop CC, I saved a PSD file after several hours of editing. I also exported a TIF file from the PSD. After closing Photoshop, I cannot access either file in any way. I cannot even copy them.
going to properties --> security, I get a message that reads, "You must have Read permissions to view the properties of this object." Click Advanced to continue.
When I click Advanced, it says "Unable to display current owner", and in none of the three tabs available (Permissions, Auditing, or Effective Access) can I click "Continue" and get any further than the message, "You do not have permission to view or edit this object's permission settings".
Please help me. This is highly frustrating, and a bug that is costing me over an hour of my time troubleshooting.
Thank you.
UPDATE:
I rebooted, and the files are... gone. Photoshop CC has no record of the file under "Open Recent".
What just happened? I lost a good 2 hours of work and a unique photograph
UPDATE2
I restarted the project, saved a PSD with Maximize Compatibility selected. Verified this file has appropriate permissions.
When I then go to File --> Save (not "Save as", but "Save"), after progressing to 90% or so, an error message comes up, "Could not save 'O:\[path]\file.PSD' because the file name was not valid."
I click "OK", and then go to the original file and check its permissions. They are now changed to "You must have read permissions".

I have this exact problem too. Windows 8.1 CC 2014 and all of a sudden I get the problems AIJ23 has. Say I have 8 files open, I save the first 3 or four, just with Control-S (saving in PSD format) no problem, then all of a sudden on the next save I get a message saying I don't have permission to save over the file followed by the same problems as above. I use Save As so I don't loose my work but I cannot delete/rename/change permissions of the original file. This only started happening about 2-3 days ago and only happens in Photoshop. I haven't managed to find much about this issue anywhere.

Photoshop not recognizing PSD files

My PSD files are not being recognized. When I go to Properties and then Open With, and browse to the Photoshop application as usual, I am unable to select Photoshop as the program to open my file. I am completely baffled.
It looks like the Open With function is not recognizing PhotoShop, and I do not know if this is a Photoshop error or a Windows error.
Other Adobe programs are working and are recognized just fine. I am using Windows 7 and Photoshop CS4. I am running up-to-date Norton 360 so it is extremnely unliklely to be a virus.
Help please!

Sounds like a basic system problem, not a problem with Photoshop per se...
First, Photoshop should have installed itself so that it would automatically be in the list of programs available to open that file type.
Second, if it's not there by default, browsing to the Photoshop.exe file should make it work as you expect.
I've just opened a file from my desktop using Right Click, then Open With, and choosing Photoshop.exe as you have described. However, in my case Photoshop is already in the list of Recommended Programs.
Out of curiosity, do you see it in the list of "Other Programs" toward the bottom of the Open With dialog? You'll have to click on the little arrow to the right to see them.
-Noel

Importing XMP sidecar with PSD files

I've got a boatload of PSD files in Aperture with keywords and other metadata. I want to import these into LR5.
Aperture will not (AFAIK) write the metadata I have in Aperture to the files themselves since they are PSDs. But it does write to XMP files, so I exported a test batch, PSD + sidecar of same name to a folder. I go to import that folder into LR5 and it works, except no metadata.
I checked the metadata in the sidecars with a text editor; it's there.
I tried the Metadata>Read Metadata from File menu; nothing.
What's up?

Thanks. One problem is that Aperture doesn't seem to put things in the XMP that I'm interested in, or in places I wanted in sidecars. I didn't get too far into it, but it seemed to write a more complete set of data into the tiffs than into the sidecar for the same file. I didn't really care if it was in XMP or exif or IPTC or wherever as long as it was useful in LR. As it turned out, exporting to tiff with the metadata from Aperture was the fastest way to go for thousands of files.
BTW, anyone have a nice chart with where various bits of metadata are stored by common applications? Although each has it's own standard there doesn't seem to be enough agreement about where a "keyword" or "tag" winds up in exif, IPTC, XMP, xattr, etc. Annoying. Supposedly Mavericks in the MacOS is gonna have some support for tagging (gee, welcome to the 21st century) in lieu of labels; wonder if they'll make any use of any of the formats we use.
BTW, Graphic Converter 8 was very helpful in massinging metadata and reorganizing in the move from Aperture to LR. After all these years it still proves to be super useful.

Why does Photoshop not show PSD file image tile in 'Open File' when Facebook can?

When selecting a PSD file in Photoshop the image tile just says "PSD" so visually you cannot select it knowing which version it is. Why can't Photoshop show the image tile like Facebook can instead of having to use Bridge? Bridge is a huge memory hog and to have to jump back and forth is a pain. If I choose a file to upload to Facebook, I can see the standard file icons and also the PSD versions.
Any ideas or should this be a request in the next update?

That's happened a more than a couple of times where I spend 20 minutes carefully preparing a post and then find out some else got it.
Anyway, psd icons in the Explorer is a sure sign of the Windows OS. They could work with Adobe to render thumbnails, but seems something I'm not privy to in their internal policies prevents that.
Chris Cox did offer some insights. The OS vendors expect their rules to be followed, so if the OS does not respond properly, it's not Adobe's job to work around that. I do wonder how third party codec vendors do it. I'll have to ask.
Btw, John Ellis has a quicklook plugin for the Mac that renders PSB thumbnails should you be interested.
PSB Quick Look Plugin
Gene

Lightroom 5.3 Mac won't import anything

I recently upgraded from Lightroom 4.x to 5.3, and I am now unable to import any new images. The import dialog allows me to select files, but once I press the import button (and this includes using "Add", "Copy", and "Copy as DNG"), nothing happens. I've left it 'transferring' overnight — nothing. I eventually cancel and a box pops up that says "No photos or videos were found to import.
I feel like I've scoured the entirety of these forums, but I've found no solution that works. I sat on hold with Adobe's nearly impossible-to-find tech support phone number for two and a half hours tonight before hanging up. No one ever got on the phone with me. Anyway. I've tried uninstalling and reinstalling LR5 and working with a fresh catalog. No luck. I even deleted all the preference files and everything. Nothing. I'm about to be in a real bind if I can't import new work soon. Any suggestions are appreciated.

Thanks for getting back to me so quickly Tony.
I'm shooting a Nikon D800, but I've also tried importing numerous different file types. It ranges from RAW files from the D800 to photos shot with an iPhone 5s, and even TIFs from a Nikon Coolscan 8000. I'm importing nothing different than before. Also, I should note that often, only a handful of thumbnails for the images in the to-be-imported folder appear.
One other discovery I've made — which may point to this being a problem with OS X Mavericks and not so much Lightroom — I logged into another fresh admin account on the computer and launched LR to test if it would import any photos into a fresh catalog. It seemed to work without a hitch.
I'm attaching a screenshot of the import dialog. This is a fresh catalog. And I cleared recent paths to no avail.
FWIW, I've scheduled an appointment at the Apple Genius Bar tomorrow afternoon to see if they might help remedy this an a couple of other minor issues. Thank goodness for Applecare.
Thanks Tony.

Frame7.1 wont import Photoshop CS5.1 .jpg file

I am (reluctantly) in the process of migrating from Windows XP +
Photoshop CS V8.0 to Windows 7/64bit + Photoshop CS5.1.
Framemaker 7.1 works well in both XP and W7/64, including generating
PDFs. I can import .jpg files written by Photoshop CS. Etc.
... except...
If I open a known-good (already imported) .jpg file using Photoshop
CS5.1 and, without making any changes, save it, Framemaker can no
longer import it, neither directly or by reference:
   "The filter encountered an error and could not complete the
    translation".
It appears the Photoshop CS5.1 writes a different .jpg file format
than Photoshop CS (rhetorical: how can it be acceptable for CS5.1 to
change the format of a basic .jpg file? but I digress...).
Examining the original .jpg file vs. the CS5 .jpg file I find:
- The new file is smaller (79KB vs. 82KB) - note both are small!
- The contents (examined using a binary editor) are quite different.
- Both versions display identically, in both CS and CS5.1 and in
   various viewers.
I have tried various experiments trying to understand this and have
had no luck. I can open the CS5 .jpg file in Photoshop CS and save it
again but Framemaker will not open this version either, same error.
This is not a RAM size issue (8GB), swap space issue, or anything else
related to the computer hardware. All SW updates are current, etc.
I have tried importing into a new, default template file, etc.
So, I tried saving as .bmp and the first time I tried to import it
Framemaker died immediately: no stack trace, no error messages, the
Frame process was just gone. After restarting, the 2nd attempt I got a
black rectangle of the correct size, but all black = not usable.
Photoshop CS + Framemaker has worked well for many years, so I know
this is a CS5 issue.
Anyone have any ideas on how to make CS5.1 generate a "standard" .jpg
file?
Anyone have any ideas on how to import CS5.1 images using
Framemaker 7.1?
Please don't advocate upgrading Framemaker to V10... Adobe provides zero
information on migration (from any version) and the last time we did
this cost us many man-months of work to "fix" 14K+ pages in 50+
manuals. We will stay with XP/CS and "eat" the new W7/CS5 system
before we move to FM10.
Thanks
Previously (everything works)
Windows XP/SP3
Photoshop CS V8.0
Framemaker 7.1P116, non-structured
Today:
Windows 7/64bit SP1
Photoshop CS5.1
Framemaker 7.1P116, non-structured

AG: IIRC, the FM7.1 JPG filter only reads the older JFIF header format JPG files, while the CS5 Photoshop and many other applications write EXIF headers in the JPG (yes , the standard evolved).
We also had a problem with JPEG 5 (legacy) vs. JPEG 2000 (newer) encoding, not in FM, but in the rendered PDFs at our print shop. The Xerox engine needed an update to fix that.
Using JPEGs in FM has various considerations, some already mentioned in this thread. But the biggest concern, in my view, is cascading compression damage. JPEG compression is always "lossy", and the artifacts at higher compression, or after successive compressions, are often visually distracting (and may be aggravated if sharpening is also applied). Even at NO compression, there are losses due to the transforms
Unless you are shooting .RAW, your camera is compressing from frame buffer to JPEG. When you re-save from your photo editor, regardless of edits, it gets re-compressed if saved to JPEG. When you render to PDF, it may get both down-samped and re-compressed again depending on PDF settings. If you post-process (optimize or reduce file size) in Acrobat, it can get down-sampled and re-compressed again.
So I shoot JPEG with as little compression as possible (RAW has other considerations). I edit in PhotoShop and save as EPS, which is a very inefficient format space-wise, but is UNcompressed*, and is a very efficient format both performance- and stability-wise in FM. I save the EPS at the resolution desired in the PDF (usually 200 dpi). Yes, it does get (and needs to be) re-compressed during Distill, but we've skipped one needless re-comp, and avoided another down-sample. We don't further optimize in Acrobat post because the images are already optimal.
EPS also supports both RGB and CMYK models, whereas JPEG is strictly RGB (or, beware: indexed color). And EPS is generally unmolested by Mr.Bill's GDI, which is crucial for color-managed CMYK.
* TIFF can also be uncompressed, and CMYK, but can be a performance issue in FM.
The Wiki page for JPEG, btw, is presently vandalized:
"The name "JPEG" stands for Joint Photosaic Experts Group, the name of the committee that created the JPEG standard and also other standards. It was discovered by <likely name of vandal redacted> of the Philippines."

Premiere Pro CS3 won't import audio on an avi file

I just recently borrowed a friend's HD camera to film some scenes for a video. I had to import them onto my computer using a converter because my computer is a windows vista ( >:( ) and the files on the camera are MTS files (they aren't compatible with CS3 anyway).
The first time I converted these files to avi files Premiere read them perfectly fine and also allowed me to use the audio that was with them. I soon decided though that the audio and video quality that I had converted them into was rather crappy so I converted the files again to much high quality (video bitrate 10000 kbps and audio bitrate 448 kbps).
By this time, I decided the video quality was what I wanted so I deleted the files off my friend's camera and returned the camera to him. (Note: the files played perfectly fine in windows media player and several other video editing software that I possess)
I opened Premiere after taking the camera back and discovered (to my disappointment and frustration) that whenever I tried to import the new files, Premiere would only import the video and not the audio. I would place the file on the video track and the audio wouldn't import onto the audio track.
Could this be a problem with the project preferences I chose? Or is it something else? Is there any hope of getting it to work?
One option I've considered doing is converting all the audio on the files to a different format or converting the video files to another format but my harddrive is running out of space as it is and I could lose quality by doing that.

(Not to mention the time it would take to reconvert the files. I've already spent several hours converting it from the camera. At the moment I also do not possess a solid avi converting program that I could trust.)

Logic X won't import a 64 bit .wav file. Why?

I'm trying to import .wav files created with FF Tools into Logic for some editing, but it says the audio file is "in a 64 bit format and cannot be used". Why is this? I thought Logic X was 64-bit friendly?
Any help on this would be greatly appreciated.
Thanks

There is also no point in using 64 bit audio files. Even 32 bit floating point is already overkill. The best choice for recording is 24 bit, for internal processing 64 bit floating point does make sense, but not for storing.
In any case, your mac comes with a very capable audio file format converting utility that can be used from the command line and reads/writes practically any audio file format you will encounter, including 64 bit wav. Type "afconvert" on your command line in terminal.app to see the options it offers. If you're not used to using the command line you might find this very uncomfortable, but it's really worth getting into it.
Let me know if you need help,
Jazz

Lightroom 3.4.1 won't import Photoshop 5.1 psd files

Similar Messages

Maybe you are looking for