|
|
Post by Sepiana on Aug 6, 2016 23:48:26 GMT
I scanned four photos as usual, except I scanned them as jpg's. Then opened each one in Photoshop Elements 14 Editor. They opened with no trouble and there is no sign of the previous problem. So at least I have a work-around for the time being. It still doesn't explain why some open normally and others don't. So, long story short, I can keep on scanning but I would still like to know what is going on. So I have registered on the Photo Family site and will continue to try to find the answer. Should that happen I will post here. I will also give you the link to the thread if there is good information coming from it. Pat, I think it is a great idea! You should not settle down for workarounds. You will never know when you will be needing TIFF files for a project.
Just a little clarification. I don't want anyone to be misled as to this . . .
I am assuming you are referring to the forum I gave you the link earlier in this thread. The "Family" in the name of the forum refers to the Adobe "family" -- Elements and its big brother, Photoshop. This is a forum where you can post any questions related to Elements.
|
|
frizzylee
Junior Forum Member
Posts: 170 
Open to constructive criticism of photos: Yes
|
Post by frizzylee on Aug 7, 2016 0:42:00 GMT
Sepiana I'm glad you brought this up as I was a little confused. I used the second link you suggested: It seemed like I was in the right place, but they wanted me to register, which I did. It said I was registering in PhotoFamily. I will look at it carefully before I post my plight to them. ha |
|
|
|
Post by Sepiana on Aug 7, 2016 0:54:53 GMT
Sepiana I'm glad you brought this up as I was a little confused. I used the second link you suggested: It seemed like I was in the right place, but they wanted me to register, which I did. It said I was registering in PhotoFamily. I will look at it carefully before I post my plight to them. ha
Either the Adobe Feedback forum or the Adobe Photoshop Elements forum (the other link I posted) will do. Adobe employees are known to participate in those forums.
Yes, you have to register if you want to post. It is just like any other forum; guests are not allowed to post. You need to be a registered member.
|
|
|
|
Post by PeteB on Aug 7, 2016 1:16:21 GMT
Has anyone suggested resetting Elements' preferences?
|
|
|
|
Post by Sepiana on Aug 7, 2016 1:34:56 GMT
Has anyone suggested resetting Elements' preferences?
Pete, I had thought about it but I brushed it aside because the problem seems to be confined to scanned TIFF files. A corrupted Preferences file would probably cause the problem to show up with other kinds of files. What do you think? Is it worth a try?
Sorry it took me so long to get back to this thread; I was at the Adobe forums checking the reports on scanning, TIFF files, Elements, etc. At this point I am getting more and more convinced it is an Elements issue and not one with your scanner or your iOS. The reports seem to center on the amount of RAM vs the size of the TIFF files as well as on a possible corrupted Preferences file. I believe we can rule out the latter. If it were a Preferences file being corrupted, I don’t think you would have the situation you describe-- some scanned TIFF files are OK when you open them in Elements; others are not.
I sincerely don't like the idea that Pat is settling to scan her files as JPEG, particularly if she is going to do some editing in Elements before sending them to print. I also have an Epson scanner. Here is what the User Guide suggests.
Source: Selecting Epson Scan Settings |
|
frizzylee
Junior Forum Member
Posts: 170
Open to constructive criticism of photos: Yes
|
Post by frizzylee on Aug 7, 2016 1:59:36 GMT
Just read Pete's post. Ouch! I've never seen the difference between jpg and tiff spelled out as clearly as this. One thing that is a given for me. . . . . .these photos will be edited, some of them a lot. Well, as my father use to say, I better "get the lead out" and post to the Adobe site.
|
|
|
|
Post by PeteB on Aug 7, 2016 17:12:32 GMT
Has anyone suggested resetting Elements' preferences?
Pete, I had thought about it but I brushed it aside because the problem seems to be confined to scanned TIFF files. A corrupted Preferences file would probably cause the problem to show up with other kinds of files. What do you think? Is it worth a try? Pat and Sepiana, I think it is worth a try ... if you seek help at Adobe, probably resetting preferences will be the first suggestion. Also, I agree scanning to a tiff makes better sense. |
|
|
|
Post by fotofrank on Aug 7, 2016 17:23:07 GMT
The resolution to the issue is not to use special characters in the file name. The scanned images had a & and # in the long file name on a MAC. Not using those characters in the file name allowed the scanned image to be opened with no issue in Elements.
|
|
|
|
Post by cats4jan on Aug 7, 2016 18:21:41 GMT
Frank - excellent catch - I bet this is just what the problem is. That thought had popped into my head - but unfortunately, there is nothing between the ears keeping my thoughts in nowadays - so I forgot to pass on the idea.  I once was trying to use a period in the name of my file. DUH - it took me forever to figure out why I had such weird formats beyond the period and why my files weren't saving as they should. |
|
|
|
Post by Sepiana on Aug 7, 2016 18:38:12 GMT
The resolution to the issue is not to use special characters in the file name. The scanned images had a & and # in the long file name on a MAC. Not using those characters in the file name allowed the scanned image to be opened with no issue in Elements. Frank,
Thanks for the input! You nailed the issue on the head. Way to go!
I just want to add that this is not a problem for Window users. You can use "&" and "#" in a file name without any problems. Elements will accept them. I do it all the time.
I am glad that Pat won't have to settle for JPEG files when scanning. And it should go along with what Pete said earlier.
Pat and Sepiana, Also, I agree scanning to a tiff makes better sense. |
|
|
|
Post by BuckSkin on Aug 7, 2016 18:40:47 GMT
As to file names, some image editing programs will not recognize images with long file names; that was a hard one for me until I got it figured out using Luminance HDR; I shortened the file-names of the offending images and they went right through there.
Interestingly, in Windows 7, I use "&" quite a bit with no negative issues thus far; whenever I put a wrong character in a file-name, I get a warning telling me I can't use such and such.
|
|
Moto
Established Forum Member
Posts: 662 
Open to constructive criticism of photos: Yes
|
Post by Moto on Aug 7, 2016 19:50:43 GMT
Windows: Un-acceptable filename characters. \  |
|
|
|
Post by Sepiana on Aug 7, 2016 20:15:02 GMT
Moto,
Yes, those are unacceptable filename characters on Windows. However, we get a warning when we use them. Pat is on a Mac and she was getting no warning (as far as I know) despite her inclusion of "#" and "&" when she named her files.
|
|
|
|
Post by PeteB on Aug 7, 2016 20:56:17 GMT
On my Mac, I tried scanning a color photo with an Epson scanner and I saved the file using the characters # and & in the file name. I had no problem saving the file and it easily opened in PSE 12. I'm using OS 10.9.5
Hopefully Frank's suggestion will be the answer, but we won't know until Pat gives it a try.
|
|
|
|
Post by Sepiana on Aug 7, 2016 21:13:39 GMT
Pete,
This is quite interesting. This is what Pat uses.
I am running OSX El Capitan v. 10.11.6 on both my MacBook Pro and on my iMac. Most of the scans have been done using MacBook Pro. I agree with you. We need Pat to confirm if the filename was indeed the culprit.
|
|
