New at PSE 7
I am a total novice and have recently aquired PSE 7. I am trying to also learn more about photograpy in hopes of having a side gig of a band photographer. Does anyone have any really good tips for someone like me who will be taking alot of on stage band photos?? They sometimes come out a little blurry, but not always. I need a good way to get rid of graininess and maybe brighten certain parts of a photo while leaving others dark. I have never used a PS or a PSE product before, so please explain anything in dummy speak!!!
Thank you so much!!
girldair!!
Taking pictures of bands, indoors, is difficult. You will get lots of digital noise. It helps if you have fast lenses (F/2.8 or ever faster), and a camera that can shoot at ISO 1600 or higher. In other words, we're talking big $$$$ here. Get used to the fact that there isn't a lot of light, your photos may be dark and noisy.
Lightening parts of images will produce additional noise. Although the PSE Editor has some noise reduction tools, you might want to look into third-party noise reductions tools like Noise Ninja or Neat Image. Shooting RAW (instead of JPG) probably helps too.
There are many tutorials for Photoshop and Photoshop Elements on lightening parts of images (Google for "dodge and burn"), those will demonstrate the techniques visually, better than I could using words here.
Good luck!
Similar Messages
-
I'm trying to convert several JPEGs into Clip Art. I need to remove the background from the image and save that file as a TGA file with a transparent background. Any advice, I'm new to PSE 5.
Thanks,
Doug>select alpha channels. In PSE I don't see where to select alpha channels.
I presume you are referring to another product when you say "previous versions of photoeditor had this feature". PE does, too, and it's always in the same place. Make a selection, go to Selection>Save Selection and save the selection, then Load the Saved Selection, save the file and it should appear as an alpha channel in most other programs. -
New Laptop - PSE 11 - preferences
Hi all - hope I have an easy one for you...
Just got a new laptop and (re)installed PSE 11 - everything is working fine but I want to bring over all my customizations from my old computer. Can you help??
(ps: I copied the //AppData../Photoshop Elements/11.0... data over but that did not work??)What do you mean by customizations--are you talking about things like extra style, shapes, actions, filters that you installed? If so, you must install them all over again on the new computer.
-
New iMovie & PSE 12 Running Painfully Slow
Have iMac 27", mid-2010, 3.2GHz Intel Core i3, 12GB memory.
Recently installed OSX Mavericks; and new version of Photoshop Elements (12).
Both the new version of iMovie and PSE are running very slowly (5-8 sec. delays when scrolling; moving clips in the timeline, etc.) Did not have this problem with previous version of iMovie or PSE 9 (was running Mountain Lion). At suggestion of Apple Tech. Support, I cleared the Cache file, and added 8GB of RAM, to a total of 12GB. Still running slow.
Anyone else experience these problems? Any suggestions for fixes?
Thanks Much,
RickLinc:
Here's the log for opening PSE 12 Editor.
Thanks for your help.
Rick
11/15/13 12:14:23.160 PM Adobe Photoshop Elements Editor[3800]: objc[3800]: Class StageDelegate is implemented in both /Applications/Adobe Photoshop Elements 12/Support Files/Adobe Photoshop Elements Editor.app/Contents/Frameworks/FileInfo.framework/Versions/A/FileInfo and /Applications/Adobe Photoshop Elements 12/Support Files/Adobe Photoshop Elements Editor.app/Contents/MacOS/Adobe Photoshop Elements Editor. One of the two will be used. Which one is undefined.
11/15/13 12:14:23.815 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:23.815 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.
11/15/13 12:14:23.816 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:23.816 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.075 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.075 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.076 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.076 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.076 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.076 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.076 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.077 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.077 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.077 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.084 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.084 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.084 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.085 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.085 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.087 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.087 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.087 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.087 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.087 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.088 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.089 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.089 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.089 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.089 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.090 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.091 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.091 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.091 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.091 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.092 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.093 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.093 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.093 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.093 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.096 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.097 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.097 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.097 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.097 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.103 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.103 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.103 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.104 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.104 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.104 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.104 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.105 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.105 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.105 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.105 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.106 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.106 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.106 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.106 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.106 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.107 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.107 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.107 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.107 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.108 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.108 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.108 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
11/15/13 12:14:24.108 PM Adobe Photoshop Elements Editor[3800]: CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API. -
NEW to pse and to forum, how to add a frame?
I have never used Photoshop. I would like to add a white frame around a photo. can anyone share how to do this? I hope i can figure out how to get back here to read the answer! LOL
If you hit the F1 key to open the online Help, in the upper right corner there's an icon to "View as PDF". Click on it and you can save the PDF to your hard drive. That's a very good thing to do because then you can search the PDF, which you can't do with the online help.
I learned PSE by reading that help file and watching the Adobe TV tutorials (some of which have sample files for downloading so you can practice with the same images used in the tutorial).
Others will have to jump in with recommendations for books, since I haven't looked at any of the books.
Ken -
New to PSE 12, Need Guidance :)
Hello Everyone,
I just upgraded to PSE 12 from 8, I got the feel of the program but I kinda seem to be lost,
you know going around in circles. I've been surfing around on the Adobe sites to get a where
to start kinda thing. I already took one pic that we took with a digital cam and played with the
touch up options, and wow what a difference. ( see below ) If anyone has any ideals that can
give me some clues of what to do, I would truly accept it. Thanks for your time, and have a
great week.
Billy
http://billypayton.com/me1%20at%205000%20ft%20on%20parkway%20in%20jackson%20co1_edited-2.j pg After
http://billypayton.com/me1%20at%205000%20ft%20on%20parkway%20in%20jackson%20co_edited-1.jp g Before
Photoshop ElementsHello Everyone,
I just upgraded to PSE 12 from 8, I got the feel of the program but I kinda seem to be lost,
you know going around in circles. I've been surfing around on the Adobe sites to get a where
to start kinda thing. I already took one pic that we took with a digital cam and played with the
touch up options, and wow what a difference. ( see below ) If anyone has any ideals that can
give me some clues of what to do, I would truly accept it. Thanks for your time, and have a
great week.
Billy
http://billypayton.com/me1%20at%205000%20ft%20on%20parkway%20in%20jackson%20co1_edited-2.j pg After
http://billypayton.com/me1%20at%205000%20ft%20on%20parkway%20in%20jackson%20co_edited-1.jp g Before
Photoshop Elements -
It won't open my camera photos. I plug the camera into the computer, turn it on, and it comes up on a fake PS 7, which I had before. I thought it was gone, but it's now a ghost that was deleted when I replaced my computer - it keeps telling me it can't open but I can't find anything to remove that connection.in my program files. Advice?
Hi,
Well, Microsoft no longer support Windows XP so you are leaving your system vulnerable.
Changing from Windows XP to Windows 7 or Windows 8.1 is a bit of a major step but I find that Windows 7 is faster and better than XP and I think that Windows 8.1 is even better. Many didn't like the original Windows 8 but improvements have been made in the 8.1 update.
Now for your problem.
Connect up your camera and switch it on.
Click on Start and then My computer - that should open up the Windows explorer and hopefully you should see your camera there.
Right click on your camera and select Properties.
The second tab should be AutoPlay - select that.
From the drop down list, select Pictures
Click on the option Select an action to perform and search the list for Organize and edit for Photoshop Elements 12 - select that
Click on OK and close Windows Explorer.
Incidentally, I prefer to use a card reader rather than connect my camera each time.
Hopefully, the next time you connect your camera, it should load the organizer
Good luck
Brian -
I am having a very hard time seeing the size of all type and icons on all toolbars, etc, they look to about 4 or 6 pt. Is there a way to make them larger?? I don't think I can use this program if I can't see the items larger. TIA
Thank you for the information. I will try the suggestions, but I am shocked that there is really no way to enlarge everything. Does Adobe think everyone has the same quality of eyesight? I feel I just wasted my money. I appreciate your reply to my question.
-
How many downloads do you get for the new holiday PSE 13 special?
Anyone know.....I can't find it anywhere Keep trying to download and it wont work for $69.99 so I guess that means no?
THanksmschriss
Does your question involve Photoshop Elements 13 or Premiere Elements 13. Sounds like Photoshop Elements 13? Somehow you thread got posted
in the Adobe Premiere Elements Forum.
Can you show proof of ownership of a prior version of Photoshop Elements?
Were you working from the following web page?
My cart
Have you used the Chat opportunity at the link I just posted to get the official Adobe pronouncement on this?
ATR -
How to transfer PSE 12 from old computer to new computer
I have a new subscription PSE 12 (Dec 2013) on my old computer which was too old and slow to operate PSE 12.
I bought a new computer and now would like to move my existing subscription of PSE 12 to my new computer, I have the SN and order numbers.
Should I just sign up for a free trial and add the SN number whet the trial expires?Should I just sign up for a free trial and add the SN number whet the trial expires?
Yes, that's the way to do it.
No need to wait until the trial expires. Adobe allows up to 30 days of free use. You can enter your serial number immediately, since you've already bought it. -
Bugs I've Encountered In PSE 7
Here are all the reproducible bugs I’ve encountered in PSE 7. Problems added since my last posting are marked [N]. In the coming weeks, I’ll evaluate PSE 8 to see how many of these have been fixed.
I’ve reported all of these problems to Adobe. Almost all of them are in the Organizer. Based on all the reports on the forums, it appears that the Editor has far fewer problems than the Organizer. Perhaps that’s because the Editor shares the same code with the professional Photoshop, while the Organizer appears to be an orphaned consumer product whose development Adobe has moved offshore.
For reference, my computer is a midrange Vista laptop with a dual-core 1.9 GHz processor, 4 GB of memory, and a 7200 RPM disk (the same speed as desktop disks).
File Management and Tagging
Major Problems
[N] The conversion of a catalog from PSE 6 to PSE 7 doesn’t properly handle photos that are stored within the PSE 6 catalog folder (as occurs when PSE 6 was used to restore a catalog from a backup). As a result, it isn’t possible to save photos in version sets, and PSE 7 will create duplicate thumbnails in the Organizer for an edited file.
File > Backup/Restore Catalog doesn’t backup and restore audio in slide shows.
Using Folder Location view to move a folder containing hidden files imported in the catalog will silently fail to move the hidden files and will leave the unhidden files disconnected in the catalog.
When converting a previous-version catalog whose photos are stored inside the catalog folder, as occurs when you’ve previously used File > Restore Catalog with New Location, PSE 7 needlessly copies all those photos. If you have a very large catalog, this will waste huge amounts of disk space; and if there isn’t enough disk space to do the copy, the conversion will fail instantly with a generic non-explanatory error message.
After reconnecting a file on a network drive, PSE will let you import the file a second time, failing to recognize it as a duplicate. The catalog is left in an inconsistent state, with two entries in the volume table for the network drive, one upper case and one lower case.
The Organizer fails very ungracefully when two drives have the same volume serial number, e.g. because of the use of a disk-cloning utility.
I’m very disappointed that Adobe didn’t add the three lines of code that would have issued a warning when it discovered two drives with the same number. While most people will never encounter this, when it strikes someone, its symptoms are very mysterious.
The Reconnect command fails to reconnect when: you move your photos to a new drive, assign the drive the letter of the old drive to the new one, and leave both drives connected to your computer.
If a hard drive containing photos in the catalog gets its drive letter reassigned by Windows, then the left-hand folder pane of Display > Folder Location view shows the old drive letter, not the new one, as containing the photos.
This sounds innocuous, but it led a user on the forums to select the wrong drive when dragging and dropping a folder, permanently deleting some files. This bug and the previous one with Reconnect have the same underlying cause – the Organizer doesn’t update drive letters in its catalog.
Folder Location view shows incorrect folder contents when more than one keyword tag is selected in the Keyword Tags pane.
Based on reports on the forums, there appear to be other situations where Folder Location view shows incorrect folder contents, but they haven’t been easy to reproduce.
The Restore Catalog command puts the wrong path into the restored catalog for folders whose name starts with the catalog name, and it will mark files in those folders as missing. For example if the catalog is named “houses”, and a folder containing photos in the catalog is named “houses photos”, files in the restored catalog will have the path “houses\ photos\” instead of “houses photos\”.
Minor Problems
In File > Export, the Common Basename can no longer be empty, and a hyphen is added automatically, so you can no longer get files named 1.jpg, 2.jpg, etc.
You can get files named 1.jpg, 2.jpg, etc. but you can’t get files named p1.jpg, p2.jpg, etc. – a hyphen is still added in that case.
Setting the Apply Metadata > Author or Copyright fields or the option Preserve Current Filename In XMP of the advanced options of the Photo Downloader causes duplicate files to be downloaded and imported.
Integration with Photoshop.com
Major problems
[N] Photoshop.com shows an incorrect date/time taken for photos with unknown month, day, or time.
For photos taken in years prior to 1970, the date/time shows as 12/31/1969 08:00 AM. For photos with year taken 1970 or later, the date/time shows as the the first month/day/minute/second in that time period in UTC that then gets converted to local time; e.g. “7/2/2005” gets shown as “7/1/2005 5:00 PM” for a user in PDT.
[N] Photoshop.com doesn’t obey the EXIF Orientation metadata field and can show photos rotated incorrectly, e.g. if they were rotated with the PSE option Edit > Preferences > Files > Rotate JPEGs/TIFFs Using Orientation Metadata.
Changes to the order of photos in a PSE album aren’t synced to Photoshop.com, and vice versa.
Adding a photo to a second synced album will cause Photoshop.com to lose any changes you’ve made with PSE’s Edit > Adjust Date And Time.
If you you rename a file that’s synced with Photoshop.com, Photoshop.com doesn’t pick up the new name (important if you’re using Photoshop.com as a backup service).
Only the top photo in a version set is synced with Photoshop.com (so you can’t rely on Photoshop.com to backup version sets).
When a stack is synced with Photoshop.com, all the photos in the stack are synced, but the fact that they were in a stack is lost (so you can’t rely on Photoshop.com to backup stacks).
Map View
Major Problems
Map view is unusably slow with more than about 6-8,000 mapped photos.
When I tested PSE 7 by importing 12,000 photos (the size of my catalog) that had GPS locations, the red push-pins didn’t blink uncontrollably as they did in PSE 6. But the Organizer crashed a number of times when I tried to zoom and pan the Map view until I was able to scroll the map to another country and then back again. The CPU continued to consume 80% of a single CPU (40% of two), even 10 minutes after I closed Map view. When I selected Limit Search to Map Area, PSE took over a minute to respond.
It takes 5 seconds to assign a keyword tag to a photo if there are 1,000 or more photos with map locations.
In PSE 7, it takes 3 seconds with 1,000 photos, 12 seconds with 8,000 photos, and 18 seconds with 12,000 photos.
Giving a map location to a tag assigned to hundreds of photos makes both the Keywords pane and the Map view unusably slow.
Giving a map location to a tag assigned to 2000 photos makes assigning any keyword tag to a photo very slow (see above). Searching on keyword tags takes 15 seconds, and a Show All takes 15 seconds.
Removing the map push-pin of a tag assigned to hundreds of photos mistakenly tries to update the metadata of each photo, which can take tens of minutes and fill up your recycle bin.
The weird thing is that assigning a map location to the tag doesn’t try to write the metadata of files with that tag.
Moving map locations always fails, silently (too bad if you want to record backcountry locations not namable via a place name).
If a photo with GPS coordinates is imported, it doesn’t show as a red push-pin on the map.
Scrolling the map or restarting the Organizer causes the pin to appear.
Color Management
Major Problems
The Organizer considers photos produced by cameras set to the color space Adobe RGB as untagged with a color profile, showing their colors incorrectly.
Metadata
Major Problems
When setting the Organizer’s date/time for imported photos containing EXIF:DateTimeOriginal but not XMP:DateTimeOriginal, PSE 7 doesn’t properly handle US Daylight Savings Time in years prior to 2007.
Edit > Adjust Date and Time doesn’t properly handle US Daylight Savings Time when setting date/times many decades ago, e.g. October 5, 1961 12:00 PM.
In Thumbnail View, the Organizer incorrectly orders files that have unknown time. For example, it will show a file dated 12/25/1976 8:00 PM PST after a file dated 12/26/1976 (unknown time) on a computer in time zone PST.
If you set a file's date/time fields to all unknown with Edit > Adjust Date And Time, the value of EXIF:DateTimeOriginal isn't cleared by File > Write Keyword Tag.
The File > Write Keyword Tag command doesn’t create or update .XMP sidecars for Nikon D300 or D80 .NEF raw files (but it does for Canon CR2 raw files).
New dates set by Edit > Adjust Date and Time sometimes get silently lost.
See http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Date/times_of_files for details and workarounds.
[N] Edit > Adjust Date and Time > Shift To New Starting Date And Time and > Shift By Set Number Of Hours writes the time in UTC rather than local time, as required by the standard, causing other tools to show the wrong date/time.
File > Write Keyword Tags and Properties fails to write the map location (GPS coordinates) of TIFFs (tested with TIFFs produced by the PSE Editor and the Nikon Coolscan V, Nikon Coolscan 5000, and Epson 4490 scanners).
File > Write Keyword Tags doesn’t write the map location (GPS coordinates) into the .xmp sidecar files of Nikon D80 or Canon G9 raw photos.
[N] The Organizer ignores correctly formatted EXIF GPS locations in some files that many other programs can read without trouble; this may be because the EXIF is encoded in little-endian byte order.
Minor Problems
[N] Deselecting the option Use “Last Modified” Date If EXIF Date Is Not Found does not work – the last-modified date is always used for an imported file that doesn’t contain an EXIF date.
The Properties – Metadata window shows the wrong value for Date Time Original when the month, day, or time is unknown.
Edit > Adjust Date and Time applied to a file with time “unknown” decrements the date by one day.
When you save an edited photo as a new file but not in a version set, the edited version picks up the date/time and caption of the original but not the keyword tags, star rating, or notes.
With the Import EXIF Caption option turned off, captions pre-existing in a file’s EXIF:ImageDescription metadata field reappear in the Organizer after invoking the Full Editor.
Searching
Major Problems
The timeline doesn’t correctly display date ranges spanning many years.
Using the Keyword Tags pane, you can no longer exclude a parent category from a search, e.g. exclude all photos tagged with any tag in the People category.
The User Guide gives two examples of how to use category exclusion that just don’t work in PSE 6 or 7. Interestingly, you can almost work around this by doing a text search of “not <category tag>”, e.g. “not People”. But this will also exclude photos that happen to have the word “people” in their filenames, captions, or notes, probably not what you want.
Find > By History > Imported On sorts the photo dates alphabetically, rather than by date/time, and it takes a couple of minutes on a large catalog, making the command almost useless; and it shows a scary message “Deleting Keyword Tags”.
[N] Searching with the Find Bar for “1 star and lower” doesn’t show photos with 0 stars.
Find > By Details > Rating Is Lower Than 1 Star does work.
Searching for “0 stars only” doesn’t work for photos in a catalog converted from PSE 5.
Searching with date ranges doesn’t properly handle time “unknown”.
Minor Problems
The Show All button sometimes doesn’t appear if you quickly type a query into the Search text box and hit Enter.
Setting a date range and then excluding two tags from the search clears the date range.
Show All doesn’t clear a date range set by Find > Set Date Range (can be very confusing).
Save Search Criteria As Smart Album isn’t available if a date range has been set but no other search criteria have been.
When searching, you can exclude a keyword tag and then include an album, but you can’t do it in the other order.
User Interface
Major Problems
On 1024x768 displays, and sometimes at higher resolutions, the Editor Print window is positioned to perfectly obscure the scroll bar of the drop-down list of printer profiles, leading people to think their printer’s profiles aren’t available.
This bug occurred with higher-resolution displays in PSE 6.
The menu bars don’t display if you have changed the screen DPI to be larger than 96 (as many people do on today’s ubiquitous high-res displays).
There is a workaround for both PSE 6 and 7. Set the option > Edit > Preferences > General > Use System Font. The result isn’t that pretty, since some of the application text will be large and some will be small, but it’s functional, and you’ll still be able to use the higher DPI with all your other applications.
Minor Problems
In the Properties window of Full Screen mode, if you click in the Notes field and do Ctrl-A to select all the text, then click in the Caption field and do Ctrl-A to select its text, the notes remain highlighted.
In the Organizer, Help > System Info reports the wrong amount for “Built-in Memory” on computers with more than 2GB of installed memory. (The command reports the correct amount in the Editor.)
The setting of View > Show Borders Around Thumbnails isn’t remembered after you restart PSE.
Copying a paragraph from Microsoft Word and pasting it into the Notes field of a keyword tag causes some of the spaces between words to be deleted.
Ctrl-A to select all text doesn’t work in the text fields of the Properties window.
Interestingly, you can use ctrl-A in the text fields of the full-screen mode Properties window.
In the full Editor, if at least one open photo is minimized to the Project Bin, Ctrl-Tab no longer cycles through the open windows.
Dialogs in the Editor sometimes bounce back when you try to move them.
Dates are shown by Display > Import Batch as 2\20\2008 rather than 2/20/2008.
In Create > Slide Show > Slide Show Preferences dialog, you can't use backspace or delete to clear the text in the Static and Transition Duration fields -- you need to select the text and then type over the selection (non-standard Windows behavior).
Escape doesn’t close the full-screen-mode Properties dialog.
You can’t use the Windows Explorer Tile command to tile the PSE Organizer and Editor windows.
The Editor window can’t be resized the standard Windows way by grabbing any edge, just the lower-right corner.
Alt doesn’t underline the shortcut letters of top-level menu items in the Full Editor (but it does in the Organizer).
The width of the Editor's Palette Bin can't be adjusted by dragging the left edge, as you can with all the other similar panes (Project Bin, Organizer Bin, Map View).
Slide Shows
Major Problems
The duration of a video clip included in a Slide Show is set to the default duration, not the length of the video clip, and right-click Edit Duration doesn’t change the clip’s duration.
For video clips, PSE 7 doesn’t enable the command to change the duration as it does for photos. But you can work around this by using Add Media > Photos And Videos From Folder to add the clip to the show.
An audio caption attached to a photo isn’t imported into a slide show even though the option Include Audio Captions as Narration is selected.
Editor
Minor Problems
[N] The Editor crashes if you invoke Quick Fix and use just one Touch Up tool (e.g. Whiten Teeth) and then save the file (but your changes are correctly saved).
The File > Save For Web command doesn’t remember the last settings (e.g. file format and quality) after your restart the Editor.
For a workaround, see http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Allow_Save_For.Just kidding. But, are you going to give us a bug comparison between 7 and 8 ? I will probably sit version 8 out and get 9 next year. Thanks for the list!
Juergen -
Since PSE 6 was released, I’ve tracked all the reproducible bugs I’ve encountered and reported to Adobe. I’ve tested these problems in PSE 8 and listed the results below – problems that appear to have been fixed in PSE 8 are marked [F], and problems that remain unfixed are marked [U].
Overview
There’s good and bad news. Adobe has fixed a number of serious bugs in the Organizer, but it has left most unfixed, even though they’ve been present since at least version 6. Even worse, the two major features introduced in the PSE 8 Organizer, face tagging and the keyword-tags text box, have show-stopper problems. And even worse yet, Full Screen view is now painfully slow with large catalogs.
The most important fixes address serious problems with PSE’s handling of drives that were introduced in version 6. PSE now notices when a drive’s letter has changed, a problem that has bedeviled many users upgrading or rearranging their drives. Also, PSE now ignores the case of UNC pathnames (network drives), no longer creating duplicate volumes for the same network drive. Unfortunately, one serious bug remains: PSE still gets horribly confused when there are two drives with the same volume serial number, and it still doesn’t even issue a warning.
But many long-standing problem areas remain: The Map View is an unusable toy. The handling of metadata is riddled with bugs. Folder Location view shows the wrong contents of folders. Searching has numerous bugs making it clumsy and confusing.
Overall, of all the bugs I’ve reported, PSE 8 fixes 8 of 46 major ones and 8 of 28 minor ones:
Major
Minor
Fixed
Unfixed
Fixed
Unfixed
File Management and Tagging
4
6
2
Integration with Photoshop.com
2
5
Map View
6
Color Management
1
Metadata
10
2
3
Searching
8
5
User Interface
1
1
5
9
Slide Shows
1
1
Editor
1
1
Total
8
38
8
20
I’ve reported all of these problems to Adobe. Almost all of them are in the Organizer. Based on all the reports on the forums, it appears that the Editor has far fewer problems than the Organizer. Perhaps that’s because the Editor shares the same code with the professional Photoshop, while the Organizer appears to be an orphaned consumer product whose development Adobe has moved offshore.
For reference, my computer is a midrange Vista laptop with a dual-core 1.9 GHz processor, 4 GB of memory, and a 7200 RPM disk (the same speed as desktop disks).
New Problems in PSE 8
[U] PSE 8 crashes or gets intolerably slow after using the new Keyword Tags text box a small number of times.
On my 4 GB Vista 32 system, PSE crashes after tagging 41 photos.
[U] If you use the new Keyword Tags text box to apply an existing tag name with a comma in it, PSE will silently create two new tags instead.
Apply the existing tag “San Francisco, CA” will create two new tags, “San Francisco” and “CA”.
[U] After applying a tag, the Keyword Tags text box loses keyboard focus and you need to mouse-click in the box again to enter another tag.
Forcing the use of the mouse defeats the purpose of the Keyword Tags text box, which is to make tagging much faster.
[U] The Find > Find People For Tagging command locks up the Organizer for about 30 seconds after you click Done (even if you haven’t made any changes), when using larger catalogs.
On a catalog with 10,000 thumbnails showing, the cursor spins for 30 seconds after clicking done. But you can work around this by doing a tag search or setting a date range to have only a small number of thumbnails showing before you invoke the command.
[U] In the Find > Find People For Tagging command, when you select Add Missing Person, you usually can’t resize the selection box by grabbing the lower-right or lower-center handles, which are the handles that most right-handed people are likely to use.
If you move the mouse very quickly so that it is over the photo before the selection box appears, you can usually resize the box with those handles. But you have to be very quick.
[U] The Find > Find People For Tagging command doesn’t do auto-complete on pre-existing People tags, making it very hard to use with existing catalogs.
I have over two hundred People tags in my catalog. Because the command doesn’t auto-complete on pre-exisiting People tags and will silently create new tags, and because I don’t remember exact spellings (that’s the point of auto-complete!), I found myself creating duplicate tags (e.g. “John Ellis” instead of “John R. Ellis”, “Bob Smith” instead of “Robert Smith”). It’s painful to clean up such a mess.
[U] Full Screen view (F11) is much slower than in PSE 7 on larger catalogs.
With a 14,000-file catalog and all thumbnails visible, PSE 7 takes 6 seconds to invoke F11, while PSE 8 takes 13 seconds. With just 20 thumbnails visible (e.g. when working on the most recent import batch), PSE 7 takes 1 second, while PSE 8 takes 7 seconds. This makes selecting the good and weeding out the bad significantly slower.
[U] PSE doesn’t remember the settings if you toggle the Full-Screen Quick Edit Panel and Quick Organize Panel to disappear completely.
On 4:3 displays, it’s desirable to hide the panels completely in full-screen view, so you see the entire image without the panels overlapping them (that’s the point of full-screen view, no?). But PSE forgets the toggle settings, even in the same session.
[U] The keyword tagging in the Quick Organize Panel doesn’t auto-complete tags you type, making it useless with more than a dozen or so tags.
It’s worse than useless, since it will silently create a new tag if you mistype the name of an existing one. And the “tag cloud” is a silly toy that doesn’t help with hundreds of tags.
File Management and Tagging
Major Problems
[F] After reconnecting a file on a network drive, PSE will let you import the file a second time, failing to recognize it as a duplicate. The catalog is left in an inconsistent state, with two entries in the volume table for the network drive, one upper case and one lower case.
[F] The Reconnect command fails to reconnect when: you move your photos to a new drive, assign the drive the letter of the old drive to the new one, and leave both drives connected to your computer.
[F] If a hard drive containing photos in the catalog gets its drive letter reassigned by Windows, then the left-hand folder pane of Display > Folder Location view shows the old drive letter, not the new one, as containing the photos.
This sounds innocuous, but it led a user on the forums to select the wrong drive when dragging and dropping a folder, permanently deleting some files. This bug and the previous one with Reconnect had the same underlying cause – the Organizer didn’t update drive letters in its catalog. Fixed in PSE 8.
[F] The Restore Catalog command puts the wrong path into the restored catalog for folders whose name starts with the catalog name, and it will mark files in those folders as missing. For example if the catalog is named “houses”, and a folder containing photos in the catalog is named “houses photos”, files in the restored catalog will have the path “houses\ photos\” instead of “houses photos\”.
[U] Folder Location view shows incorrect folder contents when more than one keyword tag is selected in the Keyword Tags pane.
Based on reports on the forums, there appear to be other situations where Folder Location view shows incorrect folder contents, but they haven’t been easy to reproduce.
[U] The Organizer fails very ungracefully when two drives have the same volume serial number, e.g. because of the use of a disk-cloning utility.
I remain mystified that Adobe didn’t add the three lines of code that would have issued a warning when it discovered two drives with the same number. While most people will never encounter this, when it strikes someone, its symptoms are very mysterious (and a lot of people using cloning utilities).
[U] The conversion of a catalog from PSE 6 to PSE 8 doesn’t properly handle photos that are stored within the PSE 6 catalog folder (as occurs when PSE 6 was used to restore a catalog from a backup). As a result, it isn’t possible to save photos in version sets, and PSE 8 will create duplicate thumbnails in the Organizer for an edited file.
[U] File > Backup/Restore Catalog doesn’t backup and restore audio in slide shows.
[U] Using Folder Location view to move a folder containing hidden files imported in the catalog will silently fail to move the hidden files and will leave the unhidden files disconnected in the catalog.
[U] When converting a previous-version catalog whose photos are stored inside the catalog folder, as occurs when you’ve previously used File > Restore Catalog with New Location, PSE 8 needlessly copies all those photos. If you have a very large catalog, this will waste huge amounts of disk space; and if there isn’t enough disk space to do the copy, the conversion will fail instantly with a generic non-explanatory error message.
Minor Problems
[U] In File > Export, the Common Basename can no longer be empty, and a hyphen is added automatically, so you can no longer get files named 1.jpg, 2.jpg, etc.
You can get files named 1.jpg, 2.jpg, etc. but you can’t get files named p1.jpg, p2.jpg, etc. – a hyphen is still added in that case.
[U] Setting the Apply Metadata > Author or Copyright fields or the option Preserve Current Filename In XMP of the advanced options of the Photo Downloader causes duplicate files to be downloaded and imported.
Integration with Photoshop.com
Major problems
[F] Adding a photo to a second synced album will cause Photoshop.com to lose any changes you’ve made with PSE’s Edit > Adjust Date And Time.
[F] If you you rename a file that’s synced with Photoshop.com, Photoshop.com doesn’t pick up the new name (important if you’re using Photoshop.com as a backup service).
[U] Photoshop.com shows an incorrect date/time taken for photos with unknown month, day, or time.
The date/time shows as the the first month/day/minute/second in that time period in UTC that then gets converted to local time; e.g. “7/2/2005” gets shown as “7/1/2005 5:00 PM” for a user in PDT.
[U] Photoshop.com doesn’t obey the EXIF Orientation metadata field and can show photos rotated incorrectly, e.g. if they were rotated with the PSE option Edit > Preferences > Files > Rotate JPEGs/TIFFs Using Orientation Metadata.
[U] Changes to the order of photos in a PSE album aren’t synced to Photoshop.com, and vice versa.
[U] Only the top photo in a version set is synced with Photoshop.com (so you can’t rely on Photoshop.com to backup version sets).
[U] When a stack is synced with Photoshop.com, all the photos in the stack are synced, but the fact that they were in a stack is lost (so you can’t rely on Photoshop.com to backup stacks).
Map View
Major Problems
[U] It takes 4 seconds to assign a keyword tag to a photo if there are 2,000 or more photos with map locations.
It takes 2 seconds with 1,000 photos, 6 seconds with 4000 photos, and 11 seconds with 8,000 photos, and 21 seconds with 12,000 photos.
[U] Map view is unusably slow with more than 8 - 10,000 mapped photos.
When I imported 12,000 photos (the size of my catalog) that had GPS locations, the Organizer crashed a number of times when I tried to zoom and pan the Map view. When I selected Limit Search to Map Area, PSE took over a minute to respond.
[U] Giving a map location to a tag assigned to hundreds of photos makes both the Keywords pane and the Map view unusably slow.
Giving a map location to a tag assigned to 1700 photos makes assigning any keyword tag to a photo very slow, 12 seconds. Searching on keyword tags and Show All each take 13 seconds.
[U] Removing the map push-pin of a tag assigned to hundreds of photos mistakenly tries to update the metadata of each photo, which can take tens of minutes and fill up your recycle bin.
The weird thing is that assigning a map location to the tag doesn’t try to write the metadata of files with that tag.
[U] Moving map locations always fails, silently (too bad if you want to record backcountry locations not namable via a place name).
[U] If a photo with GPS coordinates is imported, it doesn’t show as a red push-pin on the map.
Scrolling the map or restarting the Organizer causes the pin to appear.
Color Management
Major Problems
[U] The Organizer considers photos produced by cameras set to the color space Adobe RGB as untagged with a color profile, showing their colors incorrectly.
Metadata
Major Problems
[U] The File > Write Keyword Tag command doesn’t create or update .XMP sidecars for Nikon D300 or D80 .NEF raw files (but it does for Canon CR2 raw files).
The PSE 8 Write Keyword Tag command now gives a warning when you try to invoke it on a D300 .NEF raw file. Why PSE can write sidecars for Canon but not Nikon raw files is a mystery – it’s no harder to handle one than the other.
[U] File > Write Keyword Tags and Properties fails to write the map location (GPS coordinates) of TIFFs (tested with TIFFs produced by the PSE Editor and the Nikon Coolscan V, Nikon Coolscan 5000, and Epson 4490 scanners).
[U] File > Write Keyword Tags doesn’t write the map location (GPS coordinates) into the .xmp sidecar files of Nikon D80 or Canon G9 raw photos.
[U] The Organizer ignores correctly formatted EXIF GPS locations in some files that many other programs can read without trouble; this may be because the EXIF is encoded in little-endian byte order.
[U] New dates set by Edit > Adjust Date and Time sometimes get silently lost.
See http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Date/times_of_files for details and workarounds.
[U] Edit > Adjust Date and Time > Shift To New Starting Date And Time and > Shift By Set Number Of Hours writes the time in UTC rather than local time, as required by the standard, causing other tools to show the wrong date/time.
[U] In Thumbnail View, the Organizer incorrectly orders files that have unknown time. For example, it will show a file dated 12/25/1976 8:00 PM PST after a file dated 12/26/1976 (unknown time) on a computer in time zone PST.
[U] If you set a file's date/time fields to all unknown with Edit > Adjust Date And Time, the value of EXIF:DateTimeOriginal isn't cleared by File > Write Keyword Tag.
[U] Edit > Adjust Date and Time doesn’t properly handle US Daylight Savings Time when setting date/times many decades ago, e.g. October 5, 1961 12:00 PM.
[U] When setting the Organizer’s date/time for imported photos containing EXIF:DateTimeOriginal but not XMP:DateTimeOriginal, PSE 7 doesn’t properly handle US Daylight Savings Time in years prior to 2007, e.g. October 31, 2006 12:00 PM.
Minor Problems
[F] The Properties – Metadata window shows the wrong value for Date Time Original when the month, day, or time is unknown.
[F] When you save an edited photo as a new file but not in a version set, the edited version picks up the date/time and caption of the original but not the keyword tags, star rating, or notes.
Now, the edited version picks up date/time, caption, notes, and keyword tags, but not the star rating, which could be charitably interpreted as a plausible design decision.
[U] Deselecting the option Use “Last Modified” Date If EXIF Date Is Not Found does not work – the last-modified date is always used for an imported file that doesn’t contain an EXIF date.
[U] Edit > Adjust Date and Time applied to a file with time “unknown” decrements the date by one day.
[U] With the Import EXIF Caption option turned off, captions pre-existing in a file’s EXIF:ImageDescription metadata field reappear in the Organizer after invoking the Full Editor.
Searching
Major Problems
[U] The timeline doesn’t correctly display date ranges spanning many years.
[U] Using the Keyword Tags pane, you can no longer exclude a parent category from a search, e.g. exclude all photos tagged with any tag in the People category.
The User Guide gives two examples of how to use category exclusion that just don’t work in PSE 6, 7, or 8. Interestingly, you can almost work around this by doing a text search of “not <category tag>”, e.g. “not People”. But this will also exclude photos that happen to have the word “people” in their filenames, captions, or notes, probably not what you want. You can also use the text query “not tag:<category tag>”, .e.g. “not tag:places”, but this will exclude all tags containing “places” as part of their name – there is no way to get an exact match of a tag name.
[U] Find > By History > Imported On sorts the photo dates alphabetically, rather than by date/time.
When the results first display, they are now sorted by Imported From then (correctly) by Date/Time. However, if you click on the Date/Time column header to sort by that column, the dates are sorted alphabetically (incorrectly).
[U] Find > By History > Imported On takes a couple of minutes on a large catalog, making the command almost useless.
[U] Find > By History > Imported On shows a scary message “Deleting Keyword Tags” that is apparently harmless.
[U] Searching with the Find Bar for “1 star and lower” doesn’t show photos with 0 stars.
Find > By Details > Rating Is Lower Than 1 Star does work.
[U] Searching for “0 stars only” doesn’t work for photos in a catalog converted from PSE 5.
[U] Searching with date ranges doesn’t properly handle time “unknown”.
Minor Problems
[U] The Show All button sometimes doesn’t appear if you quickly type a query into the Search text box and hit Enter.
[U] Setting a date range and then excluding two tags from the search clears the date range.
[U] Show All doesn’t clear a date range set by Find > Set Date Range (can be very confusing).
[U] Save Search Criteria As Smart Album isn’t available if a date range has been set but no other search criteria have been.
[U] When searching, you can exclude a keyword tag and then include an album, but you can’t do it in the other order.
User Interface
Major Problems
[?] On 1024x768 displays, and sometimes at higher resolutions, the Editor Print window is positioned to perfectly obscure the scroll bar of the drop-down list of printer profiles, leading people to think their printer’s profiles aren’t available.
I can’t reproduce this in PSE 8. The Editor’s Print dialog is all rearranged. But this bug struck some people and not others, so it may be still lurking.
[U] The menu bars don’t display if you have changed the screen DPI to be larger than 96 (as many people do on today’s ubiquitous high-res displays).
Adobe should be embarrassed about this, given that more and more computers are shipping preconfigured with higher DPIs. See http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#The_Organizers_Menu_Bar_ doesnt_show for a workaround.
Minor Problems
[F] Copying a paragraph from Microsoft Word and pasting it into the Notes field of a keyword tag causes some of the spaces between words to be deleted.
[F] In the full Editor, if at least one open photo is minimized to the Project Bin, Ctrl-Tab no longer cycles through the open windows.
[F] The Editor window can’t be resized the standard Windows way by grabbing any edge, just the lower-right corner.
Well, almost – you can grab the left, right, and bottom edges but not the top.
[F] Alt doesn’t underline the shortcut letters of top-level menu items in the Full Editor (but it does in the Organizer).
Both the Editor and Organizer don’t show the underline until you let up on the Alt key, whereas other Windows program show the underline when you first press the Alt key.
[F] The width of the Editor's Palette Bin can't be adjusted by dragging the left edge, as you can with all the other similar panes (Project Bin, Organizer Bin, Map View).
[U] In the Properties window of Full Screen mode, if you click in the Notes field and do Ctrl-A to select all the text, then click in the Caption field and do Ctrl-A to select its text, the notes remain highlighted.
[U] In the Organizer, Help > System Info reports the wrong amount for “Built-in Memory” on computers with more than 2GB of installed memory. (The command reports the correct amount in the Editor.)
[U] The setting of View > Show Borders Around Thumbnails isn’t remembered after you restart PSE.
[U] Ctrl-A to select all text doesn’t work in the text fields of the Properties window.
Interestingly, you can use ctrl-A in the text fields of the full-screen mode Properties window.
[U] Dialogs in the Editor sometimes bounce back when you try to move them.
[U] Dates are shown by Display > Import Batch as 2\20\2008 rather than 2/20/2008.
[U] In Create > Slide Show > Slide Show Preferences dialog, you can't use backspace or delete to clear the text in the Static and Transition Duration fields -- you need to select the text and then type over the selection (non-standard Windows behavior).
[U] Escape doesn’t close the full-screen-mode Properties dialog.
[U] You can’t use the Windows Explorer Tile command to tile the PSE Organizer and Editor windows.
The Editor can now be tiled by Windows Explorer and other window managers, but the Organizer still can’t.
Slide Shows
Major Problems
[F] The duration of a video clip included in a Slide Show is set to the default duration, not the length of the video clip, and right-click Edit Duration doesn’t change the clip’s duration.
PSE now sets the duration to the length of the clip. You can’t edit the duration, though – you can invoke Edit Duration, but PSE ignores the new value.
[U] An audio caption attached to a photo isn’t imported into a slide show even though the option Include Audio Captions as Narration is selected.
For an individual slide, you can give the Use Existing Audio Caption command to import that photo’s existing audio caption.
Editor
Minor Problems
[F] The Editor crashes if you invoke Quick Fix and use just one Touch Up tool (e.g. Whiten Teeth) and then save the file (but your changes are correctly saved).
[U] The File > Save For Web command doesn’t remember the last settings (e.g. file format and quality) after your restart the Editor.
For a workaround, see http://www.johnrellis.com/psedbtool/photoshopelements-6-7-faq.htm#_Allow_Save_For.John,
Firstly, my apologies for the length of this post – it has been fermenting a while. For those in a hurry I have split it into two sections – the first contains some general comments on the situation with PSE (v 7 in my case) and Adobe (as I see it) and the second contains a list of issues that I have encountered and some suggestions for improvement. As with you, my comments are largely directed at the Organiser module within PSE.
Part 1:
Before going any further I’d like to say what an excellent job you’ve done in cataloguing, understanding and in many cases providing solutions to a number of bugs. Adobe should be paying you a hefty sum for doing this work. It’s a welcome change from a large percentage of what you read in blogs and forums to see things dealt with systematically, objectively and in an informed way.
I’m less impressed with Adobe’s approach. In my opinion, if you choose not to provide program updates to your customers (i.e. you get what you bought in the box and that’s it) then you have a moral obligation to make sure that what you sell is as robust and free of bugs as possible.
I would be very surprised if they were not well aware of the comments you have made (if they aren’t then that would indicate an appalling failure of their ability to process feedback). The fact that they have not, in subsequent releases, dealt with all of the issues that have been highlighted is not good. I would go further and suggest that it is actually a breach of fair trading practice and disingenuous to sell the product as “fit for purpose” knowing these bugs are still in place.
It’s unreasonable to expect software to be absolutely faultless, and this is why the issuing of updates is a much “fairer” system. The problem, I think, with Adobe’s approach is that to entice new customers to each release they need to provide new features. A natural consequence of this is that there is a temptation to prioritise development of new features rather than providing solutions to existing issues. There is no incentive for Adobe to change this state of affairs for as long as customers are purchasing their products. In this respect one of the problems is that many of the reviewers to whom prospective customers go will rely on first impressions and will not uncover many of the issues. Adobe may be comfortable with this situation (and on relying on the reflected aura of Photoshop) but their product is not cheap and there is plenty of scope for competitors to provide a more robust, dependable product at cheaper price. With free applications like Picasa they will need to be very careful they don’t drop the ball.
Don’t get me wrong I think the concept of PSE organiser is excellent (I actually prefer it to my experience of Lightroom), it is the quality of execution that I have issues with.
My first experience of PSE was version 3 and this was positive enough for me to purchase PSE 7. However, my biggest disappointment with PSE 7, because to me it is fundamental, has been the quality of rendering images in full screen mode. Yours is the first comment I have seen that comments on the appearance of “jaggies” when displaying images in PSE. My understanding is that this relates to the anti-aliasing which is carried out when converting from image to display resolution and the level to which this smoothes out gradients in hue, saturation and luminance. I never observed this problem is PSE 3. Although the degree of anti-aliasing is a subjective preference, I was deeply disappointed and still find it hard to believe that free or bundled software (picture manager, windows picture viewer, etc) can manage this when PSE 7 can’t.
Anyway, I’m not sure how to illicit a change from Adobe. One way is to write the sort of rant I have above although I doubt this will make much difference. In any case keep up the good work and hopefully something will come of it.
Part 2:
Some issues I’ve encountered:
Migration from Windows XP to Windows 7 – change in directory structure means that the “documents and settings” part of the user directory path in XP (i.e. c:\documents and settings\<<username>>\etc.) is now a shortcut which redirects you to the new location for user files which is c:\users\<<username>> \etc. If you are migrating from an old XP machine to a new Windows 7 one, you’ve kept your username the same and you have tried to retain the same directory structure then PSE 7 will still find files in your catalogue with the old style path. However, it will not recognise duplicates if you accidentally re-import the same files now they are on your Windows 7 machine. My workaround for this is to use an external file manager (e.g. windows explorer) to change the name of the directory that contains all of your photos. This causes PSE 7 to fail to resolve the path locations. You can then can select the relevant files and reconnect using the reconnect facility (File-Reconnect-Missing Files);
Watched folders are lost for any drive other than C when PSE 7 is closed and then reopened;
Duplicate files are not recognised and can be imported if they are not on the C drive (i.e. on an external drive);
Selecting a category selects all of the keyword tags/subcategories beneath it but excluding it does not exclude all of the keyword tags/subcategories beneath it; however, both selecting and excluding a sub-category selects and excludes the tags/sub categories beneath it;
Searches bring back the entire version set or stack even if only one of the files within meets the search criteria;
The instant search facility will sometimes decide that a number typed in is a date and will not find some files you would expect it to e.g. those where the number typed in is part of the filename rather than a date;
Anti-aliasing is insufficient – jaggies appear on jpegs displayed at certain zoom level. Interestingly this does not seem to occur if a jpeg has been created from a raw file through PSE 7 rather than an external application (at least for the camera I have).
Some suggestions:
Find duplicates facility;
Sort by filename and other file data;
Hide directories in the folder directory pane of the folder view if they contain no imported files – in PSE3 this was the only option and was actually quite useful to confirm that there were no imported files in a certain location (e.g. if e:\...etc was not in the list then you knew that you had no imported files located on the e:\ drive). It would be good to have this a display option.
Allow filters to be applied only to selected files;
Allow files to be rotated in the organiser without actually resaving them as a rotated file. -
Restore PSE 3 from a disc image to a re-formatted hard drive
I have Windows XP SP3 etc; Photoshop Elements 3.01; Acronis True Image 11; a 200GB hard drive (for images, audio, etc), a 250 GB hard drive for video storage and 500GB extl hard drive for backup of both hard drives. Some time ago I made a PSE backup onto the extl drive and a couple of incremental backups. I also have a disc image of both drives on the extl drive. With backup disc free space getting scarce I made a new full PSE backup and then deleted the original backups. To cure a number of conflict problems (due to multiple copies of Windows on both hard drives!) I re-formatted C drive and reinstalled the software, including PSE 3. I tried to restore my images and PSE catalog by means of PSE Restore from the PSE Backup; but after a while it asked me for discs/backups 2 and 3 - the ones I had deleted. All of the images are restored onto the C drive, but only a few tags - no Collection detail. Using Aconis I can mount the original disc image of the C drive, and the jpeg/CR2 and catalog psa files are in the usual place. However, file paths are somewhat different between the mounted copy of the C drive and the present actual C drive. Can anybody please advise me how to proceed from here? Is it just a case of using PSE 3 to move the catalog psa file from the Acronis mounted image into the C drive? The problem seems similar to the various threads that I've read on transferring to a new computer with PSE 7, but I am reluctant to "move" (as distinct from "copy") files from the Acronis image without some advice. Can anybody please offer some advice?
Hi dj_paige
Thanks a lot for the answer to my problem. Having resolved my problem with Acronis I then followed your instructions; the images and catalog with Collections etc are now fully restored. Thanks again for your help. -
I am new to PSE 12 and am trying to import my photos from folders on my desktop which I have organized by the categories I had in my previous program (Creative Memories). Many of my photos are located in multiple folders, i.e. one photo could be in "Family," Vacations" and "Birthdays." When I try to import the contents of each folder on my desktop I am often getting the message that many of my photos were not imported as they are already in my catalog. Is there a way that I can import any one photo multiple times so that it ends up in all the folders I want it to be in? I know I can locate the photo in PSE and copy it to a different folder(s), but there are so many not being imported that this would be a huge task!
By design, the organizer (and any other database management systems) is there to prevent you from duplicating your media files. The catalog management allows you to have the same image in different categories or albums. Duplication in different folders is to be absolutely avoided.
The same image file can have multiple tags like 'family', 'vacations', 'birthdays' and be present in three different albums with the same names. On obvious advantage is less disk space. Another one with your present folder system is that if you edit one of your duplicates, the other ones are unchanged.
I don't see an easy way to make your present folder structure simplified for the organizer ... -
Can not open CR2 files from a Canon 600D in PSE
Hi
Ok i will put my hand up and say i am very new to PSE, I have updated the software and have the latest camera raw plug in, but for some reason i can not open the raw files created by my 600D.
Can anyone help, or am i going to have to convert them.
Sorry if this has been asked before, but i couldn't find any posts
ChrisThe 600D should be supported in ACR 6.4 which is currently in beta so you'll have to wait until it's released, probably within days or weeks, for native support within Elements.
While you're waiting, you can download the beta version of the DNG Converter 6.4 from Adobe Labs and use that to convert your CR2 files to DNGs which will open in older versions of Camera RAW.
http://labs.adobe.com/
Follow the Camera RAW 6.4 RC link and eventually you'll get a link to download the DNG Converter 6.4 RC.
The Camera RAW 6.4 RC installer will only run if you have Photoshop, not Elements, so you can't use that, yet, but you can use the DNG Converter.
Because the DNG Converter and Camera RAW 6.4 are in beta status there could be differences in how the RAW photos look compared to when you get the released version of ACR 6.4 but probably not too much difference.
Maybe you are looking for
-
SanDisk Extreme Pro ExpressCard wont install ... ?
All, I have an older (2007) MacBook Pro lying around that I am attempting to turn into a "media" station for managing digital photos and whatnot. To make this work, I needed to (1) install Windows 7, and (2) get a reader that would let me access my S
-
Is there any way i can restore itunes to an earlier time/date, just like system restore? Thanks!
Hi.. Is there any way i can restore itunes to an earlier date/time? I accidentally lost a previous backup and now the file showing up is not the backup i want? Can i restore itunes to an earlier time like system restore on windows? Thanks!
-
Predictive text keyboard option is greyed out
I have turned on/off all keyboard and spelling options in Settings. Restore and setup as new? Keeping finders crozzed.
-
I accidentally have two accounts, how do I combine them?
I accidentally have two accounts, how do I combine them
-
Followed Tiscali set up info for Thunderbird and nothing works.
Changed from Outlook Express to Thunderbird on Win XP computer. Followed Tiscali set up info. Tiscali confirm the settings are correct but nothing works.