-
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 VU meter analysis/displays? #102
Comments
I'm currently working on disabling at least the added processing for the K14 and K20 metering, when it isn't used. I haven't measured whether this actually has a positive performance impact yet. Adding "no meter" meter scale option should be easy to do. The backend will still update the meter values, but the impact of that is minimal. |
Also, note that you can set the meter update interval in Line 120 in 9c4add8
It is currently set to 33 (ms). Setting it to 100 or even higher should lessen the burden on your CPU a bit, though the meters are a bit jumpy then. |
How about exposing that as a user option? |
Yes, that's the plan, but there are a lot of feature requests already, so I can't promise that it will happen soon. |
@SpotlightKid, @mxmilkiib: what should be displayed in the "no meter" meter scale case? Fader takes up whole channel width and meter disappears altogether, or a blank meter that takes up space or ...? |
Would we show the peak values? |
simplescreenrecorder-2021-10-25_12.26.27.mp4 |
I don't need to see the levels moving all the time and it's adding to the system lag I'm getting on this older laptop now I'm running a JACK/PipeWire first system.
Maybe there is a middle ground between bars and nothing that could at least denote there has not been silence on a channel in the last second?
The text was updated successfully, but these errors were encountered: