mirror of
https://github.com/Rigellute/spotify-tui.git
synced 2026-04-26 16:15:55 +03:00
[GH-ISSUE #626] Rendering of Tickrate and Framerate a bit confusing #254
Labels
No labels
bug
enhancement
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-tui#254
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Bios-Marcel on GitHub (Oct 19, 2020).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/626
github.com/Rigellute/spotify-tui@81e357e218/src/ui/audio_analysis.rs (L39)Because the text shown in the UI is
Key Value ValueKey, it looks pretty confusing at first.I'd recommend something like:
Tick Rate: {}\tFPS: {}On top of that, FPS seems to a fixed number of minimum rerenders, as it always displays
4in my case. In reality, there can be more than 4 rerenders per second, for example when you hold down a key. Either way, is there a value of limitting the amount of rerenders? Why not go as fast and therefore smooth as we can?@Rigellute commented on GitHub (Feb 4, 2021):
This is a bit confusing, I agree. The tick rate defaults to 250ms (so 4fps, like you see). You can increase the fps by reducing the tickrate on start up:
I used 250ms as default as I saw a fairly large increase in CPU usage in my tests on different devices.
Will look into clearing this up.