P: SDK: LrDevelopController broken in languages other than English, German, Swedish

J'utilise un Clavier Midi LaunchControl avec des touches programmées celui-ci fonctionnait très bien jusqu'à la nouvelle version LR CC, certaines vont encore mais pas les autres. Que pouvons

Thanks!

Logged a bug for the issue. We'll try to get it fixed soon.

Note that this bug will affect anyone using a hardware controller with LR.  Also see these two reports:

https://forums.adobe.com/thread/2398289
https://forums.adobe.com/thread/2398759 

The latter is from the same person behind the thread Rory Jaffe posted above.

The problem is caused by LrDevelopController.getValue() and setValue() not working properly on these parameter names in languages other than English, German, and Swedish:

Exposure, Contrast, Highlights, Shadows, Whites, Blacks, Clarity

Note that these are exactly the names that map to different develop settings based on the current process version of the photo. For example, the LrDevelopController parameter "Exposure" maps to the photo:getDevelopSettings() key "Exposure2012" for PV 4 and PV 3 (2012) but to "Exposure" for earlier process versions.

Most likely the lookup is now incorrectly doing language translation somewhere in that mapping process. (These keys are all supposed to be in English, as with all keys and parameters in the SDK.)

The workaround is to use "Exposure2012" when dealing with a PV 3 or 4 photo, and "Exposure" for earlier process versions.  That's undocumented but it works. (LrDevelopController seems to accept most of the same parameter names as photo:get/setDevelopSettings().)

Here's a debugger screenshot demonstrating this bug for "Exposure":

italian same problem. Ok english.

Bug for me too in French version, switching Lightroom to english language to get the plugin working fine

Great, I hope the bug can be fixed quickly. I am experiencing the same problems and I have a lot of customers emailing me that the plug-in does not work.
For now I am advising them to switch to using English.

Does Adobe do QA on these releases? One has to assume so, but for the life of me I don't think I've ever used any other s/w that is still so full of issues after so many versions

yes I confirm problemi.