-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weirdly Shaky Volume decibel info on obs v28 #60
Comments
update~ i tried manually removing all audio monitor filters~ thinking it must be the reason for this~ but apparently removing em all didnt reproduce this bug so far~ but if i were to add the filter without configurating it ( default) it seems to cause this bug again~ i tried deleting the plugin_config > audio monitor folder~ and adding just a single filter on a audio source~ this test showed interesting results~ only the audio source i added the filter seems to do the bug, rest of the audio sources seemed fine when changing vol etc~ so ig its mainly the plugin? |
@JoqniX I have had this issue as well. It has been plaguing us for months. We have had the issue on multiple versions of OBS v27. We have some success after disabling the settings Meter Output and Output Slider in the Audio Monitor Dock. After that, the db meter stopped fluctuating. The Websocket log still shows that OBS is still going up and down. |
yahallo~ @joelcarlton wait~ this has been going on in v27 too? wah!! also thank yu letting me know the temp fix for the groving/fluctuating db meter~ so yea i have a Automated Volume Change button made in SAMMI~ and ever since i switched to v28 i started facing this ~ ( which is dependant of the ws log ) and atm its been days right~ since i posted this. ig for now temp fix is to uninstall the plugin or not have any audio monitor filters at all! or ultimately we wait for exeldro to finally fix this bug in the coming update or so~ 🙏 also if yu have any temp solutions do share oka~ ;w; it sucks that this is happening. and i really dont wanna stop using audio monitor cuz its crucial must need! for my setup ;w; but pein~ |
We are seeing an issue where the web socket log shows 1000's of volume changes per second after we manually raised/lowered one of the faders. There seems to be no way to stop it without quitting the live stream and OBS. The whole system becomes sluggish and sometimes scenes can't be switched. Ironically the number in the db meter on top of the fader is not fluctuating. We do see the actual db meeter colors flip between green and red even if we drop the fader to the very bottom (-60 db.) This is a critical issue and hope there is a solution soon. We were forced to use this plugin since there was a growing delay in the audio when using the virtual camera and the default OBS monitor output. Does anyone have another solution for outputting audio without using the OBS monitor out or this plugin? for the short term until this plugin is updated? |
can anyone confirm if this bug still exists on the latest version which was pushed by exeldro? v0.8.2 edit - it seems to work fine for me atm~ thank god~ thank you exeldro 💖 |
@joelcarlton lmk how its going for you~ when using the latest verison~ if it works for you ill just close this issue~ |
I won't be able to test for a couple of days but I will update to the latest version and test.
… On Nov 26, 2022, at 8:27 AM, JoqniX ***@***.***> wrote:
@joelcarlton <https://github.com/joelcarlton> lmk how its going for you~ when using the latest verison~ if it works for you ill just close this issue~
—
Reply to this email directly, view it on GitHub <#60 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAADJPEHZVTVIZABICKC2ATWKIF37ANCNFSM6AAAAAAQQUPQSA>.
You are receiving this because you were mentioned.
|
its okie take your time~ |
hewwo~ it seems i've finally narrowed the culprit for this~ it was the audio monitor bug which had caused this~
please do refer this issue which i made on obs github for more details -> obsproject/obs-studio#7343
that this was affecting the obs audio mixer not the plugin's mixer
The text was updated successfully, but these errors were encountered: