Ah, thanks for the detail.
My addon mainly works by:
- Reading stream info (source HDR, audio format, fps)
- Checking stream info against addon settings configured by user
- Applying audio offset accordingly using JSON-RPC method “Player.SetAudioDelay”.
I’m just curious on what the value of adding another latency value setting is? Is it adding complexity for little gain? I appreciate your work but I want to make sure that we aren’t adding complexity or double work since the addon can live fully on its own without needing direct integration.
I’m not a programmer by trade, so it’s entirely possible I’m missing the point of what you’re trying to do 
I think that what you did initially with adding resolution specific audio settings makes sense, because then that can be used as baseline to account for differences in output time per resolution, while still using the addon to control for the rest of the delay due to audio formats.