Skip to content

Increase the framerate limit for the visualizer. - #490

Merged
arybczak merged 2 commits into
ncmpcpp:masterfrom
leg7:master
Feb 13, 2022
Merged

arybczak merged 2 commits into
ncmpcpp:masterfrom
leg7:master

Conversation

@leg7

@leg7 leg7 commented Jul 20, 2021 •

Copy link
Copy Markdown
Contributor

I changed the maximum fps limit from 144 to 1000. I have a 240Hz monitor and today 360Hz monitors are consumer level tech available on the market.

As time goes on monitor refresh rates will keep getting higher and higher so changing this limit to 1000 should be enough for now.

@arybczak

Copy link
Copy Markdown
Collaborator

Are you sure this actually helps? On my system when I set the fps to e.g. 120 the output becomes less smooth than with 60.

@leg7

leg7 commented Aug 19, 2021

Copy link
Copy Markdown
Contributor Author

Are you sure this actually helps? On my system when I set the fps to e.g. 120 the output becomes less smooth than with 60.

It can become less smooth if your system can't consistently hit the framerate. So if your computer is not powerful enough to render 240 frames per second the output will looks jittery because the frametimes are inconsistent. This would not be an issue however if your computer is fast enough to render it properly though.

It can also look worse if the framerate doesn't match your monitor's refresh rate as the mismatch would introduce tearing. So for example if your monitor is running at 60Hz ( 60 refreshes per second ) and the visualizer is running at 120 frames per second you would probably notice screen tearing artifacts.

@arybczak
arybczak merged commit 727ca95 into ncmpcpp:master Feb 13, 2022
@arybczak

Copy link
Copy Markdown
Collaborator

Thanks!

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

Successfully merging this pull request may close these issues.

2 participants