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

bypass still uses same amount of CPU #23

Closed
kjyv opened this issue Sep 28, 2017 · 1 comment
Closed

bypass still uses same amount of CPU #23

kjyv opened this issue Sep 28, 2017 · 1 comment

Comments

@kjyv
Copy link

kjyv commented Sep 28, 2017

This is maybe half a feature request, half a question. I understand the bypass command is intended to temporarily disable effects in the processing chain. I've noticed that plugins which are bypassed still run as if they were not bypassed, no input and no output is passed. Would it be possible within mod-host/lilv to set these plugins to a proper idle mode so they consume no cpu?

@falkTX
Copy link
Member

falkTX commented Apr 10, 2020

Sorry for the super long time in replying here.
But the answer if that, intentionally, mod-host keeps plugins running while they are bypassed (just with zero input buffers).
The idea is to keep plugins that use time always in sync, as otherwise we would have phase issues.

The CPU load depends on the plugin, some plugins do nothing when their input is zero, but some dont.
In any case, it is working as intended.

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