I have just installed the 2015 CC edition of Light Room but am having problems publishing and exporting photographs. When either exporting to hard disk or publishing to FlickR, I'm getting 5 or 6 random, all white images.
Posted 5 years ago
Steve Sprengel, Champion
Steve Sprengel, Champion
Hi Steve!
Thanks for taking the time to investigate this...
The blank photo takes the place of an intended photo.
Photos are same orientation and sometimes different sizes.
Up to now I only had the problem with watermarked photos. I will try it today without the watermark.
Watermark are PNG images.
Also, I have installed recently on my computer ImageMagick to create PDF image, I am wondering if the mogrify of Lightroom may have problem with the ImageMagick mogrify...
Thanks for taking the time to investigate this...
The blank photo takes the place of an intended photo.
Photos are same orientation and sometimes different sizes.
Up to now I only had the problem with watermarked photos. I will try it today without the watermark.
Watermark are PNG images.
Also, I have installed recently on my computer ImageMagick to create PDF image, I am wondering if the mogrify of Lightroom may have problem with the ImageMagick mogrify...
I don't have ImageMagick but get the same problem.
Thanks for the feedback David!
Steve Sprengel, Champion
I have tried exporting 147 photos to my hard disk - all as jpg.
If I have the watermark turned on, then 3 of them were completely white, apart from the watermark. Interestingly, using Windows Explorer to view the thumbnails then these are all ok. It is only when the file is opened that the image is white.
If I export the three images again, by themselves, then they export correctly. It is only when they are part of a large batch.
When I turned off adding a watermark and then exporting all 147 images again, they all exported OK.
Exporting the entire batch, with watermarking turned back on, then the same three images were all white.
The file size of the blank images are between 300KB to 400KB but when exported correctly, they are around 16MB.
I have uploaded the blank image.
If I have the watermark turned on, then 3 of them were completely white, apart from the watermark. Interestingly, using Windows Explorer to view the thumbnails then these are all ok. It is only when the file is opened that the image is white.
If I export the three images again, by themselves, then they export correctly. It is only when they are part of a large batch.
When I turned off adding a watermark and then exporting all 147 images again, they all exported OK.
Exporting the entire batch, with watermarking turned back on, then the same three images were all white.
The file size of the blank images are between 300KB to 400KB but when exported correctly, they are around 16MB.
I have uploaded the blank image.
CORRECTION. When exporting the entire batch for the 2nd time, with watermarking turned back on, 3 images where all white, 2 of these were the same as the 1st time, but 1 was a different image.
Same behavior here... I hope Adobe will get this fixed. I tried to contact support but it does not seems to be an option... Pay for the software and get bugs and no support. Great business model! :)
Steve Sprengel, Champion
Someone at Adobe supposedly reads each thread here, at least initially, so even though you cannot get a personal interaction with someone from Adobe now 18 days after the thread was started, that doesn't mean no one at Adobe has seen this. I'd guess someone has submitted a bug internally, already. Hopefully they will be able to fix it by the next release, especially since the same issue happened at the beginning of the LR 5 release phase.
My wife and I are both also having this problem on two different systems, but it also happened in LR 5.7. When we batch export, we sometimes (but not always) get the white thumbnail and/or white image. Sometimes the thumbnail is correct, but the file is white when opened.
It doesn't seem to matter if it's a single batch export or simultaneous batch exports:
Exporting one folder at a time, each about 500 images:
"Export Results" says 3 files "could not be opened", but I was able to individually export them.
8 images were blank (logo on white). All 8 exported correctly when individually exported.
Simultaneous export of two folders, each about 500 images:
"Export Results" says 5 files "could not be opened", but I was able to individually export them.
10 images were blank (logo on white). All 10 exported correctly when individually exported.
The files which "can't be opened" or export as white are scattered throughout the folders being exported.
It's really troubling that the thumbnails sometimes show the image, and that this problem has appeared for quite a while.
How many of us actually want to open each file to know if the export worked? When we don't check each file, we end up uploading a lot of blank images to an online gallery - very unprofessional looking.
What makes the export problem additionally difficult is when files are renamed on export. (We rename by groups and sequence number within the sporting event to make it easier for the clients.) It makes it very difficult to go back and locate the file which needs to be re-exported.
Really, I don't care about facial recognition, mapping, or other "bells and whistles". Exporting is core functionality that I do care about.
It doesn't seem to matter if it's a single batch export or simultaneous batch exports:
Exporting one folder at a time, each about 500 images:
"Export Results" says 3 files "could not be opened", but I was able to individually export them.
8 images were blank (logo on white). All 8 exported correctly when individually exported.
Simultaneous export of two folders, each about 500 images:
"Export Results" says 5 files "could not be opened", but I was able to individually export them.
10 images were blank (logo on white). All 10 exported correctly when individually exported.
The files which "can't be opened" or export as white are scattered throughout the folders being exported.
It's really troubling that the thumbnails sometimes show the image, and that this problem has appeared for quite a while.
How many of us actually want to open each file to know if the export worked? When we don't check each file, we end up uploading a lot of blank images to an online gallery - very unprofessional looking.
What makes the export problem additionally difficult is when files are renamed on export. (We rename by groups and sequence number within the sporting event to make it easier for the clients.) It makes it very difficult to go back and locate the file which needs to be re-exported.
Really, I don't care about facial recognition, mapping, or other "bells and whistles". Exporting is core functionality that I do care about.
Spot on Nuff said we pay our money and we except it deliver like it did
John R. Ellis, Champion
The bug causing "The file could not be opened" has a specific cause (bug) -- see my post in this topic: http://feedback.photoshop.com/photosh...
David - if exporting to JPEG, an easy way to check whether the image is OK is to sort by file-size. The faulty images are a lot smaller.
Steve Sprengel, Champion
You may be describing two unrelated issues happening to your exports.
The files-cannot-be-read could be a simple permissions problem, but also occurs if another process is also trying to manipulate (or read) the file at the same time LR is doing something with it. This has been reported if the export folder is a local dropbox folder as well as if the folder is being "watched" by Bridge. This is less a bug in LR and more of a user-created situation where two processes are interfering with each other (or there is a permissions problem).
The white exports are due to the watermark and a bug in LR6. LR 5.0 beta had the same problem some years ago. Hopefully Adobe can fix this one quickly as it's been reported many times since LR 6 came out. A workaround would be to not watermark during the export and use another product afterwards. I don't have anything free to recommend, but if you also have PS as part of the CC Photography Plan, then there may be a script somewhere that can do watermarks.
The files-cannot-be-read could be a simple permissions problem, but also occurs if another process is also trying to manipulate (or read) the file at the same time LR is doing something with it. This has been reported if the export folder is a local dropbox folder as well as if the folder is being "watched" by Bridge. This is less a bug in LR and more of a user-created situation where two processes are interfering with each other (or there is a permissions problem).
The white exports are due to the watermark and a bug in LR6. LR 5.0 beta had the same problem some years ago. Hopefully Adobe can fix this one quickly as it's been reported many times since LR 6 came out. A workaround would be to not watermark during the export and use another product afterwards. I don't have anything free to recommend, but if you also have PS as part of the CC Photography Plan, then there may be a script somewhere that can do watermarks.
I have LR and PS as part of the CC plan and suffer this miss firing problem and at the moment really cheesed off with Adobe for not even acknowledging the problem
I also have this problem. Random blank images but the thumbnail is fine. Really disappointing to search through 600 wedding photos to find every blank image!
I'll try the workaround to export without a watermark.
I'll try the workaround to export without a watermark.
Steve Sprengel, Champion
If you also have PS-CC then temporarily open Bridge on the output folder and make sure you have high-quality-thumbnails turned on, then Bridge will show white thumbnails, which makes things much easier to find.
Close Bridge before you Export otherwise it can interfere with writing the output files from LR.
Close Bridge before you Export otherwise it can interfere with writing the output files from LR.
So How can we the customer escalate this problem higher to Adobe ?
It would be reassuring if someone from Adobe responded to at least say they are looking into it.
Posting a link to this discussion on Twitter / facebook might raise the profile of this problem.
It would we reassurring but I think they are too busy counting the money they make from the new subscription model $$$$ :) No time to correct bugs and they don't even care. Try to contact them to report a bug. Would you buy a car again knowing that the car has problem and the company don't want you to show up at their garage to get it fixed?
Victoria Bampton - Lightroom Queen, Champion
They're busy finding and fixing the bugs. There's another related thread a couple of threads back where they replied saying they were checking into export problems though.
They don't need to find bugs, the forums are full of them. If they could fix the bugs, people would not complain on the forums. If Adobe could care for customers, we could call/email them about bugs... but that's not the case.
They don't even do a follow-up on this bug. The developer are probably too busy writing mobile stuff to make it works (or maybe they don't know how to fix it?)
Adobe don't care for their customers; only for the money of their customers.
They don't even do a follow-up on this bug. The developer are probably too busy writing mobile stuff to make it works (or maybe they don't know how to fix it?)
Adobe don't care for their customers; only for the money of their customers.
Well if they are finding and fixing the bugs I have had no updates yet ?
Victoria Bampton - Lightroom Queen, Champion
They got an initial update out a few weeks ago to address the immediate critical bugs. Updates are usually 2-4 months apart - nothing happens quickly in huge corporations. I'd expect to see another update released before too long.
lets hope so because at the moment this problem is really annoying even considered loading up my old version and cancelling CC
Rikk Flohr, Official Rep
After reading through this thread and thus far being unable to duplicate (in spite of over 3000 exported images in a couple dozen batches) this issue I need to ask the following. Are all of those on this thread, having this issue:
Using Windows 8 or later?
Exporting as JPEG?
Using a watermark?
Uploading many images >50?
If any one of these is not true, let us know.
Using Windows 8 or later?
Exporting as JPEG?
Using a watermark?
Uploading many images >50?
If any one of these is not true, let us know.
John R. Ellis, Champion
I reproduced the problem on Windows 8, exporting ~125 JPEGs at full size and quality 60, with all metadata, with a graphical watermark. In a batch of 125, I'd typically get one or two blank images (but with the watermark).
John R. Ellis, Champion
...and it was exporting to disk, no Internet uploads.
It's happening on :
1) Windows 7 Pro Service Pack1 (Aurora R7 32Go, i7-3820, SSD HD)
2) Exporting as JPG
3) Only happening using watermark
4) Could happen on less than 50 images but the ratio is +-3 to 5 on 100
Problem is random. If I export 200 images, 2-3 are blank. If I re-export same photos with same export configuration, could be 2-3 others photos but the previous one are fine.
1) Windows 7 Pro Service Pack1 (Aurora R7 32Go, i7-3820, SSD HD)
2) Exporting as JPG
3) Only happening using watermark
4) Could happen on less than 50 images but the ratio is +-3 to 5 on 100
Problem is random. If I export 200 images, 2-3 are blank. If I re-export same photos with same export configuration, could be 2-3 others photos but the previous one are fine.
John R. Ellis, Champion
...and my exports were to local SSD.
I have Windows 8.1 and I tried to export more than 250 photos (few of them are white but the watermark is ok)
Steve Sprengel, Champion
For me the watermark needs to be graphical. I was using a 1012x789 JPG and see about a 1% white export rate.
My WM 's have not changed from old version to this some are png some are jpg
Win 7 x64
JPEG
Graphical watermark
Not sure if small number of exports exhibits problem since almost always exporting large number.
JPEG
Graphical watermark
Not sure if small number of exports exhibits problem since almost always exporting large number.
Yes, Windows 8, exporting to jpeg, using watermark (tried both omg and built in text watermark), exporting 100+ images. Export each individual image they are fine and the thumbnail shows the image.
For those of you who have this problem, are your originals photos files located on your PC or on a NAS / external hard drives?
My original files are stored on the internal hard disk.
This problem is occuring to me for a long time. Throughout that time I used.
LR4 on Win7
LR4 on Win8
LR6 on Win8
occur on JPGs (other formats I haven't tried)
only watermarker (with png watermark - includes transparent pixels)
50+ photos only cannot confirm even though I think it happend even with a single photo export
LR4 on Win7
LR4 on Win8
LR6 on Win8
occur on JPGs (other formats I haven't tried)
only watermarker (with png watermark - includes transparent pixels)
50+ photos only cannot confirm even though I think it happend even with a single photo export
Steve Sprengel, Champion
This bug has been acknowledged by Adobe, so there's no need to post about it, anymore.
sorry about that :) i have got to that post a bit later
You don't have to be sorry :
1) The bug is still not fixed... and we are 2 months later.
2) The more people post about this problem in this forum, the more chance it will be fixed by Adobe in 2015.
3) The more people post in this forum, the easier it can be found in Google search and it will help others people.
If we just keep it "silent" as M. Sprengel suggest, the bug will be classified as low priority and it will take months (wait it's been 2 months - it will takes years), to get it fixed.
BTW : A bug acknowledged is not a bug fixed. Anybody want to try skydiving with a bug in the parachute? :)
1) The bug is still not fixed... and we are 2 months later.
2) The more people post about this problem in this forum, the more chance it will be fixed by Adobe in 2015.
3) The more people post in this forum, the easier it can be found in Google search and it will help others people.
If we just keep it "silent" as M. Sprengel suggest, the bug will be classified as low priority and it will take months (wait it's been 2 months - it will takes years), to get it fixed.
BTW : A bug acknowledged is not a bug fixed. Anybody want to try skydiving with a bug in the parachute? :)
David Simmonds
Carlo
szabopal
Samantha Johnston