|
Post by fotofrank on Aug 8, 2016 0:47:44 GMT
The reason for my post. I have been working with Pat via Email. This was her latest post to me:
"Here is a photo scanned as a TIFF at 300dpi. Interesting that I did not use the number symbol or ampersand in the file name. Tried opening it in PSE14. It opened with no problems at all. Looks just as it is supposed to. Do you think that might have been the problem all along? I do know there was something else once upon a time I was working on and using those symbols caused problems."
my post was not based on a best guess.
I can not replicate the issue as my scan software will not allow me to create a 36 character long file name.
|
|
frizzylee
Junior Forum Member
Posts: 170
Open to constructive criticism of photos: Yes
|
Post by frizzylee on Aug 8, 2016 2:45:05 GMT
Hi All,
Sorry to have been out of touch. I did the following this morning. As you will see, of the 6 photos I picked at random, 4 opened correctly after being rescanned and being sure not to use # and/or. One photo (171) was scanned as Tiff but shows it was at 75 ppi, so I felt it wasn't "authentic"in the sense that all others were 300 ppi. Photo 161 still had the problem when opened even though it was scanned again without using # or &. That was a big letdown as I can see no reason for it. None at all.
I don't know what would happen if I kept checking photos. I am thinking of scanning all the photos over again without the # or &. It would also give me a chance to retitle them which needs doing. If I do this, I will open each scan in PSE as I go. Right now, it looks like my best shot.
It was a very busy day but I did manage to post on the Adobe site using the link Sepiana sent. Thank you so much, Sepiana. I hope someone weighs in with thoughts about it.
Pat
Photo Scan Problem – Aug 7, 2016
Notes:
Term “corrupted” means it opens with either transparency on the right side where the photo should be, or there is a rectangular block of striped-looking colors. Right side of photo is also cut off. Layers shows Layer 0, not Background.
# means I labeled all titles with a # in front of number of photo. i.e. #235 is photo number 235.
All photos were opened in Photoshop Elements 14 Editor.
Each photo was initially opened using the original scanned photo. When I write “rescanned original photo” that is exactly what I did. Took it from album and scanned it again but without # or &.
Photo 200 - File corrupted when opened Rescanned original photo eliminating # in title It opened normally, no problems
Photo 182 - File corrupted when opened Rescanned original photo, eliminating # in title It opened normally, no problems
Photo 171 - Original scan (with #) opened as it should; however, it was scanned at 75 ppi, not 300 ppi, as others were. Also, title had both # and & in it. I did not rescan.
Photo 139 - Original scan (with #) opened as it should It was scanned at 300 ppi; I did not rescan.
Photo 161 - Original scan opened with broken dotted line around it and in Layer 0. It had original # on it. When rescanned without the #, the whole problem showed up when it was opened in PSE14. The transparency was present on the right side. Photo was also cut off on right side.
Photo 151 - File corrupted when opened Rescanned without the # Then opened with no problems
|
|
frizzylee
Junior Forum Member
Posts: 170
Open to constructive criticism of photos: Yes
|
Post by frizzylee on Aug 8, 2016 4:29:18 GMT
One other thing I forgot to mention. I did uninstall a PSE version 10 that was on my computer. Then uninstalled PSE14 and installed it back in again.
Pat
|
|
|
Post by BuckSkin on Aug 8, 2016 4:49:41 GMT
Try this:
Take some plain old jpeg files that are already stored in your drive, at least a couple dozen; load these jpegs in your Elements 14 and "save as" 300ppi TIFF; put these new TIFF images in the same folder that has the scanned images; now, open these in your Elements 14 and see if they display properly.
Thanks for reading.
|
|
frizzylee
Junior Forum Member
Posts: 170
Open to constructive criticism of photos: Yes
|
Post by frizzylee on Aug 8, 2016 13:35:24 GMT
BuckSkin. . . . .I am in the process of trying what you suggest. Have an appointment this a.m. but will report back this afternoon.
|
|
frizzylee
Junior Forum Member
Posts: 170
Open to constructive criticism of photos: Yes
|
Post by frizzylee on Aug 8, 2016 13:48:45 GMT
As I told Sepiana I would report any news from the Adobe site. It's killing me because I have an appointment this a.m. and can't get to this until later today, but you can bet I will. There has been a posting and the person seems to know about it and can replicate my situation. It seems. It's only a quick reading on my part but I am so excited I just had to post you all. Maybe, just maybe, this may be it. I hope by posting this you can access the answer I received. forums.adobe.com/message/8927824#8927824Fingers crossed!! Pat
|
|
frizzylee
Junior Forum Member
Posts: 170
Open to constructive criticism of photos: Yes
|
Post by frizzylee on Aug 8, 2016 14:31:41 GMT
Okay, this is a preliminary report. I opened a photo with the problem in Preview and followed instructions. Sure enough, it opened in PSE14 with no problem. Did the same with a couple of others and they also opened correctly in PSE14. Then I noticed that I was having a hard time finding photos in the folder with the scanned photos that have the problem. There's lots of photos in that folder but I had no problem finding corrupted photos yesterday. It seemed every one was corrupted. I intend to ask R_Kelly (the Adobe poster) about this.
And yes, I need to leave here and get going, but some things are just irresistible, aren't they?
|
|
|
Post by BuckSkin on Aug 8, 2016 14:42:53 GMT
Yes, your link connects right to your posting on Adobe.
For what it is worth, I have scanned hundreds upon hundreds of photos on an old $29.99 HP DeskJet 2200 and a Windows 7 machine, saving as TIFF, first saving at 300-dpi, then 600-dpi, and finally settling on 1200-dpi as the best option.
Of the many many photos I have scanned, I have not had a single TIFF file to display the behavior you are seeing.
|
|
|
Post by fotofrank on Aug 8, 2016 14:58:47 GMT
I can confirm that following that extra process does allow the image to be opened correctly in Elements. It does do a few other things. The file size is reduced by 24k, Image size stay the same and the .tif no longer shows up in the file name.
|
|
|
Post by Sepiana on Aug 8, 2016 15:08:55 GMT
As I told Sepiana I would report any news from the Adobe site. It's killing me because I have an appointment this a.m. and can't get to this until later today, but you can bet I will. There has been a posting and the person seems to know about it and can replicate my situation. It seems. It's only a quick reading on my part but I am so excited I just had to post you all. Maybe, just maybe, this may be it. I hope by posting this you can access the answer I received. forums.adobe.com/message/8927824#8927824Fingers crossed!! Pat
Pat, thanks for posting the link! I will take a look at your thread there.
|
|
|
Post by Sepiana on Aug 8, 2016 17:41:35 GMT
Okay, this is a preliminary report. I opened a photo with the problem in Preview and followed instructions. Sure enough, it opened in PSE14 with no problem. Did the same with a couple of others and they also opened correctly in PSE14. Then I noticed that I was having a hard time finding photos in the folder with the scanned photos that have the problem. There's lots of photos in that folder but I had no problem finding corrupted photos yesterday. It seemed every one was corrupted. I intend to ask R_Kelly (the Adobe poster) about this.
Pat,
I have just checked your Adobe forum thread. I noticed R Kelly, an Adobe Community Professional (ACP) is helping you. You are in good (excellent) hands; I am quite familiar with Kelly's work.
I am also pleased to read this advice -- "You might also experiment with setting the scanner to output png files instead of tiff. Png is a lossless format like tif". It goes hand in hand with the concern some of us had about you setting your scanner for JPEG files. That would have not been a good thing to do.
|
|
frizzylee
Junior Forum Member
Posts: 170
Open to constructive criticism of photos: Yes
|
Post by frizzylee on Aug 10, 2016 0:33:09 GMT
For Buckskin: I put 20 jpg photos into a folder. Did as suggested: oad these jpegs in your Elements 14 and "save as" 300ppi TIFF; put these new TIFF images in the same folder that has the scanned images; now, open these in your Elements 14 and see if they display properly. All of these photos displayed as they should. No problems with any of them. This was a good eye-opener for me. The TIFF photos are amazingly better. Thanks for the lesson. Pat
|
|
|
Post by BuckSkin on Aug 10, 2016 0:50:45 GMT
For Buckskin: I put 20 jpg photos into a folder. Did as suggested: oad these jpegs in your Elements 14 and "save as" 300ppi TIFF; put these new TIFF images in the same folder that has the scanned images; now, open these in your Elements 14 and see if they display properly. All of these photos displayed as they should. No problems with any of them. This was a good eye-opener for me. The TIFF photos are amazingly better. Thanks for the lesson. Pat That being the case, then it probably is not the drive that is corrupting the files. When you have one of the 300-dpi TIFF in Elements, look in lower-left just below the image window and see what the image dimensions at _-ppi says. Then, scan a TIFF at 1200-dpi and see the difference. The more dpi you scan in, the more detail and image quality you have to work with, and the larger they will print. A 5x7 photo scanned at 300-dpi will only print reasonably well at the original 5x7 size. Thanks for reading.
|
|
|
Post by Sepiana on Aug 10, 2016 2:43:06 GMT
For the benefit of anyone following this thread . . . here is a summary of where we stand on this issue.
Pat followed my suggestion and posted in the Adobe forum. She is being helped by R Kelly (who acknowledged having seen this problem before, was able to replicate it, and provided a solution).
forums.adobe.com/message/8927824#8927824
Here is Pat's initial report.
Okay, this is a preliminary report. I opened a photo with the problem in Preview and followed instructions. Sure enough, it opened in PSE14 with no problem. Did the same with a couple of others and they also opened correctly in PSE14. Then I noticed that I was having a hard time finding photos in the folder with the scanned photos that have the problem. There's lots of photos in that folder but I had no problem finding corrupted photos yesterday. It seemed every one was corrupted. I intend to ask R_Kelly (the Adobe poster) about this.
Frank (fotofrank) has confirmed that Kelly's suggestions work.
I can confirm that following that extra process does allow the image to be opened correctly in Elements. It does do a few other things. The file size is reduced by 24k, Image size stay the same and the .tif no longer shows up in the file name.
So, it looks like there is light at the end of the tunnel for Pat. I suggest we all keep an eye on that thread.
|
|
frizzylee
Junior Forum Member
Posts: 170
Open to constructive criticism of photos: Yes
|
Post by frizzylee on Aug 10, 2016 3:47:08 GMT
For fotofrank:
Thanks for the info charts comparing the difference with/without the Alpha Channel. I will be interested to look at the PNG format as well. I think I'm okay with the 24K reduction. Will have to look at the missing .TIFF file name.
|
|