-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Option to disable live vu-meter feature #44
Comments
We do have Update: Checked it now and we do have it in the theme section in config |
I confirm, I switched the setting to true and vu-meter seems disabled and bar is filled up-to-cursor with plain color. But cpu usage doesn't change at all, still ~6-7% all the time. Does this option just disable ui vu-meter or does it stop monitoring pa streams ? |
I'm quite sure it should stop the monitoring but I might be wrong, it was some times since i implemented it. |
From what I saw on the code (quickly on Actually, |
Ok, should be easy to destroy the monitor streams when switching to static_bar, i will look into it. |
Well I'm actually doing some test locally, commenting monitor doesn't seems to really reduce usage. I'm investigating :) |
After some profiling and investigation, here it is: But major cpu time (of the other thread) is spent on drawing the ui. ~5% cpu usage for redrawing the ui, by growing the Obviously, when you want the vu-meter, you need to keep Quick fix would be to disable Better improvement would switch refresh to update event only (on key press or pa event fired), this would avoid refreshing continuously and keep same code path for all situation, but this would be a way larger change on the code. |
I did start on a major rewrite in dev but I havn't gotten to finishing it yet, But that rewrite is about detaching the ui from PA to be able to use diffrent backends like CoreAudio (osx) or even Alsa. During this rewrite would be a nice place to implement this but atm it would be to much of a change. I guess I will have to take some time and finish the dev branch :P |
I really like the vu-meter like pavucontrol does, but I'm that kind of guy who keep that stuff running h24 and it eats ~5% cpu all time.
I guess it's related to the runtime sampling for monitoring the volume per source. Original pavucontrol have the same behavior.
I think, if we can disable the vu-meter feature and just listening for event, it could reduce cpu usage to about nothing. I didn't checked the code yet, I'll take a look when I'll have time and prepare a pull request if possible.
The text was updated successfully, but these errors were encountered: