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

Abnormally Hight Cpu usage on "idle" modules. ( Reaper, standalone(native), Windows 7/10 ) #490

Closed
Ongomato opened this issue Feb 8, 2023 · 8 comments

Comments

@Ongomato
Copy link

Ongomato commented Feb 8, 2023

Some modules exhibit significant increase in CPU usage after not receiving any input for a short period of time(2-4 seconds). Especially problematic on heavy modules.
This happens in Reaper on all plug-in formats, and in a standalone native build, both on windows 7 and 10.
Doesn't happen in other DAWs ( FL studio, Ableton, Bitwig )

2023-02-08-15-55-49

@dromer
Copy link
Collaborator

dromer commented Feb 8, 2023

We've seen a couple odd issues with Reaper related to transport.
Do you see a difference in cpu usage when you have transport idle VS running?

@Ongomato
Copy link
Author

Ongomato commented Feb 8, 2023

Just checked, transport doesn't seem to affect this in any way.
I get exactly the same CPU usage as in standalone version.

@falkTX
Copy link
Contributor

falkTX commented Feb 8, 2023

This is likely related to denormals.
I hate the idea of messing up with global state from within the plugin, but for this I dont think we have a choice.

@Ongomato do you know how to get the latest github action builds? I can do a test build fix if you are willing to give it a try.

@Ongomato
Copy link
Author

Ongomato commented Feb 8, 2023

Sure, i can test if it works.

@falkTX
Copy link
Contributor

falkTX commented Feb 8, 2023

ok pushed a test build in https://github.com/DISTRHO/Cardinal/actions/runs/4127770798
should be ready in ~1h from now.

@Ongomato
Copy link
Author

Ongomato commented Feb 9, 2023

Tried the test build just now and it looks like the fix worked, the issue is gone.
Thank you.

@falkTX
Copy link
Contributor

falkTX commented Feb 9, 2023

Thanks for checking!

Will add this as part of the 23.02 release

@falkTX
Copy link
Contributor

falkTX commented Jul 15, 2023

This was an old bug we forgot to close, doing that now

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

3 participants