The trouble seems to occur when someone does a lot of image tinkering in Photoshop, and then exports the image for use elsewhere (like jAlbum). None of this image editing information is of any use in a slide image in an album, of course. I'm not a Photoshop user, but I'll wager there's a way to export images without all of that xmp baggage.
See item 7, include develop settings in metadata at
https://lightroomkillertips.com/lightroom-running-slowits-probably-one-7-reasons/
Edited by: jGromit on 16-Apr-2020 10:00 - it's item 7, not 6.
That tip applies to the original photos being managed in Lightroom and whether your develop instructions will be written into their XMP. Since Lightroom edits non-destructively and never modifies the actual image data to reflect the edits, the Lightroom originals are not what you are going to be publishing with jAlbum. For the purposes of jAlbum and publishing images in general, Lightroom gives you explicit control of metadata included during an export or publish operation. See this tip for details:
https://lightroomkillertips.com/controlling-metadata-export/. I find that choosing "All Except Camera RAW Info" preserves everything except for all the LR develop instructions which are the big guilty party in pushing my XMP data over the 64KB single-segment limit. This data is only useful for other image-processing applications and a lot of it is Adobe-specific anyway, so no loss to filter this out from images exported for publishing. FWIW, I've hit the 64KB XMP segment limit with other image processing apps other than jAlbum, in particular exiv2 which I use to script various metadata operations on my images.
