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

FPS Limit #322

Open
jasperweiss opened this issue Nov 15, 2024 · 1 comment
Open

FPS Limit #322

jasperweiss opened this issue Nov 15, 2024 · 1 comment

Comments

@jasperweiss
Copy link

Neuromore causes my MacBook to draw more power than the charger can supply, it renders at over 1000 fps. On my desktop it even renders at 18000 fps. This should probably be capped at 60hz?

@stellarpower
Copy link

@jasperweiss You can turn down the refresh rate in the settings:

image

I am not entirely sure off the top of my head what the difference is between the interface and the realtime interface. May be that one is the plots, the other is the trinket extras, like the marching ants between the nodes. I have the engine set to the sample rate of my amplifier when training. Personally I wouldn't recommend running at 60Hz if your data are coming in faster than that or you will accumulate latency rapidly. The plotting takes quite a bit so you can turn that down though, and have a refresh a few times a second. I resample the data that's going into my feedback as that will never be able to display anything to me faster than the screen refresh rate, but the majority of the processing is one in, one out against the amplifier sample rate.

But yes, I have the same problem. By default, the classifier is more or less being thrown away and regenerated on every clock tick as per this line here. In my modified version I have a button to turn that finalise call off once everything is loaded and stable, and that has helped reduce the latency a bit, but it still lags when built in debug mode and draws a whole CPU core because there's a lot of inefficient stuff happening and all in the one thread. In essence the engine seems to be spinning round and round looking to ferry data around and often there may not be much that has actually happened. I've given up trying to fight it myself.

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

2 participants