On cold startup, OBS settings and state of MIDI controllers do not match
Proposed solution
Add a checkbox named "Sync on startup" for each binding. When checked, plugin should go through the action and "trigger" it with the current value set in OBS or on the MIDI device (depending on the action type), thus synchronizing them with each other to a single "source of truth".
This should be available binding by binding, not globally, so if one has actions going both ways, it can be selected which way the syncing should happen (sometimes it is desired to have a "clean state" in the OBS, but for other bindings it may be desired for the MIDI device to update to OBS) and some other actions should not be synced at all.
Problem
On cold startup, OBS settings and state of MIDI controllers do not match
Proposed solution
Add a checkbox named "Sync on startup" for each binding. When checked, plugin should go through the action and "trigger" it with the current value set in OBS or on the MIDI device (depending on the action type), thus synchronizing them with each other to a single "source of truth".
This should be available binding by binding, not globally, so if one has actions going both ways, it can be selected which way the syncing should happen (sometimes it is desired to have a "clean state" in the OBS, but for other bindings it may be desired for the MIDI device to update to OBS) and some other actions should not be synced at all.