Skip to content
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

the level meter needs to be fixed #13

Open
multidynamic opened this issue Jan 22, 2015 · 3 comments
Open

the level meter needs to be fixed #13

multidynamic opened this issue Jan 22, 2015 · 3 comments

Comments

@multidynamic
Copy link
Contributor

eosrei created an issue 2014-12-11
Halsey reports "my god, the level meter needs to be fixed! this is a long-time annoyance. I’m hoping there is a much better way to handle the metering than we are doing now which is really poor"

❌ A major issue

Matthew Adler 2014-12-28
What is the problem with the meter. Latency and ugly?

Halsey Burgund REPO OWNER 2014-12-29
Yes...both latency and the resulting ugliness, but the latency is the real issue, I think. This level meter was a total hack created about 5 years ago, so I'm hoping there is something more standard that we can grab from other audio applications/frameworks that will work better and be smoother. The general look of a left-to-right meter with the discrete blocks of color from green to red is a nice approach, but I'm flexible on the aesthetics. I just want it to be more responsive.
You must have come across level meters in your previous audio app work yes? Anything we can "borrow" or take hints from?

Matthew Adler 2014-12-29
Yeah, I have done this before. One of the apps drew a oscilloscope like display. The input just looked at some occasional incoming bytes and processing was quite a bit simpler than this one, but that may make it more responsive.

@multidynamic
Copy link
Contributor Author

Maybe just sampling every 16 ms (instead 100ms) would be less latent. (16ms ~= 60fps)

private static final int RECORDING_EVENT_INTERVAL_MSEC = 100; // 0.1 sec between updates

@13rac1
Copy link
Member

13rac1 commented Jan 27, 2015

A slightly more responsive meter would fix my issues with it. I'd love to see a rebuild/redesign of the activity, but it's Ok for now.

@hburgund
Copy link
Member

Yes, I agree. If changing that setting does indeed up the refresh rate, I think that will be fine for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants