Original filenames not recognised when importing Project Indigo DNG+JPG directly from iPhone to LrC
Hello.
I’ve looked for similar issues about importing photos directly into LrC from iPhone via a USB cable, but none seem quite the same and none provide a resolution. Let me explain.
I’ve connected my iPhone 13 Pro (iOS 26.2.1) via USB to my MacBook Pro (16” 2019, Sonoma 14.7.6). My Project Indigo camera app on the iPhone generates both a DNG and JPEG of each shot. When I try to import the pair of files directly from the iPhone device using the LrC import dialog, the DNG and JPEG show different random filenames, as shown in the attached screenshot.
Normally, the Indigo app generates filenames in the standard format: IDG_YYYYMMDD_HHMMSS_NNN, with extensions DNG and JPG, respectively. If I try to import the Indigo photos into LR mobile on the iPhone, those normal names are recognised.
Leaving aside the first two HEIC files in the top row, the photos in the LrC import dialog appear as DNG+JPEG pairs, but they each have different random names instead of the standard format, e.g., JANW5609 and XQGC3512 in the top row.
The same problem is evident if I use the Image Capture app on the MacBook. If I look at them using the Photos app on the MacBook, the JPEG filename retains the normal IDG_YYYYMMDD_HHMMSS_NNN format, while the DNG shows the random alphanumeric format.
The first two in the top row are HEIC taken with the iPhone Camera app, and they retain the normal name format: IMG_XXXX.HEIC, as expected.
There are a few problems with this outcome:
- LrC will import both the DNG and JPEG as separate photos, even though I’ve set the LrC preferences NOT to treat the JPEG as a separate file.
- The random names makes it difficult to match the DNG/JPEG pairs, particularly when there is series of similar images.
- To get back to my usual workflow is messy. I’d have to rename both the DNG and JPEG to recover the normal filename format, remove them both from the Catalog, and then import them again. Then the JPEG would be treated effectively as a sidecar file.
Obviously this leads to an inefficient and messy process.
Has anyone experienced this issue and found a reasonable workaround or fix?
AdChoices