antoine_hlmn's profile

1K Messages

 • 

16.9K Points

Mon, Aug 19, 2019 11:01 AM

Lightroom Classic: Export with previous fails when using using a user preset

Hi there,

Funny bug with the export function:
The function to Export with Previous does not work when the previous export was a User Preset. It's the previous previous setting that is then used.

Cheers!

Responses

990 Messages

 • 

14.9K Points

2 y ago

Same for me,

Version Lightroom Classic: 8.4 [ 201908011719-03751b60 ]
Licence: Creative Cloud
Paramètre de langue: fr
Système d'exploitation : Mac OS 10
Version : 10.14.6 [18G87]
Architecture de l'application : x64
Nombre de processeurs logiques: 6
Vitesse du processeur : 3.1 Ghz
Mémoire intégrée : 40 960.0 Mo
Mémoire réelle disponible pour Lightroom : 40 960.0 Mo
Mémoire réelle utilisée par Lightroom : 6 011.7 Mo (14.6%)
Mémoire virtuelle utilisée par Lightroom : 13 638.2 Mo
Taille de la mémoire cache : 710.8Mo
Version interne de Camera Raw: 11.4 [ 273 ]
Nombre maximal de liens utilisé par Camera Raw  : 4
Optimisation SIMD de Camera Raw : SSE2,AVX,AVX2
Mémoire virtuelle de Camera Raw: 1220Mo / 20479Mo (5%)
Mémoire réelle de Camera Raw: 1244Mo / 40960Mo (3%)
Affichages : 1) 5120x2880

Informations relatives au processeur graphique :
Metal: AMD Radeon Pro 575X

Path to presets...
Bibliothèque/Application Support/Adobe/Lightroom/Export Preset/Resizer multiple/Resizer bureau.lrtemplate


645 Messages

 • 

11.5K Points

2 y ago

Seems to be working as expected for me on Win10 / Lr Classic 8.4.
Antoine - are you Mac or PC?

Adobe Administrator

 • 

10.7K Messages

 • 

142.1K Points

2 y ago

I cannot reproduce on Mac 10.14.6 with Lightroom Classic 8.4.  If someone would like to write out step by step instructions so that we are certain we aren't missing anything, I would be happy to try again. 

Adobe Administrator

 • 

10.7K Messages

 • 

142.1K Points

1 y ago

Updates to Lightroom Classic, Camera Raw, and the Lightroom Ecosystem were released yesterday and contain a fix for this issue.  Please install the appropriate update and see if it solves this problem. You can read more about the updates here.

Thank you for your patience.