You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love BetterVolume, it's of massive help to me when dealing with friends with really quiet mics. Unfortunately, given the nature of BD, whenever Discord updates I have to repair/reinstall it. While most of the plugins I have "remember" my settings, for whatever reason BetterVolume doesn't, resetting everyone's volume to 100% (possibly 200%?) If there were a way to have it by default remember the custom volumes I've set for different people, it would be a much better user experience.
That said, It's always possible that I'm missing something/doing something wrong here, and that the requested functionality already exists. If so, sorry for the bother.
Thank you again for your work!
The text was updated successfully, but these errors were encountered:
BetterVolume does not have any "custom volumes". It directly overwrites the volumes used by Discord's own audio engine. If your volumes are resetting, it's your Discord installation resetting its saved volumes for whatever reason. Might be related to the remote audio settings experiment some users have.
I can imagine adding a feature for separate volumes, but I wouldn't want it to be the default. Otherwise you may "lose" volumes set while running the plugin when it's disabled or uninstalled.
Plugin
BetterVolume
Description
I love BetterVolume, it's of massive help to me when dealing with friends with really quiet mics. Unfortunately, given the nature of BD, whenever Discord updates I have to repair/reinstall it. While most of the plugins I have "remember" my settings, for whatever reason BetterVolume doesn't, resetting everyone's volume to 100% (possibly 200%?) If there were a way to have it by default remember the custom volumes I've set for different people, it would be a much better user experience.
That said, It's always possible that I'm missing something/doing something wrong here, and that the requested functionality already exists. If so, sorry for the bother.
Thank you again for your work!
The text was updated successfully, but these errors were encountered: