Environment
- MIDI2LR: 6.3.0.1
- Lightroom Classic: 15.3
- macOS (latest version)
- MIDI Controller: Stream Deck using the “MIDI Button” plugin
- MIDI connection via virtual MIDI port (IAC Driver)
Issue Description
When triggering a White Balance preset such as Cloudy via MIDI2LR, Lightroom initially sets the white balance correctly, but after approximately 1–2 seconds it automatically changes from Cloudy to Custom with slightly modified temperature values.
Example:
- Cloudy is applied
- Temperature is initially set to 6500 K
- After approximately 1–2 seconds Lightroom switches to:
- White Balance: Custom
- Temperature: 6477 K
The change happens consistently and is reproducible.
Expected Behavior
The selected White Balance preset (e.g. Cloudy) should remain active and unchanged, exactly as when selected directly in Lightroom.
Actual Behavior
The preset is applied initially, but Lightroom subsequently changes the White Balance to Custom and slightly modifies the temperature value.
Troubleshooting Performed
- Verified MIDI transmission using MIDI Monitor.
- Only a single MIDI Note On event is sent.
- No additional MIDI messages are received after the button press.
- Reset MIDI2LR settings.
- Removed all unnecessary mappings and tested with a minimal configuration.
- Verified that no duplicate mappings exist.
- Checked for old Loupedeck software, services, and background processes.
- No active Loupedeck services found.
- Tested using a Lightroom Develop Preset that only sets:
Important Finding
Applying the same White Balance via a Lightroom Develop Preset works correctly and remains stable.
Only the dedicated MIDI2LR White Balance action (e.g. “Cloudy”) causes the White Balance to change to Custom after a short delay.
This suggests that the issue may be related to the implementation of White Balance preset commands in MIDI2LR or their interaction with Lightroom Classic 15.3.
Reproduction Steps
- Map a MIDI note to “White Balance → Cloudy” in MIDI2LR.
- Open a RAW file in Lightroom Classic 15.3.
- Trigger the mapped MIDI note.
- Observe:
- White Balance initially changes to Cloudy.
- Temperature is set to 6500 K.
- After approximately 1–2 seconds White Balance changes to Custom and temperature changes to 6477 K.
Additional Notes
The issue does not occur when:
- Selecting Cloudy directly in Lightroom.
- Applying a Lightroom Develop Preset that only contains White Balance = Cloudy.
Therefore the issue appears specific to the MIDI2LR White Balance command implementation.
Environment
Issue Description
When triggering a White Balance preset such as Cloudy via MIDI2LR, Lightroom initially sets the white balance correctly, but after approximately 1–2 seconds it automatically changes from Cloudy to Custom with slightly modified temperature values.
Example:
The change happens consistently and is reproducible.
Expected Behavior
The selected White Balance preset (e.g. Cloudy) should remain active and unchanged, exactly as when selected directly in Lightroom.
Actual Behavior
The preset is applied initially, but Lightroom subsequently changes the White Balance to Custom and slightly modifies the temperature value.
Troubleshooting Performed
Important Finding
Applying the same White Balance via a Lightroom Develop Preset works correctly and remains stable.
Only the dedicated MIDI2LR White Balance action (e.g. “Cloudy”) causes the White Balance to change to Custom after a short delay.
This suggests that the issue may be related to the implementation of White Balance preset commands in MIDI2LR or their interaction with Lightroom Classic 15.3.
Reproduction Steps
Additional Notes
The issue does not occur when:
Therefore the issue appears specific to the MIDI2LR White Balance command implementation.