P: Random white images when exporting or publishing

Thanks for the updated preset, Steve.

OK - with Steve's export preset, watermark preset and graphic, I just did two exports of 240 JPEG files: One on Windows 7 and one on Windows 8.1. In both cases I got 240 JPEGS with no anomalous White - blank images.

Note: on the Win 7 machine there is no SSD drive and 12 CPU cores on the 8.1 there is only an SSD drive and 4 CPU cores.

So, the bad news is we still do not have a duplicatable failure.

Are any of you running any other applications which may have the folder to which you are exporting tied up temporarily - ie. Via Bridge, Dropbox, Creative Cloud, etc?

For the purposes of the test, I need your original preset- not a modified version. I am capable of restoring the link to the JPEG file in the preset. Can you provide me the actual preset?

Here is the original contents of my watermark preset w/o the change in graphic filename, where it is a little strange that their is both text and graphic specifications. I assume the text is the default "Simple Watermark" that I modified to have a graphic and saved as a new preset:

This is copy/pasted from Notepad:

s = {
id = "30E87C29-E66E-4D8D-A7E1-6030734D1913",
internalName = "yamd_test",
title = "yamd_test",
type = "WatermarkingPreset",
value = {
items = {
{
anchor = "bottomleft",
horizontalPadding = 0,
imagePath = "C:\\Users\\Steve\\Pictures\\2M\\you_are_my_dream_____by_shakuchan1995-d6m92rc.jpg",
kind = "image",
opacity = 1,
orientation = "AB",
sizeKind = "relative",
sizeRelativeAmount = 0.1,
text = "© Steve Sprengel",
textColorBlue = 1,
textColorGreen = 1,
textColorRed = 1,
textFontName = "Myriad Web Pro-Regular",
textHorizontalAlignment = "left",
textShadowAngle = 270,
textShadowEnabled = true,
textShadowOffset = 0.1,
textShadowOpacity = 0.8,
textShadowRadius = 0.2,
textVerticalAlignment = "top",
verticalPadding = 0,
},
},
},
version = 0,
}

Here is a version copy/pasted from WordPad, where a difference is the extra accented-A preceding the copyright symbol. I assume this is a difference between Notepad's UTF-8 and whatever Wordpad does with a copyright symbol in whatever character encoding it uses:

s = {
id = "30E87C29-E66E-4D8D-A7E1-6030734D1913",
internalName = "yamd_test",
title = "yamd_test",
type = "WatermarkingPreset",
value = {
items = {
{
anchor = "bottomleft",
horizontalPadding = 0,
imagePath = "C:\\Users\\Steve\\Pictures\\2M\\you_are_my_dream_____by_shakuchan1995-d6m92rc.jpg",
kind = "image",
opacity = 1,
orientation = "AB",
sizeKind = "relative",
sizeRelativeAmount = 0.1,
text = "© Steve Sprengel",
textColorBlue = 1,
textColorGreen = 1,
textColorRed = 1,
textFontName = "Myriad Web Pro-Regular",
textHorizontalAlignment = "left",
textShadowAngle = 270,
textShadowEnabled = true,
textShadowOffset = 0.1,
textShadowOpacity = 0.8,
textShadowRadius = 0.2,
textVerticalAlignment = "top",
verticalPadding = 0,
},
},
},
version = 0,
}

The picture I'm using is under my C:\Users\Steve\Pictures folder so it won't work as is on your computer, or if the problem is that I edited it with Notepad and resaved it with a different encoding. It is a simple preset. I just added a graphic and saved the preset so whatever else was the watermark defaults. Presumably you could make a preset on your computer and see if it looks the same as mine, other than the path to the photo, in a text editor. I didn't have any other watermark presets on my computer.

My original files are stored on the internal hard disk.

You lost me there totally 🙂

I agree with you John. I save my export to 3 SSD in RAID5 for speed and I have a good computer built for speed also. I will try to save the files to a NAS (the network connection is a lot slower that internal SSD) and see if it makes a difference.

This smells very much like a timing-dependent, concurrent-programming bug, and as such, it will be highly dependent on your hardware configuration and LR's policies for utilizing multiple processors. The speed of your processors, memory, and disk, as well as other programs running on your system, affects these sorts of bugs. It isn't at all surprising that Rikk (or anyone else) wouldn't be able to reproduce it.

As I reported earlier, I can only get it to happen when I enable all 8 CPUs on my Macbook Pro (4 cores/8 processors). With 1, 2, or 4 CPUs, it didn't happen (or if it does happen, it happens less frequently).

While I didn't see any mention in Adobe's announcements, Victoria Bamptom wrote of LR CC: "Export speed has been improved, and it makes better use of multiple cores so you don’t have to manually queue up multiple exports.". People on the forums have reported LR 6, unlike LR 5, utilizing all their processors during an export. It's likely that LR has implemented a policy for controlling concurrent use of processors during exports, and the details of this policy, which we don't know, surely confound testing even further.

You are right, it was also fine for me... 🙂