Skip to main content
coustoulin
coustoulin
Inspiring
December 12, 2022
Question

P: Redundant copy of DNG and Tiff files when export from LRC to LR6

  • December 12, 2022
  • 4 replies
  • 4836 views

Hello, please help me : I want to post a bug report and I am not sure it is understood as a BUG .... I don(t just want to discuss about it, I want to report this as a bug !!!!!

please have a look on this https://community.adobe.com/t5/lightroom-ecosystem-cloud-based-discussions/redondant-copy-of-dng-and-tiff-files-when-export-from-lrc-to-lr6/m-p/13469292#M73874

 

and

https://community.adobe.com/t5/lightroom-classic-discussions/how-can-i-syncronize-original-file-in-t...

 

 

I want to import raw files into the cloud when I had already synchronized them from LRC.

My process is :

* export original file without changing any information with post process to LR6

* After export LR6 opens an import the picture

* but it create a copy of the image, without modifying the file of the original photo

RESULT : a double picture, and afterward, LRC detects this double and download the image.

This seams to be a bug

NOTA BENE : with a nef file (with the sidecar data) I don't have the problem.

 

I use a PC on win10 : here are the release info

This topic has been closed for replies.

4 replies

Rikk Flohr_Photography
Community Manager
Rikk Flohr_PhotographyCommunity Manager
January 6, 2023

@Jim Wilde  Do you have an opinion as to which desktop app is behaving wrongly? As I read through this it looks like Lightroom Desktop?

Rikk Flohr: Adobe Photography Org
Jim Wilde
Community Expert
Jim WildeCommunity Expert
Community Expert
January 6, 2023
quote

@Jim Wilde  Do you have an opinion as to which desktop app is behaving wrongly? As I read through this it looks like Lightroom Desktop?


By @Rikk Flohr: Photography

 

Rikk, initially I was going to say that LrD was the (only) culprit, but I just repeated the tests using both LrD and LrW....and LrW was even more problematic than LrD:

 

Using LrC I identified 10 images (4 x CR3 and 6 x DNG) which had been synced to the cloud, thus smart previews only in the cloud. I exported all 10 to a desktop folder as "original".

 

Using LrD I added 2 of the CR3s and 2 of the DNGs. Prior to the import I had 160 images in the cloud of my test account, after the import the count increased to 162 (the expectation is that it wouldn't increase at all). On review, the two additional files were a second copy of the 2 x DNGs. Reviewing LrC after the sync back, the two additional DNGs are new images, not VCs (VCs are what I would normally expect, but on examination the exported copies are a slightly different file size compared to the LrC originals, so that small difference is enough to ensure that LrC's duplicates detection fails to identify them as the duplicates that they are).

 

Using LrW I then added the remaining 3 x CR3 and 3 x DNG files, and this time the photo count increased from 162 to 168, i.e. ALL the new imports, including the CR3s, were seen as new files, not linked to the SPs at all. When sync-back to LrC finished, the 3 x CR3s had appeared as VCs of the original, as expected as the file-sizes matched the originals in LrC. The 3 x DNGs were again new copies, not VCs.

 

As an aside, I was wondering why exporting DNGs as original resulted in a slightly different file-size. Without doing a forensic inspection, I would guess that some of the keywords that are attached to the originals in LrC would have the "Include on Export" option unchecked, thus are not written into the XMP section of the exported copy. thus causing a small size difference.

 

If you need any further info, or tests running, let me know.

Jim Wilde
Community Expert
Jim WildeCommunity Expert
Community Expert
January 6, 2023

One other oddity using LrW. The "normal" workflow for exchanging Smart Previews in the cloud with the originals is to add the same LrC-cataloged image to Lightroom, which then detects that it's the original file and effects the swap as intended. I had assumed that adding an LrC-cataloged original to LrW would work the same way as LrD, but not so. LrW aborts the import, reporting that the image is a duplicate:

 

 

Jim Wilde
Community Expert
Jim WildeCommunity Expert
Community Expert
January 6, 2023

@Rikk Flohr: Inactive 

 

Rikk, as you will see from the original thread I have confirmed this behaviour with DNG and Tiff files (I would expect Jpeg and PSD to be the same). To be clear, the more "traditional" method in LrD of exchanging an existing synced SP from Classic with the full original (adding the actual original from the LrC cataloged location) does still work. This problem relates only to exporting the original from Classic using the "Original" file setting, then adding the exported copy of the original to LrD....in that case the new original is not recognised as the original of the existing SP, so is duplicated in the cloud and then back in LrC. There are some wrinkles around this, as the file length of the exported copy original may be slightly different to the cataloged original in LrC (possibly related to keywords export settings), but even identical file lengths are still causing the problem in LrD (but then results in a VC in LrC).

 

Although I didn't mention it in the original thread, I'm pretty sure that I tested this on both Mac and Windows systems.

coustoulin
coustoulinAuthor
Inspiring
December 26, 2022

Hello,

 

I want to import raw files into the cloud when I had already synchronized them from LRC.

My process is :

* export original file without changing any information with post process to LR6

* After export LR6 opens an import the picture

* but it create a copy of the image, without modifying the file of the original photo

RESULT : a double picture, and afterward, LRC detects this double and download the image.

This seams to be a bug

NOTA BENE : with a nef file (with the sidecar data) I don't have the problem.

 

I use a PC on win10 : here are the release info

regards

selondon
Community Expert
selondonCommunity Expert
Community Expert
January 5, 2023

If you had already synced the photo in a Collection from Lightroom Classic to the Cloud, then that would be a lower res Smart Preview.

To get the full res into the Cloud you can just drop or import the original into the (Cloud Based) Lightroom Desktop.

This will replace the Smart Preview in the Cloud whilst retaining any edits made.

 

Is this what you are trying to do?

coustoulin
coustoulinAuthor
Inspiring
January 6, 2023

Of course i triés ! But i am on a windows system and drag'n drop is not avalaible 

please tale a look on m'y (long) dialog here : https://community.adobe.com/t5/lightroom-classic-discussions/how-can-i-syncronize-original-file-in-the-cloud-from-lrc/m-p/13445620/page/2#M304442

 

coustoulin
coustoulinAuthor
Inspiring
December 12, 2022

Hello, I'm using LRC and I want to sync pictures with the native original file. But I have only "dynamic preview" and cannot edit with Photoshop.

Can anybody help me ?

Thank you

Arnaud (France)

J
Community Expert
Jao vdLCommunity Expert
Community Expert
December 24, 2022

It's unlikely to influence Adobe much but please add your vote to this feature request to enable syncing of full resolution raw files to the cloud from Classic: https://community.adobe.com/t5/lightroom-classic-ideas/p-should-be-able-to-sync-full-raw-files-to-the-cloud-not-just-smart-previews/idi-p/12248616 Has been a request since 2017!

    F. McLion
    Community Expert
    F. McLionCommunity Expert
    Community Expert
    December 26, 2022
    quote
    quote

    But nevertheless my problem with tiff and dng files seems to be a bug. Is it known ?

     

    No, it certainly isn't a known bug (if it was known, @john beardsworth wouldn't have suggested it). I've done some extensive testing over the last couple of days and I can confirm the problem that you are seeing....specifically that when adding photos to the Lightroom desktop app that are "exported as original" copies of images initially synced as Smart Previews from LrC, the "Add Photos" process in LrD recognises proprietary raw files as existing SPs and simply replaces the SP with the new original (that's expected behaviour) but sees DNG and Tiff files as NEW images which are added to the cloud library in addition to the corresponding SP. They are thus downloaded to the synced LrC catalog where they appear as a second copy of the originals (I haven't tested Jpeg, but that might well be the same).

     

    The problem here is that AFAIK this whole "replace the synced SPs in the cloud with originals by importing them again into one of the cloud apps" is possibly an unsupported "feature" of the original cloud implementation. As such, reporting it as a bug may go nowhere...I don't know for certain, I'm just speculating that Adobe may not want to devote development resources into fixing a "bug" in a feature that they don't officially support. They may well say that the workaround would be to locate and import to LrD the actual source images that are cataloged in LrC (i.e. do not try to use exported derivatives). That process does still work, though of course it means extra work if the target images are spread around different folders. 

     

    But as I said, that's just speculation on my part. I'd suggest you put in a formal bug report and see how Adobe respond to that.


    By @Jim Wilde

     

    Thanks, but how can I put a formal bug report ? I never did it !

     

    Merry Xmas !


    Start a thread here in the forum and select the "bugs" section:

     

    --- Got your issue resolved? Please label the response as 'Correct Answer' to help your fellow community members find a solution to similar problems. ---
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices