Lightroom: Problem exporting images when spot removal was used

  • 2
  • Problem
  • Updated 4 years ago
  • (Edited)
When exporting images on which I used the spot removal tool Lr shows error "The file seems to be unsupported or damaged" on SOME images (not on all).

Before I realized that the problem has something to do with the spot removal tool, I repeatedly exported the images. After some iterations the error disappeared on some of the images. And after countless export iterations I was able to export all of them.
Last week it took me one hour to export 20 images because I had to export them over and over again until all images where exported without any error.
I also tried different hard disks because I thought ther maybe a problem with my drive. Same problem!

After finding out that the erros is connected on the use of the spot removal tool I experimented with it to maybe find a pattern. I couldn't find one. Some images export with some spots, but setting another spot results in the export error. Sometimes I have to set one spot to get the error.
This is so annoying since it slows down my workflow dramatically.
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
  • frustrated and annoyed.

Posted 4 years ago

  • 2
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14147 Posts
  • 1765 Reply Likes
Can you post one of the files that you're having trouble with? (Use Creative Cloud, Dropbox, or similar service to share the URL to the file here)
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Any ideas?
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Yeah, I can do it, but I think it's independent from the file itself.

Here's what I did: I exported the file from my original raw file without using spot removal tool. Then I re-imported the jpg-file to Lr. After that I used the spot removal tool on both files (RAW and JPG) and none of them could be exported because according to Lr they seem to be unsupported or damaged. :(

When I delete the spot removals both files export without any problem.

Here's the link to the JPG file: https://dl.dropboxusercontent.com/u/8...
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14147 Posts
  • 1765 Reply Likes
Sorry. I could not reproduce. I imported your JPEG, added several spot removals and exported without error. (Lightroom 5.7.1, Mac 10.9.5)
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Same here - Lr5.7, Windows 7.
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
So, what can I do now? Maybe there's some kind of error logging process I can turn on and send you debug information.

As I said, I don't think it's a file error, because the same image might be exported after 10 or 20 tries (without any changes in between).
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14147 Posts
  • 1765 Reply Likes
So far, you're the only person reporting this that I know of. We need to figure out what's different between your system and mine (and the rest of our customers).

What OS are you on? Are you running any Anti-virus or other utilities?

If you run in SafeMode, do you have the same problem?
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
I'm on Windows 7 Professional, SP1. Antivirus-SW is Avast Antivirus. I didn't check it when running in Safe Mode. The problems started after an update to Lr 5.7, but when I changed it back to 5.5 or 5.6 the problems continued. So I switched back to 5.7. I really thought I can turn on some kind of error logfile to give your developers information on what's going on.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14147 Posts
  • 1765 Reply Likes
There are logs you can turn on but I'm not sure that would help in this case. I suspect the files are being modified/touched by the antivirus or something else.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14147 Posts
  • 1765 Reply Likes
I would try running in safe mode to see if the problem goes away.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14147 Posts
  • 1765 Reply Likes
Have you tried to restore your prefs to see if the problem goes away?
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
No. You think of resetting the Lr presets? Could you please be more specific?
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14147 Posts
  • 1765 Reply Likes
It was suggested by a colleague who's a Lightroom expert: http://blogs.adobe.com/lightroomjourn...
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Thanks, but unfortunately it didn't work. :(
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Hi Jeffrey,

working in Safe Mode also didn't help. The error comes up very randomly.

Here's the protocol what i did in Safe Mode and the results:

1. Start Lightroom
2. Export the JPG only WITH spot removals applied.
-> Works fine, NO error.
3. Export JPG and the RAW WITH spot removals applied.
-> No Export, BOTH with errors.
4. Export JPG and the RAW WITHOUT spot removals applied.
-> Works fine, NO error.

All of a sudden an exclamation mark appeared on the JPG in the film strip. Here's a screen shot of the error message:
https://www.dropbox.com/s/dt5qn181czc...

5. Restart Lr. The exclamation mark had disappeared.
6. Export JPG and the RAW WITH spot removals applied.
-> Error on the JPG, RAW was exported
7. Export JPG and the RAW WITH spot removals applied.
-> No Export, error on both
8. Export JPG and the RAW WITH spot removals applied.
-> Both were exported without any error
9. Export JPG and the RAW WITH spot removals applied.
-> No Export, error on both
10. Export JPG and the RAW WITH spot removals applied.
-> No Export, error on both
11. Export JPG and the RAW WITH spot removals applied.
-> Both were exported without any error
After that the exclamatoin mark appeared again on the JPG file.

So, what should I do now? Maybe it's time to switch on the error logging?
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Hi Jeffrey,

my problems do not stop here. I am currently working on wedding pictures. When exporting them I realized that the corrections made with the adjustment brush are ignored on some of the exported images.

Here's a screen shot from within lightroom, where I created harsh color casts with the adjustment brush (for demonstration purposes):
https://www.dropbox.com/s/nnixep6uqc0...

And here's the exported image. No adjustments at all:
https://www.dropbox.com/s/o03uqpeb0z6...

Maybe the two issues are linked?

This is really bad, especially if your clients are waiting to get their post-processed wedding pictures!
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3833 Posts
  • 725 Reply Likes
My recommendation, since a preference reset did not cure your problem is to reboot and then take an image or two to a blank new catalog and see if you can duplicate the issue.

If you can, I recommend an uninstall/reinstall of Lightroom from a fresh download coupled with a preference reset.

If you can't then we probably need to look harder at your catalog.
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Okay. I tried your first sugggestion: rebooted my system, created a new catalog, and imported the two images (one TIF and one JPG).
First I exported both without a problem. Then I applied 3 spot removals and tried to export them. They both reported an error.

Now I will ao a fresh install in a sandboxed system (within Sandboxie) from a freshly downloaded installation file. I'll keep you informed.
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
In the sandbox I cannot uninstall Lr. All I can do is a repair on my system. This didn't help.

Do you really think it helps to unistall/reinstall Lr?

I think it's a lot of hazzle to get everything working after that (e.g. plugins, my presets and so on), so I would prefer to try to find something unusual first. Don't get me wrong, but it seems to me that it's a natural reflex of IT people (I used to be one myself) to suggest the "reboot and reinstall' option.

Is there really no way to examine what's happening during the export process when the error happens?
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Oops, he-he, Jeffrey is on the Mac..

So, startup Lightroom thusly:

"C:\Program Files\Adobe\Adobe Photoshop Lightroom 5.7\lightroom.exe" -tracebacks

in a dos box (command shell).

then just run dbgview.exe, available here:

http://technet.microsoft.com/en-us/sy...

(written by Mark Russinovich)

Dunno how it finds Lr but somehow it does..

Warning - it shows *all* errors that occur, even the ones that, well, aren't really errors - buckle your seatbelt, cause it's a wild ride..

Rob
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
:) Thank you, Rob. Results below...
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3833 Posts
  • 724 Reply Likes
Yes, I do very strongly recommend a reinstall. Have you done this yet?
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Now I have unistalled Lightroom. After that I checked that all the folders in "C:\users\thomas\AppData\Roaming\Adobe\Lightroom\" haven't been deleted.
Do I have to delete them manually before reinstalling or just leave them where they are?
It doesn't seem to me that uninstalling LR will lead to a completely fresh installation. What should I do before the reinstallation?
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Unless Rikk has a better idea, I'd say just proceed with the installation. Lr un-install/re-installation won't touch user data files, but it will re-install all Lightroom program files and non-user program data files.
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Okay, now I followed Rob's advice. I used DebugView and started Lr with the -tracebacks option.
Then I cleared the display and exported the two images with the spot removals. Here's the logging when both images lead to an error:
----------------------------------- start --------------------------------------
[\\THOMAS-PC]
00000001 0.00000000 [11980] L:
00000002 0.00002717 [11980] AgNegative:renderToFile: dng_error_bad_format
00000003 0.00002717 [11980] 0: global error - C
00000004 0.00002717 [11980] 1: [unnamed] - 1250880549:121+7
00000005 0.00002717 [11980] 2: method renderToFile - C
00000006 0.00002717 [11980] 3: [unnamed] - 2040030245:2456+93
00000007 0.00002717 [11980] 4: global pcall - C
00000008 0.00002717 [11980] 5: [unnamed] - 2040030245:2325+5
00000009 0.00002717 [11980] 6: [unnamed] - tail
00000010 0.00002717 [11980] 7: [unnamed] - tail
00000011 0.00002717 [11980] 8: global pcall - C
00000012 0.00002717 [11980] 9: upvalue ? - 1493984430:152+24
00000013 0.00002717 [11980] 10: [unnamed] - 1493984430:179+2
00000014 0.00002717 [11980] 11: [unnamed] - C
00000015 0.00002717 [11980] 12: global AgCallWithAutoreleasePool - C
00000016 0.00002717 [11980] 13: field start - 1493984430:8+39
00000017 0.00002717 [11980] 14: [unnamed] - 331190879:0+7
00000018 0.00002717 [11980] ---------------------------------
00000019 0.00040207 [11980]
00000020 0.00079418 [11980] L:
00000021 0.00081290 [11980] AgNegative:renderToFile: dng_error_bad_format
00000022 0.00081290 [11980] 0: global pcall2call - C
00000023 0.00081290 [11980] 1: [unnamed] - 2040030245:2316+7
00000024 0.00081290 [11980] 2: [unnamed] - tail
00000025 0.00081290 [11980] 3: [unnamed] - tail
00000026 0.00081290 [11980] 4: [unnamed] - tail
00000027 0.00081290 [11980] 5: global pcall - C
00000028 0.00081290 [11980] 6: upvalue ? - 1493984430:152+24
00000029 0.00081290 [11980] 7: [unnamed] - 1493984430:179+2
00000030 0.00081290 [11980] 8: [unnamed] - C
00000031 0.00081290 [11980] 9: global AgCallWithAutoreleasePool - C
00000032 0.00081290 [11980] 10: field start - 1493984430:8+39
00000033 0.00081290 [11980] 11: [unnamed] - 331190879:0+7
00000034 0.00081290 [11980] ---------------------------------
00000035 0.00083524 [11980]
00000036 0.20234440 [11980] L:
00000037 0.20238273 [11980] AgNegative:renderToFile: dng_error_bad_format
00000038 0.20238273 [11980] 0: global error - C
00000039 0.20238273 [11980] 1: [unnamed] - 1250880549:121+7
00000040 0.20238273 [11980] 2: method renderToFile - C
00000041 0.20238273 [11980] 3: [unnamed] - 2040030245:2456+93
00000042 0.20238273 [11980] 4: global pcall - C
00000043 0.20238273 [11980] 5: [unnamed] - 2040030245:2325+5
00000044 0.20238273 [11980] 6: [unnamed] - tail
00000045 0.20238273 [11980] 7: [unnamed] - tail
00000046 0.20238273 [11980] 8: global pcall - C
00000047 0.20238273 [11980] 9: upvalue ? - 1493984430:152+24
00000048 0.20238273 [11980] 10: [unnamed] - 1493984430:179+2
00000049 0.20238273 [11980] 11: [unnamed] - C
00000050 0.20238273 [11980] 12: global AgCallWithAutoreleasePool - C
00000051 0.20238273 [11980] 13: field start - 1493984430:8+39
00000052 0.20238273 [11980] 14: [unnamed] - 331190879:0+7
00000053 0.20238273 [11980] ---------------------------------
00000054 0.20240688 [11980]
00000055 0.21116857 [11980] L:
00000056 0.21119756 [11980] AgNegative:renderToFile: dng_error_bad_format
00000057 0.21119756 [11980] 0: global pcall2call - C
00000058 0.21119756 [11980] 1: [unnamed] - 2040030245:2316+7
00000059 0.21119756 [11980] 2: [unnamed] - tail
00000060 0.21119756 [11980] 3: [unnamed] - tail
00000061 0.21119756 [11980] 4: [unnamed] - tail
00000062 0.21119756 [11980] 5: global pcall - C
00000063 0.21119756 [11980] 6: upvalue ? - 1493984430:152+24
00000064 0.21119756 [11980] 7: [unnamed] - 1493984430:179+2
00000065 0.21119756 [11980] 8: [unnamed] - C
00000066 0.21119756 [11980] 9: global AgCallWithAutoreleasePool - C
00000067 0.21119756 [11980] 10: field start - 1493984430:8+39
00000068 0.21119756 [11980] 11: [unnamed] - 331190879:0+7
00000069 0.21119756 [11980] ---------------------------------
00000070 0.21123014 [11980]
00000071 1.21492612 [11980] L:
00000072 1.21497285 [11980] bad argument #1 to 'floor' (number expected, got nil)
00000073 1.21497285 [11980] 0: field floor - C
00000074 1.21497285 [11980] 1: upvalue ? - 685877130:651+37
00000075 1.21497285 [11980] 2: field drawAppIdentityPlate - 685877130:757+69
00000076 1.21497285 [11980] 3: [unnamed] - 32668683:367+99
00000077 1.21497285 [11980] 4: upvalue ? - C
00000078 1.21497285 [11980] 5: [unnamed] - 1184969544:29+7
00000079 1.21497285 [11980] ---------------------------------
00000080 1.21502054 [11980]

----------------------------------- end --------------------------------------
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
And here the TIFF-file was exported and the JPG-file resulted in an error.
----------------------------------- start --------------------------------------
00000001 0.00000000 [10180] L:
00000002 0.00005464 [10180] [string "unarchived table s"]:1: unexpected symbol near 'ï'
00000003 0.00005464 [10180] 0: global loadstring - C
00000004 0.00005464 [10180] 1: [unnamed] - 214868927:1005+8
00000005 0.00005464 [10180] 2: global pcall - C
00000006 0.00005464 [10180] 3: method makeFileIntoItem - 375650273:1180+42
00000007 0.00005464 [10180] 4: upvalue ? - 375650273:2579+123
00000008 0.00005464 [10180] 5: [unnamed] - 375650273:2763+98
00000009 0.00005464 [10180] 6: method scanTemplateDirectories - 375650273:2409+128
00000010 0.00005464 [10180] 7: upvalue ? - 375650273:3245+60
00000011 0.00005464 [10180] 8: field makeFileDataModel - 378055297:848+31
00000012 0.00005464 [10180] 9: field dataModel - 1686036424:75+27
00000013 0.00005464 [10180] 10: upvalue ? - 1943774586:122+9
00000014 0.00005464 [10180] 11: [unnamed] - 378055297:848+31
00000015 0.00005464 [10180] 12: [unnamed] - tail
00000016 0.00005464 [10180] 13: field make - 746917091:29+14
00000017 0.00005464 [10180] 14: upvalue ? - 1923840628:410+141
00000018 0.00005464 [10180] 15: upvalue ? - 1923840628:734+165
00000019 0.00005464 [10180] 16: upvalue ? - 1923840628:901+106
00000020 0.00005464 [10180] 17: [unnamed] - 1923840628:1876+32
00000021 0.00005464 [10180] 18: [unnamed] - C
00000022 0.00005464 [10180] 19: field pcallWithContext - 1289965755:181+32
00000023 0.00005464 [10180] 20: field exportPhotosViaDialog - 1923840628:1844+31
00000024 0.00005464 [10180] 21: [unnamed] - 1273880053:818+34
00000025 0.00005464 [10180] 22: [unnamed] - tail
00000026 0.00005464 [10180] 23: upvalue ? - 1275222353:218+51
00000027 0.00005464 [10180] 24: [unnamed] - 1275222353:298+5
00000028 0.00005464 [10180] 25: field popUpContextMenu - C
00000029 0.00005464 [10180] 26: field _code - 882982057:3112+8
00000030 0.00005464 [10180] 27: upvalue ? - 179812414:1495+9
00000031 0.00005464 [10180] 28: [unnamed] - 179812414:1524+12
00000032 0.00005464 [10180] ---------------------------------
00000033 0.00013674 [10180]
00000034 0.00063994 [10180] L:
00000035 0.00068642 [10180] [string "unarchived table s"]:1: unexpected symbol near 'ï'
00000036 0.00068642 [10180] 0: global loadstring - C
00000037 0.00068642 [10180] 1: [unnamed] - 214868927:1005+8
00000038 0.00068642 [10180] 2: global pcall - C
00000039 0.00068642 [10180] 3: method makeFileIntoItem - 375650273:1180+42
00000040 0.00068642 [10180] 4: upvalue ? - 375650273:2579+123
00000041 0.00068642 [10180] 5: [unnamed] - 375650273:2763+98
00000042 0.00068642 [10180] 6: method scanTemplateDirectories - 375650273:2409+128
00000043 0.00068642 [10180] 7: upvalue ? - 375650273:3245+60
00000044 0.00068642 [10180] 8: field makeFileDataModel - 378055297:848+31
00000045 0.00068642 [10180] 9: field dataModel - 1686036424:75+27
00000046 0.00068642 [10180] 10: upvalue ? - 1943774586:122+9
00000047 0.00068642 [10180] 11: [unnamed] - 378055297:848+31
00000048 0.00068642 [10180] 12: [unnamed] - tail
00000049 0.00068642 [10180] 13: field make - 746917091:29+14
00000050 0.00068642 [10180] 14: upvalue ? - 1923840628:410+141
00000051 0.00068642 [10180] 15: upvalue ? - 1923840628:734+165
00000052 0.00068642 [10180] 16: upvalue ? - 1923840628:901+106
00000053 0.00068642 [10180] 17: [unnamed] - 1923840628:1876+32
00000054 0.00068642 [10180] 18: [unnamed] - C
00000055 0.00068642 [10180] 19: field pcallWithContext - 1289965755:181+32
00000056 0.00068642 [10180] 20: field exportPhotosViaDialog - 1923840628:1844+31
00000057 0.00068642 [10180] 21: [unnamed] - 1273880053:818+34
00000058 0.00068642 [10180] 22: [unnamed] - tail
00000059 0.00068642 [10180] 23: upvalue ? - 1275222353:218+51
00000060 0.00068642 [10180] 24: [unnamed] - 1275222353:298+5
00000061 0.00068642 [10180] 25: field popUpContextMenu - C
00000062 0.00068642 [10180] 26: field _code - 882982057:3112+8
00000063 0.00068642 [10180] 27: upvalue ? - 179812414:1495+9
00000064 0.00068642 [10180] 28: [unnamed] - 179812414:1524+12
00000065 0.00068642 [10180] ---------------------------------
00000066 0.00077245 [10180]
00000067 0.00131398 [10180] L:
00000068 0.00137345 [10180] [string "unarchived table s"]:1: unexpected symbol near 'ï'
00000069 0.00137345 [10180] 0: global loadstring - C
00000070 0.00137345 [10180] 1: [unnamed] - 214868927:1005+8
00000071 0.00137345 [10180] 2: global pcall - C
00000072 0.00137345 [10180] 3: method makeFileIntoItem - 375650273:1180+42
00000073 0.00137345 [10180] 4: upvalue ? - 375650273:2579+123
00000074 0.00137345 [10180] 5: [unnamed] - 375650273:2763+98
00000075 0.00137345 [10180] 6: method scanTemplateDirectories - 375650273:2409+128
00000076 0.00137345 [10180] 7: upvalue ? - 375650273:3245+60
00000077 0.00137345 [10180] 8: field makeFileDataModel - 378055297:848+31
00000078 0.00137345 [10180] 9: field dataModel - 1686036424:75+27
00000079 0.00137345 [10180] 10: upvalue ? - 1943774586:122+9
00000080 0.00137345 [10180] 11: [unnamed] - 378055297:848+31
00000081 0.00137345 [10180] 12: [unnamed] - tail
00000082 0.00137345 [10180] 13: field make - 746917091:29+14
00000083 0.00137345 [10180] 14: upvalue ? - 1923840628:410+141
00000084 0.00137345 [10180] 15: upvalue ? - 1923840628:734+165
00000085 0.00137345 [10180] 16: upvalue ? - 1923840628:901+106
00000086 0.00137345 [10180] 17: [unnamed] - 1923840628:1876+32
00000087 0.00137345 [10180] 18: [unnamed] - C
00000088 0.00137345 [10180] 19: field pcallWithContext - 1289965755:181+32
00000089 0.00137345 [10180] 20: field exportPhotosViaDialog - 1923840628:1844+31
00000090 0.00137345 [10180] 21: [unnamed] - 1273880053:818+34
00000091 0.00137345 [10180] 22: [unnamed] - tail
00000092 0.00137345 [10180] 23: upvalue ? - 1275222353:218+51
00000093 0.00137345 [10180] 24: [unnamed] - 1275222353:298+5
00000094 0.00137345 [10180] 25: field popUpContextMenu - C
00000095 0.00137345 [10180] 26: field _code - 882982057:3112+8
00000096 0.00137345 [10180] 27: upvalue ? - 179812414:1495+9
00000097 0.00137345 [10180] 28: [unnamed] - 179812414:1524+12
00000098 0.00137345 [10180] ---------------------------------
00000099 0.00144801 [10180]
00000100 0.00190683 [10180] L:
00000101 0.00192011 [10180] [string "unarchived table s"]:1: unexpected symbol near 'ï'
00000102 0.00192011 [10180] 0: global loadstring - C
00000103 0.00192011 [10180] 1: [unnamed] - 214868927:1005+8
00000104 0.00192011 [10180] 2: global pcall - C
00000105 0.00192011 [10180] 3: method makeFileIntoItem - 375650273:1180+42
00000106 0.00192011 [10180] 4: upvalue ? - 375650273:2579+123
00000107 0.00192011 [10180] 5: [unnamed] - 375650273:2763+98
00000108 0.00192011 [10180] 6: method scanTemplateDirectories - 375650273:2409+128
00000109 0.00192011 [10180] 7: upvalue ? - 375650273:3245+60
00000110 0.00192011 [10180] 8: field makeFileDataModel - 378055297:848+31
00000111 0.00192011 [10180] 9: field dataModel - 1686036424:75+27
00000112 0.00192011 [10180] 10: upvalue ? - 1943774586:122+9
00000113 0.00192011 [10180] 11: [unnamed] - 378055297:848+31
00000114 0.00192011 [10180] 12: [unnamed] - tail
00000115 0.00192011 [10180] 13: field make - 746917091:29+14
00000116 0.00192011 [10180] 14: upvalue ? - 1923840628:410+141
00000117 0.00192011 [10180] 15: upvalue ? - 1923840628:734+165
00000118 0.00192011 [10180] 16: upvalue ? - 1923840628:901+106
00000119 0.00192011 [10180] 17: [unnamed] - 1923840628:1876+32
00000120 0.00192011 [10180] 18: [unnamed] - C
00000121 0.00192011 [10180] 19: field pcallWithContext - 1289965755:181+32
00000122 0.00192011 [10180] 20: field exportPhotosViaDialog - 1923840628:1844+31
00000123 0.00192011 [10180] 21: [unnamed] - 1273880053:818+34
00000124 0.00192011 [10180] 22: [unnamed] - tail
00000125 0.00192011 [10180] 23: upvalue ? - 1275222353:218+51
00000126 0.00192011 [10180] 24: [unnamed] - 1275222353:298+5
00000127 0.00192011 [10180] 25: field popUpContextMenu - C
00000128 0.00192011 [10180] 26: field _code - 882982057:3112+8
00000129 0.00192011 [10180] 27: upvalue ? - 179812414:1495+9
00000130 0.00192011 [10180] 28: [unnamed] - 179812414:1524+12
00000131 0.00192011 [10180] ---------------------------------
00000132 0.00197625 [10180]
00000133 5.19294500 [10180] L:
00000134 5.19295502 [10180] AgNegative:renderToFile: dng_error_bad_format
00000135 5.19295502 [10180] 0: global error - C
00000136 5.19295502 [10180] 1: [unnamed] - 1250880549:121+7
00000137 5.19295502 [10180] 2: method renderToFile - C
00000138 5.19295502 [10180] 3: [unnamed] - 2040030245:2456+93
00000139 5.19295502 [10180] 4: global pcall - C
00000140 5.19295502 [10180] 5: [unnamed] - 2040030245:2325+5
00000141 5.19295502 [10180] 6: [unnamed] - tail
00000142 5.19295502 [10180] 7: [unnamed] - tail
00000143 5.19295502 [10180] 8: global pcall - C
00000144 5.19295502 [10180] 9: upvalue ? - 1493984430:152+24
00000145 5.19295502 [10180] 10: [unnamed] - 1493984430:179+2
00000146 5.19295502 [10180] 11: [unnamed] - C
00000147 5.19295502 [10180] 12: global AgCallWithAutoreleasePool - C
00000148 5.19295502 [10180] 13: field start - 1493984430:8+39
00000149 5.19295502 [10180] 14: [unnamed] - 331190879:0+7
00000150 5.19295502 [10180] ---------------------------------
00000151 5.19298410 [10180]
00000152 5.19355059 [10180] L:
00000153 5.19356251 [10180] AgNegative:renderToFile: dng_error_bad_format
00000154 5.19356251 [10180] 0: global pcall2call - C
00000155 5.19356251 [10180] 1: [unnamed] - 2040030245:2316+7
00000156 5.19356251 [10180] 2: [unnamed] - tail
00000157 5.19356251 [10180] 3: [unnamed] - tail
00000158 5.19356251 [10180] 4: [unnamed] - tail
00000159 5.19356251 [10180] 5: global pcall - C
00000160 5.19356251 [10180] 6: upvalue ? - 1493984430:152+24
00000161 5.19356251 [10180] 7: [unnamed] - 1493984430:179+2
00000162 5.19356251 [10180] 8: [unnamed] - C
00000163 5.19356251 [10180] 9: global AgCallWithAutoreleasePool - C
00000164 5.19356251 [10180] 10: field start - 1493984430:8+39
00000165 5.19356251 [10180] 11: [unnamed] - 331190879:0+7
00000166 5.19356251 [10180] ---------------------------------
00000167 5.19358063 [10180]

----------------------------------- end --------------------------------------
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Well, I can't understand most of that, but I do recognize the error:

dng_error_bad_format

which means Lightroom didn't like the format of the photo source file, or perhaps I should say: had a problem whilst reading the file.

If the file is not wonked, then you got some kinda strange system problem. Unfortunately, I don't have a clue what exactly - maybe somebody from Adobe (or another Lr techno-guru user) can shed more light.

Rob
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
It's not a problem with the file. But the error you mentioned is in both logs. I thought it is probably the error only reported in the first log:
00000072 1.21497285 [11980] bad argument #1 to 'floor' (number expected, got nil)
00000073 1.21497285 [11980] 0: field floor - C
00000074 1.21497285 [11980] 1: upvalue ? - 685877130:651+37
00000075 1.21497285 [11980] 2: field drawAppIdentityPlate - 685877130:757+69
00000076 1.21497285 [11980] 3: [unnamed] - 32668683:367+99
00000077 1.21497285 [11980] 4: upvalue ? - C
00000078 1.21497285 [11980] 5: [unnamed] - 1184969544:29+7
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Maybe app-identity-plate is a clue - is that a watermark? (I'm getting a ways out on the limb now..).
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Nope. No personalized identity plate, just the standard "Lightroom mobile".
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
It seems to by "argument #1", so I would suppose that means (depending on the counting method) "field floor" or "upvalue". But that's just an assumption.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
I downloaded your image file and added spots - exported no problem.

Maybe your export settings will provide a clue - can you post those? (preferrably by saving as preset and post text or link to file).

Also, maybe it's the spots themselves - can you save xmp in the file or post a 1-photo catalog for testing?
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Hi Rob,

thanks a lot for your effort. I don't think it's the export settings since I tried several - all with random errors.

My test catalog contains 2 files. Here's the dropbox link to the catalog:
https://www.dropbox.com/s/a5e12khtixc...
aAnd here's the jpg file:
https://www.dropbox.com/s/8cardy64of2...

I don't think you need the TIFF file since it's larger than 1 GB...
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Thanks poeth.one.

I don't know if this is good news or bad news, but I was able to export your jpeg with spots from your catalog and it worked just fine.

If not export settings, I can only guess there is something about your system/Lr-setup that is amiss. If you've already tried "deleting" (temporarily renaming) all critical Lr data files (presets/preferences..), then it might be time to try that program re-installation (after re-downloading).

I assume your OS is up to date. If not..

Not sure what else to say..

Good luck,
Rob
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Thanks a lot, Rob. I really appreciate your information and advices.

I downloaded a the Lr installation file, deleteted the preferences file and re-installed Lr. Unfortunately it didn't help. The problems with exporting images keep coming. :(

Now I really would love the Adobe experts to come up with some ideas how to trace the error source. Is this the official site to contact Adobe or is there another way?
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3833 Posts
  • 724 Reply Likes
This is the official site.

If you've uninstalled, then reinstalled, then reset preferences and are still having the same issue then I would like to run a test on my end with your catalog.

Create an empty catalog. Import one image. Perform the Spot Removals and make they very obvious. Verify that it will not export with the corrections.

Go to File>Export as a Catalog... and make a catalog with the original Raw file included. Zip it. Put it in a Dropbox folder or similar and send me a link.
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Hi Rikk,

good to know that this is the official site. Here's the zip-file: https://www.dropbox.com/s/zu884pepls0...

Thanks!
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3833 Posts
  • 724 Reply Likes
Works fine here. Picture exports with spot removals intact. Can anyone else confirm with the above Dropbox file?
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
I already confirmed (no problem for me) with the previously posted catalog (known to be problematic for poeth.one).
Photo of Petr Šulíček

Petr Šulíček

  • 4 Posts
  • 0 Reply Likes
Hello everyone,

I am suffering with very same problem as Poeth does. When I use spot removal function in Lighroom, there is unsupported or damage error randomly during export.

I also try Poetrh's dropbox files, and when I am trying export JPG with removal spots from catalog, there is unsupoorted or damage error.

I am using Lightroom 5.7 from my creative cloud.

My HW specs:

Lenovo ThinkPad x220
Win 7 Pro, 64 bit,
intel i5-2520M
Graphic: Intel HD3000
8GB RAM

Thanks for your help!
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Hi Petr,

I'm sorry to hear that, but on the other side I'm glad to hear that I'm not the only person.
Do you also encounter those errors since the update to Lr 5.7?
And do you also have the other problem I encountered of Lr ignoring the adjustment brush?

I hope that Adobe can help us.

Best regards
Thomas
Photo of Petr Šulíček

Petr Šulíček

  • 4 Posts
  • 0 Reply Likes
Hello Thomas,

Frankly, I am not sure about issue before 5.7. But first time I notice damage error was 2-3 months ago. At very first, I assumed that the problem is with my source NEF files, but then I notice that the error depends only on spot removal usage.

Also sometimes I notice that Lr ignore my gradient filter.

Best regards

Petr
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Hi Petr,

yeah, sounds familiar. I made the upgrade in november. I dont't use the gradient tool very often, but I think it's the same error source. :(

Best regards
Thomas
Photo of Petr Šulíček

Petr Šulíček

  • 4 Posts
  • 0 Reply Likes
Here is the screenshot.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Sounds like Lightroom has a system-dependent bug in it. Hopefully Adobe will take notice.
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
That's what I hope, too, but it doesn't look like it. :(
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Hello Jeffrey, hello Rikk,

any new ideas on this topic?

Best regards
Thomas
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3833 Posts
  • 724 Reply Likes
Thomas, unfortunately, I cannot reproduce it on my end with your files. That usually means it is the 'ugly' system-specific issue as Rob has point out previously.

If you are willing to under take the time to record a screen capture video of you applying the spot correction, exporting the file and then showing the final file, I would be happy to take another look and see if we are missing a step on our end. (or yours).
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14147 Posts
  • 1765 Reply Likes
Or, potentially create a separate partition and do a clean OS install and clean LR install.
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
I don't think that you miss something in trying to reproduce my error. I don't do anything special.
I am setting a spot and afterwards export the image. The error is NOT dependant of the actual image since after enough tries (sometimes 5, other times 50) the very same image will export without an error (although I didn't change anything). So I dont' think it will help to make this screencast.

And as I (and Petr) said, the error is likely introduced with the upgrade to Lr 5.7.

I do believe that on a clean installation everything will work, but this is NOT what I expected as help from Adobe experts.
A clean installation on a new partition will NOT save my problem because that cannot be a permanent solution. Since my primary drive is a 256 GB SD Raid, there's not enough disk space left for a second installation. For performance reasons the only option for my working system is a system installation on this SD drive. So the only option would be a complete fresh installation of my complete system,

Before I do this I would really appreciate seeing you Adobe guys trying to track down that error. There must be a way to provide you guys with some error logging/debug messages, that will help the developers find out what's going on.

And on top of this: if I do a fresh install and everything woks, how can I be sure that the next upgrade of Lr will not lead to the same error again?
Photo of Thomas Pöhler

Thomas Pöhler

  • 33 Posts
  • 0 Reply Likes
Another idea: maybe you can use teamviewer to test the bug for yourself on my system?