I crop images, resize them to 2000x2000 and save as png. When I check dimensions (usually in bridge) - bridge shows me different dimensions. I open it in Photoshop - it's 2000x2000. I select properties of file in explorer - 2000x2000. In bridge - others. And I don't know it's a bug of Bridge or of Photoshop (perhaps it does not changed some metadata of file).
Photoshop 19.0 x64, Bridge 8.0.0.262 x64
PS I sent these files to another person, she has previous versions of Bridge and Photoshop - all the same. Photoshop show one size, Bridge - another.
Photoshop 19.0 x64, Bridge 8.0.0.262 x64
PS I sent these files to another person, she has previous versions of Bridge and Photoshop - all the same. Photoshop show one size, Bridge - another.
Posted 2 years ago
Todd Shaner, Champion
It's possible Bridge isn't updating the file. I've had that happen before, and PNG files seem to be the worst. But it should have updated when it got sent to your friend who had never had it cached on disk. Otherwise I'd think that purging cache might force Bridge to update the image to reflect the cropped dimensions.
I'm not seeing the problem here, but if you'd provide more information about your OS and what version of Bridge and PS you're running, it would help the Adobe team test any file you upload on the same OS and version.
I'm not seeing the problem here, but if you'd provide more information about your OS and what version of Bridge and PS you're running, it would help the Adobe team test any file you upload on the same OS and version.
These files was not in this folder before. And if it was a day or two ago (parent files with full article) - they also was 2000x2000, all files in this directory have these dimensions. I purged cache, it was my first intention. I restarted PC. Nothing changed.
images https://yadi.sk/d/Rqkfnqg33NxhsM
my config is Win 10 Pro, Photoshop 19.0 x64, Bridge 8.0.0.262 x64 (both - last versions, installed a few days ago)
my config is Win 10 Pro, Photoshop 19.0 x64, Bridge 8.0.0.262 x64 (both - last versions, installed a few days ago)
eartho, Champion
How did you create the .png? Save for Web, Export As, Save As, Lightroom?
Save As
params in screenshot
params in screenshot
Todd Shaner, Champion
I can confirm what you are seeing. When using PS 2018 'Save as PNG' Bridge incorrectly displays the XMP-tiff 'ImageWidth' and 'Image Height' metadata fields in the PNG file. Since your friend sees the same issue using PS 2017 and Bridge 2017 it would indicate a bug in PS 2018 'Save As PNG.'
All other methods of creating a PNG in PS don't exhibit this issue. A camera raw image file was cropped to 1x1 and Exported to TIFF using LR Classic. The TIFF file was then resized to 2000x2000 inside PS 2018 and output using the below methods. I'm on Windows 7 SP1 64 bit.
All other methods of creating a PNG in PS don't exhibit this issue. A camera raw image file was cropped to 1x1 and Exported to TIFF using LR Classic. The TIFF file was then resized to 2000x2000 inside PS 2018 and output using the below methods. I'm on Windows 7 SP1 64 bit.
Todd Shaner, Champion
Cristen, it appears to be a Windows system only issue. I checked the PNG files again in numerous other applications and they all show 2000x2000 pixel Width and Height dimensions. So it's not a PS issue, but a bug in Bridge 2018 (verion 8.0).
(Edited)
and in previous version of Bridge also. The person whome I send these files has Bridge 7.0. Perhaps Bridge uses some different parameters?
It shouldn't. But when it comes to Bridge. . . I rely upon Bridge all day every day, but I have learned to rely upon it with the suspicion that at any given moment during the day, it won't work properly. <sigh>
As for whether or not it's in the previous version of Bridge—I'm not so sure. I would have thought we'd be hearing about it for a long time now if that were the case. You're sending a file from your version to your friend's version, so it is quite possibly carrying along the erroneous metadata. Your friend would have to take one of her own files that has never seen 2018 and follow your exact procedure, from opening in Photoshop to saving in Photoshop exactly the way you did, to then looking at it in her pristine 2017 version of Bridge. If it happens to her files, too, then very possibly, yes, it's a bug no one has found before—maybe by simply not looking at the conflicting dimensions because they don't save to a standard file size the way you do. Actually, you didn't report it in 2017, either???
As for whether or not it's in the previous version of Bridge—I'm not so sure. I would have thought we'd be hearing about it for a long time now if that were the case. You're sending a file from your version to your friend's version, so it is quite possibly carrying along the erroneous metadata. Your friend would have to take one of her own files that has never seen 2018 and follow your exact procedure, from opening in Photoshop to saving in Photoshop exactly the way you did, to then looking at it in her pristine 2017 version of Bridge. If it happens to her files, too, then very possibly, yes, it's a bug no one has found before—maybe by simply not looking at the conflicting dimensions because they don't save to a standard file size the way you do. Actually, you didn't report it in 2017, either???
No, I didn't. I encountered this bug only yesterday and posted it here. I think about next (if it's possible) - perhaps Bridge reads some different metadata for dimensions, than other programs do. Photoshop 2018, saving as png copy wrong parameters and if Photoshop it does, than all versions of Bridge will show wrong numbers. Photoshop 2017 does all correctly, perhaps.
Hm, I viewed metadata of file using program exiftool, and it shows next values:
Image Width : 2000
Image Height : 2000
Exif Image Width : 3982
Exif Image Height : 3982
Evidently, Bridge shows us Exif Image Height and width instead of Image Height and Width.
This bug appears only in some images. I processed yesterday about 80 images with this action and it appeared only around at 10 of them. For others images params in exiftool are
Image Width : 2000
Image Height : 2000
Exif Image Width : 2000
Exif Image Height : 2000
Sorry for my English, i make mistakes for sure... Hope you understood what i meant.
Hm, I viewed metadata of file using program exiftool, and it shows next values:
Image Width : 2000
Image Height : 2000
Exif Image Width : 3982
Exif Image Height : 3982
Evidently, Bridge shows us Exif Image Height and width instead of Image Height and Width.
This bug appears only in some images. I processed yesterday about 80 images with this action and it appeared only around at 10 of them. For others images params in exiftool are
Image Width : 2000
Image Height : 2000
Exif Image Width : 2000
Exif Image Height : 2000
Sorry for my English, i make mistakes for sure... Hope you understood what i meant.
(Edited)
Your English is just fine. I'm trying to figure out what Bridge is doing, and it's most odd. Can you find anything in common between the images that turn up the wrong Exif that is different from the images that are correct? Where they're coming from, when they were created, what version they were saved from, anything?
Since Todd can repeat it, it can't be a non-English localization bug or in an action he doesn't have.
Maybe one of the Adobe Staff here can get someone from the Bridge team who can tell you where to upload a couple files to them that are showing the wrong numbers so they can find the culprit. Todd can then perhaps contribute his own file and between two sources, they can pin it down.
It's almost worse for you having it reported incorrectly only some of the time, because you have to look harder to know it's the bug, not just a file that hasn't been processed by the action. I wish you luck getting it tracked down.
Since Todd can repeat it, it can't be a non-English localization bug or in an action he doesn't have.
Maybe one of the Adobe Staff here can get someone from the Bridge team who can tell you where to upload a couple files to them that are showing the wrong numbers so they can find the culprit. Todd can then perhaps contribute his own file and between two sources, they can pin it down.
It's almost worse for you having it reported incorrectly only some of the time, because you have to look harder to know it's the bug, not just a file that hasn't been processed by the action. I wish you luck getting it tracked down.
eartho, Champion
It's not windows only, i also see the incorrect dims using MacOS10.11.6 and Bridge CC2018.
These images are from one session, i converted them into psd from lightroom (previous version) simultaneously, i can run this action once time again and it will save all correcly. (I did this for others 6 or 5 photos that I noticed first, not really figuring out what happened - and it worked - all files were 2000x2000 after second iteration. And yes, I think it's a random bug.
I use English version of Photosop, don't like localization.
Now, when i know, that it's a bug with metadata, not with dimensions themselves, I think I can deal with it, it's not so bad that if it was a bug with real dimensions. But it's uncomfortable.
I use English version of Photosop, don't like localization.
Now, when i know, that it's a bug with metadata, not with dimensions themselves, I think I can deal with it, it's not so bad that if it was a bug with real dimensions. But it's uncomfortable.
eartho, Champion
Alright, so for me when i save the png, Large and Medium option will provoke the bug, but saving with smallest file (save as) will display the correct dims. Using Save for Web with any of the metadata options also works as expected.
I'm thinking this bug is related to the bloated metadata files. The original png's are 11MB, but when i save for web or save as small, the files are 3.3MB...
I'm thinking this bug is related to the bloated metadata files. The original png's are 11MB, but when i save for web or save as small, the files are 3.3MB...
Todd Shaner, Champion
OK, I opened the same LR TIFF export file and processed it again exactly the same way. All methods of creating a PNG file with PS 2018 are showing as 2000x2000 pixels in Bridge 2018 (version 8.0). I now cannot duplicate the issue! I'll try it again in the morning after a system reboot.
I tried again, too. I cropped to roughly 2000x2000 px, but left big data intact. Then I used File> Save As, and picked PNG, Large size (fastest save) — which is what I'd used before the other times I'd used Save As — and still Bridge had no problem with it.
Next I took the same image, cropped it so it was a square closer to 2600x2600 px, left big data intact, left it at 16 bit, used Save As with Medium, Export As, Quick Export as PNG, and SFW. All of them came through with the right dimensions. I'm at a loss here. I'll no doubt run into it one of these days, but if they can't replicate it, they can't fix it.<sigh>
Next I took the same image, cropped it so it was a square closer to 2600x2600 px, left big data intact, left it at 16 bit, used Save As with Medium, Export As, Quick Export as PNG, and SFW. All of them came through with the right dimensions. I'm at a loss here. I'll no doubt run into it one of these days, but if they can't replicate it, they can't fix it.<sigh>
Avinash Kumar Singh, Employee
I have also tried these images on Photoshop 19.0 x64, Bridge 8.0.0.262 x64 but not able to reproduce this issue . If there is some reproducible steps please let us know so that we can fix it.
Here are the snapshots that I have tried on PS and Br latest versions
Here are the snapshots that I have tried on PS and Br latest versions
Todd Shaner, Champion
After rebooting this morning I'm unable to reproduce the issue using the same TIF file and or 2nd LR export TIF file. I've uploaded the original PNG file from yesterday that exhibits the issue to Dropbox. It's was created using a 5D MKII camera raw file (5616x3744) with 1x1 Crop (3744x3744), exported to 16 bit, ProPhotoRGB, TIF file format using LR Classic. The file was then resized to 2000x200 using Image Size> Automatic and 'Save As' PNG Large File Size in PS 2018 (19.0).
Inside Bridge 2018 (Version 8.0) it shows Dimensions as 3744x3744. Inside LR, PS, Windows Explorer, and numerous other applications it shows Dimensions as 2000x2000.
https://www.dropbox.com/s/52epnujf1mihj02/Lightroom%201x1%20Crop%20and%20Export_PS%20Image%20Size%20...
Here's the original TIF file that was used to create the above PNG file:
https://www.dropbox.com/s/qisv14mk8jy352t/Lightroom%201x1%20Crop%20and%20Export.tif?dl=0
Inside Bridge 2018 (Version 8.0) it shows Dimensions as 3744x3744. Inside LR, PS, Windows Explorer, and numerous other applications it shows Dimensions as 2000x2000.
https://www.dropbox.com/s/52epnujf1mihj02/Lightroom%201x1%20Crop%20and%20Export_PS%20Image%20Size%20...
Here's the original TIF file that was used to create the above PNG file:
https://www.dropbox.com/s/qisv14mk8jy352t/Lightroom%201x1%20Crop%20and%20Export.tif?dl=0
(Edited)
Avinash Kumar Singh, Employee
Avinash Kumar Singh, Employee
Hi ,
For files that you are getting incorrect/different dimension try selecting those files right click and select purge cache for selection . And then check the dimension info . Please let us know if you are still getting this issue.
Thanks,
Avinash
For files that you are getting incorrect/different dimension try selecting those files right click and select purge cache for selection . And then check the dimension info . Please let us know if you are still getting this issue.
Thanks,
Avinash
I did this first time i get this error, it does not helped. As I deleted all tests that I made then, now i repeated my test.
I saved 63 files in batch. This time first 8 photo, 10th and 12th have parent dimensions. I selected them, purged cache for them - nothing changed.
Yes, it does not help.
I saved 63 files in batch. This time first 8 photo, 10th and 12th have parent dimensions. I selected them, purged cache for them - nothing changed.
Yes, it does not help.
(Edited)
Aurica Crudu