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

Reporting latency #183

Open
robbert-vdh opened this issue Feb 26, 2023 · 0 comments
Open

Reporting latency #183

robbert-vdh opened this issue Feb 26, 2023 · 0 comments

Comments

@robbert-vdh
Copy link
Member

There are still functions to set port latency ranges (and wow is that JACK API ever overly complicated), but those need to be called from the latency callback and that has been completely removed in #148. I can add it back as another Option<LatencyHandler> argument to client.activate_async(). It may also be useful to have the LatencyHandler expose methods to set the latency for a port or entire client to a single value and have it do all of the ceremonial computations for you. And also move the latency setting functions from Port to LatencyHandler while I'm at it since it can only be misused now.

Thoughts?

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

No branches or pull requests

1 participant