P: (Early Access) Content Authenticity Initiative (CAI) for (CR & LrClassic)

In the dialog description it says "seperate". "separate" would be more accurate.

I would like to see an option during export that only states whether AI has been used or not, instead of showing "edits" along that info. If building trust around AI usage is the goal, then I believe showing "edits" other than AI usage is not necessary, unless I would choose so.

This "Content Credentials" was a waste of development time & skill.... It would have been a better use of developpers time to team up & improve functionality of other "upgrades".

I'm just looking into this and I have questions:

1) If I attach to cloud and then post my jpg to a social media site, how does an individual looking at that check the image to see if it is really mine or what edits I made. I have had people challenge me that my image was AI and I can't see any simple way to verify that to them. Seems this would help if the user could check/verify.

2) If I decide I don't want to use this feature any longer, is there a way I can remove the information that I have already allowed up to the cloud?

3) Is there any sort of "certificate" that I can generate from this to give to individuals who purchase a print from me? I like to leave them with something that they can use to verify that it is indeed my image, or at least I registered it somewhere and didn't just steal it and resell it.

4)  I would like to be able to attach more than just X, Instagram, LinkedIn to photos.

5) I don't see any option in LrC to prevent AI scraping or the "I own this . . . " checkbox.

6) Will this evolve into a subscription or pay app? Meaning will it be free forever to upload as many content credetials as I want?

7) A possible problem in the chain of editing is that I often use 3rd party apps to Denoise. These generate a tiff image that when exported with credentials doesn't really tell anybody very much except my person contact information and linked media sites. Not sure much can be done about that, but it also means that almost any AI image can be exported as a tiff and then have credentials uploaded and there does not seem to be any way that can be detected or tracked.

😎 If I change location/address/email/phone, is there any way to update that on previous image data uploaded.

9) Is there a way to log into my account and see what I have there and modify/edit it?

Hope thats not too much to ask at once, but thats my immediate feedback.

Thanks,

~ tommy

Hello,
It's a great idea. But it is so long to export files.
Usually when I export 100photos 4K to jpg fullHD it just takes only a few seconds.
Now with content credential and only productor and account (not modifications) it takes maybe 10min. Crazy too long.
And it crashes usually on some files. I think it's because of undersized servers. Maybe.
So sadly I stopped using this option.

Lrc 14.0.1

Windows11pro, I7 14700k, 64goddr5, rtx4070tisuper

I'm working with another artists catalog, I manage several of them, and the only "Producer" option I am given is for me, I guess because I'm it's my licence I'm using. I would like to have the option to have this information match the metadata for the files not just the owner of the licence.

I've been trying to link with my Instagram account but consistently get "400 Session Invalid" error. I'm on Mac and here is the System info 

Lightroom Classic version: 14.0.1 [ 202410161356-30922cfc ]
License: Creative Cloud
Language setting: en-US
Operating system: Mac OS 15
Version: 15.0.1 [24A348]
Application architecture: arm64
Logical processor count: 8
Processor speed: NA
SqLite Version: 3.36.0
Power Source: Plugged In, 100%
Built-in memory: 16,384.0 MB
Dedicated GPU memory used by Lightroom: 185.1MB / 10,922.6MB (1%)
Real memory available to Lightroom: 16,384.0 MB
Real memory used by Lightroom: 553.1 MB (3.3%)
Virtual memory used by Lightroom: 405,701.9 MB
Memory cache size: 540.2MB
Internal Camera Raw version: 17.0 [ 2043 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2
Camera Raw virtual memory: 43MB / 8191MB (0%)
Camera Raw real memory: 45MB / 16384MB (0%)

Cache1:
NT- RAM:0.0MB, VRAM:0.0MB, Combined:0.0MB

Cache2:
m:540.2MB, n:0.0MB

U-main: 111.0MB

Standard Preview Size: 2940 pixels
Displays: 1) 2940x1912

Graphics Processor Info:
Metal: Apple M2
Init State: GPU for Export supported by default
User Preference: Auto
Enable HDR in Library: OFF

Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Volumes/T7 Shield/Photography/Catalogs/SpikeShotThis/SpikeShotThis.lrcat
Settings Folder: /Users/<USERNAME>/Library/Application Support/Adobe/Lightroom

Installed Plugins:
1) AdobeStock
2) Any Tag
3) Any Vision
4) Aperture/iPhoto Importer Plug-in
5) Flickr

Config.lua flags:

The new generative remove feature is nearly perfect, and such a welcomed update! However, adding credentials other than the METADATA that's already include in each file we export feels like giving permission to ADOBE to use our images (in any future capacity), under the guise of sharing our social media profiles. That is simply not enough to agree to these terms. I personally don't need ADOBE to help me promote my photography business. I'm also confident that I don't need ADOBE to promote my social media presence. While I continue to use ADOBE products to edit my photos, I too am starting to feel the overreach with each new feature necessitating a sign off.

How can I use different "Producer" Name depending on each of my brand name... ? Thank you !