nvdweem/PCPanel

Support for control mode -60 to 12 in Voicemeeter advanced settings

Closed this issue · 5 comments

ethw commented

Voicemeeter provides gain faders from -60db to 12db. It is currently not possible to control this full range through PCPanel pro and this software as far as I can tell.

If you use the default control mode, -Inf to 12, then voicemeeter gets stuck at -60 when the pc panel fader is all the way at the bottom. Voicemeeter is interpreting that as -1000db or something like that, resulting in voicemeeter being unreactive to fader changes until voicemeter is restarted.

If we had the option to control voicemeeter between -60 and 12db then the -1000db issue wouldn't occur and the full volume range of voicemeeter would be controllable via pc panel pro.

Thanks for considering.

I don't understand what you mean exactly. I don't use VoiceMeeter myself, so could you explain in a bit more detail what you are seeing and what you expect to see?

java_MZv6eLp3mK
From what I can tell, the slider moves correctly between +12 and -inf. The only 'stange' behavior I'm noticing is that when restarting VoiceMeeter, changes made in the UI seem to be stored but changes from the PCPanel are not, but that isn't the issue you are seeing, right?

ethw commented

Sure, I'll explain more. Your screencap is definitely not my experience, here's what I'm getting. The -inf value doesn't seem to be valid for me. I don't see any settings to allow a slider to go down to -inf.

PCPanel_XaXIK9I0ir

The voicemeeter slider gets stuck at the bottom. It won't move again until I restart voicemeeter. Even if I manually click in voicemeeter to move the slider the gain doesn't change.

I'm using voicemeeter potato, maybe it's a version difference. I see that you're on the basic version of voicemeeter in your screencap.

The reddit thread I linked in my original post had someone with the same issue who found that their voicemeeter xml file was set to something like -1000 for the affected voicemeeter strip. My guess is in that -inf is somehow setting the value too low on my voicemeeter version. Seems really weird that it's working on basic voicemeeter and not potato though. Could definitely be bad config on my part.

I'm on voicemeeter potato version 3.1.1.1 and PCPanel v1.6. The issue is happening identically on every voicemeeter strip or bus that I assign the PC Panel fader to. Thanks for looking into my issue!

ethw commented

image

The Voicemeeter potato user manual says the value only goes between -60 and 12.

The basic voicemeeter manual says the same thing though, so odd that -inf might only work on one of them.

The code was actually setting a -inf instead of the -60. I checked locally (both vanilla and potato) and the behaviour in the UI seems to be unchanged for me with the exception that closing/opening VoiceMeeter vanilla keeps the gain set to -inf, so that looks promising.

Could you try the latest 1.7-snapshot build (155) to see if it fixes your issue?

The 1.7 snapshot should essentially be as stable as the 1.6, but if you want to move back to the 1.6 afterwards you can re-install that version and rename %userprofile%/.pcpanel/profiles.json.1_6.bak to just be profiles.json.

ethw commented

I just tried out 1.7 and yep the -60 to 12 setting has resolved my issue. I'll just stay on 1.7. Thank you very much for the help, much appreciated.

PCPanel_GGb7IbZls9