Okay lots of testing done, this is the best breakdown I can give - hope it helps.
Steps to reproduce:
1. Have 2 distinct audio inputs in OBS e.g. Spotify + Discord
2. Add the "Audio Monitor" plugin filter to each of these 2 inputs, named distinctly -- e.g SpotifyAudioMonitor, DiscordAudioMonitor
3. In MIDIControl, Add the keybind for a midi trigger (im using a slider for each keybind) - assign this to the first distinctly named input's filter (e.g "SpotifyAudioMonitor")
4. Confirm and save
5. In MIDIControl, Add the keybind for *the second* midi trigger - assign this to the *second* obs audio input (e.g "DiscordAudioMonitor")
6. Confirm and save
Expected:
Changing the 2 mapped sliders on my hardware midi controller send values from 0-100 accurately to their mapped counterpart as per MIDIControl plugin
Actual Behaviour:
Changing the slider mapped to "DiscordAudioMonitor" sends values from 0-100 correctly.
Changing the slider mapped to "SpotifyAudioMonitor" sends values from 0-10000 --- Incorrectly.
Example request from OBS logs:
[obs-websocket] Request >> '{
23:04:24.984: "request-type": "SetSourceFilterSettings",
23:04:24.984: "sourceName": "Spotify",
23:04:24.984: "filterName": "Spotify Audio Monitor",
23:04:24.984: "filterSettings": {
23:04:24.984: "volume": 7244.09473
23:04:24.984: },
Examples of the same request for "Discord" cap at 100 as expected.
Modifying the filterminmax.csv to have a smaller range e.g 0,10 corrects the values for Spotify but then makes it impossible to reach 100% on discord.