Show Runner info (CPU | xrun) #128
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…un count in endpoint info which has been renamed to runner info
HMM.. there should be an OSC message sent every n-seconds (I forget what N is) when the audio is active.. I'll look into this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First pass at including some display only info. Drilled open the connection modal and added a CPU meter to the header. Noticed that there isn't a dynamic stream of CPU load info incoming, maybe that's by the design and the frontend / client is supposed to poll that?
Let me know if you need help plumbing this together :D If the client should poll the cpu load it's not really a big deal and we could also add a user setting to enable / disable that.
closes #116